Thread: epub vs kepub
View Single Post
Old 11-12-2014, 01:52 PM   #6
arspr
Dead account. Bye
arspr ought to be getting tired of karma fortunes by now.arspr ought to be getting tired of karma fortunes by now.arspr ought to be getting tired of karma fortunes by now.arspr ought to be getting tired of karma fortunes by now.arspr ought to be getting tired of karma fortunes by now.arspr ought to be getting tired of karma fortunes by now.arspr ought to be getting tired of karma fortunes by now.arspr ought to be getting tired of karma fortunes by now.arspr ought to be getting tired of karma fortunes by now.arspr ought to be getting tired of karma fortunes by now.arspr ought to be getting tired of karma fortunes by now.
 
Posts: 587
Karma: 668244
Join Date: Mar 2011
Device: none
I haven't found any speed difference between epubs and kepubs.

The only differences arise because the rendering engine is different for both. Kepubs are rendered through ACCESS (somehow an engine only included in Kobos) while epubs are rendered through Adobe RMSDK which is a standard in every single eReader but kindles (because it's needed to handle ADEPT DRM scheme used by nearly everybody but Amazon).

Each renderer has its own set of little differences. The main ones, which are not bugs or improperly supported features, are:
  • ACCESS shows header and footer. RMSDK only shows footer.
  • ACCESS has hyphenation disabled by default, RMSDK has it enabled. (And in either case, changing that behaviour is somehow tricky because you need to set CSS properties in the book... more or less).
  • ACCESS (since FW 3.11) allows a per book page numbering (more or less one page is 1000 characters) and a true per chapter page turn numbering (I mean that if you change font or margin sizes, the number of pages of your chapter is updated...) RMSDK only offers the first one.
  • ACCESS has an image browser which allows a detailed navigation over embedded images in your books (double tap over a image to call it).
  • ACCESS is in theory epub3 capable, but there are really nearly no epub 3 books.
  • ACCESS handles links to short texts as pop-ups. I mean that it uses some heuristics to detect if a link is just a "footnote" in which case it just opens a pop-up window. RMSDK always jumps to the pointed position despite the size of that position.

And then you also have different known bugs on them. In this post in FW 3.11 thread you have a brief summary of them.

OTOH you don't need Kepub Output Calibre plugin. This plugin is intended to create definitive kepub duplicate versions of your epubs. If you just want to have epubs in your Calibre HDD library, you should download and install Kobo Touch Extended Driver plugin which transparently allows to convert your HDD epubs into kepubs when you send them to your Kobo eReader (if you want).
arspr is offline   Reply With Quote