Hello,
I recently exported one of my font families to preview it in FontBook on Mac. I am being warned of missing characters and I don’t know why (screenshot attached). Does anybody know why this is happening, what it means, and how to fix it?
Best,
-Sam
Make sure you cover the Mac Roman character set, which you can find in the left sidebar of Glyphs.
Does the warning give you any details as to which characters are missing?
I tried hovering over the warning and it old me “This font doesn’t support all characters in the current sample”. This is incorrect because every character I type shows up and I’m sure it’s included in the font. What I also find strange is that this warning isn’t showing up for other fonts I’ve exported in the past.
I think it’s important to note that the font showing the warning is the only font I’ve exported with the newest version of Glyphs 3 (3.3). I don’t think anything is wrong with the file because it opens just fine and there are no warnings, errors, or incompatible glyphs.
Do you cover the character set I mentioned?
Does fontbakery.com report anything?
Hi Sebastian,
I looked at the interface for “fontbakery” and I don’t know what I’m looking at. Can you tell me a little bit about what this tool is and what the various options mean?
None of the fonts I’ve created cover the entire character set you mentioned. However, only one of them shows the warning I previously mentioned in FontBook. I tried an experiment where I saved and exported a font I haven’t worked on for a while in the newest version of Glyphs 3 (there is no warning for this font in FontBook while the warning for the other file still remains). Perhaps this indicates that something is wrong with one of my source files?
Hi Sebastian,
I wanted to let you know that I found the culprit of the issue. The font is an all-uppercase font and I hadn’t mapped uppercase characters to their lowercase counterparts using multiple unicodes yet. The warning is gone now.
I just have one last question about the article for creating an all-caps font (Link: Creating an all-caps font | Glyphs). In this article, they talk about the double-bind of the “I” character in relation to Turk languages. I just want to make sure I’m interpreting what the article says correctly. If there is no “Idotaccent” in the font, all you need to do is make sure that the uppercase “I” corresponds to ‘i’ and ‘idotless’, correct? Moreover, the ‘i’ will already map to its uppercase counterpart if selecting “Update Glyph Info” from the “Glyph” menu. Therefore, the only instruction that needs to be pasted in " Glyph > Add Glyphs…" is “I=idotless”.
Please let me know if I’m missing anything.
Best,
-Sam
You need all three i’s for making Turk language work. Because you need to have the locl feature that switches i into idotaccent.
Hi Rainer,
I don’t think I was being clear enough in my last reply (my apologies). I’m centering my font around support for the basic, Central European, and Western European character sets. Languages aren’t my forte and I’m just seeking some clarification so I can learn and make sure that I’m interpreting what I’m reading correctly.
My font is an all-uppercase font and doesn’t have an “Idotaccent.” I’m trying to appropriately map lowercase letters to their uppercase counterparts when typed on the keyboard. It seems like the only unicode relationship that needs to be considered in my case is “i → I” (this relationship should be taken care of via the Update Glyph Info command in the Glyph menu). Therefore, no other steps need to be taken for my font. Is this correct?
That means your font is not supporting Turkish and other Turk languages.
Hi Rainer,
Yes, I know that my font isn’t supporting Turk languages. Thus, handling edge-cases for the “Idotaccent” isn’t a concern. However, I just want to cover my bases as much as I can and ask if there are any other edge-cases for the “I” that I need to consider for a Western and Central European character set (it seems like the “I” only needs one corresponding unicode value in my case. That said, it still seems a bit ambiguous based on what I’ve read online).