-
Notifications
You must be signed in to change notification settings - Fork 168
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
[CheckOutlinesUFO.py] KeyError: missing glyph that, well, is correctly missing #228
Comments
This is perhaps not a significant problem for anyone else, I recognise that. I just like to work inside of the |
now reporting a warning about skipping a glyph that is not in the UFO glyph map rather than crashing with an error.
I agree that this scenario should not cause the code to crash like that. I just committed a change yesterday that I think will prevent this from happening in the scenario you described, though it will still happen if you specify such a glyph on the command line. The PR (which is merged to the master branch) is here: I've got a proposed fix for the case in which you specify such a glyph on the command line in PR 229: |
now reporting a warning about skipping a glyph that is not in the UFO glyph map rather than crashing with an error.
Fixed with #229 |
now reporting a warning about skipping a glyph that is not in the UFO glyph map rather than crashing with an error.
Running
checkOutlinesUFO
on a specific file throws errors about missing glyphs, and this is sensible, but is it the right behaviour? If something is defined inlib.plist
but missing actual data, should it not skip/delete the reference in the flattening process?The text was updated successfully, but these errors were encountered: