- From: Karlsson Kent - keka <keka@im.se>
- Date: Mon, 31 Jan 2000 18:42:34 +0100
- To: www-html@w3.org
- Message-ID: <C110A2268F8DD111AA1A00805F85E58DA68577@ntgbg1>
One background reason may be that defining "case insensitive" for all of Unicode is non-trivial. How should (German) sharp s (ß) be handled? It's uppercase is "SS", so is ß equivalent to "ss"? What about Turkish dotless i and dotted i? Same or not? How about Greek iota subscripts? Uppercasing turn them into ordinary iotas, which remain ordinary iotas when lowercasing again. There is some work on this in UTR 21, but I don't think that is stable yet. The easy thing to do, when you can, is to say "case sensitive" rather that the tricky "case insensitive". Kind regards /kent k > > I'm sure I'm just lacking background on this, but could > > somebody summarize what the reason behind this minor > > hindrance is? Thanks > > XML unlike SGML is case sensitive. XML parsers will throw an > error if the > case is wrong. The working group had to decide for one way or > the other, the > four type considered were UPPERCASE, camelBack, FirstCaps, > and lowercase. > > For better or worse we voted on lowercase. This was made > clear in the early > public drafts about a year ago! It's too late to change it now!! > Frank
Received on Monday, 31 January 2000 12:43:02 UTC