Re: [charmod-norm] Case Folding (Section 2.1) - Sharp S example

I agree with @duerst and @asmusf. In particular, the purpose here is 
to point out a character whose Unicode case mapping is 'full' rather 
than 'simple'. Right or wrong (although I happen to think it is 
right), the sharp S meets that criterion.

I happen to think it is correct because, in addition to personal 
experience, etc., I recall the debate when U+1E9E was encoded. The 
main purpose cited then was, IIRC, to provide a code point for 
uppercase equivalent glyphs for cases like ALL CAPS TITLES in printing
 such as Martin mentions Duden using.

The Unicode FAQ is helpful here:

>  In standard German orthography, the sharp s ("ß") is uppercased to 
a sequence of two capital S 
> characters. This is a longstanding practice, and is reflected in the
 default case mappings in 
> Unicode. A capital form of ß is attested in a number of instances, 
and has thus been encoded in 
> the Unicode Standard. However, this character is not widely used, 
and is not recognized in the 
> official orthography as the uppercase form of ß. Therefore, the 
original mapping to "SS" is 
> retained in the Unicode character properties.

I'll address locale vs. language in a separate comment.

-- 
GitHub Notification of comment by aphillips
Please view or discuss this issue at 
https://github.com/w3c/charmod-norm/issues/68#issuecomment-180899664 
using your GitHub account

Received on Sunday, 7 February 2016 00:51:08 UTC