Quote:
Originally Posted by jhowell
I can account for why the image in your book is smaller when delivered directly to the device from Amazon as compared with transferring via USB.
The USB copy will be in KF8 (azw3) format and will have the same HTML coding that you placed into the book. In this case the image will be displayed 200x300 pixels on a 600x800 pixel screen or 1/8 of the screen area.
The copy sent directly by Amazon will be in KFX format for newer Kindles, including the Kindle 7th gen with up-to-date firmware. This is the format used for delivery of most books these days and enables enhanced typesetting features such as hyphenation and page flip.
During conversion to KFX format Amazon applies several fixups to the book's original formatting intended to increase readability. Images coded with dimensions in pixels are converted to percent instead to promote consistency of display across devices with widely varying screen resolutions. The exact details are complex and I don't understand all of the rules, but in the case of your book the new size is width:23.4375% which happens to be 300 (your image height) divided by 1280 (typical HD screen height).
The result is that the image is displayed at 23.4375% of the screen width on all devices. For your Kindle 7 that will be 140x210 pixels or 1/16 of the screen area, so that the image appears about half the size of the KF8 version.
|
THERE it is. I was sort of plowing my way toward this, but I thought it would be a KF7/KF8 thing; I don't have this mad depth of KFX expertise that @jhowell does, but I thought it would be something like this. I used to have these issues with the "send to kindle" and the faux WiFi-xfer functionality. Or, to be more accurate, I didn't, but our clients did, and it was a major source of aggro for me.
So, now--about percentages versus fixed-units.
@DNSB--if he's serious about making MOBI files, he doesn't really have a choice--he has to use fallback coding that specifies the precise pixels, due to the KF7 devices that are still out there. If he doesn't, and uses percentages, that's ignored in the KF7, and his image can/will be blown up to the size of the screen, which sucketh when you have a small image. There's a thread--a very long, very tedious thread--somewhere here in the Sigil forum, in which slowsmile/William and I had a heated discussion about his plugin that creates the fallback coding for this very purpose. You (Gregg) can now ignore the heated part, but look at the info that his plugin provides--it does the heavy lifting for you.
@Gregg--you should be sizing your images primarily by the use of percentages, not pixels (for the KF8s) as that's more consistent in terms of look/feel. However, you do also need the fallback stuff for the KF7s. And honestly, speaking as a highly-paid perfesshnul (ha), only God knows why KFX is "fixing" the coding and changing the damn size. That one just makes my head hurt.
HOWEVER, bear in mind that what that means is that what you refer to as the "whispersynch" version
is what other people are seeing--so break out the codebook, and write your media queries--you can use slowsmile's plugin's coding as a starting point.
HTH.
Hitch