googlefonts / googlefonts/ufo2ft
Avoid renaming glyphs during compilation
- Dominant language
- Python
- Stars
- 176
- Forks
- 48
- PR merge metrics
- No merged PRs in 30d
Description
Renaming glyphs after the fact is a costly operation in ttLib, because it requires serializing (to flush old glyph names out of loaded tables) and immediately deserializing the font. The font should be compiled with the target glyph names from the get go. Compiling features will need the production names mapping so designers can continue to use design names in feature files.
Linked to https://github.com/googlefonts/ufo2ft/issues/485.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing the ttLib compilation flow and the feature-compilation path described in the issue, then inspect how production and design glyph names are mapped. Verify that compilation begins with target glyph names, feature files still use design names, and the post-compilation serialize/deserialize rename step is no longer needed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- computer-graphics, tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100