[GUI Plugin] Annotations

[Savate]

No - the beta is just the same.

I give up!

This plug in does not work for me.

Thanks anyway.

[davidfor]

Originally Posted by Savate

No - the beta is just the same.

I give up!

This plug in does not work for me.

Thanks anyway.

That's strange. I ran tests using the sample you posted and it generated the expected result which included the location details. Is that the complete file or did you copy and paste a chunk? If so, could you post the complete file unchanged? There is at least one strange character in there, so maybe there is something else in the file that didn't get through the copying process. If you don't want to post it, send it to me via PM.

I'd also like to see calibre debug log when you run the fetch. That can show a lot of things about what is happening.

[Savate]

Hi thanks for your helpful reply.

I'll have another go at this in the next few days. I'll attach/send a copy of the clippings file and I'll run a log too and send that.

[rmarhi]

Hi

I recently installed Annotations (1.8) plugin but I appear to be having a problem with it.

When I try to 'fetch annotations from kobo" I get the following error:

calibre, version 3.41.2
Error fetching annotations: <p>Unable to fetch annotations from Kobo Aura.</p>

Traceback (most recent call last):
File "calibre_plugins.annotations.action", line 301, in fetch_device_annotations
File "calibre_plugins.annotations.action", line 1024, in process_selected_books
File "calibre_plugins.annotations.action", line 135, in add_annotations_to_calibre
File "calibre_plugins.annotations.annotations_db", line 180, in annotations_to_html
File "calibre_plugins.annotations.annotations", line 198, in to_HTML
File "site-packages\bs4\element.py", line 830, in __init__
ValueError: No value provided for new tag's name.


And when I try to "modify appearance" in the customize screen, I get the following error:

calibre, version 3.41.2
ERROR: Unhandled exception: <b>ValueError</b>:No value provided for new tag's name.

calibre 3.41.2 [64bit] embedded-python: True is64bit: True
Windows-10-10.0.17763-SP0 Windows ('64bit', 'WindowsPE')
('Windows', '10', '10.0.17763')
Python 2.7.15+
Windows: ('10', '10.0.17763', 'SP0', u'Multiprocessor Free')
Interface language: None
Successfully initialized third party plugins: DeDRM (6, 5, 5) && KoboTouchExtended (3, 0, 2) && KePub Input (3, 0, 0) && KePub Output (3, 0, 0) && Kobo Utilities (2, 7, 0) && KePub Metadata Reader (3, 0, 2) && Kobo Books (1, 6, 0) && KePub Metadata Writer (3, 0, 3) && Annotations (1, 8, 0)
Traceback (most recent call last):
File "calibre_plugins.annotations.config", line 325, in configure_appearance
File "calibre_plugins.annotations.appearance", line 496, in __init__
File "calibre_plugins.annotations.appearance", line 298, in initialize
File "calibre_plugins.annotations.appearance", line 276, in css_edited
File "calibre_plugins.annotations.appearance", line 368, in preview_css
File "calibre_plugins.annotations.annotations", line 198, in to_HTML
File "site-packages\bs4\element.py", line 830, in __init__
ValueError: No value provided for new tag's name.

[Quoth]

The recent update to Calibre and Kobo on it fixed the messy formatting on the Kobo Utiliies Fetch Annotation, which has always been much faster and more reliable. Connect Kobo, Highlight book, go Kobo Utilities (might need installed), Fetch annotation for book. Then copy/paste wherever you want it (inc Custom Metadata, though I use separate text files I backup.)

[davidfor]

That's a problem due to changes in the latest version of calibre. I thought I had checked all my plugins for this change. I'll try and fix it in the next day or so.

[davidfor]

Originally Posted by FrustratedReader

The recent update to Calibre and Kobo on it fixed the messy formatting on the Kobo Utiliies Fetch Annotation, which has always been much faster and more reliable. Connect Kobo, Highlight book, go Kobo Utilities (might need installed), Fetch annotation for book. Then copy/paste wherever you want it (inc Custom Metadata, though I use separate text files I backup.)

Except of course that it doesn't do the same thing as this plugin. They serve different functions.

And the change to the formatting was me needing to touch that code so I fixed other things while I was there. Nothing to do with the calibre change. Or at least not directly.

[davidfor]

I have just released version 1.9.0 of the plugin. This is a long overdue official release that rolls the functions in the various beta's I have released over the last year or so.

The list of changes are:

• New: Add support for tolino devices.
• Fix: Parsing error when annotations in library missing color attribute.
• Fix: Apparently some Kindles use lower case for location and page.
• Fix: Was writing empty p-tag after the annotation and note.
• New: Change device fetch menu option to the same name all the time.
• New: Add some shortcuts.
• Update: Internal changes for prints and testing in ParseKindleMyClippingsTxt.py.
• Fix: Update to match BeautifulSoup changes in calibre.

The tolino support is similar to the Kindle support. Annotations are written to a file called "notes.txt" in the root directory of the device. This is more a log of annotations made. There is probably another store of the annotations used for displaying them on the device, but it is not accessible over the USB connection.

The menu item for fetching from a connected device has been changed. Instead of including the name of the device, it is now a generic "Fetch annotations from connected device". This change was to make it easier to create a shortcut for the function.

The other changes are bug fixes and to support changes made in calibre.

Calibre should make the update in the next hour or so. If there are any problems, please report them here.

[rmarhi]

Release 1.90 has resolved the errors I was receiving. Thanks.

[Katja_hbg]

Hi David,
thanks for the shortcut. It works well.


Do you know the reason for the following?
It happens that I do not get the Annotation for about 20percent of my books. Although there is an Annotation and I can get it by the KoboUtility (see screenshot).
btw this is not new since last update. It is only that I find time to report this only now.

[davidfor]

Originally Posted by Katja_hbg

Do you know the reason for the following?
It happens that I do not get the Annotation for about 20percent of my books. Although there is an Annotation and I can get it by the KoboUtility (see screenshot).
btw this is not new since last update. It is only that I find time to report this only now.

I haven't noticed any issues. It should be getting annotations for all books on the device that are in the library. If the books aren't matched, the annotations won't be fetched. In the screen shot, there is only one book listed. Is that due to a search? Or a virtual library? The search shouldn't have an affect, but I don't know what will happen if you are using a virtual library.

Can you run calibre in debug mode and post the log? Or PM it to me if you would prefer. Hopefully that will give me an idea of what is happening.

[Katja_hbg]

Hi David,
the book is now deleted from the device. So I need to wait when it happens again to create a debug log. This may take some days.

I use view manager with search but not VL.

[xppx99]

hello!
Is it possible to auto trigger the fetch, every time the e-Reader is connected?

thanks

[davidfor]

Originally Posted by xppx99

Is it possible to auto trigger the fetch, every time the e-Reader is connected?

Not at the moment. It would really need to be changed to run in the background so that it doesn't get in the way. Plus, I think in running automatically, it would need to only find the changes. It isn't a change I'm interested in doing at the moment.

[mva1985]

Is there any way to actually highlight using the built-in epub reader in Calibre? Having tried many PC epub readers it seems that the one included with Calibre is the best for my laptop except it lacks highlighting features or maybe I'm missing something?

Thanks