marty39
2015-06-01 20:40:10 UTC
I loaded an old TrueType file into Fontforge version 4:18 AEST 4-Mar-2015
(Mac) and got a lot of warnings that said "The glyph named ... is mapped
to.... But its name indicates it should be mapped to...." Since the glyphs
were correctly named in the original file, I wanted to change the code
points. The warning didn't say "its code point indicates its name should be
..." so I figured if I told Fontforge to fix the problem it would change the
code point, not the name.
Wrong. Menu: Encoding: Force Encoding forced the name, not the encoding.
Menu: Element: Validate: Find Problems, check only the coding issues in the
Random tab, it says "This glyph is mapped to a unicode point which is
different from its name," I click the Fix button, and the name changes, not
the code point.
The only way I can see to fix the problem is to go through the glyphs one at
a time, click Glyph Info in the context menu, check visually to see if the
name matches the unicode name, and hit the 'a' key if it doesn't. That's
tedious. There has to be a better way.
Please help.
--
View this message in context: http://fontforge.10959.n7.nabble.com/Glyph-mapped-to-a-unicode-code-point-which-is-different-from-its-name-tp14804.html
Sent from the User mailing list archive at Nabble.com.
------------------------------------------------------------------------------
(Mac) and got a lot of warnings that said "The glyph named ... is mapped
to.... But its name indicates it should be mapped to...." Since the glyphs
were correctly named in the original file, I wanted to change the code
points. The warning didn't say "its code point indicates its name should be
..." so I figured if I told Fontforge to fix the problem it would change the
code point, not the name.
Wrong. Menu: Encoding: Force Encoding forced the name, not the encoding.
Menu: Element: Validate: Find Problems, check only the coding issues in the
Random tab, it says "This glyph is mapped to a unicode point which is
different from its name," I click the Fix button, and the name changes, not
the code point.
The only way I can see to fix the problem is to go through the glyphs one at
a time, click Glyph Info in the context menu, check visually to see if the
name matches the unicode name, and hit the 'a' key if it doesn't. That's
tedious. There has to be a better way.
Please help.
--
View this message in context: http://fontforge.10959.n7.nabble.com/Glyph-mapped-to-a-unicode-code-point-which-is-different-from-its-name-tp14804.html
Sent from the User mailing list archive at Nabble.com.
------------------------------------------------------------------------------