From Apple and Extensis: Font management under Mac OS X

If you're going to use any of the .dfonts, I'd recommend converting them to a regular Mac TrueType font form using my dfontifier application. That way, OS 9 will actually be able to make use of them when you place them in the Classic /System Folder/Fonts/ folder, or you can provide them in a form that's usable to service bureaus like the one you were using.

Hope this helps....

You can replace the .dfonts by booting into OS 9. but, I think you should not remove them without adding a replacement. Since your Garamonds are all Postscript, I am not sure what to recommend. The problem occurs in Quark?

thanks Bob. This may account for the fact that I get "font may be corrupted" errors for my Zapf Dings and Helvetica when going to print. The system is going to the dfont first. I don't have admin access to remove them.

But my Garamonds are both PostScript type 1 fonts. So at least you can say that they are mapping differently? Not sure what that means or what I can do about it, any ideas?

I experienced a similar problem once. I used Zapf Dingbats in a job...I think I used one of Apple's .dfonts. I took the job to a service bureau which was running OS 9. They eitehr could not use or did not have teh .dfonts. The characters mapped differently. Or rather, did not show up...choosing a TrueType font of Type 1 maped different characters...

I don't think there are .dfonts of teh ones you are having the trouble with, but...

After reading the above document from Apple, I have reorganized my fonts, putting all of my fonts in the System 9 fonts folder, as I run both OS9 and OSX.

I am having an issue now with both my ITC Garamond and my Adobe Garamond fonts. Both have a few family members that are showing incorrectly on screen with odd symbols and ligatures, as if a different keyboard configuration were applied to them. And each font shows slightly different wrong characters for the same sentence. I did some sorting out of the fonts, removing them from the fonts folder, eliminating some duplications and generally making sure the pairs of screen and printer fonts were intact, then reinstalled them in the OSX fonts folder so I could deal with them separately from my other fonts. This time the same thing happened but with different family members. Two that were wrong before were right now, and two others were now wrong on the screen. All of these fonts have printed correctly by the way.
Any clue what is going on here?

Very few licenses I've seen had different terms for educational use, so it's possible, but rare.

A few foundries, including Adobe, offer either special packages available only to the education market, or discounts for educational purchases. Adobe's answer is "Type Classics for Learning."

Regards,

T

Are there different licensing allowances when fonts are shared for educational use?

Thanks Bob, for taking the time to answer my questions. You've been very helpful.

BTW, Apple's Font Books checks for duplicate fonts, too, just as Suitcase does...

That said, as this topic is open for comments specific to Apple's PDF Font Management document (not to how fonts are used by QuarkXPress or Suitcase), please create a new topic. It would make your concerns a lot easier to find and follow up. Thanks.

Neil