A family of Microsoft word processing software products for creating web, email, and print documents.
I solved this problem by saving the troublesome file in what 2010 calls "compatability mode>"
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I upgraded from Office 2007 to 2010 two weeks ago. Whenever I open up documents in Print Layout View that were created under earlier versions of Word (2000, 2003, 2007), Word replaces several of the fonts with something that looks like Arial bold.Sometimes it changes just the title fonts, sometime the entire body font--it's not always the same phenomenon in each document.
The Font window on the Home tab still shows the name of the original font being used in the document, but the screen does not show that font--it just shows whatever it replaces the font with. Repeat: even though the screen in showing a different font, the Font window on the Tab Screen shows the name of the font the document should be showing.
When I change to Draft View, the fonts all display properly, but I need the correct fonts in the Print Layout to show because the bogus font that Word substitutes throws off the accuracy of what I'm looking at.
Is anyone else having this problem?
Jeff
A family of Microsoft word processing software products for creating web, email, and print documents.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
I solved this problem by saving the troublesome file in what 2010 calls "compatability mode>"
Eutactic, I finally tried this solution. I really was not comfortable deleting everything under \Office, but after backing up the registry, I gave it a try. So far it seems to have worked. I will be finishing an important project during the week, so I will have daily opportunities to see how this holds up.
Thanks for the recommendation.
Jeff
I believe I have solved this problem by simply backing up and deleting all the registry values in HKEY_CURRENT_USER\Software\Microsoft\Office. Obviously this is an extreme approach that wiped my preferences, but it appears to have done the trick.
This happens when the font specified by the document formatting
doesn't exist in the Windows\Fonts folder.
Open one of the problem documents and then click File > Options >
Advanced. In the "Show document content" section, click the Font
Substitution button. The resulting dialog will show which fonts are
unavailable and which ones are being substituted for them. Then look
in the C:\Windows\Fonts folder to see whether the "missing" fonts are
really missing.
I didn't think that upgrading from Office 2007 to 2010 would remove
any fonts, but I could be mistaken. If that's what happened, and if
you still have the Office 2007 installation disk, you might be able to
get the .ttf files from there, or copy them from another computer that
still has them.
If the files are in the Fonts folder, maybe they're corrupted or not
properly registered. Running the Office installer in repair mode
should fix that.
On Wed, 9 Jun 2010 21:52:26 +0000, jlp51 wrote:
I upgraded from Office 2007 to 2010 two weeks ago. Whenever I open up documents in Print Layout View that were created under earlier versions of Word (2000, 2003, 2007), Word replaces several of the fonts with something that looks like Arial bold.Sometimes it changes just the title fonts, sometime the entire body font--it's not always the same phenomenon in each document.
The Font window on the Home tab still shows the name of the original font being used in the document, but the screen does not show that font--it just shows whatever it replaces the font with. Repeat: even though the screen in showing a different font, the Font window on the Tab Screen shows the name of the font the document should be showing.
When I change to Draft View, the fonts all display properly, but I need the correct fonts in the Print Layout to show because the bogus font that Word substitutes throws off the accuracy of what I'm looking at.
Is anyone else having this problem?
Jeff
Jay Freedman MS Word MVP