Hi,
it seems, that there's a problem with the encoding of the document properties in some PDFs.
The attached archive contains a PDF, which is affected by this issue.
The title property and the author property contain numerous "\???" strings (where ? replaces a digit). The properties are displayed correct in Adobe Reader 7.
Regards, Michael
Encoding problem in document properties
Moderators: PDF-XChange Support, Daniel - PDF-XChange, Chris - PDF-XChange, Sean - PDF-XChange, Paul - PDF-XChange, Vasyl - PDF-XChange, Ivan - Tracker Software, Stefan - PDF-XChange
-
BigMike
- User
- Posts: 310
- Joined: Wed Nov 07, 2007 10:07 am
Encoding problem in document properties
You do not have the required permissions to view the files attached to this post.
-
Lzcat - Tracker Supp
- Site Admin
- Posts: 677
- Joined: Thu Jun 28, 2007 8:42 am
Re: Encoding problem in document properties
Have tried Acrobat 8 and Acrobat 9 - all properties displayed same as in Viewer.
Do you think that both of them wrong?
Do you think that both of them wrong?
Victor
Tracker Software
Project manager
Please archive any files posted to a ZIP, 7z or RAR file or they will be removed and not posted.
Tracker Software
Project manager
Please archive any files posted to a ZIP, 7z or RAR file or they will be removed and not posted.
-
BigMike
- User
- Posts: 310
- Joined: Wed Nov 07, 2007 10:07 am
Re: Encoding problem in document properties
I don't have Adobe 8 or 9 installed here. If they display properties as PDF-XChange Viewer does, I'd say, it's a problem with the PDF producer. Just to be sure, for me:
The author is displayed as: and the title is displayed as which is probably not intended.
But if Adobe displays the same with the latest version, I don't see any reason, why you should change anything.
Thanks for reviewing the document,
Michael
The author is displayed as:
Code: Select all
\376\377\000r\000o\000l\000a\000n\000dCode: Select all
\376\377\000i\000c\000h\000 \000k\000a\000n\000n\000 \000k\000e\000i\000n\000e\000 \000M\000a\000i\000l\000s\000 \000b\000e\000a\000n\000t\000w\000o\000r\000t\000e\000nBut if Adobe displays the same with the latest version, I don't see any reason, why you should change anything.
Thanks for reviewing the document,
Michael
-
Stefan - PDF-XChange
- Site Admin
- Posts: 19930
- Joined: Mon Jan 12, 2009 8:07 am
Re: Encoding problem in document properties
Yep we could blame the creator 
I have seen such results with Open Office created documents when a language other than English is used (for anything else they use unicode) and that's the result - unreadable document properties.
I think there was a topic on this in the forums will try to dig a link to it now.
Cheers,
Stefan
I have seen such results with Open Office created documents when a language other than English is used (for anything else they use unicode) and that's the result - unreadable document properties.
I think there was a topic on this in the forums will try to dig a link to it now.
Cheers,
Stefan
-
BigMike
- User
- Posts: 310
- Joined: Wed Nov 07, 2007 10:07 am
Re: Encoding problem in document properties
Maybe this one.
The error description seems to fit...
I'm sorry - I should have done a deeper search, I just had a short glance before posting...
The error description seems to fit...
I'm sorry - I should have done a deeper search, I just had a short glance before posting...
-
Stefan - PDF-XChange
- Site Admin
- Posts: 19930
- Joined: Mon Jan 12, 2009 8:07 am
Re: Encoding problem in document properties
Yep that one,
But no worries it's not an easy topic to find.
It actually took me more time to find it than you and I knew it's somewhere there
So the solution is to change the PDF Creator as we are following the specifications and by them we are displaying the right info as Ivan explained in the other topic.
Cheers,
Stefan
But no worries it's not an easy topic to find.
It actually took me more time to find it than you and I knew it's somewhere there
So the solution is to change the PDF Creator as we are following the specifications and by them we are displaying the right info as Ivan explained in the other topic.
Cheers,
Stefan