View Single Post
Old 10-05-2019, 12:42 AM   #218
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 rashkae View Post
It's quite possible, (I would say likely) that an oversized internal file will cause problems like this. But it's probably not the book size or book whole book progress that causes the problem. I just tested with a 1700000 word book, and the Kobo did not even seem to notice or pause on anything..
My test book is 3407994 words. Kobo says the book in question is 187436K. So an order of magnitude larger.
Quote:
(I was expecting a longer Import on disconnect, since that's where the individual file sizes used to estimate pages would be calculated, but that zipped right by.)
The import doesn't do the word count. It does gets the ToC, and it might check if the file a ToC entry exists, but it doesn't do the word counts. These are done the first time the book is opened. And that can take a while. With previous firmware versions, you could see when it was finished as that was when the page count was displayed in the footer. The timing is a bit different since 4.17.
davidfor is offline   Reply With Quote