I'm currently evaluating Aspose.Words Express 1.1 as part of an ebook publication workflow, converting DOCX to ePUB. Let me first congratulate you to your fine piece of software. It is one of the few converters to produce XHMTL-compliant ePUB files. Most other converter's don't do that, and therefore their output does not validate.
I've stumbled upon a few minor issues though, that I'd like to share with you.
a) As part of the conversion process, Aspose.Words Express creates a table of contents, derived from the document structure. Additionally, it (sometimes?) creates an extra TOC element pointing to the first page, using the DOCX's metadata title. When the DOCX's metadata title contains non-ASCII characters, they are ommitted when creating that TOC entry. Non-ASCII characters in all other TOC entries are fine.
b) Some of the ePUBs created were missing the and metatags, while others have them. I have yet to find a pattern when that happens.
c) ePUB htmls should be split into multiple parts whenever possible, because this greatly improves the percieved speed of eReaders. This does, however create "page breaks" in most eBook readers, so it has an effect on the layout. Is there any chance for the ePUB conversion process to use the DOCX's paragraph format info and manual page-breaks to determine where a split (and thus: page-break) would reflect the layout of the DOCX?
d) Some of the XHMTL files contain useless "..." tags. I have not found a pattern when those appear. It's not a big deal, and they do not have any effect on the result, but I'm still wondering why those exist.
e) Is there any chance for Aspose.Words Express to save its settings?
Thank you for offering this amazing converter for free. Even with those issues it is far better than anything else I've tested.