View Single Post
Old 03-08-2023, 05:36 PM   #18
Doitsu
Grand Sorcerer
Doitsu ought to be getting tired of karma fortunes by now.Doitsu ought to be getting tired of karma fortunes by now.Doitsu ought to be getting tired of karma fortunes by now.Doitsu ought to be getting tired of karma fortunes by now.Doitsu ought to be getting tired of karma fortunes by now.Doitsu ought to be getting tired of karma fortunes by now.Doitsu ought to be getting tired of karma fortunes by now.Doitsu ought to be getting tired of karma fortunes by now.Doitsu ought to be getting tired of karma fortunes by now.Doitsu ought to be getting tired of karma fortunes by now.Doitsu ought to be getting tired of karma fortunes by now.
 
Doitsu's Avatar
 
Posts: 5,584
Karma: 22735033
Join Date: Dec 2010
Device: Kindle PW2
According to the EPUB 2.0.1 OPF specs, dtb:depth, dtb:totalPageCount and dtb:maxPageNumber are no longer required. (Only dtb:id is required.) In the previous version, they were still mentioned.

BTW, the Apple Books Asset Guide mentions that Apple Books calculates page numbers for TOC entries:

Quote:
Table of Contents

The main Table of Contents in Apple Books is created using a nav element with an epub:type value of "toc". Readers use the Table of Contents to navigate to key locations in the book. Note that you do not define page numbers for each entry. Apple Books calculates those for the reader to accommodate different font and screen sizes.
(emphasis mine)

Spoiler:
Code:
Code:
<nav epub:type="toc">
    <ol>
      <li><a href="chapter1.xhtml">Chapter 1</a>
         <ol>
          <li><a href="chapter1.xhtml#figure1">Figure 1</a></li>
         </ol>
      </li>
      <li><a href="chapter2.xhtml">Chapter 2</a></li>
    </ol>
</nav>


Maybe Apple uses a similar method for NCX TOCs and their validator doesn't like the order of toc entries in the OP's book because they don't match the spine order.
Doitsu is offline   Reply With Quote