Last modified: 2014-01-29 16:19:59 UTC
You can reproduce this by searching wiktionary for son. It lands you on són.
I was thinking about this last night and was wondering if it would be bad if we stopped near matches from doing ascii flattening? It already only does this for English and this would be the simplest way of fixing this from a technical perspective. The downside is that "go" search would get a little more confusing: you might type into the prefix search box and see "són" as the top response because it is linked more frequently then "son".
Wiktionary has 8 pages that all "near match" son with the current analysis setup: sơn Son són son sön SON søn soñ Even with my proposed near match change it still has three: Son son SON So I'm pretty sure that is a bad idea. Another proposal: restore sorting by the number of incoming links. This would drop you on "son" as expected. Another proposal: if there is more than a single "near match" then declare that there are non and drop the user to the search page. That will give them more options and never _force_ them to the wrong page. It may be less convenient. Also, it can be done with or without removing asciifolding. Personally I'd prefer to leave the folding in place so prefix matching, which really should have folding, still looks sane.
https://gerrit.wikimedia.org/r/#/c/107433/
Verified on enwiktionary.
