Aspose.Word.Express Splitting HTML Documents

Aspose.Words Product Family
1

In the settings panel it gives the reason for splitting documents at the various levels in the orginal word document as

This setting is used for EPUB readers which limit the size of any HTML file.

I have found another reason to use this setting which may be worth mentioning. Using various eBook readers on the iPad I found that most ignore page-break-before requests and only give a "new page", i.e. display at the start of the screen if the file is split into separate HTML files at that point.

I also read somewhere that even if the reader can handle a larger file it would be more responsive if the file was split into smaller parts.

It might make sense to expand the explanation of this item.

Is there ever a reason not to split the document at least at level 1?

2

Hi Aidan,


Thanks for your inquiry.

Well, we do provide HtmlSaveOptions.DocumentSplitCriteria property in case you want to specify how document should be split when using Aspose.Words. By default the document is split by HeadingParagraph when saving to EPUB i.e. the document is split into parts at a paragraph formatted using a heading style Heading 1, Heading 2 etc. You can use it together with DocumentSplitHeadingLevel to specify the heading levels (from 1 to the specified level) at which to split.

When it comes to Aspose.Express, I have asked about the possibility of a similar option that can be specified during saving Word documents to EPUB format from our development team. I will update you as soon as I have extra information.

Best Regards,

3

Hi Aidian,


Thanks for communicating your findings here.

You are absolutely right about your above points. As it happens during previous testing I observed the same behavior (EPUB readers ignoring page breaks unless they are split into separate HTML files). You are also correct that splitting the HTML would increase speed on some readers for large files.

I can’t think of any reason not to use the split headings option, I originally disabled it by default I think to avoid any confusion for those who edited the EPUB after manually but I think now it’s actually the reverse and most people actually expect the HTML to be split.

I have an internal issue already logged to change the default of this option to Heading 2. At the same time I will update the description with your suggestions. I have linked your thread to this issue so you will know when it is resolved.

Also note that we have another feature request to split HTML content to ensure max flow, i.e not only split at heading but so the maximum size of any HTML part is 200kb.

Thanks,
4

The issues you have found earlier (filed as ) have been fixed in this update. This message was posted using BugNotificationTool from Downloads module by MuzammilKhan