-
Notifications
You must be signed in to change notification settings - Fork 51
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 "disabled" glyph classes #763
Comments
Oh, heavens, I never even looked at those because I had them disabled and assumed that glyphsLib would therefore ignore them. I will close this (with more than a little embarrassment). But isn't it odd that glyphsLib doesn't respect the "disabled" flags in the Glyphs file? Makes it a little tricky to generate fonts while a project is in progress. |
I think #761 should fix this. |
Looks good. |
We need to fix handling of disabled classes, #761 does not actually handle it. |
For example, features.fea in all generated UFOs has "uni0305" in "@MarkClass1" but "overlinecomb" elsewhere in features.fea and all other files.
To reproduce, run glyphs2ufo on this file (Junicode Italic).
Is this a bug, or is there something odd about this file?
The text was updated successfully, but these errors were encountered: