<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - Find & Replace: default value of "Diacritic-sensitive" (on/off) should be locale-specific" href="https://bugs.documentfoundation.org/show_bug.cgi?id=116835#c3">Comment # 3</a> on <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - Find & Replace: default value of "Diacritic-sensitive" (on/off) should be locale-specific" href="https://bugs.documentfoundation.org/show_bug.cgi?id=116835">bug 116835</a> from <a class="email" href="mailto:erack@redhat.com" title="Eike Rathke <erack@redhat.com>"> Eike Rathke</a> <pre>The default is now Diacritic-sensitive, but has an effect only in new installations as the checkbox value is remembered in the user configuration, which in existing installations was remembered from the hidden Diacritic-ignore status. Fwiw, contrary to what was said in <a href="show_bug.cgi?id=116835#c0">comment 0</a>, in German I do *not* expect diacritics to be ignored. Umlauts are distinct letters, not some "variation of a base" letter. Searching for Bar should not find Bär. I could bet also in French accented characters are not to be mangled. Trying to couple the Diacritic-sensitive default to locale/language IMHO is doomed to fail. There is no default locale with text, text either has a specific locale attribute or is set to None. Different portions of text can have different locales assigned. Often enough text is attributed with the user's current default locale but is written in another language and the attribute never changed. A coupled default would lead to bad user experience. Rather tackle the reason why Diacritic-sensitive was introduced first-hand: for Arabic. So have a second Arabic-diacritic-sensitive checkbox and if (default) unchecked ignore diacritics only in text portions written in Arabic script.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>