Quote:
Originally Posted by JSWolf
But you don't need a contents entry in the NCX file. You can have the internal ToC and the real ToC (NCX) and the NCX does not need to link to the internal ToC. In fact, I feel it should not link to the internal ToC. There's no need for it.
|
Wolfie, dear laddie:
We don't know how the book was built. The easiest way to get it fixed is for the user to rebuild the book's NCX using Sigil. That will solve the spine error, unless something really peculiar is going on. Your
personal preference against inline TOC's isn't really related to the error message problem.
And, lest you forget, the "inline TOC" is basically ePUB3 standard now, so...you may as well sort of bite the bullet and get over it. You'll be seeing more of them, not less of them, as time passes. Ye olden NCX will be going the way of the Dodo.
Hitch