Dosen't Leopard accept FFIL??

tomomai
12.Mar.2008 3.40am

Hello everyone.
Please give me an advice if you know anything about Leopard and FFIL!

I just got new iMac at my office and installed OS 10.5.1.
Till yesterday, I was using FFIL formatted font suitcase on my lovely old PPC iMac, with OS 10.4.11.
But it seems that my new Leopard OS dosen’t recognize FFIL file as a font but a “Unix execute file”. Even Font Book and Linotype FontExplorer can’t open the ex-FFIL files, which are about 50% of the fonts I have!

I think this might be an problem of my computer, but since I’m the only one who works on Leopard in my office, so I decide to ask people here for an advice.
Does anyone know what’s going on with my new working equipment?
Please please help me!

Eluard
12.Mar.2008 4.04am

You should upgrade to 10.5.2 first. That fixed many problems in 10.5 and not all of them were documented. My fonts work (mostly!) in 10.5.2.

Ralf Herrmann
12.Mar.2008 4.08am

Works for me (in 10.5.2).
Is it connected to Font Book when you do Command + I?

tomomai
12.Mar.2008 4.42am

>Eluard

Thanks for an advice!
I updated my OS to 10.5.2, but it didn’t work.

>Ralf
Thanks for a comment!
No, even when I link the file with Font Book and open it, it doen’t open.

I start to think this can be a problem of font file itself,
so I’ll try to copy my fonts from old computers again.

Thank you again to kind people!

Mark Simonson
12.Mar.2008 7.03am

How did you get the font file from the old iMac to your newer Mac? Over the network? Using a flash drive? A floppy disk ( ;-)?

canderson
12.Mar.2008 10.58am

What Mark is alluding to, is a situation where the old hidden “resource fork” data has been stripped away from your font file by storing the file on a file system that doesn’t support it. On your old system, make a .zip or .sit archive of the fonts and then move them over. At this point in history, font suitcases are just about the only type of file in common use that keeps critical data in the resource fork. In the old days most common document formats used resource fork data to identify the filetype, but you could still often get it to work by adding a file extension. Not so with font suitcases.

Note: You can verify this by getting info on the file. If it’s 0K in size, this is what is happening.

This can be very confusing for people who recently switched to Mac because no analogous situation exists with other operating systems. Basically, Apple is providing backward compatibility with a 20yr old file format.

tomomai
12.Mar.2008 7.51pm

>Mark

Thanks for a comment!
I copied fonts form my old iMac to a file server, and then downloaded them to new iMac.

and...

>canderson

Thank you soooo much!
I zipped up fonts in old computer and it worked!

Same things happend on AI files which I transfered in a same process, and also a .zip method worked.
In my case, adding a file extension didn’t help.

Big simle to 4 kind people!!!
I appreciate your helpful advice! xx

Eluard
13.Mar.2008 4.17am

Same thing happened to me with a Quark file when I tried to move it across to another computer — it ended up as one of those Unix Executable files. The message really misleads as to what has happened.

danielle.w
17.Jul.2008 2.45pm