> I wonder whether I should hook up the incremental loading stuff to
> get 14.ttf to work with the new backend - after all, the rest of
> FontVal already checks hmtx, and the hinting/rastering backend don't
> really need to care about advance widths perhaps.  Although that's
> unusual usage of Freetype, but ghostscript already uses freetype
> that way.

This sounds like an interesting and sensible approach.

> Lastly I think this was mentioned before: 15.ttf, 26.ttc have rather
> broken EBDT's so they fails with FreeType rather early, but the 1.0
> backend can go a lot further; and 26.ttc is mostly an old authentic
> microsoft font (with DSIG removed but otherwise identical),

Oh no, it's not identical!  There is a lot of invalid glyph outline
data in this font.


    Werner

_______________________________________________
Freetype-devel mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/freetype-devel

Reply via email to