Quote:
Originally Posted by FrustratedReader
I don't care about the fact that it's always shown the the progress for the entire book on the GUI, that's fine.
|
Then why did you make a fuss about this in your posts?
Quote:
It's annotations that are now wrong. They DID show chapter progress. It's called Chapter progress. There is no setting to change it. The so called Chapter Progress IN ANNOTATIONS is now book progress. So barely better than the Kindle PW3 which has far superior text selection.
|
And here you are wrong. I'll repeat is loudly so you can here:
NO FIRMWARE HAS EVER SHOWED PER-CHAPTER PROGRESS FOR WHERE ANNOTATIONS ARE MADE IN EPUBS. NONE. NEVER.
Yes, Kobo displays the word "Chapter" in that place. But, it has NEVER been the percentage in chapter for an epub.
If you truly believe it was different, tell me what firmware version it was, I'll install it on one of my devices and test it. And, as it is so important to you, you can downgrade to that version, and takes some screenshots to show it.
What's wrong? Other than your report of a change in behaviour in this firmware?
Quote:
Stop telling me I'm stupid and excusing Kobo's sloppy testing.
|
I have made this statement to you far to many times, and so far, you have never even tried to do this: If you are going to accuse me of something, please post proof. Post where I have excused Kobo's testing processes.
Quote:
There is a huge difference between explaining how it works and implying "it's always been like that and it's your fault for not using Kobo feedback. So you're stupid for daring to complain."
|
Well that one is a mix of true and BS. Yes, I think if you don't report a problem to Kobo, and expect it to be fixed, then you are being stupid. Especially if it is important to you.
As to complaining, I think I've expressed more displeasure when people don't complain. I want people to report problems. But, I also want the report to include enough detail to understand what the problem is. And be accurate. That way others can reproduce it, and, if possible, come up with a workaround until it does get fixed. I do get a bit tired of the same problem being reported as a newly discovered problem. Especially when it is has already been heavily discussed earlier in the same thread the problem is being reported in.
Of course, the other problem with this statement, is that, in this case, it "always has been like that".