Hello Team,
During evaluation of your product, I’ve noticed significant differences between formatting of input DOTX file and output PDF file (without modifying of document structure, just opening it to Document object and saving to PDF).
The differences spotted are:
- border formatting of the first table on the first page (single line instead of double-line),
- text wrapping on the right hand side of the first table (space is removed, below paragraph content starts in the column next to table instead of below the table)
- the bottom-border formatting of the second table on the first page.
I attach the solution which should allow to test the issue + docx output for the same input file (which keeps the right formatting on the document).
Could you please take a look and let me know what exactly happens here? Is there something that I can do on my end to fix the behaviour observed?
Thanks,
Rafał
Hi Rafał,
Thanks for sharing the detail. We have tested the scenario and have managed to reproduce the same issues at our side. For the sake of correction, we have logged these problems in our issue tracking system as follow:
WORDSNET-15071 : Allow spacing between cells is lost after DOTX to PDF conversion
WORDSNET-15072 : DOTX to PDF conversion issue with table's position
You will be notified via this forum thread once these issues are resolved. We apologize for your inconvenience.
rafal.siwakowski:
- the bottom-border formatting of the second table on the first page.
We have not found this issue while using latest version of Aspose.Words for .NET 17.3.0. Please use
Aspose.Words for .NET 17.3.0. We have attached the output PDF with this post for your kind reference.
Hello Tahir,
Many thanks for the quick reply. I will update my version of Aspose.Words and I am looking forward to hearing from you.
Cheers,
Rafał
The issues you have found earlier (filed as WORDSNET-15071) have been fixed in this Aspose.Words for .NET 22.8 update also available on NuGet.
Hi does this issue persist in aspose words for java 21.6.3
@priyanka9 The issue WORDSNET-15071 has been resolved in 22.8 version. Another issue reported in this thread WORDSNET-15072 is not yet resolved, it has been postponed and is not yet scheduled for development.