Quote:
Originally Posted by DaleDe
The iPad app supports AZK instead of KF8 and Amazon will deliver AZK from KF8 input but does support KF7 for books in that format.
Dale
|
Dale:
Yes, it's "azk." (Not really: that's what they give you to see what the book will look like on the device, but...whatever). HOWEVER, with all due respect, they could call it Do-Re-Mi; it still does NOT support KF8-type formatting. It's still 90% KF7, not KF8. No fonts, for one thing (ditto most of the reading apps, ditto Cloud Reader). No support for: Borders, right-margins,no top-and-left-right margins in a single class. PADDING. FLOAT.
Believe me: we do a lot of books that have things that ought to be
relatively simple, and then we are stuck staring at the K4iPad version. Oh, here's a lovely example: we did some (forgive my brag for one moment, I'll be over it in 30 seconds), STUNNING pullquotes for a book. Absolutely gawjamus. Looked the bee's knees in everything (major), not counting K4iPad. In which, for reasons that elude me, the alignment of the text was completely wonk. We had to change the pullquotes, (the alignment of the text inside them, I mean), because THAT particular app simply didn't render them correctly, and the client, being an Apple person, couldn't abide.
So: don't just think that ignoring KF7, because the DEVICES are going bye-bye, is okay. I don't see Amazon deciding to up the game at Apple any time soon, due to their internecine war; and the number of books being read on phones goes up by the day. Hell, I find MYSELF doing it, at doctor's offices, etc. (Which I thought was daft, a few short years ago.)
@eschwartz:
LOL. Yes, I'm here. Can't very well have you running around invoking my name without appearing, now, can I? :-)
@notjohn:
Quote:
|
Hitch will remember Divorce Doctor, the mad Aussie who used to post on the KDP forums. One of his annoying mantras was KISS, and he was absolutely right about that. Keep it simple, though I appreciate that's not possible if you are publishing for others.
|
It would be difficult for me to forget. Firstly, he was the reason I finally started putting a signature block on my posts--so that poor DIY'ers who were reading through the posts where he was claiming he was right about X and I was wrong, could look at both our websites, and make their OWN determination about who was daft and who
probably knew what she was talking about.
Secondly, if you'll recall, he was the only person I ever actually reported to Amazon (other than the spammer posts), after he went off the deep end one week and posted some ridiculous number of posts (10 or something) about me
all entitled "Hitch the Bitch," ranting about me, because someone ELSE--not I, ironically--had turned him in for his little cover scheme that was being sold on the Amazon website. He assumed that it was me, because I'd blasted him for putting up a--what did he call it? Oh, yes, an "homage cover" for "A Year in Provence," as part of his "cover design services" images he was running on Amazon. He didn't say, in the images, that it wasn't a REAL cover. (He later claimed it was a "customer image," which he was entitled to put up.) By using that cover, he'd basically
implied or allowed potential customers to infer, that P Mayle was HIS client, which
I absolutely knew was untrue--because he was MY client. And I certainly knew where he was getting his covers.
Anyway, I digress: my entire point was, forgetteth not readng APPS, when you think of the KF8-KF7 discussion, please. And NJ, it's unlikely that you'd get a KQN about your image choices, because you don't use that many images, really.
Lastly, boys and girls, Voyage has a KF7-
type-glitch, even though it's supposed to be a KF8 device: if you have an image that's larger than 50% of the width of the screen, but smaller than 100%--it's blown up to 100%. So....remember that when designing.
Hitch