Quote:
Originally Posted by Hitch
Yes, in about two weeks, right?
|
Yes, it will be interesting to see how many self-publishers are affected by this change.
Quote:
Originally Posted by Hitch
Are these the pseudo-selectors that KDP claims that it doesn't support, but which seem to work (other than in ye olden KF7, of course)?
|
Amazon's documentation for publishers is not anywhere near as clear or accurate as it should be.
Quote:
Originally Posted by Quoth
Are they going to force major publishers to ALSO use Kindle Create? I can't imagine it.
|
This change is about blocking books that use HTML/CSS features that Amazon does not support from publication. That unfortunately includes some things that work in KF8, but are not allowed under Enhanced Typesetting (KFX).
I have not seen any indication that any publisher will be forced to use KC. For reflowable books KC is intended to aid novice publishers in getting simple books published. It largely fails at that mission in my opinion.
Quote:
Originally Posted by slowsmile
Sorry, I don't agree with you here. When you ask why Enhanced Typesetting has been introduced and so fiercely pushed for Amazon ebooks then the answer has to be "To create higher quality ebook features and internals."
|
I see the purpose of KFX to be mainly about giving Amazon full control over the Kindle ecosystem and reading experience. I believe that they were unhappy with how the relative openness of KF8 worked out, with its renderer based on Webkit.
The fact that Amazon has aggressively locked down KFX DRM while at the same time allowing the long-broken DRM of MOBI/KF8 to continue unchanged makes me suspect that their long-term goal is to move to KFX only, at least for newly published books. This month's change is a step in that direction.
Their desire to avoid obsoleting older Kindle devices is currently holding them back, but as those slowly go out of service Amazon may be able to justify it, especially if they offer a generous trade-in allowance.