Fontlab 7 vs Monotype's Font Validator

Dusan Jelesijevic
Dusan Jelesijevic Posts: 71
edited January 10 in Type Design Software
Hello,

Monotype's font validator reports me 2 red errors each time I want to upload new file versions of font files (older families previously done in FL5).

PostScript names are unique in the family
It looks like your two or more font files have same PostScript Name. Please delete and re-upload the font files with unique PostScript Names.

Version names are unique
It looks like your two or more font files have same Version Name (NID 3). Please delete and re-upload the font files with unique Version Names.

As I don't know if it's bug (with their website) or if it's related to font files, I have checked, checked and checked many times all my names and versions and everything seems alright (I compared with font files that hadn't those issues, how I did it with them), I'd like to know if there's maybe some other place in FL7 beside Font Info where I should check for these issues?

Thanks,
Dusan
Tagged:

Comments

  • Thomas Phinney
    Thomas Phinney Posts: 3,104
    Nobody would be able to tell for sure if it was something wrong with the new font files in this regard, without you sharing the “version name”* and PostScript name entries for the new fonts. (Name IDs 3 and 6.)

    * Note that the name ID 3 Monotype is calling “version name” is what the spec calls the “unique font identifier” — NOT the same as the name ID 5 version string.

    That said… I wonder if maybe the problem is the reverse of the obvious one. Maybe Monotype’s system is not recognizing that the new versions are supposed to be the same family members as the existing files? Because of course, they are supposed to duplicate existing files. Have you done updates (replacing old version with newer) before?
  • Dusan Jelesijevic
    Dusan Jelesijevic Posts: 71
    edited 9:08AM
    Yes, I did updates previously and everything went well.

    What's strange here is that I get same red warnings even when I try to update font family containing single weight only  :)   

    I'm making massive update – all families we did in FL5. I have made some minor changes in FL7 and generated all font files. All the information in Font Info are filled out correctly, as I'm doing with every newly done family made in FL7.

    All worked fine for a couple of days – I updated 1/3 of our catalogue without any red warnings, but one day they just started appearing no matter what font family I wanted to update.

    Logically, I assumed it's something at my side at first, that's why I reached here for help. But, I emailed them also to tell me specifically how to correct these warnings and why are they keep appearing all of sudden.

  • John Hudson
    John Hudson Posts: 3,578
    It sounds like it might be an issue on their side. Possibly their website back end is not replacing the old files, but trying to add the new ones as duplicates, triggering these kind of warnings. I have seen this kind of problem with file management systems, sometimes even linked to using specific browsers (e.g. works when using Safari, but not when using Chrome). Have you tried doing the uploads using a different browser?

Categories