W3C home > Mailing lists > Public > public-qt-comments@w3.org > April 2016

[Bug 29496] [FO31] parse-ietf-date with military timezones and leniency towards single-digit numbers

From: <bugzilla@jessica.w3.org>
Date: Thu, 28 Apr 2016 02:56:10 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-29496-523-Be5QCZDIdZ@http.www.w3.org/Bugs/Public/>

--- Comment #10 from Liam R E Quin <liam@w3.org> ---
Thanks, Abel. I agree that a TZ offset of 130 is weird but I don't see it as a
problem. None the less I'm also OK with disallowing it and allowing only (1:30,
01:30, 0130).  It doesn't come up often in practice but it does happen
(Newfoundland is an example). So on rereading in that spirit I'm ok with your
comment 7, although let's use tzoffset and not miltime for the name --
"Military time" is sometimes used to mean the 24-hour clock system, and I don't
think you're proposing to disallow 130 as equivalent to 1:30am in the time

You are receiving this mail because:
You are the QA Contact for the bug.
Received on Thursday, 28 April 2016 02:56:13 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:58:00 UTC