>> I'm wondering, how about leaving the CFF limit as is and apply it
>> to Type1, too, and just turn off hinting for that glyph? Not
>> entirely correct, but an easy way out when the hinting obviously
>> went wrong.
>
> Actually, since the FreeType hinter handles it fine, how about
> returning a specific error code when this happens and fall back to
> the old engine, if it is available? Otherwise, perhaps the
> autohinter?
Maybe, yes, but I think unhinted is the easiest solution. However,
this shouldn't prevent you with testing other solutions :-)
Werner
_______________________________________________
Freetype-devel mailing list
Freetype-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/freetype-devel
