- tz - lists.iana.org

FW: Time Zone Localizations
by Olson, Arthur David (NIH/NCI) June 15, 2004

June 15, 2004

Masayoshi Okutsu has been added to the time zone mailing list; this is a message sent before Masayoshi was added. --ado -----Original Message----- From: Masayoshi Okutsu [mailto:Masayoshi.Okutsu@Sun.COM] Sent: Friday, June 11, 2004 8:44 PM To: Mark Davis Cc: tz(a)lecserver.nci.nih.gov Subject: Re: Time Zone Localizations Probably you have misunderstood my first question... Many zones have changed their time zones in their history. It's not a valid assumption that a single zone ID represents a single time zone. It may be confusing to say "zone changes time zones". Let me give you an example. Here's the history of Asia/Singapore. # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Singapore 6:55:25 - LMT 1901 Jan 1 6:55:25 - SMT 1905 Jun 1 # Singapore M.T. 7:00 - MALT 1933 Jan 1 # Malaya Time 7:00 0:20 MALST 1936 Jan 1 7:20 - MALT 1941 Sep 1 7:30 - MALT 1942 Feb 16 9:00 - JST 1945 Sep 12 7:30 - MALT 1965 Aug 9 # independence 7:30 - SGT 1982 Jan 1 # Singapore Time 8:00 - SGT During 1942-02-16 until 1945-09-12, Asia/Singapore's time zone was Japan Standard Time (GMT+09:00). (Sorry if this isn't a good example...) The LDML spec didn't look like supporting all historical time zones within a single zone. So what I'd like to see is something organized like: <zone type="Asia/Singapore" > <zoneNameSet format="SGT"> <long> <generic>Singapore Time</generic> <standard>Singapore Time</standard> <daylight>Singapore Time</daylight> </long> <short> <generic>SGT</generic> <standard>SGT</standard> <daylight>SGT</daylight> </short> </zoneNameSet> ... <zoneNameSet format="LMT"> <long> <generic>Local Mean Time</generic> ... <short> <generic>LMT</generic> ... </zoneNameSet> <exemplarCity>Singapore</exemplarCity> </zone> Obviously use of this structure involves redundant names. Probably it should have all name sets which can be referred to by <zone>. I got several bug reports on Java time zone support because it supports all historical changes since 1.4. Some customers were just confused with historically correct local time. Some of them could have been avoided if Java was capable of giving historically correct time zone names. Hope my question is now clearer. Thanks, Masayoshi Mark Davis wrote: >I don't know where you are getting that. They are *not* user-defined >IDs. The text in http://www.unicode.org/reports/tr35/ defines the IDs >as matching the IDs in ftp://elsie.nci.nih.gov/pub/. See also >http://www.unicode.org/cldr/data_formats.html#Display_Names also. > >Mark >__________________________________ >http://www.macchiato.com >► शिष्यादिच्छेत्पराजयम् ◄ > >----- Original Message ----- >From: "Masayoshi Okutsu" <Masayoshi.Okutsu(a)Sun.COM> >To: "Mark Davis" <mark.davis(a)jtcsv.com> >Cc: <tz(a)lecserver.nci.nih.gov> >Sent: Fri, 2004 Jun 11 08:41 >Subject: Re: Time Zone Localizations > > >Mark Davis wrote: > > > >>Actually, this is directly related, since LDML is the format used for CLDR. >>However, the comment is based on a misunderstanding: LDML currently >>does allow for translation of *all* of the timezone IDs, modern and historical. >> >> >> >> >I guess you don't translate timezone IDs... Anyway, do you mean that >LDML allows users to define DTD? (Sorry if this is not a correct way to >talk about XML...) So the syntax of <zone> is really user-defined? > >Thanks, >Masayoshi > > > >>The problems we are trying to address with this proposal are that the >>sheer volume of translations is difficult to manage, *and* many >>languages just don't have corresponding terms. And we didn't give >>guidance before as to which IDs were the most important to translate, >>so the translations that are in CLDR were not done in any kind of priority order. >> >>Mark >>__________________________________ >>http://www.macchiato.com >>► शिष्यादिच्छेत्पराजयम् ◄ >> >>----- Original Message ----- >>From: "Masayoshi Okutsu" <Masayoshi.Okutsu(a)Sun.COM> >>To: "Mark Davis" <mark.davis(a)jtcsv.com> >>Cc: <tz(a)lecserver.nci.nih.gov> >>Sent: Fri, 2004 Jun 11 06:43 >>Subject: Re: Time Zone Localizations >> >> >>This is a bit off from the proposal, but related to time zone localizations. >> >>It appears that the Locale Data Markup Language spec for >><timeZoneNames> >>(http://www.unicode.org/reports/tr35/#%3CtimeZoneNames%3E) assumes >>that a time zone has a single set of long and short names, which >>assumption is not valid if a system supports historical time zone changes. >>Actually, the time zone support in Java has this problem because it >>supports historical changes since 1.4 and always display the "latest" >>time zone names. I planned to fix it in J2SE 1.5 (a.k.a. Tiger), but I >>couldn't due to another commitment. >> >>Is it possible for CLDR to make corrections to the <timeZoneNames> >>spec so that it can represent all historical name changes? >> >>Thanks, >>-- >>Masayoshi Okutsu >>Java Internationalization >>Sun Microsystems (K.K.) >> >>Mark Davis wrote: >> >> >> >> >> >>>The common locale data repository project (CLDR) hosted by the >>>Unicode consortium (www.unicode.org/cldr/) provides for translations >>>of time zone IDs, based on the public domain time zone database at ftp://elsie.nci.nih.gov/pub/. >>> >>> >>> >>> >>A >> >> >> >> >>>number of issues have come up concerning those translations, and we >>>have put together a proposal for changing the way that is done. The >>>goal would be to >>> >>> >>> >>> >>make >> >> >> >> >>>changes in CLDR 1.1, which would be released around mid-October of this year. >>>The current version of the proposal is at: >>> >>>http://oss.software.ibm.com/cvs/icu/~checkout~/icuhtml/design/formatt >>>ing/time_ >>> >>> >z > > >>> >>> >>one_localization.html >> >> >> >> >>>I'd very much appreciate any feedback on the proposal. >>> >>>Mark >>>__________________________________ >>>http://www.macchiato.com >>>► शिष्यादिच्छेत्पराजयम् ◄ >>> >>> >>> >>> >>> >>> >>> >>> >> >> >> >> >> > > > > >

1 0

FW: Time Zone Localizations
by Olson, Arthur David (NIH/NCI) June 15, 2004

June 15, 2004

Masayoshi Okutsu has been added to the time zone mailing list; this is a message sent before Masayoshi was added. --ado -----Original Message----- From: Masayoshi Okutsu [mailto:Masayoshi.Okutsu@Sun.COM] Sent: Friday, June 11, 2004 11:42 AM To: Mark Davis Cc: tz(a)lecserver.nci.nih.gov Subject: Re: Time Zone Localizations Mark Davis wrote: >Actually, this is directly related, since LDML is the format used for CLDR. >However, the comment is based on a misunderstanding: LDML currently >does allow for translation of *all* of the timezone IDs, modern and historical. > > I guess you don't translate timezone IDs... Anyway, do you mean that LDML allows users to define DTD? (Sorry if this is not a correct way to talk about XML...) So the syntax of <zone> is really user-defined? Thanks, Masayoshi >The problems we are trying to address with this proposal are that the >sheer volume of translations is difficult to manage, *and* many >languages just don't have corresponding terms. And we didn't give >guidance before as to which IDs were the most important to translate, >so the translations that are in CLDR were not done in any kind of priority order. > >Mark >__________________________________ >http://www.macchiato.com >► शिष्यादिच्छेत्पराजयम् ◄ > >----- Original Message ----- >From: "Masayoshi Okutsu" <Masayoshi.Okutsu(a)Sun.COM> >To: "Mark Davis" <mark.davis(a)jtcsv.com> >Cc: <tz(a)lecserver.nci.nih.gov> >Sent: Fri, 2004 Jun 11 06:43 >Subject: Re: Time Zone Localizations > > >This is a bit off from the proposal, but related to time zone localizations. > >It appears that the Locale Data Markup Language spec for ><timeZoneNames> >(http://www.unicode.org/reports/tr35/#%3CtimeZoneNames%3E) assumes that >a time zone has a single set of long and short names, which assumption >is not valid if a system supports historical time zone changes. >Actually, the time zone support in Java has this problem because it >supports historical changes since 1.4 and always display the "latest" >time zone names. I planned to fix it in J2SE 1.5 (a.k.a. Tiger), but I >couldn't due to another commitment. > >Is it possible for CLDR to make corrections to the <timeZoneNames> spec >so that it can represent all historical name changes? > >Thanks, >-- >Masayoshi Okutsu >Java Internationalization >Sun Microsystems (K.K.) > >Mark Davis wrote: > > > >>The common locale data repository project (CLDR) hosted by the Unicode >>consortium (www.unicode.org/cldr/) provides for translations of time >>zone IDs, based on the public domain time zone database at ftp://elsie.nci.nih.gov/pub/. >> >> >A > > >>number of issues have come up concerning those translations, and we >>have put together a proposal for changing the way that is done. The >>goal would be to >> >> >make > > >>changes in CLDR 1.1, which would be released around mid-October of this year. >>The current version of the proposal is at: >> >>http://oss.software.ibm.com/cvs/icu/~checkout~/icuhtml/design/formatti >>ng/time_z >> >> >one_localization.html > > >>I'd very much appreciate any feedback on the proposal. >> >>Mark >>__________________________________ >>http://www.macchiato.com >>► शिष्यादिच्छेत्पराजयम् ◄ >> >> >> >> >> >> > > > > >

