View Single Post
Old 05-14-2009, 05:20 PM   #44
radius
Lector minore
radius ought to be getting tired of karma fortunes by now.radius ought to be getting tired of karma fortunes by now.radius ought to be getting tired of karma fortunes by now.radius ought to be getting tired of karma fortunes by now.radius ought to be getting tired of karma fortunes by now.radius ought to be getting tired of karma fortunes by now.radius ought to be getting tired of karma fortunes by now.radius ought to be getting tired of karma fortunes by now.radius ought to be getting tired of karma fortunes by now.radius ought to be getting tired of karma fortunes by now.radius ought to be getting tired of karma fortunes by now.
 
radius's Avatar
 
Posts: 660
Karma: 1738720
Join Date: Jan 2008
Device: Aura One, Paperwhite Signature
Just wanted to put my two cents in...

I am going to call a page number based on physical, rendered screenfuls of text physical pages. I am going to use virtual pages to mean those where the page number is calculated, stored etc. and do not have a link to the number of rendered screens.

I want the following things from page numbers:

1) Progress indication - how much of the current book have I read versus how much left to read?
- Tie

2) Navigation - skip ahead/back by a number of pages
- Tie; maybe slight edge to physical numbers

3) Book length comparison - how many pages does this book have compared to that book?
- Physical numbers win as long as I stay on the same device and font but I read on multiple devices in many fonts

4) Portability - I want the same page number to represent the same block of text regardless of the device I am reading on and regardless of the text size I am reading at.
- Virtual wins

So for me, its pretty close, but virtual pages win by a tiny margin for me.
radius is offline   Reply With Quote