MobileRead Forums - View Single Post - Mobigen Why are css media query examples in Amzn Kindle Publishing Guidelines so terrible?

rjnagle · 06-13-2020, 02:27 PM

Thanks.

Jhowell, To push back a little on your point.

Title page must have something more than a heading font. Also, the defaults don't especially seem well-suited for large devices 10-12 inch width.

Actually, the original reason for using queries is that I wanted to substitute a heading with an illustrated graphic and then to resize according to screen width. You would expect form factors over a certain size to have these heading graphics about 50% of width, but on paperwhite and iPad minis it makes sense to make the image a little wider (maybe 75% or 80%) for legibility....

Frankly, I haven't been keeping up with KFX (although maybe I should). It would really be sad if Amazon is drifting further from supporting css in the epub3 standard. I never really saw the benefit/value of the KFX format. How is it helping readers? How is it helping publishers? I kind of got the impression that KFX is mainly for Amazon creation tools (though I see in Previewer that I could export my epub to kfx).

(I for one would welcome changes to make it easier to force new pages. Even Google Play Books is pretty terrible about supporting that).

06-13-2020, 02:27 PM	#3
rjnagle Zealot Posts: 126 Karma: 2167 Join Date: Oct 2005 Location: Houston, Texas Device: ipad 1, Nook Simple Touch, Kindle 3, ebookwise 1150	Thanks. Jhowell, To push back a little on your point. Title page must have something more than a heading font. Also, the defaults don't especially seem well-suited for large devices 10-12 inch width. Actually, the original reason for using queries is that I wanted to substitute a heading with an illustrated graphic and then to resize according to screen width. You would expect form factors over a certain size to have these heading graphics about 50% of width, but on paperwhite and iPad minis it makes sense to make the image a little wider (maybe 75% or 80%) for legibility.... Frankly, I haven't been keeping up with KFX (although maybe I should). It would really be sad if Amazon is drifting further from supporting css in the epub3 standard. I never really saw the benefit/value of the KFX format. How is it helping readers? How is it helping publishers? I kind of got the impression that KFX is mainly for Amazon creation tools (though I see in Previewer that I could export my epub to kfx). (I for one would welcome changes to make it easier to force new pages. Even Google Play Books is pretty terrible about supporting that). Last edited by rjnagle; 06-13-2020 at 02:30 PM.