-
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
Update buildcff2vf #825
Update buildcff2vf #825
Conversation
a8ecfcf
to
057dae6
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For now I've only looked at the Codacy report and requested some changes based on it. I'll plan on doing a closer review after you've made these changes. Thanks.
Also, the flake8 report has a few things from above and a few new things:
|
057dae6
to
3b8b790
Compare
@cjchapman @miguelsousa I fixed the Codacy and flake8 issues. I see the first two builds failed, but it looks like it is an issue with the build environment rather than the code. |
…tion Fixing outline compatibility can fail because the code assumes that the first font in the master_fonts argument to do_compatibility() is the default. Fix by passing in the default font index in the font list into do_compatibilization(), so that the region font list can be formed by deleting the actual default font from the font list. Fix same issue in CompatibilityPen.getCharStrings(). Add test case. Fixes #816
@readroberts (cc: @miguelsousa) this branch was trying to use the |
8deb2f1
to
e229453
Compare
@readroberts (cc: @miguelsousa) Correction: I've rebased this branch off the |
I'm dismissing my earlier review because the changes I requested have been made, and now I've touched this branch to fix the CI issues, so I think someone else should do the final approval of this branch.
A side effect of using the fontTools subsetter module to implement glyph subsetting with the -i option is that features are removed if they are not in the subsetter default features set. Since buildcff2vf is not intended to filter out features, I fixed this by setting the subsetter module's layout_features option field to '*', which causes it to pass through all features. Add test case. Fixes #817
When a point is a curve in one master source font and a line in another, the code will convert the line to a flat curve. However, the code in the class CompatibilityPen assumes that the point coordinates are absolute. A few months ago, I changed the parent class CFF2CharStringMergePen (in fontTools) from using absolute to relative coordinates, and forgot about this dependency. Also fixed the test cases that use the compatibilization option.
e229453
to
da615db
Compare
I've reworked the commits. Should be ready for @josh-hadley to review. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have nothing consequential to add here. LGTM.
Address issue 816: wrong set of masters referenced when fixing compatibility issues, if default master is not the first font the master font list.
Address issue 817: fix unintentional filtering of features when using the subsetting option.