Quote:
Originally Posted by Doitsu
Sorry, I can't help you with that, but the screenshots were taken with the current iOS Kindle app and I don't think that the KDP tools will mess with the layout. After all a "beautiful page layout" was one of the top selling points of the Kindle for iOS 4.9 app:
BTW, most of the (admittedly rather gimmicky) pseudo selector and CSS3 stuff in my test file doesn't even require explicit fallbacks. Non-KF8 compatible iOS apps will simply display a plainer version as you can see in the screenshots of the unaltered mobi7 version of the same file, which doesn't contain any conditional styles.
Note that even mobi7 files are automatically hyphenated.
|
Well, that's nice, but that's a pretty far piece from what I'm seeing, when a client uploads a MOBI--as AZK's cannot be uploaded for sale--and what's delivered to a 4th-gen iPad in the iOS reading app.
I'm not trying to be combative here, Doits; but what's shown in the AZK isn't what's delivered for the book that's on sale. For example--you probably have an Amazon KDP test account--if you upload that book that you took the screenshots of, with the red, and download the Step-7 mobi, what's THAT look like? Or, for that matter, what's the online iOS preview look like?
Because what I see, from my clients who have books on sale, and what the AZK looks like, aren't the same. The devices still seem to be delivering far closer to KF7 than KF8. No? I mean, listen: who, more than I, would want to see bookmakers NOT have to worry about KF7? Nobody here.
There's NOBODY here that would like to see KF7 go the way of the dodo than I. And let's not forget that Kindle Cloud Reader is also out there, which won't even display FONTS, folks, much less anything else.
(And to whomever it was that mentioned it: yes, K4PC is pretty KF8-ish. I don't disagree.)
Hitch