[Device Plugin] Kobo Touch Extended Driver

[jgoguen]

No, the change I made stops the plugin from failing if the spine points to a nonexistent file.

[Nick_1964]

Originally Posted by davidfor

Except that the fix is a workaround. It means the changes you wanted as the book was sent to the device will not be done. No conversion to kepub, no fiddling with the CSS. If you want that, you need to fix the book.

Yes, I understand, I checked the last 50 books that are send to calibre, ALL 50 has problems like problems with entity (alien in the book ? ) with fonts that are called but not present,font names that are described but not actually in the book ( like css font family name Fontin-regular does not match the actual fontname Fontin )
FOUT: CSS: Property: Invalid value for "CSS Level 2.1" property: 0.75 em [257:5: margin-bottom]****[OEBPS/Styles/template.css]
FOUT: CSS: Property: Invalid value for "CSS Level 2.1" property: 1em 3 1em 3 [268:2: margin]****[OEBPS/Styles/template.css]

Name it.. every book that you buy here has problems.. mainly because they use one default css and adapt some values for the book but don't change the rest... or they rename files because of the social DRM but don't adapt the spine.
While auto-repair doesn't fix all, or just destroy the whole book.

About my initial post here,because the error was telling about problems with communication to the device, I didn't searched for a mistake in the book.
Not to make any critcial statement,if the error was "something is wrong with the book" I would look into it.
So I was a bit misled by the error.

From the autor of the plugin I understand that it does make the settings i want,but skips the error,and continue, so it is not a workaround.
I don't use the kepub, i use the plugin only because of the hyphenation setting.
I buy about 10 books a week because I am a lot in the hospital, some books are directly transferred by the bookshop to my device, so even when it contains errors I can't change it when i am in the hospital, when I change it while the book is in the device (otg cable on tablet,rename the epub to zip and do it manually) it erase all settings and the book shows up new.. 99% of all customers (I guess) doesn't know of all the errors inside "as long as it displays.." you know..
When I had used the normal driver, I wasn't warned about the issues anyway..
I will look more into the books to find errors buth which one are critical and which one isn't, and how do I fix it without introducing new ones....I bought a new one this afternoon and it contains 22 errors.. with more then 2200 books in my calibre database.

And to continue this long story (almost an ebook) most errors are translated into my language,make it almost impossible to find something back on Google.. I read, I am not an ebook professor.. almost feel like I am into court because I asked a question about the plugin..

[Nick_1964]

New book bought 3 minutes ago (as we don't use normal DRM you don't download it trough ADE,you just get a link that open a normal download in Chrome)

22 errors.
After first automatic repair it contains still errors,
After second automatic repair it contains still errors..
Where to begin..

[JSWolf]

Originally Posted by Nick_1964

New book bought 3 minutes ago (as we don't use normal DRM you don't download it trough ADE,you just get a link that open a normal download in Chrome)

22 errors.
After first automatic repair it contains still errors,
After second automatic repair it contains still errors..
Where to begin..

Begin in English as I cannot help if I cannot understand the error messages.

[Nick_1964]

Never mind, thank you for changing the plugin jgoguen.

[brydon10]

So does this driver automatically convert epubs to kepubs the same way manually converting the files would? Or does it just rename the extension? I tried using the driver to auto-convert and send a rather large epub file to my kobo glo, and the file wouldn't open, I had to force restart my glo.

I then tried manually converting the epub to kepub, then sending to the device with the regular driver. It worked perfectly.

[jackie_w]

Nevermind. Leave it to the experts.

[jgoguen]

Assuming you start with an ePub both ways, the code used to convert via driver or calibre conversion is identical. If you start with anything else, it's converted using the calibre conversion to ePub then to KePub. Either way, going from any source format to KePub via driver should be identical to converting in calibre and then using the driver (or even manually sideloading the converted KePub).

[brydon10]

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.

[davidfor]

Originally Posted by brydon10

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.

[jgoguen]

I should have been clear, the KePub code is identical. The driver unpacks the ePub, does some cleanup (you can see what by looking at the driver options), and adds the Kobo spans. The conversion process runs all of calibre' standard conversion to ePub (and you can convert ePub to ePub) and then runs the driver's KePub code against that unpacked converted ePub.

I'd like to get the ePub that generates the KePub that's causing the Kobo to crash. Could you upload it to https://www.dropbox.com/request/YS51qPlpvXcndymRhlfO please?

[brydon10]

Sure jgoguen. Done.

[TheKillingBean]

Plugin doesn't work anymore with the latest update from Calibre. When I transfer the files to the Kobo Glo HD I get the following error:


'KOBOTOUCHEXTENDED' object has no attribute 'OPT_MODIFY_CSS'

Traceback (most recent call last):
File "site-packages/calibre/gui2/device.py", line 87, in run
File "site-packages/calibre/gui2/device.py", line 584, in _upload_books
File "calibre_plugins.kobotouch_extended.device.driver" , line 250, in upload_books
AttributeError: 'KOBOTOUCHEXTENDED' object has no attribute 'OPT_MODIFY_CSS'

[davidfor]

In calibre v2.60, I have made major changes to the KoboTouch driver. These will be mainly visible in the configuration dialog. Unfortunately, these changes have broken the extended driver. I had discussed these changes with jgoguen and we had planned an updated to the driver. But, we have gotten the timing wrong. Kovid has been releasing calibre every two weeks recently, so I was expecting another week. But, the release timing is about having enough changes for it to be worthwhile, so I should have planned better.

Attached to this post a version of the extended driver that will work with calibre 2.60. It has the changes to make it work, but does not take full advantage of the changes in the configuration dialog. This will be here until jgoguen has a chance to make an official release.

Edit: There might be a problem with the driver configuration caused by using the incompatible versions. If you see an error opening the configuration of the extended driver after installing the attached version, please close calibre and delete the configuration file. This is in the calibre configuration directory and is called "device_drivers_KOBOTOUCHEXTENDED.py".

[Martina Schein]

Thank you David for this Beta driver. It works fine. Now I can copy my eBooks again by Calibre on my "Kobo Aura H2O" without I get the issue raised by TheKillingBean error message.