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
PDF-XChange Viewer 2.055 Viewer no longer modifes the Producer field in a document's information fields. Instead it uses a custom information field to store data regarding the version used to save a document.
I installed PDF-XChange Viewer 2.054 and I have the same problem.
I installed PDFCreator 0.9.6 and I have the same problem now. I disappointed
The change in the latest build is in regards of the "creator" field not being changed from e.g. PDFCreator to PDF XChange - we will now write the name of our application in a custom field e.g. "Modified By" instead of overwriting the creator information.
The "problem" with the latest version of PDF Creator is that the correct metadata instead of unicode characters is an ASCII string of the unicode representation. The correctly formatted information Adobe is displaying is stored in another filed - which according to their own specification should not be used if there is data in the "incorrectly formatted" one we are displaying.
The problem originates with PDF Creator and GPL rather than with us, as we are following the specification here, and are displaying for you the information that we are supposed to.
I tested Bullzip PDF Printer, PDFill PDF Writer and PDFCreator but all software which uses Ghostscript as PrimoPDF, CutePDF Writer, etc. seems affected.
PDF-XChange Viewer 2.056
GPL Ghostscript 8.70 and older : Title, Author, Subject and Application are false GPL Ghostscript 8.71 : Title, Author, Subject and Application are true GPL Ghostscript 9.00 : Subject are false
Advice :
Firstly, Install Ghostscript and you will be able easily upgrade or downgrade version.
Secondly, Install one (several) PDF Printer/Writer and it will discern Ghostscript automatically (not Bullzip PDF Printer with version 9.xx).
If I have an answer of Artifex Software or if a new version of Ghostscript is distributed I would inform you.
Anyone can submit problems at http://bugs.ghostscript.com. Please put the relevant
info into a 'New' bug there and we'll have a look. Please make sure and give the
Ghostscript invocation used (command line) and attach any relevant sample file.
I tried to look at the 'tracker-software' site below, but it wanted me to register
before showing me anything (which I didn't want to do).
Also at bugs.ghostscript.com you can search to see if the problem is already
reported, or search CLOSED bugs for a fix if it works in the latest release (that
is probably not the case for your current problem since I see you mention
9.00)
I see that there is some development on your bug report, but it does seem like they will need the resulting PDF as well.
As it's not our fault shall we consider this as solved on our side?