View Single Post
Old 03-11-2014, 09:38 AM   #946
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 DNSB View Post
Given the problems that various implementors have in making web pages render identically -- try looking at many web pages in IE, Firefox, Chrome, Opera, etc, you are asking a bit much to have two renderers supporting different standards give identical results.

Regards,
David
Correct, but Adobe is de facto the standard on e-readers. That won't change when 3pub replaces epub2.
A renderer should simply follow the epub3 specification.
Which renderer is used is not that important as it is basically a page rendering engine plus a DRM solution. Kobo could also use the Adobe renderer and use there own kDRM solution or the Access renderer and Adobe DRM schemes.
A reader should use one page renderer that recognizes the format (epub or kepub) and apply the appropriate DRM scheme.

Access should license the Adobe DRM scheme and offer it to their customers. Best of both worlds? Easier to maintain by Kobo? Other?
Anak is offline   Reply With Quote