Hi,
This is exactly how I read pdf's/scans on Nokia 770, except that I use jpg's 480x800, embedded into blank html (Fbreader reads those files) and rendered at lower quality so I have about 20-50kb per image. For all fiction books it works page to page, for technical books, sometimes 1-1, sometimes 1-2. It is unbelievable fast since you access an image at a time, but you cannot jump between pages. I guess that you can insert chapters inside the html, but I have not tried. I have books up to 2000 images (100MB) and it works nicely.
I guess the same should work on any eink with appropriate size images. It depends I guess on size and quality of screen.
Liviu
Quote:
|
Originally Posted by ali
So the idea is to render everything on your desktop pc and create one grayscale image per page. 1024x768 pixels with 16 colors is uncompressed(!) 384kbytes. So instead of storing a 15-page pdf on the iliad, I'd store a format that holds 15 images. That should reduce rendering time to nothing, with no visual difference (you can't zoom tho). Page flipping would just be reading the correct portion from the file and copying it directly into the framebuffer.
It doesn't help at all with your 10-billion-pages monster pdfs, and it will probably not work for novels, where every page is about ~1k text in a single font. The pdf's I have use lots of differents fonts on every page, have diagrams and such. Sometimes they take multiple seconds to render a page on my 2GHz processor - what will this be on a 400mhz cpu without fpu?
|