1 0

FW: Time Zone Localizations
by Olson, Arthur David (NIH/NCI) June 15, 2004

June 15, 2004

Masayoshi Okutsu has been added to the time zone mailing list; this is a message sent before Masayoshi was added. --ado -----Original Message----- From: Masayoshi Okutsu [mailto:Masayoshi.Okutsu@Sun.COM] Sent: Friday, June 11, 2004 10:50 AM To: Chuck Soper Cc: tz(a)lecserver.nci.nih.gov Subject: Re: Time Zone Localizations Chuck Soper wrote: > Are these tables informational or vital to the process? For example, > will the Aliases table be used to "Canonicalize the Olson ID" (step 1 > of the Fallback procedure)? If so, then the table should be based on > the current time zone data files instead of "current Java data". This > could turn into a serious maintenance issue. Ideally, I think that a > script could be run on the time zone data files to generate a new > aliases table each time the time zone data files are updated > (currently tzdata2004a). I agree. And it's unclear what the "current Java data" is. *My* current Java data is tzdata2004a, which is very unlikely to be shipped with 1.5... > Where did AET (line 2, Aliases table) for Australia/Sydney come from? > I can't find any reference to it in tzdata2004a. I guess it came from JDK1.1 compatibility names. Someone (not me!) invented 3-letter time zone IDs in JDK 1.1, which failed to support more time zones. Java uses the Olson zone IDs since 1.2. But we still have the JDK 1.1 compatibility names as far as they don't conflict with any Olson zone IDs. > ### Equivalent Modern Zones > My first reaction whenever I see a significant effort to simplify > something for the user is to think that it could lead to problems. I tend to agree with you. I think we should find out another way to reduce the number of localized time zone name strings. > How did you determine that "A lot of people just don't care about > historic differences"? Do most people use time zones merely to keep > track of the current time or current differences between another time > zone? How else do users use time zones? Right. And how can we define "current" for time zones which change their offsets some time in the future, like America/Mendoza in tzdata2004a? The day after tomorrow...? :-) Masayoshi

1 0

FW: Time Zone Localizations
by Olson, Arthur David (NIH/NCI) June 15, 2004

June 15, 2004

Masayoshi Okutsu has been added to the time zone mailing list; this is a message sent before Masayoshi was added. --ado -----Original Message----- From: Masayoshi Okutsu [mailto:Masayoshi.Okutsu@Sun.COM] Sent: Friday, June 11, 2004 9:43 AM To: Mark Davis Cc: tz(a)lecserver.nci.nih.gov Subject: Re: Time Zone Localizations This is a bit off from the proposal, but related to time zone localizations. It appears that the Locale Data Markup Language spec for <timeZoneNames> (http://www.unicode.org/reports/tr35/#%3CtimeZoneNames%3E) assumes that a time zone has a single set of long and short names, which assumption is not valid if a system supports historical time zone changes. Actually, the time zone support in Java has this problem because it supports historical changes since 1.4 and always display the "latest" time zone names. I planned to fix it in J2SE 1.5 (a.k.a. Tiger), but I couldn't due to another commitment. Is it possible for CLDR to make corrections to the <timeZoneNames> spec so that it can represent all historical name changes? Thanks, -- Masayoshi Okutsu Java Internationalization Sun Microsystems (K.K.) Mark Davis wrote: >The common locale data repository project (CLDR) hosted by the Unicode >consortium (www.unicode.org/cldr/) provides for translations of time >zone IDs, based on the public domain time zone database at >ftp://elsie.nci.nih.gov/pub/. A number of issues have come up >concerning those translations, and we have put together a proposal for >changing the way that is done. The goal would be to make changes in CLDR 1.1, which would be released around mid-October of this year. >The current version of the proposal is at: > >http://oss.software.ibm.com/cvs/icu/~checkout~/icuhtml/design/formattin >g/time_zone_localization.html > >I'd very much appreciate any feedback on the proposal. > >Mark >__________________________________ >http://www.macchiato.com >► शिष्यादिच्छेत्पराजयम् ◄ > > > >

1 0

IERS Message No. 58: IERS Conventions Center: New discussion foru m and web site.
by IERS Central Bureau June 15, 2004

June 15, 2004

*************************************************************************** IERS Message No. 58 June 15, 2004 *************************************************************************** IERS Conventions Center: New discussion forum and web site. The IERS Conventions center has developed a Discussion Forum and a new web and ftp site for the IERS Conventions, on a server at the BIPM. 1) The user discussion forum http://tai.bipm.org/iers/forum/ is open for users to offer their comments, criticism, and suggestions regarding the update of the IERS Conventions. It is organized in themes following the present structure of the IERS Conventions (2003). To post a contribution it is necessary to be registered. Registration is a very simple procedure. It is only necessary to provide a login_name and password, and a valid e-mail address. It is recommended that the login_name be representative of your real name because the login_name is used to identify the authors of contributions. Reading the contributions is open and anonymous. A number of contributions have been posted in advance of the public opening by Jim Ray in order to stimulate discussions. Responses and new contributions are welcome. 2) The new ftp site ftp://tai.bipm.org/iers/ has two directories: * ftp://tai.bipm.org/iers/conv2003/ is a mirror of the usual ftp site ftp://maia.usno.navy.mil/conv2003/ containing all files of the Conventions (2003) (Note that as of June 4, 2004 the pdf files of the chapters have not been updated on the USNO site). * ftp://tai.bipm.org/iers/convupdt/ is used to store material relative to future updates of the IERS Conventions. 3) The new web site http://tai.bipm.org/iers/ has two main pages: * http://tai.bipm.org/iers/conv2003/conv2003.html which ultimately points to the material of the Conventions (2003). * http://tai.bipm.org/iers/convupdt/convupdt.html which is used for Conventions updates. It is planned to save all the information on successive updates incrementing in the pages of each chapter. See an example version in http://tai.bipm.org/iers/convupdt/convupdt_c5.html Gérard Petit and Dennis D. McCarthy IERS Conventions Center *************************************************************************** IERS Messages are edited and distributed by the IERS Central Bureau. To subscribe or unsubscribe, please write to <central_bureau(a)iers.org>. Archives: http://www.iers.org/iers/publications/messages/ ***************************************************************************

1 0

RE: zdump -v crashes with 64-bit time_t
by Olson, Arthur David (NIH/NCI) June 15, 2004

June 15, 2004

Here's a proposed change to zdump to avoid crashes when NULL is returned by asctime. --ado ------- zdump.c ------- *** /tmp/geta13866 Mon Jun 14 11:47:06 2004 --- /tmp/getb13866 Mon Jun 14 11:47:06 2004 *************** *** 1,4 **** ! static char elsieid[] = "@(#)zdump.c 7.31"; /* ** This code has been made independent of the rest of the time --- 1,4 ---- ! static char elsieid[] = "@(#)zdump.c 7.32"; /* ** This code has been made independent of the rest of the time *************** *** 334,339 **** --- 334,346 ---- return result; } + static char * + nonnull(s) + const char * const s; + { + return (s == NULL) ? "NULL" : s; + } + static void show(zone, t, v) char * zone; *************** *** 344,352 **** (void) printf("%-*s ", (int) longest, zone); if (v) ! (void) printf("%.24s UTC = ", asctime(gmtime(&t))); tmp = localtime(&t); ! (void) printf("%.24s", asctime(tmp)); if (*abbr(tmp) != '\0') (void) printf(" %s", abbr(tmp)); if (v) { --- 351,359 ---- (void) printf("%-*s ", (int) longest, zone); if (v) ! (void) printf("%.24s UTC = ", nonnull(asctime(gmtime(&t)))); tmp = localtime(&t); ! (void) printf("%.24s", nonnull(asctime(tmp))); if (*abbr(tmp) != '\0') (void) printf(" %s", abbr(tmp)); if (v) {

3 5

RE: Time Zone Localizations
by Olson, Arthur David (NIH/NCI) June 14, 2004

June 14, 2004

