- From: <bugzilla@wiggum.w3.org>
- Date: Tue, 08 Dec 2009 12:41:37 +0000
- To: public-qt-comments@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8456
Summary: Behaviour of 'FULLY-NORMALIZED' not well defined in
fn:normalize-unicode
Product: XPath / XQuery / XSLT
Version: Working drafts
Platform: PC
OS/Version: Windows NT
Status: NEW
Severity: normal
Priority: P2
Component: Functions and Operators 1.1
AssignedTo: mike@saxonica.com
ReportedBy: oliver@cbcl.co.uk
QAContact: public-qt-comments@w3.org
The specification of normalize-unicode states:
Returns the value of $arg normalized according to the normalization criteria
for a normalization form identified by the value of $normalizationForm
It also refers to:
See [Character Model for the World Wide Web 1.0: Normalization] for a
description of the normalization forms.
However, consider the following query:
normalize-string('̂', 'FULLY-NORMALIZED')
Normalizing this string does not produce a fully normalized result. I assume
the correct way to fully normalize this is to add a leading space character,
but I cannot see where this behaviour is specified.
--
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 Tuesday, 8 December 2009 12:41:46 UTC