New script: which characters in a TTF are not in any GF `.nam` subset?
See original GitHub issuePlease provide a script to tell us which characters in a TTF are not in any GF .nam
subset.
Issue Analytics
- State:
- Created 6 years ago
- Comments:7 (5 by maintainers)
Top Results From Across the Web
Redefining GF Latin Core Set · Issue #13 · googlefonts/glyphsets
I made a test page and indeed the actual latin subset served by GF no longer includes these characters, so they should be...
Read more >subset — fontTools Documentation - Read the Docs
It accepts any TT- or CFF-flavored OpenType (.otf or .ttf) or WOFF (.woff) font file. The subsetted glyph set is based on the...
Read more >Subset Font By Specific Glyphs - unicode - Stack Overflow
I'd like to reduce the size by creating a subset which only contains the specific characters within an HTML page. So, ideally, I'd...
Read more >Creating font subsets - Dev Diary
Subsetting fonts is the process of taking a large font file as input and creating other smaller files, with fewer characters or OpenType ......
Read more >Font Subsets - Latin, Cyrillic, and Greek Fonts
Asia/Pacific [APac] — This font includes Latin script support for Pinyin, Papua New Guinea, Philippines, languages from India, China and Myanmar and other ......
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 FreeTop 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
Top GitHub Comments
When I say module, I also really think it should be a stand alone github repository. Everything that needs to read these nam files basically needs code from there. We already have some copy and paste job somewhere in pyfontaine and there’s also graphicore/googleFontsTools which is a mess to keep in sync, but used for specimentTools and much less in size than the google/fonts repository.
These things happen because we don’t want to download thousands of fonts, just to read some nam files.
The new repository could be a git submodule of google/fonts.
I’ll close this here, since it is now tracked at the googlefonts/tools issue tracker.