Was directed here from my failed bug report: Diacritics and curly/smart quotes cannot be searched well, universally or in a note . Not that anyone’s asking for it, but here are my two cents…
To me, calling this a feature request, even a “valuable” one, downplays reasonable expectations that most users have, especially after being primed to expect similar fuzzy logic from so many other programs.
If you searched your bank card transactions for “Lucky’s Diner”, but by default your bank removed apostrophes from business names, you’d expect some logic to show “Luckys Diner” transactions when searching for “Lucky’s Diner”, in the same way you’d expect your bank’s search function to understand “luckys diner” (lowercase) is the same as “Luckys Diner”.
At the very least, you’d expect your bank to explicitly tell you how to type your search queries if they’re going to have such exacting, narrow scope. Not doing so leads to misleading results. In my example, you might get no results and wrongly think you used a different card for the transaction. What a waste of your time.
You could argue adding such logic is a new feature, but it’s also clearly bad UX with a UI operating in a subtly opaque way. If a huge break from common usability expectations can’t count as a bug—when we all know bugs tend to rightfully take priority—and a fix is more likely to count as a nice-to-have feature, I think the Troubleshooting Guide for bug reports should make it clearer what counts as a bug. That would be useful for everyone.
Not trying to be snide. I legitimately do not understand the distinction if this counts as a feature request rather than a bug.
For a lot of us, the search results are clearly missing relevant information, breaking functionality in a variety of ways. But because this is a feature request, I’m going to assume it’s naturally not as high priority (nearly four years in here). Meanwhile, to see accurate results in Obsidian, I have to painstakingly, manually replace single straight quotes/apostrophes with curly quotes/apostrophes (real fun on mobile, and Omnisearch doesn’t appear to recognize them either) or try to remember alt codes for diacritics (just kidding, I’m often on a TKL keyboard where this is a nightmare). It’s a thing I didn’t initially realize I had to do. Really, it’s just forcing me to use other programs half the time, when I’d really like to use Obsidian.