[Bug 27338] fn:parse-ietf-date

https://www.w3.org/Bugs/Public/show_bug.cgi?id=27338

--- Comment #3 from Liam R E Quin <liam@w3.org> ---
[left open because we should consider changing the grammar]

* parse-ietf-date-15
fixed, thanks!

On whitespace, the description says,
Accepts one or more whitespace characters (x20, x09, x0A, x0D) wherever a
single space is required

Probably the grammar should use a + in the definition of S; the grammars I
merged to get here were rather imprecise about such things, unfortunately.


* parse-ietf-date-19

fixed, thanks!

* parse-ietf-date-20, parse-ietf-date-21, parse-ietf-date-22,
parse-ietf-date-23
fixed (same error)

* parse-ietf-date-errs9
Hah you're right, the - is taken as a separator. Fixed; the new version should
I think be an error. You can't actually get a negative year in there by the
grammar, of course, so unless an implementor tried to cheat by using a
parsedate() library function and forgot to test for this case it seems
unlikely.

Thanks for the report!

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Thursday, 4 December 2014 03:27:23 UTC