Acrobat 7 Standard making strange character substitutions

[Tom_C...@adobeforums.com]

Yes, we're still using Acrobat 7.

Acrobat has always been unable to handle some fonts (particularly decorative fonts such as cursive fonts) but until recently it has handled most common fonts reasonably well.

Today I created a document in MS Word and created a pdf file from it by using the "Adobe PDF" printer driver selection -- as usual.

And, of course, Acrobat created the PDF file, as it always has....

BUT today Acrobat is changing some of the characters within one font.

Acrobat is changing ordinary zero characters to a slashed zero character (which doesn't even exist in this font)

Acrobat is changing ordinary apostrophe characters into some strange large capital O with a tilde over it. Interestingly enough, Acrobat is inserting this enormous character but only leaving the amount of space normally occupied by the regular apostrophe, so that the s after the apostrophe is coming out inside the middle of the O character.

And Acrobat is changing the degree symbol character to a 1/4 fraction character.

Interestingly enough Acrobat makes these substitutions only in one specific font within the document. Parts of the text that are in a different font or even in the same font but in BOLD are not having the problem.

The font where Acrobat makes these strange substitutions is Windows' own Arial font -- specifically 11 point Arial regular -- it doesn't make these strange substitutions in text written in 11 point Arial Bold or in Times New Roman

[Tom_C...@adobeforums.com]

I just changed the 11 point Arial regular text to 11 point Arial Narrow regular text -- and Acrobat worked correctly

Changed the text back to 11 point Arial regular and Acrobat changes all the Zeros, Appostrophes, and degree symbols.

[Bill@VT]

This is an issue with fonts not being embedded in a PDF and with 4 fonts that are listed by Acrobat. I have the link to the knowledge base on another computer, but you can search for it. The solution is to remove 4 fonts as I recall. Then the font substitution works correctly. The problem is finding the problem fonts in the knowledge base.