Quote:
Originally Posted by HarryT
That is actually one benefit of the increasing "standarisation" of reading devices on Adobe Digital Editions (ADE). ADE does have consistent page numbering which is independent of font size and device, so if you refer to page 50 of a particular ePub book, everyone using ADE-based software to read that book will have the same page 50.
|
Only I wouldn't call that "page", but something else, like "fragment", "position", "marker"...
Even if you read a document by scrolling, take your typical webpage in a browser, you have a document with a given width (usually it fits in your window) and a large height. In the window you see only a portion of the total height of the document, and you can move this window (or the document) up and down with a scroll bar. Usually, the scroll bar represents the total 100% length of the document and the scroll button is positioned at the corresponding relative position of the window in the document, and sized also in proportion to the size of the window with respect to the total document length (if the window can show half the document, the button takes half the total scroll bar height).
It would only be beneficial if it were possible to have some numbers measuring this. Call the size of the scroll button "1" (that is, one page). Measure the total length of the scroll bar in button units, that's the total "pages" of the document. Measure the position of the button in the bar in button units as well, that's the current "page". Round it all to integer numbers, and you're done. Sure, these page numbers are not useful for referencing, only for "internal" use by the user while reading a book.