Free Support Forum - aspose.com

When saving RTF to PDF- header information is incorrect

When I attempt to convert an RTF to PDF using the newer method of word.SaveAs(pdfFile) i’m noticing the header information in the PDF is not the same as in the original RTF. Both files are attached.

Hi

<?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" />

Thanks for your request. The problem occurs because there is a text frame in your Header. Currently Aspose.Words does not fully support positioning of text frames upon rendering. Your request has been linked to the appropriate issue. You will be notified as soon as this feature is supported.

As a workaround, you can try avoiding using text frames in your document.

In addition, you should note that text frames are obsolete and are not used very often. You can use TextBoxes instead of frames.

Best regards.

Thanks for the quick response. Fortunately, these are documents that we generate in house so I will be able to modify the header to use text boxes going forward.

It is perfect that you can change your document. Please let me know if you need help with refactoring your document, I will be glad to help you.

<?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" />

Best regards.

Actually another related question. I had originally used the old conversion method of using both Word and PDF toolkits to and had no issues converting this type of RTF. With the newer version of the libraries, it appears the header and footer are missing altogether. PDF file attached. Is this intentional?

Hi

<?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" />

Thanks for your inquiry. No, this is not intentional. However, you should note that any issues in Old conversion method will not be fixed. So, you should use new method.

Best regards.

The issues you have found earlier (filed as 8182) have been fixed in this update.


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

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


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