Quote:
Originally Posted by jhowell
Kindle apps and devices have multiple book renderers, each of which handles line spacing and font sizes differently. The majority of Amazon purchased books will use the KFX renderer. Books you email in MOBI format will use the older MOBI renderer. (You cannot email KFX.)
There is a third reflowable renderer for KF8 (AZW3) format, which produces different results from the other two. You could email a Master MOBI produced using Amazon's Kindle Previewer - not calibre - and that will give you KF8 on your Kindle but will still use MOBI on your iOS device. (KF8 is not supported by Kindle for iOS.) Reading position, notes, and annotations will sync between the Kindle and iOS app even though the formats are not the same, but you would lose the cover thumbnail image of the book on your Kindle.
Your choice of font will also affect the line spacing differently across renderers. That is just the way it is on the Kindle platform.
Either emailing or sideloading a MOBI will yield the same rendering.
|
Right, but if memory serves--and I admit, I'm reaching back--I had this customer that was obsessed about line-heights. He'd had a formatter BEFORE us that delivered 1.0em line-height files to him--
never telling him that they'd be auto-converted to 1.2ems, the
moment he uploaded them at KDP. I had to demo it for him about 10x, before he'd believe me.
But my point is, he was able to sideload that mobi (dual, what we called KF8 .mobi) to his own Kindle and 'see' his desired line-heights without any trouble. That's why he was convinced that we were incompetent--after all, his other formatter "got it right." (sigh).
Hitch