Thread: Aura E2 Paging issue
View Single Post
Old 05-01-2021, 04:42 PM   #2
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: 46,784
Karma: 169712580
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by fabrice91 View Post
Hi,

Since few month, my book pagination has an issue : when I start the book on the first chapter with says 32 pages for example, I'm on page 1/32, then next page is also 1/32 then next is 2/32 then 2/32 then 3/32 etc...It doesn't follow the "natural" pagination 1/32 then 2/32 then 3/32 etc...
This issue is on my Kobo Aura Edition 2 and on the Kobo H2O of my wife.
I use Calibre to deal with my epub books.
I download epub file on Calibre then transfer it to the two Kobo without any filter or transformation.
So does anybody have a clue how to fix this issue ?
Thanx

Fabrice
There is no "fix" for that issue when reading epubs. If you are reading epub books, the page number is calculated using Adobe's Synthetic Page numbering algorithm unless a page map/pagelist is implemented. I don't read many kepubs but at one time, kepubs used a page per screen page numbering but I believe that is no longer quite correct.

To quote from a message I wrote in 2015:

Quote:
Synthetic page names
  • When page map is not available in the document, Adobe Digital Editions will synthesize a page-map based on the document content. The approach used is the following:
  • Determine a compressed byte length of each resource which is referenced in the spine, subtracting any known encryption overhead (IV size).
  • Assume that there is a page for each 1024 bytes in each resource, rounding up to the nearest whole number of pages for each resource.
  • To map page breaks into a resource, use the number of pages for the resource as determined in step 2, count the number of Unicode characters in the resource; distribute synthetic page breaks in the resource evenly between the characters by dividing the number of characters by the number of pages; if the number of characters don’t divide evenly among the pages, round the number of characters per page up and let the last “page” contain less characters than the rest.
I don't pay that much attention to page numbers so this answer may be all wrong. YMMV or should that be YPCMV?
Last edited by DNSB; 05-01-2021 at 04:45 PM.
DNSB is offline   Reply With Quote