[Device Plugin] Kobo Touch Extended Driver

[taming]

I'm sorry to hear about your wrist. Do take care of it, not letting it heal could be a game changer for your career. And besides, it's probably yor baby holding arm as well. I assume that it's not just your wife who will be doing that .

[samhy]

Get better soon jgoguen (and congrats for the soon to be extended family )

[jgoguen]

Version 1.4.3 has been posted, coming soon to a calibre update notification near you!

Fixed in this release:

• Bug #66 - Do not add spaces after punctuation marks where there shouldn't be any.
• Bug #68 - Fix issues with multi-line comment nodes being mangled when smartening punctuation.

Thanks to everyone for the good wishes for my wrist and my family!

[gers1978]

Originally Posted by jgoguen

Version 1.4.3 has been posted, coming soon to a calibre update notification near you!

Fixed in this release:

• Bug #66 - Do not add spaces after punctuation marks where there shouldn't be any.
• Bug #68 - Fix issues with multi-line comment nodes being mangled when smartening punctuation.

Thanks to everyone for the good wishes for my wrist and my family!

All the best.

Should we still file bug reports in the meantime?

[Leonatus]

@jgoguen: I would like to attach myself to all those who wish you everything good for your wrist and family! Thanks for considering my problems in your last update!

Originally Posted by Leonatus

Hm, just coming from testing, but even more odd:
After switching on the standard driver (of course switching off the extended), I first fetched the book again, converted it and - just to try - applied the Hyphenate-This!-Plugin. Then sent to device.
Result: Issues showed above vanished, but instead, there are many, many punctuation marks of any kind (.,.,;,!, even quotation marks) that don't rest immediately after the last word of a line, but stand alone in the new line. Very ugly!

Removed the book, either from device as from bibliotheque. Fetched and converted the book again, now without using the Hyphenate-This!-Plugin.
Result: The same!

