View Single Post
Old 09-21-2013, 09:31 PM   #95
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 Nightyume View Post
Honestly, one reason for this is that it's less demanding. Since the device only has to worry about processing the data and rendering for a single chapter it reacts a lot faster (quite evident when doing things like changing font sizes). With epubs it basically treats the entire book as a single chapter making reaction times somewhat slower (but switching chapters is faster). Plus with kepubs you still get a xx% done, which refers to your progress in the whole book and not the chapter.
I don't think it does that. See https://wiki.mobileread.com/wiki/Adob...s#Page_numbers for how the page numbers are calculated. There is no need to render the complete book using that algorithm. From my experience, the time taken after changing the font settings is dependent on how big the chapter is, not the size of the book. And I don't see much difference between epubs and kepubs.
davidfor is offline   Reply With Quote