> I've run across a font that causes an assertion failure at line 591
> in cf2hints.c:
>
> /* paired edges must be in proper order */
> FT_ASSERT( !isPair ||
> topHintEdge->csCoord >= bottomHintEdge->csCoord );
>
> I'm wondering: is there some reason this is an assertion, rather
> than an error that gets reported back to the caller? I.e., why
> doesn't it fall into the same general category as any other sort of
> invalid/corrupted font?
I don't think there's a specific reason for this. This code was
simply inherited while integrating it to FreeType, and up to now we
haven't seen a failure here.
> I can extract the font and post it, if needed.
Please file a bug report and attach the failing font to it!
Werner
_______________________________________________
Freetype-devel mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/freetype-devel
