- tz - lists.iana.org

change in Jordan daylight savings
by hsm6second＠mac.com Sept. 30, 2006

Sept. 30, 2006

In its infinite wisdom the government here decided to end daylight savings as usual on 29 September. Not sure exactly when they eventually will (always unpredictable), but most likely not before 20 October. So Jordan is still GMT+3. Hope this is quickly updated in TZ. Thanks. --Hilal

1 0

RE: Question on abbreviations
by Paul Schauble Sept. 29, 2006

Sept. 29, 2006

So in this case: Rule US 1942 only - Feb 9 2:00 1:00 W # War Rule US 1945 only - Aug 14 23:00u 1:00 P # Peace Why is %s undefined in 1943? This was the question that started the thread. If the time setting carries forward, surely the letter should also. ++PLS -----Original Message----- From: tz-request(a)elsie.nci.nih.gov [mailto:tz-request@elsie.nci.nih.gov] On Behalf Of Ken Pizzini Sent: Wednesday, September 27, 2006 3:14 PM To: tz(a)lecserver.nci.nih.gov Subject: Re: Question on abbreviations On Wed, Sep 27, 2006 at 02:37:58PM -0700, Mark Davis wrote: > I share your confusion. If Paul (Eggert's) description is right, then I have > to ignore the TO field in some circumstances which are entirely unclear to > me. I would much rather see the TO field corrected. That is, if TO=1942 is > ignored, and 1945 is the real date, then the line should be corrected to > TO=1945. The key to understanding is that the rules describe a list of *transitions*. After a transition, the described effect on zone offset and abbreviation *remain* in effect until the next transition. The "TO" part of a rule is used to enable a shorthand for a _recurring_ transition, such as "first Tuesday of February", for all years within the range. If "to" is "only", then the *transition* being documented is a singleton, but the transitioned-into offset/abbreviation remains in effect until the _next_ transition, no matter how far in the future. > There are other failures in the parsing. My error messages are: ... > I looked into why this is happening, and found: > > Zone Europe/Amsterdam 0:19:32 - LMT 1835 > 0:19:32 Neth %s 1937 Jul 1 > But the first LETTER/S defined by Neth is in 1916, so during the range from > 1835 to 1916 this is undefined. If the LETTER/S are magically also defined > *before* the first FROM, that should be described in the specification. Yes, this is a failure of the documentation. If a Zone refers to a time within a Rule that is before the first transition mentioned for that rule, then the _oldest_standard_time_ "Letter/s" is used. In this case, AMT. > BTW, the documentation was a first a bit confusing to me, since it says that > fields are delimited by spaces, and lists a single Zone UNTIL field. > However, if you look carefully at the documentation, there are really 4 > fields: > > UNTIL_YEAR UNTIL_IN UNTIL_ON UNTIL_AT > > which are optional [but only in "truncation" from the end: that is, it > corresponds to the (Perl) regex (UNTIL_YEAR (UNTIL_IN (UNTIL_ON > (UNTIL_AT)?)?)?)?]. > > I'm not the only one to have initially made this mistake: the proposed XML > format for the TZ database makes the same mistake. Confusing: granted. Whether "Until" is one or multiple fields is a matter of interpretation. The _traditional_ understanding is that it is a *single* "timestamp field" which may happen to have spaces within it. BTW the subfields aren't "YEAR IN ON AT", but "YEAR MONTH DAY TIME". In this regard, a recent addition to the tzcode tarball is zoneinfo2tdf.pl, which translates the more free-with-spaces zone tzdata into a form which strictly uses a single tab between fields. This may make life easier for some by simplifying their parser's requirements. (Or not.) --Ken Pizzini

5 12

FW: timezone modification for Uruguay
by Olson, Arthur David (NIH/NCI) [E] Sept. 28, 2006

Sept. 28, 2006

