Thread: Kepub format questions
View Single Post
Old 02-07-2019, 06:26 PM   #16
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,906
Karma: 47303748
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by geek1011 View Post
Kepubify aims to be fast, correct (as in being as close as possible to normal kepubs),
The latter was also the intention of the KoboTouchExtended driver. If there is something it doesn't do, people should report it.

And comparing speed between to two is also a problem. During the send-to-device, calibre is making sure there are making sure the metadata and the covers are up to date. Plus there is the metadata updating on the device.
Quote:
scriptable, simple, easy-to-use, non-bloated,
The latter is a bit rude to say as the driver isn't bloated. Whether calibre itself is bloated depends on your viewpoint. It's big, but it does a lot. Calibre is also scriptable.
Quote:
and provides fixes for many common kepub bugs. It also doesn't need to manage your whole library to work properly.

KTE is slower, but better integrated with Calibre (though kepubify will be getting plugin sometime this year). In addition, it supports the whole range of conversion options Calibre has. Some people also find it easier to use, as everything can be done from a GUI.

You can also use a mix of the two if you prefer. You can use kepubify to convert your books to kepub, but KTE to manage syncing them with your kobo.
If you are converting books to kepubs and keeping them in the calibre library, you don't need the extended driver. The base KoboTouch driver handles sending kepubs. And the extended driver doesn't add much when doing this. But you should add the kepub metadata reader and writer plugins.
Quote:
Also, kepubify comes with a standalone seriesmeta tool to update series metadata on all your books even if you don't use calibre to manage them.
I'm amused by the fact that this post is effectively telling people they don't need calibre, but, the seriesmeta tool relies on calibre specific metadata for the series info. But, it won't work ePub3 books. ePub3 has a definition for series info in the metadata and calibre uses that.

@forster01: I think it comes down to how you are managing your ebooks. If you use calibre, then use it to do the send-to-device. Whether that is via the KoboTouchExtended driver or a conversion to kepub, it doesn't matter much. If you are using other tools to manage your books, then kepubify makes more sense.
davidfor is offline   Reply With Quote