Quote:
Originally Posted by rcentros
Yeah, but we know the difference between a 500 page book (novel) and a 200 page book (romance, western, etc.). I've got a nine book series I bought from Kobo. The print length is 2,828 pages (when adding all nine books). The old way Kobo handled KePub page numbering resulted in 2,744 "pages." (So fairly close, not exact, correlation.) Now that same series (in my standard sized font, is 6,946 "pages" (screens)). But if I use the smallest font size it's 1,523 "pages" — the largest font-size produces a "page" count of 82,836. In other words, KePubs "page" count has become completely worthless.
You may be in favor of "divorcing" eBook page counts from paper book page counts, but I'm not. I still read both eBooks and printed books and I like consistency, or at least relative consistency. An arbitrary screen "page" count just isn't going to hack it for me. I'll go a different direction.
|
Stop reading KePub and read ePub. You'll get the page numbers you want. They won't change if you change the font and/or font size. ADE is consistent across different devices running RMSDK. pBooks are not consistent. In your example, one of those books could be a trade PB and the other a mass market PB. The page numbers don't match at all. Different physical size and the text size will be smaller in the mass market edition. Heck, you can have two different mass market books and the text can be of different sizes and thus, the page numbers are worthless when comparing.
But, if I take two completely different ePub and look at the page numbers in RMSDK, I have page numbers that are consistent and you can use them to compare the length of the book.