View Single Post
Old 04-27-2009, 06:19 PM   #52
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 Valloric View Post
Tell me, what do you think should be the expected handling for huge single file epub books on a device like the Sony Reader?
Well, i'm not a contributor of the ePub-specification and can only speak for myself. Why doesn't the reading software use a stax-like aproach when parsing XHTML for example? Why does the epub-producer have to split the file into parts if just those parts that are required could be read? It's not easy to implement such solutions (not because of the XML but because of the CSS-selectors for example) but developers do this day for day if they know that the targeted plattform is low on resources. A specification can take account of such concerns and include (or point to) best practices for such scenarios. It can also explain such scenarios in a more abstract manner than i did here.
netseeker is offline   Reply With Quote