Toshiro is not on the time zone mailing list; direct replies appropriately. --ado -----Original Message----- From: toshiro(a)internet.com.uy [mailto:toshiro@internet.com.uy] Sent: Thursday, September 28, 2006 12:59 PM To: tz(a)lecserver.nci.nih.gov Subject: timezone modification for Uruguay The gobernment decreed to modify the timezone every year automatically from now until further notice the first Sunday of October at 2:00 AM (1 hour forward) and the second Sunday of March at 2:00 AM (1 hour behind). url: http://www.presidencia.gub.uy/_web/decretos/2006/09/CM%20210_08%2006%202 006_00001.PDF

3 2

timezone modification for Uruguay
by toshiro＠internet.com.uy Sept. 28, 2006

Sept. 28, 2006

The gobernment decreed to modify the timezone every year automatically from now until further notice the first Sunday of October at 2:00 AM (1 hour forward) and the second Sunday of March at 2:00 AM (1 hour behind). url: http://www.presidencia.gub.uy/_web/decretos/2006/09/CM%20210_08%2006%202006…

1 0

RE: Question on abbreviations
by Paul Schauble Sept. 28, 2006

Sept. 28, 2006

Then I'm confused. At the end of 1942, that rule should expire, because of the "only" leaving what rule in effect? Apparently none, leaving the time in 1943 undefined. Where can I find a explanation of the tz text database format? Thanks, ++PLS -----Original Message----- From: tz-request(a)elsie.nci.nih.gov [mailto:tz-request@elsie.nci.nih.gov] On Behalf Of Paul Eggert Sent: Wednesday, September 27, 2006 9:29 AM To: tz(a)lecserver.nci.nih.gov Subject: Re: Question on abbreviations "Mark Davis" <mark.davis(a)icu-project.org> writes: > According to the spec, TO = "only" is equivalent to saying that the TO value > equals the FROM value. Yes, that's what's happening here. The rule to switch to DST applies only in 1942. There is no rule to switch _out_ of DST in 1942, so DST continues until 1945, the next rule that applies. >> Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S >> > ... >> > Rule US 1942 only - Feb 9 2:00 1:00 W # War >> > Rule US 1945 only - Aug 14 23:00u 1:00 P #

4 6

New country codes: RS, ME
by Mark Davis Sept. 28, 2006

Sept. 28, 2006

There are new country codes RS for Serbia and ME for Montenegro. http://www.iso.org/iso/en/prods-services/iso3166ma/03updates-on-iso-3166/nl… I would suggest the following changes: In zone.tab Change the line: CS +4450+02030 Europe/Belgrade to: RS +4450+02030 Europe/Belgrade Add: ME +4247+01928 Europe/Podgorica In europe Add: Link Europe/Belgrade Europe/Podgorica Mark

2 1

RE: Question on abbreviations
by Paul Schauble Sept. 27, 2006

Sept. 27, 2006

