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

Free Support Forum - aspose.com



Lorsque j'ajoute un filigrane à un document Word la onvertion en PDF ne reproduit pas exactement le document.

Dim mDocument As New Aspose.Words.Document("c:\test.doc")



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

Thanks for your request. I managed to reproduce these problems on my side. This problem occurs because Aspose.Words does not support floating images positioning during rendering. As a workaround, you can try refactoring your document to avoid using floating images.

Also in the next version positioning of floating content upon rendering should be better supported so hopefully the content will be laid out well. We will inform you when this fix is ready.

Best regards,

We are happy to tell you that a very cool and important feature (filed as 7180) is included in the new version of Aspose.Words. Text wrapping around images and shapes when rendering Microsoft Word documents to PDF, XPS and printing is now supported. You can download the latest version from here.

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


J'ai fait le test avec cette nouvelle version, le filigrane semble correct par contre la mise en page ne l'est pas. Le numéro de page 2 se retrouve en milieu de page.

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

Thank you for additional information. The problem occurs because page number is inside 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,

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.