Quote:
Originally Posted by AaronShep
Kovid, my test is to submit new HTML files for books that are already listed with Enhanced Typesetting enabled. These files are immediately processed as KFX, no waiting. The next day, I ask Amazon to replace my purchased copy with the latest version, and that shows me the new file with the latest KFX processing. It's cumbersome, but it allows at least limited testing.
I think the reason for KFX is to be able to add and modify "secret sauce" ingredients and make them hard for competitors to copy -- though, so far, they've made a royal mess of it. I do like the new JPEG XR format. I have no doubt there are more changes coming, and they're just setting up the groundwork. And I also know they're working hard to get the bugs out.
|
There is no reason Amazon could not generate a different KF8 eBook for each device in order to have device specific images. Also given that Adobe can do the typesetting for ePub with no changes to the ePub, there's no reason Amazon could not have done the same for KF8. That way, all KF8 eBooks would support the enhanced typesetting from the start including side loaded KF8. Amazon could also have KF8 support JPEG XR. But, one thing Amazon is doing wrong is converting all images to JPEG XR. Only JPEG should be converted to JPEG XR.
Anyway, I don't think KFX is so Amazon can do more for the user. I think KFX is so the user cannot remove the DRM and/or convert to ePub.