[Device Plugin] Kobo Touch Extended Driver

[Nick_1964]

Originally Posted by jgoguen

The main driver doesn't do any of the file manipulation my driver does. Even if you aren't making KePubs there's still a bunch of extra cleanup I do.

Upload two books that fail at https://www.dropbox.com/request/ggFXXxINqmQzzzY0HxUJ please.

To "solve" the problem I converted them with calibre and after that they did survived the transfer, but I found the 2 originals and send them..
I use your driver because it has the function to disable the hyphenation.


Book 2 Karen-Rose Niemand zeggen gives the error:
Failed to parse 'Karen Rose' by 'Niemand zeggen' with error: 'f225cb12131a.html' (file: calibre_plugins.kobotouch_extended.container, line: 172)

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 294, in upload_books
File "site-packages\calibre\devices\kobo\driver.py", line 1918, in upload_books
File "calibre_plugins.kobotouch_extended.device.driver" , line 231, in _modify_epub
InvalidEPub: Failed to parse 'Karen Rose' by 'Niemand zeggen' with error: 'f225cb12131a.html' (file: calibre_plugins.kobotouch_extended.container, line: 172)

[oren64]

Delete.

[jgoguen]

Much of the code is shared between the conversion and driver plugins, and the code for hyphenation and disabling hyphenation calls the same function whether its a conversion or sending a book to a device. The only way one should work and the other fail is if you have different options selected for each. Can you check that, for the ones in both places, you have the same options selected for the extended driver and the KePub conversion output plugin?

[Nick_1964]

Originally Posted by jgoguen

Much of the code is shared between the conversion and driver plugins, and the code for hyphenation and disabling hyphenation calls the same function whether its a conversion or sending a book to a device. The only way one should work and the other fail is if you have different options selected for each. Can you check that, for the ones in both places, you have the same options selected for the extended driver and the KePub conversion output plugin?

Yes, I did put some extra in the .css but if I disable the option,the result is the same..does it have something to do with an embedded .otf font ?? one of them has..
( I did send you the 2 books by the way)

[jgoguen]

The Kobo reader had problems with an embedded font, not sure if it still does, but even that was only a problem if you choose the "Document Default" font on the reader. The extended driver doesn't care about embedded fonts, it just ignores the font files during processing and leaves the font declarations in the content files alone.

[Nick_1964]

Originally Posted by jgoguen

The Kobo reader had problems with an embedded font, not sure if it still does, but even that was only a problem if you choose the "Document Default" font on the reader. The extended driver doesn't care about embedded fonts, it just ignores the font files during processing and leaves the font declarations in the content files alone.

Then I don't know where the error comes from, it is not on all books, about 48 of the 50 went without any troubles.. it just gives this error and an error "communicating with the device" (that sends me to a wrong path of searching into the usb drivers...) when I open the book that is transferred with the normal driver it doesn't give an error on the device itself..

[jgoguen]

I looked at the books and they both share a problem in the spine data: they reference a file that doesn't actually exist in the ePub. The error you posted only happens when it tries to load a file that isn't present (which itself only happens on poorly constructed books) and examining the books you sent me supports that.

I'll add some code when I get a chance to silently handle this case, but it's a problem with the creator of the book.

[Nick_1964]

Originally Posted by jgoguen

I looked at the books and they both share a problem in the spine data: they reference a file that doesn't actually exist in the ePub. The error you posted only happens when it tries to load a file that isn't present (which itself only happens on poorly constructed books) and examining the books you sent me supports that.

I'll add some code when I get a chance to silently handle this case, but it's a problem with the creator of the book.

Ebooks are in The Netherlands , sorry for the words, "a pain in the ass".
They try to create them with fonts that are not copyrighted but designed by their own.
Most of the time this are fonts that are not dark but more grey,they don't look sharp,they have all kinds of errors,2 times a front with picture in it and much much more problems.
99% of all the books selled by multiple vendors (like Bol.com or Kobo) are downloaded from one source "the central bookhouse" so the stores only works as a selling channel (frontend), you pay,get a link and the link downloads it from the central bookhouse" but they all use somekind of their own social DRM.
Some of them just add an "invisible" watermark, but others also change the internal html files to this watermark number.
Nothing wrong there, but it happens a lot that the social DRM doesn't work right so you get 2 kinds of errors:
1. Name is changed in the spine but the HTML files are not renamed.
2. Names are changed in the HTML but not in the spine.
They think, as long as the index is correct, the books are transferred correct, which they are with the Kobo desktop program.
They are also send wireless and there is no check or something so they are ok on the reader.
But at the moment you use Calibre and your plugin,the error stops the transfer. (just because the plugin works correct and does the check THEY should have done)
When you contact the vendor and try to point them at the problem,they just answer "we don't support Calibre" (or whatever other program you use).
Most of the time when an error occurs I first load it into Sigil and try to fix it there...
The truth for most bookstores here is that they don't like the epub's because they are so much pirated spread, they don't give any support and most of the time they release a paper book first and the ebook a couple of days or weeks later,so a lot buy the paper book instead..

