Thank you for clarification. I see the problem. If you don’t control input documents we cannot fully avoid issues with them. Here is a spreadsheet showing level of import and export to HTML and PDF (link below). But it states only that something is supported or partially supported with minimum details. We plan to improve this part of documentation in the future. The better way is experimenting with real documents and discussing particular differences here in the forum.
We maintain defect database internally. These numbers are the issue identifiers. We usually provide information on particular issues but we cannot grant access to this database. Some information is internal there or lacks user friendly manner. It would be difficult to maintain publicly accessible database. So it’s better to ask support people to get relevant information.
#3701 has high priority (major) since we have collected many requests on these list labels. Currently Aspose.Words relies on HTML ordered lists and only the last level number appears in list items. So “1.2.3.” becomes simply “3.” Hopefully we’ll get right with it up to the end of 2008. The idea is outputting list another way or parameterization of these approaches. All this should be also properly round-tripped (DOC->HTML->DOC).
#4488 is less priority issue (minor). Floating contents are not typical for HTML though they can be utilized. But it seemingly requires much effort. So I cannot expect any timeframes even for myself.
If you plan using Aspose.Words in OEM then we can also help with issues/documents coming from your customers. We consider all reported cases and think about improvements.