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

Free Support Forum - aspose.com

Preserve Shape Position with Anchor Text Wrapping during ODT to HTML Conversion using C# .NET | Small Viewport

Hi, with the latest version of Aspose words for Net (20.8.0 - at the time of writing), when converting an odt file to its html representation the drawn objects are loosing their position when the viewport is smaller than usual (half the screen). It appears that their posititon is not fixed in the html and are wrapping when the viewport gets smaller.

I’ve attached in the archive:

  1. The code I’ve used for conversion
  2. The input file
  3. The generated html.
  4. The image that shows how it looks in a small viewportobjects_drawn_loosing_initial_position_with_small_viewports.zip (75.6 KB)

@arnoldbeilandevozon,

We managed to reproduce this issue on our end and logged it in our bug tracking system with ID WORDSNET-20893. Your thread has also been linked to this issue and you will be notified as soon as it will get resolved in future. Sorry for the inconvenience.

@arnoldbeilandevozon,

Regarding WORDSNET-20893, there are some shapes with different anchor/text wrapping options and it seems everything is fine. Maybe, we have missed something but shape with absolute position have absolute position in the HTML, and shape with relative position have relative position in the HTML. Please see the following screenshots:

So, we need additional information with detailed explanation what is wrong here. The ‘drawn objects are loosing their position’ is unclear. If shape is anchored to the text, it’s the expected behavior. You can change document size to the smaller one and check it in the MS Word. Also, we have tried to export document to the HTML from the MS Word, shape position is the same. If there is another problem, then we need clear and detailed explanation of the expected output.

Also, there the document appear slightly different in MS Word and LibreOffice editor.

So, please elaborate your inquiry further in detail what exactly wrong here or better please provide expected output document showing the desired output here for our reference.

@awais.hafeez thanks for your detailed explanation. With these things in mind it’s clear that it’s a issue on our side, and this can be closed.

Thanks for all the help.

@arnoldbeilandevozon,

It is to inform you that we have completed the work on WORDSNET-20893 and concluded to close this issue with “Not a Bug” status. In case you have further inquiries or may need any help in future, please let us know by posting a new forum thread in Aspose.Words forum.