Page remaining bug

[JSWolf]

Originally Posted by Jellby

On the other hand, the last page of the chapter may be just 4-5 lines long, and the first page probably has a title that takes that much space. So over all, the count might be even more correct than if you add 1

I remove all that excess space for chapter titles. And the last page of the chapter does vary from one line to almost a full page, But it's still a page ad it still counts.

[JSWolf]

I downloaded the latest nightly and I cannot find Footer: add "Include current page in pages left" setting (#8093) as an option. I'm probably missing something.

[Frenzie]

It's on page 2 of settings (gear) → status bar → settings. Pages in the menus are something we generally try to avoid.

[JSWolf]

Originally Posted by Frenzie

It's on page 2 of settings (gear) → status bar → settings. Pages in the menus are something we generally try to avoid.

Thank you. It works very well.

[LittleBiG]

Actually the solution without the new option was absolutely okay. What you actually wanted was the "Page turns left" until the next chapter. So this naming about including the current page into the page left is just simply imperfect. True, but not logical.

Summarized in one sentence: when you are on the last page, there is no more page (0) until the next chapter, but still you have to turn page once (1) to reach it.

[JSWolf]

Originally Posted by LittleBiG

Actually the solution without the new option was absolutely okay. What you actually wanted was the "Page turns left" until the next chapter. So this naming about including the current page into the page left is just simply imperfect. True, but not logical.

Summarized in one sentence: when you are on the last page, there is no more page (0) until the next chapter, but still you have to turn page once (1) to reach it.

The solution without the new option was not OK. Every update lost the solution and it had to be put back.

The way I look at it, when I start a chapter that has say 16 pages, I have 16 pages to read until the next chapter. I don't have 15pages. When I am on the last page of the chapter, I have 1 page left to read.

The same goes for the number of pages in the book. The last page is not page 0 because that means I have no more pages left to read. But I do, I have 1 page left to read.

But whatever you think, you can have it your way now and that's very good.

[Quoth]

I think the pages left should = 0 when you are on the last page of a chapter because that shouldn't include the current page.

You do not have more pages to read when you are reading the last page. Pages left are the pages not yet turned to!

| | | |

How many matches and spaces?

On a paper book if there are 342 pages and you are on page 341 are there two pages left or one? You subtract current page from number of pages because you already see current page even if you have not started reading it. And how is the ereader software to know if you have read the entire page and thinking about it before turning the page?

[LittleBiG]

Originally Posted by Quoth

I

| | | |

How many matches and spaces?

Indeed! We had to learn this early in school, we got the example with fence and fence posts. I am really happy that somebody other than me still remembers.

[JSWolf]

Originally Posted by Quoth

I think the pages left should = 0 when you are on the last page of a chapter because that shouldn't include the current page.

You do not have more pages to read when you are reading the last page. Pages left are the pages not yet turned to!

| | | |

How many matches and spaces?

On a paper book if there are 342 pages and you are on page 341 are there two pages left or one? You subtract current page from number of pages because you already see current page even if you have not started reading it. And how is the ereader software to know if you have read the entire page and thinking about it before turning the page?

With a pBook of 342 pages and you turn the page and are now at 341, you have two pages to read. So if I am on the last page of a chapter, I have 1 page left to read before I move on to the next chapter/section/end the book. I also have 1 page left to turn to move on from the end of the chapter.

If the chapter has 16 pages, when I am on the first page of the chapter, I know I have 16 pages to read. If thelast page of the chapter was to show as 0, I would see 15 at the start of the chapter and unless I remembered to do the math, I would be off by one page.

[rkomar]

Originally Posted by JSWolf

With a pBook of 342 pages and you turn the page and are now at 341, you have two pages to read. So if I am on the last page of a chapter, I have 1 page left to read before I move on to the next chapter/section/end the book. I also have 1 page left to turn to move on from the end of the chapter.

If the chapter has 16 pages, when I am on the first page of the chapter, I know I have 16 pages to read. If thelast page of the chapter was to show as 0, I would see 15 at the start of the chapter and unless I remembered to do the math, I would be off by one page.

It just comes down to whether or not you include the current page in the total number remaining. I don't think you can say either choice is wrong. If koreader picks one side, then it's probably best to just accept that.

If you want to stick with your reasoning, then you should probably start numbering pages at 0, because you haven't read anything yet at the start of that page.

[Frenzie]

Originally Posted by rkomar

If you want to stick with your reasoning, then you should probably start numbering pages at 0, because you haven't read anything yet at the start of that page.

I believe I wrote the same thing almost word for word.

But the setting is there now, so everyone can relax.

[mergen3107]

I also love this new option! Thank you guys!

I am going to add a Wiki article regarding this option to make things (hopefully) clear. I'll summarize my thoughts here from both perspectives. Please let me know if you think something is off in my reasoning.

I think all this polemic stems from the fact that there are actually two different perspectives on how to interpret "pages left" in a chapter/book. They both are fine within their own context and both definitely have a right to exist, and here is why.

1) Reader's perspective (when the new checkbox is ON).
In this perspective, on any given page the question is "How many pages are left to actually read to finish this chapter?". In other words, the "count" starts at the beginning of a current page.

Edges cases:
- You are on the 1/n page of a chapter. "Pages left" shows n.

- After (n-1) page turns, you are on the n/n page of a chapter. "Pages left" shows 1. So you are going to actually read one more page (this last one) before the chapter ends.


2) Code/rendering perspective (when the new checkbox is OFF).
In this perspective, on any given page the question is "How many pages are left to render to finish this chapter?". In other words, the "count" starts at the beginning of a next page.

Edges cases:
- You are on the 1/n page of a chapter. "Pages left" shows (n-1).

- After (n-1) page turns, you are on the n/n page of a chapter. "Pages left" shows 0, because there are no more pages to render that belong to current chapter.


In both cases, the respective sum of pages is consistent in their respective context, and I think there is no need to start counting from 0 in any case:
- In Reader's perspective, on the 1/n page, no pages are actually read (0), and there are "n" to go. So, 0+n = n.
- In Rendering perspective, on the 1/n page, 1 page is already rendered (1), and there are "(n-1)" to go. So, 1 + (n-1) = n.

[Frenzie]

I'd talk about n a lot less and call it something like text vs page-based perspective.

E.g., not:

You are on the 1/n page of a chapter. "Pages left" shows n.

But:

You're on the last page of a chapter. "Pages left" shows 1.

Also it's probably a lot less confusing to talk about paper books than to involve computer terminology like code and rendering. Do you still have to flip a page or not?

As an aside, the final page often looks a little something like in my attachment.

[Jellby]

Would there be any interest in implementing/using a "chapterbar" like I had in e.g. Gulliver's Travels?

The idea would be an additional progress bar above or below the main progress bar, that shows only the pages in the current chapter, but with visible page boundaries, like a row of little boxes, one per page. Ideally all pages would be the same size, so short chapter would have short bars, long chapters longer bars (hoping that there are not many 100+ page chapters). Then one could use different shades for previous pages, current page, and following pages, and let the user do the counting, I think it could be intuitive for everyone.

So if you're currently on page 7 out of 10 in the chapter, it could look something like:

[#|#|#|#|#|#|o| | | ]

[NiLuJe]

@Jellby: I'm not an "always-on" kind of person for the status bar, but this sounds fun, mildly useful, and not too gnarly to write .