There is also the original issue of %s being null in 1943. This seems to be a bug. But maybe not. I'm unable from the documents I've seen to determine the intended behavior. None the less, it seems obvious to me that either both the time resulting from the transition and the letter carry forward or neither one does. Have one but not the other carry forward seems nonsensical. ++PLS ________________________________ From: tz-request(a)elsie.nci.nih.gov [mailto:tz-request@elsie.nci.nih.gov] On Behalf Of Mark Davis Sent: Wednesday, September 27, 2006 4:14 PM To: tz(a)lecserver.nci.nih.gov Cc: tz(a)lecserver.nci.nih.gov Subject: Re: Question on abbreviations My reading of the specification (zic.8.txt) was that the first rule mentioned was operative during the interval from 1942 to "only", that is, during 1942 alone. This was by my reading of: TO Gives the final year in which the rule applies. In addition to minimum and maximum (as above), the word only (or an abbreviation) may be used to repeat the value of the FROM field. While it was explained to me what the actual code does, I don't think this is reflected in the above text -- or at least, not at all clearly. According to this text, if I saw the following: Rule US 1942 1944 - Feb 9 2:00 1:00 W # War The rule should not apply in 1945. So I request that the text be fixed, because the rule clearly, according to the explanations given on this thread, applies *afterwards* (and the circumstances in which it applies need to be clearly specified. Is it until the next Rule that has an SAVE value with the same SAVE value as this Rule? Until the next Rule that has a SAVE value?... mark On 9/27/06, Paul Schauble <Paul.Schauble(a)ticketmaster.com> wrote: So in this case: Rule US 1942 only - Feb 9 2:00 1:00 W # War Rule US 1945 only - Aug 14 23:00u 1:00 P # Peace Why is %s undefined in 1943? This was the question that started the thread. If the time setting carries forward, surely the letter should also. ++PLS -----Original Message----- From: tz-request(a)elsie.nci.nih.gov [mailto:tz-request@elsie.nci.nih.gov] On Behalf Of Ken Pizzini Sent: Wednesday, September 27, 2006 3:14 PM To: tz(a)lecserver.nci.nih.gov Subject: Re: Question on abbreviations On Wed, Sep 27, 2006 at 02:37:58PM -0700, Mark Davis wrote: > I share your confusion. If Paul (Eggert's) description is right, then I have > to ignore the TO field in some circumstances which are entirely unclear to > me. I would much rather see the TO field corrected. That is, if TO=1942 is > ignored, and 1945 is the real date, then the line should be corrected to > TO=1945. The key to understanding is that the rules describe a list of *transitions*. After a transition, the described effect on zone offset and abbreviation *remain* in effect until the next transition. The "TO" part of a rule is used to enable a shorthand for a _recurring_ transition, such as "first Tuesday of February", for all years within the range. If "to" is "only", then the *transition* being documented is a singleton, but the transitioned-into offset/abbreviation remains in effect until the _next_ transition, no matter how far in the future. > There are other failures in the parsing. My error messages are: ... > I looked into why this is happening, and found: > > Zone Europe/Amsterdam 0:19:32 - LMT 1835 > 0:19:32 Neth %s 1937 Jul 1 > But the first LETTER/S defined by Neth is in 1916, so during the range from > 1835 to 1916 this is undefined. If the LETTER/S are magically also defined > *before* the first FROM, that should be described in the specification. Yes, this is a failure of the documentation. If a Zone refers to a time within a Rule that is before the first transition mentioned for that rule, then the _oldest_standard_time_ "Letter/s" is used. In this case, AMT. > BTW, the documentation was a first a bit confusing to me, since it says that > fields are delimited by spaces, and lists a single Zone UNTIL field. > However, if you look carefully at the documentation, there are really 4 > fields: > > UNTIL_YEAR UNTIL_IN UNTIL_ON UNTIL_AT > > which are optional [but only in "truncation" from the end: that is, it > corresponds to the (Perl) regex (UNTIL_YEAR (UNTIL_IN (UNTIL_ON > (UNTIL_AT)?)?)?)?]. > > I'm not the only one to have initially made this mistake: the proposed XML > format for the TZ database makes the same mistake. Confusing: granted. Whether "Until" is one or multiple fields is a matter of interpretation. The _traditional_ understanding is that it is a *single* "timestamp field" which may happen to have spaces within it. BTW the subfields aren't "YEAR IN ON AT", but "YEAR MONTH DAY TIME". In this regard, a recent addition to the tzcode tarball is zoneinfo2tdf.pl, which translates the more free-with-spaces zone tzdata into a form which strictly uses a single tab between fields. This may make life easier for some by simplifying their parser's requirements. (Or not.) --Ken Pizzini

1 0

Question on abbreviations
by Mark Davis Sept. 27, 2006

Sept. 27, 2006

