{ What does this error mean? }

Rene Verkaart's picture

I'm finishing up my font Insider and a friend of mine is test-driving it. The font seems to work just fine in FontExplorer, but doesn't work well in InDesign CS3 (5.01) and Illustrator CS3 (13.02). All fonts are suitcases for Mac.

It keeps giving out this error:
"You might not be able to print with "fontname" or stroke its characters because the font outline file is missing."

That the hell does that mean? I never get that error here. I don't have InDesign CS3, so I can't reproduce the problem. Is there anyone else that get's the same errors and knows how to solve this?

Mark Simonson's picture

If you generated a Type 1 font for Mac, there will be two files: The font suitcase ("FFIL" on the icon) and an outline font file ("LWFN" on the icon). The error indicates that only the suitcase file was installed.

Rene Verkaart's picture

Normally I double click the FFIL file and the font is installed in Fontbook. I don't know how FontExplorer works, but my guess is that it works the same. How else should you install both files?
If you check the destination folder for the fonts, both files are in there.
Is there another problem that might initiate this error?

Mark Simonson's picture

The sure fire way is to go to your home folder, then go to Library > Fonts. Drag both files to the Fonts folder. This is essentially what Font Book does when you tell it to install a FFIL file you double-clicked on. I knows about the companion LWFN file automatically. FontExplorer's default behavior is to make a copy of the files in its private database, but you have to drag both files to it, not just the FFIL.

Generally, when I'm testing fonts, I don't use a font management tool. I copy files manually to either my user Fonts folder or the Adobe Fonts folder ([main hard drive]/Library/Application Support/Adobe/Fonts/).

Rene Verkaart's picture

Thnx Mark, I'll send this solution to my friend and see if it works.

Rene Verkaart's picture

Ok, quick reply. Both font files are in the right place. FontExplorer seems to have an own ordner per font, so there must be another problem at work.
Can the LWFN file be corrupt? Can it be that, when generating the font, the outlines are not put out?

Strange...

Mark Simonson's picture

I've never heard of an LWFN file being corrupt, but I suppose it's possible. In the pre-OS X days it was common for FFIL (suitcase) files to become corrupt because they were always open for read/write access when they were active.

Syndicate content Syndicate content