Quote:
Originally Posted by slowsmile
@Doitsu...
[/I]
Yes, unfortunately, you did say it. Here it is again with some emphasis:
"If the epub/mobi file supports Enhanced Typesetting, Amazon will convert it to a KFX file, if the device/app supports it. If the green check mark is missing, users will get at most AZW3 files."
And as I've already mentioned, if you run a Kindle check like ET on a KFX file that has been successfully generated by Kindle software(Kindle Create) then why should it fail?
|
William, you are mixing apples and oranges. Doits
never said what you're trying to imply he said, through a tortured construction. Where you are going off the tracks is when you ignore the first part of his sentence, which said:
Quote:
|
"If the epub/mobi file supports Enhanced Typesetting,..."
|
He very obviously was not talking about KPF files, which is the output format of Kindle Create and the other DIY-applications (Kindle Textbook Creator, etc.). KPF is a proprietary, relatively
useless format, owned by Amazon, that is an interim step in the Word-->"Kindle eBook" process. Unlike ePUB or MOBI, it's
not a standalone format--you can't load it to any device, and read it. You can't make an ePUB by its lonesome, I mean, sans helpful plugins and the like). It's (apparently)
deliberately constructed, much like Apple's iBooks app, to keep the user in the Amazon walled garden of content creation and distribution. (And don't get me started about what's under the surface!)
But enough about the realities of KPF/KFX. The
point is, Doits was correctly discussing what happens, in KP, KG, etc., with
either ePUB or MOBI input content. He was
NOT discussing KPF files. While I suppose it's
possible that a KPF file
might be useful for Gregg, in his travels and travails, it's hardly a "format" that I'd expect to see discussed here on MR very much, as it's basically a Word template that creates a straightjacket that's not very usable.
And
lastly,
that's not what was being discussed here, anyway. I don't understand
why you had Gregg buy your book, since it has nothing, absolutely
nothing to do with what he's trying to do here, which is
use your image plugin to manage his cover images in his backmatter, in the ePUB he's converting to MOBI (KF8). That's all that's being queried here. Nothing about KFX.
I realize that you've established yourself as an
expert on KPF and KindleCreate on the Amazon Forums, but that is not what was being asked about here, not even remotely.
Oh, and lastly, Doits is
correct--if you load a valid ePUB or MOBI to KP3, and it will display the green checkmark if the file will be subsequently converted to KFX (for reflowable Enhanced Typesetting, for regular, reflowable ePUB/MOBI files, or for FXL). And, of course, a KFX file will
not be delivered to those devices that can't support it. (Like my Trusty K2).
Nothing has changed in the "Chinese Menu" world of what happens, post the
PW (Publishing Workflow). The file is rendered into
myriad formats, from KF8 (AZW) to KF7 to now, KFX. And whatever the hell is getting delivered to iOS these days. The correct file is then delivered to the requested device, when the user indicates which device is going to be used for viewing the requested book. That's still the same.
Hitch