-
Notifications
You must be signed in to change notification settings - Fork 475
atttempt to fix offset overflows in MarkBasePos subtables #1297
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
atttempt to fix offset overflows in MarkBasePos subtables #1297
Conversation
this should also fix the first of the two errors reported by @miguelsousa in #1296 (comment) |
@anthrotype this patch does NOT fix the Source Serif overflow error reported in #1296.
|
@miguelsousa thanks for checking, I'll have a look next week |
Yeah, I checked and indeed, this PR doesn't fix that Source Serif Pro build issue. I'm going to merge this PR, as it fixes some other Noto build failures. We'll try to fix #1296 in a different patch. |
Can you check how many marks and how many bases in there? |
not many: 28 marks and 71 bases |
That's unusual. How can I test this easily? |
Ok I follow up on the other issue. |
if an offset overflows within a MarkBasePos (GPOS lookup type 4), we attempt to split it by moving half of the mark classes to the new subtable.
Fixes googlefonts/fontmake#450