A concrete example: "Exactly two years before McMurdo was established, blaa blaa seems to have happened there." It is reasonable to have that two years before return something reasonable in local time too. I think the 2013e version is more reasonable output. 2013d $ TZ=Antarctica/McMurdo date Mon Sep 23 18:56:23 NZST 2013 $ TZ=Antarctica/McMurdo date -d '59 years ago' Thu Sep 23 18:56:24 zzz 1954 2013e $ TZ=Antarctica/McMurdo date Mon Sep 23 18:57:52 NZST 2013 $ TZ=Antarctica/McMurdo date -d '59 years ago' Thu Sep 23 18:57:55 NZST 1954 Regards, Jaakko
On Sep 22, 2013, at 9:57 PM, Lester Caine <lester@lsces.co.uk> wrote:
A similar situation has now been created in the PHP API, which has also been switched to using TZ as the 'bible' when it comes to DST information. So the above statement applies ... except that the TZ data needs to return 'invalid' when a request is made that it can not process.
On Sun, 22 Sep 2013, Guy Harris wrote:
Such as any request for information given a date/time prior to the establishment of some form of standard time in the specified tzdb zone.
-- Foreca Ltd Jaakko.Hyvatti@foreca.com Keilaranta 1, FI-02150 Espoo, Finland http://www.foreca.com