View Single Post
Old 08-06-2012, 02:54 AM   #13
HarryT
eBook Enthusiast
HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.
 
HarryT's Avatar
 
Posts: 85,557
Karma: 93980341
Join Date: Nov 2006
Location: UK
Device: Kindle Oasis 2, iPad Pro 10.5", iPhone 6
Quote:
Originally Posted by Oldpilot View Post
I find it hard to believe that a plain-vanilla e-ink Kindle is all that much more sophisticated than the other readers out there. My Kindles don't have any problem with even the biggest of my books, say a 400KB html file and six or ten 127KB jpegs.
It's not that it's "more sophisticated" - quite the opposite, in fact. The reason there's the limit is that ePub supports CSS, and hence has to maintain state information for every part of the text. When the ePub reader opens a file, it has to parse it, and hold that parse tree in memory. The Mobipocket format, which the Kindle uses, is stateless. Only the page currently being displayed is loaded into memory, and there's no parse tree, hence much lower memory requirements. (The new Kindle "KF8" format, however, basically is ePub, and works the same way that ePub does.)
HarryT is offline   Reply With Quote