Note, though, that there is foreseeable instability if I retire in 2012 as planned. (More on this when we reach 2007.) --ado -----Original Message----- From: Paul Eggert [mailto:eggert@CS.UCLA.EDU] Sent: Friday, June 11, 2004 9:56 PM To: Mark Davis Cc: tz(a)lecserver.nci.nih.gov Subject: Re: Time Zone Localizations "Mark Davis" <mark.davis(a)jtcsv.com> writes: > ftp://elsie.nci.nih.gov/pub/ > > Is there a stable link to a document that we could cite as the > specification for the IDs, instead of just pointing to an FTP site? When you ask for a "specification for the IDs", do you mean "which TZIDs are in the Olson database?" or "what syntax is allowed for the TZIDs?"? Either way, I'd say that the FTP site is the stable reference. According to my records that location dates back to April 25, 1992, so it's one of the most stable links on the planet.

3 2

FW: zdump -v crashes with 64-bit time_t
by Olson, Arthur David (NIH/NCI) June 14, 2004

June 14, 2004

Andreas Schwab is not on the time zone mailing list; direct replies appropriately. --ado -----Original Message----- From: Andreas Schwab [mailto:schwab@suse.de] Sent: Wednesday, June 09, 2004 11:11 AM To: tz(a)elsie.nci.nih.gov Subject: zdump -v crashes with 64-bit time_t zdump does not cope with gmtime/localtime returning NULL, which can easily happen on systems having a 64-bit time_t when zdump tries to display the lowest/highest time_t value. GNU libc's implementation of gmtime/localtime returns NULL when tm_year would overflow. Also cf. the recent discussion on comp.std.c about asctime/ctime potentially writing beyond the internal buffer when the year is outside the range [-999, 9999] (although GNU libc's asctime does not have this particular problem). Andreas. -- Andreas Schwab, SuSE Labs, schwab(a)suse.de SuSE Linux AG, Maxfeldstraße 5, 90409 Nürnberg, Germany Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different."

1 0

proposed tz patch for Argentina, Aaland Islands, etc.
by Paul Eggert June 14, 2004

June 14, 2004

