For me, a page is a measurement of a certain amount of lines of a certain width on a surface.
Pageless (for me) would mean that either the width or the height of the surface is larger than I can easily oversee. So, if you read a book, while scrolling (instead of "page turning"), I'd say you're reading a pageless text. If you use the "page turning" functions, aka, refreshing the entire surface with new content, you're reading pages.
The problem with the current readers (and I do find all readers have this problem) is that a "page" is either hard-coded (ex: epub or PDF) or calculated (ex: mobi). The first scenario is fine if everybody would read from a screen with exactly the same size, with exactly the same font-size, the second scenario is just never really done right (I even think it's almost impossible to do it correctly). I still prefer the second scenario as it does give me some sort of progress bar. Those page numbers from the ADE implementation never made any sense to me...
For me, the perfect ereading software wouldn't show page numbers, but rather progress in the book. This is independent of font-size or page-size.
|