Hi,
On 2016-04-26 13:44:44, Maurice Kinal wrote to Wilfred van Velzen:
about: "Re: kernel 4.5.2":
WvV>> my computer knows in what timezone it is located, so it can
WvV>> calculate the offset.
MK> What good is that?
I like to keep in sync with the local world around me! If I use UTC time in
conversations when people expect local time, they might wonder what is wrong
with me. ;)
MK> In the case here the offset is zero so there is nothing for it to
MK> calculate. However if any of the locals in this neck of the woods asks me
MK> what time it is then I could do something like this;
MK> maurice@lilmikey [ ~ ]$ TZ=PST8PDT date +"%A, %d %B %Y, %T.%N %z"
MK> Tuesday, 26 April 2016, 06:39:11.512122527 -0700
Maybe you can put that in your fido messages as well, out of courtesy to the
rest of us?
MK> Also for the French speaking locals (there are a couple in the
MK> neighbourhood) this might be more meaningful to them;
MK> maurice@lilmikey [ ~ ]$ LANG=fr_CA.utf8 TZ=PST8PDT date +"%A, %d %B %Y,
MK> %T.%N %z" mardi, 26 avril 2016, 06:41:01.480260762 -0700
MK> Having done this I have to wonder what good any of this would be to anyone
MK> else and appears to be a total waste of bytes. I believe that the date,
MK> time and offset given at the top of my reply would be of the greatest use
MK> to you since it already is adjusted to your time which is how you figured
MK> out that the obsolete header time is UTC (+0000). Also if you were really
MK> curious you could have looked up the timezone for Ladysmith BC, Canada
MK> which is the location in the Origin line at the bottom.
Home work... I've done my share of that already. ;)
Plain UTC or my localtime provides me with less information then your localtime
+ utc offset.
I like to know what local time it is for people when they write something, that
provides me with important context about your circumstances!
MK> Kinderen van tegenwoordig. :::sigh:::
MK> Het leven is goed,
MK> Maurice
;)
(perfect translations!)
Bye, Wilfred.
--- FMail-W32 1.69.22.178-B20160331
* Origin: Native IPv6 connectable node (2:280/464)
|