Here's a proposed patch to the tz database. It changes the Argentina data to reflect the June 1 time zone changes reported by Mariano Absatz. This patch also adds support for the new country code AX. To support these things, this patch adds the following Zone or Link lines: America/Rio_Gallegos America/Tucuman Europe/Mariehamn This patch also removes a few broken links from tz-link.htm, and adds a link to the new CLDR localization effort. =================================================================== RCS file: RCS/europe,v retrieving revision 2004.1 retrieving revision 2004.1.0.1 diff -pu -r2004.1 -r2004.1.0.1 --- europe 2004/05/27 16:00:30 2004.1 +++ europe 2004/06/14 07:46:16 2004.1.0.1 @@ -921,6 +921,10 @@ Zone Europe/Helsinki 1:39:52 - LMT 1878 2:00 Finland EE%sT 1981 Mar 29 2:00 2:00 EU EE%sT +# Aaland Is +Link Europe/Helsinki Europe/Mariehamn + + # France # From Ciro Discepolo (2000-12-20): =================================================================== RCS file: RCS/southamerica,v retrieving revision 2004.1 retrieving revision 2004.1.0.1 diff -pu -r2004.1 -r2004.1.0.1 --- southamerica 2004/05/27 16:00:30 2004.1 +++ southamerica 2004/06/14 07:46:16 2004.1.0.1 @@ -155,6 +155,19 @@ Rule Arg 2000 only - Mar Sun>=1 0:00 0 - # </a> says that standard time in Argentina from 1894-10-31 # to 1920-05-01 was -4:16:48.25. Go with this more-precise value # over Shanks. +# +# From Mariano Absatz (2004-06-05): +# These media articles from a major newspaper mostly cover the current state: +# http://www.lanacion.com.ar/04/05/27/de_604825.asp +# http://www.lanacion.com.ar/04/05/28/de_605203.asp +# +# The following eight (8) provinces pulled clocks back to UTC-04:00 at +# midnight Monday May 31st. (that is, the night between 05/31 and 06/01). +# Apparently, all nine provinces would go back to UTC-03:00 at the same +# time in October 17th. +# +# Catamarca, Chubut, La Rioja, San Juan, San Luis, Santa Cruz, +# Tierra del Fuego, Tucum # Unless otherwise specified, data are from Shanks through 1992, from # the IATA otherwise. As noted below, Shanks says that @@ -163,8 +176,7 @@ Rule Arg 2000 only - Mar Sun>=1 0:00 0 - # # Zone NAME GMTOFF RULES FORMAT [UNTIL] # -# Buenos Aires (BA), Capital Federal (CF), Santa Cruz (SC), -# Tierra del Fuego, Antartida e Islas del Atlantico Sur (TF) +# Buenos Aires (BA), Capital Federal (CF), Zone America/Buenos_Aires -3:53:48 - LMT 1894 Oct 31 -4:16:48 - CMT 1920 May # Cordoba Mean Time -4:00 - ART 1930 Dec @@ -174,24 +186,37 @@ Zone America/Buenos_Aires -3:53:48 - LMT -3:00 - ART # # Santa Fe (SF), Entre Rios (ER), Corrientes (CN), Misiones (MN), Chaco (CC), -# Formosa (FM), Salta (SA), Tucuman (TM), Santiago del Estero (SE), -# Cordoba (CB), La Rioja (LR), San Juan (SJ), San Luis (SL), La Pampa (LP), -# Neuquen (NQ), Rio Negro (RN), Chubut (CH) +# Formosa (FM), Salta (SA), Santiago del Estero (SE), Cordoba (CB), +# La Pampa (LP), Neuquen (NQ), Rio Negro (RN) # # Shanks also makes the following claims, which we haven't verified: # - Formosa switched to -3:00 on 1991-01-07. -# - La Rioja and San Juan switched to -4:00 on 1991-03-01 -# and then to -3:00 on 1991-05-07. # - Misiones switched to -3:00 on 1990-12-29. # - Chaco switched to -3:00 on 1991-01-04. -# - San Luis switched to -4:00 on 1990-03-14, then to -3:00 on 1990-10-15, -# then to -4:00 on 1991-03-01, then to -3:00 on 1991-06-01. # - Santiago del Estero switched to -4:00 on 1991-04-01, # then to -3:00 on 1991-04-26. +# +Zone America/Cordoba -4:16:48 - LMT 1894 Oct 31 + -4:16:48 - CMT 1920 May + -4:00 - ART 1930 Dec + -4:00 Arg AR%sT 1969 Oct 5 + -3:00 Arg AR%sT 1991 Mar 3 + -4:00 - WART 1991 Oct 20 + -3:00 Arg AR%sT 1999 Oct 3 + -4:00 Arg AR%sT 2000 Mar 3 + -3:00 - ART +# +# Tucuman (TM), La Rioja (LR), San Juan (SJ), San Luis (SL), Chubut (CH) +# +# Shanks also makes the following claims, which we haven't verified: +# - La Rioja and San Juan switched to -4:00 on 1991-03-01 +# and then to -3:00 on 1991-05-07. +# - San Luis switched to -4:00 on 1990-03-14, then to -3:00 on 1990-10-15, +# then to -4:00 on 1991-03-01, then to -3:00 on 1991-06-01. # If we need to add Zones for these areas, we may need to have a subdirectory # for Argentina, as e.g. "America/San_Luis" is too ambiguious. # -Zone America/Cordoba -4:16:48 - LMT 1894 Oct 31 +Zone America/Tucuman -4:20:52 - LMT 1894 Oct 31 -4:16:48 - CMT 1920 May -4:00 - ART 1930 Dec -4:00 Arg AR%sT 1969 Oct 5 @@ -199,6 +224,8 @@ Zone America/Cordoba -4:16:48 - LMT 1894 -4:00 - WART 1991 Oct 20 -3:00 Arg AR%sT 1999 Oct 3 -4:00 Arg AR%sT 2000 Mar 3 + -3:00 - ART 2004 Jun 1 + -4:00 - WART 2004 Oct 17 -3:00 - ART # # Jujuy (JY) @@ -224,6 +251,8 @@ Zone America/Catamarca -4:23:08 - LMT 18 -4:00 - WART 1991 Oct 20 -3:00 Arg AR%sT 1999 Oct 3 -4:00 Arg AR%sT 2000 Mar 3 + -3:00 - ART 2004 Jun 1 + -4:00 - WART 2004 Oct 17 -3:00 - ART # # Mendoza (MZ) @@ -242,6 +271,17 @@ Zone America/Mendoza -4:35:16 - LMT 1894 -3:00 - ART 2004 May 23 -4:00 - WART 2004 Oct 17 -3:00 - ART +# +# Santa Cruz (SC), Tierra del Fuego, Antartida e Islas del Atlantico Sur (TF) +Zone America/Rio_Gallegos -4:36:52 - LMT 1894 Oct 31 + -4:16:48 - CMT 1920 May # Cordoba Mean Time + -4:00 - ART 1930 Dec + -4:00 Arg AR%sT 1969 Oct 5 + -3:00 Arg AR%sT 1999 Oct 3 + -4:00 Arg AR%sT 2000 Mar 3 + -3:00 - ART 2004 Jun 1 + -4:00 - WART 2004 Oct 17 + -3:00 - ART # Aruba # Zone NAME GMTOFF RULES FORMAT [UNTIL] =================================================================== RCS file: RCS/iso3166.tab,v retrieving revision 2003.5 retrieving revision 2003.5.0.1 diff -pu -r2003.5 -r2003.5.0.1 --- iso3166.tab 2003/12/15 14:36:37 2003.5 +++ iso3166.tab 2004/06/14 07:46:16 2003.5.0.1 @@ -2,11 +2,11 @@ # # @(#)iso3166.tab 1.14 # -# From Paul Eggert <eggert(a)twinsun.com> (2003-02-04): +# From Paul Eggert <eggert(a)twinsun.com> (2004-06-14): # # This file contains a table with the following columns: # 1. ISO 3166-1 alpha-2 country code, current as of -# ISO 3166-1 Newsletter No. V-8 (2003-07-23). See: +# ISO 3166-1 Newsletter No. V-10 (2004-04-26). See: # <a href="http://www.iso.org/iso/en/prods-services/iso3166ma/index.html"> # ISO 3166 Maintenance agency (ISO 3166/MA) # </a>. @@ -36,6 +36,7 @@ AS Samoa (American) AT Austria AU Australia AW Aruba +AX Aaland Islands AZ Azerbaijan BA Bosnia & Herzegovina BB Barbados =================================================================== RCS file: RCS/zone.tab,v retrieving revision 2003.4 retrieving revision 2003.4.0.1 diff -pu -r2003.4 -r2003.4.0.1 --- zone.tab 2003/10/06 13:32:21 2003.4 +++ zone.tab 2004/06/14 07:46:16 2003.4.0.1 @@ -41,11 +41,13 @@ AQ -6617+11031 Antarctica/Casey Casey St AQ -7824+10654 Antarctica/Vostok Vostok Station, S Magnetic Pole AQ -6640+14001 Antarctica/DumontDUrville Dumont-d'Urville Base, Terre Adelie AQ -690022+0393524 Antarctica/Syowa Syowa Station, E Ongul I -AR -3436-05827 America/Buenos_Aires E Argentina (BA, DF, SC, TF) -AR -3124-06411 America/Cordoba most locations (CB,CC,CH,CN,ER,FM,LP,LR,MN,NQ,RN,SA,SE,SF,SJ,SL,TM) +AR -3436-05827 America/Buenos_Aires Buenos Aires (BA, CF) +AR -3124-06411 America/Cordoba most locations (CB, CC, CN, ER, FM, LP, MN, NQ, RN, SA, SE, SF) +AR -3124-06411 America/Tucuman Tucuman, La Rioja, San Juan, San Luis, Chubut (CH, LR, SJ, SL, TM) AR -2411-06518 America/Jujuy Jujuy (JY) AR -2828-06547 America/Catamarca Catamarca (CT) AR -3253-06849 America/Mendoza Mendoza (MZ) +AR -5138-06913 America/Rio_Gallegos Santa Cruz, Tierra del Fuego (SC, TF) AS -1416-17042 Pacific/Pago_Pago AT +4813+01620 Europe/Vienna AU -3133+15905 Australia/Lord_Howe Lord Howe Island @@ -59,6 +61,7 @@ AU -3455+13835 Australia/Adelaide South AU -1228+13050 Australia/Darwin Northern Territory AU -3157+11551 Australia/Perth Western Australia AW +1230-06858 America/Aruba +AX +6006+01957 Europe/Mariehamn AZ +4023+04951 Asia/Baku BA +4352+01825 Europe/Sarajevo BB +1306-05937 America/Barbados =================================================================== RCS file: RCS/tz-link.htm,v retrieving revision 2004.1 retrieving revision 2004.1.0.1 diff -pu -r2004.1 -r2004.1.0.1 --- tz-link.htm 2004/05/27 16:00:30 2004.1 +++ tz-link.htm 2004/06/14 07:46:16 2004.1.0.1 @@ -9,7 +9,7 @@ <meta http-equiv="Content-type" content='text/html; charset="US-ASCII"' /> <meta name="DC.Creator" content="Eggert, Paul" /> <meta name="DC.Contributor" content="Olson, Arthur David" /> -<meta name="DC.Date" content="2004-05-24" /> +<meta name="DC.Date" content="2004-06-14" /> <meta name="DC.Description" content="Sources of information about time zones and daylight saving time" /> <meta name="DC.Identifier" content="http://www.twinsun.com/tz/tz-link.htm" /> @@ -109,9 +109,6 @@ World</a></li> <li><a href="http://www.convertit.com/Go/ConvertIt/World_Time/Current_Time.ASP">Current Time in 1000 Places</a></li> <li><a href="http://timezoneconverter.com/">Time Zone Converter</a></li> </ul></li> -<li><a href="http://www.holidayfestival.com/">The Worldwide Holiday -& Festival Site</a> lists DST-related clock changes along with -holidays.</li> <li><a href="http://www.timeanddate.com/worldclock/">The World Clock - Time Zones</a> is a web interface to a time zone database derived from @@ -152,9 +149,8 @@ contains a script <code>parse_olson</cod <code>tz</code> source into <a href="http://www.perl.org/">Perl</a> modules. It is part of the Perl <a href="http://datetime.perl.org/">DateTime Project</a>, which is freely -available under both the GPL and the Perl <a -href="http://www.perl.com/language/misc/Artistic.html">Artistic -License</a>. DateTime::TimeZone also contains a script +available under both the GPL and the Perl Artistic +License. DateTime::TimeZone also contains a script <code>tests_from_zdump</code> that generates test cases for each clock transition in the <code>tz</code> database.</li> <li><a href="http://oss.software.ibm.com/icu/">International Components for @@ -184,7 +180,7 @@ is a <code>tz</code> binary file reader href="http://www.python.org/">Python</a>. It is freely available under a BSD-style license.</li> </ul> -<h2>Other <code>tz</code>-based time zone conversion software</h2> +<h2>Other <code>tz</code>-based time zone conversion software and standards</h2> <ul> <li><a href="http://java.sun.com/">Sun Java</a> releases since 1.4 contain a copy of a recent <samp>tz</samp> database in a Java-specific @@ -195,10 +191,16 @@ time zones calculator</a> is a HyperCard <li><a href="http://www.cimmyt.org/timezone/">World Time Explorer</a> is a Microsoft Windows program.</li> +<li><a +href="http://oss.software.ibm.com/cvs/icu/~checkout~/icuhtml/design/formatting/ti…">Time +Zone Localization</a> is a proposed mechanism for localizing time zone +labels and abbreviations; for example, one might use it to specify +Russian translations for "Eastern European Summer Time", "EEST", and +<code>Europe/Bucharest</code>.</li> </ul> <h2>Other time zone databases</h2> <ul> -<li><a href="http://www.astro.com/cgi-bin/atlw3/aq.cgi?lang=e">Atlas Query +<li><a href="http://www.astro.com/cgi/aq.cgi?lang=e">Atlas Query - Astrodienst</a> is Astrodienst's Web version of Shanks's excellent time zone history atlases published in both <a href="http://astrocom.com/software/pcatlas.php">computer</a> and <a @@ -217,7 +219,7 @@ for the <code>usno*</code> files in the <li><a href="http://www.airportcitycodes.com/aaa/">Airlines, Airplanes and Airports</a> lists current standard times for thousands of airports around the world. This seems to be derived from -the <a href="http://www.iata.org/sked/publications/">Standard +the <a href="http://www.iata.org/ps/publications/9179.htm">Standard Schedules Information Manual (SSIM)</a> of the the <a href="http://www.iata.org/">International Air Transport Association</a>, @@ -252,9 +254,7 @@ boundaries between time zones within cou <li>Manifold.net's <a href="http://www.manifold.net/download/freemaps.html">Free Maps and GIS Data</a> includes a Manifold-format map of world time zone -boundaries distributed under the GPL. The GeoCommunity's <a -href="http://software.geocomm.com/data/intl_timezones.html">International -Time Zones</a> publishes the same data in other formats.</li> +boundaries distributed under the GPL.</li> <li>The US Geological Survey's National Atlas of the United States publishes the <a href="http://www.nationalatlas.gov/timeznm.html">Time Zones of the United States</a> in the public domain.</li>

1 0

another attempt to change the clocks in the UK
by Peter Ilieve June 9, 2004

June 9, 2004

The summer silly season is almost upon us, and here in the UK some MPs' thoughts are turning again to fiddling with the clocks. Yesterday (8 June) Nigel Beard MP introduced his Lighter Evenings Bill under what is called the ten minute rule. This would advance the clocks in England and Wales by one hour, still keeping summer time. The Scottish Parliament and the Northern Ireland Assembly could make a similar decision for their areas. One of the supporters of this Bill appears to be our old friend John Butterfill (now Sir John Butterfill), who has proposed his own Bill in the past. You can see the Commons order of business that includes this at <http://www.publications.parliament.uk/pa/cm200304/cmagenda/ob040608.htm> and you can read Nigel Beard's speech in Hansard at <http://www.publications.parliament.uk/pa/cm200304/cmhansrd/cm040608/debtext… 08-05.htm#40608-05_head1>. I haven't found the text of the Bill itself yet. It will probably turn up on the Parliament website next week. Ten minute rule Bills have almost no chance of becoming law, so we don't have to worry too much about this yet. Peter Ilieve peter(a)aldie.co.uk

