Re: I18N-ISSUE-242: Clarify case-insensitive match for domains [ITS-20] from Yves Savourel on 2013-01-21 (www-international@w3.org from January to March 2013)

From: Yves Savourel <ysavourel@enlaso.com>
Date: Mon, 21 Jan 2013 05:54:22 -0700
To: <public-multilingualweb-lt-comments@w3.org>
CC: "'www-international'" <www-international@w3.org>
Message-ID: <assp.0733595da2.assp.073347d593.00ad01cdf7d6$6f4f9180$4deeb480$@com>

Hi Norbert,

> http://www.w3.org/TR/2012/WD-its20-20121206/#domain
> 
> Steps 3-1-2-5 and 3-2-5 of the algorithm for interpreting values in 
> the Domain data category state "the mapping is case-insensitive".
>
> 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.

The aim is to try to avoid missing a mapping if the left side of the pair is not in the same case as the value retrieve through domainPointer.

But you make a good point: while it works fine with ASCII, having non-ASCII characters in the value would make things a lot more tricky.


cheers,
-yves

Received on Monday, 21 January 2013 12:54:52 UTC