Word 2004 checking even inactive fonts + finding integer onescorrupt

N

Nikolai Franke

Hello.

All of the sudden, Word 2004 (Version 11.2) running on Mac OS X 10.4.10
(PPC) has started to apparently check all the fonts on my machine during
application startup, including those inactive, and it claims of many fonts
that they are damaged and need to be removed. It presents me with a dialog
popup for each one of these allegedly damaged fonts and requires an ok click
for each of them, which makes starting the app take several minutes.
I have Mac's Font Book running, plus FontAgent Pro. The fonts determined to
be corrupt by Word 2004 are found to be just fine by FontAgent Pro; it
activates them with no problem, and all applications, including Word itself,
use them with no problem, which leads me to suspect that they aren't
actually damaged.
Nothing has been changed other than a system update (from 10.4.9 to
10.4.10).

Any idea (other than actually removing these fonts) ?

Thanks a lot
 
N

Nikolai Franke

Nikolai Franke said:
Hello.

All of the sudden, Word 2004 (Version 11.2) running on Mac OS X 10.4.10
(PPC) has started to apparently check all the fonts on my machine during
application startup, including those inactive, and it claims of many fonts
that they are damaged and need to be removed. It presents me with a dialog
popup for each one of these allegedly damaged fonts and requires an ok click
for each of them, which makes starting the app take several minutes.
I have Mac's Font Book running, plus FontAgent Pro. The fonts determined to
be corrupt by Word 2004 are found to be just fine by FontAgent Pro; it
activates them with no problem, and all applications, including Word itself,
use them with no problem, which leads me to suspect that they aren't
actually damaged.
Nothing has been changed other than a system update (from 10.4.9 to
10.4.10).

Any idea (other than actually removing these fonts) ?

Have you tried trashing all the font caches as described in
http://word.mvps.org/Mac/CorruptFontErrors.html
? Given that everything else is working fine, try flinging Word's cache
first.

Word's font skills are a bit special[1] aren't they?

1. Local 'yoof' usage. special as in 'special needs' which is nanny
state usage for thick as a double ditch.

Hello Elliott,

thankyou very much indeed. Doing as described in the html you linked solved
it (even though the file 'com.apple.ATS.plist' doesn't exist on my machine;
maybe this has changed in 10.4.10?).

thanks again, best wishes

N.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top