New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Should use sfntVersion to pick glyph outlines #419
Comments
I'm pretty sure that the test in question made the wrong assumption about what should happen in this particular case. Looking at the OpenType definition for
Rather than saying "which data to use based on the version", the only prescription here is for "which version to use, based on the data". At best we can only conclude that, because the |
I’ve asked the community (at opentype-layout@unicode.org) whether or not they’d like to have the test case, cc’ing you. Let’s discuss there. Personally I have no opinions here; it seems like a rather theoretical problem anyway. |
Was this ever resolved? Should we look at this or not? |
@brawer seeing you were recently active - any update on this? |
OpenType.js should look at the
sfntVersion
field in thesfnt
offset table to determine whether to use PostScript or TrueType outlines.Expected Behavior
In the Unicode test suite for text rendering engines, test case SFNT-1 should pass.
Current Behavior
Test case SFNT-1 is failing.
Possible Solution
If a font contains both
CFF
andglyf
tables, look at thesfntVersion
field in the sfnt offset table to decide which one to use.Steps to Reproduce (for bugs)
AB
as string to display.CFF
underneathA
andB
; instead got this:The text was updated successfully, but these errors were encountered: