Quote:
Originally Posted by arspr
A joint answer to both of them.
Koboish numbering is dynamic, relative, based over your current book layout. ADE/RMSDK is static and absolute based on whatever you want (character count, file size, compressed file size, they are all more or less equivalent).
|
Actually, the ADE/RMSDK algorithm uses the compressed size of the chapter files. Every 1024 bytes of compressed data is one page with any leftovers in a chapter file rounding up to the next page (1024 bytes = 1 page, 1025 bytes=2 pages) with a fudge factor added for DRMed epubs. And I would disagree that character count, file size or compressed file are are more or less equivalent. Depending on the compression algorithm, you can get wide variances in the compression ratio.
An epub with a lot of inline styles will appear to have more pages than an epub with most of the styles in a stylesheet. One public domain cookbook I modified went from 270 pages to 112 pages according to the Adobe algorithm since the original did not have an embedded stylesheet, depending on 200+ lines inside <style></style> tags at the beginning of each recipe/chapter file and two or three <span></span> tags at the beginning of each paragraph.
The only advantage to the ADE/RMSDK page numbering
in my opinion is that it is consistent on identical epubs -- if I am reading a ebook on a Kobo mini, Aura HD, iPad or computer, the same ebook shows the same page numbers. No worries about font size, line spacing, margins, etc.
Regards,
David