-
Notifications
You must be signed in to change notification settings - Fork 52
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
Disabled features still interfere with automatic code #1026
Comments
does ufo2glyphs un-comment the contents of these
I guess we could do that only when minimal=True (fontmake sets that for compilation) |
Yes.
Good idea. |
Partially fixes #1026 by handling the case where we are building with fontmake. When round tripping is desired, the generated UFO when built with ufo2ft will still have the above issue.
If a font has a disabled feature, we will still write a feature block to the UFO but with
# disabled
comment and all of its contents commented out. For feature with automatic code generation likekern
ormark
this will prevent ufo2ft from generating code for this feature. We could fix this by commenting out the whole feature block, but then going back from UFO to Glyphs will drop the feature (do we still care about this?).The text was updated successfully, but these errors were encountered: