Quote:
Originally Posted by JSWolf
KF8 doesn't need to be pre-rendered. The renderer just needs to handle all the new features.
|
The new features of KFX are
provided via pre-rendering (and image optimization). So saying that KF8 renderer can simply "handle all the new features" doesn't make a lot of sense to me. If it were truly
that simple to incorporate the enhanced typography features in such a way that all devices/apps (which supported enhanced typography) would display them similarly via KF8, it would have been done that way I believe.
What you're describing is handling it the same way as epub does. Meaning that the same file will render differently (from subtle to drastic) in every app and on every device.
I'm not arguing that either practice is inherently "better" than another. I'm just pointing out that there are actual merits to a system that provides book files that are tailored to each device/app that's rendering it in order to achieve a uniform typographic appearance across a variety of devices/apps. Tasking the renderer with achieving something similar may not be as feasible/efficient.