Page MenuHomePhabricator

some #timel codes incorrectly assume that local time is still UTC
Closed, DuplicatePublic

Description

Author: xaviersmp

Description:
I could not find any variable to print the timezone of {{LOCALTIME}} so I tried to code one by myself using Parserfunctions and I found that some of the {{#timel}} codes assume that the time is in UTC even when this is not true, and this produces an incorrect output:

{{#timel:c}} should print the ISO 8601 formatted date, but it incorrectly prints a +00:00 timezone creating a false timestamp.

{{#timel:r}} should print the RFC 2822 formatted date, but it always prints a +0000 timezone. http://tools.ietf.org/html/rfc2822 specifies that +0000 precisely means UTC and it also specifies that when the timezone is not sure and may not be UTC the correct output is -0000.

{{#timel:U}} should print the number of seconds since January 1 1970 00:00:00 GMT. This number is incorrect.

You can find my tests in http://ca.wikipedia.org/w/index.php?oldid=7174012


Version: unspecified
Severity: normal
URL: http://ca.wikipedia.org/w/index.php?oldid=7174012

Details

Reference
bz28353

Event Timeline

bzimport raised the priority of this task from to High.Nov 21 2014, 11:28 PM
bzimport added a project: ParserFunctions.
bzimport set Reference to bz28353.
bzimport added a subscriber: Unknown Object (MLST).
  • This bug has been marked as a duplicate of bug 7133 ***