Quote:
Originally Posted by kso
Shame there is no mechanism by which you could tailor your instructions to specific devices or media, so you'd be able to verify before publication that your code --- as long as you and the previewer both follow published guidelines --- actually does what you want.
|
Well, there are, in fact, media queries that you can use to (somewhat) tailor your rendering to devices. Kindles are basically honoring screen-size-based identifications, using device-aspect-ratio. It's not perfect, mind you; for example, you still can't really tailor to the LookInside--but it's a huge step up from a few years ago when there was NO way to separate out an iPad, for example, from other KF8-rendering devices.
And you can use them for older-device capability, too. "amzn-mobi" versus "amzn-kf8" and the like.
Quote:
I've seen several types of glitches, mostly to do with indentation (of lists), ignoring the PRE element (proportional spacing), and vertical spacing.
All the things I've noticed so far work in PV 2.94 and on actual Kindle devices when I sideload KF8 books. That's what's really frustrating.
So far KPV 3 appears to be a step backwards (or maybe not yet ready for production?) for the author, even if it has advantages for Amazon.
klaus
|
Images can display quite improperly, both in size and alignment. I've had to take screenshots of books, on real physical devices, to assuage customer concerns based upon what they see in KP3. Also, the line-heights in KP3 are slighly off, slightly too tall/high. While that mayn't seem a big deal, to some customers who are very obsessed about appearance, the distance between (for example) the end of one body paragaph to the next subhead, to the following body paragraph is VERY important and they can be quite...distressed...if they think that the layout isn't close to what they've got in print (or whatever).
Hitch