Quote:
ACTUALLY, we still give our customers made-to-order MOBI files. I mean, sure...if a customer is having a cow, because they read some blog somewhere, we'll give them (solely) an ePUB, but generally speaking, we don't trust the auto converter. (Plus, don't forget, we do a TON of font work!) We build and test the MOBIs ourselves. We don't believe in the "one file to rule them all" approach, e.g., give the client an ePUB and turn 'em loose.
When you do that, you can't use media queries for the Kindle versions. We prefer to optimize the files for the Kindles, both new and old. (I just updated my K2, for crying out loud and it still works, chugging along...)
I mean...if we're asked for a single ePUB, and no mobi, we can and will do that but our preference is to optimize the files for the environment to which they are destined.
Like you, I'm concerned about the realities, behind the scenes, with KPF uploads. Not that my job is to think about folks who might buy a book and want to download it and er, tweak it or whatever, but...just the same...
I like sticking with stuff that I can dissect, if need be. Take apart, find out what's wrong, see the code...all that.
|
@Hitch...Alot of people on the KDP forum seem to think that I'm in love with Kindle Create. I do like the app -- but with many frustrated caveats. I'll give you one simple example. I'm writing a how-to ebook on KC and to me it's absolutely essential that there is a multi-level NCX TOC in my Kindle ebook to help the reader easily navigate all the heading levels in the ebook. I mean it's a how-to book for goodness sake where readers will always need to quickly jump around to reference particular bits of information. But how can you do that easily when Kindle Create will only ever give you a single level NCX TOC?? I mean you can even create multi-level NCX TOCs easily in Word or epub that will work just fine in Kindle ebooks. So why the hell can't you do that in Kindle Create? I've already suggested this twice to dev support as a change to KC's NCX TOC and I'm giving them till Jan 2020 to make and release that change so I can actually use Kindle Create to produce that ebook. If it doesn't happen then I'll just use Jutoh with Sigil to produce the epub versions(with a multi-level NCX TOC) and Kindle Create can go swing.
And a big thank you for the above information. It's funny because in the Kindle documentation they brag that the command line version of the new Kindle Previewer is suitable for batch processing KPF files for professional formatters. And here you are as a professional formatter saying you wouldn't touch Kindle Create or KPF with a barge pole. So I doubt if any professional formatter worth his/her salt is using that command line utility to produce
any KPF files. I also understand why as well -- because KC doesn't give you enough control over the formatting + distribution problems.
You've also given me a great idea. I think I'll add a new chapter to my how-to book on KC called "Kindle Create: Critique, Caveats and Wish List" where I could vent all my pent up frustrations about KC. Seriously. It might wake them up.