I was testing a font in Windows 10 and realized that in the menu the name shows .notdef.
I checked the name table and everything seems fine. Does someone had this happening before or know how to address this?
This is a representation of the currently selected word in Word.
It doesnât happen with other installed fonts, though.
I have a solution for this! Nobody seem to know why this happens, but I did som trial and error and for me it was the fact that we normally add 2â4 Greek glyphs to our fonts.
For some reason, Office seem to think that the font now support Greek, but decides to let me know it does not support full Greek, so therefor displays the .notdef like that in the menu. Stupid, I know. Office is.
3 Likes
YES! Thanks a lot for finding this and sharing it 
I haver cracked quite many Office-related font issues, I should be hired by Microsoft as their expert consultant for modern Type designers.
One which is really handy is how to make kerning work in Powerpoint.
- Make sure you have no glyphs without unicode value in that have kerning pairs.
- Export the TTF with the âExport Kern Tableâ custom parameter. Here you also need to limit the kerning pairs to the number it says, so expect to sit and remove all smaller kerning pairs the font have for an hour or so, if you are a fine-tune-kerning kind of guy.
- It basically should work now â but does NOT (haha) so the TTF-font has to opened up in FontLab and then exported again, this last thing is a problem with Glyphs.
And if a PC-client want to avoid people pressing the Bold-button:
Export the font and say that the very same font you are exporting is also the âBoldâ style linked to itself (it works on PC, not on Mac).
Last but not least, never try name a font with a name that has the three letters âNORâ in a row like that. Doing so will make Office think itâs the normal style, so it basically messes upp the weights, and display the wrong ones. Really weird issue, it took almost a week to figure this one out. Have tried to report this to Microsoft, but ignore me everytime I try to get some kind of support or have questions, I guess they just want everybody to use Calibri.
5 Likes
But what exactly is the solution?
I already tried adding the âcodePageRangesâ parameter, but that didnât help.
Looking at the list of fonts, that space in the font menu is either blank or filled with samples for fonts actually supporting non-western codepages. This includes fonts which definitely have the pi and Omega characters, but still the menu keeps that space blank. So, there must be solution to let these Windows apps know that Greek is not actually supported.
I only see this âNo glyphâ issue with my own fonts exported from Glyphs. All of them.
Can you please send me the .glyphs file to support (at) (this website without âwwwâ or âforumâ). I will have a look.
To answer my own question: Adding the âunicodeRangesâ field with Latin-only values fixes the issue.
1 Like
Oh, great â have to try this!
Hey @opentype â where do you add this? A custom parameter? Can not seem to find it, and bumped in to the problem just recently. Thanks!
@mekkablue Do you have any solution for this? More and more clients complain. 
Can you send me the .glyphs files again? Trying to reproduce the issue.
Basically any font that has one or more greek characters (but not the full set) ends up this way, but I just emailed you a glyphs file for your reference.
Can you check the unicode ranges of the exported font?
Not sure how to do that.
Open the font in FontTableViewer or OTMaster or use ttx.
In case you havenât found it yet: Yes, itâs a custom parameter in the Font tab. Clicking to edit the value brings up a list of checkboxes to tick, so you donât have to worry about writing all the ranges in the precisely correct way.
In your case, checking all the ranges in the screenshot in your last post except Greek should do it.
1 Like
Thanks! Iâll give that a try.