|
Hi,
To me the ideal book format would be like this:
1: For regular books that consist mostly of text with possibly a picture here and there, so for most (nonscans) fiction books, the smallest universal format necessary which is txt for some, html for others (for all if you want chapter links, and other embedded goodies). I would have everything (including the pictures) embedded in one file with the appropriate folder in the html case
2: For books that contain text, but also have figures, diagrams and the like everywhere in an essential way (most technical books, comics...), and for image only pdf/djvu scans whether they are of type 1 or 2 books, a format that can render the book a page at a time without reading the whole book for info (like pdf or djvu does now) unless you so choose. The book itself may take lots of hard disk/flash memory space (cheap), but the rendering should take very little ram (expensive). The closest I find it now is to use jpg images embedded in a blank html, cut to device size and maybe in two (nokia 770 or Ebookwise 1150 for me) if appropriate, but I have to work somewhat to tailor them from my pdf/djvu/scans and I would rather have a format that does that automatically. The djvu script for librie that I saw is a hack in that direction (takes a djvu page, cuts it to size, pads, makes it librie readable and displays it), but I have no idea how fast it works. A format that would contain an executable script of this type with the possibilty of cutting the page to adjust to device screen without scrolling/zooming would be ideal.
Liviu
|