I'm getting 3 strange cases when parsing the tz database, for the following cases: - Didn't find %s values for M%sT under America/Phoenix:US for 1944 to 1944 - Didn't find %s values for C%sT under Asia/Macau:PRC for 1999 to +INF - Didn't find %s values for CE%sT under Europe/Warsaw:Poland for 1922 to 1940 Let's take the first case. In the file northamerica, we have the following lines. Zone America/Phoenix -7:28:18 - LMT 1883 Nov 18 11:31:42 -7:00 US M%sT 1944 Jan 1 00:01 -7:00 - MST 1944 Apr 1 00:01 -7:00 US M%sT 1944 Oct 1 00:01 -7:00 - MST 1967 -7:00 US M%sT 1968 Mar 21 -7:00 - MST Now, according to my reading of zic.8.txt, to see what the values for %s are, we look at the rules that are in effect for the period in question. So for the 2nd occurence of M%sT, we are concerned with the time between 1944 Apr 1 00:01 UNTIL 1944 Oct 1 00:01, according to the US rules. In the Rule documentation, we have: LETTER/S Gives the "variable part" (for example, the "S" or "D" in "EST" or "EDT") of time zone abbreviations to be used when this rule is in effect. If this field is -, the variable part is null. So to get the value, we should look at the US rule that is in effect during 1944. Here are the US rules: # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S Rule US 1918 1919 - Mar lastSun 2:00 1:00 D Rule US 1918 1919 - Oct lastSun 2:00 0 S Rule US 1942 only - Feb 9 2:00 1:00 W # War Rule US 1945 only - Aug 14 23:00u 1:00 P # Peace Rule US 1945 only - Sep 30 2:00 0 S Rule US 1967 2006 - Oct lastSun 2:00 0 S Rule US 1967 1973 - Apr lastSun 2:00 1:00 D Rule US 1974 only - Jan 6 2:00 1:00 D Rule US 1975 only - Feb 23 2:00 1:00 D Rule US 1976 1986 - Apr lastSun 2:00 1:00 D Rule US 1987 2006 - Apr Sun>=1 2:00 1:00 D Rule US 2007 max - Mar Sun>=8 2:00 1:00 D Rule US 2007 max - Nov Sun>=1 2:00 0 S None of them are operant during 1944, so I don't find any value for M%sT. Am I misreading something? Mark On 9/26/06, Paul Eggert <eggert(a)cs.ucla.edu> wrote: > > Steffen Thorsen <straen(a)thorsen.priv.no> writes: > > > Daylight Saving Time ended Friday for "Rule Palestine" > > Thanks for the heads-up. Here is a proposed patch, which incorporates > the Palestine change along with the other changes already proposed to > this list recently. > > =================================================================== > RCS file: RCS/africa,v > retrieving revision 2006.12 > retrieving revision 2006.12.0.1 > diff -pu -r2006.12 -r2006.12.0.1 > --- africa 2006/09/18 16:58:11 2006.12 > +++ africa 2006/09/20 19:35:29 2006.12.0.1 > @@ -212,35 +212,13 @@ Rule Egypt 1990 1994 - > May 1 1:00 1:00 > # Go with IATA starting in 1995, except correct 1995 entry from 09-30 to > 09-29. > Rule Egypt 1995 max - Apr lastFri 0:00s 1:00 S > Rule Egypt 1995 2005 - Sep lastThu 23:00s 0 - > -# From Hammad Hassan (2006-09-13), quoting The Egyptian Gazette > (2006-09-10), > -# issue no. 41,083, page 1, column 1: > -# Egypt will switch back to the winter time on the eve of the first day > of > -# the Muslim holy month of Ramadan, expected to start this year on Sept. > 24.... > -# "Clocks will be turned back starting from the night on which Darul Ifta > ... > -# announces sighting the crescent of the month of Ramadan,..." Magdi > Radi, > -# the Cabinet spokesman, said yesterday. > -# From Hammad Hassan (2006-09-17): > -# when we reach 1:00AM at Sep 25 the clocks will be turned back to > 12:00AM. > -# I think also this change will be this year and may be the next couple > of > -# years only. (They just want to exclude Ramadan from the summer time; > if > -# so, the change will be among 3 years only if my calculations are > correct). > -# From Paul Eggert (2006-09-17): > -# For now, assume a similar rule will be followed in 2006/2008, and that > -# Ramadan will start as predicted by GNU Emacs 21.4. Here's the code > used > -# to generate the 2006/2008 lines: > -# (let ((year 1427)) > -# (while (< year (+ 1427 3)) > -# (let ((date (calendar-gregorian-from-absolute > -# (calendar-absolute-from-islamic (list 9 2 year))))) > -# (insert (format "Rule\tEgypt\t%d\tonly\t-\t%s\t%2d\t 1:00\t0\t-\n" > -# (extract-calendar-year date) > -# (calendar-month-name (extract-calendar-month date) > 3) > -# (extract-calendar-day date)))) > -# (setq year (1+ year))))) > -Rule Egypt 2006 only - Sep 25 1:00 0 - > -Rule Egypt 2007 only - Sep 14 1:00 0 - > -Rule Egypt 2008 only - Sep 3 1:00 0 - > -Rule Egypt 2009 max - Sep lastThu 23:00s 0 - > +# From Steffen Thorsen (2006-09-19): > +# The Egyptian Gazette, issue 41,090 (2006-09-18), page 1, reports: > +# Egypt will turn back clocks by one hour at the midnight of Thursday > +# after observing the daylight saving time since May. > +# http://news.gom.com.eg/gazette/pdf/2006/09/18/01.pdf > +Rule Egypt 2006 only - Sep 21 23:00s 0 - > +Rule Egypt 2007 max - Sep lastThu 23:00s 0 - > > # Zone NAME GMTOFF RULES FORMAT [UNTIL] > Zone Africa/Cairo 2:05:00 - LMT 1900 Oct > =================================================================== > RCS file: RCS/asia,v > retrieving revision 2006.11 > retrieving revision 2006.11.0.3 > diff -pu -r2006.11 -r2006.11.0.3 > --- asia 2006/08/28 16:18:48 2006.11 > +++ asia 2006/09/26 17:55:21 2006.11.0.3 > @@ -1476,6 +1476,15 @@ Zone Asia/Karachi 4:28:12 - LMT > 1907 > # Gaza changed as well, but presumed Gaza to follow the same rules as > # the West Bank. > > +# From Steffen Thorsen (2006-09-26): > +# according to the Palestine News Network (2006-09-19): > +# > http://english.pnn.ps/index.php?option=com_content&task=view&id=596&Itemid=5 > +# > The Council of Ministers announced that this year its winter schedule > +# > will begin early, as of midnight Thursday. It is also time to turn > +# > back the clocks for winter. Friday will begin an hour late this > week. > +# I guess it is likely that next year's date will be moved as well, > +# because of the Ramadan. > + > # The rules for Egypt are stolen from the `africa' file. > # Rule > NAME FROM TO TYPE IN ON AT SAVE LETTER/S > Rule EgyptAsia 1957 only - May 10 0:00 1:00 S > @@ -1488,8 +1497,10 @@ Rule EgyptAsia 1966 only - > Oct 1 3:00 0 > Rule Palestine 1999 2005 - Apr Fri>=15 0:00 1:00 S > Rule Palestine 1999 2003 - Oct Fri>=15 0:00 0 - > Rule Palestine 2004 only - Oct 1 1:00 0 - > -Rule Palestine 2005 max - Oct 4 2:00 0 - > +Rule Palestine 2005 only - Oct 4 2:00 0 - > Rule Palestine 2006 max - Apr 1 0:00 1:00 S > +Rule Palestine 2006 only - Sep 22 0:00 0 - > +Rule Palestine 2007 max - Oct Fri>=15 0:00 0 - > > # Zone NAME GMTOFF RULES FORMAT [UNTIL] > Zone Asia/Gaza 2:17:52 - LMT 1900 Oct > @@ -1668,11 +1679,18 @@ Rule Syria 1993 only - Sep > 25 0:00 0 - > # IATA SSIM (1998-02) says 1998-04-02; > # (1998-09) says 1999-03-29 and 1999-09-29; (1999-02) says 1999-04-02, > # 2000-04-02, and 2001-04-02; (1999-09) says 2000-03-31 and 2001-03-31; > -# ignore all these claims and go with Shanks & Pottenger. > +# (2006) says 2006-03-31 and 2006-09-22; > +# for now ignore all these claims and go with Shanks & Pottenger, > +# except for the 2006-09-22 claim (which seems right for Ramadan). > Rule Syria 1994 1996 - Apr 1 0:00 1:00 S > -Rule Syria 1994 max - Oct 1 0:00 0 - > +Rule Syria 1994 2005 - Oct 1 0:00 0 - > Rule Syria 1997 1998 - Mar lastMon 0:00 1:00 S > Rule Syria 1999 max - Apr 1 0:00 1:00 S > +# From Stephen Colebourne (2006-09-18): > +# According to IATA data, Syria will change DST on 21st September [21:00 > UTC] > +# this year [only].... This is probably related to Ramadan, like Egypt. > +Rule Syria 2006 only - Sep 22 0:00 0 - > +Rule Syria 2007 max - Oct 1 0:00 0 - > # Zone NAME GMTOFF RULES FORMAT [UNTIL] > Zone Asia/Damascus 2:25:12 - LMT 1920 # Dimashq > 2:00 Syria EE%sT > =================================================================== > RCS file: RCS/southamerica,v > retrieving revision 2006.3 > retrieving revision 2006.3.0.2 > diff -pu -r2006.3 -r2006.3.0.2 > --- southamerica 2006/04/03 14:07:15 2006.3 > +++ southamerica 2006/09/20 19:35:02 2006.3.0.2 > @@ -1064,6 +1064,10 @@ Rule Uruguay 2005 only - Mar > 27 2:00 0 > # 02:00 local time, official time in Uruguay will be at GMT -2. > Rule Uruguay 2005 only - Oct 9 2:00 1:00 S > Rule Uruguay 2006 only - Mar 12 2:00 0 - > +# From Jesper Norgaard Welen (2006-09-06): > +# > http://www.presidencia.gub.uy/_web/decretos/2006/09/CM%20210_08%2006%202006… > +Rule Uruguay 2006 max - Oct Sun>=1 2:00 1:00 S > +Rule Uruguay 2007 max - Mar Sun>=8 2:00 0 - > # Zone NAME GMTOFF RULES FORMAT [UNTIL] > Zone America/Montevideo -3:44:44 - LMT 1898 Jun 28 > -3:44:44 - MMT 1920 May 1 # > Montevideo MT >

