Quote:
Originally Posted by nabsltd
KFX handles things like drop caps differently from KF8. So, if I want to target older Kindles that don't support KFX, I need to be able to distinguish between the two.
|
When Amazon created KF8 format they added the amzn-mobi and amzn-kf8 media queries so that formatting could be tailored to each of those formats. When KFX was added later they added amzn-et but also made amzn-kf8 apply to KFX format so that books already published would convert properly.
So if you want to target only KF8 you need something like "@media amzn-kf8 and not amzn-et".
Quote:
Originally Posted by nabsltd
The Paperwhite 11th gen does not respond "true" to any media queries that are documented on the web to work with previous Paperwhites. I'd like to distinguish between the Scribe and the Paperwhite...
|
In KF8 media queries are handled when the book is rendered on the reading device so formatting based on things like the screen size is possible. However in both MOBI and KFX media queries are evaluated when the book is converted into those formats so media queries that depend on the characteristics of the reading device do not function.
Quote:
Originally Posted by nabsltd
the Paperwhite has bugs with vertical margins, where the value in the CSS is multiplied by 1.6.
...
The next pages have 4x horizontal rules with (margin|padding)-top of 20%. It's easy to see on a Paperwhite 11 that the spacing is actually about 33%.
|
One of the features of Enhanced Typesetting as implemented in KFX format is altering some aspects of the formatting as specified by the publisher to better normalize formatting across Kindle books. One aspect of this is automatically changing vertical spacing to be relative based on the chosen font size.
In this case conversion to KFX changes the spacing from 20% to instead be about five lines high based on the current font size.