[Device Plugin] Kobo Touch Extended Driver

[jgoguen]

Open calibre, go to Preferences, Plugins, check the box for user-installed plugins (right above the list), expand the device drivers list, and double-click KoboTouchExtended. I'm on my phone, not near a computer, so it's possible some of those directions won't be the exact names you're looking for.

Is there a particular reason why you want to save each converted KePub? Depending on what you're trying to accomplish, there may be a simpler way than using this debugging option.

[stumped]

Originally Posted by jgoguen

Is there a particular reason why you want to save each converted KePub? Depending on what you're trying to accomplish, there may be a simpler way than using this debugging option.

no - I am happy to turn it off, with your guidance. I was concerned that the settings had it writing to some folder whose name I had forgotten, so there could be a missing folder crash.
I think when i first used it I was curious to see that the files looked like, so I enabled it, & forgot about it...
...
i see I almost found it - i did not inspect all the tabs - so it's the final tab- called extended.
in there I should just blank the entry for
copy generated Kepub files to a directory [ I had C:/test in there , I see ],
I will assume yes, unless you post otherwise

[Tom8o]

Originally Posted by davidfor

The problem has been seen before. A search of the extended driver thread, suggests it is something to do with the Windows username. The username probably has non-ASCII characters in it.

The error is happening when it uses the temporary directory. Changing that in Windows to point elsewhere will probably fix it. Or set the environment variable CALIBRE_TEMP_DIR to point to a suitable directory for calibre to use

I tried to do so- I set two environment variables called CALIBRE_TEMP_DIR (one in System Variables and one in User Variables), both to C:\CALTEMPDIR, but for some reason the log still calls some other path, after which the error shows up:

Copying file 'C:\CALTEMPDIR\calibre_sxsvzh\kepub_nwtglg_stylehacks' to 'C:\CALTEMPDIR\calibre_sxsvzh\c5xevi_epub_container' as 'kte-css/stylehacks.css'
Adding reference to kte-css/stylehacks.css to file text/part0000.html
C:\Program Files (x86)\Calibre2\pylib.zip\ntpath.py:532: UnicodeWarning: Unicode unequal comparison failed to convert both arguments to Unicode - interpreting them as being unequal
Python function terminated unexpectedly
  All strings must be XML compatible: Unicode or ASCII, no NULL bytes or control characters (Error Code: 1)

I am not sure if I did the exact thing, so here are a couple pictures of the "Environment Variables..." window (including part of my username which is likely to be causing the ASCII error, heh):





No idea what to do next, I feel like the next step is to keep Calibre from calling that Calibre2 directory (C:\Program Files (x86)\Calibre2\pylib.zip), but seeing as how it seemingly is where Calibre is installed, I have no idea what to do. Perhaps the folder shouldn't be directly in C:\ ?

[jgoguen]

That's it, just make that blank and it won't try to save generated files to a separate folder.

[BetterRed]

You shouldn't need C:CALTEMPDIR in your System EnvVar 'Path'. But you should have C:\Program Files (x86)\Calibre2\ in there.

But I doubt that's causing the problem.

