Thread: Firmware 4.18.13737 released
View Single Post
Old 10-05-2019, 08:53 PM   #252
JSWolf
Resident Curmudgeon
JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.
 
JSWolf's Avatar
 
Posts: 80,685
Karma: 150249619
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
Quote:
Originally Posted by ratinox View Post
FSVO "correctly".

As I noted previously a few times, ebooks don't have pages which means that the technically most correct way to paginate ebooks is not to paginate them at all.

Adobe page numbers is just another misguided attempt at applying physical book skeuomorphism to things that don't behave like physical books. And they have no correspondance with actual pages anyway. They're just counts of 1000 characters (IIRC) which makes them a lousy way to display percentages because you have to divide by the total "page" count to get something meaningful.

The progress bar shows you useful information in an unobtrusive and more accurate fashion, and percentage displays provide increased accuracy if you really need it.

While I generally dislike change for the sake of change, and I really don't like it when things I come to rely on disappear, I think the new UI is a significant improvement. Remove the faux page numbers entirely and it'll be close to perfect.
Page numbers in a pBook are based on the number of pages. But that's based on how the book is layed out and the size of the pages. The problem is that the same eBook can have a different layout based on the font size, the font, line height, margins, and the size of the screen (or program/app windows). So in order to have page numbers that work across different screen sizes and different layouts for the same eBook, Adobe came up with a solution.

I think Adobe's solution works rather well. Do you have a better idea that works?
JSWolf is offline   Reply With Quote