This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Normalization form FULLY-NORMALIZED is used in test cases cbcl-fn-normalize-unicode-001 and cbcl-fn-normalize-unicode-006. fn:normalize-unicode says, in part: "Conforming implementations must support normalization form "NFC" and may support normalization forms "NFD", "NFKC", "NFKD", and "FULLY-NORMALIZED". They may also support other normalization forms with ·implementation-defined semantics." I believe that both test cases should accept error FOCH0003, indicating that FULLY-NORMALIZED is not one of the values supported by the implementation.
Fixed as suggested. Please mark as CLOSED if you agree with the resolution. Otherwise, REOPEN.
I have introduced a new "dependency" for unicode-normalization-form and have use this to mark tests that have a dependency on any of the normalization forms which processors are not obliged to support. For the two tests cited, I have split them into two variants one for processors that support the normalization form, one for those that don't.