About 2.5 million of people run calibre from the standard Windows install folders (Program Files and Program Files (x86), and most are from non English speaking countries, see ==> calibre - Usage Statistics for calibre. Many would have diacritics etc in their user names.

You could try installing the Portable version of calibre - its completely self-contained. If the conversion fails using it, then that would suggest it's not a Windows related issue. Installing the Portable version will not interfere with your installed version - if you install on on a thumb drive you can use it on another computer.

BTW: I can't see your launchpad post - probably because its marked Private to protect an attachment. Not a problem.

BR

[Tom8o]

Originally Posted by BetterRed

You shouldn't need C:CALTEMPDIR in your System EnvVar 'Path'. But you should have C:\Program Files (x86)\Calibre2\ in there.

But I doubt that's causing the problem.

About 2.5 million of people run calibre from the standard Windows install folders (Program Files and Program Files (x86), and most are from non English speaking countries, see ==> calibre - Usage Statistics for calibre. Many would have diacritics etc in their user names.

You could try installing the Portable version of calibre - its completely self-contained. If the conversion fails using it, then that would suggest it's not a Windows related issue. Installing the Portable version will not interfere with your installed version - if you install on on a thumb drive you can use it on another computer.

BTW: I can't see your launchpad post - probably because its marked Private to protect an attachment. Not a problem.

BR

Well, the Launchpad thing shouldn't be a problem seeing as it's the exact text as the body of this post and a public domain book from Amazon.

Tried portable, but it gave me this error:


Oh well. Tried it on another account on the same computer which didn't have any non-ASCII in its name, and that worked! Sent it over, and it worked beautifully (save for displaying a couple punctuation marks incorrectly). I guess I'll make do with that for now.

[trinity1]

BTW, since I had issues with epub removed from my Kobo Glo shelves (whenever I connect the Glo to the PC-Calibre), I removed the plugin (as well as the config file), but Calibre 2.68 still removes my epubs from the shelves onto the device... So, I don't think it's a plugin issue.

[BetterRed]

@Tom8o - where did you install portable - if it was somewhere in your %userprofile% directory I suspect it too was struck down by the non-ASCII chars in the file path.

But I can't understand why you and not many, many other people.

@davidfor - if this is a plugin related issue, then if you tell me which one I'll merge this thread into it. I try to keep loose threads to a minimum in the PI subforum - like Florida does with hanging chads

BR

[davidfor]

Originally Posted by trinity1

BTW, since I had issues with epub removed from my Kobo Glo shelves (whenever I connect the Glo to the PC-Calibre), I removed the plugin (as well as the config file), but Calibre 2.68 still removes my epubs from the shelves onto the device... So, I don't think it's a plugin issue.

No, it's a driver configuration issue. You have configured the driver to manage collections. This is done whenever you connect. If you don't want the collections to be managed from calibre, turn the option off. Otherwise, you need to adjust them to do what you want.

Of course, it is possible there is a bug in the driver. (Well, actually there is, but it won't have the effect I thing you are describing.) If you have the driver configured correctly and the the collections seem to be messed up, I need a debug log. Run calibre in debug mode, connect the device and let the connection jobs run. Then close calibre and post the log displayed or PM it to me. And give me the name of a book and collection that is being being messed up and how it is. I can usually tell from the log what is going wrong.

[davidfor]

Originally Posted by Tom8o

Oh well. Tried it on another account on the same computer which didn't have any non-ASCII in its name, and that worked! Sent it over, and it worked beautifully (save for displaying a couple punctuation marks incorrectly). I guess I'll make do with that for now.

In that case, it sounds like there is a problem in how you did the environment variables. You don't need the temp directory in the PATH, but I doubt that is causing a problem. With the CALIBRE_TEMP_DIR set, it might be useful to see the full log.

@BetterRed: This is a problem with the KoboTouch Extended Driver. You can merge it into that thread.

[BetterRed]

Originally Posted by davidfor

@BetterRed: This is a problem with the KoboTouch Extended Driver. You can merge it into that thread.

Moderator Notice
Duly Done

[trinity1]

Originally Posted by davidfor

No, it's a driver configuration issue. You have configured the driver to manage collections. This is done whenever you connect. If you don't want the collections to be managed from calibre, turn the option off. Otherwise, you need to adjust them to do what you want.

Of course, it is possible there is a bug in the driver. (Well, actually there is, but it won't have the effect I thing you are describing.) If you have the driver configured correctly and the the collections seem to be messed up, I need a debug log. Run calibre in debug mode, connect the device and let the connection jobs run. Then close calibre and post the log displayed or PM it to me. And give me the name of a book and collection that is being being messed up and how it is. I can usually tell from the log what is going wrong.

if for "collections messed up" you mean that - whenever I connect Kobo with Calibre - ALL my books are removed from the collections (which I have manually created, and in which I want to decide whether to include a book or not), well, the collections are messed up.
I thought it was a Calibre issue because when I uninstalled the plugin, the problem was still there (or there was some file to be manually deleted after unistalling the plugin? Like, “device_drivers_KOBOTOUCHEXTENDED.py”, which wasn’t deleted after the plugin unistall)
(Noob) Question 1: I have Windows 10 (64bit). How can I let Calibre run in debug mode?
Question 2: if I use the kobotouchextended is there any other plugin which has to be unistalled due to possible conflicts?

[davidfor]

Originally Posted by trinity1

if for "collections messed up" you mean that - whenever I connect Kobo with Calibre - ALL my books are removed from the collections (which I have manually created, and in which I want to decide whether to include a book or not), well, the collections are messed up.

If after connecting to calibre, the collections change, then that means the driver is configured to manage collections. Open the driver configuration and look at the options.

I thought it was a Calibre issue because when I uninstalled the plugin, the problem was still there (or there was some file to be manually deleted after unistalling the plugin?

It probably means you had both the extended driver and the KoboTouch driver configured for collection managment.

Like,
“device_drivers_KOBOTOUCHEXTENDED.py”, which wasn’t deleted after the plugin unistall)

Uninstalling plugins does not remove any configuration. But, there won't be anything using it, so there is no harm

(Noob) Question 1: I have Windows 10 (64bit). How can I let Calibre run in debug mode?

Right-click on the preferences button and select "Restart in debug mode".

Question 2: if I use the kobotouchextended is there any other plugin which has to be unistalled due to possible conflicts?

Only the KoboTouch driver. They both manage the same devices. Usually if both are enabled, then extended driver is used, but, I prefer not to risk it.

[trinity1]

Thanks. I want to give another chance to Kobo touch extended. So, I will disable Kobo touch, install Kobo touch extended again, [run calibre in debug mode], configure it and then see what happens.

In the meanwhile, thanks for your support.

Tapatalked from LeeDroidROM-powered HTC One M8

EDIT: of course it was as you said. Disabled kobo touch, checked kobotouch extended settings, everything works.

[davidfor]

Originally Posted by trinity1

Thanks. I want to give another chance to Kobo touch extended. So, I will disable Kobo touch, install Kobo touch extended again, [run calibre in debug mode], configure it and then see what happens.

In the meanwhile, thanks for your support.

Tapatalked from LeeDroidROM-powered HTC One M8

EDIT: of course it was as you said. Disabled kobo touch, checked kobotouch extended settings, everything works.

Good to hear it is working.