control: retitle -1 date: weird timezones displayed for old dates Wed, 6 Mar 2013, 18:48 -07:00 from Bob Proulx <b...@proulx.com>: > What is the timezone name for EET? So that we can reproduce your test > case correctly? > ... > Without knowing which localized timezone you are using it is > going to be harder to debug. Each table is unique.
$ cat /etc/timezone Europe/Kiev > > $ date --date='@0' > > Thu Jan 1 03:00:00 MSK 1970 > > Your timezone appears to be +0300 hours from UTC. No, as for now, it's +0200, and +0300 is only for DST ;) (BTW, +0400 has nothing to do with my system, it just belongs to the web mail service). > Instead of using the old legacy default date output format which is > ambiguous. It is much more useful to use the date -R format which > displays the output using a standard unambiguous format. OK, got it. > Working with time in UTC is almost always the most trouble free way to > do things. Yes, I agree with you. > Note that there is no need for quoting those strings above. There are > no spaces and no special shell characters to protect against. Oh, I've just copied the syntax from the date manpage. > All of those seem correct to me. Perhaps I am just not looking at the > right part of things. What output were you expecting? $ date -d "12 Aug 1910 15:00" Fri Aug 12 15:00:00 KMT 1910 $ date -d "12 Aug 1910 15:00UTC" Fri Aug 12 17:02:04 KMT 1910 $ date -d "12 Aug 1910 15:00UTC" -R Fri, 12 Aug 1910 17:02:04 +0202 I was just playing with old dates; EET & EEST looked OK, in contrast to MSK, KMT & LMT; looks like it's not a bug, but a cool feature trying to display the old-style date/time for a specific location (not considering Julian / Gregorian calendar variation though). Where a table describing all these things like MSK, KMT & LMT can be found?
