I just experienced the same thing when trying to eSign the doc. Weird. I'm using Reader X.
I am experiencing a similar problem with a pdf document created in MS Word 2007.
When viewed in Acrobat 7 Std or 9.X Pro, the document content displays normally. But when viewed in Reader 9 or X, the following events occur:
- Immediately upon scrolling up or down to a page with an embedded Visio drawing (.vsd), a Korean language pack error message appears. Message text varies depending on Reader version.
- Embedded Visio drawings display only a portion of their shape elements. See the example below. The image is company proprietary so I can't show you a full image for comparison.
Both of the above errors occur in:
- new pdfs generated from the archived Word 2007 source document;
- the archived pdf whenever it is retrieved an reopened.
Previously, the archived pdf could be opened and viewed in Reader 9 or X with neither of the above errors occuring.
I reproduced the errors on several workstations.
Both errors always occur together.
I confirmed the default language in Word, Visio, and Acrobat as U.S. English.
While our problems differ, my solution may still be relevant.
My culprit was a rogue font in an embedded Visio drawing. I identified and located the font using the "List text using non-embedded fonts" Preflight analysis in Acrobat 9.4 Pro. I checked the encoding of each non-embedded font and discovered that Arial Unicode MS used Korean font encoding (specifically, KSCms-UHC-H). See screenshot below. Doubleclicking on one of the font properties highlighted the offending text in the pdf.
I went to that location in the source file, which happened to be in the first embedded Visio drawing (shown above). I double clicked the drawing, selected all, and selected Arial font. Then I regenerated the pdf and viewed it in Reader X. The Korean language pack error message did not appear and all Visio drawings displayed normally.
I would recommend using the Acrobat preflight tools to locate text or objects with incorrect font encoding within your PDF or form, then surgically striking (or carpet bombing) the affected location(s) in the source files with embedded/supported fonts.
Hope this helps.
Message was edited by: mugg326