Plugin ideas... add yours here

[The Holy]

It sounds like we are on the same page then. If two separate plugins are made, I would request that my other suggestion gets included in the simpler plugin.

The simpler plugin could be called “Basic metadata match” and include “Basic Language Match” and “Title & Author Match”. The title & author match would just search for the book's title and author's last name, provided by what Calibre has set for each field, inside the book. After testing a few books it looks like it would work pretty well, the search will probably need to remove any subtitle in the title though.

The advanced plugin could be “Advanced Language Match”. The thing is that I'm not sure how useful this plugin would be for people using Calibre, and frankly how many would use it. If one wants to identify the language of a text, there are already tools for it, some here: https://aclweb.org/aclwiki/Language_...fication_Tools along with Google translates automatic identification of a language. The ability to identify any language would be good to have in Calibre, but the basic plugin may end up being good enough anyway for 99% of people who use it.

So how about we start on the Basic metadata match plugin and decide which way to check for languages?

[BetterRed]

@The Holy - most plugins are initially developed by people who need them.

BR

[Fiat_Lux]

Originally Posted by The Holy

It sounds like we are on the same page then. If two separate plugins are made, I would request that my other suggestion gets included in the simpler plugin.

The simpler plugin could be called “Basic metadata match” and include “Basic Language Match” and “Title & Author Match”. The title & author match would just search for the book's title and author's last name, provided by what Calibre has set for each field, inside the book. After testing a few books it looks like it would work pretty well, the search will probably need to remove any subtitle in the title though.

The advanced plugin could be “Advanced Language Match”. The thing is that I'm not sure how useful this plugin would be for people using Calibre, and frankly how many would use it. If one wants to identify the language of a text, there are already tools for it, some here: https://aclweb.org/aclwiki/Language_...fication_Tools along with Google translates automatic identification of a language. The ability to identify any language would be good to have in Calibre, but the basic plugin may end up being good enough anyway for 99% of people who use it.

So how about we start on the Basic metadata match plugin and decide which way to check for languages?

I'd call them the _When you don't have any idea what languages are used plugin_, and _When you know what languages are used plugin_.

_When you don't have any idea what languages are used_ would use a letter-frequency/glyphs-utilized based detection system. Throw a book at it, and it will get the correct language 90% of the time. Initial cut would differentiate between roughly 250 languages.Subsequent versions would add minority/endangered languages.
FWIW, I'm currently working on a python script that can do that identification. Due to health issues, it is taking far longer than expected.

_When you know what languages are used plugin_ would do a word frequency
analysis, getting the correct language 99% of the time. The first cut here would be English/Not-English.

The sequence to add languages would be:
* Most produced written content in the target language;
* Most spoken language;
* Content availability on MobileRead;

[Ertagon]

Kindle Comic Margins

What current CBZ -> AZW3 in calibre looks like [link]
What it looks like from Kindle Comic Converter [link]


Justification:
Kindle Comic Converter (KCC) - is generally slow, supports few formats and does not integrate well into the Calibre ecosystem. It's generally painful to use at scale.


Todo:
- Modify the CBZ input to have a "Kindle margins remove" or create a separate input just for this. It should maintain all of the CBZ input functionality. Any other implementations are good as long as they make sense and allow for/include the original CBZ functionality.

- Investigating the KCC python code and the output itself might prove insightful. Example of .epub output from KCC [xhtml], css, content.opf

- Read Amazon's documentation


Goal:
A publically available plugin which essentially replaces KCC by implementing CBZ conversion that does not produce extra margins, as shown in the links above. The plugin should not have any breaking bugs. Maintenance is not expected.


Reward: €100 (payable no sooner than 9/01/2023) + €50 (if W/B margins functionality from KCC implemented).
Awarded upon successful completion of the plugin.
Award email: jaroslawjanas.dev@gmail.com (email me before publishing it)
To give this posting validity, here is my GitHub profile


Note: If this remains uncompleted for a more extended period of time, I will do it myself, but it might take a considerable amount of time since I am completely unfamiliar with the Calibre codebase. I'd instead give someone the money since it will cost me more (in time) to do it myself.

If the plugin/behaviour is added without claiming the reward, it will go towards funding the Calibre project.

Feel free to email me with questions.

[tomsem]

Has anyone looked into creating a plugin to collect Vocabulary Builder data (from multiple Kindles), and provide a way to enable a way to sync the database between devices (if only Amazon would do this)?

The database seems pretty easy to understand, and I assume there's a way to uniquely identify a Kindle.

I want to see where I can get with a standalone script, but welcome some feedback or suggestions.

[Update: it seems the Vocabulary Builder database does sync, though it seems to need a 'nudge' sometimes: go to Reader Settings and toggle it off and then back on.]

[tomsem]

Originally Posted by Ertagon

Kindle Comic Margins

What current CBZ -> AZW3 in calibre looks like [link]
What it looks like from Kindle Comic Converter [link]


Justification:
Kindle Comic Converter (KCC) - is generally slow, supports few formats and does not integrate well into the Calibre ecosystem. It's generally painful to use at scale.


