TOC not fully working

[keres]

I'm doing maybe my fifth book with Sigil and am very happy with it. I've run into my first problem. I've constructed the book as usual and am viewing it in Chrome's ePub Reader. The HTML TOC I've generated works, but when I try o to use the table of contents button on the bottom toolbar, the TOC I've generated displays, but when I click on a link to a section in the book I get this message:

The ebook is incomplete and can unfortunately not be opened.

I've tried the various tools, like "prettifying" the HTML. I've generated the TOC with the Tools > Table of Contents > Generate Table of Contents. Then I tried generating it with the ePub3 Tools and not getting anywhere.

Could this be a Chrome ePubReader error?

[KevinH]

Which version of Sigil?
Which platform?
If Windows please make sure any links match case of all characters in filename as some readers are case-sensitive.
Is your epub an epub2 or epub3?
The toc you are referring to, is it the html toc, the epub3 nav, or the epub2 toc.ncx?
Which links are broken?
Does the chrome epub reader support epub3 or only epub2?
Could you be making an epub3 but kept never filled in the ncx from the nav?

[keres]

Thanks so much for the prompty reply.


Which version of Sigil?
1.3.0


Which platform?
Windows 10


If Windows please make sure any links match case of all characters in filename as some readers are case-sensitive.
All filenames are lower case. I'm assuming you're referring to the file toc.ncx


Is your epub an epub2 or epub3?
epub3. This is the first time using it. I was about to just recreate the whole thing using epub2 if I didn't get any other advice.


The toc you are referring to, is it the html toc, the epub3 nav, or the epub2 toc.ncx?
A toc.ncx was generated automatically. There's also a nav.xhtml that cannot be deleted.


Which links are broken?
Any TOC header item brings up the error message.


Does the chrome epub reader support epub3 or only epub2?
I know it supports epub2 just fine. Can't find any information confirming epub3.


Could you be making an epub3 but kept never filled in the ncx from the nav?
No idea how to do that.

[Doitsu]

Originally Posted by keres

Could this be a Chrome ePubReader error?

An epub3 book contains two TOCs, the NAV toc that you generate with the Sigil TOC tool and an optional toc.ncx TOC that some older apps will use.

Try the following:

• Check the book with the IDPF validator or my Sigil plugin.
  
• If it doesn't report any errors, select Tools > Epub3 Tools > Generate NCX/Guide and save the epub.

If the TOC still doesn't work, there's a bug in the app.

[keres]

I took twenty minutes and re-created the book in ePub2. Works fine. I ran the ePub3 version through the first validator you linked to and it came up with errors everytime it found an endnote "a href." The endnotes are all working fine so I'm not feeling the need to fix something that ain't broke. My client is a retired minister so there's not a bottomless pit to finance the effort.

I'm ready to say that Chrome's eBookReader just isn't ready for ePub3.

Thanks for the help!

[AlanHK]

Originally Posted by keres

everytime it found an endnote "a href."

Quote a line of code and the problem might be more obvious.

Originally Posted by keres

I'm ready to say that Chrome's eBookReader just isn't ready for ePub3.

Try Azardi http://azardi.infogridpacific.com/

But what devices/readers is the target user ?

Originally Posted by Doitsu

Check the book with the IDPF validator or my Sigil plugin.

Highly recommend installing the epubcheck plugin. The output links you to the problem text. Google the error message if it isn't obvious and you usually get an explanation.