View Single Post
Old 06-20-2009, 01:35 PM   #18
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 DaleDe View Post
I agree with the original author on most of what he says but towards the end when he says Mobi displays wrong but still displays. This is a function of the Reader itself and not the format of the data.
It is in a sense an issue with the "data format", Dale. If you jump to an arbitrary point in a Mobi file you have no way of knowing what current "state" you should be in - bold, italic, centred, left-justified, fully-justified, or anything else. That's why ePub loads the entire XML parse-tree into memory, so it has valid state data for every "node" in the tree and knows how to render it "correctly" if you jump arbitrarily to that node.

This "problem" with Mobi is precisely what allows it to work "well enough" on ANY device, no matter how limited its memory resources may be, since you're only ever dealing with a single "page" of the book at a time.
HarryT is offline   Reply With Quote