-
Notifications
You must be signed in to change notification settings - Fork 7
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
Hhea.pm update() bug #9
Comments
Actually, the OT spec says:
Certainly this means, in the least, that whitespace glyphs contribute to advanceWidthMax but not to any of the other three fields in question, so I suspect neither the current nor proposed code can be right. But, imo, this actually opens a small can of worms. What exactly is meant by "glyphs that have contours" ? Does it mean that composite glyphs don't count since they don't actually have contours? I wouldn't think so, in which case the wording is poor. Assuming the test of
|
Hangs on the meaning of I'm thinking that if GID 0 does not pass the test
... then the reversed
... I'm just imagining how this would work - I've done no testing on this. |
Is this better?
|
I made a small modification ...
... to avoid the situation of
I ran my largest pipeline process with this code installed in Thanks for the assistance!! |
I believe that Hhea->update() needs the following modification. This is based on the convention of taking the "extent" for empty glyphs to be the LSB rather than the ADW. I've done some (but not extensive) testing on this ...
The text was updated successfully, but these errors were encountered: