- From: klensin via GitHub <sysbot+gh@w3.org>
- Date: Thu, 04 Feb 2016 03:21:52 +0000
- To: public-i18n-archive@w3.org
klensin has just created a new issue for https://github.com/w3c/charmod-norm: == Case Folding (Section 2.1) - Sharp S example == I recommend not using Sharp S as an example. While the explanation is consistent with the Unicode one, with the introduction of U+1E9E, one of the main arguments for that particular "case" folding/ mapping has dissolved into "stability", i.e., "we did it that way before so we need to continue" (not necessarily a bad argument, but different from "need to map to "SS" because there is no upper case and then back to "ss"). There is also a case to be made that the appropriateness or inappropriateness of that mapping is narrowly locale-dependent and is seems to me that this section doesn't want to go there. Please view or discuss this issue at https://github.com/w3c/charmod-norm/issues/68 using your GitHub account
Received on Thursday, 4 February 2016 03:21:54 UTC