Thread: Aura HD Corrupt database?
View Single Post
Old 01-13-2014, 01:42 AM   #33
DNSB
Bibliophagist
DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.
 
DNSB's Avatar
 
Posts: 47,141
Karma: 169815798
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by Rev. Bob View Post
My read of the spec is that the TOC must contain at least one navPoint element; that is, it cannot be empty. This correlates with the requirement that the depth must be a positive integer; a TOC with only one navPoint element is "flat" by definition and thus has the minimum depth of 1.
Minor disagreement. The .ncx file is required to contain a navMap element. I could find no requirement for navPoint or navLabel elements within the navMap(*). The issue seems to arise if there are no TOC elements -- they are not an absolute requirement -- and several programs I've used with epubs will add a default navPoint/navLabel pointing to the first file but the depth will remain at 0.

* I got this from the Daisy spec where it states that navPoint contains one or more navLabels but does not state that navMap contains one or more navPoints. If it ain't compulsory, it's not required so a <navMap> </navMap> structure would appear to be valid.


Regards,
David

Last edited by DNSB; 01-13-2014 at 02:02 AM. Reason: fat fingers cause typos...
DNSB is online now   Reply With Quote