W3C home > Mailing lists > Public > public-qt-comments@w3.org > March 2013

[Bug 19004] [FO30] format-integer tests expecting err:FODF1310

From: <bugzilla@jessica.w3.org>
Date: Mon, 11 Mar 2013 08:45:46 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-19004-523-1LRkltmkQq@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=19004

--- Comment #18 from Michael Kay <mike@saxonica.com> ---
(In reply to comment #17)
> Sorry for my jumping in late. I am wondering if the new results of the
> following two test cases...
> 
> format-integer-025:
>   format-integer(1500000, '#')
>   1500000
> 
> format-integer-026
>   format-integer(1500000, '#a')
>   1500000
> 
> ...harmonize with the specification, which says that "there MUST be at least
> one mandatory-digit-sign" in decimal-digit-patterns.

Yes, they do, because the rule in question only applies when you have a
"decimal digit pattern", and you only have a decimal digit pattern when the
primary format token contains at least one digit. In fact, the rule cited is
now always true by definition.
> 
> Next, I am not sure where to spot the "default primary format" mentioned in
> comment #15.

I think comment #15 is using the phrase "default primary format token" to refer
to the token used when this rule is invoked: "If an implementation does not
support a numbering sequence represented by the given token, it must use a
format token of 1." Which in this case means that "#" and "#a" are not errors,
they are format tokens with an implementation-defined meaning, which is likely
to be "1".

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Monday, 11 March 2013 08:45:48 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:45:51 UTC