W3C home > Mailing lists > Public > public-webapi@w3.org > November 2007

[XHR] i18n comment 4: clarify case-insensitive limited to ASCII-only HTTP header values

From: <addison@yahoo-inc.com>
Date: Thu, 29 Nov 2007 16:11:05 +0000
To: public-webapi@w3.org, public-i18n-core@w3.org
Message-Id: <20071129160809.E6DE64F2CE@homer.w3.org>

Comment from the i18n review of:

Comment 4
At http://www.w3.org/International/reviews/0711-xhr/
Editorial/substantive: S
Owner: AP

Location in reviewed document:

Section 1.2.2 defines case-insensitive matching as follows:

There is a case-insensitive match of strings s1 and s2 if after uppercasing both strings (by mapping a-z to A-Z) they are identical.

This doesn\'t make clear that this only applies to a limited domain of ASCII-only HTTP headers rather than serving as an overall definition of case-insensitivity.

It should also mention that this is the default case mapping for Latin text.

There are languages (Turkish, for example) in which the default mapping doesn\'t apply and this potentially causes problems for matching: when case-mapping is instantiated in these locales, by default they do the \"wrong thing\".

In any case, I would propose that this be changed as suggested below, since some programmers forget about locale-specific rules in their default case-mappings:

There is a case-insensitive match of strings s1 and s2 if they compare identically using the default case foldings defined by Unicode (which equates the ranges [a-z] and [A-Z]). Note that these do not include language-specific mappings, such as the dotted/dotless \'i\' mappings in Turkish or Azerbaijani (see Unicode Section 3.13 and the CaseFolding.txt file in the UCD).
Received on Thursday, 29 November 2007 16:08:16 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:16:24 UTC