View Single Post
Old 04-07-2008, 09:53 AM   #16
tompe
Grand Sorcerer
tompe ought to be getting tired of karma fortunes by now.tompe ought to be getting tired of karma fortunes by now.tompe ought to be getting tired of karma fortunes by now.tompe ought to be getting tired of karma fortunes by now.tompe ought to be getting tired of karma fortunes by now.tompe ought to be getting tired of karma fortunes by now.tompe ought to be getting tired of karma fortunes by now.tompe ought to be getting tired of karma fortunes by now.tompe ought to be getting tired of karma fortunes by now.tompe ought to be getting tired of karma fortunes by now.tompe ought to be getting tired of karma fortunes by now.
 
Posts: 7,452
Karma: 7185064
Join Date: Oct 2007
Location: Linköpng, Sweden
Device: Kindle Voyage, Nexus 5, Kindle PW
Quote:
Originally Posted by HarryT View Post
I think that to say it's "totally inaccurate" is putting it a little strongly. It seems to routinely have an error of about a dozen pages, but that's an absolute error, not a relative one. eg if you jump, say, 80% of the way through a book, you'll end up within about a dozen pages of the "true" 80% point. That's good enough for many purposes.
How do you know that. I think you are guessing. I now tested to page forward 100 pages from the beginning and then jump 100 pages. The error was 33 pages. Paging forward 50 pages gave an error of 15 pages. This does not seem to be an absolute error to me.

So how did you do the experiments that let you claim what you claimed?

But as I have said before this is pretty uninteresting if you want to know how long a text is and how much you have read of it. It is easy to implement this functionality. You only have to count characters and the make sure you only count displayed characters if you have an html file but that is not hard. I assume that is how the Kindle solve these problems.
tompe is offline   Reply With Quote