G
Guest
Greetings!
At the suggestion of Beth Rosengard, I am reposting my personal solution
to the following problem in Word 2004 with an easily searchable subject
header.
When I first installed Tiger via Erase and Install (Quicksilver G4/867,
1.5 MB of RAM, large number of volumes mounting regularly), with a
fresh, updated installation of Word 2004 over the top of it, Word
started misbehaving badly. Upon launch it would go into the "optimizing
font menu" operation, then about 2/3 of the way through my font
inventory (around 200 fonts), it would start throwing off font
corruption errors, starting with Romic (an Adobe PS Type 1 font freshly
reinstalled from the original CD). Theses messages would continue, each
requiring that it be dismissed by hand. And the fonts were *not*
corrupt; each was either newly installed by a new program installed
after Tiger (Word 2004, Acrobat, etc.), or was freshly installed from a
verified archive CD. I didn't try other Office 2004 apps.
This was so frustrating that I returned to my cloned backup of Panther,
but for irrelevant reasons, I didn't want to stay thee, so I went back
to Tiger, went to work, and resolved the problem.
In my case, it turned out that I had erroneously installed some Windows
TTF fonts in both Library/Fonts and in ~/Library/Fonts, Upon removing
the duplicate fonts and cleaning out the system and Office font caches
(I used Font Finagler, but there are other options), the problem went
away completely. I did not have to reinstall Tiger, Office, or other
fonts, nor did I have to set up a test user account.
This solution worked for me, and I didn't have to try anything else.
However, Matt Neuberg's advice, offered in this group and elsewhere on
multiple occasions (set up a fresh user account and try Word there, and
if the problem does not occur, simply migrate all your files to that
account), would presumably have solved the problem, because the second
set of duplicate fonts in my original user's font folder would not have
loaded. Additionally, I have read here that Font Book can manage
duplicate fonts, and it would presumably be another way to resolve this
situation. I don't personally use it.
George
P.S. 200 fonts is too many, but I haven't gotten around to weeding them
out yet. In Word I generally set up a custom toolbar which my own font
menu which includes only my everyday fonts, so this expedites things
considerably, even though the regular font menus are way too long.
At the suggestion of Beth Rosengard, I am reposting my personal solution
to the following problem in Word 2004 with an easily searchable subject
header.
When I first installed Tiger via Erase and Install (Quicksilver G4/867,
1.5 MB of RAM, large number of volumes mounting regularly), with a
fresh, updated installation of Word 2004 over the top of it, Word
started misbehaving badly. Upon launch it would go into the "optimizing
font menu" operation, then about 2/3 of the way through my font
inventory (around 200 fonts), it would start throwing off font
corruption errors, starting with Romic (an Adobe PS Type 1 font freshly
reinstalled from the original CD). Theses messages would continue, each
requiring that it be dismissed by hand. And the fonts were *not*
corrupt; each was either newly installed by a new program installed
after Tiger (Word 2004, Acrobat, etc.), or was freshly installed from a
verified archive CD. I didn't try other Office 2004 apps.
This was so frustrating that I returned to my cloned backup of Panther,
but for irrelevant reasons, I didn't want to stay thee, so I went back
to Tiger, went to work, and resolved the problem.
In my case, it turned out that I had erroneously installed some Windows
TTF fonts in both Library/Fonts and in ~/Library/Fonts, Upon removing
the duplicate fonts and cleaning out the system and Office font caches
(I used Font Finagler, but there are other options), the problem went
away completely. I did not have to reinstall Tiger, Office, or other
fonts, nor did I have to set up a test user account.
This solution worked for me, and I didn't have to try anything else.
However, Matt Neuberg's advice, offered in this group and elsewhere on
multiple occasions (set up a fresh user account and try Word there, and
if the problem does not occur, simply migrate all your files to that
account), would presumably have solved the problem, because the second
set of duplicate fonts in my original user's font folder would not have
loaded. Additionally, I have read here that Font Book can manage
duplicate fonts, and it would presumably be another way to resolve this
situation. I don't personally use it.
George
P.S. 200 fonts is too many, but I haven't gotten around to weeding them
out yet. In Word I generally set up a custom toolbar which my own font
menu which includes only my everyday fonts, so this expedites things
considerably, even though the regular font menus are way too long.