View Single Post
Old 05-14-2013, 04:54 PM   #350
Anak
Guru
Anak ought to be getting tired of karma fortunes by now.Anak ought to be getting tired of karma fortunes by now.Anak ought to be getting tired of karma fortunes by now.Anak ought to be getting tired of karma fortunes by now.Anak ought to be getting tired of karma fortunes by now.Anak ought to be getting tired of karma fortunes by now.Anak ought to be getting tired of karma fortunes by now.Anak ought to be getting tired of karma fortunes by now.Anak ought to be getting tired of karma fortunes by now.Anak ought to be getting tired of karma fortunes by now.Anak ought to be getting tired of karma fortunes by now.
 
Posts: 603
Karma: 641742
Join Date: Mar 2012
Location: DE
Device: Kobo Glo
Quote:
Originally Posted by taming View Post
No, i think that every vendor will have its own spin on things like whether or not there is a title at the top of the page, and buyers may decide that they like one company's take on it over another, but that the old ePubs will disappear.
Your right that this year the switch to epub3 will be made. But, I don't know if the old epub2s are going to disappear soon. That is to be decided by the publishers.
To my knowledge there is no mass coversion tool available yet, to convert exisiting epub2 to epub3 or to epub3+2 (the latter is complient with old readers, where epub2 is an embedded fallback). I've no doubt such tool will surface.
I don't think that Kobos spin of epub3 will be any different than epub2.
They have developed a house style and that won't change drastically with the introduction of epub3.
What is needed is a universal drm not different vendor specfic proprietary drm so buyers can buy book in any shop.
Adobe (or any other party) could step into this by offering a new drm protection solution/module as an addon to epub3 and leave the development of epub3 to others. Adobe has the infrastructure in place.

Readium and other developers of epub 3 engines should publish a best practices epub 3 guide on how a epub 3 should be constructed to keep it flexibible for user agents (devices) to add features that can be adjusted by user input. True, that isn't any different from epub2 but there are many epubs out there that lack flexibility because every (child) element in a css contains "hard coded" redundant data that only should be set at higher levels.

Last edited by Anak; 05-14-2013 at 05:20 PM.
Anak is offline   Reply With Quote