On Tue, Apr 18, 2000 at 03:06:03AM +0900, Tim Seifert wrote:
> Seeing as locale has limited support for more unusual timezones, and
> none for daylight savings.
True, but not worse than it was before. The granularity is one hour, and
you can set any offset relative to GMT you need. The old ENV:TZ method
worked the same way. DST is (indirectly) supported by moving the highlighted
bar in Locale preferences one slot to the right during the summer. With
ENV:TZ you had to decrease the number in the variable by one. The effect
is the same.
> Being able to set something like a MIAMI_TZ
> variable, may be of some use (avoiding other problems with the general
> TZ variable).
I'll probably add an optional ENV:MIAMI/TIMEZONE in the next version
with a higher granularity (minutes most likely) and a format such as
"+0100" to support those few areas in the world which have DST offsets
of fractions of an hour.
> Likewise, some way for Miami to understand whether
> daylight savings is currently in effect.
That would not really help. You need to change your system clock for DST
anyway, and any changes to the DST status in applications has to be kept
in sync with that, or your time calculations will be off by one hour.
This means automatic changes to the DST status in applications would only
make matters worse.
--
Holger Kruse
[EMAIL PROTECTED]
--
To unsubscribe send "unsubscribe miamidx-talk-ml" to
"[EMAIL PROTECTED]". For help on list commands send "help" to
"[EMAIL PROTECTED]".
