A user, Canapin, reported that the search function on their forum is returning approximate results instead of exact matches. They used the example of searching for “passants in:title”, which used to return the topic “les passants” among the first results, but now displays results with words like “passe”, “pass”, “passage”, and “passion” before the exact string “passants”.
JammyDodger suggested using double quotes around the word to make it an exact search, which helped but still returned a result with no “passants” in the title.
Canapin found this puzzling, and tgxworld explained that in French, “passants” is reduced to the “pass” lexeme before searching against post contents.
Canapin questioned the usefulness of this reduction, while sam explained that the French implementation in Postgres is responsible for the reduction and that it can be configured, but more advanced dictionaries are complicated to set up.
I’m afraid I don’t know enough about the Search to know if that’s on purpose or not, but you can add double quotes around a word to make it an exact search if that helps?
That sure helps, but the default behavior is puzzling.
For an unknown reason, when searching the exact string with double quotes, it also returns a result that has no “passants” in the title (but it has in the first post content):
I don’t feel it makes much sense in French to reduce such a word to “pass”. This is more confusing than helping considering there are a lot of words that begin with “pass” without being (directly or not) related to the verb “passer”.
But if we can target the exact string with double quotes instead, that will do .
Also, what’s with the second result not having “passants” in the title despite using the double quotes on my last screenshot?