W3C home > Mailing lists > Public > www-international@w3.org > January to March 2013

Re: [ISSUE-102] I18N-ISSUE-242: Clarify case-insensitive match for domains [ITS-20]

From: Norbert Lindenberg <w3@norbertlindenberg.com>
Date: Wed, 27 Feb 2013 21:53:32 -0800
Cc: Norbert Lindenberg <w3@norbertlindenberg.com>, <public-multilingualweb-lt-comments@w3.org>, "'www-international'" <www-international@w3.org>
Message-Id: <0BF6168B-CF93-4F83-8D33-48A7E4A4A2B3@norbertlindenberg.com>
To: Yves Savourel <ysavourel@enlaso.com>
Yes, it does.

Norbert


On Jan 23, 2013, at 8:19 , Yves Savourel wrote:

> Hi Norbert,
> 
> https://www.w3.org/International/multilingualweb/lt/track/issues/102
> 
>> First, is case-insensitive matching really necessary here? 
>> In discussions of other technologies, e.g. CSS, we found 
>> that it's hard to get case-insensitive matching right, 
>> i.e. make it work so that it doesn't have surprising/confusing 
>> results in some languages, while strict string equality 
>> is easy to understand.
>> 
>> Second, if it is really necessary, then the precise meaning of 
>> "case-insensitive" matching has to be specified. Unicode 
>> case-folding using the C and F mappings of the Unicode data 
>> file CaseFolding.txt is our normal recommendation.
> 
> After reviewing the advantages of using non-case-sensitive mapping vs. the problem of folding non-ASCII characters, we think it's simpler to drop non-case-sensitivity mapping.
> 
> Could you please confirm that this solution addresses your concern?
> 
> Thanks,
> -yves
> 
> 
> 
> 
> 
Received on Thursday, 28 February 2013 05:54:03 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 28 February 2013 05:54:04 GMT