Quote:
Originally Posted by wallcraft
From Producing ePub Documents from InDesign:
I don't think most existing .epub books (or .LIT or .MOBI books, which being OEB-based can do the same thing) have 1 file per chapter, perhaps because most publishers want to target "simple HTML" e-book formats too. I find it surprising that it matters whether chapters are in separate files or not, but perhaps this is an Adobe Digital Editions specific implementation detail.
FBReader can take a few seconds to layout (say) a multi-MB CHM file, but its primary limitation is that loads the entire document into memory. This (presumably) improves speed, but can be a limitation for really long documents. This is on FBReader's list of thinks to fix, but memory is so cheap that I'm not sure this is a big deal - particularly for Linux devices with virtual memory. |
I think ADE treats each XHTML stream as a logical page that is then split up into separate pages depending on font size and screen size. It keeps a single logical page in memory at one time. As a result having a single very long logical page is likely to cause swapping and slow down page turns. The same is true for LRF (except that there it is <Page> elements than should not be too long instead of individual files.
Memory does seem to be a problem when it comes to handhelds as manufactures want to keep prices as low as possible, which often means they skimp on RAM.