View Single Post
Old 01-07-2018, 02:47 PM   #8
DNSB
Bibliophagist
DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.
 
DNSB's Avatar
 
Posts: 47,239
Karma: 171291590
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by sherman View Post
I think at the end of the day, the problem comes down to the image size being specified in px or pt, and Adobe RMSDK will not scale the images to fit the page if the specified size is too large. Maybe that is the "proper" way of handling such images, but it is sure a right pain in the posterior...

I often have this problem when converting from amazon KF8 books.
Yet another reason for not using absolute measurements when specifying image or font sizes since they, by defnition, are not scaleable.

I've owned ebooks where the image and font sizes were specified in pixels. Looked okay on my original Kobo (the mark 1 with Bluetooth and a 600x800 screen) but when I re-read it on my KA1, everything was tiny and could not be resized. A quick edit of the CSS to change to relative measurements and while the images look a bit soft, I can now change the font size and the images don't need a magnifying glass.

Mobi format ebooks do require images to be specified in pixels. Yet another reason to prefer AZW3.
DNSB is offline   Reply With Quote