My God! What is this? Until now, I considered the basic driver as 'asset of the last resort' (please don't mind!) in the case that the Extended driver wouldn't work properly. But this time, the Extended works more consistent. Nevertheless, my impression is that's me who did something wrong.

As it's no longer the question of regex, I would prefer to report my experiences here, and no longer in the Sigil thread, where the point has been opended:

I formatted the book in question completely new and applied it then to the standard driver, and afterwards, to the extended driver. the problem seems indeed to have been the book itself, as both drivers now worked it out like a charm - no problems at all!

I added table formattings - no problem with both!

Then even dropcaps: no problem with the standard driver. The extended driver accepted (shows) them as well, but as soon as those dropcaps were added, the bookmark function of the extended driver would not work any more - don't see why.

At this opportunity I noticed that, switching on the "silently ignore .." option which would convert the book as epub, doesn't have in consequence to adopt the bookmark function as it works with the standard driver.

I'm not complaining, only reporting - I can easily live without dropcaps. But it's interesting to see that both drivers have their respective advantages so that they can be selected following the individual preferences. Great!

Only one question: the standard driver changes the page counting not at every page turn, but only after each second page turn. So, for example, page 256 remains and will only change into 257 after having read two "real" pages. Is there a way to control this?

[BobC]

Originally Posted by jgoguen

Version 1.4.3 has been posted, coming soon to a calibre update notification near you!

Fixed in this release:

• Bug #66 - Do not add spaces after punctuation marks where there shouldn't be any.
• Bug #68 - Fix issues with multi-line comment nodes being mangled when smartening punctuation.

Thanks to everyone for the good wishes for my wrist and my family!

I installed the update then restarted and got a notification that a new version was available. Installed that from the notification, restarted and it's Groundhog Day again - Calibre is still reporting 1.42 installed, 1.43 available.

Have I just been too quick off the mark or is there a problem with the issue number ?

BobC

[BobC]

Originally Posted by Leonatus

Only one question: the standard driver changes the page counting not at every page turn, but only after each second page turn. So, for example, page 256 remains and will only change into 257 after having read two "real" pages. Is there a way to control this?

This isn't a driver issue but relates to the different rendering engines used by the Kobo. If you use the standard driver you get a standard EPUB which is rendered using the Adobe renderer. Ones transfered with the extended driver will become "kepubified" and rendered using the Access renderer. Adobe counts a page as 1024 characters IIRC irrespective of the font size etc so 1 Adobe page doesn't correspond to 1 page displayed on the Kobo. The Access renderer is more intelligent and a page there is a page on your screen.

With the Adobe reader page 123 will be page 123 whatever size and type of font you are using. Not so with Access. Chose your driver and thus your rendering engine according to how you want to see your pages numbered.

HTH BobC

[Leonatus]

Thanks!

[jgoguen]

Originally Posted by gers1978

All the best.

Should we still file bug reports in the meantime?

Yes, absolutely, just understand that it may take me longer than usual to get around to replying and fixing it.

Originally Posted by Leonatus

Only one question: the standard driver changes the page counting not at every page turn, but only after each second page turn. So, for example, page 256 remains and will only change into 257 after having read two "real" pages. Is there a way to control this?

No, this is just the way each renderer handles page numbers. The ePub renderer gives you the estimated number of pages in the entire book based, I think, on a certain number of words per page. The KePub renderer gives you the number of page turns remaining in the currently loaded content file, which is usually the same as the number of page turns remaining in the current chapter but not always.

Originally Posted by BobC

I installed the update then restarted and got a notification that a new version was available. Installed that from the notification, restarted and it's Groundhog Day again - Calibre is still reporting 1.42 installed, 1.43 available.

Have I just been too quick off the mark or is there a problem with the issue number ?

BobC

I'd put money on that being my fault I bet I forgot to increment the driver version in the code. I'll fix that later today. Since you did the update, you've got the 1.4.3 code but you'll need to update again once I post the ZIP file with the correct version number.

[BobC]

Originally Posted by jgoguen

I'd put money on that being my fault I bet I forgot to increment the driver version in the code. I'll fix that later today. Since you did the update, you've got the 1.4.3 code but you'll need to update again once I post the ZIP file with the correct version number.

Yep - checked on Github container.py updated 10 hours ago, driver.py 8 days ago (same in my local copy). I've "fixed" my local copy of driver.py with the right version number and am no longer getting reminders.

Wishing your wrist a full recovery.

BobC

[Eno78]

Hi !

Sorry for my english, i'm french. ^^

First, thank you for your work. =) I use Kobo AuraHD (2.6.1) with Calibre (0.9.35) and KoboToucheExtended (1.4.3)

I have problems with the conversion epub / kepub.
- When I use the table of contents, the Kobo does not keep my page in memory.
- Some words or parts of sentences are deleted. There are at least with version 1.4.3.

Is there a solution?

Thank. =)

[Eno78]

Originally Posted by BobC

I installed the update then restarted and got a notification that a new version was available. Installed that from the notification, restarted and it's Groundhog Day again - Calibre is still reporting 1.42 installed, 1.43 available.

Have I just been too quick off the mark or is there a problem with the issue number ?

BobC

I had this problem and it was on account of my firewall.

[Martina Schein]

I want to install this plugin, but I've got the following error message:

calibre, version 0.9.36
ERROR: Failed to install the plugin: During the installation of the extension is a problem. This plugin is now removed. Please post the error message in detail below in the forum thread of this extension and restart Calibre new.

Traceback (most recent call last):
File "site-packages\calibre\gui2\dialogs\plugin_updater.py", line 728, in _install_clicked
File "site-packages\calibre\customize\ui.py", line 361, in add_plugin
File "site-packages\calibre\customize\ui.py", line 53, in load_plugin
File "site-packages\calibre\customize\zipplugin.py", line 167, in load
File "site-packages\calibre\customize\zipplugin.py", line 150, in load_module
File "calibre_plugins.kobotouch_extended.__init__", line 7, in <module>
ImportError: cannot import name KOBOTOUCHEXTENDED

[jgoguen]

Are you installing this for the first time or is this an upgrade? Are you installing by building the plugin manually or did you pick it from the list of plugins?

[Martina Schein]

I install this plugin for the first time and pick them from the list of plugins.