Quote:
Originally Posted by GeoffR
Up to and including firmware version 3.18.0 there was a showPageHeader=false entry you could add to the device's configuration file that would remove the title text from the top of the page in KePubs, but it still left a blank area where the text was.
But this no longer works in the current firmware, and there is no other way I know to remove the KePub header without removing the footer too.
One thing to check if you are using Calibre to convert the books is that you have Preferences > Common options > Output profile set to Tablet. If you have it set to something else the size of the images will be reduced when the book is converted.
Apart from that, it is up to the publisher to set the size of the image in the book. If the publisher doesn't specify a size then the image is displayed at its natural pixel size. Unfortunately many publishers either don't bother to specify a size, or else specify an absolute or pixel size that will only look right on devices with a certain screen resolution.
(The strange thing is that some publishers do the cover image correctly, proving that they know how to size the images relative to screen size, but then fail to do the same for the other images in the book.)
What the publisher should do is specify the image size relative to the screen size of the device it is being displayed on (by using height:90%; for example), or in some cases relative to the font size the reader has selected (using height:2em; for example.) If this is the problem then all you can do is edit the book before sideloading. There are two approaches to editing the image sizes for the book:
1. Use image manipulation tools such as ImageMagick to resize all the images in the book to suit your device. This works for those cases where the publisher has not specified a size for the images in the CSS/HTML. e.g. if the publisher has made the images sized to suit a 600x800 screen, then resizing with a scale factor of 180% should make them the right size for a 1080x1440 device. This can often be done with a single command (mogrify -resize 180% *.jpg).
The advantage of this approach is that it is easier for books where there are a large number of images, and it doesn't require any knowledge of CSS/HTML. The disadvantage is that it will have to be re-done when you want to load the book to another device with a different size screen, and it might not work if the publisher has specified an absolute or pixel size in the CSS/HTML.
2. Edit the CSS and/or HTML files to specify the image size relative to the screen size. E.g. if the image is 400x700 pixels and the images are suitable for a 600x800 device then you could set the size as height:87.5%; width:auto; and the image would have the same size relative to the screen height on all devices. (You might also want to look at using min-height,max-height,min-width,max-width styles, or look into using a SVG block if you want finer control of things such as aspect ratios.)
The Advantage of this approach is that it will work for devices with different screen sizes -- it is what the publisher should have done in the first place. The disadvantage is that you will probably need to edit each HTML entry for each image separately -- a lot of work if there are a lot of images -- and know enought about CSS/HTML to know what to edit.
In both cases the quality of the results will be limited by the quality of the original images provided by the publisher.
|
Thanks. I used calibre and tried many output profiles. All with the same result. But my question now would be, why do I see the images the right way using an ebook reader on android or when I sideload them to the paperwhite 3? If the book isn't properly set up, shouldn't I see the wrong size on all devices? It looks like it's the way kobo shows the book that's the problem.
Oh, btw. This happens with all my books. I remember Google play books used to behave this way until the updated it, many months ago, and now it shows up fine. That's why I think it's a reader problem and not a book problem.