View Single Post
Old 05-22-2020, 08:24 PM   #31
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,105
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
With RMSDK, this index could be made as it uses page numbers that do not change when any settings change.
Jon, how are you planning on generating those page numbers since they will have to be generated from the final epub? Remember that making changes to a file in the epub can cause the page numbers to change.

To quote from Adobe's documentation:
  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.
DNSB is offline   Reply With Quote