Font problems...

[MikeTheVike]

I'm going to try and explain this and hope it makes sense...I'm updating an ad for a client. They use a font that I don't have installed. I found the font on another computer here, but I can't seem to get it installed. I burned the font to a disk, and tried to install it from there, also tried installing it from the desktop. It doesn't give me and error, but it doesn't appear in Fontbook.

The font is called OPTICarmella-HandScript...I found two files, one named that and the other named OPTICarHanScr...The OPTICarmella-HandScript has the letters "FFIL" in the icon, and the OPTICarHanScr has "LWFN" Am I missing something here? These are the only 2 files that were found in a folder that Quark created during a Collect for output of the ad previously...Thanks for any help

[PrintDriver]

Sometimes a restart is in order...

If that doesn't work,
Those are the two icons for the two parts of a postscript font. I haven't had this problem with Q6 so I haven't looked (and I'm not at work) but does Quark have a folder in the main hard drive library>Application Support folder that has a font folder in it? Adobe does. There are some Postscript fonts that do not load properly into font management and stashing them manually into the particular program font folder (if there is one) sometimes works. The other place to try stashing the font parts manually is in your Home Directory>Library>fonts folder. This is the first place OSX looks for fonts and if there is a conflict for some reason putting them here may solve it.

[panzer]

i have had loads of problems with older fonts ie from older versions of mac

have you double clicked on em ? 9SILY QUESTION PROB0

[panzer]

i know i am ages away with this

"FFIL" = for OS X and "LWFN = for classic

[PrintDriver]

FFIL and LWFN are two parts of a postscript font. You have to have both for the font to print in either OS.

LWFN is the outline portion, FFIL is the display portion.
Please send both when sending files for print.

[jimking]

Stinking FontBook. As PrintDriver stated, restart. When I was using FontBook, I'd always had to close FontBook and the application down after loading the font and restart funkyBook and the app for it to see the darn font.

[PrintDriver]

This is an old thread Jim. Panzer posted somewhat inaccurate info this morning.