1 0

FW: [Arthur David Olson: RE: tz list server problem?]
by Olson, Arthur David (NIH/NCI) June 8, 2004

June 8, 2004

Dag-Erling is not on the time zone mailing list; direct replies appropriately. --ado -----Original Message----- From: des(a)des.no [mailto:des@des.no] Sent: Monday, June 07, 2004 3:08 PM To: Olson, Arthur David (NIH/NCI) Cc: Garrett Wollman ... I was trying to suggest the following addition to etcetera: Index: etcetera =================================================================== RCS file: /home/ncvs/src/share/zoneinfo/etcetera,v retrieving revision 1.1.2.5 diff -u -r1.1.2.5 etcetera --- etcetera 6 Apr 2001 16:43:21 -0000 1.1.2.5 +++ etcetera 25 May 2004 16:38:14 -0000 @@ -16,6 +16,8 @@ # We want this to work even on installations that omit the other older names. Link Etc/GMT GMT +Link Etc/UTC UTC + Link Etc/UTC Etc/Universal Link Etc/UTC Etc/Zulu DES -- Dag-Erling Smørgrav - des(a)des.no

3 2

Argentina's timezones blues
by Mariano Absatz May 27, 2004

May 27, 2004

Hi, It's somehow hard to find the normative for each Province, but, according to the press, in the next days more Provinces will join Mendoza in setting the clocks back an hour to UTC-04:00. From http://www.lanacion.com.ar/04/05/27/de_604825.asp http://www.clarin.com/diario/2004/05/27/elpais/p-00401.htm San Juan will do it at midnight Sunday 30th (yes, it's the night between Sunday and Monday, just don't ask, it gets worse yet) until October 17th. Tucumán will do it at midnight Monday 31th, and apparently, Chubut, La Rioja, Santa Cruz and Tierra del Fuego would do it also on Monday night. Santa Cruz is apparently waiting for a Provincial Congress confirmation (the other Provinces are using Governors' Decrees). San Luis would also change its tz on Monday night according to: http://www.lanacion.com.ar/04/05/27/de_604901.asp http://www.clarin.com/diario/2004/05/27/um/m-766786.htm The City of Buenos Aires, as well as the Provinces of Buenos Aires, Córdoba, Santa Fe, Entre Ríos and Corrientes confirmed they will NOT change the timezone this winter. The rest of the Provinces are supposed to be analyzing what to do... FWIW, Argentina consists of 23 Provinces and the Autonomous City of Buenos Aires: Ciudad de Buenos Aires (4) Buenos Aires (4) Catamarca Chaco Chubut (3) Córdoba (4) Corrientes (4) Entre Ríos (4) Formosa Jujuy La Pampa La Rioja (3) Mendoza (1) Misiones Neuquen Rio Negro Salta San Juan (2) San Luis (3) Santa Cruz (3) Santa Fe (4) Santiago del Estero Tierra del Fuego (3) Tucumán (3) (1) Already switched on May 23 (2) Would switch on May 30 (3) Would switch on May 31 (4) Would not switch this year FWIW, the districts included in (4) account for the most part of the population of the countries, including the cities where most corporations have their computers installed... Please... take into account that, except for (1) I'm taking this from the newspapers... I'll try to get some authoritative data, but I'm not sure if I'll be able... I'll keep informing you as this think develops... -- Mariano Absatz - El Baby mailto:baby@baby.com.ar http://www.baby.com.ar/ PGP KEYS: http://www.baby.com.ar/datos/personales.html#claves_pgp |\ _ _\\/'> Powered by Pegasus Mail /|__) http://www.pmail.com ) )\ ----------------------------------------------------------- Who are you going to believe, me or your own eyes? -- Groucho Marx

1 0

Re: America/Sao_Paulo DST problem
by Ruby Ballen May 27, 2004

May 27, 2004

I just tested in my system and the time was correctly reported before and after the transition on Feb 14 23:59:59. RBallen

1 0

RE: America/Sao_Paulo DST problem
by Olson, Arthur David (NIH/NCI) May 27, 2004

May 27, 2004

Here are a few lines of "zdump" output for America/Sao_Paulo: America/Sao_Paulo Sun Oct 19 03:00:00 2003 UTC = Sun Oct 19 01:00:00 2003 BRST isdst=1 America/Sao_Paulo Sun Feb 15 01:59:59 2004 UTC = Sat Feb 14 23:59:59 2004 BRST isdst=1 America/Sao_Paulo Sun Feb 15 02:00:00 2004 UTC = Sat Feb 14 23:00:00 2004 BRT isdst=0 America/Sao_Paulo Sun Oct 17 02:59:59 2004 UTC = Sat Oct 16 23:59:59 2004 BRT isdst=0 The important thing to note is at midnight on February 14 clocks are set back an hour. This means that there are two instants when a well-maintained Sao Paulo wall clock would read 11:00:00 PM on February 14 (as well as two instants when it would 11:00:01, 11:00:02, and so on through 11:59:59). The "my_date.c" program feeds year-mon-mday-hour-min-sec into mktime; the values being fed in lie in the "fall back" hour above. Mktime is supposed to return an instant when a wall clock shows the time that's been input to it; here, since there are two such instants (and since "tm_isdst" has been set to -1), mktime is allowed to pick either instant to return. It's luck of the draw that determines which instant mktime returns. --ado

1 0

America/Sao_Paulo DST problem
by Stefano Scarponi May 27, 2004

May 27, 2004

Hi all, During an investigation about customer brazilian problem I downloaded your latest tz lib from "ftp://elsie.nci.nih.gov/pub/". I build and install the library on Linux Redhat 9. I created a simple "my_date.c" that perform a mktime into the range 00:00 - 14 Feb 2004 to 23:59 - 15 Feb 2004. The DST from Brasil Sao_Paulo is the following: file southamerica: Rule Brazil 2000 2001 - Oct Sun>=8 0:00 1:00 S Rule Brazil 2001 max - Feb Sun>=15 0:00 0 - Rule Brazil 2002 only - Nov 3 0:00 1:00 S Rule Brazil 2003 max - Oct Sun>=15 0:00 1:00 S So for the DST about Feb Sun>=15 at 0:00 I expected that the DST occurs at 0:00 15 Feb, but I saw that it occurs at 23:49 14 Feb as you can see from the output program. I set the TZ to TZ=America/Sao_Paulo ./my_date .. .. .. date =<day=14 hours=23 min=45> diff=-60 epoque=1076809501 DST=<1> date =<day=14 hours=23 min=46> diff=-60 epoque=1076809561 DST=<1> date =<day=14 hours=23 min=47> diff=-60 epoque=1076809621 DST=<1> date =<day=14 hours=23 min=48> diff=-60 epoque=1076809681 DST=<1> date =<day=14 hours=23 min=49> diff=-3660 epoque=1076813341 DST=<0> <-------- DST occurs here date =<day=14 hours=23 min=50> diff=-60 epoque=1076813401 DST=<0> date =<day=14 hours=23 min=51> diff=-60 epoque=1076813461 DST=<0> date =<day=14 hours=23 min=52> diff=-60 epoque=1076813521 DST=<0> date =<day=14 hours=23 min=53> diff=-60 epoque=1076813581 DST=<0> date =<day=14 hours=23 min=54> diff=-60 epoque=1076813641 DST=<0> .. .. I think that this is a bug because the DST is for 15 Feb at 0:00 and NOT 23:49 14 Feb. Do you have some suggestions or do you already knows about this problem? This is my "my_date.c" (See attached file: my_date.c) Thanks Stefano

1 0

Now ready: tzcode2004a.tar.gz and tzdata2004a.tar.gz
by Olson, Arthur David (NIH/NCI) May 27, 2004

May 27, 2004

The files... ftp://elsie.nci.nih.gov/pub/tzcode2004a.tar.gz ...and... ftp://elsie.nci.nih.gov/pub/tzdata2004a.tar.gz ...are now available. In addition to the proposed changes circulated on the time zone mailing list by Paul Eggert, these include the changes to handle DST transitions that occur at the end of a month in some years but at the start of the following month in other years (these changes were circulated back in March). I've also added a copy of the correspondence that's the basis for claims about DST in the Navajo Nation. --ado

1 0

Re: Beginner questions
by Ruby Ballen May 26, 2004

May 26, 2004

