- From: <bugzilla@jessica.w3.org>
- Date: Mon, 10 Feb 2014 17:47:04 +0000
- To: public-i18n-core@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16970 --- Comment #6 from Addison Phillips <addison@lab126.com> --- In cases where existing implementations don't agree (which is what John Daggett asserts is the case here), I think it is reasonable to specify the best reasonable algorithm for the case. In re-reading section 2.3 this morning, what is striking is that case sensitive comparison does not do normalization. This suggests that Unicode caseless matching probably should not do normalization--particularly the destructive compatibility (K) normalization--either. Moving to Unicode default caseless matching would introduce a "normalization" issue with the identifiers in question, but it is clearly a normalization issue that already exists. At the same time, removing the normalization step would simplify implementation (particularly since Unicode's caseless matching uses the less-common NFD/NFKD normalizations). -- You are receiving this mail because: You are on the CC list for the bug.
Received on Monday, 10 February 2014 17:47:07 UTC