[Device Plugin] Kobo Touch Extended Driver

[Anyssia]

Originally Posted by JSWolf

What version plugin were you using before you reverted? What happens if you go into the edit with this eBook and check it with the editor error checker and epubcheck? If you have any errors and you fix them and then send it with the latest version, does it work?

Do you have access to a Windows system? If so, can you install calibre and the extended driver and try this eBook?

It could be because of some sort of error that the plugin is failing to convert to KePub or something to do with your Linux setup or the driver is borked since 3.6.7.

I was using 3.6.9 and reverted to 3.6.7.
edit this book and error checker/epub check came back clear.
I'm already on Windows 11

[JSWolf]

Originally Posted by Anyssia

I was using 3.6.9 and reverted to 3.6.7.
edit this book and error checker/epub check came back clear.
I'm already on Windows 11

I'll have to give 3.6.9 a go. I've not sent any KePub to my Libra 2 since 3.6.7.

But at least I know I can go back if need be. Thanks.

I'll post my findings.

[ownedbycats]

If it's of any help for troubleshooting, two ePubs downloaded with FanFicFare success kepubified and uploaded to device without errors.

[DNSB]

Originally Posted by ownedbycats

If it's of any help for troubleshooting, two ePubs downloaded with FanFicFare success kepubified and uploaded to device without errors.

From the sample ePub posted in the Kepub Output plugin thread, it seems to be an issue with HTML comments ( '<!-- This is a HTML comment -->' ) embedded in the text files.

See message #561 in the KePub Output Plugin thread for the original post

[jgoguen]

Version 3.6.10 should be offered by calibre within the next hour. This was caused by etree not following their own documentation, which was merry fun trying to chase down. But now there's also a test file including comments.

[JSWolf]

Originally Posted by jgoguen

Version 3.6.10 should be offered by calibre within the next hour. This was caused by etree not following their own documentation, which was merry fun trying to chase down. But now there's also a test file including comments.

Thank you very much for the fix. Sorry it was a pain to find out what was going on.

[norb]

I still get the Not a ZIP file error when i try to upload a PDF to my libra color using v3.6.10.
The same error as with v3.6.9.

calibre, version 7.16.0
ERROR: Error: Error communicating with device

Not a ZIP file

Traceback (most recent call last):
File "calibre\ebooks\oeb\polish\container.py", line 1181, in __init__
File "calibre\utils\zipfile.py", line 774, in __init__
File "calibre\utils\zipfile.py", line 809, in _GetContents
File "calibre\utils\zipfile.py", line 824, in _RealGetContents
calibre.utils.zipfile.BadZipfile: File is not a zip file

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "calibre\gui2\device.py", line 112, in run
File "calibre\gui2\device.py", line 646, in _upload_books
File "calibre_plugins.kobotouch_extended.device.driver" , line 342, in upload_books
File "calibre\devices\kobo\driver.py", line 2270, in upload_books
File "calibre_plugins.kobotouch_extended.device.driver" , line 152, in _modify_epub
File "calibre_plugins.kobotouch_extended.container" , line 117, in __init__
File "calibre\ebooks\oeb\polish\container.py", line 1188, in __init__
File "calibre\utils\localunzip.py", line 255, in extractall
File "calibre\utils\localunzip.py", line 242, in _extractall
ValueError: Not a ZIP file

downgrading to 3.6.7 fixes the problem.

[jgoguen]

Originally Posted by JSWolf

Thank you very much for the fix. Sorry it was a pain to find out what was going on.

Not your fault the lxml folks didn't follow their own documentation!

Originally Posted by norb

I still get the Not a ZIP file error when i try to upload a PDF to my libra color using v3.6.10.
The same error as with v3.6.9.

Can you create a bug on GitHub, include the full calibre debug log, and attach a PDF I can use to reproduce? Not one subject to copyright, if that's all you have I'll have to figure out another way to test a fix.

[norb]

Originally Posted by jgoguen

Can you create a bug on GitHub, include the full calibre debug log, and attach a PDF I can use to reproduce? Not one subject to copyright, if that's all you have I'll have to figure out another way to test a fix.

I created an issue with a debug log and added a PDF that produced the error for me.
Let me know if there is anything else that would help you figure this out.

That you for all the work you are doing!

[jgoguen]

Found it, I was creating an ePub container before verifying that I actually had an ePub-ish file. Version 3.6.11 should be offered by calibre within the next hour or so.

[Greyhunter]

Sorry to be late, as I wrote my last post just before going on holidays (aaaand then we decided to adopt a new kitten).

Everything is working well now, thank you very much for your quick support!

[giododa]

I hope I am writing in the right section of the forum.
I have a Kobo Libra H20 (firmware: 4.24.15676) and use Calibre 7.17 to handle my ebooks.
I use Kobotouchextended 3.6.11 driver to send Kepubs to the reader.
When I scroll "My books" list on the Libra I see that only a few books belonging to a serie display their metadata (in particular series' details) in different ways compared to others, as you can see in the attached file 1 and 2 (three books in the same serie).
In the third attached file you can see the plugboard template informations I am using.
I would like to see details as displayed in file 2.
There is any clue about this problem?
Thanks in advance for your attention.

[theducks]

Kobo handles series differently.
As you can see, there is no Kobo entry in my plugboard.
That is because the driver handles that natively .

But something to remember. Series (and some other metadata) is transferred on the SECOND connection. That is because the first disconnect is when the Kobo creates the Database entry it uses. The Second connect now has a place for the metadata to be stored.

[giododa]

Thank you, i will try.

[chaley]

Originally Posted by giododa

I would like to see details as displayed in file 2.

If you want what is shown in "file 2" where the series information is not in the title, remove the metadata plugboard that puts the series information into the title.