View Single Post
Old 10-11-2012, 10:15 PM   #2
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 28,605
Karma: 204624552
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
I'm not sure if there's anything special about configuring a fallback ncx in epub3, but regardless ... I can't imagine that the ncx would be listed as an itemref in the spine—linear or no.

I'm pretty sure a fallback ncx is handled just like an ncx in epub2 --

In the manifest:
<item id="ncx" href="toc.ncx" media-type="application/x-dtbncx+xml"/>

and the spine:
<spine toc="ncx">
<itemref idref="cover" linear="no"/>
<itemref idref="book" linear="yes"/>
<itemref idref="toc" linear="no"/>
</spine>
DiapDealer is offline   Reply With Quote