[Device Plugin] Kobo Touch Extended Driver

[davidfor]

Originally Posted by snowstone

Right now my computer stopped recognizing my Kobo... Not sure what happen. I have yet to try it today. Hopefully it will be fixed itself by rebooting.

By the way, I never needed to install "KePub Metadata Reader" and "KePub Metadata Writer", it always worked without them. Do you think I should install them?

Firstly, those are not needed unless you store kepubs in your library.

When you say, "computer stopped recognizing my Kobo", do you actually mean that? Or do you mean that calibre stopped seeing it? They are very different things. If the former, there is nothing in this plugin or calibre that can help. You need to work out why it is happening. I would recommend asking in the Kobo forum.

If it is calibre, were there any errors? Does the computer see it? Can you write to the device without calibre?

[snowstone]

Originally Posted by davidfor

Firstly, those are not needed unless you store kepubs in your library.

When you say, "computer stopped recognizing my Kobo", do you actually mean that? Or do you mean that calibre stopped seeing it? They are very different things. If the former, there is nothing in this plugin or calibre that can help. You need to work out why it is happening. I would recommend asking in the Kobo forum.

If it is calibre, were there any errors? Does the computer see it? Can you write to the device without calibre?

It was the actual laptop. I still haven't tested it today. I read sometimes this happens with kobo.

On the plugins, no I keep all my books as epub, only convert when I send to kobo, so I can keep using the reading stats. In that case I'll continue to use only this plugin.

Thanks for the answer, and for your work on the plugin

[jgoguen]

Originally Posted by Leonatus

Same error message as before.

Can you get the full stack trace? Line numbers may have changed, I want to make sure I'm looking in the right place.

[Leonatus]

calibre, version 4.16.0
FEHLER: Fehler: Fehler beim Kommunizieren mit dem Gerät

'utf8' codec can't decode byte 0xe4 in position 31: invalid continuation byte

Traceback (most recent call last):
  File "site-packages\calibre\gui2\device.py", line 90, in run
  File "site-packages\calibre\gui2\device.py", line 513, in _books
  File "site-packages\calibre\devices\kobo\driver.py", line 1565, in books
  File "site-packages\calibre\devices\kobo\driver.py", line 3542, in get_debugging_title
  File "site-packages\calibre\devices\kobo\driver.py", line 3264, in get_pref
  File "calibre_plugins.kobotouch_extended.device.driver", line 113, in settings
  File "calibre_plugins.kobotouch_extended.common", line 95, in print_formatted_log
  File "calibre_plugins.kobotouch_extended.common", line 84, in _tag_args
UnicodeDecodeError: 'utf8' codec can't decode byte 0xe4 in position 31: invalid continuation byte

Of course:

[JSWolf]

Originally Posted by darthyoda6

Upgrading is easy. Liking how everything is changed is hard. I've tried upgrading to Windows 10 several times, and I keep having to go back to Windows 8.1.

Why do you have to keep going back to Windows 8.1?

[JSWolf]

Originally Posted by snowstone

It was the actual laptop. I still haven't tested it today. I read sometimes this happens with kobo.

With my H2O, it's never happened on Windows 10, Windows 7, and Windows 8.1.

[snowstone]

Originally Posted by JSWolf

With my H2O, it's never happened on Windows 10, Windows 7, and Windows 8.1.

I don't know the reason, even when I had a Kobo Glo, it sometimes happened. Some say it can be the cables used, or the usb ports. I have no idea why it happens, but it happens on occasion. But since I only have to connect my Kobo ever so often to upload new ebooks, it usually doesn't bother me much. It's still annoying when it happens.

Right now, the laptop recognizes the kobo. Again, weird. But since it works most of the time, not much to complain.

[jgoguen]

Originally Posted by kovidgoyal

@jgoguen: I would suggest using the calibre prints() function to print or alternately to check for bytes in the log object you are using and force them to unicode.

Today I learned prints() isn't just a wrapper for print() in the Stream classes!


Looking at that shows where I'm going wrong, I'm expecting to need Unicode strings but from the way calibre.prints() works I actually need to be returning bytes instances. I'll work on changing the code to use calibre.prints(), thanks!

[jgoguen]

Windows testers, here's another package to try out.

[patrickchung]

Originally Posted by jgoguen

Windows testers, here's another package to try out.

thanks a lot
this version work fine for me.
Win10 64Bits Chinese Language.

[DNSB]

Quick test here after removing the workaround and no issues with a VM using Canadian French as the system language (Win 10 x64 2004).

[jgoguen]

New version posted. If I recall the update schedules correctly, calibre should start offering it sometime in the next hour or so. Amazing how well things work when you give it the right data!

Someone tell Microsoft 1991 called, they want their "Unicode is in beta" nonsense back.

Thanks to everyone who tested multiple versions, Kovid for pointing me at calibre.prints(), and the rest of you for your patience with this. Hopefully this is the last time Unicode is an issue here before Python 2 calibre is retired.

[Leonatus]

Everything is working well again! Thank you so much, Joel!

[davidfor]

Originally Posted by snowstone

It was the actual laptop. I still haven't tested it today. I read sometimes this happens with kobo.

If by that you mean the laptop isn't seeing the device, then you need to fix that before calibre will see it. The usual culprits are issues with the USB port or the cables. Rebooting the computer and the device can help. Other reasons will depend on the OS. MACs have had something change in the permissions recently that seems to be popping up. Linux has a single app access issue. MS likes to screw with Windows at least once a year.

[bansheeat]

Thanks again for you hard work jgoguen. It works now