View Single Post
Old 06-20-2009, 02:01 PM   #22
netseeker
sleepless reader
netseeker ought to be getting tired of karma fortunes by now.netseeker ought to be getting tired of karma fortunes by now.netseeker ought to be getting tired of karma fortunes by now.netseeker ought to be getting tired of karma fortunes by now.netseeker ought to be getting tired of karma fortunes by now.netseeker ought to be getting tired of karma fortunes by now.netseeker ought to be getting tired of karma fortunes by now.netseeker ought to be getting tired of karma fortunes by now.netseeker ought to be getting tired of karma fortunes by now.netseeker ought to be getting tired of karma fortunes by now.netseeker ought to be getting tired of karma fortunes by now.
 
netseeker's Avatar
 
Posts: 4,763
Karma: 615547
Join Date: Jan 2008
Location: Germany, near Stuttgart
Device: Sony PRS-505, PB 360° & 302, nook wi-fi, Kindle 3
Quote:
Originally Posted by HarryT View Post
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.
Can mobile browsers render even large XHTML-documents correctly? Yes. Do they need to load the whole document into memory? No. ePub-renderers also don't need to do that. It's just a matter of how the software developers implement their CSS renderer and not really a matter of "XML parse-trees".
Even on mobile devices XML can be used as stream. The parsing can be done using event models (SAX) or newer approaches (StaX). The XML isn't the problem, some CSS-styles are. Mobile browsers were able to solve that and hence ePub-renderers could solve that too.
netseeker is offline   Reply With Quote