View Single Post
Old 05-29-2025, 09:25 PM   #3841
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,481
Karma: 169115146
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by Solitaire1 View Post
I wonder if a factor in this could be that EPUB ebooks don't have conventional pages like printed books. Please correct me if I'm wrong but I thought that with EPUB each page is a certain number of lines and due to that a "page" could be two/three screens in length (that's been my experience with EPUB ebooks).
If you have a pagemap or a page-list in the ePub with the page numbers matched to a specific paper version or are using the Adobe Synthetic Page Number algorithm, you can get that effect depending on the font size and screen size you are using. For the ASPN algorithm, the count is based on the number of compressed bytes in the individual files inside the .zip container file.

To quote Adobe's ePub Best Practices ebook:
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:
  1. Determine a compressed byte length of each resource which is referenced in the spine, subtracting any known encryption overhead (IV size)
  2. 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
  3. 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.

Last edited by DNSB; 05-29-2025 at 09:27 PM.
DNSB is online now   Reply With Quote