Something is wrong with installer for Build 313!

[gate1975mlm]

I just downloaded PDF-XChange Editor 5.5 Build 313 and something is wrong with the 32Bit/64Bit file in the Zip!

The installer says version 5.5 Build 312.10 not the new Build 313. And also this installer gives me an error and will not install anyway.

[Tracker Supp-Stefan]

Hello gate1975mlm,

Yes we are aware of this, and will fix it as soon as the devs in the Canadian office come to work. In the mean time please use the .msi installation packages that will work correctly.

Regards,
Stefan

[gate1975mlm]

Hello gate1975mlm,

Yes we are aware of this, and will fix it as soon as the devs in the Canadian office come to work. In the mean time please use the .msi installation packages that will work correctly.

Regards,
Stefan

Thanks for the info

Also this build have a lot of new improvements?

[Tracker Supp-Stefan]

Hi gate1975mlm,

Yes there are quite some improvements, and you can now SaveAs PDF/A an existing file using the Editor.
The full version history needs to be reviewed for spelling errors and we will have that uploaded later today as well.

Regards,
Stefan

[David.P]

Ouch...

Build 313 has just destroyed a hundred pages document of mine while saving. The saved version is defective in all alternative PDF viewers. The PDF is currently still open but also defective in PDF-XChange Editor, and it won't 'save' nor 'save as'. Choosing 'save optimized copy' from the file menu does not do anything.




Trying to extract all pages yields a defective extracted document as well.



Seems as if I have to go back to a previous version of both my PDF and PDF-XChange Editor

The PDF in question has been put together and edited using PDF-XChange Editor build 312.

Regards
David

[David.P]

Ouch²...

after uninstalling build 313 and installing build 312, the latter won't even start anymore...



Manually deleting the program folder in order to get rid of the above build 313 remnants now makes it impossible to even install build 312 because of allegedly missing access rights of the installer:



What's more, the installer ignores any alternative path for program installation (F:\Program Files instead of C:\Program Files in my case).



Regards
David.P

[David.P]

Alright, possibly this is (was) related to a recent move of my PC into a company domain which allegedly takes access rights away from drive C:\ (although I have PC administrator rights ).

Therefore, possibly the PDF-XChange Editor installer could not update (all) files in C:\Program Files correctly. However, it did not complain about anything when installing build 313.

Anyway, after temporarily leaving that network domain, I managed to install and run build 313 again.

I edited that same PDF document again and so far, it did not corrupt or break down. Knock on wood.

At any rate, what I guess should be fixed is that the PDF-XChange Editor installer ignores other program paths than the standard path C:\Program Files.

Regards
David.P

[Tracker Supp-Stefan]

Hi David,

Glad to hear that you managed to reinstall correctly, and hoping that that file corruption was a one off.
Thanks for the comments on the installer - will pass them along to our devs!

Regards,
Stefan

[David.P]

Thank you very much Stefan
Regards
David

[Tracker Supp-Stefan]

[David.P]

OK not so much luck, the Editor has done it again (that same PDF is broken again, can't be saved, can't be opened in other PDF viewers).

However this time, the 'Save Optimized Copy' function worked, and largely restored the PDF document however, some pages seem to have lost all font information and look awry.



Therefore, something seems to be broken that had been working in build 312.

Regards
David.P

[David.P]

OK, now my PDF has been destroyed a third time, this time beyond repair.

Going back to build 312 (if I can get it installed).

I'll send you the broken PDF via mail in oder for your engineers to look into it.

Regards
David.P

[Will - Tracker Supp]

Hi David,

Thanks for the post - please make sure that the optimization wasn't set to un-embed embedded fonts (fonts section). Also, please make sure that the PDF Specification Version is higher than 1.2 (Document Properties --> Description).

Cheers,

[David.P]

Yes Stefan, I did not unembed any fonts. Also, the PDF broke down before optimizing it, just by a normal 'save'. The PDF version is 1.6.

Regards
David

[Will - Tracker Supp]

Hi David.P,

Did you send the PDF via email yet? If so, I'm not sure that we've got it. If not, please do send it as and when you can.

Do you still have a copy of the PDF before it was corrupted? If so, then please send this too.

Cheers,

[David.P]

Hello Will,

thank you for your reply. Actually I had sent the file to a wrong address. I just re-sent it to your support e-mail.

I had already thought of sending you the file before it got corrupted, however hesitated because it contains confidential stuff (which I deleted from the corrupted file that I was able to open with PDF-XChange Viewer). Additionally, I'm in holiday now, and don't have access to that file for a week.

Therefore I hope you can find out something from the corrupted file.

The file was put together from a number of scans and then OCR'ed with Ad*be Acr*bat ClearScan, as I always do.

Cheers
David

[Will - Tracker Supp]

Hi David,

Thanks for that - we'll see what we can do with the corrupt file. If we need the original, I'll get back to you.

In the meantime, enjoy your holiday

[generosis]

Hello folks,

I seem to have the same problem.
Editor corrupts my pdf files.
Just to test it out, I tried it on the "PDF_VE_.pdf" file in the installation folder("PDF Editor" folder).
I did a highlight and saved. Everything ok. After a second time, this comes up:


I do a full save. Everything ok. After a couple of highlights though they become invisible:


As a proof, note that two of them are selected and with yellow color in the panel, but transparent on the page.
If I do an incremental save, this pops up:


If I open the file with the latest Xchange Viewer:

The red highlights are done with Viewer.

Viewer handles all the other "corrupted" files well though, as far as editing and saving goes.

Regards

[Tracker Supp-Stefan]

Hello generosis,

Yes I managed to reproduce this when I switched on the "Always use incremental save" checkbox in the Editor preferences, and then trying to place a couple of highlights.

I will pass this to our devs now for investigation.

Regards,
Stefan