optionally merge TTX tables found in UFO3 data folder
See original GitHub issueUFO3 has a ‘data’ folder where one could store extra, application specific data.
http://unifiedfontobject.org/versions/ufo3/data/
I propose that ufo2ft automatically merges into the compiled font any .ttx tables which it finds inside font.ufo/data
folder, if the filename starts with the org.fonttools.*
reverse domain.
Before I start working on the patch, I wanted to see if people liked the idea.
The immediate use case which I have in mind is merging the private TSI* tables where Microsoft Visual TrueType stores the hinting source data.
Having ufo2ft merge these automatically upon compilation would be handy I think.
What do you guys think?
Issue Analytics
- State:
- Created 7 years ago
- Comments:28 (14 by maintainers)
Top Results From Across the Web
fonttools/NEWS.rst at main - GitHub
A library to manipulate font files from Python. Contribute to fonttools/fonttools development by creating an account on GitHub.
Read more >fonttools [python-library] - Occam :: Details
| fontTools is a library for manipulating fonts, written in Python. The project includes the TTX tool, that can convert TrueType and OpenType...
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
just to clarify: when i say VTT stores its sources in the “binary” private tables, I just mean that they are stored in the compiled font, I don’t mean they are binary data. It’s actually UTF-8 encoded plain text, containing the VTT Talk and assembly source code.
Back to topic:
Should this issue be closed as ‘wontfix’ or left open? 😃