Re: On language-dependent defaults for character-folding

[Óscar Fuentes]

Eli Zaretskii <address@hidden> writes:

>> ñ shall match ñ, but n shall not match either, from an Spaniard POV.
>
> But in the case of 2 characters, a literal n is present in the buffer,
> so not finding it would be a miss, don't you think?

Then you are not thinking as an Spaniard, but as someone who is versed
on character representations by computers.

In practice, n matching ñ (the composed one) will not be a big issue,
since it will happen rarely. Same for the rest of compositions that
looks like ñ but are not "the" ñ. If someone complains, we can explain
what the problem is and that we opted for handling such compositions as
groups of characters.

> What about finding ⒜ when searching for a, don't you want to find
> that?  This is not specific to any language.

That would be nice, sometimes. If I search for (a), should it match ⒜?
What if I wish to replace all occurrences of (a) by [1]? Do you really
want to go down that route?

But we are digressing. Eli, you are missing the point. If you wish to
set Emacs defaults as per the convenience of people who think of text as
a series of codes at the expense of breaking basic expectations of those
who see text as... text, well, frankly, I don't think it is a good
decision.