This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 2652 - Alternative result for fn-normalize-unicode-2
Summary: Alternative result for fn-normalize-unicode-2
Status: CLOSED FIXED
Alias: None
Product: XML Query Test Suite
Classification: Unclassified
Component: XML Query Test Suite (show other bugs)
Version: 0.8.4
Hardware: PC Windows XP
: P2 normal
Target Milestone: ---
Assignee: Carmelo Montanez
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-01-05 16:40 UTC by Michael Kay
Modified: 2006-01-11 21:25 UTC (History)
0 users

See Also:


Attachments

Description Michael Kay 2006-01-05 16:40:50 UTC
The first argument to the function is an ASCII string. The result of normalizing
an ASCII string is always the same as the input string, regardless of the
normalization form used. 

The spec says:

(XPath 3.1.5): a function need not evaluate an argument if the function can
evaluate its body without evaluating that argument.

(XPath 2.3.4): If, at such an intermediate stage of evaluation, a processor is
able to establish that there are only two possible outcomes of evaluating Q,
namely the value V or an error, then the processor may deliver the result V
without evaluating further items in the operand E. 

In this case it is not necessary to evaluate the second argument once it is
known that the first argument consists entirely of characters that are
unaffected by any of the normalization algorithms.

This might seem rather pedantic, but an implementation that doesn't report an
error here is conformant under these rules, so it would be better to change the
first argument to a non-ASCII string to ensure interoperable results.
Comment 1 Carmelo Montanez 2006-01-11 20:41:16 UTC
Fixed.  Used a non ascii character for first argument.  Please close the bug 
when able to verify.

Thanks,
Carmelo