View Single Post
Old 05-31-2022, 10:20 AM   #23
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by Uncle Robin View Post
Allegations to the contrary nothwithstanding, I was not being maliciously or deliberately obtuse. I know nothing at all about how ebooks are structured as files.
Sorry, I wasn't meaning that. I probably should have said "originally suggested".
Quote:
What I DO know is that the stats presented said "44% READ" (e.a.) when that was patently not true. As an indicator of the percentage of the book actually READ (the information it was allegedly presenting), the figure was meaningless to the point of absurdity. THAT is simple fact, regardless of the mechanics of file size, internal structure etc.
'
I've just checked a de-drmd epub in KOReader and its stats match those of the kepubs internal progress bar and the ADE epub - wrong, but not AS wrong as the "% read" figure shown on the 'cover' when sleeping or in the statistics under "Activity". The end matter is 15% of the entire book, not 50%.
That probably means that KOReader has implemented the Adobe method.

The problem is that it isn't hard to construct a book that screws with any of these progress calculations. I've always found a certain persons insistence on the Adobe page counting algorithm as it is extremely easy to mess with (just use a lot of repetition as it is based on the compressed size or change the compression algorithm for one file, but that's cheating). For the kepub method, the percent read is a mix of file size and word count, so messing with that is just as easy. And if there are images, they are not counted unless it is the only thing in the internal file. Throwing in some CSS to put vertical whitespace in some places will mess with it as well.

Personally, I do not remember seeing the percent read out by anywhere near as much as you are reporting. If I calculate it from the pages, then I'm usually within a percent of what the device shows. But, I am reading Any chance of seeing the book that is doing this?
davidfor is offline   Reply With Quote