3 4

DST ended early in Palestine
by Steffen Thorsen Sept. 26, 2006

Sept. 26, 2006

Daylight Saving Time ended Friday for "Rule Palestine" according to the Palestine News Network on 2006-09-19: http://english.pnn.ps/index.php?option=com_content&task=view&id=596&Itemid=5 > The Council of Ministers announced that this year its winter schedule > will begin early, as of midnight Thursday. It is also time to turn > back the clocks for winter. Friday will begin an hour late this week. I guess it is likely that next year's date will be moved as well, because of the Ramadan. Best regards, Steffen Thorsen

2 1

FW: update zonerules for Brazil
by Olson, Arthur David (NIH/NCI) [E] Sept. 26, 2006

Sept. 26, 2006

Reinald Verheij is not on the time zone mailing list; direct replies appropriately. --ado ________________________________ From: Reinald Verheij [mailto:reinald.verheij@infor.com] Sent: Tuesday, September 26, 2006 4:42 AM To: tz(a)lecserver.nci.nih.gov Cc: Roelco Rens Subject: update zonerules for Brazil Hi, I understood that Brazil will enter DST at November 5 0:00 2006. This is because of elections (just like 2002). The timezone rules say "first Sunday on or after october 15". So there is a mismatch. Is there an update available for the zonerules for Brazil? I did not find it on the ftp site of elsie.nci.nih.gov. Reinald Verheij Infor

2 1