- From: <bugzilla@jessica.w3.org>
- Date: Fri, 29 Apr 2016 22:26:12 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29555 Abel Braaksma <abel.braaksma@xs4all.nl> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |abel.braaksma@xs4all.nl --- Comment #8 from Abel Braaksma <abel.braaksma@xs4all.nl> --- A few additional observations that I think fit the scope of this bug-report (while supporting the proposed solutions): (1) Typo in the 2nd of the last three bullets of "9.8.4.3 The Width Modifier", s/should/SHOULD/, i.e. replace: "For timezone offsets this should be done by" with: "For timezone offsets this SHOULD be done by" (2) Also, that same paragraph suggests that: [ZN,5] with tz 00:00 as "GMT:00" [ZN,8] with tz 00:00 as "000GMT:00" [Z00,6] with tz as 05:30 as "005:30" (this seems the intended meaning) [ZZ,8-*] with tz as 05:00 as "0000R:00 I think this can be fixed by specifying, just like the first bullet point, that it only applies when numeric tz representations are requested. Perhaps by starting the paragraph with: "For numerical representations of timezone offsets, this SHOULD be [...]" (3) And one more nitpick: the paragraph just before this section may be more correct or complete if it added "by choosing one of the following", i.e.: "If the full representation of the value is shorter than the specified minimum width, then the processor should pad the value to the specified width by choosing one and only one of the following options:" (this prevents the overlap between "numerical presentation of numbers" and "timezone offsets") -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Friday, 29 April 2016 22:26:15 UTC