- From: <bugzilla@jessica.w3.org>
- Date: Wed, 26 Sep 2012 15:47:09 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=19004
O'Neil Delpratt <oneil@saxonica.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
AssignedTo|oneil@saxonica.com |mike@saxonica.com
--- Comment #1 from O'Neil Delpratt <oneil@saxonica.com> 2012-09-26 15:47:09 UTC ---
(In reply to comment #0)
> The F&O 3.0 specification states that
>
> "If the primary format token contains at least one Unicode digit then it is
> taken as a decimal digit pattern, and in this case it must match the regular
> expression ^((\p{Nd}|#|[^\p{N}\p{L}])+?)$. If it contains a digit but does not
> match this pattern, an error is raised [err:FODF1310]."
Further down in the format-integer section of the specification there are some
'must' statements, indicating rules which the picture must abide by. The tests
are edge cases of these.
Therefore, the specification should be clearer in regards to defining a error
code for the 'must' statement and the regex.
I am raising this as a F&O spec issue. The change required is trivial enough,
but it does require flagging up to the WG.
--
Configure bugmail: https://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 Wednesday, 26 September 2012 15:47:10 UTC