In ncx, TOC section scope not included in the parent - no warning or error

[rdeltour]

From vgros00@gmail.com on May 07, 2012 16:43:07

PROBLEM: In toc.ncx, when a TOC section scope (src attribute) is not included in the parent, there is no epubcheck warning or error.

METHOD: for example :

  <navMap>
    <navPoint id="chapter" playOrder="1">
      <navLabel>
        <text>Chapter 1</text>
      </navLabel>
      <content src="chapter.html#first"/>
      <navPoint id="section" playOrder="2">
        <navLabel>
          <text>Section 1</text>
        </navLabel>
        <content src="chapter.html"/>
      </navPoint>
    </navPoint>
  </navMap>

RESULT: No warning or error in epubcheck3.0b5.

EXPECTED: If there is a subsection included in the parent, but src attribute not included in the src parent ==> warning (or error).

PLATFORM: windows 7

Original issue: http://code.google.com/p/epubcheck/issues/detail?id=175

[rdeltour]

From markus.g...@gmail.com on October 11, 2012 14:11:42

Status: Accepted
Labels: Type-Enhancement Priority-Low EPUBVersion-ALL

[jschvartz]

Had the same problem. Kindle refuses to convert ....

[tofi86]

I'm going to schedule this for next epubcheck maintenance release...

[jschvartz]

Thanks Tobias.
Is there an open discussion about checks not purely "Epub compliance", but rather "Device compliance". The goal would be to issue warnings concerning specific devices like:

• images more than 2 million pixels for Ibook
• specific constraints for Kindle
  etc..
  Or is this too far beyond the scope of EpubCheck ?
  Joel

[tofi86]

With epubcheck 3.0.1 we introduced "HINTS" for exactly this purpose.
However, the HINTS implemented so far are only a few and not device/vendor specific. I think I remember a discussion about not implementing vendor specific HINTS since they are hard to maintain...

[DLSieving]

Here we are in late 2016 and the problem has not been fixed.

[DLSieving]

This error occurred for me in one case because the chapters in the body of the book were not in the same order as they were referenced in my custom TOC. Even though I had deselected all TOC auto generation options in Calibre, Kindle Previewer went ahead notwithstanding and attempted to construct its own internal TOC. Finding chapters out of their listed order during this process apparently confused it.

[jimrose38]

This error also occurred when I attempted to upload a Calibre epub file to kdp. The problem was that I had two navPoints titled the same "Epilogue" Not sure how that happened. Was able to delete the first navPoint using Calibre, and the Kindle previewer was happy.

[othmanemoujahid]

To resolve that, should change the type of toc from empty to normal

[rdeltour]

The feature request sounds legit (ping @danielweck @mattgarrish), although given this affect EPUB 2.0.1 this is low priority.

Please upvote this issue (in the opening comment) if you feel it should be prioritized.

[rdeltour]

@vincent-gros I'm not sure if your 👍 is related to the treatment of the issue, or actually an upvote 🤔. For upvoting, please 👍 on the first issue comment! Sorry to not have made this clearer 😊

[vincent-gros]

Both! I will upvote on the first comment, because this can detect a blocker for converting or ingesting EPUB2 in some softwares/platforms. But I also agree with you, this is not high priority because mainly related on EPUB 2.0.1.

(note: I am vgros00@gmail.com, the author of this issue 😄)