On 8/20/05, Werner LEMBERG <[EMAIL PROTECTED]> wrote: > > From: Rogier van Dalen <[EMAIL PROTECTED]> > > FWIW: someone reported a similar problem in my TrueType loading > > code, for another font. I was not sure this was due to a bug in my > > code. My guess was, though I have not yet had the time to check it, > > that the font set bit 2 of "flags" in the "head" table, which > > according to http://www.microsoft.com/typography/otspec/head.htm > > means "Left sidebearing point at x=0". This might lead an > > unsuspecting operating system to mask a bug in the font. > > Indeed, the font in question (Gotyk3.ttf) has the `left sidebearing > point at x=0' bit set; with other words, the font is buggy. > > What do you think of translating only if this bit in the `head' table > is set? Currently, FreeType ignores it, but it seems that Windows > uses it. Rogier, how do you handle this your engine?
Ermmm, I ermmm, just don't, basically. I have other priorities than the Freetype project: buggy fonts tend to look buggy on my rasteriser, and I'm happy with that. The strategy you propose sounds good to me, though I think you forgot a "not". Regards, Rogier _______________________________________________ Freetype-devel mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/freetype-devel
