Register Guidelines E-Books Today's Posts Search

Go Back   MobileRead Forums > E-Book Formats > ePub

Notices

Reply
 
Thread Tools Search this Thread
Old 02-20-2010, 03:33 PM   #16
jimad
Connoisseur
jimad is on a distinguished road
 
Posts: 53
Karma: 52
Join Date: Apr 2008
Device: Kindle
Sorry, but this is what I think I've been able to figure out about this subject:

Both Epub and Mobi files can be generated using the set OPF files and by following their specs. Those specs say that NCX (section navigation) and TOC (Table of Contents) are not the same thing.

http://www.openebook.org/2007/opf/OP...inal_spec.html

EPUB as implemented for ADE (Adobe Digital Editions) uses NCX by default to navigate the document. If you also include a TOC then ADE will display two navigation structures, one simpler cleaner one representing the TOC and a more in-depth messier one for NCX. Since most implementers think it looks like a mistake to display two navigational structures within ADE, most EPUB implementors simply implement NCX and leave out the TOC.

Kindle instead by default uses TOC to navigate the document. Kindle specs for MOBI say "you must have a TOC" meaning NCX is optional. On a Kindle if you push the "TOC" button what you see is TOC not NCX. NCX, if present, is supposed to implement right-click left-click "fast forward" and "fast reverse" to next section, NOT TOC.

Now, I have not been able to get Kindlegen to correctly do the "fast forward" "fast reverse" thing via NCX, so maybe THAT aspect is broken in Kindlegen.

However, I CAN get Kindlegen to expressly implement TOC if I expressly implement TOC in the OPF Files. For example, I can take an EPUB document -- which is simply a zipped version of the OPF file set, add a TOC where a TOC clearly didn't exist previously, compile that OPF set using Kindlegen's option to build from OPF, and the TOC works correctly.

What I suggest Calibre does on EPUB to MOBI conversion is to understand the difference in the conventions used by the EPUB vs MOBI "communities" when implementing the OPF specs and automagically converts the EPUB NCX structure to a OPF TOC. This "works" but gives an "ugly" TOC -- one that has more detail than one would typically expect in a hand-written TOC.

One can manually add a TOC to an existing EPUB (unzipped to OPF file set) or perhaps what is easier one can add a single ref TOC which simply points to the TOC presumably already implemented within the doc files. Then when you push the TOC button on Kindle you get a page displayed with a single link "Table of Contents" you click on that link and it takes you to the TOC embedded within the document.

Unfortunately, most people have a hard time accepting that EPUB and MOBI can implement and expect slightly different versions of the same OPF spec!
jimad is offline   Reply With Quote
Old 02-20-2010, 03:41 PM   #17
jimad
Connoisseur
jimad is on a distinguished road
 
Posts: 53
Karma: 52
Join Date: Apr 2008
Device: Kindle
PS: Search this Kindle document repeatedly on "Table of Contents" for a somewhat obtuse and confusing discussion of the difference between NCX and TOC -- "TOC" which this document refers to as "HTML TOC." The OPF specs also confuse this issue by unfortunately choosing the arbitrary name "toc" for their ncx example files!

http://s3.amazonaws.com/kindlegen/Am...elinesV1.3.pdf
jimad is offline   Reply With Quote
Advert
Old 02-20-2010, 06:32 PM   #18
charleski
Wizard
charleski ought to be getting tired of karma fortunes by now.charleski ought to be getting tired of karma fortunes by now.charleski ought to be getting tired of karma fortunes by now.charleski ought to be getting tired of karma fortunes by now.charleski ought to be getting tired of karma fortunes by now.charleski ought to be getting tired of karma fortunes by now.charleski ought to be getting tired of karma fortunes by now.charleski ought to be getting tired of karma fortunes by now.charleski ought to be getting tired of karma fortunes by now.charleski ought to be getting tired of karma fortunes by now.charleski ought to be getting tired of karma fortunes by now.
 
Posts: 1,196
Karma: 1281258
Join Date: Sep 2009
Device: PRS-505
Quote:
Originally Posted by jimad View Post
What I suggest Calibre does on EPUB to MOBI conversion is to understand the difference in the conventions used by the EPUB vs MOBI "communities" when implementing the OPF specs and automagically converts the EPUB NCX structure to a OPF TOC. This "works" but gives an "ugly" TOC -- one that has more detail than one would typically expect in a hand-written TOC.
This is largely because publishers are incorporating too much in their NCX to start with. There's no reason to have separate navigation entities for the title page, dedication, copyright page and all the other fluff that makes up the front matter. It's just bad practice on the part of the person creating the ePub.

When the Amazon doc tries telling people "It is generally a good idea to place an HTML page with a table of contents at the beginning of the book" I just despair -NO NO NO.

Last edited by charleski; 02-20-2010 at 06:35 PM.
charleski is offline   Reply With Quote
Old 09-29-2010, 12:46 PM   #19
pccsoares
Junior Member
pccsoares began at the beginning.
 
Posts: 2
Karma: 10
Join Date: Sep 2010
Device: Kindle 3
I managed to get the "articles list" option enabled from an ebook compiled with KindleGen.

All I had to do was changing the OPF to include de tag:

<x-metadata><output encoding="utf-8" content-type="application/x-mobipocket-subscription-magazine"></output></x-metadata></metadata>
pccsoares is offline   Reply With Quote
Reply


Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
mobi conversion - kindle chapter marker issues foghat Calibre 10 09-29-2010 07:46 PM
To MOBI, Chapter detection fails? Works for EPUB Fmstrat Calibre 7 08-29-2010 05:37 PM
ePub to Mobi Conversion Quality Logiedan Calibre 8 08-17-2010 04:02 PM
Epub to Mobi conversion MichaelGray Calibre 2 08-12-2010 01:08 PM
Conversion to Mobi to ePub errors erik_reader Conversion 5 08-07-2010 02:03 AM


All times are GMT -4. The time now is 10:02 PM.


MobileRead.com is a privately owned, operated and funded community.