On Thu, 4 Mar 1999, Will Baldwin wrote:
> S�ndningsdatum: Thu, 4 Mar 1999 22:14:44 +500
> Fr�n: Will Baldwin <[EMAIL PROTECTED]>
> �mne: TZ variable for Pegasus
> Someone said that for emails to display the correct time offset from
> GMT, for Pegasus, they should have a Set statement to set TZ to
> something like +0200, or something. Is this correct? I don't use
> Pegasus, but was told that for Blue Wave to work correctly for me, I
> need to have TZ=EST5, for non-daylight savings time, and TZ=EST5EDT
> for daylight savings time. That's because I live in the Eastern U.S.
>
> I've heard that most programs compiled w/C automatically look for TZ,
> for some reason. I suppose there are other ways to set it. Perhaps
> for me, using TZ=+0500 would work, too. I've heard there are many
> other variations, too.
>
>
> -- [EMAIL PROTECTED][EMAIL PROTECTED] Anderson, IN, USA
>
>
> Net-Tamer V 1.11X - Test Drive
>
>
Well, as you said, there are many ways of specifying the timezone
where you live. You could do it with letters like "EST" (which is a
little bit confusing for Europeans not familiar with American
timezones) or with digits indicating the offset from "UT" (Universal
Time), formerly better known as "GMT", Greenwich Mean Time. If you
live to the East of Greenwich (in England) you would have a positive
offset, like +0100 (hhmm) for myself, living in Sweden, or +0200 for
Or Botton, living in Israel, who was the one asking about how to set
the timezone in Pegasus. If you live to the West of Greenwich you
would have a *negative* offset. Yours would probably then be -0500.
The famous document which specifies how this should be done in e-mail
is called RFC 822, "Standard for the Format of ARPA Internet Text
Messages". It says the offset, when specified in digits, *should*
have four digits. I have no idea why the program you are using for
your e-mail, Nettamer, uses only three, and a positive value at that.
This is clearly not conformant with RFC 822. Here is the actual text
from RFC 822:
------------------------------
August 13, 1982 - 25 - RFC #822
Standard for ARPA Internet Text Messages
5. DATE AND TIME SPECIFICATION
5.1. SYNTAX
date-time = [ day "," ] date time ; dd mm yy
; hh:mm:ss zzz
day = "Mon" / "Tue" / "Wed" / "Thu"
/ "Fri" / "Sat" / "Sun"
date = 1*2DIGIT month 2DIGIT ; day month year
; e.g. 20 Jun 82
month = "Jan" / "Feb" / "Mar" / "Apr"
/ "May" / "Jun" / "Jul" / "Aug"
/ "Sep" / "Oct" / "Nov" / "Dec"
time = hour zone ; ANSI and Military
hour = 2DIGIT ":" 2DIGIT [":" 2DIGIT]
; 00:00:00 - 23:59:59
zone = "UT" / "GMT" ; Universal Time
; North American : UT
/ "EST" / "EDT" ; Eastern: - 5/ - 4
/ "CST" / "CDT" ; Central: - 6/ - 5
/ "MST" / "MDT" ; Mountain: - 7/ - 6
/ "PST" / "PDT" ; Pacific: - 8/ - 7
/ 1ALPHA ; Military: Z = UT;
; A:-1; (J not used)
; M:-12; N:+1; Y:+12
/ ( ("+" / "-") 4DIGIT ) ; Local differential
; hours+min. (HHMM)
5.2. SEMANTICS
If included, day-of-week must be the day implied by the date
specification.
Time zone may be indicated in several ways. "UT" is Univer-
sal Time (formerly called "Greenwich Mean Time"); "GMT" is per-
mitted as a reference to Universal Time. The military standard
uses a single character for each zone. "Z" is Universal Time.
"A" indicates one hour earlier, and "M" indicates 12 hours ear-
lier; "N" is one hour later, and "Y" is 12 hours later. The
letter "J" is not used. The other remaining two forms are taken
from ANSI standard X3.51-1975. One allows explicit indication of
the amount of offset from UT; the other uses common 3-character
strings for indicating time zones in North America.
------------------------------
Lars-Einar Jansson
Stockholm, Sweden
To unsubscribe from SURVPC send a message to [EMAIL PROTECTED] with
unsubscribe SURVPC in the body of the message.
Also, trim this footer from any quoted replies.
