View Single Post
Old 10-31-2019, 11:46 PM   #64
Tex2002ans
Wizard
Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.
 
Posts: 2,306
Karma: 13057279
Join Date: Jul 2012
Device: Kobo Forma, Nook
Quote:
Originally Posted by slowsmile View Post
Remember this is OLD mobi7. The only way you can style and size a mobi7 is using absolute pixels in "height" and "width" declarations within the image tags.
... That's exactly what I wrote.

Quote:
Originally Posted by slowsmile View Post
If you increase the size of an image using percentage values and you go beyond its actual pixel size that's when you will get blurriness and pixelation problems due to extrapolation -- which is just a guessing game at best.
Which is why you use high resolution sources. Much less chance of blurriness/pixelation due to upscaling.

Again, why they recommend 300+DPI source images.

Back to the fantasy map example. Better if it was downscaled to half size on your Kindle and "unreadable", you click on it, and now you can see the full resolution image and pan/scan.

If you preemptively included a lower resolution map, users have an unreadable mess, AND there's nothing they can do about it.

Last edited by Tex2002ans; 10-31-2019 at 11:50 PM.
Tex2002ans is offline   Reply With Quote