View Single Post
Old 03-08-2017, 10:40 PM   #33
KevinH
Sigil Developer
KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.
 
Posts: 8,939
Karma: 6361444
Join Date: Nov 2009
Device: many
The epub3 spec is unclear. All throughout the spec they talk as if the navdoc is a required separate xhtml file. No where I could find in the epub 3.01 spec did it say that it could be mixed into a more general xhtml file. That said, I could not find a clear line that the navdoc MUST be the only thing in that file either.

Given the navdoc is machine parsed by reading systems (but still usable for human viewing) I think it would be safest in its own doc with the nav property set in the manifest.
KevinH is online now   Reply With Quote