Quote:
Originally Posted by pazos
I don't have a Kobo since 2017 but IIRC the RMSDK shows the same kind of "real pages" like KOReader does (see attachment)
The only difference is that KOReader follows the spec and thus require a proper epub(3) that features that and Adobe does its nasty magic on all kind of epubs.
|
RMSDK uses Adobe synthetic page-map algorithm if a page-list or pagemap is not present.
- 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 compressed 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.
If you happen to have a Base64 encoded image, it will do terrible things to the page count.
If the ebook does not have a physical edition but does have a pagemap or page-list, it does cause a certain degree of curiosity as to where those number come from.