Quote:
Originally Posted by travger
Example:
I want to find novellas.
One of the books has "author of award-winning novella" in comments (though I try to avoid this, but...).
Now this book is also included in the search result.
Having something unusual instead of 'novella' avoids situations like this. Nvella or *nlla is my own creation.
Also, I am 98% sure of never having to explain. Nobody sits behind my computer without me hanging around with watchful eyes. If I share over the net - recipient is free to delete/change all the tags.
|
I haven't been tracking novellas or novelettes separately, just lump them in with short stories or short articles as %shr.
I stayed away from using asterisk or plus as symbol because they're often used as a wildcards in search and replace in calibre and other applications. Minus and plus and ampersand also, used sometimes as operators in some applications. The ones I listed above seemed relatively safe and avoided needing any special fonts or extravagant keyboard commands such as preceding keystroke with function, control, option, alt, command, or also combining one of more of those with shift key.
The ones that seem to work safely in calibre at the moment are underscore, percent, dollar, semicolon, exclamation point, at (@). I imagine the pound sign would work okay too. To make something unique, it helps to give that symbol a unique letter combination. Such as $xHFP being format problem with headers/footers/pagenumbers, where the x means it's serious enough to trash if it can't be fixed or replaced. The $x combo makes it unique no matter what else is in the tag.
Those symbols also can be used as suffixes rather than prefixes, but prefixes are usually more useful for sorting purposes.
Other symbols used in calibre regex (like plus or asterisk) could maybe be used with a backslash exception, but I'm not sure yet exactly how the search routine parses those, and why risk forgetting the backslash (if it works at all) or bothering with those at all?