Old Font Files in Leopard showing up as Unix Executable File

Sorry, I don't have the answer here. But I am dealing with the same issue and want to make sure this stays in front of the eyes of the powers that be at Apple. I too, have older fonts that are part of various customers marketing, etc.
NEED HELP HERE!!

Sol

The Execute permissions seem to have been set for the files. You can use the chmod command via the terminal, or install FileUtilsCm (free) from http://www.abracode.com/free/cmworkshop/file_utils.html

See also thread http://discussions.apple.com/thread.jspa?messageID=6125826&#6125826

DN

I'm having the same problem. Installed FileUtilsCM, made sure plug-in is in correct folder, and restarted system... no luck. The older font still reads as an executable file. I'm running 10.5.2.

Any ideas? Did this work for anyone else??

If they're older fonts, can I assume most of these are Type 1 PostScript fonts? These fonts still work just fine in Leopard, so something else is going on. Try this.

1) Repair permissions and restart your Mac. This likely won't really help, but can't hurt anything to try.

2) Reset the LaunchServices Database. You can use OnyX to do that. After resetting the database, a bunch of programs you have installed will act as if you've never run them before, causing the standard dialogue box to pop up saying that "You are running x app for the first time." Just click OK to continue.

Get info on them and make sure they have the correct extension. Try [these.|http://www.fileinfo.net/filetypes/font]

Thanks soo much everyone for all the help.

I've installed reset permissions, reset LaunchServices using OnyX, rebooted, and files are still "unix executable" to start with. I then used FileUtils app to "Clear Executible Status," which makes them open in txt editor, and say they are 0kb in size. I then renamed the extentions, playing around with a bunch of different types, and no luck at all with any of them.

Here is a screen shot ( http://180bydesign.com/uploads/Picture5.png) of my folder (at top) with a list of fonts, and fontbook.app (at bottom) when I try to add a font from that location. No luck.

PS - here's something weird... I had a friend w/ Tiger send me a font suitcase which he zipped, and it did same thing, but then he zipped it twice (wierd, I know) and it worked! I unzipped the first one, then unzipped the second file within that first one, and WALLA, the suitcase actually looked and acted like a font. This doesn't help at all with all the other saved files, but it certainly helps. I might open a pc & try to double zip all the old ones & see if that does the trick.

OK, I've had an idea:

Your fonts are "Minion", and I think they should have the extension .otf, so change the extension to that (also try .ttf and other common types). Next, force Font Book to open the files (hold down ⌘ and ⌥ and drag the files to the dock icon).

Crap... didn't work. You had me going! Actually, I saw that minion was already installed, so starting with "Sassoon" I tried a bunch of file-types. The oft & ttf made it open in fontbook w/out holding down ⌘ and ⌥, but once it opened, it didn't do anything.

Try this in Terminal:

chmod -x (hit spacebar, drag font file to Terminal window press return)

Then relaunch Finder and see if the problem persists.

Thanks, Király, that works. I also figured out that to use FileUtils, you rightclick on file, then go to more options.... then by clicking "clear executable attributes" it will do this same thing. It doesn't, however, fix the font prob and make the font read correctly.
- Thank You though.

they are 0kb in size

And there's the problem. They'll never work since something has happened to the fonts themselves. 0 kb means just what it says. There's no information there at all. Just a name with no content.

You'll have to get the original fonts and copy them to your Mac again.

{quote:title=Kurt Lang wrote:}There's no information there at all.{quote}

Dude, I'm telling you... when my friend w/ tiger send them, it is the exact same problem... here is a screen shot of the exact same folder with a load of fonts that are 'plaintext 0kb', and w/in it there is another zipped folder where the fonts work. I've seen them at the source and both folders are real fonts. This, actually, is how we learned that if we zip them twice, it will start working again:

http://www.180bydesign.com/uploads/Picture7.png

Maybe it's a problem with Archive Utility.

But that makes no sense. Zero kb means just that. There's no data related to the file name you see listed.

From what I can make out in the upper folder window you link to, the first set of fonts in the center are empty items that don't work. You then unpacked the .zip file in that folder to the listing at the right, which do work. Those all must have a size (not 0 kb). Without seeing what exactly you're doing, I couldn't tell you why your initial zipping of the fonts is producing 0 kb copies.

Hi,
I don't have the answer, I just wanted to raise my hand and say "me too!"
So far, this has only happened on a couple of fonts among the many I have. These fonts are Type 1, worked perfectly in Tiger, as well as OS9, and now don't appear in Leopard. In desperation (as it's happened to one font I really need) I re-purchased one from MyFonts: it still didn't work, appears bitmapped. After querying with MyFonts, they told me that after testing it they got the same problem in Leopard too. At least they refunded me, even though they couldn't fix the font.