View Single Post
Old 06-14-2020, 10:18 AM   #6
rjnagle
Zealot
rjnagle knows what time it isrjnagle knows what time it isrjnagle knows what time it isrjnagle knows what time it isrjnagle knows what time it isrjnagle knows what time it isrjnagle knows what time it isrjnagle knows what time it isrjnagle knows what time it isrjnagle knows what time it isrjnagle knows what time it is
 
Posts: 126
Karma: 2167
Join Date: Oct 2005
Location: Houston, Texas
Device: ipad 1, Nook Simple Touch, Kindle 3, ebookwise 1150
I remember all the Kindle-only kludges I had to devise in 2011 and 2012 (not that Adobe's own support for epub2 was much better). But after KF8, I held out hope that the epub standard and proprietary standard would move closer. Indeed for a few years that seemed to be the case, and I even was able to use a common stylesheet for both kindle systems and epub-based systems. I fear that is no longer becoming possible anymore. If the css media queries supported by Kindle are mostly proprietary and undocumented, then the two systems will continue to diverge.

I have used media queries mainly to scale/resize/position images; on android and ios based systems, they seem to have more support. It's the reading systems on the e-ink devices (as opposed to the e-ink simulations on Kindle Previewer) that have always been the problem.

I think there is a need is for a mechanism to adjust layouts depending on the size of the display. With images it is particularly hard because max-width is not supported.

Sure maybe we could differentiate between kf8 and mobi using amazon's current media queries, but display size is a much bigger concern for me.
rjnagle is offline   Reply With Quote