We're sorry Aspose doesn't work properply without JavaScript enabled.

Free Support Forum - aspose.com

Table in PDF isn't equal to a one in DOCX

Hi guys,


Attached is zip file with 2 documents build by Aspose.Words. The columns size in PDF is not correct. The call of mOutputDocument.UpdateTableLayout(); before saving the document didn’t help.

Regards,
Alex
Hi Alex,

Thank you for inquiry. While using latest version of Aspose.Words, we did not observe Table layout problem. It would be great if you try to use the latest version at your end and see if it resolves your issue. I have attached output Pdf file.

In case of any ambiguity, please let me know.

Hi Imran,


Thank you for quick response. I beg your pardon but I put wrong DOCX file in zip. Correct one is attached now. And yes, I am using 11.0.0.0.

Regards,
Alex

Hi Imran,


Any luck in reproducing the issue?

Regards,
Alex

Hi Alex,


Thank you for inquiry. While using latest version, i managed to reproduce bottom line style difference, highlighted in screen shot as well. I have
logged your issue into our bug tracking system. Your request has also been
linked to the appropriate issue. Once we sort it out, we will let you
know.

Sorry for inconvenience. If you facing any other issue, please highlight it with screenshot.

<o:p></o:p>

Hi Alex,


Moreover, you can use following code snippet as workaround:

Document doc1 = new
Document(“c:/temp/test013/Test11.docx”);

MemoryStream stream = new MemoryStream();

doc1.Save(stream,SaveFormat.WordML);

Document doc2 = new Document(stream);

doc2.Save("c:/temp/test013/Test11Out.pdf", SaveFormat.Pdf);


Hope this will help.


Hi Imran,


Thank you, the workaround works perfectly.

Regards,
Alex

Hi
Alex,


Thank you very much
for your feedback. It is great to hear that your issue has been resolved. You
are always welcome and please feel free to ask if you have any query in future.<o:p></o:p>

We always welcome constructive response from our customers.


The issues you have found earlier (filed as WORDSNET-5929) have been fixed in this .NET update and this Java update.


This message was posted using Notification2Forum from Downloads module by aspose.notifier.