Thank you for adding the "silent" mode.. giving the support the vendors must give actually.

[jgoguen]

So the font files wouldn't have been a problem here, though that sounds like a royal pain in the ass. Sounds like what caused the problem here is this "social DRM" had a file referenced in the spine not in the book. It would be interesting to look at the book in calibre's editor and see if it detects a file in the book not in the spine... maybe when I get a chance

[JSWolf]

Rule of ePub and Calibre plugins...

If you run a Calibre plugin on an ePub and you get an error message, run the ePub through epubcheck and the eBook checker in the eBook editor to see if its a problem with the ePub or the plugin.

The plugins require a structurally correct ePub and if they get ePub that's not correct, you can get error(s) with the plugin.

[Nick_1964]

Originally Posted by jgoguen

So the font files wouldn't have been a problem here, though that sounds like a royal pain in the ass. Sounds like what caused the problem here is this "social DRM" had a file referenced in the spine not in the book. It would be interesting to look at the book in calibre's editor and see if it detects a file in the book not in the spine... maybe when I get a chance

Most of the time I manage to make something of it by set the font weight to bold instead of normal so it is displayed a bit better but there are really terrible fonts used sometimes,the only other thing you can do is just let Calibre rip out the total font..most of the readers have their own set of fonts..
They have different versions of the social DRM, sometimes they use a hidden image where the image is set to base64 code,containing information about purchase,and put that in every file, sometimes the book get a visual warning with a number and they put the number in every file and rename the files with the number where the last 2 digits are the real page numbers (and i think that went wrong in this 2 books) but the most stupid is.. people just upload their books to usenet, adverting their hidden DRM like this and no antipiracy organisation get it out.. all the bookstores and publishers are screaming that epubs are so wide spread but they don't use the information in the books.
It now is legal under some conditions to sell your ebooks back to the store, who strips out your Social DRM and generate a new one when another person buys it, but most of the time they forgot to update the spine so the previous owner's data is still in the book. (author is being paid for every second hands ebook selling)
And when you sell your book back, you are supposed to remove your copy of the book from your device. (like someone will check you do... )
But at the next sync, Kobo pushes it back to your device because it isn't deleted from your account.
To make it even more strange, paper books have a price that is protected, as a book seller you are not allowed to sell it under the price that is agreed with the publisher, but with ebooks,the bookshop can make discounts because those books are not protected.
So they ruin the epub market theirself.

[Nick_1964]

Originally Posted by JSWolf

Rule of ePub and Calibre plugins...

If you run a Calibre plugin on an ePub and you get an error message, run the ePub through epubcheck and the eBook checker in the eBook editor to see if its a problem with the ePub or the plugin.

The plugins require a structurally correct ePub and if they get ePub that's not correct, you can get error(s) with the plugin.

Yes.. but when plugin one says nothing, plugin 2 says "error while communicating to the device" you don't suspect the book is not correct, now I know the error, I will check the book.. 90% of all the books sold here, gives errors..

[JSWolf]

Originally Posted by Nick_1964

Yes.. but when plugin one says nothing, plugin 2 says "error while communicating to the device" you don't suspect the book is not correct, now I know the error, I will check the book.. 90% of all the books sold here, gives errors..

So fix the errors and then see if the plugin error(s) disappear. If not, then report the error(s).

[Nick_1964]

Originally Posted by JSWolf

So fix the errors and then see if the plugin error(s) disappear. If not, then report the error(s).

Jgoguen did something better,adapted the plugin. Solved, Thank you.

[davidfor]

Originally Posted by Nick_1964

Jgoguen did something better,adapted the plugin. Solved, Thank you.

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.