Hi,
I've been hearing about this for more than a year now. Some of the users have been telling me that they had received this error before. But I personally never had a problem, until I did search for it and found a lot of users complaining about this. It is a valid font, you install it, no problem, another user with the same OS like Windows 10 tries to install the font and get this error. It never goes away and also doesn't seem to be based on anything. Sometimes it's ttf files, sometimes otf and sometimes totally random.
The tech guys all over the internet finally concluded that it may be related to Windows Firewall! No one knows why and how! But my question is is there any font programmer here that could help me to understand why is this happening and how to fix it? I don't know what should I say to my customers sometimes, they have paid for the fonts. Fonts are working and had been tested, but somehow this happens!
Thanks!
Comments
Though, both of those possible (guessed) names, e.g., "DejaVu Sans Mono Bold Oblique", should just be within limits. The example I gave is exactly 29 characters.
Is it possible that we can find out how Windows Font Viewer actually "consider" a file a valid font? (beside the file name length)
Family Name <= 31
PS Font Name <= 29
FOND Name <= 30
From my experience you won't have this issue if you use an external font manager. Our font manager (MainType) comes with a free edition, so do give it a try.
Have You tried to delet the windows font cache?
The reason I'm saying is not font-related because it happens to very very well-known fonts which millions of people already installed them, and the reason I'm saying it's not going away because it's connected to how Windows identifies fonts, and you won't see it on other operating systems (as far as I know).
What I - was - am looking for is to find out how Windows Font Viewer does this "recognition" which ends to this error. I hope I was clear
You can try to run your font through OTS first and see whether OTS throws an error. It's very helpful for validating fonts.
My point from the beginning was to find out what's the issue with Windows Font Viewer. Obviously I couldn't make it clear enough.
Current GDI error handler only rejects a font but not reports the reason. For a kernel component like GDI, it is not a bad idea.
As I mentioned before you got different results from people with the same Windows version.
On top of the frustration that users have to feel, I think this is a very bad publicity for freelance type designers, because the font actually is not corrupt, yet the user can't install it and obviously you can't explain to them that it's a Windows GDI thing, because they paid for a font and they want to use it anyhow.