> Brad has shown me a font where ttfautohint's code causes vertical
> clipping of glyph `g' on some (older) Windows IE versions since its
> depth at same ppem sizes exceeds the usWinDescent value.
Uh, oh. This was caused by a very embarassing bug: one of the central
bytecode routines to round to integers was buggy.
Since the fix (already in the git repository) considerably improves
the appearance of a lot of fonts, I'll soon do a new release of
ttfautohint.
Anyway, the central question remains: What to do if hinting might
exceed the usWin values (e.g. by using ttfautohint's -x option).
Werner
_______________________________________________
Freetype-devel mailing list
Freetype-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/freetype-devel
