Quote:
Originally Posted by notimp
Hey - to your credit, you did introduce a new aspect. To your credit, I havent acknowledged it so far. And it was my fault.
Lets change that, what do you say.
Lets have a field day with it.
Because what you introduced a page back - was the notion of .kfx primarily being a "distribution format". Some sort of dumb container where it doesnt matter if people are still allowed to create or understand it - because format development, or culture creation takes part entirely separate from it. You even went so far as to say "why does it matter, that publishers arent able to understand a distribution format?".
(That by the way is a much more likely explanation for why they didnt react, when Amazon took over the production aspect of eBooks entirely - they got sold on it being "just new a new DRM container". *Bravo.*)
And thats a false premise.
Its exactly the distinction between DRM (the container (a format mainly for the distribution side of things)) and format (the "book") that gets purposefully blurred here.
So -
- .kfx (kf10) isnt a container, it is a format.
- .kfx isnt a distribution format, it is Amazons next iteration of the main Kindle file format (kf8>kf10)
- distribution usually doesnt change layout, .kfx creation does
- distribution usually isnt sold to consumers using a feature addon approach (new with distribution - ligatures! Its an exclusive!)
- .kfx does impact content (pictures), readability, and final layout - it is not a distribution container.
It is not the DRM layer - it is the format we arent allowed to create anymore.
False premise, you are trying to massage the facts. Your turn.
Why does it matter? Because we are loosing feature parity. Books we (or publishers) can create will be below the new Amazon standard. And there are structural reasons why it will be much harder to regain it, this time around. I've listed them before.
|
Is WebKit also a format? Because newer versions of WebKit can implement ligatures, modify rendering of layout, readability, and pictures, and of course,
iterate.
...
But really, it's all the same, because a container is a synonym for a format.
So I am not at all sure of what you are trying to say.