No support for regular expressions #2
Description
The current implementation searches for anything that contains the searched term. For instance, searching for "air" will find "cairo".
I think style of search is desirable, and I do make use of it for finding things I didn't know they exist. However it's not every time it is needed, and certainly not for all users. Not to mention the fact that if the term is common and/or have just a few characters, it will take an unnecessary time to find all matches.
It shouldn't be be the only option.
Options coming to mind:
1 - the script understands some regex flavor and just parse it. Caveat: the matching quality will depend on the users regex kung fu abilities.
2 - keep as it is but accept one argument for literal searching. Caveat: might not work if the user needs only one part of the search term to be literally matched.
3 - let the user configure its own searching preferences and just parse them.
Any thoughts?
EDIT/UPDATE:
I couldn't find the air and cairo example on Tatoeba.org, but searching for air resulted in Buenos Aires. It seems that Tatoeba does the same and I can't find any related to regex support on the advanced search.