Quote:
Originally Posted by skillachie
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? |
I get it that you don't understand. Take a pBook. Lets say there is a total of 50 pages, The first page you start reading is page 1 and the last page you read is page 50. The last page of a pBook is labeled as last page. So if you go to the last page of a pBook, you see how many pages there are.
In this case, I have a chapter that has 8 pages/screens. I do not have 7 as is shown. I have 8. The fruit analogy is wrong. 8 shows how many pages I have. I eat one fruit, and it's gone. I read one page and that page is still exists even if I've turned the page. When I am on the first page, I have 8 pages. When I am on the 2nd page of the chapter, I have 7 pages. Please understand this and fix it. What you could do is make it an option to have it so it displays the pages correctly and your incorrect way. When we turn the page to a new chapter, we should be seeing the exact number of pages we have to read to finish the chapter and not have it off by 1.
When I brought the very same issue up with Marvin, it was fixed.