Quote:
Originally Posted by chaley
<pontification>
From a development standpoint, it wouldn't be hard ...
</pontification>
|
I completely agree with this view. However, (no that doesn't mean I'm going to backtrack .... much) Calibre does inhabit the high end when it comes to the technical sophistication of users and the skills needed to use many features. Extra CSS, regex expressions in multiple locations and XPath for TOC require a lot of skill, even with Kovid's excellent wizards.
If I was still struggling through my initial stages of data entry, I would have loved to have had a sticky thread with useful Python code fragments that could be executed with:
Quote:
|
calibre-debug -e myscript.py
|
.
It would have a first post saying there's no bulk undo, use at your own risk, make a backup first, etc. Then some scripts like:
Regex search and replace in title or author.
Populate a field with the contents of other fields or data.
etc.
People could add scripts, as they do recipes, as they're written. I clearly remember my frustration when I couldn't easily directly modify the metadata.db SQL database to do regex searches and fix miscellaneous errors in title/author.
I have to say that in view of the many recent improvements in Calibre, I want such scripts a lot less (plus I'm no longer actively adding my old ebook library).
Still, I have no problem with providing some options (outside the Calibre installed environment) to help the most sophisticated Calibre users who are willing to run at the bleeding edge and take the consequences.