On Sun 04 Feb 2018 at 14:39:44 (+0100), Thomas Schmitt wrote:
> Richard Hector wrote:
> > Incidentally, the gnu 'Date input formats' link above does talk about
> > only accepting English names for days and months, but doesn't say
> > anything about the ordering of day and month (except, under 'General
> > date syntax', saying that 'Order of the items is immaterial' ...)
> The preamble quote tells a lot about the disillusion of the writer
> of "Date input formats".
> The disease is much less obvious in german language, though. There you
> need to go down to quarter hours and regional habits to get truely ambigous.
> In english i sometimes have to riddle whether a date is Day/Month/Year or
> Month/Day/Year. Whatever the rules are, writers seem confused about them.
> Possibly because so many of us aliens are around.
> And what should human or machine think of my mail client's idea about
> when you sent your mail ?
> Tomorrow Richard Hector Re: policy around 'wontfix' bug tag
I don't know how you did that, but here:
$ date --debug -d "Mon, 5 Feb 2018 01:25:36 +1300"
date: parsed day part: Mon (day ordinal=0 number=1)
date: parsed date part: (Y-M-D) 2018-02-05
date: parsed time part: 01:25:36 TZ=+13:00
date: input timezone: +13:00 (set from parsed date/time string)
date: using specified time as starting value: '01:25:36'
date: warning: day (Mon) ignored when explicit dates are given
date: starting date/time: '(Y-M-D) 2018-02-05 01:25:36 TZ=+13:00'
date: '(Y-M-D) 2018-02-05 01:25:36 TZ=+13:00' = 1517747136 epoch-seconds
date: output timezone: -06:00 (set from TZ="US/Central" environment value)
date: final: 1517747136.000000000 (epoch-seconds)
date: final: (Y-M-D) 2018-02-04 12:25:36 (UTC0)
date: final: (Y-M-D) 2018-02-04 06:25:36 (output timezone TZ=-06:00)
Sun Feb 4 06:25:36 CST 2018
$ TZ=London date
Sun Feb 4 17:17:56 London 2018
$ TZ=NZ date
Mon Feb 5 06:17:58 NZDT 2018
Sun Feb 4 11:18:00 CST 2018