Strange glyphs displayed when using private use area (PUA)
cormullion opened this issue ยท comments
When you display glyphs from the Private Use Area U+F000 ... you see strange glyphs in the list at the left and the text entry field:
I'm interested to know what they are. ๐๐ค
I have no idea, this is rendered by the OS.
That looks like the Apple Times.ttc file - which is not OpenType.
If you extract the TTFs from the TTC, you can open them in FontCreator and FontLab 8 (not 7) - but they are a complete mess.
And the FontCreator developer says they have bad check sums.
Dumping the TTF with ttx results in multiple "excess bytes" warnings when dumping the glyf table.
These errors prevent the fonts from working/installing in other operating systems - so they could just be Apple sabotage.
@cormullion These non-standard Apple fonts are the problem.
@justvanrossum Perhaps a warning is appropriate when fonts are opened which contain non-standard tables (feat morx etc.). Or is FG supporting this non-OpenType stuff?
These non-standard Apple fonts are the problem.
It's the same with any ttf font - I just chose Times because it's in the system.
FontGoggles uses HarfBuzz, which does support various Apple specific features.
But indeed, this issue is about the UI text, which is rendered by the OS, so FontGoggles has no influence on that.
Ok, you can close this if you like. My curiosity can go unsatisfied (for now), I was hoping it was going to be something intriguing. ๐
You probably installed a font that has glyphs for these characters and for some reason the UI toolkit font fallback is using it which is rather unusual since a well behaving font fallback system should skip PUA since there meaning is tied a specific font and fallback to ad different font makes no sense.
If you go to FontBook and search for any of these characters, it should tell you which fonts has them. My system has two fonts that support U+F000 but I get what looks like a .notdef glyph when I paste it into FontGoggles text input field, so no fallback is happening for me. May be your system UI font does actually support these characters?
You probably installed a font that has glyphs for these characters and for some reason the UI toolkit font fallback is using it which is rather unusual since a well behaving font fallback system should skip PUA since there meaning is tied a specific font and fallback to ad different font makes no sense.
@khaledhosny Thanks - I think you've solved this. For the first two Private Use Areas, MacOS displays question marks for the first one, but uses fallback fonts for the second one. I was picking up weird glyphs from FairFax and a Nerd Font. I agree these fonts' PUA glyphs probably shouldn't be used in this context.