<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - Find & Replace: Rename diacritics and kashida search options" href="https://bugs.documentfoundation.org/show_bug.cgi?id=111846#c28">Comment # 28</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - Find & Replace: Rename diacritics and kashida search options" href="https://bugs.documentfoundation.org/show_bug.cgi?id=111846">bug 111846</a> from <a class="email" href="mailto:khaledhosny@eglug.org" title="Khaled Hosny <khaledhosny@eglug.org>"> Khaled Hosny</a> <pre>(In reply to Eike Rathke from <a href="show_bug.cgi?id=111846#c27">comment #27</a>) > That's not just a little glitch, that's a crunchy bug, and also the default > presets were wrongly chosen, clearly one normally does not want to ignore > diacritics. Not in Arabic or in languages where diacritics are not parts of the letters (in Arabic خالد and خَالِدْ are the same word). It is just like case-insensitive search being the default. > Additionally having Not-Diacritic-sensitive and > Not-Kashida-sensitive being the implied defaults for every search adds > specifically for ignore-diacritic a heavy extra performance penalty > transliteration decomposing every text first to normalize diacritics. I didn’t notice any performance difference last I tried this, but I didn’t do any actual performance testing.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>