View Single Post
Old 03-01-2009, 02:49 PM   #31
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
ProDigit, your first issue doesn't seem to be a "real" issue:
"Zip" itself isn't a compression format itself, Zip allows different compression formats to be used. Thats why sometimes incompatibilities can occur. Let's say we would use a zip-container with deflate as compression format then we wouldn't see any incompatibilities because deflate is specificied within RFC 1951 and widely used and accepted.

The other issue you mentioned - the hardware - seems to be another non-issue too:
ePub isn't much more than (X)HTML, images and some meta informations within a zip-container. If ePub does work on mobile reading devices then other (X)HTML-renderers using compressed (X)HTML would work too. And as Ea already pointed out there are some current reading devices which already do offer some kind of HTML-support out of the box.
netseeker is offline   Reply With Quote