Hi, I read the thread about .epub format about memory issues.
Quote:
|
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.
|
I thinking of putting together a master document and had never considered that the idea of one file vs. multiple files might have an impact upon memory and pagination on the device.
I'm guessing that for my source I could use xinclude to combine several xml documents into a single xml file to convert into an ebook (whether as .epub or as a converted binary format). Or I could use a publishing program (like Open Office or In Design) to create a master document and drop several files ("chapters") into the master document. Then the single master document could be converted.
But if there are memory issues, would that be a good reason to split my output into multiple xhtml files?
Apart from memory issues, can you think of any advantages of splitting the output into multiple files?
I personally find the mobipocket GUI program does a pretty horrible job of preserving hyperlinks when you import several html files into a project. The only time I can feel certain the links will work is if the output is a single file, not a group of files. But the .epub discussion seems to imply that reading systems vary in how they read and paginate files deriving from a single file.
Does anyone have that experience with mobipocket also? Hyperlinks are so easy in web browsers; how could the mobipocket creation tool screw it up so often?