17099 2012-05-18 11:04:43 +0000 [FO30] format-integer invalid picture string 2012-06-13 08:41:30 +0000 1 1 1 Unclassified XPath / XQuery / XSLT Functions and Operators 3.0 Last Call drafts PC All CLOSED FIXED P2 normal --- 14873 1 mike mike tim public-qt-comments oldest_to_newest 67859 0 mike 2012-05-18 11:04:43 +0000 We now have unambiguous rules for separating the picture string of format-integer into a primary format token and modifiers; but we still have some ambiguity about how errors in the primary format token are handled. In particular, for the first form of format token (consisting of digits, '#' signs, and grouping separators), we say "With this form, the primary format token must match the regular expression ^((\p{Nd}|#|[^\p{N}\p{L}])+?)$". The question is, what happens if it doesn't? There are two possible interpretations: (a) it doesn't belong to this form of format token, it belongs to some other form, presumably the last form, which is implementatation defined, falling back to "1" if it's not recognized. (b) it's an error. I think the intent is (b), in which case we ought to make this clear, and should define an error code. I propose to clarify that any format token that contains at least one Unicode digit belongs to the first form of format token and must conform to the rules for that form, otherwise a dynamic error occurs, for which I intend to re-use FODF1310. A number of test cases in test set fn-format-integer are affected, in particular those that currently raise XTDE0030. 68274 1 mike 2012-05-29 17:06:43 +0000 The proposal was accepted.