Currently Being ModeratedMay 2, 2012 12:26 PM (in response to scimicon)
Should I reinstall Font Book?
That won't help in the least. Your problem is here:
So I have two files, one with the 0K unix files and one with the resource forks content. Both show up as Unix files.
0K means just what it says. The file is nothing more than a file name. Any data that was supposed to be there is gone. I'm guessing you have a Type 1 PostScript font. The suitcase of screen fonts, and its matching outline font. With such fonts, all data is in the resource fork for both items. So if one got stripped, it's very likely they both did.
In Windows, if a file is an unrecognized type, its icon is show as a dog-eared piece of paper with the Windows logo in the center. That's Windows' way of saying, "I have no clue what this is." While there are actually some UNIX executables in OS X, it's usually OS X's way of saying, "What is this?".
You're going to have to retrieve the font from its original source and replace the damaged copies.
Currently Being ModeratedMay 2, 2012 12:38 PM (in response to Kurt Lang)
The resource fork file shows content.
Currently Being ModeratedMay 2, 2012 12:53 PM (in response to scimicon)
How do you know it's the resource fork? There isn't an easy way for the user to tell what's in the resource fork as opposed to the data fork. Secondly, the resource fork of what? Post a file name.
Currently Being ModeratedMay 2, 2012 1:45 PM (in response to Kurt Lang)
Basically I have a CD with one file with a list of fonts showing 0K and another file labeled RESOURCE.FRK containing the same list of fonts with various amounts of data attached to each one. I believe I've used this list to reinstall fonts in the past, but it's been so long that I can't guarantee that. They might just be data files as you say.
Here's an example copied directly from the "resource fork file" on the CD
The CD list file shows 14 KB of info.
These are old fonts mostly collected from Adobe add-ons and some that I bought on floppies !!!! (remember those?)
I might try installing these on someone's older system. I didn't keep a backup folder (dumb, dumb, dumb)
Or I might just go for a new beginning.....
Currently Being ModeratedMay 2, 2012 1:58 PM (in response to scimicon)
Ah! Excellent information.
I bought on floppies !!!! (remember those?)
The name ADOBES~1 in particular tells me that this is a DOS/Windows formatted disk, since that's what Win '95 and forward uses for the truncated 8.3 DOS name related to the file's or folder's long name. Is this correct?
If so, then RESOURCE.FRK may be a trashed Mac resource fork that couldn't be burned to the CD since DOS/Windows doesn't support two forks. You may have to go all the way back to the floppy disks (if at all possible) to retrieve the original fonts.
Currently Being ModeratedMay 2, 2012 2:32 PM (in response to Kurt Lang)
Nope, not DOS/Windows. I've been Mac-ing the whole time. That's why I think there is a glimmer of hope. But it's pretty faint. The floppies are long gone. No practical way to access them. Thanks for your input.
Currently Being ModeratedDec 6, 2012 12:58 PM (in response to jim1964)
I found a solution that may not apply to everyone.
We had fonts on a shared network drive. I could could not use the fonts (10.6) but a colleague with 10.5 had no issues at all.
I asked her to compress the font files from her machine and when I opened the zip file on my machine the fonts got their beautiful icons back and suddenly had size back. The opened in Fontbook and installed.
So it is a bug. You need to find a machine with an older OS, compress the fonts, then open them on newer OS. A bit clunky but it works without having to tinker in the Terminal.
Currently Being ModeratedDec 6, 2012 1:10 PM (in response to JBriare)
So it is a bug.
In a sense, yes. But it would be a bug in the communication between the network drive and the Macs running 10.6, not the fonts themselves. Though I think that was your intent.