[Bug 8456] [FO11] Behaviour of 'FULLY-NORMALIZED' not well defined in fn:normalize-unicode

http://www.w3.org/Bugs/Public/show_bug.cgi?id=8456





--- Comment #2 from Michael Kay <mike@saxonica.com>  2010-01-13 11:35:43 ---
I propose that (a) in the 1.0 spec, we don't fix this; (b) in 1.1, we fix it as
follows:

Delete the sentence "See [Character Model for the World Wide Web 1.0:
Normalization] for a description of the normalization forms."

Substitute "Normalization forms NFC, NFD, NFKC, and NFKD, and algorithms for
converting a string to each of these forms, are defined in [Unicode
Normalization]." where this is a new normative reference to
http://unicode.org/reports/tr15/. Add the standard wording about which version
of Unicode may be used.

Add "The motivation for normalization form FULLY-NORMALIZED is described in
[charmod-norm]." {which now becomes a non-normative reference} "However, as
that specification did not progress beyond working draft status, the normative
specification is as follows.

A string is fully-normalized if (a) it is normalization form NFC as defined by
[Unicode Normalization], and (b) it does not start with a composing character.

A composing character is a character that is one or both of the following: 

(a) the second character in the canonical decomposition mapping of some
character that is not listed in the Composition Exclusion Table defined in [UTR
#15], or

(b) of non-zero canonical combining class (as defined in [Unicode]).

A string is converted to FULLY-NORMALIZED form as follows:

(a) if the first character in the string is a composing character, prepend a
single space

(b) convert the string to normalization form NFC


-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Wednesday, 13 January 2010 11:35:45 UTC