Well, yes. What I was trying to say is if it is possible to do this: - When the user enables automatic DST calculations, use the regular rules. - When the user disables automatic DST calculations, compute local time using the offset that the time zone has when it is in standard time, regardless of DST being in effect or not. It's a desire to have this option, but if it's difficult to achieve it's OK. Thanks tz-request@lecserver. nci.nih.gov To: RBallen(a)hypercom.com cc: tz(a)lecserver.nci.nih.gov 05/26/04 11:21 AM Subject: Beginner questions <<On Wed, 26 May 2004 08:11:51 -0700, Ruby Ballen <RBallen(a)hypercom.com> said: > 2) Is it possible to disable DST changes when using this library? > Say the user wants to move the clock forward/backward manually when > DST is in effect instead of the library doing it for him. This does not make sense. The clock per se is not changed during the DST transition, only the way local time is computed from UTC. -GAWollman

2 1

Beginner questions
by Ruby Ballen May 26, 2004

May 26, 2004

Some questions about this library (please, keep in mind I'm new using it): 1) I was testing localtime() using US/Pacific as time zone and trying to see if transitions to DST were done correctly. So I set my local time to April 4 2004, 1:59 a.m.. Some minutes later the local time was correctly reported as April 4, 3:02. Then, I set my local time to October 31, 1:59 and I double checked that localtime() was in fact giving me 1:59. Two minutes later I was expecting the wall clock to go back one hour. It didn't. What am I doing wrong? 2) Is it possible to disable DST changes when using this library? Say the user wants to move the clock forward/backward manually when DST is in effect instead of the library doing it for him. Thanks a lot for you help. RBallen

3 2

Re: Beginner questions
by Ruby Ballen May 26, 2004

May 26, 2004

It makes sense. Thanks. So if I set it to October 31, 00:59:00 and wait for an hour I should see the transition, right? Thanks a lot. bww(a)acm.org To: RBallen(a)hypercom.com 05/26/04 08:21 AM cc: Subject: Re: Beginner questions > Then, I set my local time to October 31, 1:59 and I double checked > that localtime() was in fact giving me 1:59. Two minutes later I was > expecting the wall clock to go back one hour. It didn't. What am I doing > wrong? There are two 01:59's on that day ... you set the time to the second, after which there is no transition.

1 0

proposed tz changes for Argentina, Mongolia, Mars, etc.
by Paul Eggert May 24, 2004

May 24, 2004

