Re: revised w/nocase text, considering titlecase and cased

[Alex Shinn <alexshinn@xxxxxxxxx>]

On Sat, May 10, 2014 at 11:21 AM, John Cowan <cowan@xxxxxxxxxxxxxxxx> wrote:

Alex Shinn scripsit:

> But if you decide they should _not_ have case mappings, then
> you're treating them strictly as symbols, and giving them case
> properties is inconsistent.  It should be one or the other.

They are something like symbols, but they are letter-like in other ways.
Per contra, the circled Latin letters are considered symbols (and so
have no case) but have case mappings just the same.

They are letter-like.  Unicode decided they are not case-like -

they exist by themselves without any *-cased counterpart.

Therefore they should not have case properties.

You can also argue the other direction, that case is not just

about exact semantic identity, but perceived identity.  When

I isearch in emacs I expect case insensitive matches (unless

specifically disabled) and would expect "x" to match either

case of x in formulas.  Likewise in natural sorting you expect

the different cases to sort together.  This is also true for

mathematical symbols even when there is no relation at all

between the two cases, such as in

  http://en.wikipedia.org/wiki/Greek_letters_used_in_mathematics,_science,_and_engineering

Or put more simply, everyone _knows_ that X is the upper-

case of x, and expect it to behave that way in software.

Unicode is breaking expectations here.

 

In Unicode, things are always more complicated than you think.

Rhetoric.  They are a committee making decisions, many of

which could go either way.  I'm pointing out this was a bad

decision.  Such things happen.

-- 

Alex