Some images become very large when converting .doc to .html

A client of ours has provided a test document (attached) which has some issues when it is converted from DOC format to HTML format. The issues concern the placement and size of objects in the output format. I have been able to replicate the issue using Words for .NET 5.2.0. Of greatest concern are the very large images which appear in the bottom of the HTML.

I have tested several workarounds to attempt to get these documents formatted correctly in the HTML output, but so far haven’t had much luck. I’m honestly not too familiar with Aspose.Words, but I haven’t found anything specifically mentioning that the things the client is doing are unsupported. Any assistance, workarounds, or resolutions will be greatly appreciated. Also, we’re currently in the process of downloading 5.2.1 to see if that addresses any of the formatting issues, so if you see anything which may be fixed in that release then let us know and we’ll keep an eye out during testing.

Let me know if there’s any more information you need.


Thank you for your inquiry.
Conversion to HTML has some restrictions. The main problem is that floating contents are not supported. This is a known issue #4488 in our defect database. Due to this reason floating shapes are not properly positioned: they are output as if they were inline. Images that become very large belong to a canvas in the source document. Canvases have coordinate systems different from what used for top-level shapes that is not taken in consideration. I expect this problem is a part of #4488 too. This feature is quite complicated and won’t be addressed in the nearest future.
Another problem is that shapes are not exported to HTML. For instance ellipses are numbered as 1, 2, 3, 4 but we see only digits in HTML. This is a known issue #1146 and it also won’t be fixed soon.
You can gather some information about what is supported by HTML export in this spreadsheet:
Please let me know if the documents you need to convert can be refactored (edited manually). If so we can find workarounds for your customer.

Thanks, Viktor! That response is just what I needed. I’ll follow up with the client and post again if they require anything else.

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

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

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