This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
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.
Guys, I've just spent days on the telephone with Microsoft support. They took remote control of my computer and were able to reproduce this font rendering problem 100 percent of the time. The problem occurs when the only software on my machine is Windows 7 and MS Office Professional Pro 2010. It only happens in Word 2010. Therefore, we know the problem has nothing to do with printer drivers or third-party software. The fonts I use are Adobe and Linotype OpenType fonts with postscript outlines. These same fonts work flawlessly on every other program on the planet, including all Microsoft products, past and present, EXCEPT Word 2010.
Oddly, although they tried very hard to resolve the problem, MS support approaches the problem this way: "Why aren't Adobe fonts compatible with Word 2010?" I suggest that they have it bass ackwards. The question should be, "What bug in Word 2010 prevents it from working properly with Adobe fonts?"
At the end of the day, tech insists that I need to talk with Adobe to find out why their fonts are not compatible with Word 2010!
I believe that Microsoft needs to put a disclaimer in their advertising for Word 2010 which states, "Caution! MS Word 2010 will not work with industry standard fonts." In the alternative, they could admit there is a bug and fix it... I'm not holding my breath.
Used Font Substitution in Microsoft Word so that when I am working on documents to import to InDesign, it will use a non-Postscript font.
When I import the files into InDesign, use strict style controls to ensure that the Adobe program uses the required Adobe fonts.
I don't think we will ever get Microsoft and Adobe together on this. Furthermore, newer versions of Adobe programs tend to favor Adobe OpenType fonts over older PostScript fonts. Have seen strings of complaints on Adobe's forums about this issue, and keep my old PageMaker DVD around in case I need to reload the PS version of one font which Adobe won't even SELL anymore.
Guess this is forced evolution.
Guys, I've just spent days on the telephone with Microsoft support. They took remote control of my computer and were able to reproduce this font rendering problem 100 percent of the time. The problem occurs when the only software on my machine is Windows 7 and MS Office Professional Pro 2010. It only happens in Word 2010. Therefore, we know the problem has nothing to do with printer drivers or third-party software. The fonts I use are Adobe and Linotype OpenType fonts with postscript outlines. These same fonts work flawlessly on every other program on the planet, including all Microsoft products, past and present, EXCEPT Word 2010.
Oddly, although they tried very hard to resolve the problem, MS support approaches the problem this way: "Why aren't Adobe fonts compatible with Word 2010?" I suggest that they have it bass ackwards. The question should be, "What bug in Word 2010 prevents it from working properly with Adobe fonts?"
At the end of the day, tech insists that I need to talk with Adobe to find out why their fonts are not compatible with Word 2010!
I believe that Microsoft needs to put a disclaimer in their advertising for Word 2010 which states, "Caution! MS Word 2010 will not work with industry standard fonts." In the alternative, they could admit there is a bug and fix it... I'm not holding my breath.