Convert DOCX file into Image based PDF

Aspose.Words Product Family
1

Dear,

We would like to use the Aspose.Word product to convert DOCX file to PDF.
This PDF we would want to be image based, so no teyt based pdf, but image.

Every page in the DOCX document, should become a separate image in the pdf.

Doing like this, we hope to preserve the layouting of the Docx file.

In general the text based is ok, but we occasionally run into the issue that there a few more lines on the PDF page than on the original DOcx page.

Many thanks for your support

Patrick Vanbrabant

2
Hi Patrick,

Thanks for your inquiry. In your case, we suggest you please save the document to TIFF file format as shown below and convert it to PDF using code example shared in following article. Hope this helps you.
Convert an Image to PDF

Document doc = new Document(MyDir + "input.docx");
doc.save(MyDir + "output.tiff", SaveFormat.TIFF);
PatrickVB:
In general the text based is ok, but we occasionally run into the issue that there a few more lines on the PDF page than on the original DOcx page.
However, if your issue is related to page layout then you will face the same issue in output TIFF file format. Could you please attach your input Word document here for testing? We will investigate the issue on our side and provide you more information.

3

Hi Tahir,


Many thanks for the quick reply.

I have attached the document used for testing and the resulting pdf.
The problem is with the last paragraph of page 6. I think it is related to not respecting the Widow/Orhpan control.
Even though that paragraph has the setting to avoid widow/orphan lines, the resulting pdf is not respecting that setting.

In the Docx document, there are two lines of that paragraph on page 7. In the resulting pdf document, there is only one line on page 7.

I’m using AsposeWords 17.6 Java.

For us it is a very strong requirement that the pdf document must be identical to the original Docx document.

Regards

Patrick
4
Hi Patrick,

Thanks for sharing the detail. We have tested the scenario and have managed to reproduce the same issue at our side. For the sake of correction, we have logged this problem in our issue tracking system as WORDSJAVA-1604. You will be notified via this forum thread once this issue is resolved.

We apologize for your inconvenience.

5

Hi Tahir,


Is there any known workaround?

Thanks

Patrick
6
Hi Patrick,

Thanks for your inquiry. Unfortunately, there is no workaround for this issue. We apologize for your inconvenience.
7

Hi Tahir,


Do you have any estimate by when the bug could be fixed. We are currently evaluating Aspose.Words to be integrated in our of our applications.

However as indicated before, we have a strong requirement that the resulting output of the pdf conversion must be identical to the original Docx document.

Any indicated of timeline would be appreciated.

Kind regards

Patrick Vanbrabant
8
Hi Patrick,

Thanks for your inquiry and sharing the concern. Currently, your issue is under analysis phase. Once our product team completes the analysis of your issue, we will then be able to provide you an estimate.

Thanks for your patience and understanding.
9

Hi Tahir,

What is the status of this issue. Currently the plan is to go into production with the project which needs the Docx to PDF conversion end of October.

Any indication by when the issue would be fixed, is essential for our decision making on procurement or not.

Many thanks
Patrick

10

@PatrickVB,

Thanks for your inquiry. We regret to share with you that your issue has been postponed. We will inform you via this forum thread as soon as there are any further developments.

We apologize for your inconvenience.

Best Regards,
Tahir Manzoor

11

Dear team,

Is there any update on the issue about not respecting the Orphan setting. The issue has been reported almost one year ago.

Many thanks for the feedback

Patrick

12

@PatrickVB,

Thanks for your inquiry. Unfortunately, there is no update available on this issue. We will inform you via this forum thread once there is any update available on this issue.

We apologize for your inconvenience.

13

The issues you have found earlier (filed as WORDSJAVA-1604) have been fixed in this Aspose.Words for .NET 20.5 update and this Aspose.Words for Java 20.5 update.