Quote:
Originally Posted by eschwartz
 I'd originally thought (due to not carefully reading) that ADE calculated based on characters. I must've glossed over the truth on account of rejecting the sheer stupidity as impossible. (Moral: Never underestimate corporate stupidity  especially not Adobe.) |
It isn't as simple as the link to the section of the wiki would have you believe.
From the
Page Map section of the Wiki.
Quote:
|
Adobe can add a page-map to provide mapping between the hardcopy book page numbers and the eBook. In the absence of a page-map ADE computes an arbitrary page number for each file in the spine using 1024 unicode characters as the page size. The last page in the file contains whatever overflow is needed.
|
Further on in talking about Page Maps (which I know is different from the algorithm for page counts) it says,
Quote:
|
Most if not all of the portable devices supporting ADE use this page number as the eBook page number. Since most eBooks pages are not capable of showing 1024 readable characters on a screen there is usually multiple screens with the same page number. Sony, for example, displays page numbers on the status line that is the ADE number and a sub-number. If the Sony Reader showed 3-7 you see 3 ADE page number and a sub-number of 7 within that main number. The number of available sub-numbers varies since it is a virtual page number based in the screen and font size. Images will also increase the screen number but not the ADE number. The idea of the ADE number is to have a single number that can be referenced like a book reference you sometimes see in academic works so it should not change based on font size or screen size.
|
From using many devices that used ADE over the years I know first hand that the number of pages, when not using a page-map, was never skewed wildly because of images.
I'll let others ponder this further.