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.
In my earier posting about font substitution, was not very clear. Neither is Word 2010, but here's how I solved a problem with my favorite heading font, Franklin Roman #2, a PostScript font that won't show up on screen in Office 2010:
To make this universal, I opened the Normal.dotm template and applied the font substitution in it.
For those folks who import text from Word files to InDesign, you can set that program to use the Adobe fonts you really want to use in the finished dtp product.
It is a clunky solution, but back in the old days of PageMaker, learned to count on the the Adobe program's formatting and not depend on Microsoft Word to render text the way I wanted it to show up in page layout documents.
Adding my name to the many, many people experiencing this problem. Primarily with Gotham (not an Adobe font! H&FJ.) I was blaming my font manager, which I installed about the same time I upgraded to Word 2010, so I'm really dismayed to find out this is a Word 2010 problem that has persisted for nearly a year.
I do have CS5 installed, my default printer is a Xerox Phaser but I also have Adobe PDF and MS XPS Document Writer installed, I already had a RTL font installed.
My experience mimics other reports that closing and reopening the document will reset it briefly, as will changing the printer, but the more you edit it, the worse the kerning gets until you can't edit the document at all because the letters are so spaced out you can't tell where one word ends and the next begins (and where you click in the document isn't always where it looks like you're clicking, so once the letter spacing has gone crazy, so you can't edit it anyway.) Also (and I haven't seen anyone mention this behavior yet), sometimes the letter spacing is very tight and all the letters pile up on top of one another.
So discouraged that Microsoft hasn't been able to reproduce this. Should we all be listing every installed program to try and find the common thread? Aargh.