Specialized Type1 fonts not printing on 10.1.1

houchin

houchin

Registered
I'm having some problems getting some of my Postscript fonts to work on
Mac OS X (10.1.1). The problem fonts are the specialized fonts from
one of Adobe's expert sets (small caps fonts, special symbols, ...)

In all of the apps that I've tried, the fonts display fine on the screen.
However, problems occur when I try and print the document.

In Freehand 10, the document prints, but those fonts are replaced with
Courier. In Word X, Word crashes when it tries to print the document.

Any suggestions?
 
Check the actual font file folder. In the folder you should have a font suitcase and the corresponding font files for each weight (regular, bold, italic etc. -- in your case, expert italic, expert bold etc.)

I suspect one of the parts are missing. Postscript Type 1 come in the two aformetioned.;)

Check my image of Adobe Garamond Expert font and how it should look like as a font set.

(I hope this helpful (you may know all this anyway:eek: ))
 

Attachments

  • fontfolder.jpg
    fontfolder.jpg
    82.1 KB · Views: 15
I had all of that installed. The roman parts of AGaramond work fine, so
I'm really not sure what's going on. Actually, I don't have the AFM files installed, as they didn't do anything in OS 9 (or at least for the Apps I was
using). Maybe I'll try reinstalling from scratch as opposed to copying from
an older System.

Do you have the fonts installed in /Library/Fonts or in ~/Library/Fonts

I like the idea of putting each font in separate folders, though.
 
The reason for having my fonts in seperate folders is because I have them on a seperate partition, being used by Extensis Suitcase 10.1 (because Suitcase doesn't mind where you put them).

If you do not have this, then you'll need to put the fonts in the pathname you mentioned AND without being in folders (basically all font files in the system library font folder or the user library font folder need to be without folders (messy I know!))

You don't need the AFM files, these are the fonts' information for apps like Fontographer etc.

Does your Garamond Expert set match mine?
 
The only difference is that my postscript files have the old Mac OS 9 red A
icon, rather than a Mac OS X specific one.
 
it sounds like OSX hasn't recognised the font as a font file.

The ones in my image had nothing special done to them, they are simple Postscript Type 1 fonts originally used in OS7.6 through to OS9.:confused:
 
Ok, the problem is now solved. It appears that at least one of the files was
corrupt. Reinstalling them did the trick.

XFont Info also helped out, as it was able to confirm that something was
wrong because it couldn't show the corrupt fonts.
 
Yep, you really do need those font apps rather than relying on just the system's font use.;)
 
Ok. Correct that. Problem not fixed, at least not totally.

I reinstalled the fonts, and made a test document that used some of the fonts from that font set, and that worked. However, it appears that only some of the fonts were not working, and the one that I tested was one of the working fonts.

I checked out the fonts in Font Doctor, and it said that everything was fine.
I also got the demo of Suitcase and installed the fonts with that.

I'm not sure what changed things, but all of the fonts (I made a special document that used them all) work in some applications, such as Word X.
However, in Freehand, some of them still don't work when printing to postscript printers.

If you watch the "processing job" messages in Print Center, I get the message "AGaramond-RegularSC not found, substituting Courier." The thing that bugs me about this is that the font that originally started this was the Semibold Small Caps version, not the Regular small caps (and in fact Regular Small Caps isn't even in the document.

At this point, I'm going to guess that it's a Freehand problem and submit a bug report to them. I guess I'm going to have to install Freehand 9 on the system and run it from Classic :(
 
You must log in or register to reply here.
Back
Top