View Single Post
Old 07-02-2024, 07:13 PM   #7
oston
Connoisseur
oston ought to be getting tired of karma fortunes by now.oston ought to be getting tired of karma fortunes by now.oston ought to be getting tired of karma fortunes by now.oston ought to be getting tired of karma fortunes by now.oston ought to be getting tired of karma fortunes by now.oston ought to be getting tired of karma fortunes by now.oston ought to be getting tired of karma fortunes by now.oston ought to be getting tired of karma fortunes by now.oston ought to be getting tired of karma fortunes by now.oston ought to be getting tired of karma fortunes by now.oston ought to be getting tired of karma fortunes by now.
 
Posts: 81
Karma: 2138296
Join Date: Nov 2016
Device: ipad, Kindle Scribe, Kobo Libra 2
Quote:
Originally Posted by KevinH View Post
....

2. remove the nav entry from the spine completely. But this generates an error since the nav can only link to things in the spine, and the nav internally links to itself. So you must remove the internal link in the nav.xhtml to itself on the nav landmarks.
Many thanks, indeed, for this really helpful reply.

Where does the Option 2 generate an error?

After posting my question, I tried this option just deleting the nav iten from the spine. After re-running epubcheck, I got No Problems Found when I ran epubcheck!.

Another option might be to just ignore that error. I think we did that for another book recently and the publisher was able to upload it to Amazon.

Many thanks for all this help Kevin.
Jim
oston is offline   Reply With Quote