Thread: kepub vs epub render engines
View Single Post
Old 03-26-2020, 08:03 PM   #27
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,796
Karma: 146391129
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 sherman View Post
As far as I'm aware, the latest version of RMSDK uses Readium for it's epub3 compatibility, and therefore probably webkit to render, which is what ACCESS uses so...

So basically, the version of RMSDK that Kobo uses is basically the latest version of the 'legacy' renderer (with all the nice typography features), so there really isn't any point to upgrading.
Um...no. The version of RMSDK that Kobo is using does not have all the nice typography features. You cannot use the OT features of an opentype font to get say true small caps.

RMSDK has better typography then Access and makes for a better reading experience. If the new RMSDK was put in place, then if what you say is true about the latest RMSDK basically being similar enough to Accessfor ePub 3 features, then Access can be dumped.
JSWolf is offline   Reply With Quote