Hello everyone,
I'm working on my first font and whenever I try to install the OTF I get a "System Validation" error in Font Book. The TTF works fine though. I checked online and asked some people for help, but could not solve this problem. Auto hinting is deselected, so it's not that.
I asked someone else to generate the font and that person got the same problem. It seems to be a Fontlab-related thing on export of OTF.
Does anyone know what this might be and how to fix it?
0
Comments
@Erwin Denissen exported the OTF file using FontCreator and that solved the error.
Unfortunately, I can't use FontCreator, because it's Windows only.
Then, I used the free Glyphs trial to export the font. At first, I got an error - I had glyphs with the same name. This was because some lowercase letters were above the x-height.
Anyway I fixed that and exported the font using the Glyphs app trial and it works perfectly fine now.
As a newbie exploring a new program I probably messed up some settings in Fontlab. I'm not sure though.
You can use WineBottler to run FontCreator directly on OS X. Alternatively you can use VirtualBox or Parallels to run Windows on your Mac.
Just to be clear, the font passed every other validation test, just not the system validation test.
A while ago we had an old customer who wanted to restore PS Type1 fonts that she purchased a decade or more ago and who got a validation error in Font Book. We expected a permission problem with the back-up disk and when she copied the fonts to the active desktop prior to installing, everything went fine.
Opening and saving the font in another application to circumvent this problem is not the most elegant solution IMHO. I cannot imagine that whatever present-day font tool is used, too strange things happens with the fonts’ guts. If you promise me to delete the tool from your system after checking the font, I can send you a download link for OTM 6.3. You could for instance use the consistency checker for tracing the problem –if there is a problem.
If you are interested, please send an e-mail to: <ihopethatotmcansolvetheproblem[at]dtl.nl>.
F.
Additionally I also changed some of the metrics stuff and a couple of entries in the naming tables that were inconsistent. However, the original entries did not negatively influence the validation in Font Book.
If the revised font that I sent you on the 10th of April validates well (as it did here), then the error in the font’s table directory definitely caused the problem.
F.