Check for glyph names are confused by multiply encoded glyphs
See original GitHub issueIn https://github.com/khaledhosny/reem-kufi master I get:
ReemKufi-Regular.ttf: Glyph 0x00A0 is called "space": Change to "nbsp" or "uni00A0"
(which should be skipped anyway, see #819) but that glyph is used for both space and NBSP (cmap
entries for both characters map to the same glyph) which is a common practice.
The code should detect such multiple mappings and accept the glyph name if it is good for one of them, or just give up since the name is bound to be “wrong” for all but one of them any way.
Issue Analytics
- State:
- Created 7 years ago
- Comments:12 (10 by maintainers)
Top Results From Across the Web
Finding and Changing Glyphs | CreativePro Network
There are three methods for picking the glyph you want to find. The first one is the easiest: Simply highlight the first glyph...
Read more >PostScript AFM file and glyph names - fonts - Stack Overflow
Glyphs which aren't encoded have a character code of -1 in the AFM file, so you can't look those up in the Encoding....
Read more >make: /bin/sh: 1: Syntax error: "(" unexpected #7 - GitHub
I need to generate these TTF files in order to verify if my changes to the ... Check for glyph names are confused...
Read more >Finding common font problems automagically - FontForge
Check Unicode/Name mismatch Look for glyphs whose name indicates a unicode value different from the one attached to a glyph. So if a...
Read more >Multiple Masters, part 2: keeping your outlines compatible
In order to interpolate, Glyphs needs compatible drawings in all masters. Here is how to make sure your paths are ready for interpolation....
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
“It should not be treated as an error, no.”
yeah… it seems that the real solution here is to simply drop the “Check glyphs have unique names” check as pointed out by @m4rc1e