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.
To assist us in solving this issue, please answer the following questions. Thank you.
4. Can you reproduce the issue in *.doc files? [File -> Save As -> Save as type = "Word 97-2003 Document (*.doc)"]
-Omega
===
Here are several workarounds for this issue from my other thread, but please continue to assist us by answering the questions above. Workarounds in order of most convenient to least convenient are:
-Omega
ARGH.
It seems that Microsoft's position is thatuntil andunless the first-level Word tech support can duplicate the problem on a (virtual) machine, there's nothing that can be done. I've spent a fair amount of time trying things, but (1) though I have been able teo find a easy, simple, consistent reproduction scenario (on my machine), (2) have been unable to come up with a way for MSFT first-level support to see the problem happen.
The more I mess with this, the more convinced that thisis certainly a Word bug, but simply can't get past the Word firewall "If I can't make it happen here, there's nothing we can do."
I have one PC with the problem, one without. Unfortunately, the one with the problem is my main PC (and the one that generates the bulk of my revenue). I could take a day or two and reinstall everything (taking good notes), which may yield a PC that has the problem... but frankly I'm not entirely sure if I can spare the time.
Does anyone out there care enough about this problem to help me out? I've spent a great amount of time getting nowhere, and the only path forward seems to be one that'll take another 'bunch' of time. Can someone start from scratch, a complete reinstall, and take very good notes about what was installed/updated in what order that yields a computer with the problem?
Otherwise, I'm not sure we'll ever get anywhere. Please post if you're willing to help out.
Adam
All:
MSFT tech support has closed the incident. They'll re-open and deal with it ONLY IF someone can describe a repeatable scenario for reproduction -- in this case, this means a PC configuration that yields the problem. See above, can someone help out?