Thread: kepub vs epub render engines
View Single Post
Old 03-25-2020, 11:29 PM   #13
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: 46,410
Karma: 169098492
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by hobnail View Post
Why does Kobo use two different rendering engines? Or, why can't they use the kepub rendering engine for epubs?
The simple answer is that when Kobo moved into the Japanese market, they needed an epub3 renderer to handle Japanese typography. Their answer was to use the "ACCESS NetFront™ BookReader v1.0 EPUB Edition" to open epub3 ebooks with the file extension .kepub.epub. OTOH, they needed to keep using RMSDK to be compatible with Adobe ADEPT DRMed epubs and pdfs.

So two renderers became part of Kobo's firmware. RMSDK is still not close enough to a full featured epub3 renderer to allow sole use.
DNSB is offline   Reply With Quote