Match Diacritics

[raccoon]

Can someone explain to me the Search option Match Diacritics and why it behaves the way it does?

Behavior: When you turn on Match Diacritics, then diacritics will not be matched. When you turn off Match Diacritics, then diacritics will be matched.

This seems like exactly the opposite behavior than should be expected. It also creates a situation where one of the search options should be checked by default, when ideally, all search options should be unchecked by default unless you want extra-normal behaviors.

pokemon matching pokémon is an extra-normal behavior.

Should we not invert the behavior of Match Diacritics and have it disabled by default? Assume that the person searching for "e" means "e" and not question their intelligence?

[therube]

Tradition, tradition my boy.
It's always been that way, & so it shall stay, IMO .

To one who doesn't normally concern themselves with diacritics, I guess you could say, enable it by default.
To one who diacritics does matter, they would want it disabled by default.

I suppose the "correct" answer is to have it disabled by default, & for those where it doesn't matter, they enable it.


Myself, matters not (what the default is). (I keep it enabled.)

[void]

Match diacritics enabled:

diacritics must match exactly:
é == é
e != é
é != e
e == e



Match diacritics disabled:

diacritics are ignored:
é == é
e == é
é == e
e == e

The default is to ignore diacritics.



Think of match diacritics like match case.
Match case enabled: case must match exactly: A != a
Match case disabled: case is ignored. A == a

[raccoon]

Think of match diacritics like match case.

I see. I guess when when you put it that way I can understand your flow of logic.

To me, I thought it meant "Match Diacritics lets e match diacritical é."
And similarly, "No Match Diacritics means e will not match diacritical é."

Thanks for clearing it up.