Quote:
Originally Posted by Julien Pham
And so I guess you write down on a piece of paper the page number you're in? 
As for myself have just an iPhone and a Kobo Touch, but now I have the Kobo I do not read on the iPhone anymore, screen too small ^^
Last time I have to find back where I was in my reading, I just remembered the chapter and a word and I did a search on my Kobo and I found the page I was at this way.
This also means you have to sync your library on all those devices, to be sure to have the book with you when you need so, right?
Perhaps a way to choose the display we want could be helpful then, so people who prefer to know where they are in the chapter can, and when you need an absolute page number you can. Currently the only way I have to know how many pages I need to finish the chapter (useful when I'm going to bed, usually I would like to know if I'm far from chapter end or not) is to go to the chapter list, go to next chapter, look at page number, then come back where I was. Not very convenient. |
No, I do not write it on a piece of paper, remembering a single number is not difficult to do. If I'm reading more than one book at a time (on more than one device), I record the page numbers in Evernote (cloud note syncing service) against the book title and they are now available on all my devices. Your method of remembering a chapter and a word and then doing a search seems longer and open to miss-hits with search as I don't see how you can guarantee the word you choose is the only one in the chapter.
If though I'm only using one device at that time to read a book and am not likely to switch to another device, them as theducks said, there is no need to remember anything as ADE will do all the remembering.
Putting my books on my devices is easy to do with services like Dropbox and Sugarsync, it's not a problem. Being an avid reader, it's handy having my books available to me.
The main problem with page numbering is that no matter what is chosen as the method, it will not please everyone. Having multiple different methods in the same reading system so as to try and cover all possible options is likely to be pretty complex and will in all likelihood slow it down, and I doubt many of the developers will wish to spend the time doing it.