Quote:
Originally Posted by JSWolf
|
This SDK was from 2011, when Adobe had yet to do its take on ePub3. From what I can tell (and I am no expert) there are three parts to this. The SDK defines what is possible and supports the features it outlines. The device manufacturers choose what features they will implement from among what is possible. The folks who code the books have to do it in a way that is recognized and properly implemented by the SDK.
Now, device manufacturers can override what the publisher has chosen, but the direction (at least from what I can tell from Kobo) is to go as hands off as possible with the CSS the publisher has chosen when we are talking about their proprietary format (Kobo ePUB3 compliant ePUB or kepub) and to use the rendering agent Adobe recently released for Adobe ePUB3 DRM. I doubt that anyone is going back and recoding already released books. I imagine that the publishing houses are all over the place in terms of how they are coding.
I'd expect it to take some time for it to all shake out. By then there will probably be yet another change in standards. The material included in the Aura promos talks about "fixed layout ePUBs". I don't know what that might be, but it could be what we think of as a reflowable PDF.
Time will tell.