[GUI Plugin] Kobo Utilities

[bluepeter]

Originally Posted by DNSB

What timezone do you have configured under Setttings => Date and time => Time zone? Given you are in Britain, pick a large city near you. When I tested London, the timezone was set to UTC+1 which would appear correct for daylight savings time (BST) there

You've hit the nail on the head: I must have forgotten to set the timezone after the last factory reset, and didn't notice because the default was UTC. Once I set the time zone by selecting London, the clock started showing the right time.

Thank you very much.

[JSWolf]

There are at least two menu items that are labeled as shelves. Kobo changed the name to collections. So can anyplace where KU is using the obsolete and incorrect term shelves please be change to the correct term collections? Thanks.

[ownedbycats]

for what it's worth, the code is available on Github. You can change it yourself and submit a pull request.

EDIT: https://github.com/majutsushi/kobo-utilities/pull/16

[Majutsushi]

Thanks! I have actually been thinking about those features recently since as mentioned before some of them are probably obsolete.

Here is my current thinking:

• Order Series Shelves: Remove, obsoleted by the series functionality in the firmware.
• Get Shelves From Device: Remove, obsoleted by collections management in Calibre. I'm unclear on how this one-way sync would have been useful anyway.
• Manage Series Information: This one I'm less sure about. It uses the official series support in the firmware, but I wonder what use case there would be to manage the series information directly on the device, independently from the Calibre metadata. I checked the version history of the plugin and this feature has apparently been there almost from the beginning, about 2013. Maybe Calibre didn't support syncing series information back then? Is there any reason to still use this?

My current plan is to disable those features in the menu for now without actually removing them, and then if no one brings up a valid use case for a while to actually remove the code.

[ownedbycats]

Get Shelves from Device might be useful for if you already have set up Kobo collections on device and want to quickly bring into Calibre. Aside from this, not sure if any use.

[Terisa de morgan]

Originally Posted by Majutsushi

• Get Shelves From Device: Remove, obsoleted by collections management in Calibre. I'm unclear on how this one-way sync would have been useful anyway.

See message

[compurandom]

Originally Posted by Majutsushi

• Get Shelves From Device: Remove, obsoleted by collections management in Calibre. I'm unclear on how this one-way sync would have been useful anyway.

Please don't remove this. I don't use it often, but I've had a few cases where collections in calibre got messed up and I reimported them from the device.

Or I was offline and edited shelves heaviily on the device, and then imported them into a new column in calibre and merged the changes...

Or I had two libraries on distant desktops and used the device to copy the collections between them...

If anything, I'd like this feature enhanced somehow to merge collections into calibre tags, but it would be messy to implement that in any but the most simplistic way.

[JSWolf]

Before doing anything to the collections, make sure you're using the new code that changes shelves to collections. Thanks.

[ownedbycats]

Originally Posted by JSWolf

Before doing anything to the collections, make sure you're using the new code that changes shelves to collections. Thanks.

There was this response on pull request:

Thanks for your work! There are still a bunch of mentions of shelves in the dialogs, but as mentioned in the forum thread it probably makes sense to remove some of these features anyway, so no point in changing all of the strings for now.

[JSWolf]

Originally Posted by ownedbycats

There was this response on pull request:

The problem is that we have two different names for the same thing and that can cause confusion to some. So I do think it's best to use the term that Kobo uses so we don't have any confusion with newer users.

[PeterT]

Originally Posted by ownedbycats

for what it's worth, the code is available on Github. You can change it yourself and submit a pull request.

EDIT: https://github.com/majutsushi/kobo-utilities/pull/16

Do you also need to update the translations for the plugin? See https://github.com/majutsushi/kobo-u...ons/default.po

[bkennelly]

Another vote for keeping "Get Shelves from Device", at least until Calibre implements true, 2-way sync. (Unless I am doing something wrong, it currently only pushes from Calibre to Kobo and overwrites whatever was there.)

[JSWolf]

Originally Posted by PeterT

Do you also need to update the translations for the plugin? See https://github.com/majutsushi/kobo-u...ons/default.po

That depends if the which translations use shelves and which use collections.

[Steven Karp]

Okay, I've clearly screwed up.

I've got two Kobo readers, same model (one is mine, one is my spouse's). Until recently, I've used two different computers to update them, but now that I'm trying to consolidate and update them both from one computer (with two separate Calibre libraries), I'm running into trouble.

Kobo Utilities sees them both as being the same reader, which means I can't set up separate profiles for them. Both are detected as having a serial number ending in 429. Interestingly, when KU backs up the database, on one it names it with the 429 serial number and on the other, it names it as ending in 297. So at some level, it's recognizing the difference.

I suspect that at some point in the deep reaches of history, I copied the entire data directory from one to the other. But that was several thousand books ago, and I'd hate to have to wipe both devices and start fresh.

Is there a way to (a) figure out which one has the spurious serial number and (b) change it to the correct number WITHOUT factory resetting the device?

[PeterT]

Jon; the strings used in thr plugin are actually index's into the translation system. The strings in the plugin to be translated are written as _("string string string"). The exact same strings are then listed in the default translation template which is then used to create the actual translation. The translations are loaded from compiled version of the templates.

If the intent is NOT to worry about translation then then why even keep the translation stubs in the plugin (i.e. change the _('string string ') etc to 'sttring string.

Ignoring this is just another sign of sloppiness.