Quote:
Originally Posted by theducks
RPN only work if everyone is using the same Print Edition.
|
Not necessarily.
Similar to navigating with the Table of Contents (HTML or NCX) or Headings (<h1>-><h6>), some devices/apps can navigate via page numbers as well.
Quote:
Originally Posted by theducks
IMHO Chapter + Paragraph# works better as that does not change depending on text Zoom setting. It still fails on different editions (content edits).
|
At 39:30 of
DAISY's "EPUB Accessiblity 101" video, page numbers get brought up.
For about 5 minutes, they described issues that Libraries/Students/Disability-Services bring up with missing page #s.
The director from Macmillan also mentions chapter/paragraph numbering, and how "most users find that very annoying".
* * *
Side Note: Back in the famous
2016 thread: "Sick of Amazon Kindle books without Page Numbers...", I came up with the terms "Format-specific"/"Format-neutral" ways of citing things:
- Physical book page numbers.
- [...]
- Byte-based "locations" in EPUB/MOBI.
+ listed all the pros/cons.
And in
2019: "Fractional Page Numbering", I described many of the edge-cases:
- "What's a word?"
- "What's a paragraph?"
- "What's a page?"
Side Note #2: In the famous
2017 thread: "Citing Websites", I also showed off EPUB3 page-list + how it shows up in some apps.
(I also described Link Rot + updating the backlist + linked to lots of good stuff too!)
* * *
Anyway, like I said, I've slowly been leaning more towards including RPNs
if possible...
... but there's still a lot of niggling issues there. (Like marking where the actual pages are + trying to keep all Print/Ebook changes in sync.)
RPNs are definitely something that's been gnawing away at me for years... and it might be something I need to tackle at a mass scale soon.