I've used Sigil 1.9.20 to update a couple of links in the back-matter of an epub (originally prepared in an earlier version of Sigil). I also moved a page from front-matter into the back-matter and changed the order of two files at the front. I amended the html contents and edited the ncx table of contents using Sigil Tools>Table of Contents>Edit. All checked out ok with epubcheck (v. 5).
This book had been published wide for several years. When I uploaded the new version to D2D, they got a rejection from Apple (only) with hints that there was something wrong with the table of contents.
After the second iteration of checks, rechecks and passing epubcheck with no fault found each time, the third Apple rejection contained some additional info ...
Quote:
Incomplete/Inaccurate app generated Table of Contents.
The Table of Contents navigates to incorrect sections. Please make sure it navigates to the exact section indicated in the title.
Table of Contents is not correctly implemented. For example, Chapter 13 has page 159 listed in the Table of Contents but it is on page 160 in the book. Introduction is on page 13, not page 12 as listed in the Table of Contents, etc.. Please check and fix each Table of Contents entry that requires a change.
|
From this, it appears that Apple's app used for checking the book's epub file has generated its table of contents and does not like the result.
My file is a reflowable EPUB2 and has never had any page numbers assigned by me or Sigil. In fact the toc.ncx has the only two references to the word 'page' in the book and I would interpret that as an indication that there is no page numbering :
Code:
<meta name="dtb:totalPageCount" content="0"/>
<meta name="dtb:maxPageNumber" content="0"/>
How did Apple's app manage to produce page numbers? Any suggestions on what I can do to correct this and eliminate their objection?