Quote:
Originally Posted by Toxaris
I would not be beneficial for speed. Turning pages or go to the next chapter will actually be a lot faster for small chapters than for large chapters.
|
I don't know about that...
If I understand it right, It may take a little longer for a device to find a chapter in hundreds of chapters,compared to one in tens. Though the loading time of that chapter may be a bit longer, like you say, but the loading time of consecutive chapters within that chunk should be less.
Meaning, in case of a large book, read in a linear line, one chapter after the other until the end of the book, is better to have larger files containing more chapters within a (~280kB) html; using in-document reference points to chapters.
In case of a bible, concordance, or dictionary, small chapters should be preferred for the sake of faster loading time, and quicker able to find chapters; using the reference point of the beginning of an html page.
I'm torn between using the toc.ncx or a selfmade HTML toc.
The toc.ncx is fast, easy, but adds some code to the book. The HTML might be a little slower to browse around, can be made to look nicer (eg: in 2 columns, or at least away from the stock TOC layout, or something).
But my biggest concern is how an ebook will handle once the TOC.ncx becomes very large (in case of a bible there are over 1100 chapters; a concordance even more,and a dictionary could have as much as 500.000 links (that is, if you want to reference each word)).
In these cases it does make sense to start trimming on the toc file; or have very efficient code!