Quote:
Originally Posted by darryl
I had not thought this through adequately nor sufficiently understood the technical advantages of kfx, but clearly this does fit in very neatly with Amazon's customer-driven philosophy. In fact, given the variety of Amazon devices and applications and its obsessiveness with customer satisfaction, having a single format able to deliver a near uniform and optimal reader experience over all devices and applications is an explanation in itself. As I understand DiapDealer's above comments, an epub like implementation in kf8 would not have the desired result of a similar rendering on all devices. Instead, to achieve this would require a separate customised kf8 file for each device, a far less satisfactory solution.
|
I still stand on my reasoning that KFX is not needed and that all of this can still be done with KF8 without the need to change KF8. It can all be done with the renderer for KF8. It's just a matter of how KF8 is interpreted. Most Kindle eBooks start like as ePub. They then get converted to Mobi, KF8, and KFX. Some piece of software has to do the conversion from the source ePub to get these files. There's no reason the renderer for KF8 deliver the KFX experience. The KF8 renderer could be customized for each screen resolution and KFX would not need to exist.