On a debian Koha package install without any zebra modifications, we observe searching for words with double vowels is returning odd results. eg on https://lst.koha-ptfs.eu/cgi-bin/koha/opac-main.pl on Koha 18.1110000 food = 24 results foood = 22 results Foood (with 3 consecutive letter o's) should not return results. Also observed on other package install examples.
It could be that oo is reduced to o in the Zebra mapping (I had something similar happen with i ii iii, but haven't checked for ooo), so you actually end up with food. Depending on your settings (fuzzy search and similar) this might also be expected, as those are thought to catch simple spelling errors.
I don't think it is fuzzy search settings. QueryFuzzy is set to "Don't try". Which file in the zebra mapping could it be so I can check?
I think it's etc/zebradb/etc/word-phrase-utf.chr
Thanks. I can't see anything in that file that would map 1 lowercase letter o to 2 (or 2 to 3). Our file is like this: https://github.com/Koha-Community/Koha/blob/18.11.x/etc/zebradb/etc/word-phrase-utf.chr Any idea which line might be causing this to happen?
(In reply to Bernard from comment #4) > Thanks. I can't see anything in that file that would map 1 lowercase letter > o to 2 (or 2 to 3). Our file is like this: > https://github.com/Koha-Community/Koha/blob/18.11.x/etc/zebradb/etc/word- > phrase-utf.chr Any idea which line might be causing this to happen? My theory is, that the combination of those is doing it: equivalent ō(oo) map ō o I could be wrong :)
You were right! Commenting out equivalent ō(oo) did the trick for that example. Unfortunately, there may be similar problems for other vowel combinations. eg aa ("aachen" brings up "aachen" and "achen") I am assuming equivalent ā(aa) might be the one to comment out for that, but of course it means those diacritics are not properly mapped then if they should ever genuinely come up.
(In reply to Bernard from comment #6) > You were right! Commenting out > equivalent ō(oo) > did the trick for that example. > > Unfortunately, there may be similar problems for other vowel combinations. eg > aa ("aachen" brings up "aachen" and "achen") > > > I am assuming > equivalent ā(aa) > > might be the one to comment out for that, but of course it means those > diacritics are not properly mapped then if they should ever genuinely come > up. A library reported this to us and we decided together that we won't change it... too worried about side effects for other searches, especially if you have records in multiple languages where these might appear...
Should we mark this WONTFIX for now?