-=> mark lewis wrote to Wilfred van Velzen <=-


 ml> 26 Apr 16 19:38, you wrote to Maurice Kinal:

 MK>> calculate.  However if any of the locals in this neck of the woods
 MK>> asks me 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

 WV> Maybe you can put that in your fido messages as well, out of courtesy
 WV> to the rest of us?

 ml> why? his special time stamp header thingee does the conversion to your
 ml> time for you... his software can specialize that for those he adds to
 ml> some lookup table or address book... when he writes to you, that stamp

Linux is really good for time zone calcuations, because it tends to come with a
complete list of time zone info, including Daylight Savings transitions, and a
simple

TZ=

can do a lot of conversions.  I use a similar trick on my IRLP node to schedule
connections to nets that are scheduled in some other time zone.  The script is
called

tzschedule [week]     [parameters]

[week] is the week of the month.  This triggers extra logic for schedules that
are like "second Tuesday of the month", since cron doesn't handle this well.

 is the name of the time zone to schedule the event in, eg UTC

 is the hour of the event in the foreign time zone.

 [parameters] is the commandline to run

This script is designed to be called from cron. :)

 ml> will be the time in your area when he writes his post... if he writes
 ml> to someone in Oz two minutes later, the new post's header will have the
 ml> time in the Oz timezone that he is writing the post... if both were
 ml> taken and converted to UTC they would be two minutes apart... the same
 ml> if they are both converted to another timezone...

Cool. :)



 ml> )\/(ark

 ml> Always Mount a Scratch Monkey

 ml> ... Cat HAIR all over the keyboard. Don't blame me for spelling errors

Haha, know the problem. :)



... Variables won`t; constants aren`t.
--- MultiMail/Win32 v0.49