Quote:
Originally Posted by DaleDe
Saving a few bytes is a poor reason to leave out the toc.ncx file. An ePub features it to be able to bring up the TOC at any time while reading a document. This provides for a ready ability to be able to traverse the document as needed by the reader. This is the dominant reason for adding it. It is not, as you presume just a link to the definition. It is the only method defined by the standard for traversing the document by chapters.
Dale
|
I beg to differ, although I don't have much knowledge of epub yet,it seems to me that an in-document HTML could also contain a toc; and though most readers are able to access the toc.ncx from anywhere within a book,I don't know if ALL readers would support this (they may be compatible with it, but not offer any special toc menus subtracted from the toc.ncx file.
In actuality, I'm planning to create yet another big project, for which saving every bit of memory is going to be needed. Unnecessary references to links get loaded and oft remain in the device's memory.
In a 250kB book this does not make much difference, but in creating a bible with structure, probably could...
I'm planning on creating a bible. If you look up my "bible framework" on mobile read, you'll notice it has well over 3.000 links in it.
I made a KJV bible a few years ago for the Sony Reader (in LRF format).
I made the bible entirely out of a single HTML file. Every book included contains links to chapters, and each chapter contains a link to the toc and previous and next chapter.
The bible I created for the sony, would not function properly on the sony (although it would on a computer), probably because of lack of memory, because of too many hyperlinks.
For that reason I'm keen on trimming as much as possible.
If things go the way I suppose they go, I could choose to get the books defined in toc.ncx, and use in-document hyperlinks.
If I would create every chapter link in the toc.ncx file, that file would well exceed 200kB, and I don't know how any reader would handle that...