-
Notifications
You must be signed in to change notification settings - Fork 24
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
iup_delta_optimize: fix interpretation of contour_ends #565
Conversation
…ur lengths Towards fixing #564 Also needs corresponding changes in the fontc calling site
Fixes googlefonts/fontations#564 requires googlefonts/fontations#565 to be released and write-fonts to be bumped first
this will a breaking change for fontc, should I also bump write-fonts minor version within this same PR, or you prefer a follow-up? |
Fixes googlefonts/fontations#564 requires googlefonts/fontations#565 to be released and write-fonts to be bumped first
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure if this is ready but the fix lgtm.
Probably a follow-up but current policy is merge without approval for version bumps. |
thanks for the review, yes it's ready but we need to update write-fonts first before we can integrate this |
sorry, I meant before we can integrate googlefonts/fontc#390 |
Bumped minor because #565 introduced a breaking change to iup_delta_optimize
Fixes googlefonts/fontations#564 requires googlefonts/fontations#565 to be released and write-fonts to be bumped first
Fixes #564
the input and expected result is taken from what fontmake/fonttools spit out for Oswald's glyph "two"
EDIT: Commit 36a8929 also fixes #567