To use ZoneTime, a zone name and an offset must be passed as command line arguments.
The easiest way to do this is to use a Windows shortcut, because it only needs doing
once, and an icon will be displayed for the shortcut based on the program file.

(More accurately, a command argument will need its offset changing whenever its zone
changes from daylight saving time to winter time or vice versa. Precise dates depend
on politics and geography, and given that a person would use this tool to show only
the zones they need, it is intractably difficult and pointless to try to automate this
much detail in such a small tool! You're on your own... :)

Example of a command line in a shortcut, immediately after making it:
"C:\windows\Desktop\LuaTools\Examples\ZoneTime\ZoneTime.exe"

Immediately following that text, add a space, then the line below:
"Britain:\t\t" 1 "Germany:\t\t" 2 "East US:\t\t" -4 "East AUS:\t" 10

Include ALL characters, including double-quotes. They let you use spaces in names.

This will demonstrate the method, and after seeing how it looks, it can be modified as
needed to display several zone times, probably as many as the screen can show you.

======================================================================================

What follows is a demonstration of an assertion made in the Lua file.
Extraordinary claims need extraordinary proof...

WD={"Sun","Mon","Tue","Wed","Thu","Fri","Sat"}  T={1872,5,18,0,0,0}
a.clk(T)  a.clk(T)  --Call twice, first to get a timestamp, then to get the weekday.
c.put(string.format("%02d/%02d/%04d\t%02d:%02d:%02d  \t(%s)",T[3],T[2],T[1],T[4],T[5],T[6],WD[T[7]]))

So as you can see, he really WAS born on a Saturday.
Just so you know... many tools that claim to handle UNIX time could not have told you that because
they break or lie when given a negative UNIX timestamp or a date before the start of the year 1970.
