DOCX to PDF convertion issues Spire.Doc for Java

[smfukaya]

Dear E-Iceblue,

I have just started using Spire.Doc for Java in order to convert some DOCX files to PDF but the outcome files layouts are broken. I am attaching the source and the output files and I was wondering if you could help us.

With spire.doc 2.10.3 the converted PDF file did not keep the DOCX page layout / breaks.

With spire.doc 2.11.5 Acrobat Reader shows the error message "An error exists on this page. Acrobat may not display the page correctly. Please contact the person who created the PDF document to correct the problem." and renders the file with all pages blank (Google Chrome 79.0.3945.79 64-bit does not display any message but also shows it with blank pages, and Mozilla Firefox Browser Developer 72.0b6 64-bit loads its content with the same bad layout of those generated with spire.doc 2.10.3).

Thanks in advance.

Yours sincerely,
Sergio Fukaya

[smfukaya]

Dear E-ICEBLUE Support,

I am also attaching the converted PDF file using the spire.doc for Java 2.10.3 based on the https://github.com/eiceblue/Spire.Doc-f ... toPDF.java example and https://github.com/eiceblue/Spire.Doc-f ... plate.docx file.

Yours sincerely,
Sergio Fukaya

[Amber.Gu]

Hi,

Thanks for your inquiry.
I tested your files with Spire.Doc for Java Version:2.11.5 and did notice some issues. For the file "pc07TC-042859-026-12.docx", there was the same error message as you mentioned when I opened the result Pdf file by Adobe. For the file "convertedTemplate.docx", I didn't get the same issue as yours, but I found the result Pdf file was a blank document.
I have logged the two issues into our bug tracking system. Once there is any progress, we will inform you ASAP.
Sorry for the inconvenience caused.

Best wishes,
Amber
E-iceblue support team

[smfukaya]

Hi E-iceblue,

I was wondering if you had any updates on this problem and what are the company SLA for bug fixes. I realized that there is a new version 2.12.3 (by the way, it seems that the JAR in the Maven repository is actually Spire.XLS - at least in its manifest file), but I could not find the release notes. While the document header looks better (except for the missing grayscale filter applied to the images), the body was broken for attached document.

Best wishes,
Sergio Fukaya

[Amber.Gu]

Hi,

Thanks for your reply.
I checked the state of your issue, sorry that it has not been resolved yet. We have urged our Dev team. Once there is any progress, we will inform you ASAP. Sorry for the inconvenience caused.

As for the Maven issue about Spire.Doc for Java, we just checked the Maven repository and found we had uploaded a wrong version of Spire.Xls on the website. We will re-upload the correct package of Spire.Doc for Java on Maven ASAP. Now the latest version is Spire.Doc for Java Version:3.1.1, we suggest you download it from our website firstly before we update the version on Maven.

And you could check the news and release of our products from the following link: https://www.e-iceblue.com/News/list.html

Best wishes,
Amber
E-iceblue support team

[Amber.Gu]

Hi,

Hope you are doing well.
About the Maven issue of Spire.Doc for Java, we have updated the new package of Spire.Doc for Java Version:3.1.1 on Maven. Now you could download the correct version form the following link: http://repo.e-iceblue.com/nexus/content/groups/public/e-iceblue/spire.doc/3.1.1/

Best wishes,
Amber
E-iceblue support team

[smfukaya]

Hi Amber,

The 3.1.1 version produced the same results of the 2.12.3 for the specific document ("pc07TC-042859-026-12.docx(3.1.1).zip"). I dug a little bit and found out that there was some kind of a "hidden" (or not visible) embedded document object (DOCX) reference (r:id="rId4") in the document header section right after the table (word\header1.xml). In order to see it, edit the header with Microsoft Word, select all content of the header section, copy and paste it into a new document. I am not sure, but it seems that it happens if you embed a document right after a table in the header section (maybe is due to the embedded document content height).

Microsoft Word keep it hidden when converting to PDF, while Spire.DOC renders and process it recursively as a document (not as a rendered image) for every page (as it is in the header section).

Removing the embedded object from the DOCX and converting it again, solved that problem ("pc07TC-042859-026-12-fixed.docx(3.1.1).zip"). Perhaps Spire.Doc should be modified to reproduce Microsoft Word behavior... Nevertheless, we need the color filters applied to the images be reproduced too.

Best wishes,
Sergio Fukaya

[Amber.Gu]

Hi,

Thanks for your reply.
I have recorded the information you offered into our bug tracking system. And I have urged our Dev team and improved your issue to the highest priority. Please share us little more time, once there is any progress, we will inform you ASAP.
Sorry for the inconvenience caused.

Best wishes,
Amber
E-iceblue support team

[Phillipsaf]

Astonishing way of expression. Obey it up!

[rachel.lei]

Hi Phillipsaf,

Thanks for your post.
Do you want to know the progress of the issues on this topic? Or you encountered any issue related to our products? If you have any issue about using our products, please provide the detailed information about your issue to help us further investigate it.
Besides, if you have any suggestions for our products, welcome to share with us!

Sincerely,
Rachel
E-iceblue support team