Thread: KFX Format
View Single Post
Old 03-07-2017, 10:15 PM   #571
eggheadbooks1
Read, don't parrot.
eggheadbooks1 figured out that Keyser Söze was the Kevin Spacey character in less than 20 minutes.eggheadbooks1 figured out that Keyser Söze was the Kevin Spacey character in less than 20 minutes.eggheadbooks1 figured out that Keyser Söze was the Kevin Spacey character in less than 20 minutes.eggheadbooks1 figured out that Keyser Söze was the Kevin Spacey character in less than 20 minutes.eggheadbooks1 figured out that Keyser Söze was the Kevin Spacey character in less than 20 minutes.eggheadbooks1 figured out that Keyser Söze was the Kevin Spacey character in less than 20 minutes.eggheadbooks1 figured out that Keyser Söze was the Kevin Spacey character in less than 20 minutes.eggheadbooks1 figured out that Keyser Söze was the Kevin Spacey character in less than 20 minutes.eggheadbooks1 figured out that Keyser Söze was the Kevin Spacey character in less than 20 minutes.eggheadbooks1 figured out that Keyser Söze was the Kevin Spacey character in less than 20 minutes.eggheadbooks1 figured out that Keyser Söze was the Kevin Spacey character in less than 20 minutes.
 
Posts: 224
Karma: 110242
Join Date: Apr 2011
Device: Kindle Fire, Kobo Touch, Aldiko for Android
Quote:
Originally Posted by jhowell View Post
Yes, that is what it does.
Thank, JHowell, that's what I thought but didn't want to conclude without question.

So now I've been doing tests to see what, exactly, KFX doesn't like. Media queries is the first culprit.

It makes sense that a KFX file would not contain media queries (since KFX files are only sent to newer devices and apps). However, in the KDP publication process, a single ePub file uploaded to KDP is processed into multiple files: mobi7, mobi8, and now potentially KFX. So I wonder why the mere presence of media queries prevents Enhanced Typesetting. They do not interfere with K8. Do you think this has something to do with the way that ePub files are converted to this new format that is not HTML based?

So, if one wants their book to be eligible for Enhanced Typesetting, it appears to be a blanket rule that one must forgo media queries for older devices in any file uploaded to KDP. Yes, mobi7 consumers are few, and in simple ebooks media queries are unnecessary. But if you have a complex ebook, it's now clear that you have to choose between customers of future Amazon products and the existing customers that may have older devices. It seems like just another way to force consumers to upgrade.

Secondly, KP3 does not report on errors unless the conversion process fails. I deliberately created unresolved hyperlinks (one internal, one external) and the book built without any warnings; the links were simply dead. That's kind of a drag. KP2 produced warnings for such errors. Seems like a loss of a helpful feature.
eggheadbooks1 is offline   Reply With Quote