View Single Post
Old 09-07-2023, 05:19 PM   #10
DNSB
Bibliophagist
DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.
 
DNSB's Avatar
 
Posts: 47,160
Karma: 169815798
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by JSWolf View Post
Is there any easy way to make a page map that works with RMSDK if you have page number IDs in the ePub?
It should be fairly easy to do automatically if someone wrote a tool but I'm not aware of any existing tools. Checking the few epubs I have around that have page numbers as IDs, they also have pageList entries in the XHTML navigation document and toc.ncx files. Since pageList is a part of the epub recommendation and that 15 years ago, the comment on page-map was "the 'page-map' attribute is not supported in the OPF Package Schema and thus NOT ALLOWED.", implementing page-map is unlikely to be a good idea.

Oddly the epubs that I have the implement pageList tend to flag that portion of the XHTML navigation document as hidden.

Code:
<nav epub:type="page-list" hidden="hidden">
 <ol>
   <li><a href="hurkle.xhtml#page101">101</a></li>
   <li><a href="hurkle.xhtml#page102">102</a></li>
   <li><a href="hurkle.xhtml#page103">103</a></li>
   <li><a href="hurkle.xhtml#page104">104</a></li>
 </ol>
</nav>
DNSB is offline   Reply With Quote