View Single Post
Old 11-11-2019, 11:36 AM   #19
j.p.s
Grand Sorcerer
j.p.s ought to be getting tired of karma fortunes by now.j.p.s ought to be getting tired of karma fortunes by now.j.p.s ought to be getting tired of karma fortunes by now.j.p.s ought to be getting tired of karma fortunes by now.j.p.s ought to be getting tired of karma fortunes by now.j.p.s ought to be getting tired of karma fortunes by now.j.p.s ought to be getting tired of karma fortunes by now.j.p.s ought to be getting tired of karma fortunes by now.j.p.s ought to be getting tired of karma fortunes by now.j.p.s ought to be getting tired of karma fortunes by now.j.p.s ought to be getting tired of karma fortunes by now.
 
Posts: 5,810
Karma: 103362673
Join Date: Apr 2011
Device: pb360
Quote:
Originally Posted by Tex2002ans View Post
It seems like you're trying to create an absolutely arbitrary numbering that doesn't fit ANY sort of standard, making the fractional numbers even worse than just normal "Real Page Numbers".

If you're going through all this trouble, just stick with RPNs from the physical book.
But I am sticking with and augmenting page numbers from physical books.

All I have done is point out that existing devices will display, in addition to roman numerals and ascii integers, page numbers such as 4.5 (and I assume 13b).

I have not tried to predict characters per screen or anything like that, just inserting anchors with fractional page ids in between the existing anchors with integer page ids, then inserting references to those anchors into either the pagelist section of toc.ncx or the page-map.xml file.

kindlegen will work with either, and kindles handle the resulting book apnx files just fine.

So far, epub devices that I have tried only seem to work with page-map EPUBs, whether fractions are involved or not.
j.p.s is offline   Reply With Quote