Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'An informative Apple guide to font management' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
An informative Apple guide to font management
Authored by: DavidRavenMoon on Jan 30, '04 02:07:10PM
The problem I have found in replacing the system versions of some fonts, such as Helvetica, is that some of the PostScript versions display incorrectly. I have been able to fix this by opening the printer font file in Fontographer, and saving a new font suitcase.

It seems to be an issue with unicode support, and it effects such applications as Safari, iChat, Mail, etc. Using Suitcase X1 to turn on a PostScript version of Helvetica has crashed iChat on several occasions, and QuarkXPress 6 both displays and prints the fonts incorrectly.

Here is a screen shot of the malformed fonts in Suitcase. In this case it's AGaramond.

And here is Helvetica rendering wrong in the address line in Mail.

Anyone have any ideas?



[ Reply to This | # ]

An informative Apple guide to font management
Authored by: Darukaru on Jan 31, '04 12:52:41AM

I've seen the same thing happen in Safari v100.1 with only the standard OS X .dfont fonts enabled.



[ Reply to This | # ]
An informative Apple guide to font management
Authored by: ajabu on Feb 04, '04 02:07:29PM

I had the same problem, and removed helvetica fractions from my user/lib/fonts folder.

At the same time, I checked that Times 13 and Andale Mono 11 as standard fonts in Safari (as I believe the two programs use the same font settings?). I'm guessing that some web pages look quite unreadable too (only in Safari)?

This solved my problem with mail. I furthermore disabled another font, Times Phonetic (in Font Book, running Panther).

I have decided not to use Suitcase for some time, trying to use Font Book. Don't think the problems are related to Suitcase specifically.

Seems that font IDs and names get mixed up. Happy to see that I wasn't alone re. this font / display problem, it was very anoying!



[ Reply to This | # ]