Quote:
Originally Posted by eschwartz
I rather thought my whole point was that they aren't consistent on account of some books use Real Page Numbers and some use a set number of characters.
|
But, we aren't comparing the page numbering between two different books. We are comparing the page numbering between the same edition of a book on different epub reading devices or apps. In this case, whether they are Real Page Numbers (I feel like I need a trademark symbol after that) or Adobe generated page numbers doesn't matter as the reading device/app should handle this. i.e. if the page map is available, use it otherwise generate the numbers. If this is done, it doesn't matter which type of page number is being used because it will be consistent across all device/apps for a particular edition of a book.
Quote:
This is completely ignoring the Kobo, which apparently uses 1 screen == 1 page, at least some of the time.
"Some of the time" -- even worse than just having one device which consistently goes against the EPUB grain. 
|
But, we are talking about two different formats. Kobo supports two primary flowable formats. ePubs are handled by an RMSDK. This follows the page numbering rules of all other RMSDK based devices and apps.
Kobo's own format, "Kobo epubs" or kepubs, are handled by a different reader application on the device. This has the ability to do pages per chapter where each page is a screen and will be renumbered if you change the presentation (font, size, borders, line spacing, justification). It also has an option to use full book page numbering. In this case, a page is not a screen. I don't know if they are using the Adobe algorithm or something else. If they are using the Adobe algorithm, the page numbers can't be compared as a kepub has extra tags in them making them a different size and hence the Adobe algorithm would calculate different page numbers.