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 2712 - [XSLT 2.0] format-number(NaN)
Summary: [XSLT 2.0] format-number(NaN)
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XSLT 2.0 (show other bugs)
Version: Candidate Recommendation
Hardware: PC Windows XP
: P2 normal
Target Milestone: ---
Assignee: Michael Kay
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-01-13 17:50 UTC by Michael Kay
Modified: 2006-01-27 20:59 UTC (History)
0 users

See Also:

Attachments

Description Michael Kay 2006-01-13 17:50:17 UTC 
Rule 1 at http://www.w3.org/TR/xslt20/#formatting-the-number specifies that NaN
is formatted using the prefix and suffix of the positive sub-picture. This
appears to be incompatible with XSLT 1.0, which ignores the prefix and suffix in
this case. The JSK 1.1.8 documentation (which 1.0 references) states:

* NaN is formatted as a single character, typically \\uFFFD.

* +/-Infinity is formatted as a single character, typically \\u221E, plus the
positive and negative pre/suffixes.

The "single character" is nonsense (though it's still there in the JDK 1.5
spec): DecimalFormatSymbols allows a String for these symbols! 

But the spec does say (in effect) that the prefix/suffix are NOT used for the
NaN case.

A post on the mulberry xsl-list today has pointed out this backwards
incompatibility with existing XSLT 1.0 implementations (citing Saxon and Xalan).
Comment 1 Michael Kay 2006-01-27 20:58:53 UTC 
This change was agreed by the WG and has been applied.