-
Notifications
You must be signed in to change notification settings - Fork 4
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
Breite-Light.ufo refers to “component_1” without defining it #1
Comments
This reminds me of a finding I made recently: Tarobish/Katibeh#94 (comment)
|
But this is different, there's no other glyph that could be @brawer I am wondering, while the UFO docs say nothing about how to handle missing components, the pen protocol is explicit in skipping them, see: https://github.com/behdad/fonttools/blob/master/Lib/fontTools/pens/basePen.py#L197 If you would use a normal segment pen in fontmake, it should just drop the missing component without further notice. This is may be the reason why other ufo-consumers did not complain earlier about such files. But, I'm not aware of each component handling case in ufoLib. Is the source of your error in ufoLib? I guess the source of the UFO here is Glyphs, so someone should have noticed this before—well, or not. |
Just double-checking before nagging the Glyphs folks: can you confirm that Breite-Light.ufo was indeed written by Glyphs? |
Good call, and I don't know in fact :-) @nicolasfpauly how did you make these ufos? Seems, like I was wrong BTW:
While a recent ufo generated by glyphs:
|
In Breite-Light, glyph uni090E refers to “component_1” which is not defined by the font. Because of this dangling reference, fontmake cannot build the font.
The text was updated successfully, but these errors were encountered: