<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Find & Replace: Rename diacritics and kashida search options" href="https://bugs.documentfoundation.org/show_bug.cgi?id=111846#c20">Comment # 20</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - 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 Thomas Lendo from <a href="show_bug.cgi?id=111846#c19">comment #19</a>) > The 2 main reasons are stated in the initial post. From the UX point of view > it's worth to discuss that and to take it into consideration. > > Many search results in Google of "ignore diacritics" are developer-related. > The search functionality of LibO is used by non-developers mostly. Also > "include" is only a suggestion--a good and better term has to be found by > English native speakers so that it will be understand immediately. Inventing new jargon is unlikely to help users, unlike sticking to existing nomenclature. That is similar to the never ending attempts to replace the floppy disk save icon with some of thing modern just because someone thinks this will help users who never saw an actual floppy disk.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>