Quote:
Originally Posted by JSWolf
The logic to page numbers as they exist is all wrong. If I have a chapter that has 10 screens/pages, when I display the first page of the chapter, I have 10 pages to read. When I get to the last page of the chapter, I have 1 page left to read. So all the page numbers are off by 1 and the last page is 100% off. It's not last page, it's page 1.
So a 10 page chapter should how 10, 9, 8, 7, 6, 5, 4, 3, 2 ,1 and no last page at all and it should not start with an incorrect one page less showing. This shows that the chapter is 9 pages as it is and that the last page doesn't count.
This is a bug that needs to be fixed. It's 10 pages left and not 9 pages left. I am not reading 9 pages in a 10 page chapter. The correct way is to show that the chapter has 10 pages and not 9 pages.
I would think this is a simple fix. Add 1 to the page numbers and dump the last page code.
1)Prioritize fixing any bugs for existing features - SO FIX THE EXISTING PAGE NUMBERS AS IT'S A MAJOR BUG!
|
Hi JSWolf,
Thanks for your detailed explanation and feedback. However, I will break it down based on what we have observed in the industry. The logic you refer to is not used for
Pages Remaining in Chapter but Total Pages in Chapter. They are two different metrics. They can be broken down as:
- Pages Remaining in Chapter
- Total Pages in Chapter
Pages Remaining in Chapter
This simply let the reader know the number of pages left that are not currently displayed or being read.
Simple Example: If you have 10 fruits and you decide to start eating 1 out of 10 of the fruits then what you have
left is
9 fruits remaining.
You cannot say you have 10 fruits remaining while eating 1 of the 10 fruits. The same logic applies to number of pages/screens.
Apple Books and others have implemented Pages Remaining in Chapter in this same manner. Feel free to investigate
Total Pages in Chapter
This will let the user know at all times where they are in reference to the total number of pages/screens in the chapter
Simple Example: If you have 10 fruits and you decide to start eating 1 out of 10 of the fruits. You want to know how much out of the 10 fruits you have already ate or start to eat then you are 1/10 , eat another and you are 2/10
This is the metric you might be use to seeing if you used Marvin, Yomu, Moon+ and others. However Marvin incorrectly used the word
left when using the Total Pages in Chapter metric which could be where the confusion might be if you used Marvin primarily.
What we can do is implement
Total Pages in Chapter as well. Where you can then tap on the section that currently displays
Pages Remaining in Chapter to switch to
Total Pages in Chapter metric.
In summary, our current implementation of
Pages Remaining in Chapter is mathematically correct and is therefore not a bug and so won't update that implementation. However, we are more than willing to add
Total Pages in Chapter to allow readers to toggle to that. Would that work for you?
Does the above explanation helps to clear this up?Is it clear that there are two different and distinct metrics?