View Single Post
Old 03-12-2014, 11:24 PM   #951
DNSB
Bibliophagist
DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.
 
DNSB's Avatar
 
Posts: 47,432
Karma: 171313058
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by Anak View Post
Yes, I'm aware and have seen different browser engines handle web pages differently. I just wanted to state that Kobo should use only one renderer (I guess Kobo would choose Access; lower costs/fees or easier to build/adapt or any other reason etc.) that works with both epub flavours and different DRM schemes. Using only one renderer will build pages near 100% identical.

I do use Datalogics DL Reader as it is a lot faster as ADE.
I don't know what Adobe/Datalogics would charge for using ADEPT DRM outside of Adobe's software framework but I suspect it would be little if any cheaper and would likely be a pain to implement -- dev hours are not free.

My opinion is that if Kobo had to choose one renderer, at this point in time, Kobo would have to go with ACCESS -- one look at how an epub2 renderer handles Japanese typography gives you all the information you need to make that decision.

Regards,
David
DNSB is offline   Reply With Quote