Link to home
Start Free TrialLog in
Avatar of Trinity_Eric
Trinity_Eric

asked on

When using Adobe Pro 8, a user is getting PDF's that have random # signs which did not exist on the original MS Word 2010 Document.

Other users are not experiencing this phenomenon with same versions. I have applied all updates from Adobe, only this one user is generating these # signs within the document.
Avatar of jmdion
jmdion


Are the # signs replacing characters that should be there or are they inserted in between?  Can you post a sample PDF not containing confidential information?
Avatar of Trinity_Eric

ASKER

Before and after screen shots of Word and then the PDF that is output.
WORD-example.jpg
PDF-example.jpg
Let me know if you want the actual .pdf
This is very strange.  I am stumped.
Doesn't do it on other PC's and doesn't happen with Nitro PDF... going to end up wasting an Adobe license I fear.
Avatar of Ingeborg Hawighorst (Microsoft MVP / EE MVE)
Hello,

does Word have any characters in that position? Can you post a screenshot of Word with the hidden characters (paragraph marks, etc)  turned on?
There is a paragraph mark in that location, but there is also one below that outside the header that does not produce the # sign in the PDF. (screenshot attached)

We had trouble before with # signs showing up in the PDF conversion and our marketing company made some changes to remove hidden characters. It works fine for everyone else in the office except this one machine.
Word-withparagraph.jpg
Maybe format that paragraph (including the paragraph mark) as white text on white background and see if the PDF still shows the #.

It's not a solution to the issue, just a workaround ...


ASKER CERTIFIED SOLUTION
Avatar of Trinity_Eric
Trinity_Eric

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Glad you found a solution. Happy for you to accept your own answer on this. cheers,
No one was able to identify why this was happening, I was able to create a workaround by upgrading Adobe.