-
Notifications
You must be signed in to change notification settings - Fork 93
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
Glyphs.app's Feature Condition Syntax is not supported #951
Comments
I think that's Glyphs.app's specific way to specify FeatureVariations-style conditional substitutions, the official FEA spec is set to encode these differently -- if/when @simoncozens proposal at adobe-type-tools/afdko#1350 is merged (not sure what's the status on that). fonttools, which fontmake uses to compile OT layout features, only supports the latter. glyphsLib may eventually add support for translating from Glyphs.app's own notation to the FEA variation syntax, but I don't think anybody is actively working on that, see googlefonts/glyphsLib#800 |
Thank you for the information! |
I'm having the same situation with another project. I left a comment in the glyphsLib#800 issue linked above. |
Same problem here. |
Running into this, as well. Also posted over on the glyphsLib issue. |
I'm using fontmake to export VF with CFF2 outlines from a Glyphs3 file. It builds the UFO and designspace but then fails when I have this code in the feature rlig:
This is the error:
Generating fonts from Designspace failed: <features>:510:1: Expected glyph class definition or statement: got NAME condition
(line 510 is: condition 18 < wght < 278, wdth < 40;)
Is there way to go around this changing the Glyphs file? Or some other simple solution?
The text was updated successfully, but these errors were encountered: