RE: char equivalence classes in search - why not symmetric?

[Drew Adams <drew.adams@oracle.com>]

>   > > Currently the user can either search for "any kind of e" or "only é"
>   > > or "only è" or "only ê", etc.
> 
>   > That would still be the case.
>   > The only difference would be that when s?he wants to search for "any
>   > kind of e" s?he can use any of the equivalent e-chars.  Any of [eéèêæë]
>   > would behave the same as `e' does not, when searching for any of
>   > [eéèêæë].
> 
> This seems to be a miscommunication.

That communication is itself unclear.  _What_ seems to you to be a 
miscommunication?

The point is that what you say is true currently would still be the
case with what is proposed in this thread.  The user would continue
to be able to search for either any kind of e or for only a specific
kind of e.