The source code xxx is broken message

[joeitaliano]

hello

i have opened a document using the viewer and filled some of the form fields and saved the document.

i have now i opened the same document using adobe and also filled the form and and saved it

now when i open the document using the viewer the message "the source document xxx is broken. pdf-xchange cannot use the save for this document..."

any reason

thanks

[John - Tracker Supp]

Hi Joe,

can you please provide a sample and advise which of Adobe's products you used to complete the form and save ?

Thanks

[joeitaliano]

hi john have emailed it you you please confirmed you have received it

[Paul - PDF-XChange]

Hi joeitaliano,

we recieved an email with an attachment pdfproblem.old. We will look into this today.


thanks

[joeitaliano]

hi paul just checking if any progress on this one

thanks joe

[Paul - PDF-XChange]

Hi Joe,

sorry for not getting back to you on this one. I opened both documents without that error. Can you confirm you are using the current build of the Viewer? 2.5.191.

Also - I believe you are using Win 7 x64. Is that right? I can test on that platform if needed...

[joeitaliano]

hi john

i opened the one that titled .. after adobe and on the bottom left hand side there was an warning symbol. see attachement

[Paul - PDF-XChange]

Got it, thanks joe,

will test after the week end.

Regards

[Lzcat - Tracker Supp]

Hi Joe.
Typically we show this warning message when non all pdf objects described in xref tables or streams. In general all pdf objects from document range (from 0 to MaxObjNum) should be described in xref table (or stream), even some of them are not used (they are marked as free), but for some reason Adobe leave holes in pdf documents with XFA forms (yes, some unused objects are not listed in xref). And as always Adobe product prefer to not notify about this as we does.
In most cases you may safe ignore non-critical errors and they will be corrected during save if it is not incremental.
HTH.

[joeitaliano]

victor

please see attachment zip file

the one with out word bad in the file name i opened and then changed some text and saved it as bad

now what happens is that if i open the bad one with adobe it complains and does not allow me to do anything

can this be fixed please

[Lzcat - Tracker Supp]

First file (saved using Adobe) contains an Adobe-specific digital signature which allows Adobe Reader to modify the document (without this signature Adobe Reader won't modify the document).

Second file (updated by Viewer) also contains this signature, but there were changes and therefore the Reader treats this document as altered after signing, so the signature is no longer valid (and won't modify it).

This is Adobe specific behaviour, and we can do nothing with this.
PS. Second document is valid and can be edited using Acrobat without any problems.

[joeitaliano]

victor

when you say it had a digital signature are you tell me that the document when it was created by the developer was created with a digital signature or is adobe getting to smart and putting one there to give people problems

i want to be able to have these document used without problem between adobe and xchange

joe

[Lzcat - Tracker Supp]

Adobe puts a signature on the file to make the file editable with Adobe Reader.

We cannot add such signature because Adobe does not allow this.

There is no way to work with the file using any other Viewer and Adobe Reader becuse of the Reader limitaions. If you will use Acrobat instead of Reader - it is possible.

Why - ask Adobe and perhaps ask him them if they intended for the PDF standard to be 'Open' why do this ?

[joeitaliano]

victor

it is making more sense now

the solutions is not to have the pdf created by client with "reader extension" rights

joe

[Stefan - PDF-XChange]

Hello Joe,

The solution would indeed be to create your documents without using Adobe products, and then there would be no signature and no issues with the free Adobe Reader.

Best,
Stefan

[joeitaliano]

hi stefan

i agree but outside my control as client uses only adobe

cheers

[John - Tracker Supp]

Hi Joe,

understood - its only since Adobe started offering a few free extra features in their reader to combat the success of our Reader and others - that in the latest release they have chosen to restrict access to documents modified by their free reader if mod's are made - so much for an open PDF Standard !

I should add that Adobe have tried this previously and eventually been forced to remove such restrictions as they proved very unpopular and caused a lot of dissent - do not be surprised if these restrictions quietly dissapear in the future ...

[John - Tracker Supp]

Hi Joe,

a little more info - this is possibly not quite as 'nefarious' as first thought/indicated - its actually an error by Adobe when they create the XREF table for the file in the example - they report 'X' number of objects in the table as being present - when in fact there are only 'Y' objects - a cynic might say this is intentional as the net result is we detect an error and want to correct this when opened with our viewer so the file is 100% valid in all PDF compliant tools, but I could not possibly say that...

But by playing by the rules we are in fact shooting ourselves in the foot - as by doing so - we cannot save the PDF with its original valid Digi Sig (Inserted by Adobe when allowing their own Reader to make changes to the file) - it cannot be saved as an incremental update as we are modifying the original XREF to correct the error - which invalidates the signature ...

So - what we need to do is actually identify this very specific type of error and actually not try and play fair and correct the error for the benefit of all - but identify it as an error which will result in problems re-opening in Adobe Reader (only the 'X' versions I should add) if we correct it and consequently actually ignore the issue totally.

Not what we want to do at all - but I think something we will have to try and do - without breaking the option to fix other files with similar issues ...

We are investigating this now and hope to have a satisfactory (well unsatisfactory but functional) solution soon.

Thanks for your patience.

[joeitaliano]

hi john

totally agree with you and you are correct i did use the x reader

i was also right - i am dealing with the smartest people when it comes to PDF

keep up the good work and i will try to give you more input as i find things so that adobe can have a hard time

cheers

[John - Tracker Supp]

Hi Joe,

thanks for the kind words and understanding - we hope to have this resolved in a new release as soon as possible which will not modify these specific files in terms of the incorrect XREF table - but continue to do so for other files where the XREF table is incorrect and no Digi Sig exists.

HTH

[Paul - PDF-XChange]

Hi Joe,

I am happy to be able to tell you that your issue (RT#782: Correcting Invalid Adobe XREF table causes problems later in Adobe Reader) was resolved in the most recent build. Please update to the latest build and confirm.
http://www.docu-track.com/knowledgebase ... nt-version

I have closed the ticket. Should you require further action please let me know.

Paul

[joeitaliano]

fantastic

do you know if RT#777: Form fields allow typing beyond visible boundaries is also fixed in that release

many thanks

joe

[Stefan - PDF-XChange]

Hello Joe,

I am afraid that ticket 777 is still open and there has been no update in it mentioning any fixes in build 192.
I will try to get some more information on it from the devs.

Best,
Stefan

[joeitaliano]

hi stefan

where can i get a list of the bug fixes for a release so i can check in future

thanks

joe

[John - Tracker Supp]

Hi Joe,

its here when ready - the udpated one will be posted later today :

https://www.pdf-xchange.com/PDFXV_history.html