Todo:
- Modify the CBZ input to have a "Kindle margins remove" or create a separate input just for this. It should maintain all of the CBZ input functionality. Any other implementations are good as long as they make sense and allow for/include the original CBZ functionality.

- Investigating the KCC python code and the output itself might prove insightful. Example of .epub output from KCC [xhtml], css, content.opf

- Read Amazon's documentation


Goal:
A publically available plugin which essentially replaces KCC by implementing CBZ conversion that does not produce extra margins, as shown in the links above. The plugin should not have any breaking bugs. Maintenance is not expected.


Reward: €100 (payable no sooner than 9/01/2023) + €50 (if W/B margins functionality from KCC implemented).
Awarded upon successful completion of the plugin.
Award email: jaroslawjanas.dev@gmail.com (email me before publishing it)
To give this posting validity, here is my GitHub profile


Note: If this remains uncompleted for a more extended period of time, I will do it myself, but it might take a considerable amount of time since I am completely unfamiliar with the Calibre codebase. I'd instead give someone the money since it will cost me more (in time) to do it myself.

If the plugin/behaviour is added without claiming the reward, it will go towards funding the Calibre project.

Feel free to email me with questions.

I took a look at the KCC (command line) code a few months ago, as it was the closest thing to my use case (make photo albums from a set of images, with landscape spreads that join smoothly when in 2 page mode on a tablet, and scaling up and down for 'best fit').

I had some success hacking to get it to do this, but reached a point where I was struggling too much with the way the code is structured, and concluded it would be better to start over from scratch.

The KCC IMO is not well structured, it seems to do too many things to do any of them well, and the greatest Python sin of all, it doesn't conform to Python naming conventions or PEP8 generally.

I think one of the KCC developers had a project to create a calibre plugin, but they wanted to use Python 3 features which wasn't supported at the time so it probably isn't much of a starting point.

So I would agree it's better to start over with a clear list of requirements, as I plan to do with my photo album idea, should I ever get around to it.

If you don't find a willing recruit, you could just build a command line tool, get that working, and worry about the plugin stuff later. Which is my plan.

[riocca]

Hello! If it possible maybe anybody can make metadata source plugin for russian books - to look for book info on https://primo.nlr.ru/, https://www.livelib.ru/, https://www.labirint.ru/. Years ago there was a plugin for ozon.ru, but it isn't book resource and now is impossible to find metadata for russian books in calibre.

[Rellwood]

A tag mapper that would allow for columns other than "tags". Also (if possible) allow the mapper to change the tags in multiple columns at once.

I have different columns than just tags that could use the mapper rather than manually fixing the tags.

[Tenome]

Is there a working metadata/ID plug-in for Open Library?

[ownedbycats]

Originally Posted by Tenome

Is there a working metadata/ID plug-in for Open Library?

No. I was looking into it in 2021 but then dropped it for some reason.

[lakedai]

Hello everyone.
Is there any plugin that provide vim style book list browsing function --- scroll down/up/first/last. For example J -> Down/K -> Up/X -> delete etc. Currently the Preference->Shortcuts do not include something like that. Thank you.

[BetterRed]

Originally Posted by lakedai

Hello everyone.
Is there any plugin that provide vim style book list browsing function --- scroll down/up/first/last. For example J -> Down/K -> Up/X -> delete etc. Currently the Preference->Shortcuts do not include something like that. Thank you.

None I can think of.

If X->delete signifies delete the book record, that's doable in the Remove book shortcuts.

Most plugins have been developed by the first person who needed a particular functionality.

The only plugin I can think of that is 'shortcut' oriented is the Scroll Book Details plugin ==>> Index of plugins.

BR

[BetterRed]

@lakedai - I've moved your plugin and replies to its own thread ==>> [GUI Plugin] VimStyle

And I'm about to request your Message box be enabled.

BR

[Reader4106]

Endnotes, footnotes in ePub books
I read many books in ePub format which have endnotes or footnotes.
In most cases these references are displayed as small superscript numbers in the form of indices. To "hit" them with the fingertips is usually very difficult. If they are close to the function zones of the eReader on the page edges, it is often not possible to jump to the texts.
However, I have also been able to read books in which the word preceding the jump mark (index) was in a different font style and usually additionally underlined. This makes jumping to the reference much easier.

I would therefore like to see a tool which:
- extends the jump marks in the ePub books by the word(s) preceding it, and marks it with its own text style.
- It should be possible to set a minimum number of characters (e.g. 8) for the jump mark.
- If this style can be defined by the user in the tool settings (size [+/-%], bold, italic, underline/overline, color [16 shades of gray]), this would be a further improvement and simplification.
- A preceding WYSIWYG representation would also help a lot.

The style change should also be able to be made for the return marker of the actual endnote. Since this usually consists of only a few characters, a suffix such as "Number " or "No. etc. " could be prefixed.

If it were then also possible to restore the original state of the ePub, the tool would be perfect.

It seems important to me that the resizing of the font is only ever relative to the size defined in the ePub format, to accommodate the different display sizes of users when reading.

[BetterRed]

@Reader4106 - this Sigil plugin might be a good starting point, ==>> FootnoteManipulator

BR