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.
Gentlemen:
On my system I can repeat the Word 2010 unintended display of the Arial-like font change as follows:
1. Clean up your system by doing a system restart.
2. Open your pinned Word 2010 from the Start Menu to a New Document.
3. Type four or five lines in an OT font (I used Adobe Palatino LT Std). KEEP THIS WINDOW OPEN ON YOUR DESKTOP.
4. Now I go to Start and hover over Word until the recent docs list pops up (a Win 7 feature). Select one on the list which uses an OT font and click to open it. A new Word Window should come up on top of the previous Word window.
5. Type something, anything anywhere in the older OT doc you just opened.
6. Now click the edge of the background Window containing the New Doc (the one with the few sentences you just typed) to bring it forward.
7. Bingo, either (a) you should see an Arial-like font instead of the OT font you intended; or (b), if you don’t, then you will if you drag the cursor over (highlight) some text and then you should see the Arial change as you do.
I've done this a half-dozen times and get the same behavior.
Let me know if you get the same results.
R.
I will continue to monitor this forum to see if those in contact with MS tech support post a solution. My guess is that this is not a matter of settings and options, plug-in or add-on interference, etc., but, sadly, a deeper bug that requires a rewrite to repair.
Please, please, please. Everyone with the problem ***kindly indicate what software (other than Win & Word) that you've installed that comes with fonts.***I believe that the issue may be related to the software that brings the non-MS fonts in.
MSFT tech support has tried to use the fonts that I have trouble with, but doesn't see the problem occur. A theory is that, e.g., Adobe CS5, installation does something to cause this problem to occur.
My interactions with MSFT tech support is that they are (1) trying, but (2) until we can make the situation occur ontheirmachine(s), there's not much they're really going to do.
Please help.