Thread: kepub vs epub render engines
View Single Post
Old 03-26-2020, 07:51 AM   #16
JSWolf
Resident Curmudgeon
JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.
 
JSWolf's Avatar
 
Posts: 79,998
Karma: 147448039
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
Quote:
Originally Posted by DNSB View Post
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.
What about the current version of RMSDK? Is that good enough to handle ePub 3? If yes, then all Kobo needs to do is remove Access and update to the current RMSDK.
JSWolf is offline   Reply With Quote