[Freetype] Re: Freetype digest, Vol 1 #404 - 3 msgs

[Jon Harrop]

> > To do this I either need adaptively subdivided contours which are
> > continuously scalable (i.e. no pixel hinting or integer round-off)
> > or I need to get hold of the contours as lists of implicit curves
> > (Bezier's, I assume) so that I can feed them into my own code.
>
> The code for that it rather deeply buried into FreeType...

Perhaps this part of FreeType (i.e. loading TTFs) should be split off into a 
separate library? Either that or alter the API to allow the library users to 
access the contours.

> > I don't want to use the FreeType rasterizer as I need to apply my
> > own fill types and stroke and fill the contours.
>
> But this is the very thing what FreeType is all about!

I would be able to use the FreeType rasterizer if it treated text in an 
infinitely scalable way. But it doesn't appear to. Bounding boxes, for 
example, appear to be specified in integer units. So the layout of text will 
be ruined by the accumulation of unecessary round-off errors.

On top of that, I can't get glyphs as contours. So it appears that my only 
option is to gut FreeType, cut-n-paste the TTF loading part into my own code 
and not link to the library.

Is this right or am I missing something?

Cheers,
Jon.