OSX 10.7 Safari 5.1 font rendering problem

I still haven't heard from Apple Engineers regarding this problem... I have all of my fonts stored in a remote folder and access them with Suitcase Fusion.

I have removed all of the fonts in my Lib/Fonts folder, turned off "auto-activation", quit Suitcase Fusion and restarted. The problem still exists.

I don't believe it is a conflict since I had no issues prior to the Lion upgrade and my other browsers are working fine.... It is a Safari bug and I will be happy when Apple figures this out and issues a patch.

Until then, I am using FireFox (v5.0.1).

Hi - Had the same problem - I have Suitcase Fusion 2 on the computer and it's "font vault" was messing the browser up. To turn it off I went to System Prefs > Suitcase Fusion Core - unchecked "start Suitcase Fusion 2 Core at Log-in" and turned off the Suitcase Fusion 2 Core - Then restarted. All seems fine now (now just waiting for Suitcase to update their program...)

New Web Open Fonts standard has been adopted by Apple for Safari 5.1 running under Lion.

Garbage (Last Resort Font) is displayed in Safari 5.1 in place of improper fonts.

Problem may be caused by Duplicate Fonts or bad kind of Fonts.

Type 1 Postscript Fonts are no longer accepted by Safari.

Use only Open Type or TrueType Fonts.

Duplicate Fonts must be eliminated with FontBook.

NB:

Results are not guaranteed!

Restart of the System doesn't solve the problem permanently.

I don't know what did it, but the problem for me is gone. Either of these could be it...

- I reinstalled Lion

- I wiped my FontAgentPro library and started it from scratch

So, it looks like tobystokes was right, it is a sandboxing issue. See here for a description of the problem:

https://discussions.apple.com/thread/3191320?start=30&tstart=0#15718224

and the solution:

https://discussions.apple.com/thread/3191320?start=30&tstart=0#15718511

The solution presented by robert_tx in the discussion I linked to solved the whole problem immediately.

That may have solved it for you, but my local fonts are fine. I only have the problem with text replacement, nAmely fontface. So I think there are bigger issues here than a font path in a sandbox file. More accurately I'd dummies that safari would rather websites didn't have any text.

*summise, Apple, not dummies.

Nope. You have the same problem with Suitcase Fusion

Well i dont use it, so it cant be that :p

I do use font explorer, but ive wiped it along with the library and reinstalled from scratch, didnt make any difference. Also how would font explorers font path effect a fontface font being called via js and css, it shouldnt be touching font explorer.

Also system fonts are fine, the only fonts affected for me are webfonts.

I've noticed before that sometimes with webfonts, Safari will try to use a local copy of the font if you have it. I don't know why it does this, but I've had it try to load fonts which I've downloaded but aren't even loaded into a Font Manager, sometimes triggering the Potentially Unsafe Download message that you get when opening a downloaded file for the first time. It was really annoying when it happened.

Because of this, I think it's still possible that it could be a sandboxing issue. Have you checked your logs for any messages like the ones mentioned in the other topic? They would look something like this:

7/23/11 11:21:13.385 PM sandboxd: ([5248]) WebProcess(5248) deny file-read-data /Users/robert/Documents/Fonts/FontExplorer X/Font Library/C/Calibri 3/Calibri.ttf

Just open up Console (you can find it using spotlight) and search for "sandboxd" in your logs.

Jeremy Bohn wrote:

I don't know what did it, but the problem for me is gone. Either of these could be it...

- I reinstalled Lion

- I wiped my FontAgentPro library and started it from scratch

I forgot to also add that FontAgentPro had been updated for Lion compatibility so that could have fixed the issue too.

Ah that sounds interesting.

Although I have a feeling I've experienced the problem with any instance of fontface (so in some cases I don;t have the font locally) I think it's worth me investigating; admitedly I haven't checked the logs which I should.

It would be very odd behaviour for Safari to check the system for a web font, but I'm assuming it's an attempt to reduce load and to speed up the rendering and download times - if that is the problem of course.

Nice effort I suppose, but it really doesn't work. I've had similar issues with Chrome in the past though, struggling with web fonts; could even have been the same issue.

What is worth noting though, is the fact that Safari doesn't simply fall-back through the font-family; it forces in the 'A' character glyphs; so no matter how you look at it it's behaving very oddly.

Nothing a half-baked beta test wouldn't have flagged, mind :/

@font-face WILL try to access a local file if one pf the same name exists.

And it's also possible that FontAgent (or similar) will try and auto-activate it.

but note that this is a pre-Lion issue:

http://paulirish.com/2009/bulletproof-font-face-implementation-syntax/#fontexplo rerfail

I upgraded to Lion and had the same garbeled font issue in Safari.

I use Fontexplorer Pro. I went in an removed Arial TTF and enabled Arial OTF and it fixed it all for me.