Quote:
Originally Posted by chaley
If I am following the thread correctly, that won't do what you want.
The "problem" is that as DaltonST points out, there can be at most one instance of a tag with a given spelling, ignoring case. If you delete the tag from a book then add it with a new case then if that tag exists on other books with different case then the tag will also change its case. You have only 2 choices: - use the existing tag (with its letter case) so nothing changes other than adding the tag to the book.
- use the same spelling with different letter case, in which case the tag will change on all books with that tag.
To do what it seems you want then you must change its spelling.
I think there is zero chance that this behavior will change. |
This is one of the few points I strongly disagree with Kovid about calibre behaviour. That and updating the modified timestamp for all books when adding or removing a custom column. Both go against everything I've ever done with database migrations and updating. I have spent to much time turning off the automatic updating while modifying the database schema to agree with this.
@Quoth: There is option or tweak that related to this. If you set it, it is a little harder to accidentally change the case of a tag in the metadata editor. Unfortunately, I can't quickly see what it is. I think I have it set at home, so I'd have to check there.