OTF font doesn’t work on Windows

Hi,
I edited a font with Glyphs and exported it as OTF (it has alternate characters).
However, my colleague it working with Windows and can’t use the font. It says „file is not a valid font file“.

I already googled and found out it might have something to do with the Adobe Post Script (CFF) being blocked by Windows.
microsoft.com: Datei ist keine gültige Schriftartendatei

If I try to export the font as TTF it says it contains multiple glyphs with identical names (sure, as it contains alternative glyphs).
Is there any way to export the font with Glyphs as OTF compatible for Windows?

Thanks!

Ok, just heard about Font Validator, I’ll try this!

(Most threads about this topic are up to 10 years old so I thought there might be a quick solution by now :grimacing: )

How do you name an alternate glyphs? They should have a suffix like .alt1 or .ss01 or .loclLANGCODE.

I don’t think the alternate glyphs have any effect on this.

Maybe the font names are very (too) long?

Do you send the font to your colleague in a zip file? You can’t install a font from a zip file, you have to extract it first.

Do users in your organisation generally have permission to install fonts on their machines? Maybe that is blocked by the system administrators.


The “solution” in the thread you linked is complete bullshit. I guess the “Security-IT Unternehmen” went bankrupt in the meantime if that’s their level of expertise:

“A security IT company has looked at the file and identified the problem.
Adobe Post Script (CFF) is a popular carrier for malware and has been generally excluded from the latest updates by Microsoft. Since the OTF format can contain an Adobe Post Script, Windows (older versions get the problem with the latest updates, Windows 10 in general) will block the font (reinstallation is prevented, use is no longer possible if the font was already installed before an update).”

1 Like

For Windows, only export TrueType flavor and keep your (family and style) names short.