Problem with margin on docx to pdf conversion

Aspose.Words Product Family
1

Hello,


We are facing to an issue on docx to PDF conversion.

Please find in attachement the file test1.docx. It’s the source file to convert.

The file test1.pdf is the result on the conversion with Aspose code, provided in code.txt file.

Could you please have a look on this issue, because the result pdf file is not correct on margin right, especially for tabs.

I provide you the file test1-ok.pdf file, get by save function directly in MS Word.
This file is correct.

Thank you.

Regards.

Alexis.
2

Hi Alexis,


Thanks for your inquiry.

While using the latest version of Aspose.Words i.e. 15.9.0, we managed to reproduce this issue on our end. We have logged this issue in our bug tracking system. The ID of this issue is WORDSNET-12601. Your thread has also been linked to this issue and you will be notified as soon as it is resolved. Sorry for the inconvenience.

Best regards,
3

Hello support team, Can you give a resolution date for this subject? I have to take my commitment to customers. Many thanks for your return. Raphaël

4
Hi Alexis,

Thanks for your inquiry. Our product team has completed the analysis of this issue (WORDSNET-12601) and the root cause has been identified. However, the implementation of the fix of this issue has been postponed till a later date.

The issue actually depends on the resolution of an internal extremely complex issue (WORDSNET-832). Therefore, WORDSNET-12601 is postponed until at least WORDSNET-832 is resolved, our product team will review your issue after the first iteration of WORDSNET-832 is ready. We apologize for your inconvenience.

Best regards,
5

Dear Support team,

Is it possible to have a planning for the resolution of these WORDSNETs?

Many thanks in advance.

Raphaël

6

Hi Raphaël,


Thanks for your inquiry. Unfortunately, we won’t be able to share any reliable estimate at the moment. The implementation of the fix of this issue has been postponed till a later date. We will inform you via this thread as soon as this issue is resolved. We apologize for your inconvenience.

Best regards,
7

Dear Support team, Is it possible to have a planning for the resolution of these WORDSNETs? Many thanks in advance. Raphaël

8
Hi Raphaël,

Thanks for your inquiry. This problem actually requires us to implement a new feature in Aspose.Words and we regret to share with you that implementation of this issue has been postponed for now. However, the fix of this problem may definitely come onto the product roadmap in the future. Unfortunately, we can not currently promise a resolution date. We apologize for your inconvenience.

Best regards,
9
Hi Raphaël,

Thanks for your inquiry. Unfortunately, we won't be able to share any reliable estimate at the moment. The implementation of the fix of this issue has been postponed till a later date. We will inform you via this thread as soon as this issue is resolved. We apologize for your inconvenience.

Best regards,
10

Hello Support team,
do you have any news on this topic ?
Best regards
Daniel STEPHAN
AIRBUS

11

Hi Daniel ,


Thanks for your inquiry. Unfortunately, we won’t be able to share any reliable estimate at the moment. The implementation of the fix of this issue has been postponed till a later date. We will inform you via this thread as soon as this issue is resolved. We apologize for your inconvenience.

Best regards,
12

The issues you have found earlier (filed as WORDSNET-12601) have been fixed in this Aspose.Words for .NET 22.8 update also available on NuGet.