[GUI Plugin] Kobo Utilities

[sparajoy]

I just got my Clara Colour today, tested out the new plugin and everything seems to be working as expected so far! Set reader font worked correctly and everything, saw the new fonts when i checked for them

[JSWolf]

Originally Posted by ownedbycats

That's how it already works. I'm running the test version myself and the fonts are still available on older firmware.

KOBO_FONTS = {
            (0, 0 ,0): { # Format is: Display name, setting name
                 'Document Default':  'default', 
                 'Amasis':            'Amasis', 
                 'Avenir':            'Avenir Next', 
                 'Caecilia':          'Caecilia',
                 'Georgia':           'Georgia', 
                 'Gill Sans':         'Gill Sans', 
                 'Kobo Nickel':       'Kobo Nickel', 
                 'Malabar':           'Malabar', 
                 'Rockwell':          'Rockwell', 
                 'Gothic':            'A-OTF Gothic MB101 Pr6N', 
                 'Ryumin':            'A-OTF Ryumin Pr6N', 
                 'OpenDyslexic':      'OpenDyslexic', 
                 },
            (3, 19, 0): { # Format is: Display name, setting name
                 'Document Default':     'default', 
                 'Amasis':               'Amasis', 
                 'Avenir':               'Avenir Next', 
                 'Caecilia':             'Caecilia',
                 'Georgia':              'Georgia', 
                 'Gill Sans':            'Gill Sans', 
                 'Kobo Nickel':          'Kobo Nickel', 
                 'Malabar':              'Malabar', 
                 'Rockwell':             'Rockwell', 
                 'Kobo Tsukushi Mincho': 'KBJ-TsukuMin Pr6N RB', 
                 'Kobo UD Kakugo':       'KBJ-UDKakugo Pr6N M', 
                 'OpenDyslexic':         'OpenDyslexic', 
                 },
            (4, 13, 12638): { # Format is: Display name, setting name
                 'Document Default':     'default', 
                 'Amasis':               'Amasis', 
                 'Avenir':               'Avenir Next', 
                 'Caecilia':             'Caecilia',
                 'Georgia':              'Georgia', 
                 'Gill Sans':            'Gill Sans', 
                 'Kobo Nickel':          'Kobo Nickel', 
                 'Malabar':              'Malabar', 
                 'Rockwell':             'Rockwell', 
                 'AR UDJingxihei':       'AR UDJingxihei', 
                 'Kobo Tsukushi Mincho': 'KBJ-TsukuMin Pr6N RB', 
                 'Kobo UD Kakugo':       'KBJ-UDKakugo Pr6N M', 
                 'OpenDyslexic':         'OpenDyslexic', 
                 },
            (4, 34, 20097): { # Format is: Display name, setting name
                 'Document Default':     'default', 
                 'Amasis':               'Amasis', 
                 'Avenir':               'Avenir Next', 
                 'Caecilia':             'Caecilia',
                 'Georgia':              'Georgia', 
                 'Gill Sans':            'Gill Sans', 
                 'Kobo Nickel':          'Kobo Nickel', 
                 'Malabar':              'Malabar', 
                 'AR UDJingxihei':       'AR UDJingxihei', 
                 'Kobo Tsukushi Mincho': 'KBJ-TsukuMin Pr6N RB', 
                 'Kobo UD Kakugo':       'KBJ-UDKakugo Pr6N M', 
                 'OpenDyslexic':         'OpenDyslexic', 
                 'Rakuten Serif':        'Rakuten Serif',
                 'Rakuten Sans':         'Rakuten Sans',                    
                 },     
				 
            (4, 39, 22801): { # Format is: Display name, setting name
                 'Document Default':     'default', 
                 'Atkinson Hyperlegible':'Atkinson Hyperlegible', 
                 'Bariol':               'Bariol', 
                 'Bitter':               'Bitter',
                 'Caecilia':             'Caecilia',
                 'Gill Sans':            'Gill Sans', 
                 'Kobo Nickel':          'Kobo Nickel', 
                 'Malabar':              'Malabar', 
                 'Noto Sans':            'Noto Sans',
                 'Texturina':            'Texturina',
                 'AR UDJingxihei':       'AR UDJingxihei', 
                 'Kobo Tsukushi Mincho': 'KBJ-TsukuMin Pr6N RB', 
                 'Kobo UD Kakugo':       'KBJ-UDKakugo Pr6N M', 
                 'OpenDyslexic':         'OpenDyslexic', 
                 'Rakuten Serif':        'Rakuten Serif',
                 'Rakuten Sans':         'Rakuten Sans',     
                 'Ubuntu':               'Ubuntu',	
                 'Vollkorn':             'Vollkorn',				 
                 },

Gotcha. Thank you.

[Enebat]

I use Kobo Utilities, and I have it set to show me that old Shelves column that is now Collections.
So far so good, but I would like to add a new tab with other data that is also text, neither date, nor percentage, nor rating.
Is there a way to add more tabs similar to #Shelf?

[theducks]

Utilities is just a middleman between Calibre and the Kobo.
It can't have a (Calibre) column for something that does not exist ON THE KOBO, nor put something from Calibre anyplace EXCEPT a supported location.

You CAN use the (Calibre) Metadata Plugboard to fudge additional Calibre data into a standard Kobo field. Just be aware that too much fudge will break other interactions.

[Quoth]

As well as reading for fun I proof read epub originated in LO Writer via odt -> docx ->Calibre epub.

So I make short notes with big highlights. These are saved as text files to view while editing in LO Writer. They are never synced nor copied into the epubs in Calibre or saved in Calibre, that would be varyiing from disastrous to pointless.

I discovered that if the Calibre record has no formats (like they have been deleted so an outdated version isn't copied to an ereader), the Kobo Utilities gives a blank window when attempting to read Annotations etc for an ebook on the ereader. Putting ANY epub file (maybe any file?) in the ebook record on Calibre allows the annotation to appear in the popup window and be copy/pasted into my text editor, which years ago was Notepad++, but now is KATE.

Though reading annotations by this method for years, I first encountered this this week. The Kobo Database was OK and as another title that still had formats could have annotations read, I guessed that adding a file to Calibre would re-enable the Annotation fetching.


Not sure if this a bug or intentional, but I'd never ever want to copy reading position/bookmarks/highlights/notes into the actual epub file in Calibre. I disabled that in the Viewer years ago. I have columns for reading status etc and haven't stored annotations in Calibre since changing from Kindle to Kobo.

I know about adding a menu on the Kobo and text export there, but finding a title in Calibre and import to clipboard from ereader is more convenient.

[sparajoy]

Originally Posted by ownedbycats

Beta Version 2.16.14
Warning: Experimental!

For Firmware 4.39.22801 (for Libra Colour, Clara BW, and Clara Colour), this ideally should enable the new fonts in 'Set Reader Fonts for Selected Books.' I have not tested this personally as I have not those devices.

If anyone using the new firmware would care to test this (or buy me a new reader - just kidding! ), it would be greately appreciated. Mostly checking that the new fonts actually set correctly - some of them might have different internal names as used in the content_settings table, and there's some weirdness around Bariol possibly only being available for Tolinos.

I made the changes by the list on this github issues:

Additions: Atkinson Hyperlegible, Bariol, Bitter, Noto Sans, Texturina, Ubuntu, and Vollkorn.
Removals: Georgia, Avenir, Amasis.

Some further testing on my Clara Colour, not sure if this is related to the driver support for the new database formats or else something hinky going on in the plugin itself. Every time I connect my device, all files that have a reading position and last opened date on them are registering as having "new" data, even though the values are unchanged. It is accurately catching real changes, but I'm having to sift through a couple hundred entries every time to confirm actual new data.

I might be able to poke around in the code this weekend and see if I can dust the cobwebs off my python skills, but figured I'd surface it here as well in case anyone else wants a look.

[ownedbycats]

I think I know what happened here, as it also happened to me when upgrading to my Libra H2O: Check the profiles in the Customize Kobo Utilities dialog, devices tab. Make a new one for the colour device. Then check this option:

[sparajoy]

Originally Posted by ownedbycats

I think I know what happened here, as it also happened to me when upgrading to my Libra H2O: Check the profiles in the Customize Kobo Utilities dialog, devices tab. Make a new one for the colour device. Then check this option:

Attachment 208018

That's exactly what it was thank you - that'll learn me to mess around in plugin settings before I've had my coffee

[nichobi]

Noticed that the plugin wasn't working for me after upgrading to Python 3.12, and trying to change the settings kept giving me a popup saying I had to restart calibre before customising. Turns out this is because of the removal of the SafeConfigParser alias, which has been deprecated since 3.2. Replacing all instances of

SafeConfigParser

with just

ConfigParser

in the .py files in the plugin .zip file seems to be enough to get it running again

[JSWolf]

Originally Posted by nichobi

Noticed that the plugin wasn't working for me after upgrading to Python 3.12, and trying to change the settings kept giving me a popup saying I had to restart calibre before customising. Turns out this is because of the removal of the SafeConfigParser alias, which has been deprecated since 3.2. Replacing all instances of

SafeConfigParser

with just

ConfigParser

in the .py files in the plugin .zip file seems to be enough to get it running again

Will that work with the Windows version of calibre as Python is bundled with it?

[DNSB]

Originally Posted by JSWolf

Will that work with the Windows version of calibre as Python is bundled with it?

As far as I am aware, the only calibre versions that use an external Python install are various Linux distros, otherwise you need a custom build. Normally calibre uses it's bundled Python to avoid issues such as the OP's.

[Majutsushi]

Originally Posted by DNSB

As far as I am aware, the only calibre versions that use an external Python install are various Linux distros, otherwise you need a custom build. Normally calibre uses it's bundled Python to avoid issues such as the OP's.

This issue will affect everyone once the bundled Python is updated to 3.12. Since all of the functionality of 'SafeConfigParser' is also present in 'ConfigParser' since version 3.2 there should be no reason to not update the plugin as soon as possible.

[DNSB]

Originally Posted by Majutsushi

This issue will affect everyone once the bundled Python is updated to 3.12. Since all of the functionality of 'SafeConfigParser' is also present in 'ConfigParser' since version 3.2 there should be no reason to not update the plugin as soon as possible.

In past, when similar issues came up, Kovid Goyal has added aliases as needed to allow the older plugins to run without needing modifications.

Since the original creator of the plugin is no longer available to maintain it, it is up to the community to maintain the plugin.

[PeterT]

I think the standard approach has been to initially use a try / except block to initially attempt to import the new module name and if that fails import the old name.

See

try:
    from PyQt5.Qt import QUrl, pyqtSignal, QTimer
    from PyQt5.Qt import (QMenu, QModelIndex, QFileDialog, QIcon)
except ImportError:
    from PyQt4.Qt import QUrl, pyqtSignal, QTimer
    from PyQt4.Qt import (QMenu, QModelIndex, QFileDialog, QIcon)

as an example. (Code from the current Kobo Utilities plugin.)

Sent from my Pixel 7a using Tapatalk