@Hitch: Thanks for putting me straight on the issue of kindle covers.
Quote:
Originally Posted by Hitch
Neither Kindlegen nor Previewer ignore media-queries. What media-queries are you trying to use that you think are being ignored by Previewer?
|
I was imprecise.
@media amzn-kf8/amzn-mobi is handled by the previewer. Any kind of device query is ignored, e.g.
@media amzn-kf8 and (device-height:800px). It is handled correctly by (at least some) physical devices. Or is there some syntax mistake here?
BTW, is there any other way to distinguish between e-ink and Fire devices than querying device resolution?
Quote:
|
Users can't set line-spacing in KF8 except as allowed by some, not all devices. That's why it can't override it. There are some very NOT subtle differences between HDX and DX and the Fire. However, I have yet to find real differences between the Previewer and devices, other than the font limitations imposed by Previewer for the Fire.
|
You are probably right about the reliability of the previewer; on second thoughts, apparent differences between the previewer and the device are probably due to different default font size and line spacing. But it's bad enough that the previewer cannot replicate that.
I've found slight differences in the interpretation of relative positioning for DX and HDX (and very big differences with positioning for e-ink). I would be very grateful for any heads-up about any other unpleasant surprises I might expect.
[Sigh]. The big selling point for a closed, proprietary format is that it is supposed to ensure a consistent, uniform user experience. [Mirthless chuckle]
-------EDIT-------
Gah. I meant subtle differerences between HD and HDX, not DX and HDX. Sorry. But I challenge anyone to try to comprehend KF8 without ending up with an addled mind...