-
Notifications
You must be signed in to change notification settings - Fork 13
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
Solve nested components #5
Comments
Looks like ufo2ft has a mechanism to flatten components on export (by adding a filter to the UFO). Maybe I’ll use GlyphsLib then ufo2ft rather than a direct fontMake export. Should solve it. |
For now that’s the best answer. I’ll work on getting a fontmake flag to do it. |
@aaronbell @simoncozens Could fontmake solve this? or do you have workaround proposal for now? |
I have pull requests against fontmake and ufo2ft. If/when they are merged, it will be easy to solve. Until then, convert to UFO and add the lib key that Aaron mentions above. |
@minjooham I will take care of it in a build script to convert to UFO and then build the font. No need to change the source format in the repro. |
Great! Thanks a lot @aaronbell |
What is the current status of this? |
@davelab6 i will be able to resolve it in the build script. :) |
The branch / PR that I created flattens components and resolves this issue :) |
@minjooham said,
From From https://github.com/googlefonts/fontbakery/blame/8cf2698f36d8e6562444c0f8b09104bc75e709c5/Lib/fontbakery/profiles/glyf.py it looks like @simoncozens recently authored this check.
Simon, Do you know any tips to fix this?
I guess if this is resolved the tips should be added to the fontbakery check metadata :)
The text was updated successfully, but these errors were encountered: