View Single Post
Old 02-21-2013, 05:22 PM   #24
guma
Connoisseur
guma ought to be getting tired of karma fortunes by now.guma ought to be getting tired of karma fortunes by now.guma ought to be getting tired of karma fortunes by now.guma ought to be getting tired of karma fortunes by now.guma ought to be getting tired of karma fortunes by now.guma ought to be getting tired of karma fortunes by now.guma ought to be getting tired of karma fortunes by now.guma ought to be getting tired of karma fortunes by now.guma ought to be getting tired of karma fortunes by now.guma ought to be getting tired of karma fortunes by now.guma ought to be getting tired of karma fortunes by now.
 
Posts: 93
Karma: 473808
Join Date: Jul 2012
Device: kobo touch
Quote:
Originally Posted by PeterT View Post
If only it was that simple. Remember, that in order to do that, the eBook reader would have to process the entire book using the current settings, decompressing each and every compressed element in the book, running it through the rendering engine, and then, whenever a change was made in the formatting selected by the user (different font, different size, margin changes) this whole process would have to be repeated.
If my old bebook one reader running an open source operating system (open inkpod) could do it perfectly fine (recomputing the page count after setting changes was fairly fast) I can't see any reason why current devices with their much faster processors should not be able to.
guma is offline   Reply With Quote