-
-
Notifications
You must be signed in to change notification settings - Fork 18
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
ValueError raised instead of BooleanOperationsError #62
Comments
this is an edge case... and the spec allows this https://unifiedfontobject.org/versions/ufo3/glyphs/glif/#point-types
BooleanOperation should treat it like a line segment... |
@moyogo who/what tool created that ufo? |
@anthrotype Festive has the issue in the Glyphs files, the issue isn't created when glyphsLib generates the UFOs. |
I don't understand. You tried running booleanOperations from within Glyphs.app? Or on a UFO exported from Glyphs.app? |
Neither. Fontmake was used on the Glyphs file. |
So you saying that the .glyphs source itself contains curve segments without offcurve points. Is that even legal for Glyphs.app? |
@vv-monsalve Did Festive have Glyphs sources initially or did they come from a different format? |
@anthrotype the outlines were definitely broken in Glyphs.app so it's not valid there. |
The issue is not that the outlines are bad, but that a meaningful error should be raised when it is the case. |
well, actually they are valid at least according to the current UFO spec, as frederik pointed out above. |
The designer provided Glyphs sources, although I understand they used to be Fontlab files originally |
This is a followup to googlefonts/ufo2ft#492 (comment)
booleanOperations should probably raise a BooleanOperationsError instead of a ValueError with the two glyphs taken from https://github.com/googlefonts/festive:
https://github.com/googlefonts/ufo2ft/files/6221735/OutlineTest.ufo.zip
The text was updated successfully, but these errors were encountered: