fonts/readerly
1
0
Fork 0
Code Releases Activity

Fix zero-area contours after export to TTF

Browse Source
This commit is contained in:
Nico Verbruggen
2026-03-02 13:33:08 +01:00
parent 834534a00c
commit b2160079a7
3 changed files with 96 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
README.md
View File

@@ -87,4 +87,12 @@ Several metadata scripts are applied via FontForge:
#### Step 4: Export
The final fonts are exported from FontForge as both SFD (FontForge source) and TTF. The build supports optional old-style kern tables, but this is off by default because it has no effect on device tests.
The final fonts are exported from FontForge as TTF. A cleanup step removes zero-area contours that can cause missing glyphs on macOS. The build supports optional old-style kern tables, but this is off by default because it has no effect on device tests.
#### TTF cleanup (manual exports)
Some FontForge exports emit 1–2 point contours in the `glyf` table. macOS can treat these as invalid and skip the glyph entirely (for example, `m` or italic `u`). The build pipeline removes these zero-area contours automatically. If you manually export a TTF from an SFD and see missing glyphs, run:
```
python3 cleanup_ttf.py out/ttf/Readerly-Regular.ttf
```