Quote:
Originally Posted by prepbgg
Comparing two toc.ncx files:
A - the one inside the epub file generated by Calibre from my rtf file (which does not work in FBReader on my Android phone)
B - the one inside the Project Gutenberg book which I downloaded (which works in FBReader)
I have noticed that whereas the <navPoint> tags in B have playOrder properties numbered consecutively 1, 2 , 3, ...., those in A have playOrder all set to 0.
Could that be significant?
|
Could be, the one in A is invalid:
playOrder attributes remain required. Although
playOrder attributes are not used to sequence SMIL content, they
should contain valid values that reflect the linear document reading order. This could, for example, be used when one is navigating a pageList to find a corresponding location in the navMap.
... well, as invalid as the strong is the "should".
The relevant part of the NCX spec says:
The playOrder attribute is required on each pageTarget, navTarget and navPoint. It provides a means to collate all pageTargets, navTargets, and navPoints into a single ordered sequence that reflects their order in the normal playback sequence of the book as presented in the spine and SMIL file(s).
playOrder is a positive integer; the first playOrder value in a document shall be 1. When the content elements of any pageTargets, navTargets, or navPoints reference the same SMIL time container, they must have the same playOrder value.
playOrder must increase by one for each unique SMIL time container referenced by any pageTarget, navTarget or navPoint.