Unable to Find Glyph $09F8

FontCreator - Font Editor FontCreator - Support
1
  1. I ran the Validation Wizard which identified one problem at $09F8
  2. I tried to search for “09F8” and “#09F8” and “$09F8” but nothing worked.
  3. I changed the display mode to decimal and ran the validator again
  4. This time the validator reported the problem at glyph index 2552
  5. I searched for “2552” and found nothing
  6. I searched for “#2552” and found the glyph

Did I do something wrong?

2

2552 is $9F8

So try to search for #9F8

3

That still doesn’t find it.

Searching for “#$9F8” does find it. So does searching for “#$09F8”

4

Yes, that is correct.

5

Searching for “#$9F8” finds me the glyph with glyph index #$09F8, searching for “$9F8” finds me the glyph at code point $09F8 and searching for “9F8” finds me any glyphs with the character sequence 9F8 in the glyph name. I wouldn’t expect a search for “#9F8” to find anything, because 9F8 isn’t a valid decimal number. :wink:

6

Was it really showing $E9F8? Then it is a bug as it actually should have been $9F8.

7

No. It shows $09F8 — that was an error due to tiredness, I have edited the thread title and post titles. I was editing hex codes in glyphnames.dat beginning with E at the time, but it still doesn’t work as expected.

I understand that the # means glyph index, but if the captions are set to Glyph Index, and Code-points are in hex, why are Glyph Index numbers shown in Hex?

This particular glyph has no code-point so only a Glyph Index search could locate it.

8

I must admit I sometimes find it annoying to have the glyph index as hexadecimal, but I’m not sure how other users feel about it. We could decide to always show glyph indexes as decimal.

9

I’d like them to be postcript names of course!

10

I would prefer Unicode character names, but never decimal.

11

I don’t understand this comment. Is it a joke? Maybe you meant postcrypt names?

How can Glyph Index numbers use Glyph Names?

12

I just keep mentioning it… regardless of the subject.