-
Notifications
You must be signed in to change notification settings - Fork 13
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
Support component flattening #268
Conversation
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.
the flattening logic LGTM, but would prefer if disabled by default
it just occurred to me that, after flattening components, we may end up with orphan glyphs that are no longer used by composite glyphs and may also have no direct cmapping nor be substituted to from GSUB rules so they are basically dead weight, which a subsetter --unicodes='*' would surely get rid of, but maybe the compiler could/should be smarter and avoid them to be left in. |
Co-authored-by: Cosimo Lupo <clupo@google.com>
Good point, filed #270 |
Improves Oswald build alignment with fontmake as run by gftools. See #250 (comment).
Builds on #267.
Once this plus the PRs it builds on are merged the largest source of difference in
glyf
for Oswald is that we don't remove implicit on-curves.