Firmware Update 5.16.7 out

[lotre]

Originally Posted by jhowell

[*]Changes related to the handling of page numbers.

Very curious about the changes related to page numbers. Are they only for Amazon books or for send-to-kindle books & side loaded ones as well?

[jhowell]

Originally Posted by lotre

Very curious about the changes related to page numbers. Are they only for Amazon books or for send-to-kindle books & side loaded ones as well?

Sorry, I don’t know. My analysis is mostly looking for new text strings that show up in the latest firmware and there are several new strings in the latest release that relate to page numbering.

[tomsem]

Some folks want to see page numbers the reflect the current pagination of the ebook. Perhaps that is going to be a new option.

[jackm8]

I don't think it would be better. That way page numbers would depend on font size setting. As it's now, they're fairly universal across all reflowable books on the device.

[tomsem]

Originally Posted by jackm8

I don't think it would be better. That way page numbers would depend on font size setting. As it's now, they're fairly universal across all reflowable books on the device.

Yes, of course. I'm not saying it is better, just something some people would like, e.g. they would like to know 'how many page turns to the next chapter?'.

Kindle only has 'nn mins left in chapter', which is a bit too fuzzy to them, even though this doesn't depend on pagination.

[JSWolf]

Originally Posted by tomsem

Yes, of course. I'm not saying it is better, just something some people would like, e.g. they would like to know 'how many page turns to the next chapter?'.

Kindle only has 'nn mins left in chapter', which is a bit too fuzzy to them, even though this doesn't depend on pagination.

And the problem with time left is it varies depending on how fast you read. And even then we don't always read at the same speed. Sometimes I do read faster then others.

[tomsem]

Originally Posted by JSWolf

And the problem with time left is it varies depending on how fast you read. And even then we don't always read at the same speed. Sometimes I do read faster then others.

I think it tries to adjust to reading speed for the particular book in question.

Of the choices there are for indicating progress, it's the one I prefer most of the time. I'm not that concerned about how accurate it is; it gives good idea of how long a chapter is.

[DNSB]

Originally Posted by tomsem

I think it tries to adjust to reading speed for the particular book in question.

Of the choices there are for indicating progress, it's the one I prefer most of the time. I'm not that concerned about how accurate it is; it gives good idea of how long a chapter is.

My personal preference is pages in book/pages in chapter. Reading times on a Kindle, Kobo, Tolino or Pocketbook ereader does not seem to like my reading speed. As an example, when I get to the 45% point in a book after 40 minutes of reading and I am told it's going to take 2.6 hours to finish the book and 11 minutes to finish the chapter, you get rather dubious about the usefulness of the times shown.

[jackm8]

Originally Posted by DNSB

My personal preference is pages in book/pages in chapter. Reading times on a Kindle, Kobo, Tolino or Pocketbook ereader does not seem to like my reading speed. As an example, when I get to the 45% point in a book after 40 minutes of reading and I am told it's going to take 2.6 hours to finish the book and 11 minutes to finish the chapter, you get rather dubious about the usefulness of the times shown.

Maybe the book has blank pages fluff for the last 30%, and your reader detected that? Problem with e-books is that they're not limited by the cost of papers, so they often fling whole essays at the end of the novel, ruining our percentages and read estimations.

[DNSB]

Originally Posted by jackm8

Maybe the book has blank pages fluff for the last 30%, and your reader detected that? Problem with e-books is that they're not limited by the cost of papers, so they often fling whole essays at the end of the novel, ruining our percentages and read estimations.

I doubt that is the problem unless the ereaders I've tested have a lot more artificial intelligence than advertised. From my testing, the problem is that none of the ereaders that I've tested handle reading speeds over ~500WPM well. One of my test books was a self-generated omnibus of the first 13 1632 books so about 2,364,000 words. While it was not happy on some ereaders, on the ones where it worked, the reading speed was still highly inaccurate a million words in.

[tomsem]

I do not expect 'time to read' to be accurate. I don't keep track of it. I still think it is useful. I like to read to the end of chapters and even a rough estimate lets me calibrate my attention span.

[DNSB]

Originally Posted by tomsem

I do not expect 'time to read' to be accurate. I don't keep track of it. I still think it is useful. I like to read to the end of chapters and even a rough estimate lets me calibrate my attention span.

Hmmm... As I wrote, 40 minutes to read 45% the book, 156 minutes to read the remaining 55% and 11 minutes to finish the chapter is not even close to accurate and is not useful to me other than for a cheap laugh.

Looking at my last Kobo Reading Life email, 109 books read totalling 41,314 pages with 153.16 hours spent reading for an average of 4.45 pages/minutes.

[JSWolf]

I prefer to see how many pages left in the chapter. It gives me a lot more accuracy then time left.

[tomsem]

Originally Posted by JSWolf

I prefer to see how many pages left in the chapter. It gives me a lot more accuracy then time left.

Right, but Kindle does not offer that option (regardless of what a 'page' means).

[JSWolf]

Originally Posted by tomsem

Right, but Kindle does not offer that option (regardless of what a 'page' means).

That to me is a drawback especially if I want to know if I can fish the chapter before stopping reading.