Rtf to Pdf formatting

Hi,

I am converting an Rtf byte[] to Pdf, but the formatting in Pdf does not match that in Rtf. If rtf have 2 pages and text ‘abcdefghijklmn’ is on page 2 in rtf, after the conversion to Pdf I see the same text in page1 in the pdf file. How can I have the content paging match. Also, some of the font families are not getting converted e.g. Blackadder ITC.

Thank you,
Mahita

Hi Mahita,

Thanks for your inquiry. Please note that Aspose.Words requires TrueType fonts when
rendering documents to fixed-page formats (JPEG, PDF or XPS). Make sure
you have all the Fonts installed on your machine you’re using to convert
Word document to Pdf format. I would suggest you please read the
following articles:
http://www.aspose.com/docs/display/wordsnet/How+Aspose.Words+Uses+True+Type+Fonts
http://www.aspose.com/docs/display/wordsnet/How+to++Specify+True+Type+Fonts+Location

If the problem still remains, please attach your input Word document here for testing. I will investigate the issue on my side and provide you more information.

Thank you. The articles you suggested did explain how to handle the fonts.


However I still have the problem with the content shrinking/overflowing. In my word report I have the text ‘abcdefghijklmnop’ in page 2, however when I use aspose to convert rtf to pdf I see this text in page 1. Please advise how to fix this.

-Mahita

Hi Mahita,

Thanks for your inquiry. Could you please attach your input Word document here for testing? I will investigate the issue on my side and provide you more information.

I attached the word document, the expected alignment and the alignment after conversion to PDF.


Please advise on how to fix the issue.

Thanks,
Mahita

Hi Mahita,

Thanks for sharing the detail. I have tested the scenario and have managed to reproduce the same issue at my side. For the sake of correction, I have logged this problem in our issue tracking system as WORDSNET-12163. I have linked this forum thread to the same issue and you will be notified via this forum thread once this issue is resolved.

We apologize for your inconvenience.

Hi Mahita,

Could you please provide the unprotected
document here for investigation purposes? It is difficult to analyze a
document with restricted editing.

Hi,

I recently got the latest Aspose.Words version 15.9.0.0. Could you please let me know if this version has the fix for the reported issue when converting Rtf to Pdf.

Thanks

Hi Mahita,

Thanks
for your inquiry. Unfortunately, this issue is not resolved yet. We are waiting for unprotected document from your side. Please check my previous post.

Could you please provide the unprotected
document here for investigation purposes? It is difficult to analyze a
document with restricted editing.

Hi,

I attached an unprotected document you can use for debugging purpose (FullDoc.docx). Also, another issue was noticed. A text wrap is see. In attachment wrapping.docx, the third line in the header gets wrapped when the document is converted to PDF. I assume this issue is related to the issue for contents showing in different page. Please correct me if I am wrong.

Thank you,
Mahita

Hi Mahita,

Thanks
for sharing the detail. I have tested the scenario and have managed to
reproduce the same text wrapping issue at my side. For the sake of correction, I have
logged this problem in our issue tracking system as WORDSNET-12544. I
have linked this forum thread to the same issue and you will be notified
via this forum thread once this issue is resolved. We apologize for your inconvenience.

The FullDoc.docx is different from the document which you shared before. I have not found the shared issue posted in your first post while using latest version of Aspose.Words v15.9.0. Please check input document’s screenshot and output Pdf for your kind reference.

The issues you have found earlier (filed as WORDSNET-12544) have been fixed in this Aspose.Words for .NET 17.5 update and this Aspose.Words for Java 17.5 update.


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

The issues you have found earlier (filed as WORDSNET-12163) have been fixed in this Aspose.Words for .NET 19.7 update and this Aspose.Words for Java 19.7 update.