Re: On language-dependent defaults for character-folding

[Eli Zaretskii]

> From: Óscar Fuentes <address@hidden>
> Date: Fri, 12 Feb 2016 19:42:50 +0100
> 
> 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.

Aren't there Spaniards who are also 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.

So you do think this, too, is not a problem?

> > 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 ⒜?

I don't know.  What do you think?

> What if I wish to replace all occurrences of (a) by [1]? Do you really
> want to go down that route?

I don't think so, no.

> 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.

I was trying to develop a dialogue which will help me and you
understand where your resistance begins and where it ends.  I think
it's important to do that to better understand the issues, but if you
don't want that, we can stop any moment.