Thread: kepub vs epub render engines
View Single Post
Old 03-25-2020, 06:00 AM   #4
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,907
Karma: 47303748
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
For epubs, they use the RMSDK. That gives support for books with Adobe DRM including books from lots of libraries. And it includes PDF support. But, they are restricted to how and what Adobe wants to implement.

Kepub rendering exists so that they have control on the books from their store with their own DRM. And they don't have to pay any license fee to Adobe if you don't download the epub version. It also gives them control over the rendering and features they implement.

And what you did is exactly what Kobo recommends to authors. And I occasionally recommend for anyone to who wants to test things without actually converting the book. The .kepub.epub extension triggers the choice of the rendering engine. About the only thing that doesn't work properly is the reading location and bookmarks. These require the spans to be added.
davidfor is offline   Reply With Quote