Would you consider the ICU4J method com.ibm.icu.text.UTF16.charAt [1] to be in 
violation of C1 because it can return surrogate code points?

Or the ICU4J method com.ibm.icu.lang.UCharacter.isUUppercase [2] because it's a 
predicate that tells you that surrogate code points do not represent upper case 
characters?

Or the ICU4J method com.ibm.icu.lang.UCharacter.toUpperCase [3] because it's a 
transform that maps surrogate code points to themselves as their upper case 
form?

Norbert

[1] 
http://icu-project.org/apiref/icu4j/com/ibm/icu/text/UTF16.html#charAt(java.lang.CharSequence,%20int)
[2] 
http://icu-project.org/apiref/icu4j/com/ibm/icu/lang/UCharacter.html#isUUppercase(int)
[3] 
http://icu-project.org/apiref/icu4j/com/ibm/icu/lang/UCharacter.html#toUpperCase(int)


On Mar 26, 2012, at 23:11 , Glenn Adams wrote:

> 
> On Mon, Mar 26, 2012 at 10:37 PM, Norbert Lindenberg 
> <[email protected]> wrote:
> The conformance clause doesn't say anything about the interpretation of 
> (UTF-16) code units as code points. To check conformance with C1, you have to 
> look at how the resulting code points are actually further interpreted.
> 
> True, but if the proposed language
> 
> "A code unit that is in the range 0xD800 to 0xDFFF, but is not part of a 
> surrogate pair, is interpreted as a code point with the same value."
>  
> is adopted, then will not this have an effect of creating unpaired surrogates 
> as code points? If so, then by my estimation, this will increase the 
> likelihood of their being interpreted as abstract characters... e.g., if the 
> unpaired code unit is interpreted as a unpaired surrogate code point, and 
> some process/function performs any predicate or transform on that code point, 
> then that amounts to interpreting it as an abstract character.
> 
> I would rather see such unpaired code unit either (1) be mapped to U+00FFFD, 
> or (2) an exception raised when performing an operation that requires 
> conversion of the UTF-16 code unit sequence.

_______________________________________________
es-discuss mailing list
[email protected]
https://mail.mozilla.org/listinfo/es-discuss

Reply via email to