Quote:
Originally Posted by rube
Some of the images I've resized I've found to be big enough to display on a large screen tv! No one reads ebooks on a large screen tv. I wonder what the publishers would say if they knew how many of their books get opened up and the images resized  |
eInk works completely differently then LCD. A small image on a hi-res LCD screen can look OK. But a small image on a hi-res eInk screen may not look OK. You cannot take a low-res image (say a map) and make it full screen on a hi-res eInk screen without the image being fuzzy.
One of the problems was because of Mobipocket. Before eInk, Mobipocket had a limit on the size of images. I think it was a limit on the size of the images. So when Mobipocket eBooks were converted to other formats, the images were overly compressed and too small. A lot of the original devices used to read Mobipocket had small low-res screen such as a Blackberry. With eInk, the screen started off at 6" with a resolution of 800x600 and mostly stayed that way. There were some larger screens with a higher resolution such as the iRex and the Kindle DX. There were some that used 1024x758 resolution screens. But eInk did not get truly hi-res until 300dpi screen became the screens for most Readers. The older Readers didn't have hi-res, didn't have much system memory, and they didn't have all that fast a processor. Plus, eBooks back then has low-res images.
Now we have 300dpi Readers and hi-res images at least for the cover and title page image. These older Readers were never designed to handle such large graphics. They slowed down, froze, or rebooted. It has almost nothing to do with the size of the HTML file. It has to do with the size if the graphics.