Should compileTTF() call cu2qu?
See original GitHub issueRight now I need to manually call cu2qu to convert fonts with cubic outlines before calling compileTTF()
, but it might make some sense to do this by default in some way or another.
Issue Analytics
- State:
- Created 7 years ago
- Reactions:1
- Comments:5 (1 by maintainers)
Top Results From Across the Web
cu2qu - PyPI
This library provides functions which take in UFO objects (Defcon Fonts or Robofab RFonts) and converts any cubic curves to quadratic.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
One problem of calling
font_to_quadratic()
beforecompileTTF()
is that it modifies the font in place which is problematic if the caller wants to continue working with the original font (e.g. a font editor exporting the font), so I thinksetupTable_glyf()
is a good place to do the conversion without having to modify the source font.I think we can add optional parameter for error tolerance to
compileTTF()
.(with what error tolerance though?)