Quote:
Originally Posted by HarryT
I must admit that I still don't really "get" why this is really necessary. Why does it take more memory to "process" a long book than a short one, when all that one needs to display is the current page? It doesn't seem to be an issue with any other book format.
|
Well... I've seen a (maybe related) issue with mobipocket in the Cybook. If you have an anchor inside an element (say inside <h1>...</h1>) and you jump to this anchor, then you don't see the content formatted according to the element (i.e., you don't see the <h1> content in bold large font), probably because the reader doesn't know it's inside an element... probably because it didn't load the whole book into memory... (I don't know if this happens always, but it happens sometimes at least). That's also probably a reason why the nesting level in mobipocket is severely limited.