Here’s an example of a Word file where we’re seeing text over images and running off the page as well. The examples below can be seen in the aspose PDF file.
1. Text off page - pages 8, 12, and 20
2. Text layered over image - page 358
I’ve provided a link to the original and resulting PDF. We are running Aspose.Words for .NET version 10.0.0
Thanks for your request. The problem occurs because Tight and Through wrapping styles are not supported during rendering yet. I linked your request to the appropriate issues, you will be notified as soon as these features are supported. The four wrapping types now supported cover the majority of user scenarios. Although Tight and Through are used rarely, we are very likely to support them in one of the further versions.
Please see the following link for more information:
Also we decided we are not going to implement the Tight and Through text wrapping options right now. We are postponing these features until we catch up on some other planned features. We will get back to decide on Tight and Through later in 2011.
In additional, it seems you have already reported this problem to us with other your document.
Since support for Tight and/or Through wrapping options is not planned anytime soon, it would help if we could detect the use of these wrapping options and inform our users accordingly. What is the recommended means of detecting whether a document contains an image for which the wrapping type is Tight or Through?
Thanks for your inquiry.
You can use the code below to detect any shapes using these types of wrapping.
foreach (Shape shape in doc.GetChildNodes(NodeType.Shape, true))<?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" />
if (shape.WrapType == WrapType.Tight || shape.WrapType == WrapType.Through)
Console.WriteLine("This type of object wrapping is not currently supported");
Hello, I see that there are more customers that want to have this support in aspose.words. Cant you make some effort and try to fix this. Please.
Thanks for your request. Sure we will fix this problem in future. But currently we had to postpone it because there are a lot of other issues we have to work on.