Here are proposed changes to the tz data. The most urgent items are this weekend's emergency law in Mendoza, Argentina, and a correction to the daylight-saving rules in Mongolia, as these changes affect current time stamps. Changes affecting current time stamps: * Mendoza, Argentina moved its clocks back this weekend due to an emergency law designed to save energy. (This is unusual, as normally clocks are moved forward to save energy, but apparently the province uses a lot of electricity in the morning.) Thanks to Mariano Absatz for this item. * Mongolia does observe daylight-saving time. Thanks to Ganbold Ts. for this item. Changes affecting historical time stamps: * Fixes for time stamps before 1901 in Singapore and Kuala Lumpur. Thanks to Mok Ly Yng for this item. * Cuiaba, Brazil used normal Brazilian daylight-saving rules in 1994/1995. (Sorry, I forgot to write down who told me this.) * The names of time zones in Alaska didn't change officially until November 30, 1983, which means Alaska was officially observing "Yukon Time" for most of November 1983. (Thanks to Arthur David Olson for this item.) Administrative change to how hard links are created: * Link the old name "Navajo" to America/Shiprock, not America/Denver. Commentary fixes only: * Quite a bit of commentary added for the hot topic of time and time zones on Mars. * A cross-reference to Cyprus in the `europe' file. * Calcutta is now officially called `Kolkata'. * The Date and Time Gateway has moved from bsdi.com (which no longer exists) to twiki.org. * Joseph Myers's page on time in Britain has moved from student.cusu.cam.ac.uk to www.srcf.ucam.org. * Add URLs pointing to ICU, Joda Time, and Sun Java 1.4. =================================================================== RCS file: RCS/southamerica,v retrieving revision 2003.5 retrieving revision 2003.5.0.1 diff -pu -r2003.5 -r2003.5.0.1 --- southamerica 2003/12/15 14:31:42 2003.5 +++ southamerica 2004/05/24 07:26:59 2003.5.0.1 @@ -141,6 +141,13 @@ Rule Arg 2000 only - Mar Sun>=1 0:00 0 - # This kind of things had always been done this way in Argentina. # We are still -03:00 all year round in all of the country. # +# From Mariano Absatz (2004-05-21): +# Today it was officially published that the Province of Mendoza is changing +# its timezone this winter... starting tomorrow night.... +# http://www.gobernac.mendoza.gov.ar/boletin/pdf/20040521-27158-normas.pdf +# From Paul Eggert (2004-05-24): +# It's Law No. 7,210. This change is due to a public power emergency, so for +# now we'll assume it's for this year only. # # From Paul Eggert (2002-01-22): # <a href="http://www.spicasc.net/horvera.html"> @@ -232,6 +239,8 @@ Zone America/Mendoza -4:35:16 - LMT 1894 -4:00 - WART 1992 Oct 18 -3:00 Arg AR%sT 1999 Oct 3 -4:00 Arg AR%sT 2000 Mar 3 + -3:00 - ART 2004 May 23 + -4:00 - WART 2004 Oct 17 -3:00 - ART # Aruba @@ -389,8 +398,8 @@ Rule Brazil 1992 only - Oct 25 0:00 1:0 Rule Brazil 1993 only - Jan 31 0:00 0 - # Decree <a href="http://pcdsh01.on.br/HV942.htm">942</a> (1993-09-28) # adopted by same states, plus AM. -# Decree <a href="http://pcdsh01.on.br/HV1252.htm">1,252</a> (1994-09-22) -# adopted by same states, minus AM and MT. +# Decree <a href="http://pcdsh01.on.br/HV1252.htm">1,252</a> (1994-09-22; +# web page corrected 2004-01-07) adopted by same states, minus AM. # Decree <a href="http://pcdsh01.on.br/HV1636.htm">1,636</a> (1995-09-14) # adopted by same states, plus MT and TO. # Decree <a href="http://pcdsh01.on.br/HV1674.htm">1,674</a> (1995-10-13) @@ -536,8 +545,6 @@ Zone America/Campo_Grande -3:38:28 - LMT # # Mato Grosso (MT) Zone America/Cuiaba -3:44:20 - LMT 1914 - -4:00 Brazil AM%sT 1994 Sep 22 - -4:00 - AMT 1995 Sep 14 -4:00 Brazil AM%sT 2003 Sep 24 -4:00 - AMT # =================================================================== RCS file: RCS/europe,v retrieving revision 2003.5 retrieving revision 2003.5.0.1 diff -pu -r2003.5 -r2003.5.0.1 --- europe 2003/12/15 14:31:42 2003.5 +++ europe 2004/05/24 07:26:59 2003.5.0.1 @@ -707,6 +707,9 @@ Zone Europe/Sofia 1:33:16 - LMT 1880 # Croatia # see Serbia and Montenegro +# Cyprus +# See the `asia' file. + # Czech Republic # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S Rule Czech 1945 only - Apr 8 2:00s 1:00 S =================================================================== RCS file: RCS/asia,v retrieving revision 2003.5 retrieving revision 2003.5.0.1 diff -pu -r2003.5 -r2003.5.0.1 --- asia 2003/12/15 14:31:42 2003.5 +++ asia 2004/05/24 07:26:59 2003.5.0.1 @@ -380,7 +380,7 @@ Zone Asia/Dili 8:22:20 - LMT 1912 # India # Zone NAME GMTOFF RULES FORMAT [UNTIL] -Zone Asia/Calcutta 5:53:28 - LMT 1880 +Zone Asia/Calcutta 5:53:28 - LMT 1880 # Kolkata 5:53:20 - HMT 1941 Oct # Howrah Mean Time? 6:30 - BURT 1942 May 15 # Burma Time 5:30 - IST 1942 Sep @@ -1012,17 +1012,13 @@ Rule NBorneo 1935 1941 - Sep 14 0:00 0:2 Rule NBorneo 1935 1941 - Dec 14 0:00 0 - # # peninsular Malaysia -# From Paul Eggert (2003-11-01): # The data here are taken from Mok Ly Yng (2003-10-30) # <http://www.math.nus.edu.sg/aslaksen/teaching/timezone.html>. -# Before 1901, Penang, Malacca and Singapore each had their own time zone; -# assume Kuala Lumpur used Malaccan time. # Zone NAME GMTOFF RULES FORMAT [UNTIL] -Zone Asia/Kuala_Lumpur 6:46:48 - LMT 1880 - 6:49:00 - MMT 1901 Jan 1 # Malacca Mean Time +Zone Asia/Kuala_Lumpur 6:46:46 - LMT 1901 Jan 1 6:55:25 - SMT 1905 Jun 1 # Singapore M.T. 7:00 - MALT 1933 Jan 1 # Malaya Time - 7:00 0:20 MALST 1936 + 7:00 0:20 MALST 1936 Jan 1 7:20 - MALT 1941 Sep 1 7:30 - MALT 1942 Feb 16 9:00 - JST 1945 Sep 12 @@ -1089,6 +1085,15 @@ Zone Indian/Maldives 4:54:00 - LMT 1880 # # [The province of Selenge is omitted from the above lists.] +# From Ganbold Ts., Ulaanbaatar <ganbold(a)micom.mng.net> (2004-04-17): +# Daylight saving occurs at 02:00 local time last Saturday of March. +# It will change back to normal at 02:00 local time last Saturday of +# September.... As I remember this rule was changed in 2001. +# +# From Paul Eggert (2004-04-17): +# For now, assume Rives McDow's informant got confused about Friday vs +# Saturday, and that his 2001 dates should have 1 added to them. + # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S Rule Mongol 1983 1984 - Apr 1 0:00 1:00 S Rule Mongol 1983 only - Oct 1 0:00 0 - @@ -1098,8 +1103,9 @@ Rule Mongol 1983 only - Oct 1 0:00 0 - Rule Mongol 1985 1998 - Mar lastSun 2:00s 1:00 S Rule Mongol 1984 1998 - Sep lastSun 2:00s 0 - # IATA SSIM (1999-09) says Mongolia no longer observes DST. -Rule Mongol 2001 only - Apr 27 2:00s 1:00 S -Rule Mongol 2001 only - Sep 28 2:00s 0 - +Rule Mongol 2001 only - Apr lastSat 2:00 1:00 S +Rule Mongol 2001 max - Sep lastSat 2:00 0 - +Rule Mongol 2002 max - Mar lastSat 2:00 1:00 S # Zone NAME GMTOFF RULES FORMAT [UNTIL] # Hovd, a.k.a. Chovd, Dund-Us, Dzhargalant, Khovd, Jirgalanta @@ -1309,10 +1315,10 @@ Zone Asia/Riyadh 3:06:52 - LMT 1950 # The data here are taken from Mok Ly Yng (2003-10-30) # <http://www.math.nus.edu.sg/aslaksen/teaching/timezone.html>. # Zone NAME GMTOFF RULES FORMAT [UNTIL] -Zone Asia/Singapore 6:55:25 - LMT 1880 +Zone Asia/Singapore 6:55:25 - LMT 1901 Jan 1 6:55:25 - SMT 1905 Jun 1 # Singapore M.T. 7:00 - MALT 1933 Jan 1 # Malaya Time - 7:00 0:20 MALST 1936 + 7:00 0:20 MALST 1936 Jan 1 7:20 - MALT 1941 Sep 1 7:30 - MALT 1942 Feb 16 9:00 - JST 1945 Sep 12 =================================================================== RCS file: RCS/tz-link.htm,v retrieving revision 2003.5 retrieving revision 2003.5.0.1 diff -pu -r2003.5 -r2003.5.0.1 --- tz-link.htm 2003/12/15 14:31:42 2003.5 +++ tz-link.htm 2004/05/24 07:26:59 2003.5.0.1 @@ -9,7 +9,7 @@ <meta http-equiv="Content-type" content='text/html; charset="US-ASCII"' /> <meta name="DC.Creator" content="Eggert, Paul" /> <meta name="DC.Contributor" content="Olson, Arthur David" /> -<meta name="DC.Date" content="2003-09-21" /> +<meta name="DC.Date" content="2004-05-24" /> <meta name="DC.Description" content="Sources of information about time zones and daylight saving time" /> <meta name="DC.Identifier" content="http://www.twinsun.com/tz/tz-link.htm" /> @@ -99,8 +99,8 @@ Here are some recent links that may be o </p> <h2>Web pages using recent versions of the <code>tz</code> database</h2> <ul> -<li><a href="http://www.bsdi.com/date/">Date and Time Gateway</a> is a -text-based point-and-click interface to tables of current time +<li><a href="http://twiki.org/cgi-bin/xtra/tzdate">Date and Time Gateway</a> +is a text-based point-and-click interface to tables of current time throughout the world.</li> <li>Fancier web interfaces, roughly in ascending order of complexity, include: <ul> @@ -157,6 +157,15 @@ href="http://www.perl.com/language/misc/ License</a>. DateTime::TimeZone also contains a script <code>tests_from_zdump</code> that generates test cases for each clock transition in the <code>tz</code> database.</li> +<li><a href="http://oss.software.ibm.com/icu/">International Components for +Unicode (ICU)</a> contains a C/C++ library for internationalization that +has a compiler from <samp>tz</samp> source into an ICU-specific format. +ICU is freely available under a BSD-style license.</li> +<li><a href="http://joda-time.sourceforge.net/">Joda Time - Java date +and time API</a> contains a class +<code>org.joda.time.tz.ZoneInfoCompiler</code> that compiles +<code>tz</code> source into a Joda-specific binary format. Joda Time +is freely available under a BSD-style license.</li> </ul> <h2>Other <code>tz</code> binary file readers</h2> <ul> @@ -177,6 +186,9 @@ under a BSD-style license.</li> </ul> <h2>Other <code>tz</code>-based time zone conversion software</h2> <ul> +<li><a href="http://java.sun.com/">Sun Java</a> releases since 1.4 +contain a copy of a recent <samp>tz</samp> database in a Java-specific +format.</li> <li><a href="http://www1.tip.nl/~t876506/AboutTimeZonesHC.html">HyperCard time zones calculator</a> is a HyperCard stack.</li> @@ -330,7 +342,7 @@ is Singapore in the "Wrong" Time Zone?</ history of legal time in Singapore and Malaysia.</dd> <dt>United Kingdom</dt> <dd><a -href="http://student.cusu.cam.ac.uk/~jsm28/british-time/">History of +href="http://www.srcf.ucam.org/~jsm28/british-time/">History of legal time in Britain</a> discusses in detail the country with perhaps the best-documented history of clock adjustments. The National Physical Laboratory also maintains an <a @@ -362,6 +374,11 @@ among time scales like TAI, TDB, TT and Space Flight - Reference Systems - Time Conventions</a> briefly explains interplanetary space flight timekeeping.</li> <li><a +href="http://www.giss.nasa.gov/tools/mars24/help/notes.html">Technical +Notes on Mars Solar Time as Adopted by the Mars24 Sunclock</a> briefly +describes Mars Coordinated Time (MTC) and the diverse local time +scales used by each landed mission on Mars.</li> +<li><a href="http://hpiers.obspm.fr/eop-pc/products/bulletins/bulletins.html">Bulletins maintained by the IERS EOP (PC)</a> contains official publications of the Earth Orientation Parameters Product Center of the =================================================================== RCS file: RCS/northamerica,v retrieving revision 2003.5 retrieving revision 2003.5.0.1 diff -pu -r2003.5 -r2003.5.0.1 --- northamerica 2003/12/15 14:36:18 2003.5 +++ northamerica 2004/05/24 07:26:59 2003.5.0.1 @@ -193,10 +193,6 @@ Rule US 1987 max - Apr Sun>=1 2:00 1:00 # Samoa standard time # The law doesn't give abbreviations. # -# From Paul Eggert (1995-12-19): -# Shanks uses 1983-10-30, not 1983-11-30, for the 1983 transitions. -# Go with Shanks. -# # From Paul Eggert (2000-01-08), following a heads-up from Rives McDow: # Public law 106-564 (2000-12-23) introduced the abbreviation # "Chamorro Standard Time" for time in Guam and the Northern Marianas. @@ -323,13 +319,14 @@ Zone America/Juneau 15:02:19 - LMT 1867 -8:00 US P%sT 1946 -8:00 - PST 1969 -8:00 US P%sT 1983 Oct 30 2:00 + -9:00 US Y%sT 1983 Nov 30 -9:00 US AK%sT Zone America/Yakutat 14:41:05 - LMT 1867 Oct 18 -9:18:55 - LMT 1900 Aug 20 12:00 -9:00 - YST 1942 -9:00 US Y%sT 1946 -9:00 - YST 1969 - -9:00 US Y%sT 1983 Oct 30 2:00 + -9:00 US Y%sT 1983 Nov 30 -9:00 US AK%sT Zone America/Anchorage 14:00:24 - LMT 1867 Oct 18 -9:59:36 - LMT 1900 Aug 20 12:00 @@ -338,6 +335,7 @@ Zone America/Anchorage 14:00:24 - LMT 1 -10:00 - CAT 1967 Apr -10:00 - AHST 1969 -10:00 US AH%sT 1983 Oct 30 2:00 + -9:00 US Y%sT 1983 Nov 30 -9:00 US AK%sT Zone America/Nome 12:58:21 - LMT 1867 Oct 18 -11:01:38 - LMT 1900 Aug 20 12:00 @@ -346,6 +344,7 @@ Zone America/Nome 12:58:21 - LMT 1867 O -11:00 - NST 1967 Apr -11:00 - BST 1969 -11:00 US B%sT 1983 Oct 30 2:00 + -9:00 US Y%sT 1983 Nov 30 -9:00 US AK%sT Zone America/Adak 12:13:21 - LMT 1867 Oct 18 -11:46:38 - LMT 1900 Aug 20 12:00 @@ -354,6 +353,7 @@ Zone America/Adak 12:13:21 - LMT 1867 O -11:00 - NST 1967 Apr -11:00 - BST 1969 -11:00 US B%sT 1983 Oct 30 2:00 + -10:00 US AH%sT 1983 Nov 30 -10:00 US HA%sT # Shanks writes that part of southwest Alaska (e.g. Aniak) # switched from -11:00 to -10:00 on 1968-09-22 at 02:00, =================================================================== RCS file: RCS/backward,v retrieving revision 2003.4 retrieving revision 2003.4.0.1 diff -pu -r2003.4 -r2003.4.0.1 --- backward 2003/10/06 13:32:20 2003.4 +++ backward 2004/05/24 07:26:59 2003.4.0.1 @@ -65,7 +65,7 @@ Link Africa/Tripoli Libya Link America/Tijuana Mexico/BajaNorte Link America/Mazatlan Mexico/BajaSur Link America/Mexico_City Mexico/General -Link America/Denver Navajo +Link America/Shiprock Navajo Link Pacific/Auckland NZ Link Pacific/Chatham NZ-CHAT Link Pacific/Pago_Pago Pacific/Samoa =================================================================== RCS file: RCS/Theory,v retrieving revision 2003.5 retrieving revision 2003.5.0.1 diff -pu -r2003.5 -r2003.5.0.1 --- Theory 2003/12/15 14:36:34 2003.5 +++ Theory 2004/05/24 07:26:59 2003.5.0.1 @@ -7,6 +7,7 @@ Names of time zone regions Time zone abbreviations Calendrical issues + Time and time zones on Mars ----- Time and date functions ----- @@ -504,3 +505,48 @@ convert to the Gregorian calendar until Source: H. Grotefend, _Taschenbuch der Zeitrechnung des deutschen Mittelalters und der Neuzeit_, herausgegeben von Dr. O. Grotefend (Hannover: Hahnsche Buchhandlung, 1941), pp. 26-28. + + +----- Time and time zones on Mars ----- + +Some people have adjusted their work schedules to fit Mars time. +Dozens of special Mars watches were built for Jet Propulsion +Laboratory workers who kept Mars time during the Mars Exploration +Rovers mission (2004). These timepieces look like normal Seikos and +Citizens but use Mars seconds rather than terrestrial seconds. + +A Mars solar day is called a "sol" and has a mean period equal to +about 24 hours 39 minutes 35.244 seconds in terrestrial time. It is +divided into a conventional 24-hour clock, so each Mars second equals +about 1.02749125 terrestrial seconds. + +The prime meridian of Mars goes through the center of the crater +Airy-0, named in honor of the British astronomer who built the +Greenwich telescope that defines Earth's prime meridian. Mean solar +time on the Mars prime meridian is called Mars Coordinated Time (MTC). + +Each landed mission on Mars has adopted a different reference for +solar time keeping, so there is no real standard for Mars time zones. +For example, the Mars Exploration Rover project (2004) defined two +time zones "Local Solar Time A" and "Local Solar Time B" for its two +missions, each zone designed so that its time equals local true solar +time at approximately the middle of the nominal mission. Such a "time +zone" is not particularly suited for any application other than the +mission itself. + +Many calendars have been proposed for Mars, but none have achieved +wide acceptance. Astronomers often use Mars Sol Date (MSD) which is a +sequential count of Mars solar days elapsed since about 1873-12-29 +12:00 GMT. + +The tz database does not currently support Mars time, but it is +documented here in the hopes that support will be added eventually. + +Sources: + +Michael Allison and Robert Schmunk, +"Technical Notes on Mars Solar Time as Adopted by the Mars24 Sunclock" +<http://www.giss.nasa.gov/tools/mars24/help/notes.html> (2004-03-15). + +Jia-Rui Chong, "Workdays Fit for a Martian", Los Angeles Times +(2004-01-14), pp A1, A20-A21.

