On Wed, Jun 06, 2001 at 05:37:54PM -0700, Russ Allbery wrote: > David L Nicol <[EMAIL PROTECTED]> writes: > > Russ Allbery wrote: > > >> a caseless character wouldn't show up in either IsLower or IsUpper. > > > maybe an IsCaseless is warrented -- or Is[Upper|Lower] could return > > UNKNOWN instead of TRUE|FALSE, if the extended boolean attributes allow > > transbinary truth values. > > Well, UNKNOWN isn't accurate either; the case *is* known. It's just > neither upper nor lowercase. > > (I wonder what it should return for titlecase characters too, for that > matter.) What happens if unicode supported uppercase and lowercase numbers? [I had a dig about, and it doesn't seem to mention lowercase or uppercase digits. Are they just a typography distinction, and hence not enough to be worthy of codepoints?] Nicholas Clark
- Re: Should we care much about this Unicode-ish criticism... David L. Nicol
- Re: Should we care much about this Unicode-ish criticism... Russ Allbery
- RE: Should we care much about this Unicode-ish criticism... Garrett Goebel
- Re: Should we care much about this Unicode-ish criticism... Nick Ing-Simmons
- RE: Should we care much about this Unicode-ish criticism... Nick Ing-Simmons
- Re: Should we care much about this Unicode-ish criticism... Buddha Buck
- Re: Should we care much about this Unicode-ish criticism... Dan Sugalski
- RE: Should we care much about this Unicode-ish criticism... Dan Sugalski
- Re: Should we care much about this Unicode-ish criticism... Nicholas Clark
- RE: Should we care much about this Unicode-ish criticism... Hong Zhang
- RE: Should we care much about this Unicode-ish criticism... NeonEdge
- Re: Should we care much about this Unicode-ish crit... Nicholas Clark
- Re: Should we care much about this Unicode-ish crit... Bryan C . Warnock
- RE: Should we care much about this Unicode-ish criticism... Hong Zhang