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 28567 - [FO31] format-number: grouping-separators, mantissa part
Summary: [FO31] format-number: grouping-separators, mantissa part
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: Functions and Operators 3.1 (show other bugs)
Version: Working drafts
Hardware: PC Windows NT
: 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:
: 28682 (view as bug list)
Depends on:
Blocks:
 
Reported: 2015-04-27 16:15 UTC by Debbie Lockett
Modified: 2016-12-16 19:55 UTC (History)
1 user (show)

See Also:


Attachments

Description Debbie Lockett 2015-04-27 16:15:10 UTC
A few of issues with the format-number() function.

1. The last example in 4.7.2 should say: returns "12.346E2"

2. 4.7.3 includes the rule:
"A sub-picture must contain at least one character that is an optional-digit-sign or a member of the decimal-digit-family."
I believe a new rule (or amendment) is required to say:
"The mantissa part must contain at least one character that is an optional-digit-sign or a member of the decimal-digit-family."
e.g. so that a pattern such as ".e99" is not allowed.

3. 4.7.3 includes the rule:
"A sub-picture must not contain a grouping-separator-sign adjacent to a decimal-separator-sign."
Should there in fact be a rule to say that a grouping-separator-sign is not allowed at the end of an integer part?
e.g. consider the pattern "#,".

4. There is no rule to say that grouping-separator-signs can not be adjacent. Should there be? If this is allowed, I believe that by following the algorithm in 4.7.4 (Analysing the picture string) currently duplicates get ignored e.g. format-number(12345.678, '#,,###') returns 12,345
Comment 1 Michael Kay 2015-05-05 17:17:04 UTC
The changes were accepted and have been applied.
Comment 2 Michael Kay 2015-05-23 18:56:41 UTC
*** Bug 28682 has been marked as a duplicate of this bug. ***