1 0

Argentina - Mendoza: Changes
by Mariano Absatz May 21, 2004

May 21, 2004

Hi, well, today it was officially published that the Province of Mendoza is changing its timezone this winter... starting tomorrow night. I'm quite in a hurry, but: At midnight Saturday May 22nd, the clocks will be pulled back one hour (from UTC-03:00 to UTC-04:00). At midnight Saturday October 16th, the clocks will get back to UTC-03:00. The Official data is at http://www.gobernac.mendoza.gov.ar/boletin/pdf/20040521-27158-normas.pdf (in Spanish). Regards. -- Mariano Absatz - El Baby mailto:baby@baby.com.ar http://www.baby.com.ar/ PGP KEYS: http://www.baby.com.ar/datos/personales.html#claves_pgp |\ _ _\\/'> Powered by Pegasus Mail /|__) http://www.pmail.com ) )\ ----------------------------------------------------------- Windows, another fine product from the folks who gave us EDLIN.

1 0

possible changes in Argentina (southamerica)
by Mariano Absatz May 19, 2004

May 19, 2004

Hi, Apparently, the Province of Mendoza, in Argentina's Mid-West, is about to change it's timezone to UTC-04:00 Most of Argentina lies 'geographically' in that tz, but at some point in time, after having implemented UTC-03:00 for the summer, the country 'just stayed there'... what's more, a few years ago, for some time, it used a summer tz of UTC-02:00. As Mendoza is one of the Provinces in the Western border, it is most affected for using a 'more Eastern' tz, and this is especially bad in the (Southern) winter. As there's an Energy crisis in Argentina, Mendoza is trying to 'wake up an hour later'. It remains to be seen if the Province of Mendoza effectively legislates this and what the other Provinces do (especially, the other Provinces in the West). Newspaper info (in Spanish): http://www.lanacion.com.ar/04/05/11/de_600178.asp http://www.clarin.com/diario/2004/05/15/elpais/p-00401.htm http://www1.cronica.com.ar/article/articleview/1084567955/1/20/ http://www.losandes.com.ar/2004/0505/editorial/nota186060_1.htm http://www.losandes.com.ar/2004/0512/economia/nota187333_1.htm I'll keep the list posted as this develops. Regards. -- Mariano Absatz - El Baby mailto:baby@baby.com.ar http://www.baby.com.ar/ PGP KEYS: http://www.baby.com.ar/datos/personales.html#claves_pgp |\ _ _\\/'> Powered by Pegasus Mail /|__) http://www.pmail.com ) )\

2 2

Time zones from Windows XP
by Ruby Ballen May 18, 2004

May 18, 2004

I am new in this mailing list so, please, forgive me if this has been asked before. I'm trying to map the list of time zones that Windows XP includes, to the correct binary files in tz Database, but I am missing some of them. I just could not find which one to use or if it is supported at all. Here is the list: (GMT - 12:00) International Date Line West (GMT - 06:00) Central America (GMT - 03:00) Brasilia (GMT - 02:00) Mid-Atlantic (GMT + 01:00) West Central Africa (GMT + 06:00) Sri Jayawardenepura (GMT + 13:00) Nuku’alofa Also, is there any site where I can find documentation about this library? Thanks a lot for your help. RBallen

3 2

tzdata 2003e: imperfections
by Oscar van Vlijmen May 18, 2004

May 18, 2004

I found a couple of small imperfections in the tzdata files. asia file: Cyprus is now (May 01, 2004) part of the European Union. In spite of the interesting remarks for Cyprus in the tz data file, the Cyprus entry should be in the europe file. antarctica file: New Zealand: Rules are given, but no Zone information, so no actual time information. All files: GMT is obsolete. UTC should be used. Nearly all files, lots of entries: In some cases DST is no longer observed, but the Zone lines still mention a DST Rule. One example from the asia file (some information omitted by me): # Korea (North and South) ... # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S Rule ROK 1960 only - May 15 0:00 1:00 D Rule ROK 1960 only - Sep 13 0:00 0 S Rule ROK 1987 1988 - May Sun<=14 0:00 1:00 D Rule ROK 1987 1988 - Oct Sun<=14 0:00 0 S # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Seoul 8:27:52 - LMT 1890 8:30 - KST 1904 Dec 9:00 - KST 1928 8:30 - KST 1932 9:00 - KST 1954 Mar 21 8:00 ROK K%sT 1961 Aug 10 8:30 - KST 1968 Oct 9:00 ROK K%sT ... Since South Korea no longer observes DST, it would be better for the consistency of the database if the last line was changed into: 9:00 ROK K%sT 1988 Oct and an extra line was added, like: 9:00 - KST The software will give the correct time for e.g. this moment I guess, because no Rule line can be found, valid for May 2004. So, changing the database files for this could get a low priority, but it is still an imperfection! Oscar van Vlijmen 2004-05-17

7 11

RE: tzdata 2003e: imperfections (DST rules)
by Olson, Arthur David (NIH/NCI) May 17, 2004

May 17, 2004

> If I am interpreting the documentation correctly, then the last Zone line says that there is a Rule "ROK" in effect, but for dates after Sunday October 09, 1988 no Rule can be found. The last Rule line says that on Sunday October 09, 1988 you should transition out of DST, and that's what the software does. After that, there aren't any transitions specified by Rules, so the software doesn't do anything else. This really is what's supposed to happen; there's no need for a change here. --ado

1 0