Problem converting Word that created by OpenXML to PDF

Hi,


In our .NET application, we create a WORD document using OpenXML technology, and then using Aspose.Words to convert the doc byte array to PDF, but in the output PDF the tables are corrupted.
Attached an example of the output PDF (1.pdf).

If we save the source WORD in the file system ,then open it in MS-WORD and the convert it to PDF - the output PDF is OK (attached 2.pdf), but this is not possible in our case.

thanks,
Ariela



Hi Ariela,

Thanks for your inquiry. To ensure a timely and accurate response, please attach the following resources here for testing:

  • Your input Word document.
  • Please attach the output Pdf file that shows the undesired behavior. (1.pdf have 0kb file size)
  • Please create a standalone console application (source code without compilation errors) that helps us to reproduce your problem on our end and attach it here for testing.

As soon as you get these pieces of information ready, we'll start investigation into your issue and provide you more information. Thanks for your cooperation.

PS: To attach these resources, please zip them and Click 'Reply' button that will bring you to the 'reply page' and there at the bottom you can include any attachments with that post by clicking the 'Add/Update' button.

Attached the original word + 1.pdf & 2.pdf

it’s important that you don’t open the original word with MS Word, because then it fixes something and the problem does not occur

The code is a basic conversion - opening the word document and then saving it as PDF, with no parameters

Hi Ariela,

Thanks for sharing the detail. We have converted the shared document (wordExample.docx) to Docx and Pdf. We have noticed the table rendering issue in output Pdf. For the sake of correction, we have logged this problem in our issue tracking system as WORDSNET-13888. You will be notified via this forum thread once this issue is resolved. We apologize for your inconvenience.
dvirP:
it's important that you don't open the original word with MS Word, because then it fixes something and the problem does not occur
Thanks for sharing this detail. Unfortunately, the input document (wordExample.docx) cannot open in MS Word. See the attached image for detail. We need the correct document for further investigation. Thanks for your cooperation.

Hi,


Please change the extension of the word document to “.docm” (instead of “.docx”) and then it can be opened by MS Word.
The original extension was “.docm”, I changed it because your site does not support attachments with this extension.
Sorry for not mentioning it before.

Ariela
Hi Ariela,

Thanks for sharing the detail. We will inform you via this forum thread once this issue is resolved. We apologize for your inconvenience.

Hi,


Any news with this issue?
Hi Ariela,

Thanks for your inquiry. We try our best to deal with every customer request in a timely fashion, we unfortunately cannot guarantee a delivery date to every customer issue. Our developers work on issues on a first come, first served basis. We feel this is the fairest and most appropriate way to satisfy the needs of the majority of our customers.

Currently, your issue is pending for analysis and is in the queue. Once our product team completes the analysis of this issue, we will then be able to provide you an estimate.

Thanks for your patience and understanding.

Any news? we need a solution for this problem as soon as possible.

Please your help

Thanks
Hi Ariela,

Thanks for your inquiry. We regret to share with you that your issue (WORDSNET-13888) has been postponed due to missing feature WORDSNET-832 (Make table layout as close to Word as possible) which is related to your issue.

After the fix of WORDSNET-832, our product team will look into your issue. We will be sure to inform you via this forum thread as soon as this feature is available.

We apologize for your inconvenience.

A post was merged into an existing topic: Problem converting Word created by OpenXML to PDF

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