From mboxrd@z Thu Jan  1 00:00:00 1970
From: erik quanstrom <quanstro@quanstro.net>
Date: Mon, 28 Sep 2009 21:45:15 -0400
To: 9fans@9fans.net
Message-ID: <5951b8637c4bf7c8bd3515126ab454b6@ladd.quanstro.net>
In-Reply-To: <<1209a838da1003845b874b8a9ca0b4b7@isd.dp.ua>>
References: <<1209a838da1003845b874b8a9ca0b4b7@isd.dp.ua>>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] /adm/timezone/EET is bad
Topicbox-Message-UUID: 79407d86-ead5-11e9-9d60-3106f5b1d025

On Mon Sep 28 09:34:51 EDT 2009, yarikos@gmail.com wrote:
> Today I noticed my Plan 9 machine displayed time which is 1 hr past
> surrounding world.  Digging around, I found that DST start/end dates
> for Eastern-European Time (/adm/timezone/EET) for current year are
> bad.  Those follow pre-1996 conventions for ending dates and does DST
> switch 2 hours later.  For more information, see
> http://en.wikipedia.org/wiki/European_Summer_Time.
>
> Bundled program prints valid pair of dates for a given year in
> 1996-2099 range.
>
> Yaroslav.

that's pretty nifty.  i wish i had gotten my code that small.
i don't have formulae that compact.  when i generated us
time zones, i took the more intuitive approach of using
command lines like "dateof 2009 mar sun 1" or "dateof 2009
mar sun last".  that way it was easy enough to encode the
appropriate rules and generate tz files directly.

i dusted that stuff off and added eet.  the zones generated
for the us will be different by 1hr in the fall for 2007-.  repeat
2:00-3:00, not 1:00-2:00.

/n/sources/contrib/quanstro/timezone

i noticed that the system's eet starts in 1986 not 1977
as i think it should.  am i wrong?  i'm not an eet expert.

- erik