View Single Post
Old 06-20-2009, 02:50 PM   #31
jgray
Fanatic
jgray ought to be getting tired of karma fortunes by now.jgray ought to be getting tired of karma fortunes by now.jgray ought to be getting tired of karma fortunes by now.jgray ought to be getting tired of karma fortunes by now.jgray ought to be getting tired of karma fortunes by now.jgray ought to be getting tired of karma fortunes by now.jgray ought to be getting tired of karma fortunes by now.jgray ought to be getting tired of karma fortunes by now.jgray ought to be getting tired of karma fortunes by now.jgray ought to be getting tired of karma fortunes by now.jgray ought to be getting tired of karma fortunes by now.
 
Posts: 554
Karma: 2928497
Join Date: Mar 2008
Device: Clara 2E & Sage
Quote:
Originally Posted by netseeker View Post
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.
I was just reading up on StaX. I'm no expert, but this does look like a good fit for an e-reader application.

From reading your comments (including the ones later in the thread), it certainly looks like you know what you're talking about. Perhaps you should work at Adobe
jgray is offline   Reply With Quote