Forums
New posts
Articles
Product Reviews
Policies
FAQ
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Menu
Log in
Register
Install the app
Install
Forums
Apple Computing Products:
macOS - Apps and Programs
Word 2004 corrupt fonts - word won't run
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="gdane" data-source="post: 477064" data-attributes="member: 37499"><p><strong>Move the FontCacheTool</strong></p><p></p><p>This font error in Word plagued me for a while before I finally moved the FontCacheTool. (Tried everything else in that article referenced above; nothing worked permanently.)</p><p></p><p>Path: Microsoft Office 2004 > Office > Support Files</p><p></p><p>Create another folder in Support Files named 'Disabled', then drag FontCacheTool into it. This will cure forever the evil font error.</p><p></p><p>Drawbacks: If you actually DO have a corrupt font, Word won't know it. But then again, FontBook will validate if you ask it to:</p><p></p><p>Open FontBook; select All Fonts in the Collection; then select all of the fonts in the Fonts pane; select Validate Fonts from the File menu.</p><p></p><p>FontBook will tell you what's broken.</p><p></p><p>BTW, hang on to that FontCacheTool. If you need to update Office or Word, move it back into the Support Files folder loose.</p><p></p><p>For what it's worth -- and this is ONLY the opinion of an OS X Support Specialist (supporting a network in Arizona of roughly 170 Macs) -- FontBook is better than Suitcase. I've used them both -- Suitcase for 7 years; FontBook for 5. Both have advantages and disadvantages (seems like everything does, eh?), but FontBook, over the long haul, gives me less trouble.</p><p></p><p>And neither FontBook nor Suitcase would have any bearing on this Word 2004 font error. This is a bug that neither Microsoft nor Apple can explain, mainly because it doesn't happen on every install, or on specific platforms.</p><p></p><p>Then again, it's stuff like this that keeps IT types employed. (Maybe that's why it happens<img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /></p><p></p><p>Anyway, if you want Word to quit bugging you about fonts, moving the FontCacheTool is the only sure cure, albeit with a caveat or two.</p><p></p><p>gDane</p></blockquote><p></p>
[QUOTE="gdane, post: 477064, member: 37499"] [b]Move the FontCacheTool[/b] This font error in Word plagued me for a while before I finally moved the FontCacheTool. (Tried everything else in that article referenced above; nothing worked permanently.) Path: Microsoft Office 2004 > Office > Support Files Create another folder in Support Files named 'Disabled', then drag FontCacheTool into it. This will cure forever the evil font error. Drawbacks: If you actually DO have a corrupt font, Word won't know it. But then again, FontBook will validate if you ask it to: Open FontBook; select All Fonts in the Collection; then select all of the fonts in the Fonts pane; select Validate Fonts from the File menu. FontBook will tell you what's broken. BTW, hang on to that FontCacheTool. If you need to update Office or Word, move it back into the Support Files folder loose. For what it's worth -- and this is ONLY the opinion of an OS X Support Specialist (supporting a network in Arizona of roughly 170 Macs) -- FontBook is better than Suitcase. I've used them both -- Suitcase for 7 years; FontBook for 5. Both have advantages and disadvantages (seems like everything does, eh?), but FontBook, over the long haul, gives me less trouble. And neither FontBook nor Suitcase would have any bearing on this Word 2004 font error. This is a bug that neither Microsoft nor Apple can explain, mainly because it doesn't happen on every install, or on specific platforms. Then again, it's stuff like this that keeps IT types employed. (Maybe that's why it happens:) Anyway, if you want Word to quit bugging you about fonts, moving the FontCacheTool is the only sure cure, albeit with a caveat or two. gDane [/QUOTE]
Verification
Post reply
Forums
Apple Computing Products:
macOS - Apps and Programs
Word 2004 corrupt fonts - word won't run
Top