[GUI Plugin] Annotations

[Quoth]

I used to use "Annotations", but as I don't want them in Calibre, but in separate text files, the Kobo Utilities suit better. The format is easily changed in any good text editor after copy, paste, save. I used to use Notepad++ in Windows and now use KATE on Linux Mint.
You can then paste them back into Calibre.


Edit:
On Kobo you can also edit the config so there is an extra context menu item per ebook to allow export as a text file. Then you can copy it off using USB transfer in a file manager, but I found Annotations simpler, then Kobo Utilities suited my use case better.

[PeterT]

Here's a pre-release version of 1.7.14. It's the exact same as Teresa's versions, just with a new version number (her beta had not changed version number from the previous release).

I've forked the repository to https://github.com/PeterJT/calibre-annotations/

When I get some feedback I'll update the first post with the new release.

[Terisa de morgan]

Bad memory moment, sorry.

[Terisa de morgan]

Originally Posted by Leonatus

As I got the above mentioned error message, I tried the KoboUtilities plugin, and it worked. I'm not a technic, so I can't give further explications, but the remarks bopuc made are pretty correct, as far as I can see.

Ok, I remember now why my KoboUtilities call Annotations...

[bopuc]

Originally Posted by PeterT

Here's a pre-release version of 1.7.14. It's the exact same as Teresa's versions, just with a new version number (her beta had not changed version number from the previous release).

I've forked the repository to https://github.com/PeterJT/calibre-annotations/

When I get some feedback I'll update the first post with the new release.

Hi PeterT

Thank you for this. Does this mean that you are taking maintainership of the codebase?

You wrote that you forked the repo and released "the exact same as Teresa's versions"… could you please elaborate? Teresa's zip was a modified copy of the last officially released plugin, whereas the repo contains a few things that are not included in the zip (notably release build scripts, some additional unfinished reader support, annotation colors for PocketBook, etc…).

I'd really like to move this forward in a cohesive, collaborative and sustainable way, without duplicating/multiplying efforts. I made some suggestions to that effect in my previous post. I've also forked the code, this time into a separate non-personal repo which can be used and managed by more than one person: https://github.com/calibre-annotatio...re-annotations . Happy to open it up to anyone interested.


Why I care:
In my view, the Annotations plugin is the only solution currently for safely and easily managing annotations, in an automated and integrated way, supporting multiple ereaders, not requiring copy & pasting and managing one's own database/archive separate from Calibre and the books the annotations come from. As mentioned, it provides an enormous amount of the value, to me personally, of reading ebooks. As such, I want it to stabilize and stick around. I do not want control of it, I just want it to continue to be useful and useable to anyone like me.

[bopuc]

Originally Posted by Quoth

I used to use "Annotations", but as I don't want them in Calibre, but in separate text files, the Kobo Utilities suit better. The format is easily changed in any good text editor after copy, paste, save. I used to use Notepad++ in Windows and now use KATE on Linux Mint.
You can then paste them back into Calibre.


Edit:
On Kobo you can also edit the config so there is an extra context menu item per ebook to allow export as a text file. Then you can copy it off using USB transfer in a file manager, but I found Annotations simpler, then Kobo Utilities suited my use case better.

Lovely.

I prefer the automation of just importing everything with one click, then accessing it in the database as necessary for further integrations (e.g.: I automatically push my annotations into my writing app—Obsidian—and publish them inline on my personal ebook library webapp (linked in signature below).

[PeterT]

No. I dont I tend to be the maintainer but i could facilitate it

The extra files are a major mistake on my part and will be fixed shortly.

The only change I made was to update the version number to reflect the fact that Teresa's build had c still used hanges made from the lasf official release but her build still identified as the same version number as the official one.

Sent from my TB350FU using Tapatalk