Quote:
Originally Posted by JSWolf
Also, make sure your images are high resolution. When reading on devices such as a Kobo Aura HD , Kobo Aura H2O, and Kindle Voyage, if the image is too low a resolution, they will look fuzzy from having to be increased too much to fit the screen. If this is an eBook you are planning on selling, then yes you need high resolution images.
|
But not too high a resolution. Experimentally, images above about 4 megapixels will fail to render in spectacular ways in the WebKit rendering engine on iOS, depending heavily on what software is rendering it.
For example, on my book website (
www.patriotsbooks.com), I have thumbnails of book covers, and you can click to zoom in see the cover at full-screen size. On iOS, I had to actually load a scaled-down version of the images on iOS, because in Safari, the SVG code failed to properly scale the image down, and ended up showing one corner of the image at full size (one source pixel to one screen pixel).
Literally, the only difference between working content and non-working content was using a lower-resolution JPEG.
What's curious is that those exact same images worked correctly for me in iBooks on iOS, but Apple rejected my submission and required me to scale them down anyway. So the SVG handling of large images in iOS is still very fragile—perhaps a consequence of Apple not having removed whatever horrible hacks they did to make things work back in 128 MB of RAM on early hardware?
Either way, experimentally, the 2,640 x 2,040 images worked in iBooks, but failed in MobileSafari, whereas the 2,265 x 1,750 images work fine even when scaled up in SVG to 2,640 x 2,040 and then back down.
Just an FYI.