FONTBOOK FROZEN ON VALIDATING FONTS UPDATE
FONTBOOK FROZEN ON VALIDATING FONTS PRO

The rest sounds a lot like a particularly painful version of the old 'make it work, then make it fast' mantra, or of the sort of lack of polish characteristic of a 1.0 release.

This strikes me as the most basic precaution, and something that the app should not have been released without (then again, the iTunes for Windows folks made the same mistake with corrupt MP3s). It could even leave repair to a third party app - the point is that given that corrupt fonts are a common problem, and given the severity of the crashes that a corrupt font causes, you'd think that Apple would have put a safeguard in. You can blame corrupt fonts for FontBook crashes, but corrupt fonts are hardly a new problem, so you'd think that FontBook would at least be able to identify fonts as corrupt rather than trusting them implicitly. Its main problem appears to be immaturity.

FONTBOOK FROZEN ON VALIDATING FONTS PRO

It surfaces repeatedly as a pro app in Apple's own literature.

I don't see any evidence that FontBook is aimed at average users.

FONTBOOK FROZEN ON VALIDATING FONTS UPDATE

Maybe I have to go through all my fonts and update the older ones but they worked fine in Suitcase X under Jaguar.Īnyone have any tips or good experiences handling a large number of fonts with FontBook? Interface is great, it just doesn't work right. Don't just spin the ing beachball when I add a folder of dozens of fonts. Activation/deactivation of fonts should be fairly quick.ģ. Font book should not activate fonts by default when you add them!Ģ. So to test things out I tried to validate a bunch of them, including the system typefaces (arial, etc). I thought at first I was finding some sketchy ones but it looks like the majority of them wouldn't be validated. I'm back to normal but now I have to wait for Suitcase X1 to work with Panther or FontBook to get smart.ġ. Hey guys, I just picked up my new MBPR and am having trouble installing new fonts. Every thing came up fine but there were 1200 fonts in my user font folder that I then deleted. Couldn't force quit, no other apps were coming up or starting and I couldn't even log out or restart. It takes about 30 seconds (on a 933MHz G4 with 1GB RAM) to deactivate a font. I'll just deactivate them as I go through them. Firstly it ground my machine to a halt, so I suspected it was activating the fonts instead of just loading them.

Fontbook frozen on validating fonts