Thread: [Device Plugin] Kobo Touch Extended Driver
View Single Post
Old 06-04-2016, 08:42 PM   #1540
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,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by brydon10 View Post
Thanks jackie and jgoguen.

I thought it should be the same process too, just automated. Maybe it was the epub file. I'll have to try it again with another one and see what happens.

Edit: Well, I just tried to transfer a small 500kb epub with Kobo Touch extended. It sent very fast, which makes me think it's not converting properly. However, it was renamed to a kepub. The file worked somewhat, but it still froze when navigating around the table of contents and my Glo restarted itself. It must be a problem with my configuration.
There is a difference between converting the book to kepub and sending the epub as a kepub using the driver. The driver doesn't use the full conversion pipeline. It "simply" processes each file in the epub to add the spans necessary for navigation on the device. This also means the driver is probably faster sending the book than a conversion plus a send.

What that means is that if there are problems in the epub, the conversion might fix them. But, the driver probably won't. One thing it doesn't do is touch the ToC. If that is broken in the epub, it will be broken in the kepub the driver sends. But, the conversion will probably fix it. The restart while navigating is probably related to this.

What I would suggest is opening the epub in the calibre editor and using the error checking tool to look for problems. Or, do an epub-to-epub conversion and then sending that to the device using the extended driver.
davidfor is offline   Reply With Quote