https://bugs.freedesktop.org/show_bug.cgi?id=56524

Patrick Ohly <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|PIM Manager:                |PIM Manager:
                   |accent-insensitive search   |accent-insensitive and
                   |                            |transliterated search

--- Comment #2 from Patrick Ohly <[email protected]> ---
Another, related request was to match foreign and Latin ways of writing the
same text, for example 江 = jiāng (= Jiang when ignoring case and accents).

I've decided to treat this the same way as accent-insensitive search, meaning
that the default will be as relaxed as possible: case-insensitive,
accent-insensitive, and transliterated. I've finished the implementation
(including updated tests) and now only need to check for regressions, then
merge into master.

Here's the updated README:

    For text values, the default search without explicit flags is
    very tolerant, meaning that it ignores quite a few differences
    between search term and value. The default search:
    - transliterates any foreign script in search term and values
      to Latin before comparison, thus finding 江 when searching
      for Jiang and vice-versa
    - is case-insensitive
    - is accent-insensitive

    Case and accent differences get removed after the optional
    transliteration. Spaces between words always matter.

    This behavior can be modified by giving additional,
    optional flags after the search value:
    'case-insensitive' - force case-insensitive search (available for the sake
    of consistency and just in case, should the default ever change)
    'case-sensitive' - force case-sensitive search
    'accent-insensitive', 'accent-sensitive' - same for accents
    'transliteration' - force transliteration, i.e. explicitly choose the
    current default
    'no-transliteration' - disable transliteration

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
Syncevolution-issues mailing list
[email protected]
https://lists.syncevolution.org/mailman/listinfo/syncevolution-issues

Reply via email to