- tz - lists.iana.org

RE: bug in tzcode2001c: strftime locale cache
by Olson, Arthur David (NCI) June 15, 2001

June 15, 2001

> The strftime locale code attempts to read the locale cache even if the > cache wasn't set up correctly. This leads to bogus output on your program's > second (and subsequent) call to strftime(), if lookup failed. > ... > This patch fixes this. An alternate fix appears below. --ado *** 7.62/strftime.c Fri Jun 15 13:00:07 2001 --- 7.63/strftime.c Fri Jun 15 13:00:07 2001 *************** *** 603,609 **** static const char locale_home[] = LOCALE_HOME; static const char lc_time[] = "LC_TIME"; static char * locale_buf; - static char locale_buf_C[] = "C"; int fd; int oldsun; /* "...ain't got nothin' to do..." */ --- 603,608 ---- *************** *** 664,671 **** goto bad_locale; bufsize = namesize + st.st_size; locale_buf = NULL; ! lbuf = (lbuf == NULL || lbuf == locale_buf_C) ? ! malloc(bufsize) : realloc(lbuf, bufsize); if (lbuf == NULL) goto bad_locale; (void) strcpy(lbuf, name); --- 663,669 ---- goto bad_locale; bufsize = namesize + st.st_size; locale_buf = NULL; ! lbuf = (lbuf == NULL) ? malloc(bufsize) : realloc(lbuf, bufsize); if (lbuf == NULL) goto bad_locale; (void) strcpy(lbuf, name); *************** *** 714,720 **** (void) close(fd); no_locale: localebuf = C_time_locale; ! locale_buf = locale_buf_C; return &localebuf; } #endif /* defined LOCALE_HOME */ --- 712,718 ---- (void) close(fd); no_locale: localebuf = C_time_locale; ! locale_buf = NULL; return &localebuf; } #endif /* defined LOCALE_HOME */

1 0

bug in tzcode2001c: strftime locale cache
by Jonathan Lennox June 14, 2001

June 14, 2001

The strftime locale code attempts to read the locale cache even if the cache wasn't set up correctly. This leads to bogus output on your program's second (and subsequent) call to strftime(), if lookup failed. I discovered this because lookup failed for me on Solaris and FreeBSD -- on Solaris because locales are kept as .so's, and on FreeBSD because the "C" locale is left implicit and not stored on disk. This patch fixes this. --- tzcode2001c/strftime.c Tue Jun 5 13:49:50 2001 +++ tzcode2001c-Sun5/strftime.c Thu Jun 14 14:27:35 2001 @@ -604,6 +604,7 @@ static const char lc_time[] = "LC_TIME"; static char * locale_buf; static char locale_buf_C[] = "C"; + static int cache_good; int fd; int oldsun; /* "...ain't got nothin' to do..." */ @@ -629,7 +630,7 @@ ** If the locale name is the same as our cache, use the cache. */ lbuf = locale_buf; - if (lbuf != NULL && strcmp(name, lbuf) == 0) { + if (cache_good && lbuf != NULL && strcmp(name, lbuf) == 0) { p = lbuf; for (ap = (const char **) &localebuf; ap < (const char **) (&localebuf + 1); @@ -705,6 +706,7 @@ ** Record the successful parse in the cache. */ locale_buf = lbuf; + cache_good = 1; return &localebuf; @@ -715,6 +717,7 @@ no_locale: localebuf = C_time_locale; locale_buf = locale_buf_C; + cache_good = 0; return &localebuf; } #endif /* defined LOCALE_HOME */ -- Jonathan Lennox lennox(a)cs.columbia.edu

1 0

Proposal: API for thread-safe time zone functions
by Jonathan Lennox June 13, 2001

June 13, 2001

One of the major shortcomings of the current time zone API defined by ISO C and POSIX is that they rely on global data to define the current time zone. If you're writing a server program which needs to talk to people all over the world in their local time zones, this can lead to remarkable difficulties. Therefore, I've written up a proposal (attached) for a thread-safe API for time zone functions. These extend (I think) the current time API in a natural way. There are two forms: one purely re-entrant, and another one that specifies thread-local timezone data to be used by the existing time functions. I've drawn a lot of inspiration for this work from Ulrich Drepper's work on thread-aware POSIX locales (http://www.cygnus.com/~drepper/tllocale.ps.bz2) * Are people interested in this? * Do people think that my proposal is a sensible API? * Would people be interested in seeing the resulting code? * Would people be interested in helping write the code? * Would the resulting code (assuming it's written sensibly) be acceptable/appropriate for incorporation into tzcode? Comments very welcome! A proposal for thread-safe time zone information. Three functions manipulate a struct tz: Name newtz -- create a time zone object Synopsis #include <time.h> struct tz* newtz(const char *tzname); Description The newtz() function creates a new time zone object, corresponding to the given time zone name. tzname is a pointer to a string representing the name of the allocated time zone. It has the same syntax as the "TZ" environment variable, both the POSIX forms and locally-defined symbolic names. The allocated struct tz contains all necessary information to represent times in the specified time zone. It has one externally-visible element: tz_name, an array of two ASCII strings containing the time zone abbreviations for standard and daylight time in the current time zone. struct tz { const char *tz_name[2]; (private data) }; If tzname is NULL, the returned struct tz describes the local wall-clock time, as best as it is known by the local system. If tzname is the empty string "", the returned struct tz describes Coordinated Universal Time (UTC). (The POSIX rules also allow UTC to be represented with the string "GMT0".) This interface is designed so that newtz(getenv("TZ")) will return an object describing the default time zone object that non-thread-aware versions of the time functions will use by default, provided TZ (if set) is set to a valid time zone name. Return Value If the function call succeeds, the return value is a pointer to a time zone object, which should be released by a call to freetz(). If it fails, it returns NULL and sets errno. Errors The newtz() function shall fail if: ENOMEM Not enough memory is available to create the time zone object. ENOENT No known time zone corresponds to tzname. newtz() may also fail with other errno values if there is a problem with the system time zone database. Name freetz -- Free resources allocated for a time zone object Synopsis #include <time.h> void freetz(struct tz* tzobj); Description The freetz() function frees the resources allocated for a time zone object returned by a call to newtz() or duptz(). If the system defines the tm_zone field of struct tm, this function invalidates the strings pointed to by the tm_zone field of all struct tm values created by localtime_z called with this tzobj. Return Value None. Errors None. Name duptz -- Duplicate a time zone object Synopsis #include <time.h> struct tz* duptz(const struct tz* tzobj); Description The duptz() function can be used to duplicate an existing time zone object. A time zone object can be used at any time in multiple places but if the lifetime can possibly end before all uses are finished one has to create a duplicate. Return Value If the function succeeds it returns a pointer to a time zone object identical to the one represented by the pointer passed in tzobj. If it fails it returns NULL. Errors The duptz() function shall fail if: ENOMEM Not enough memory is available to create the duplicated time zone object. The duptz() function may fail if: EINVAL tzobj does not point to a valid time zone object. Modified time-zone-aware time manipulation functions: struct tm * localtime_z(const time_t *clock, struct tm *result, const struct tz *tz); Equivalent to localtime_r() or gmtime_r(), in the time zone represented by tz, except that tz->tz_name is not modified. (The return value's tm_zone value is set correctly, if the system has tm_zone.) char * ctime_z(const time_t *clock, char *buf, const struct tz *tz); Equivalent to ctime_r(), in the time zone represented by tz. char * asctime_z(const struct tm *tm, char *buf, const struct tz *tz); Equivalent to asctime_r(), in the time zone represented by tz. time_t mktime_z(struct tm* tm, const struct tz *tz); Equivalent to mktime() or timegm(), in the time zone represented by tz. size_t strftime_z(char *buf, size_t maxsize, const char *format, const struct tm* timeptr, const struct tz *tz); Equivalent to strftime(), in the time zone represented by tz. char * strptime_z(const char *buf, const char *format, struct tm *timeptr, const struct tz *tz); Equivalent to strptime(), in the time zone represented by tz. (This affects only the interpretation of the %Z format specifier.) Thread-support functions Name tzuse -- use time zone object in current thread. Synopsis #include <time.h> void tzuse(const struct tz *tz); Description The tzuze() function is similar to the tzset() function, but it does not affect the global time zone. Instead it selects the new time zone only for the current thread. The time zone setting for all other threads remains the same. Once tzuse() has been called, all calls to the functions localtime(), localtime_r(), ctime(), ctime_r(), asctime(), asctime_r(), mktime(), strftime(), and strptime() in the current thread will use the current thread's define time zone. If tzuse() is called with a NULL pointer as its argument, the current thread will again use the global time zone object. -- Jonathan Lennox lennox(a)cs.columbia.edu

9 33

Re: Russian cities
by Oscar van Vlijmen June 13, 2001

June 13, 2001

How to prove that Volgograd (Russia) is in the same timezone as Moscow? Well now, I have tried some more search phrases and found at last a couple of Russian pages with lists of all major Russian cities. It seems that there are only let's say one or two originals and many copies of them at several sites. I found the following URLs. http://www.bereg.ru/sprav_info/inform/time.shtml http://newhouse.ru/help/timezone.html http://real.businesstime.ru/trip/sprav/timez.html http://www.mark-itt.ru/Collection/Russia/tz_rus.html and more with the same list. The table heading appearing in most lists reads (literally) translated: Table of corrections of time of cities of the Russian Federation and of states of neighbouring foreign countries relative to the city of Moscow. All lists tell us that Volgograd is in the same timezone as Moscow (UTC+3). But also Saratov and very likely the whole Saratovskaya oblast' is in the Moscow timezone! Ul'yanovsk, Samara and Astrakhan' are in UTC+4 according to these lists. Oscar van Vlijmen 13-Jun-2001

1 0

Question about Zone/Rule semantics
by Damon Chaplin June 13, 2001

June 13, 2001

I have a question about how to interpret Zone/Rule data. I'm unsure about this zone: Zone America/Chihuahua -7:04:20 - LMT 1921 Dec 31 23:55:40 -7:00 - MST 1927 Jun 10 23:00 -6:00 - CST 1930 Nov 15 -7:00 - MST 1931 May 1 23:00 -6:00 - CST 1931 Oct -7:00 - MST 1932 Apr 1 -6:00 - CST 1996 -6:00 Mexico C%sT 1998 -6:00 - CST 1998 Apr Sun>=1 3:00 -7:00 Mexico M%sT The corresponding Rule lines are: Rule Mexico 1996 2000 - Apr Sun>=1 2:00 1:00 D Rule Mexico 1996 2000 - Oct lastSun 2:00 0 S What is the wall-clock offset from UTC on April 10th 1998? The last UNTIL value is "1998 Apr Sun>=1 3:00", which is just after the April Rule came into effect ("Apr Sun>=1 2:00"). So I'm unsure if the Rule is supposed to still be in effect or not. i.e. I don't know if it should be -7:00 (standard time) or -6:00 (daylight time). It makes more sense if it is daylight time, but then why didn't the UNTIL value just use "Apr Sun>=1 2:00" and make it obvious. My general question is: do Rules apply to a particular period within a Zone (i.e. one line in the Zone description) even when they happened before the Zone period started? Damon (I'm working on a program to convert the timezone database to the format needed by the iCalendar specification, for use by calendaring apps etc.)

1 0

Changes in Argentina (or not)
by Mariano Absatz June 12, 2001

June 12, 2001

Hi, one of the major newspapers here in Argentina said that the 1999 Timezone Law (which never was effectively applied) will (would?) be in effect starting Sunday, June 17th (yeah, in the middle of winter, down here). The article is at http://ar.clarin.com/diario/2001-06-06/e-01701.htm for those that can read Spanish. The only verifiable Law applying is Murphy's Law applies since tzdata2001c was published YESTERDAY. The Law itself is "Ley N° 25155", sanctioned on 25-Aug-1999, enacted 17-Sep-1999 and published 21-Sep-1999. The official publication is at: http://www.boletin.jus.gov.ar/BON/Primera/1999/09-Septiembre/21/PDF/BO21-09 -99LEG.PDF Regretfully, you have to subscribe (and pay) for the on-line version of the Boletin Oficial at http://www.jus.gov.ar/servi/boletin/ to be able to access it. There's another (paid) service where you can get all the Argentine Laws at http://std.saij.jus.gov.ar/ which lawyers prefer. Not paying, I only could see the Summary at: http://www1.hcdn.gov.ar/folio-cgi- bin/om_isapi.dll?clientID=1622813&advquery=Huso%20Horario&infobase=leyes.nfo&record= {844}&softpage=Document42&x=22&y=19&zz= Since I don't trust it's quite valid 'cause it has a very "dynamic" look, I got there from http://www.diputados.gov.ar/ pressed the "BASES de DATOS" button, followed the "Leyes Nacionales" link, entered "Huso Horario" and pressed "BUSCAR". There you get to the summary (alas in Spanish). I'll attempt a rough translation here: ==================================================================================== Title: Official Time. Summary: Time zone four (4) hours to the west of the Greenwich Meridian is established as the Official Time in all of the Country territory, according to the correspondig place of the Argentine Republic in the International Time Zone System. Starting at zero hour of the first Sunday of October every year, the time zone three (3) [west] of the Greenwich Meridian will be adopted up until the zero hour of the first Sunday of March in the following year. Updates: Decree 186/2000, enacted 2-Mar-2000, published 3-Mar-2000: The change of the Official Time enacted by Article 2 of Law # 25155 is prorrogated until the first Sunday in March, 2001. ==================================================================================== Anyway, considering the problems that arised when the Law was published, the general ignorance surrounding the subject in general (and especially in National and Provincial Authorities), mixed with the will to confront anything the government attempts (for good or for bad), I would wait a week before commiting changes. Recent history is on my side :-) In fact, I saw no Decree published in the last few days. I attach a tentative 'diff -c' against the latest (tzdata2001c) southamerica file. I'll keep the list informed of news regarding this. -- 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 ) )\ *** southamerica Wed Jun 6 09:58:19 2001 --- southamerica.new Wed Jun 6 10:11:23 2001 *************** *** 115,120 **** --- 115,127 ---- Rule Arg 1999 only - Oct Sun>=1 0:00 1:00 S Rule Arg 2000 only - Mar Sun>=1 0:00 0 - # + # Mariano Absatz (2001-06-06): + # Though the Decree hasn't been published yet, apparently, Law #25155 from + # 1999 would be implemented starting Sunday, June 17th in 2001. + Rule Arg 2001 only - Jun Sun>=17 0:00 0 - + Rule Arg 2001 max - Oct Sun>=1 0:00 1:00 S + Rule Arg 2002 max - Mar Sun>=1 0:00 0 - + # # From Peter Gradelski via Steffen Thorsen (2000-03-01): # We just checked with our Sao Paulo office and they say the government of # Argentina decided not to become one of the countries that go on or off DST. *************** *** 135,141 **** -4:00 Arg AR%sT 1969 Oct 5 -3:00 Arg AR%sT 1999 Oct 3 0:00 -4:00 Arg AR%sT 2000 Mar 3 0:00 ! -3:00 - ART # # Santa Fe (SF), Entre Rios (ER), Corrientes (CN), Misiones (MN), Chaco (CC), # Formosa (FM), La Pampa (LP), Chubut (CH) --- 142,149 ---- -4:00 Arg AR%sT 1969 Oct 5 -3:00 Arg AR%sT 1999 Oct 3 0:00 -4:00 Arg AR%sT 2000 Mar 3 0:00 ! -3:00 - ART 2001 Jun 17 0:00 ! -4:00 Arg AR%sT # # Santa Fe (SF), Entre Rios (ER), Corrientes (CN), Misiones (MN), Chaco (CC), # Formosa (FM), La Pampa (LP), Chubut (CH) *************** *** 146,152 **** -3:00 Arg AR%sT 1991 Jul -3:00 - ART 1999 Oct 3 0:00 -4:00 Arg AR%sT 2000 Mar 3 0:00 ! -3:00 - ART # # Cordoba (CB), Santiago del Estero (SE), Salta (SA), Tucuman (TM), La Rioja (LR), San Juan (SJ), San Luis (SL), # Neuquen (NQ), Rio Negro (RN) --- 154,161 ---- -3:00 Arg AR%sT 1991 Jul -3:00 - ART 1999 Oct 3 0:00 -4:00 Arg AR%sT 2000 Mar 3 0:00 ! -3:00 - ART 2001 Jun 17 0:00 ! -4:00 Arg AR%sT # # Cordoba (CB), Santiago del Estero (SE), Salta (SA), Tucuman (TM), La Rioja (LR), San Juan (SJ), San Luis (SL), # Neuquen (NQ), Rio Negro (RN) *************** *** 157,163 **** -3:00 Arg AR%sT 1990 Jul -3:00 - ART 1999 Oct 3 0:00 -4:00 Arg AR%sT 2000 Mar 3 0:00 ! -3:00 - ART # # Jujuy (JY) Zone America/Jujuy -4:21:12 - LMT 1894 Nov --- 166,173 ---- -3:00 Arg AR%sT 1990 Jul -3:00 - ART 1999 Oct 3 0:00 -4:00 Arg AR%sT 2000 Mar 3 0:00 ! -3:00 - ART 2001 Jun 17 0:00 ! -4:00 Arg AR%sT # # Jujuy (JY) Zone America/Jujuy -4:21:12 - LMT 1894 Nov *************** *** 170,176 **** -4:00 - WART 1992 Oct 18 -3:00 - ART 1999 Oct 3 0:00 -4:00 Arg AR%sT 2000 Mar 3 0:00 ! -3:00 - ART # # Catamarca (CT) Zone America/Catamarca -4:23:08 - LMT 1894 Nov --- 180,187 ---- -4:00 - WART 1992 Oct 18 -3:00 - ART 1999 Oct 3 0:00 -4:00 Arg AR%sT 2000 Mar 3 0:00 ! -3:00 - ART 2001 Jun 17 0:00 ! -4:00 Arg AR%sT # # Catamarca (CT) Zone America/Catamarca -4:23:08 - LMT 1894 Nov *************** *** 182,188 **** -3:00 Arg AR%sT 1992 Jul -3:00 - ART 1999 Oct 3 0:00 -4:00 Arg AR%sT 2000 Mar 3 0:00 ! -3:00 - ART # # Mendoza (MZ) Zone America/Mendoza -4:35:16 - LMT 1894 Nov --- 193,200 ---- -3:00 Arg AR%sT 1992 Jul -3:00 - ART 1999 Oct 3 0:00 -4:00 Arg AR%sT 2000 Mar 3 0:00 ! -3:00 - ART 2001 Jun 17 0:00 ! -4:00 Arg AR%sT # # Mendoza (MZ) Zone America/Mendoza -4:35:16 - LMT 1894 Nov *************** *** 195,201 **** -4:00 - WART 1992 Oct 18 -3:00 - ART 1999 Oct 3 0:00 -4:00 Arg AR%sT 2000 Mar 3 0:00 ! -3:00 - ART # Aruba # Zone NAME GMTOFF RULES FORMAT [UNTIL] --- 207,214 ---- -4:00 - WART 1992 Oct 18 -3:00 - ART 1999 Oct 3 0:00 -4:00 Arg AR%sT 2000 Mar 3 0:00 ! -3:00 - ART 2001 Jun 17 0:00 ! -4:00 Arg AR%sT # Aruba # Zone NAME GMTOFF RULES FORMAT [UNTIL]

1 1

strftime("%Z") invalidated by TZ change: is this a fair restriction?
by Jonathan Lennox June 12, 2001

June 12, 2001

This is an issue that occured to me in the process of converting tzcode to support my proposed thread-safe API. I think the following restriction is necessary to the POSIX 200x spec. If a 'struct tm' broken-down time structure is created by localtime() or localtime_r(), or modified by mktime(), and the value of the "TZ" environment variable is subsequently modified, the results of the %Z and %z strftime() and wcsftime() conversion specifiers are undefined, when strftime() or wcsftime() is called with such a broken-down time structure. If the broken-down time structure is subsequently modified by a successful call to mktime(), the results of these conversion specifiers are once again defined. If a 'struct tm' broken-down time structure is modified by gmtime(), it is implementation-defined whether the result of the %Z and %z strftime() and wcsftime() conversion specifiers shall refer to UTC or the current local time zone, when strftime() or wcsftime() is called with such a broken-down time structure. I think it's too late to get this restriction into the Austin Group revised POSIX spec, but some version of it probably ought to go into the tzcode man pages (along with documentation of what tzcode does for the second case, which is dependent on the value of TM_ZONE and TM_GMTOFF at compile-time). The motivating example for the first two paragraphs is the code attached below (test-tzchange.c). It produces the following output on FreeBSD 4.3 (which uses a slightly old version of tzcode, with some local changes that shouldn't affect this; it defines TM_ZONE and TM_GMTOFF): $ ./test-tzchange Fri 04 May 11:11:00 2001 EDT Fri 04 May 11:11:00 2001 PPT Fri 04 May 11:11:00 2001 PDT This occurs because lclptr->chars has a different value for the two time zones; since test_tm->tm_zone is a pointer into lclptr->chars, it ends up pointing somewhere bogus, and thus claiming that "Pacific Peace Time" was used in 2001. I don't think it's possible to fix this in tzcode without either breaking binary compatibility of 'struct tm', leaking memory on a TZ change, or breaking %Z for non-current time zones. The motivating example for the third paragraph is that System V (at least Solaris) and tzcode do different things, and I don't think either one is about to change. (System V always gets its %Z from tzname[i], I think.) The underlying motivation for all this is that I don't see any sensible way to set tm_zone, for struct tm's produced by reentrant timezone functions, that doesn't end up leading to free pointer dereferences following tz_free(). However, if the analogous operation for process-wide timezones is *already* undefined, it's clearly not nearly as much of a problem. What do people think about this? #include <stdio.h> #include <time.h> #include <stdlib.h> /* #define OLD_NAMES */ #ifdef OLD_NAMES /* Define this on Solaris */ #define FIRST_NAME "US/Eastern" #define SECOND_NAME "US/Pacific" #else /* Proper Olson tzdata names. */ #define FIRST_NAME "America/New_York" #define SECOND_NAME "America/Los_Angeles" #endif int main() { struct tm* test_tm; time_t then = 988989060; char buf[256]; /* Compatibility names are used, rather than new Olson names, so as to * test on Solaris. */ if (putenv("TZ=" FIRST_NAME) != 0) { fprintf(stderr, "putenv failed (1)\n"); exit(1); } if ((test_tm = localtime(&then)) == NULL) { fprintf(stderr, "localtime failed\n"); exit(1); } if (strftime(buf, sizeof(buf), "%a %d %h %H:%M:%S %Y %Z", test_tm) == 0) { fprintf(stderr, "strftime failed (1)\n"); exit(1); } printf("%s\n", buf); if (putenv("TZ=" SECOND_NAME) != 0) { fprintf(stderr, "putenv failed (2)\n"); exit(1); } tzset(); if (strftime(buf, sizeof(buf), "%a %d %h %H:%M:%S %Y %Z", test_tm) == 0) { fprintf(stderr, "strftime failed (2)\n"); exit(1); } printf("%s\n", buf); test_tm->tm_isdst = -1; if (mktime(test_tm) == -1) { fprintf(stderr, "mktime failed\n"); exit(1); } if (strftime(buf, sizeof(buf), "%a %d %h %H:%M:%S %Y %Z", test_tm) == 0) { fprintf(stderr, "strftime failed (3)\n"); exit(1); } printf("%s\n", buf); exit(0); } -- Jonathan Lennox lennox(a)cs.columbia.edu

2 1

Minimap of russian cities
by Jesper Nørgaard June 10, 2001

June 10, 2001

I thought you might like to have a mini-map of how the russian cities I mentioned, appears on the map of World Time Explorer: Regards, Jesper Nørgaard Welen Email: jnorgard(a)Prodigy.Net.mx Programador/Analista CIMMYT - Centro Internacional de Mejoramiento de Maíz y Trigo Dirección: CIMMYT Int. c/o Jesper Nørgaard Km. 45, Carretera México-Veracruz El Batán Texcoco, Edo. de México CP 56130 MEXICO Tel.: +52 (5) 58-04-20-04 ext. 1374 Fax: +52 (5) 58-04-75-58 Tel. Casa: 53-10-05-95 ó 53-10-97-78 CIMMYT home page: http://cimmyt.cgiar.org Check out my free program World Time Explorer: http://www20.Brinkster.com/timezone50/index.htm http://members.theglobe.com/timezone50/index.htm

1 0

Re: Proposal: API for thread-safe time zone functions
by Russ Allbery June 9, 2001

June 9, 2001

Garrett Wollman <wollman(a)khavrinen.lcs.mit.edu> writes: > (In the FreeBSD Project, and probably many other places, our coding > standard is very explicit: don't use typedefs for structures. This > deficiency in C is precisely the reason for making that requirement.) I'm completely with Garrett on this. Pointers to incomplete structs make *great* opaque datatypes in C; typedefs have considerably more problems and are really annoying to deal with. It's really a shame that FILE wasn't instead defined as a pointer to an incomplete struct, since the way it works right now, lots of headers that have no need whatsoever of all the crap in stdio.h have to include it solely because there's one function (which many callers may not even use) that takes a FILE * as an argument. -- Russ Allbery (rra(a)stanford.edu) <http://www.eyrie.org/~eagle/>

1 0

(no subject)
by Kim McGarghan June 8, 2001

June 8, 2001

unsubscribe

1 0

Change in DST for Argentina
by Syed Sajjath June 7, 2001

June 7, 2001

Hi, Is anyone aware of changes in Argentina to add Daylight Savings. One of my contacts sent the following information. From TZ database, Argentina is GMT -3 and no DST. >> With this, timezone for Argentina will be modified as follows: >> from 1st Sunday October until first Saturday March: GMT -3 >> from 1st Sunday Martch until first Saturday October: GMT -4 Thanks -Syed

2 1

Dave Wilson: Drowning in a Sea of Clocks
by Paul Eggert June 7, 2001

June 7, 2001

In yesterday's Los Angeles Times, Dave Wilson wrote a humorous piece "Drowning in a Sea of Clocks" complaining about the number of clocks he has to change every spring and fall. He goes on: Like all good paranoid fantasies, mine has a villain: the Japanese. Japanese electronics designers have been deliberately building clocks into everything in hopes of weakening our industrial might. Now, you might say, "Dave, that's crazy talk. The Japanese have a lot more of these gadgets than we do. They're gadget freaks, man. They'd be hurt by this as much as we are, or even more." Which shows how much you know, pal. The Japanese don't have daylight saving time. He finally resolves to disable all his clocks that serve no function. (His oven clock now blinks 00:00.) See: http://www.latimes.com/business/cutting/20010405/t000029080.html

2 1

Additional Greenland time zone
by Gwillim Law June 6, 2001

June 6, 2001

Does anyone out there speak Norwegian or Danish? The tz database lists only three time zones for Greenland, with standard time equal to UTC-1, UTC-3, and UTC-4. Some recent time zone maps (e.g. <http://www.hammondmap.com/timezone/maintz.html>) show a fourth time zone in northeast Greenland with UTC as its standard time. Doing some Internet research, I found a document, "Notices to Mariners", in Norwegian and English, at <http://www.statkart.no/efs/efshefter/2001/efs5-2001.pdf>. The following excerpt obviously has a good deal of useful information, but appears in Norwegian only. "220. (T). Grønland. Sommertid 2001. Sommertiden begjynner den 24. mars 2001. Grønland har 4 lokale tider, og i relasjon til UTC gjelder følgende tidslinje: Forsvarsområdetved Thule UTC-4 Grønlandsk normaltid UTC-3 Scoresby-sund UTC-1 Danmarks-havn UTC Danmark (Mellem-europæisk tid) UTC+1 Sommertid innføres som følger: 1. Grønlandsk normaltid: Den 24. mars 2001 kl. 2200 stilles uret frem til kl. 2300. 2. Scoresbysund: Den 25. mars 2001 kl. 0000 stilles uret frem til kl. 0100. 3. I forsvarsområdet ved Thule samt i Danmarkshavn innføres det ikke sommertid." What I make of this is: Greenland Summer time begins on 24 March 2001. Greenland has four local times, and the relation to UTC is according to the following time line: [the following five items are aligned horizontally] Thule and environs [?] UTC-4 Standard Greenland time UTC-3 Scoresbysund UTC-1 Danmarkshavn UTC Denmark (Central European Time) UTC+1 Summer time [...?] 1. Standard Greenland time: on 24 March 2001 at 22:00 change the clock to 23:00 [?] 2. Scoresbysund: on 25 March 2001 at 00:00 change the clock to 01:00 3. In the environs of Thule together with Danmarkshavn [...?]." Here's an excerpt from another page <http://www.gh.gl/kn/news/govern/ukiunalun.htm>, probably in Danish: "Vintertid fra på søndag den 31. oktober Uret stilles en time tilbage Natten mellem lørdag og søndag den 31. oktober 1999 slutter sommertiden. Der skiftes officielt lørdag den 30. oktober 1999 kl. 23:00. Det betyder, at vi kl. 23:00 stiller klokken en time tilbage til kl. 22:00. For Ittoqqortoormiit slutter sommertiden søndag den 31. oktober 1999 kl. 01:00, hvor klokken stilles een time tilbage til kl. 00:00. For Danmarkshavn og i forsvarsområdet i Pituffik er der ikke indført sommertid/vintertid." It looks as if this means that in most of Greenland, the clock turned back from 30 October 1999 23:00 to 22:00. In Ittoqqortoormiit (= Scoresbysund), it went from 31 October 1999 01:00 to 00:00. In Danmarkshavn and Pituffik (= Thule), something else happened, but I can't tell what. There are similar texts on <http://www.statkart.no/efs/efshefter/2000/efs5-2000.pdf>, <http://www.gh.gl/dk/nyheder/regering/2000/meddelt1610-2.htm>, and <http://www.epr.gl/government/dk_pressrel/160301_sommertid.html>. It looks as if they're all paraphrased from official Greenland press releases. Can anyone translate the rest, or fill in any more details? Gwillim Law

2 1

RE: [akr@m17n.org: bin/27630: mktime problem.]
by Olson, Arthur David (NCI) June 5, 2001

June 5, 2001

Garrett's analysis of the cause of the Africa/Monrovia problem is accurate (see the end of this message). The conservative approach to fixing the problem would be as shown just below. The more radical approach would be to ditch the saved_seconds hackery completely; it predates the conditional normalize_overflow(&yourtm.tm_min, &yourtm.tm_sec, SECSPERMIN) call that now appears in the code, which should do what the saved_seconds hackery was designed to do. --ado *** 7.73/localtime.c Tue Jun 5 14:04:57 2001 --- 7.74/localtime.c Tue Jun 5 14:04:57 2001 *************** *** 1383,1389 **** } if (increment_overflow(&yourtm.tm_year, -TM_YEAR_BASE)) return WRONG; ! if (yourtm.tm_year + TM_YEAR_BASE < EPOCH_YEAR) { /* ** We can't set tm_sec to 0, because that might push the ** time below the minimum representable time. --- 1383,1391 ---- } if (increment_overflow(&yourtm.tm_year, -TM_YEAR_BASE)) return WRONG; ! if (yourtm.tm_sec >= 0 && yourtm.tm_sec < SECSPERMIN) ! saved_seconds = 0; ! else if (yourtm.tm_year + TM_YEAR_BASE < EPOCH_YEAR) { /* ** We can't set tm_sec to 0, because that might push the ** time below the minimum representable time. -----Original Message----- From: Garrett Wollman [mailto:wollman@khavrinen.lcs.mit.edu] Sent: Friday, May 25, 2001 2:01 PM To: tz(a)elsie.nci.nih.gov Subject: [akr(a)m17n.org: bin/27630: mktime problem.] A FreeBSD user submitted the following bug report. I'm curious as to whether the current tzcode still has this problem. My analysis follows at the end. -GAWollman ... For example, TZ=Africa/Monrovia, 1972/05/01 00:44:30 cannot be converted to time_t. Since this example is taken from `zdump -v Africa/Monrovia' and it is after Epoch, there is no reason to fail. ... This problem appears to result from the `saved_seconds' hackery in time2(): saved_seconds = yourtm.tm_sec; yourtm.tm_sec = 0; time2() then goes on to attempt to find (in this example) 1972-05-01T00:44:00, which does not exist in this time zone, and returns failure.

1 0

tzcode2001c.tar.gz and tzdata2001.tar.gz
by Olson, Arthur David (NCI) June 5, 2001

June 5, 2001

The files ftp://elsie.nci.nih.gov/pub/tzcode2001c.tar.gz and ftp://elsie.nci.nih.gov/pub/tzdata2001c.tar.gz are now available. These incorporate the changes circulated last week on the time zone mailing list by Paul Eggert and Andrew Brown. --ado

1 0

[The Times 2001-06-02] Timezone cheats using Net for exams
by Joseph S. Myers June 2, 2001

June 2, 2001

From Saturday's Times: SATURDAY JUNE 02 2001 Timezone cheats using Net for exams BY GLEN OWEN, EDUCATION CORRESPONDENT, AND LAURA PEEK IN WASHINGTON A GLOBAL network of timezone cheats has been established on the Internet to pass examination secrets between candidates. Overseas students, who start the same papers at staggered intervals because of international time differences, are corresponding with candidates who have already finished their exams. The English examination boards alerted to the scam by The Times, have promised to review procedures, and warn that any candidate found cheating will be disqualified. One board admitted that the growth of Internet use and mobile text messaging presented a significant twist to an old problem. Schools in Brazil, Bermuda, the USA and Canada, also contacted by The Times yesterday, said they would be reviewing examination procedures to prevent time-zone cheating. [ ... - for full article see Times website: ] http://www.thetimes.co.uk/article/0,,2-2001190449,00.html http://www.thetimes.co.uk/article/0,,59-2001190216,00.html -- Joseph S. Myers jsm28(a)cam.ac.uk

1 0

(no subject)
by USMCGRANDMOTHER＠aol.com June 2, 2001

June 2, 2001

1 0

RE: proposed tz changes for Mongolia, Jan Mayen, Chagos, Indonesia, etc.
by Jesper Nørgaard June 1, 2001

June 1, 2001

A few comments on the proposed tz changes ... Check out my free program World Time Explorer: http://www20.Brinkster.com/timezone50/index.htm ---------- From: Paul Eggert[SMTP:eggert@twinsun.com] Sent: Jueves 31 de Mayo de 2001 3:00 To: tz(a)elsie.nci.nih.gov Subject: proposed tz changes for Mongolia, Jan Mayen, Chagos, Indonesia, etc. >Here are proposed changes to the tz code and data. The most pressing >ones are those for Mongolia, Jan Mayen, and Chagos, as the current UTC >offsets are incorrect. Also, these changes affect the current time >zone abbreviations for Indonesia. >* Jan Mayen observes Oslo time, not -01:00. Also, add commentary about > time in Svalbard and Jan Mayen since 1925. > (Thanks to Steffen Thorsen for this.) Actually I would have liked to take credit for that, at least the first part, but I don't deny that Steffen is the expert (by birth, I presume) of norwegian issues :-) ... >* Southwest Borneo switched from +08:00 to +07:00 on 1988-01-01. > This entails a new zone 'Asia/Pontianak'. > (Thanks to Gwillim Law for this.) Funny, I had it all along right under my nose without noticing it. I send a screenshot from my program World Time Explorer which shows the region. And the line down the middle of Borneo from Malaysia actually *is* a time zone border - I just hadn't realized it, since the line towards Malaysia is a country border, not a time zone border. Can anyone confirm that Palangkaray (with population 148,700 latitude -2.19 and longitude 113.82) is also on GMT+7 just like Pontianak, and that Bandjarmasin (with population 534,600 and latitude -3.34, longitude 114.57) is on GMT+8? The screenshot I send is BorneoSouthWest.gif. The map was developed by Manifold, check out http://www.manifold.net/download/freemaps.html. >* Time Zone Converter has moved. The new name will be World Time Explorer 1.6 further down on page http://www20.brinkster.com/timezone50/index.htm you can find 3 download buttons for this program, which has maps included from which the graphic that I attach to the mail were taken. Note that it's a beta version, mainly because I want to put some more functionality into the program before releasing it officially, but also because the help file is not up-to-date at all. But the existing functions should work. Note that you can take a snapshot of world time from all distinct time zones in Time Calculator. And by the way, you need a Windows computer to use it ... Regards Jesper Nørgaard Welen

2 1

proposed tz changes for Mongolia, Jan Mayen, Chagos, Indonesia, etc.
by Paul Eggert May 31, 2001

May 31, 2001

Here are proposed changes to the tz code and data. The most pressing ones are those for Mongolia, Jan Mayen, and Chagos, as the current UTC offsets are incorrect. Also, these changes affect the current time zone abbreviations for Indonesia. The other changes cover historical data, minor porting glitches for the code, and the web page describing tz. As usual, thanks to everyone who wrote in; it couldn't be done without you! Code changes * Add support for non-POSIX systems that lack sys/stat.h. * Add instructions for OSF1 V5.0 cc (which mishandles 'const'). Data changes * Mongolia observes DST this year, from 04-27 02:00 to 09-28 03:00. (Thanks to Rives McDow for this.) * Jan Mayen observes Oslo time, not -01:00. Also, add commentary about time in Svalbard and Jan Mayen since 1925. (Thanks to Steffen Thorsen for this.) * The British Indian Ocean Territory (Indian/Chagos) seems to have switched from +05:00 to +06:00; for lack of better info, we'll guess that it occurred on 1996-01-01. * The English abbreviations for the current time zones in Indonesia are WIT, CIT, and EIT (not JAVT, BORT, JAYT which were purely guesswork on my part). Thanks to Gwillim Law for pointing me at a web page that had an (incorrect) translation about this. * Southwest Borneo switched from +08:00 to +07:00 on 1988-01-01. This entails a new zone 'Asia/Pontianak'. (Thanks to Gwillim Law for this.) * Shanks now says that Mongolia didn't introduce DST until 1983. * Chile introduced DST in 1966, not 1969. (Thanks to Gwillim Law for this.) * Fixes for legal time in the Netherlands before 1938: - From 1918 through 1921 DST ended the last Monday in September, not the last Sunday. - Amsterdam Mean Time was +00:19:32.13 until 1937-07-01. The tz database can't represent the ".13", unfortunately. - Add commentary about legal time in the Netherlands before 1937. (Thanks to Robert H. van Gent for this.) * Fixes for legal time in Sweden before 1917: - Sweden adopted standard time on 1879-01-01, not 1878-05-31. - Standard time was +1:00:14, not +1:12:12. - The switch to +1:00 occurred on 1900-01-01 at 00:00, not at 01:00. - 1916 DST was from 05-14 23:00 to 10-01 01:00, not from 04-14 23:00 to 10-01 00:00. (Thanks to Ivan Nilsson for this.) * Change zone.tab entry to say that Sala y Gomez is like Easter Island, while the other Chilean locations are all like Santiago. (Thanks to Gwillim Law for this.) Changes that affect commentary only. * Add brief instructions for how to retrieve, build and test tz. * Add more commentary for Choibalsan, Mongolia, which may or may not be in a different time zone from Ulaanbaatar. (Thanks to Rives McDow for this.) * Add more commentary about why the Antarctica/Vostok entry is guesswork. (Thanks to Lee Hotz for this.) * Fix the spelling of "Attlee". (Thanks to Mark Brader for this.) * Add commentary for Villa Las Estrellas, the only town in the Antarctic. * Add commentary for the islands of Aldabra, Farquhar, and Desroches, which were transferred from the British Indian Ocean Territory to the Seychelles in 1976. * Add remarks about why Alaska's switch from Julian to Gregorian is somewhat notional, as none of the locations currently in the tz database were permanently inhabited in 1867 by anyone using either calendar. * Remove commentary about Brad Sherman's attempt to let California operate on Denver time, as it's too hard to keep track of all the legislative proposals right now. * Navassa is now administered by the US Fish and Wildlife Service. Changes that affect the web page tz-link.htm only. * Use family name first in the Dublin Core metadata, as the standard recommends. * Mention Tru64, which uses tz too. * Change <samp> to <code> in tz-link.htm, as that better matches what's being represented. * Time Zone Converter has moved. * World Time Server no longer publishes maps (that I could see, anyway). * Mention http://www.dstc.qut.edu.au/DST/marg/daylight.html, which is more useful than the official page http://www.lawlink.nsw.gov.au/crd.nsf/pages/time2 for Australia. * Mention http://www.nrc.ca/inms/time/tze.html for Canada. * Translate the title of http://www.phys.uu.nl/~vgent/wettijd/wettijd.htm from Dutch to English. (Thanks to Robert H. van Gent for this.) * Mention the SOFA code. (Thanks to Markus Kuhn for this.) * The International Earth Rotation Service's web site has moved. * ISO 8601 has been updated; the current version is ISO 8601:2000. (Thanks to Markus Kuhn for this.) * Mention Internet RFC 2822 and draft-ietf-impp-datetime-03.txt. =================================================================== RCS file: RCS/README,v retrieving revision 1997.7 retrieving revision 1997.7.0.1 diff -pu -r1997.7 -r1997.7.0.1 --- README 1997/09/04 20:55:54 1997.7 +++ README 2001/05/31 00:59:05 1997.7.0.1 @@ -33,8 +33,22 @@ Since POSIX frowns on correct leap secon the "zic" command (in the absence of a "-L" option) has been changed to omit leap second information from its output files. -Be sure to read the comments in "Makefile" and make any changes -needed to make things right for your system. +Here is a recipe for acquiring, building, installing, and testing the +tz distribution on a GNU/Linux or similar host. + + mkdir tz + cd tz + wget 'ftp://elsie.nci.nih.gov/pub/tz*.tar.gz' + gzip -dc tzcode*.tar.gz | tar -xf - + gzip -dc tzdata*.tar.gz | tar -xf - + +Be sure to read the comments in "Makefile" and make any changes needed +to make things right for your system, especially if you are using some +platform other than GNU/Linux. Then run the following commands, +substituting your desired installation directory for "$HOME/tzdir": + + make TOPDIR=$HOME/tzdir install + $HOME/tzdir/etc/zdump -v America/Los_Angeles To use the new functions, use a "-ltz" option when compiling or linking. =================================================================== RCS file: RCS/tz-link.htm,v retrieving revision 2001.2 retrieving revision 2001.2.0.2 diff -pu -r2001.2 -r2001.2.0.2 --- tz-link.htm 2001/04/05 20:43:41 2001.2 +++ tz-link.htm 2001/05/31 03:53:40 2001.2.0.2 @@ -1,5 +1,5 @@ <?xml version="1.0" encoding="US-ASCII"?> -<!DOCTYPE html +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> @@ -7,9 +7,9 @@ <title>Sources for Time Zone and Daylight Saving Time Data</title> <link rel="schema.DC" href="http://purl.org/DC/elements/1.1/" /> <meta http-equiv="Content-type" content='text/html; charset="US-ASCII"' /> -<meta name="DC.Creator" content="Paul Eggert" /> -<meta name="DC.Contributor" content="Arthur David Olson" /> -<meta name="DC.Date" content="2000/10/03" /> +<meta name="DC.Creator" content="Eggert, Paul" /> +<meta name="DC.Contributor" content="Olson, Arthur David" /> +<meta name="DC.Date" content="2001-05-30" /> <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" /> @@ -25,14 +25,14 @@ Please send corrections to this web page to the <a href="mailto:tz@elsie.nci.nih.gov">time zone mailing list</a>. </p> -<h2>The <samp>tz</samp> database</h2> +<h2>The <code>tz</code> database</h2> <p> The public-domain time zone database contains code and data that represent the history of local time for many representative locations around the globe. It is updated periodically to reflect changes made by political bodies to UTC offsets and daylight-saving rules. -This database (often called <samp>tz</samp> or <samp>zoneinfo</samp>) +This database (often called <code>tz</code> or <code>zoneinfo</code>) is used by several implementations, including <a href="http://www.linux.org/">GNU/Linux</a>, @@ -43,17 +43,30 @@ including <a href="http://unix.hp.com/operating/">HP-UX</a>, <a href="http://www.sgi.com/developers/technology/irix.html">IRIX</a>, <a href="http://www.sco.com/products/openserver/">SCO OpenServer</a>, -<a href="http://www.sun.com/solaris/">Solaris</a>, and -<a href="http://www.sco.com/unixware/">UnixWare</a>. -In the <samp>tz</samp> database's +<a href="http://www.sun.com/solaris/">Solaris</a>, +<a href="http://www.tru64unix.compaq.com/">Tru64</a>, and +<a href="http://www.sco.com/unixware/">UnixWare</a>.</p> +<p> +In the <code>tz</code> database's <a href="ftp://elsie.nci.nih.gov/pub/">FTP distribution</a>, -the code is in the file <samp>tzcode<var>C</var>.tar.gz</samp>, -where <samp><var>C</var></samp> is the code's version; -similarly, the data are in <samp>tzdata<var>D</var>.tar.gz</samp>, -where <samp><var>D</var></samp> is the data's version. -The code lets you compile the <samp>tz</samp> source files into +the code is in the file <code>tzcode<var>C</var>.tar.gz</code>, +where <code><var>C</var></code> is the code's version; +similarly, the data are in <code>tzdata<var>D</var>.tar.gz</code>, +where <code><var>D</var></code> is the data's version. +The following shell commands use <a +href="http://www.gnu.org/software/wget/">GNU wget</a> to download +these files to a GNU/Linux or similar host; see the downloaded +<code>README</code> file for what to do next.</p> +<pre style="margin-left: 2em"><code>mkdir tz +cd tz +wget 'ftp://elsie.nci.nih.gov/pub/tz*.tar.gz' +gzip -dc tzcode*.tar.gz | tar -xf - +gzip -dc tzdata*.tar.gz | tar -xf - +</code></pre> +<p> +The code lets you compile the <code>tz</code> source files into machine-readable binary files, one for each location. It also lets -you read a <samp>tz</samp> binary file and interpret time stamps for that +you read a <code>tz</code> binary file and interpret time stamps for that location.</p> <p> The data are by no means authoritative. If you find errors, please @@ -68,7 +81,7 @@ format).</p> The Web has several other sources for time zone and daylight saving time data. Here are some recent links that may be of interest. </p> -<h2>Web pages using recent versions of the <samp>tz</samp> database</h2> +<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 @@ -91,19 +104,19 @@ time zone converter</a> is a multilingua holidays.</li> <li><a href="http://www.timeanddate.com/worldclock/">The World Clock</a> is a web interface to a time zone database derived from -<samp>tz</samp>'s.</li> +<code>tz</code>'s.</li> </ul> -<h2>Other <samp>tz</samp> compilers</h2> +<h2>Other <code>tz</code> compilers</h2> <ul> <li><a href="http://www.karuna.freeserve.co.uk/vzic.tgz">Vzic</a> -compiles <samp>tz</samp> source into VTIMEZONE text as specified by +compiles <code>tz</code> source into VTIMEZONE text as specified by the <a href="ftp://ftp.isi.edu/in-notes/rfc2445.txt">iCalendar</a> specification published by the <a href="http://www.ietf.org/html.charters/calsch-charter.html">IETF Calendaring and Scheduling Working Group</a>. Vzic is freely available under the <a href="http://www.gnu.org/copyleft/gpl.html">GNU General Public License (GPL)</a>.</li> -<li>Possible XML schemata for the <samp>tz</samp> data include <a +<li>Possible XML schemata for the <code>tz</code> data include <a href="http://www.w3.org/2000/01/foo">one</a> sketched out by <a href="http://www.w3.org/People/Berners-Lee/">Tim Berners-Lee</a> and <a @@ -112,27 +125,27 @@ used by the <a href="http://www.iplanet.com/products/iplanet_calendar/">iPlanet Calendar Server</a>.</li> </ul> -<h2>Other <samp>tz</samp> binary file readers</h2> +<h2>Other <code>tz</code> binary file readers</h2> <ul> <li>The <a href="http://www.gnu.org/software/libc/">GNU C Library</a> has an independent, thread-safe implementation of -a <samp>tz</samp> binary file reader. +a <code>tz</code> binary file reader. This library is freely available under the <a href="http://www.gnu.org/copyleft/lesser.html"> GNU Lesser General Public License (LGPL)</a>, and is widely used in GNU/Linux systems.</li> <li><a href="http://www.bmsi.com/java/#TZ">ZoneInfo.java</a> -is a <samp>tz</samp> binary file reader written in Java. +is a <code>tz</code> binary file reader written in Java. It is freely available under the GNU LGPL.</li> </ul> -<h2>Other <samp>tz</samp>-based time zone conversion software</h2> +<h2>Other <code>tz</code>-based time zone conversion software</h2> <ul> <li><a href="http://www1.tip.nl/~t876506/AboutTimeZonesHC.html">HyperCard time zones calculator</a> is a HyperCard stack.</li> <li><a -href="http://timezone50.homepage.com/">Time Zone Converter</a> is a -Microsoft Windows 95/98/NT4 program.</li> +href="http://www20.Brinkster.com/timezone50/">Time Zone Converter</a> is a +Microsoft Windows program.</li> </ul> <h2>Other time zone databases</h2> <ul> @@ -146,10 +159,12 @@ href="http://astrocom.com/">Astro Commun time info, public holidays</a> contains information on local time, sunrise and sunset, and public holidays in several hundred cities around the world.</li> +<li><a href="http://www.worldtimeserver.com/">World Time Server</a> +is another time zone database.</li> <li><a href="http://tycho.usno.navy.mil/tzones.html">World Time Zones</a> contains data from the Time Service Department of the US Naval Observatory (USNO), used as the source -for the <samp>usno*</samp> files in the <samp>tz</samp> distribution.</li> +for the <code>usno*</code> files in the <code>tz</code> distribution.</li> <li>The <a href="http://www.iata.org/">International Air Transport Association</a> publishes the <a href="http://www.iata.org/sked/ssim.htm">Standard @@ -166,7 +181,7 @@ zone map</a>; the <a href="http://www.lib.utexas.edu/Libs/PCL/Map_collection/world_maps.html"> Perry-Castañeda Library Map Collection</a> of the University of Texas at Austin has copies of -recent editions. +recent editions. The pictorial quality is good, but the maps do not indicate summer time, and parts of the data are a few years out of date.</li> @@ -175,9 +190,6 @@ current time</a> has several fancy time zone maps; it covers Russia particularly well. The maps' pictorial quality is not quite as good as the CIA's but the maps are more up to date.</li> -<li><a href="http://www.worldtimeserver.com/">World Time Server</a> -has a separate little outline map for each region of each country that -currently observes a different time.</li> </ul> <h2>Time zone boundaries</h2> <ul> @@ -210,15 +222,20 @@ time zone boundary.</li> <li>A few countries have well-documented histories of legal time. <dl> <dt>Australia</dt> -<dd>The Community Relations Division of the NSW Attorney General's -Department maintains a history of <a -href="http://www.lawlink.nsw.gov.au/crd.nsf/pages/time2">daylight -saving in New South Wales</a>.</dd> +<dd><a +href="http://www.dstc.qut.edu.au/DST/marg/daylight.html#more">Australia's +Daylight Saving Times</a> contains pointers to government records and to +histories of daylight saving.</dd> <dt>Brazil</dt> <dd>The Time Service Department of the National Observatory records <a href="http://pcdsh01.on.br/DecHV.html" hreflang="pt-BR">Brazil's daylight saving time decrees (in Portuguese)</a>.</dd> +<dt>Canada</dt> +<dd>The Institute for National Measurement Standards publishes current +and some older information about <a +href="http://www.nrc.ca/inms/time/tze.html">Time Zones and Daylight +Saving Time</a>.</dd> <dt>Germany</dt> <dd>The National Institute for Science and Technology maintains the <a href="http://www.ptb.de/english/org/4/43/432/lega.htm">Realisation of @@ -234,7 +251,7 @@ href="http://www.cddhcu.gob.mx/bibliot/p hreflang="es">history of Mexican local time (in Spanish)</a>.</dd> <dt>Netherlands</dt> <dd><a href="http://www.phys.uu.nl/~vgent/wettijd/wettijd.htm" -hreflang="nl">De wettelijke tijdregeling in Nederland (in Dutch)</a> +hreflang="nl">Legal time in the Netherlands (in Dutch)</a> covers the history of local time in the Netherlands from ancient times.</dd> <dt>United Kingdom</dt> <dd><a @@ -259,22 +276,28 @@ answers questions like "What is the diff href="http://sadira.gb.nrao.edu/~rfisher/Ephemerides/times.html">Astronomical Times</a> explains more abstruse astronomical time scales like TT, TCG, and TDB.</li> +<li>The <a href="http://www.iau.org/">IAU</a>'s <a +href="http://www.iau-sofa.rl.ac.uk/">Standards Of Fundamental +Astronomy</a> (SOFA) initiative publishes Fortran code for converting +among time scales like TAI, TDB, TT and UTC.</li> <li><a href="http://www.jpl.nasa.gov/basics/bsf2-3.htm">Basics of Space Flight - Reference Systems - Time Conventions</a> briefly explains interplanetary space flight timekeeping.</li> -<li><a href="http://hpiers.obspm.fr/webiers/results/bul/README.html">Bulletins -of IERS</a> contains official publications of the +<li><a +href="http://hpiers.obspm.fr/eop-pc/products/bulletins.html">Bulletins +maintained by the IERS EOP (PC)</a> contains official publications of +the Earth Orientation Parameters Product Center of the International Earth Rotation Service, the committee that decides when leap seconds occur.</li> <li>The <a href="http://clockdev.usno.navy.mil/archives/leapsecs.html">Leap Second Discussion List</a> covers <a href="http://clockdev.usno.navy.mil/cgi-bin/wa.exe?A3=ind00&L=leapsecs&P=…">McCarthy -and Klepczynski's proposal to remove leap seconds</a> +and Klepczynski's proposal to discontinue leap seconds</a> (which requires discussion list membership to read). This proposal is being studied by the URSI Commission J <a href="http://space.mit.edu/URSI/leapsecond.html">Working Group on the -Leap Second</a>, and the <a href="http://www.iau.org/">IAU</a> +Leap Second</a>, and the IAU has plans to report on this proposal by 2003.</li> </ul> <h2>Time notation</h2> @@ -284,7 +307,18 @@ has plans to report on this proposal by the International Standard Date and Time Notation</a> is a good summary of <a href="http://www.iso.ch/markete/8601.pdf">ISO 8601:1988 - Data elements and interchange formats - Information interchange -- Representation of dates and times</a>.</li> +- Representation of dates and times</a> (which has been superseded by +<a href="http://www.iso.ch/cate/d26780.html">ISO 8601:2000</a>).</li> +<li> +Section 3.3 of <a +href="ftp://ftp.isi.edu/in-notes/rfc2822.txt">Internet RFC 2822</a> +specifies the time notation used in email and <a +href="ftp://ftp.isi.edu/in-notes/rfc2616.txt">HTTP</a> headers.</li> +<li> +<a +href="ftp://ftp.isi.edu/internet-drafts/draft-ietf-impp-datetime-03.txt">Date +and Time on the Internet: Timestamps</a> proposes an ISO 8601 profile +for use in new Internet protocols.</li> </ul> <h2>Related indexes</h2> <ul> =================================================================== RCS file: RCS/Makefile,v retrieving revision 2001.2 retrieving revision 2001.2.0.1 diff -pu -r2001.2 -r2001.2.0.1 --- Makefile 2001/04/05 20:43:41 2001.2 +++ Makefile 2001/05/31 00:59:05 2001.2.0.1 @@ -86,6 +86,7 @@ YEARISTYPE= ./yearistype LDLIBS= # Add the following to the end of the "CFLAGS=" line as needed. +# -Dconst= if `const' does not work (SunOS 4.x cc, OSF1 V5.0 cc) # -DHAVE_ADJTIME=0 if `adjtime' does not exist (SVR0?) # -DHAVE_GETTEXT=1 if `gettext' works (GNU, Linux, Solaris); also see LDLIBS # -DHAVE_INCOMPATIBLE_CTIME_R=1 if your system's time.h declares @@ -97,6 +98,7 @@ LDLIBS= # -DHAVE_SETTIMEOFDAY=3 if settimeofday ignores 2nd arg (4.4BSD) # -DHAVE_STRERROR=0 if your system lacks the strerror function # -DHAVE_SYMLINK=0 if your system lacks the symlink function +# -DHAVE_SYS_STAT_H=0 if your compiler lacks a "sys/stat.h" # -DHAVE_SYS_WAIT_H=0 if your compiler lacks a "sys/wait.h" # -DLOCALE_HOME=\"path\" if locales are in "path", not "/usr/lib/locale" # -DHAVE_UNISTD_H=0 if your compiler lacks a "unistd.h" (Microsoft C++ 7?) =================================================================== RCS file: RCS/private.h,v retrieving revision 2000.5 retrieving revision 2000.5.0.1 diff -pu -r2000.5 -r2000.5.0.1 --- private.h 2000/07/31 13:27:54 2000.5 +++ private.h 2001/05/31 00:59:05 2000.5.0.1 @@ -54,6 +54,10 @@ static char privatehid[] = "@(#)private. #define HAVE_SYMLINK 1 #endif /* !defined HAVE_SYMLINK */ +#ifndef HAVE_SYS_STAT_H +#define HAVE_SYS_STAT_H 1 +#endif /* !defined HAVE_SYS_STAT_H */ + #ifndef HAVE_SYS_WAIT_H #define HAVE_SYS_WAIT_H 1 #endif /* !defined HAVE_SYS_WAIT_H */ @@ -123,16 +127,6 @@ static char privatehid[] = "@(#)private. */ /* -** SunOS 4.1.1 cc lacks const. -*/ - -#ifndef const -#ifndef __STDC__ -#define const -#endif /* !defined __STDC__ */ -#endif /* !defined const */ - -/* ** SunOS 4.1.1 cc lacks prototypes. */ =================================================================== RCS file: RCS/zic.c,v retrieving revision 2000.6 retrieving revision 2000.6.0.1 diff -pu -r2000.6 -r2000.6.0.1 --- zic.c 2000/08/10 13:31:47 2000.6 +++ zic.c 2001/05/31 00:59:05 2000.6.0.1 @@ -7,9 +7,15 @@ static char elsieid[] = "@(#)zic.c 7.101 #include "private.h" #include "locale.h" #include "tzfile.h" -#ifdef unix -#include "sys/stat.h" /* for umask manifest constants */ -#endif /* defined unix */ + +#if HAVE_SYS_STAT_H +#include "sys/stat.h" +#endif +#ifdef S_IRUSR +#define MKDIR_UMASK (S_IRUSR|S_IWUSR|S_IXUSR|S_IRGRP|S_IXGRP|S_IROTH|S_IXOTH) +#else +#define MKDIR_UMASK 0755 +#endif /* ** On some ancient hosts, predicates like `isspace(C)' are defined @@ -613,7 +619,7 @@ const char * const tofile; (void) exit(EXIT_FAILURE); result = link(fromname, toname); -#if (HAVE_SYMLINK - 0) +#if (HAVE_SYMLINK - 0) if (result != 0) { const char *s = tofile; register char * symlinkcontents = NULL; @@ -2187,7 +2193,7 @@ char * const argname; ** created by some other multiprocessor, so we get ** to do extra checking. */ - if (mkdir(name, S_IRUSR|S_IWUSR|S_IXUSR|S_IRGRP|S_IXGRP|S_IROTH|S_IXOTH) != 0) { + if (mkdir(name, MKDIR_UMASK) != 0) { const char *e = strerror(errno); if (errno != EEXIST || !itsdir(name)) { =================================================================== RCS file: RCS/africa,v retrieving revision 2000.7 retrieving revision 2000.7.0.1 diff -pu -r2000.7 -r2000.7.0.1 --- africa 2000/10/10 15:35:14 2000.7 +++ africa 2001/05/31 00:59:05 2000.7.0.1 @@ -481,6 +481,12 @@ Zone Africa/Dakar -1:09:44 - LMT 1912 # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Indian/Mahe 3:41:48 - LMT 1906 Jun # Victoria 4:00 - SCT # Seychelles Time +# From Paul Eggert (2001-05-30): +# Aldabra, Farquhar, and Desroches, originally dependencies of the +# Seychelles, were transferred to the British Indian Ocean Territory +# in 1965 and returned to Seychelles control in 1976. We don't know +# whether this affected their time zone, so omit this for now. +# Possibly the islands were uninhabited. # Sierra Leone # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S =================================================================== RCS file: RCS/antarctica,v retrieving revision 2001.2 retrieving revision 2001.2.0.1 diff -pu -r2001.2 -r2001.2.0.1 --- antarctica 2001/04/05 20:43:40 2001.2 +++ antarctica 2001/05/31 00:59:05 2001.2.0.1 @@ -39,8 +39,8 @@ Rule ArgAQ 1974 only - Jan 23 0:00 1:00 Rule ArgAQ 1974 only - May 1 0:00 0 - Rule ArgAQ 1974 1976 - Oct Sun<=7 0:00 1:00 S Rule ArgAQ 1975 1977 - Apr Sun<=7 0:00 0 - -Rule ChileAQ 1969 1997 - Oct Sun>=9 0:00 1:00 S -Rule ChileAQ 1970 1998 - Mar Sun>=9 0:00 0 - +Rule ChileAQ 1966 1997 - Oct Sun>=9 0:00 1:00 S +Rule ChileAQ 1967 1998 - Mar Sun>=9 0:00 0 - Rule ChileAQ 1998 only - Sep 27 0:00 1:00 S Rule ChileAQ 1999 only - Apr 4 0:00 0 - Rule ChileAQ 1999 max - Oct Sun>=9 0:00 1:00 S @@ -92,11 +92,13 @@ Zone Antarctica/Mawson 0 - zzz 1954 Feb # Brazil - year-round base # Ferraz, King George Island, since 1983/4 -# Chile - year-round bases +# Chile - year-round bases and towns # Escudero, South Shetland Is, -621157-0585735, since 1994 -# Frei, King George Is, -6214-05848, since 1969 +# Frei, King George Island, -6214-05848, since 1969-03-07 # O'Higgins, Antarctic Peninsula, -6319-05704, since 1948-02 # Prat, -6230-05941 +# Villa Las Estrellas (a town), King George Island, since 1984-04-09 +# These locations have always used Santiago time; use TZ='America/Santiago'. # China - year-round bases # Great Wall, King George Island, since 1985-02-20 @@ -219,6 +221,15 @@ Rule NZAQ 1990 max - Mar Sun>=15 2:00s 0 # of GMT). This is a time zone I think two hours east of Moscow. The # natural time zone is in between the two: 8 hours ahead of GMT.'' # +# From Paul Eggert (2001-05-04): +# This seems to be hopelessly confusing, so I asked Lee Hotz about it +# in person. He said that some Antartic locations set their local +# time so that noon is the warmest part of the day, and that this +# changes during the year and does not necessarily correspond to mean +# solar noon. So the Vostok time might have been whatever the clocks +# happened to be during their visit. So we still don't really know what time +# it is at Vostok. But we'll guess UTC+6. +# Zone Antarctica/Vostok 0 - zzz 1957 Dec 16 6:00 - VOST # Vostok time =================================================================== RCS file: RCS/asia,v retrieving revision 2001.2 retrieving revision 2001.2.0.1 diff -pu -r2001.2 -r2001.2.0.1 --- asia 2001/04/05 20:43:40 2001.2 +++ asia 2001/05/31 00:59:05 2001.2.0.1 @@ -37,8 +37,11 @@ # 4:00 GST Gulf* # 5:30 IST India # 7:00 ICT Indochina* +# 7:00 WIT west Indonesia +# 8:00 CIT central Indonesia # 8:00 CST China # 9:00 CJT Central Japanese Time (1896/1937)* +# 9:00 EIT east Indonesia # 9:00 JST Japan # 9:00 KST Korea # 9:30 CST (Australian) Central Standard Time @@ -131,9 +134,11 @@ Zone Asia/Thimphu 5:58:36 - LMT 1947 Aug 6:00 - BTT # Bhutan Time # British Indian Ocean Territory -# From Whitman: +# Whitman and the 1995 CIA time zone map say 5:00, but the +# 1997 and later maps say 6:00. Assume the switch occurred in 1996. # Zone NAME GMTOFF RULES FORMAT [UNTIL] -Zone Indian/Chagos 5:00 - IOT # BIOT Time +Zone Indian/Chagos 5:00 - IOT 1996 # BIOT Time + 6:00 - IOT # Brunei # Zone NAME GMTOFF RULES FORMAT [UNTIL] @@ -357,7 +362,7 @@ Zone Asia/Dili 8:22:20 - LMT 1912 8:00 - TPT 1942 Feb 21 23:00 # E Timor Time 9:00 - JST 1945 Aug 9:00 - TPT 1976 May 3 - 8:00 - TPT 2000 Sep 17 00:00 + 8:00 - CIT 2000 Sep 17 00:00 9:00 - TPT # India @@ -374,27 +379,43 @@ Zone Asia/Calcutta 5:53:28 - LMT 1880 # Nicobar Is # Indonesia +# +# From Gwillim Law (2001-05-28), overriding Shanks: +# <http://www.sumatera-inc.com/go_to_invest/about_indonesia.asp#standtime> +# says that Indonesia's time zones changed on 1988-01-01. Looking at some +# time zone maps, I think that must refer to Western Borneo (Kalimantan Barat +# and Kalimantan Tengah) switching from UTC+8 to UTC+7. +# # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Jakarta 7:07:12 - LMT 1867 Aug 10 # Shanks says the next transition was at 1924 Jan 1 0:13, # but this must be a typo. 7:07:12 - JMT 1923 Dec 31 23:47:12 # Jakarta 7:20 - JAVT 1932 Nov # Java Time - 7:30 - JAVT 1942 Mar 23 + 7:30 - WIT 1942 Mar 23 9:00 - JST 1945 Aug - 7:30 - JAVT 1948 May - 8:00 - JAVT 1950 May - 7:30 - JAVT 1964 - 7:00 - JAVT + 7:30 - WIT 1948 May + 8:00 - WIT 1950 May + 7:30 - WIT 1964 + 7:00 - WIT +Zone Asia/Pontianak 7:17:20 - LMT 1908 May + 7:17:20 - PMT 1932 Nov # Pontianak MT + 7:30 - WIT 1942 Jan 29 + 9:00 - JST 1945 Aug + 7:30 - WIT 1948 May + 8:00 - WIT 1950 May + 7:30 - WIT 1964 + 8:00 - CIT 1988 Jan 1 + 7:00 - WIT Zone Asia/Ujung_Pandang 7:57:36 - LMT 1920 7:57:36 - MMT 1932 Nov # Macassar MT - 8:00 - BORT 1942 Feb 9 # Borneo Time + 8:00 - CIT 1942 Feb 9 9:00 - JST 1945 Aug - 8:00 - BORT + 8:00 - CIT Zone Asia/Jayapura 9:22:48 - LMT 1932 Nov - 9:00 - JAYT 1944 # Jayapura Time + 9:00 - EIT 1944 9:30 - CST 1964 - 9:00 - JAYT + 9:00 - EIT # Iran # From Paul Eggert (2000-06-12), following up a suggestion by Rich Wales: @@ -960,38 +981,52 @@ Zone Indian/Maldives 4:54:00 - LMT 1880 # Suhbaatar, and possibly Khentij. # From Paul Eggert (1999-12-15): -# For now, we'll comment out the east zone (Choybalsan) -# and use Shanks's and the IATA's data for the daylight-saving rules. # Naming and spelling is tricky in Mongolia. # We'll use Hovd (also spelled Chovd and Khovd) to represent the west zone; # the capital of the Hovd province is sometimes called Hovd, sometimes Dund-Us, # and sometimes Jirgalanta (with variant spellings), but the name Hovd # is good enough for our purposes. -# Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S -Rule Mongol 1981 1984 - Apr 1 0:00 1:00 S -Rule Mongol 1981 1984 - Oct 1 0:00 0 - -Rule Mongol 1985 1990 - Mar lastSun 2:00 1:00 S -Rule Mongol 1985 1990 - Sep lastSun 3:00 0 - -Rule Mongol 1991 1998 - Mar lastSun 0:00 1:00 S -Rule Mongol 1991 1995 - Sep lastSun 0:00 0 - -# IATA SSIM (1996-09) says 1996-10-25; go with Shanks. -Rule Mongol 1996 only - Oct lastSun 0:00 0 - -Rule Mongol 1997 1998 - Sep lastSun 0:00 0 - +# From Rives McDow (2001-05-13): +# In addition to Mongolia starting daylight savings as reported earlier +# (adopted DST on 2001-04-27 02:00 local time, ending 2001-09-28), +# there are three time zones. +# +# Provinces [at 7:00]: Bayan-ulgii, Uvs, Khovd, Zavkhan, Govi-Altai +# Provinces [at 8:00]: Khovsgol, Bulgan, Arkhangai, Khentii, Tov, +# Bayankhongor, Ovorkhangai, Dundgovi, Dornogovi, Omnogovi +# Provinces [at 9:00]: Dornod, Sukhbaatar +# +# [The province of Selenge is omitted from the above lists.] + +# 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 - +# IATA SSIM says 1990s switches occurred at 00:00, but Shanks (1995) lists +# them at 02:00s, and McDow says the 2001 switches also occurred at 02:00. +# Also, IATA SSIM (1996-09) says 1996-10-25. Go with Shanks through 1998. +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 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] +# Hovd, a.k.a. Chovd, Dund-Us, Dzhargalant, Khovd, Jirgalanta Zone Asia/Hovd 6:06:36 - LMT 1905 Aug 6:00 - HOVT 1978 # Hovd Time 7:00 Mongol HOV%sT +# Ulaanbaatar, a.k.a. Ulan Bataar, Ulan Bator, Urga Zone Asia/Ulaanbaatar 7:07:32 - LMT 1905 Aug 7:00 - ULAT 1978 # Ulaanbaatar Time 8:00 Mongol ULA%sT -# We're not sure about this entry yet, so we'll omit it for now. -#Zone Asia/Choybalsan 7:38:00 - LMT 1905 Aug -# 8:00 - CHOT 1978 # Choybalsan Time -# 9:00 Mongol CHO%sT 19?? -# 8:00 Mongol ULA%sT +# Choibalsan, a.k.a. Bajan Tuemen, Bajan Tumen, Chojbalsan, +# Choybalsan, Sanbejse, Tchoibalsan +# We're still not sure about this data, so we'll omit it for now. +#Zone Asia/Choibalsan 7:38:00 - LMT 1905 Aug +# 7:00 - ULAT 1978 +# 8:00 Mongol ULA%sT 1983 Apr +# 9:00 Mongol CHO%sT # Choibalsan Time # Nepal # Zone NAME GMTOFF RULES FORMAT [UNTIL] =================================================================== RCS file: RCS/europe,v retrieving revision 2001.2 retrieving revision 2001.2.0.1 diff -pu -r2001.2 -r2001.2.0.1 --- europe 2001/04/05 20:43:41 2001.2 +++ europe 2001/05/31 00:59:05 2001.2.0.1 @@ -41,7 +41,10 @@ # 0:00 GMT BST Greenwich, British Summer # 0:00 GMT IST Greenwich, Irish Summer # 0:00 WET WEST Western Europe +# 0:19:32 AMT NST Amsterdam, Netherlands Summer (1835-1937)* +# 0:20 NET NEST Netherlands (1937-1940)* # 1:00 CET CEST Central Europe +# 1:00:14 SET Swedish (1879-1899)* # 2:00 EET EEST Eastern Europe # 3:00 MSK MSD Moscow # @@ -1371,22 +1374,59 @@ Zone Europe/Monaco 0:29:32 - LMT 1891 Ma 1:00 EU CE%sT # Netherlands + # Howse writes that the Netherlands' railways used GMT between 1892 and 1940, # but for other purposes the Netherlands used Amsterdam mean time. -# The data before 1945 is taken from + +# However, Robert H. van Gent writes (2001-04-01): +# Howse's statement is only correct up to 1909. From 1909-05-01 (00:00:00 +# Amsterdam mean time) onwards, the whole of the Netherlands (including +# the Dutch railways) was required by law to observe Amsterdam mean time +# (19 minutes 32.13 seconds ahead of GMT). This had already been the +# common practice (except for the railways) for many decades but it was +# not until 1909 when the Dutch government finally defined this by law. +# On 1937-07-01 this was changed to 20 minutes (exactly) ahead of GMT and +# was generally known as Dutch Time ("Nederlandse Tijd"). +# +# (2001-04-08): +# 1892-05-01 was the date when the Dutch railways were by law required to +# observe GMT while the remainder of the Netherlands adhered to the common +# practice of following Amsterdam mean time. +# +# (2001-04-09): +# In 1835 the authorities of the province of North Holland requested the +# municipal authorities of the towns and cities in the province to observe +# Amsterdam mean time but I do not know in how many cases this request was +# actually followed. +# +# From 1852 onwards the Dutch telegraph offices were by law required to +# observe Amsterdam mean time. As the time signals from the observatory of +# Leiden were also distributed by the telegraph system, I assume that most +# places linked up with the telegraph (and railway) system automatically +# adopted Amsterdam mean time. +# +# Although the early Dutch railway companies initially observed a variety +# of times, most of them had adopted Amsterdam mean time by 1858 but it +# was not until 1866 when they were all required by law to observe +# Amsterdam mean time. + +# The data before 1945 are taken from # <http://www.phys.uu.nl/~vgent/wettijd/wettijd.htm>. + # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S Rule Neth 1916 only - May 1 0:00 1:00 NST # Netherlands Summer Time Rule Neth 1916 only - Oct 1 0:00 0 AMT # Amsterdam Mean Time Rule Neth 1917 only - Apr 16 2:00s 1:00 NST Rule Neth 1917 only - Sep 17 2:00s 0 AMT Rule Neth 1918 1921 - Apr Mon>=1 2:00s 1:00 NST -Rule Neth 1918 1921 - Sep lastSun 2:00s 0 AMT +Rule Neth 1918 1921 - Sep lastMon 2:00s 0 AMT Rule Neth 1922 only - Mar lastSun 2:00s 1:00 NST Rule Neth 1922 1936 - Oct Sun>=2 2:00s 0 AMT Rule Neth 1923 only - Jun Fri>=1 2:00s 1:00 NST Rule Neth 1924 only - Mar lastSun 2:00s 1:00 NST Rule Neth 1925 only - Jun Fri>=1 2:00s 1:00 NST +# From 1926 through 1939 DST began 05-15, except that it was delayed by a week +# in years when 05-15 fell in the Pentecost weekend. Rule Neth 1926 1931 - May 15 2:00s 1:00 NST Rule Neth 1932 only - May 22 2:00s 1:00 NST Rule Neth 1933 1936 - May 15 2:00s 1:00 NST @@ -1396,10 +1436,13 @@ Rule Neth 1937 1939 - Oct Sun>=2 2:00s 0 Rule Neth 1938 1939 - May 15 2:00s 1:00 S Rule Neth 1945 only - Apr 2 2:00s 1:00 S Rule Neth 1945 only - Sep 16 2:00s 0 - +# +# Amsterdam Mean Time was +00:19:32.13 exactly, but the .13 is omitted +# below because the current format requires GMTOFF to be an integer. # Zone NAME GMTOFF RULES FORMAT [UNTIL] -Zone Europe/Amsterdam 0:19:28 - LMT 1892 May - 0:19:28 Neth %s 1937 Jul - 0:20 Neth NE%sT 1940 May 17 0:00 +Zone Europe/Amsterdam 0:19:32 - LMT 1835 + 0:19:32 Neth %s 1937 Jul 1 + 0:20 Neth NE%sT 1940 May 17 0:00 # Dutch Time 1:00 C-Eur CE%sT 1945 Apr 2 2:00 1:00 Neth CE%sT 1977 1:00 EU CE%sT @@ -1417,17 +1460,62 @@ Rule Norway 1959 1964 - Mar Sun>=15 2:00 Rule Norway 1959 1965 - Sep Sun>=15 2:00s 0 - Rule Norway 1965 only - Apr 25 2:00s 1:00 S # Zone NAME GMTOFF RULES FORMAT [UNTIL] -Zone Europe/Oslo 0:43:00 - LMT 1895 +Zone Europe/Oslo 0:43:00 - LMT 1895 Jan 1 1:00 Norway CE%sT 1940 Aug 10 23:00 1:00 C-Eur CE%sT 1945 Apr 2 2:00 1:00 Norway CE%sT 1980 1:00 EU CE%sT # Svalbard & Jan Mayen + +# From Steffen Thorsen (2001-05-01): +# Although I could not find it explicitly, it seems that Jan Mayen and +# Svalbard have been using the same time as Norway at least since the +# time they were declared as parts of Norway. Svalbard was declared +# as a part of Norway by law of 1925-07-17 no 11, section 4 and Jan +# Mayen by law of 1930-02-27 no 2, section 2. (From +# http://www.lovdata.no/all/nl-19250717-011.html and +# http://www.lovdata.no/all/nl-19300227-002.html) The law/regulation +# for normal/standard time in Norway is from 1894-06-29 no 1 (came +# into operation on 1895-01-01) and Svalbard/Jan Mayen seem to be a +# part of this law since 1925/1930. (From +# http://www.lovdata.no/all/nl-18940629-001.html ) I have not been +# able to find if Jan Mayen used a different time zone (e.g. -0100) +# before 1930. Jan Mayen has only been "inhabitated" since 1921 by +# Norwegian meteorologists and maybe used the same time as Norway ever +# since 1921. Svalbard (Arctic/Longyearbyen) has been inhabited since +# before 1895, and therefore probably changed the local time somewhere +# between 1895 and 1925 (inclusive). + +# From Paul Eggert (2001-05-01): +# +# Actually, Jan Mayen was never occupied by Germany during World War II, +# so it must have diverged from Oslo time during the war, as Olso was +# keeping Berlin time. +# +# <http://home.no.net/janmayen/history.htm> says that the meteorologists +# burned down their station in 1940 and left the island, but returned in +# 1941 with a small Norwegian garrison and continued operations despite +# frequent air ttacks from Germans. In 1943 the Americans established a +# radiolocating station on the island, called "Atlantic City". Possibly +# the UTC offset changed during the war, but I think it unlikely that +# Jan Mayen used German daylight-saving rules. +# +# Svalbard is more complicated, as it was raided in August 1941 by an +# Allied party that evacuated the civilian population to England (says +# <http://www.bartleby.com/65/sv/Svalbard.html>). The Svalbard FAQ +# <http://www.svalbard.com/SvalbardFAQ.html> says that the Germans were +# expelled on 1942-05-14. However, small parties of Germans did return, +# and according to Wilhelm Dege's book "War North of 80" (1954) +# <http://www.utpress.utoronto.ca/publishing/rights/dege_warnorthof80.htm> +# the German armed forces at the Svalbard weather station code-named +# Haudegen did not surrender to the Allies until September 1945. +# +# All these events predate our cutoff date of 1970. Unless we can +# come up with more definitive info about the timekeeping during the +# war years it's probably best just do do the following for now: Link Europe/Oslo Arctic/Longyearbyen -# From Whitman: -# Zone NAME GMTOFF RULES FORMAT [UNTIL] -Zone Atlantic/Jan_Mayen -1:00 - EGT +Link Europe/Oslo Atlantic/Jan_Mayen # Poland # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S @@ -1638,7 +1726,7 @@ Zone Europe/Bucharest 1:44:24 - LMT 1891 # enforcing curfew at the wrong time. # # Zone NAME GMTOFF RULES FORMAT [UNTIL] -Zone Europe/Kaliningrad 1:22:00 - LMT 1893 Apr +Zone Europe/Kaliningrad 1:22:00 - LMT 1893 Apr 1:00 C-Eur CE%sT 1945 2:00 Poland CE%sT 1946 3:00 Russia MSK/MSD 1991 Mar 31 2:00s @@ -1795,11 +1883,56 @@ Zone Atlantic/Canary -1:01:36 - LMT 1922 # Ignore this for now, as the Canaries are part of the EU. # Sweden -# Zone NAME GMTOFF RULES FORMAT [UNTIL] -Zone Europe/Stockholm 1:12:12 - LMT 1878 May 31 - 1:12:12 - SMT 1900 Jan 1 1:00 # Stockholm MT - 1:00 - CET 1916 Apr 14 23:00s - 1:00 1:00 CEST 1916 Sep 30 23:00s + +# From Ivan Nilsson (2001-04-13), superseding Shanks: +# +# The law "Svensk forfattningssamling 1878, no 14" about standard time in 1879: +# From the beginning of 1879 (that is 01-01 00:00) the time for all +# places in the country is "the mean solar time for the meridian at +# three degrees, or twelve minutes of time, to the west of the +# meridian of the Observatory of Stockholm". The law is dated 1878-05-31. +# +# The observatory at that time had the meridian 18 degrees 03' 30" +# eastern longitude = 01:12:14 in time. Less 12 minutes gives the +# national standard time as 01:00:14 ahead of GMT.... +# +# About the beginning of CET in Sweden. The lawtext ("Svensk +# forfattningssamling 1899, no 44") states, that "from the beginning +# of 1900... ... the same as the mean solar time for the meridian at +# the distance of one hour of time from the meridian of the English +# observatory at Greenwich, or at 12 minutes 14 seconds to the west +# from the meridian of the Observatory of Stockholm". The law is dated +# 1899-06-16. In short: At 1900-01-01 00:00:00 the new standard time +# in Sweden is 01:00:00 ahead of GMT. +# +# 1916: The lawtext ("Svensk forfattningssamling 1916, no 124") states +# that "1916-05-15 is considered to begin one hour earlier". It is +# pretty obvious that at 05-14 23:00 the clocks are set to 05-15 00:00.... +# Further the law says, that "1916-09-30 is considered to end one hour later". +# +# The laws regulating [DST] are available on the site of the Swedish +# Parliament beginning with 1985 - the laws regulating 1980/1984 are +# not available on the site (to my knowledge they are only available +# in Swedish): <http://www.riksdagen.se/english/work/sfst.asp> (type +# "sommartid" without the quotes in the field "Fritext" and then click +# the Sok-button). +# +# (2001-05-13): +# +# I have now found a newspaper stating that at 1916-10-01 01:00 +# summertime the church-clocks etc were set back one hour to show +# 1916-10-01 00:00 standard time. The article also reports that some +# people thought the switch to standard time would take place already +# at 1916-10-01 00:00 summer time, but they had to wait for another +# hour before the event took place. +# +# Source: The newspaper "Dagens Nyheter", 1916-10-01, page 7 upper left. + +# Zone NAME GMTOFF RULES FORMAT [UNTIL] +Zone Europe/Stockholm 1:12:12 - LMT 1879 Jan 1 + 1:00:14 - SET 1900 Jan 1 # Swedish Time + 1:00 - CET 1916 May 14 23:00 + 1:00 1:00 CEST 1916 Oct 1 01:00 1:00 - CET 1980 1:00 EU CE%sT =================================================================== RCS file: RCS/northamerica,v retrieving revision 2001.2 retrieving revision 2001.2.0.1 diff -pu -r2001.2 -r2001.2.0.1 --- northamerica 2001/04/05 20:44:38 2001.2 +++ northamerica 2001/05/31 00:59:05 2001.2.0.1 @@ -81,12 +81,12 @@ # From Joseph Gallant <notquite(a)hotmail.com>, citing # George H. Douglas, _The Early Days of Radio Broadcasting_ (1987): # At 7 P.M. (Eastern War Time) [on 1945-08-14], the networks were set -# to switch to London for Atlee's address, but the American people +# to switch to London for Attlee's address, but the American people # never got to hear his speech live. According to one press account, # CBS' Bob Trout was first to announce the word of Japan's surrender, # but a few seconds later, NBC, ABC and Mutual also flashed the word # of surrender, all of whom interrupting the bells of Big Ben in -# London which were to precede Mr. Atlee's speech. +# London which were to precede Mr. Attlee's speech. # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S Rule US 1918 1919 - Mar lastSun 2:00 1:00 D @@ -185,13 +185,6 @@ Rule US 1987 max - Apr Sun>=1 2:00 1:00 # "Chamorro Standard Time" for time in Guam and the Northern Marianas. # See the file "australasia". -# From Ryan Alessi of the Thousand Oaks Star (2001-02-15) via Rives McDow: -# Brad Sherman, D-Sherman Oaks, introduced a bill in Congress on -# Wednesday that could have California operating on Denver time as -# early as this summer.... The options include keeping -# daylight-saving time all year long, or setting clocks back two hours -# -- instead of just one -- during the existing daylight-saving time. - # US Eastern time, represented by New York @@ -280,7 +273,7 @@ Zone America/Los_Angeles -7:52:58 - LMT # Alaska # AK%sT is the modern abbreviation for -9:00 per USNO. # -# From Paul Eggert (2001-04-01): +# From Paul Eggert (2001-05-30): # Howse writes that Alaska switched from the Julian to the Gregorian calendar, # and from east-of-GMT to west-of-GMT days, when the US bought it from Russia. # This was on 1867-10-18, a Friday; the previous day was 1867-10-06 Julian, @@ -288,6 +281,13 @@ Zone America/Los_Angeles -7:52:58 - LMT # ignoring the switch from Julian to Gregorian, since we can't represent # the Julian calendar. # +# As far as we know, none of the exact locations mentioned below were +# permanently inhabited in 1867 by anyone using either calendar. +# (Yakutat was colonized by the Russians in 1799, but the settlement +# was destroyed in 1805 by a Yakutat-kon war party.) However, there +# were nearby inhabitants in some cases and for our purposes perhaps +# it's best to simply use the official transition. +# # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Juneau 15:02:19 - LMT 1867 Oct 18 -8:57:41 - LMT 1900 Aug 20 12:00 @@ -407,7 +407,7 @@ Zone America/Boise -7:44:49 - LMT 1883 N # Pam Belluck reported in the New York Times (2001-01-31) that the # Indiana Legislature is considering a bill to adopt DST statewide. # Her article mentioned Vevay, whose post office observes a different -# time zone than Danner's Hardware across the street. +# time zone from Danner's Hardware across the street. # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER Rule Indianapolis 1941 only - Jun 22 2:00 1:00 D @@ -589,10 +589,11 @@ Zone America/Menominee -5:50:27 - LMT 18 -6:00 US C%sT # Navassa +# administered by the US Fish and Wildlife Service # claimed by US under the provisions of the 1856 Guano Islands Act # also claimed by Haiti # occupied 1857/1900 by the Navassa Phosphate Co -# US lighthouse 1917/1997-01 +# US lighthouse 1917/1996-09 # currently uninhabited # see Mark Fineman, ``An Isle Rich in Guano and Discord'', # _Los Angeles Times_ (1998-11-10), A1, A10; it cites =================================================================== RCS file: RCS/southamerica,v retrieving revision 2001.1 retrieving revision 2001.1.0.1 diff -pu -r2001.1 -r2001.1.0.1 --- southamerica 2001/03/13 17:57:40 2001.1 +++ southamerica 2001/05/31 00:59:05 2001.1.0.1 @@ -493,16 +493,26 @@ Zone America/Rio_Branco -4:31:12 - LMT 1 # Because of the same drought, the government decided to end DST later, # on April 3, (one-time change). -# From Gwillim Law (2001-02-20): -# I came across a Chilean on-line newspaper, La Tercera. Its -# <a href="http://www.tercera.cl/diario/1998/03/13/extras.html"> -# 1998-03-13 issue -# </a>, says (my translation): -# "At 24:00 (midnight) tomorrow (Saturday) - 22:00 in the insular -# territory [Easter Island, Juan Fernandez, etc.] - winter time will -# begin in the entire country." +# From Gwillim Law (2001-05-04): +# I came across another article in "La Tercera" about Chilean DST. +# <http://www.tercera.cl/diario/2000/10/13/t-extras.html> +# It clearly confirms my earlier suggestion, that DST begins at 22:00 +# on Easter Island.... But it also seems to be saying that the +# observance of DST in Chile began in 1966, rather than 1969 as +# ... [Shanks] has it.... +# +# My translation: +# +# "The Chilean Army has announced that summer time will begin tomorrow, +# Saturday, October 14 in continental Chile, insular Chile, and +# Antarctica, as provided by Supreme Decree 25 of January 11, 1966. +# By the preceding, official time in continental Chile and Chilean +# Antarctic, and official time in Western Insular Chile, which applies +# to Easter Island and Sala y Gomez Island, will be set forward at +# midnight and at 22:00, respectively, by 20 minutes." -# From Paul Eggert (2001-02-21): +# From Paul Eggert (2001-05-04): +# Go with this article in preference to Shanks's 1969 date for modern DST. # Assume this rule has been used since DST was introduced in the islands. # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S @@ -510,8 +520,8 @@ Rule Chile 1918 only - Sep 1 0:00 1:00 Rule Chile 1919 only - Jul 2 0:00 0 - Rule Chile 1927 1931 - Sep 1 0:00 1:00 S Rule Chile 1928 1932 - Apr 1 0:00 0 - -Rule Chile 1969 1997 - Oct Sun>=9 4:00u 1:00 S -Rule Chile 1970 1998 - Mar Sun>=9 3:00u 0 - +Rule Chile 1966 1997 - Oct Sun>=9 4:00u 1:00 S +Rule Chile 1967 1998 - Mar Sun>=9 3:00u 0 - Rule Chile 1998 only - Sep 27 4:00u 1:00 S Rule Chile 1999 only - Apr 4 3:00u 0 - Rule Chile 1999 max - Oct Sun>=9 4:00u 1:00 S @@ -528,10 +538,9 @@ Zone Pacific/Easter -7:17:28 - LMT 1890 -7:00 Chile EAS%sT 1982 Mar 14 # Easter I Time -6:00 Chile EAS%sT # -# Whitman says Juan Fernandez Is are like America/Santiago. -# San Ambrosio, San Felix -# no information; probably like America/Santiago - +# Sala y Gomez Island is like Pacific/Easter. +# Other Chilean locations, including Juan Fernandez Is, San Ambrosio, +# San Felix, and Antarctic bases, are like America/Santiago. # Colombia # Shanks specifies 24:00 for 1992 transition times; go with IATA, =================================================================== RCS file: RCS/zone.tab,v retrieving revision 2001.1 retrieving revision 2001.1.0.1 diff -pu -r2001.1 -r2001.1.0.1 --- zone.tab 2001/03/13 17:57:42 2001.1 +++ zone.tab 2001/05/31 00:59:05 2001.1.0.1 @@ -12,7 +12,7 @@ # first latitude (+ is north), then longitude (+ is east). # 3. Zone name used in value of TZ environment variable. # 4. Comments; present if and only if the country has multiple rows. -# +# # Columns are separated by a single tab. # The table is sorted first by country, then an order within the country that # (1) makes some geographical sense, and @@ -120,8 +120,8 @@ CG -0416+01517 Africa/Brazzaville CH +4723+00832 Europe/Zurich CI +0519-00402 Africa/Abidjan CK -2114-15946 Pacific/Rarotonga -CL -3327-07040 America/Santiago mainland -CL -2710-10927 Pacific/Easter Easter Island +CL -3327-07040 America/Santiago most locations +CL -2710-10927 Pacific/Easter Easter Island & Sala y Gomez CM +0403+00942 Africa/Douala CN +4545+12641 Asia/Harbin north Manchuria CN +3114+12128 Asia/Shanghai China coast @@ -187,7 +187,8 @@ HR +4548+01558 Europe/Zagreb HT +1832-07220 America/Port-au-Prince HU +4730+01905 Europe/Budapest ID -0610+10648 Asia/Jakarta Java & Sumatra -ID -0507+11924 Asia/Ujung_Pandang Borneo & Celebes +ID -0002+10920 Asia/Pontianak west & central Borneo +ID -0507+11924 Asia/Ujung_Pandang east & south Borneo, Celebes, Bali, Nusa Tengarra, west Timor ID -0232+14042 Asia/Jayapura Irian Jaya & the Moluccas IE +5320-00615 Europe/Dublin IL +3146+03514 Asia/Jerusalem @@ -237,7 +238,8 @@ ML +1239-00800 Africa/Bamako southwest M ML +1446-00301 Africa/Timbuktu northeast Mali MM +1647+09610 Asia/Rangoon MN +4755+10653 Asia/Ulaanbaatar most locations -MN +4801+09139 Asia/Hovd Bayan-Olgiy, Hovd, Uvs +MN +4801+09139 Asia/Hovd Bayan-Olgiy, Govi-Altai, Hovd, Uvs, Zavkhan +#MN +4804+11430 Asia/Choibalsan Dornod, Sukhbaatar (unsure about this) MO +2214+11335 Asia/Macao MP +1512+14545 Pacific/Saipan MQ +1436-06105 America/Martinique

2 1

IERS Message No. 10
by central_bureau＠iers.org May 30, 2001

May 30, 2001

*************************************************************************** IERS Message No. 10 May 30, 2001 *************************************************************************** CHAMP Announcement of Opportunity Release The GeoForschungsZentrum Potsdam (GFZ) has released on May 28, 2001 electronically an Announcement of Opportunity for conducting basic scientific research and application oriented projects using data and data products from its georesearch mission CHAMP. Individuals or parties interested in proposing a CHAMP mission investigation in response to this AO are requested to contact the Newsletter No. 3 at http://op.gfz-potsdam.de/champ/ for further details. Christoph Reigber (CHAMP Project Director) ---------------------------------------------------- Univ.-Prof. Dr.-Ing. Dr.-Ing. E.h. Christoph Reigber GeoForschungsZentrum Potsdam (GFZ) Division 1: Kinematics & Dynamics of the Earth Telegrafenberg A 17, D-14473 Potsdam, Germany phone: +49 (0)331 288-1100, -1101 (secr.) fax: +49 (0)331 288-1111 e-mail: reigber(a)gfz-potsdam.de www: http://www.gfz-potsdam.de/ ***************************************************************************

1 0

Year Round Daylight Saving Time?
by Martin Smoot May 29, 2001

May 29, 2001

the latest energy problems have prompted Massacuhsetts to consider year round Daylight saving time. cnn.com (under US) has an article: http://www.cnn.com/2001/US/05/29/daylight.saving.ap/index.html there is also a reference on the wmal.com web page (WMAL is a washington area radio station). I have not found any other references although I have not really looked very hard. -- Martin Smoot Network Storage Solutions 703-834-2242 msmoot(a)nssolutions.com www.nssolutions.com

2 1

[akr@m17n.org: bin/27630: mktime problem.]
by Garrett Wollman May 25, 2001

May 25, 2001

A FreeBSD user submitted the following bug report. I'm curious as to whether the current tzcode still has this problem. My analysis follows at the end. -GAWollman ------- start of forwarded message (RFC 934 encapsulation) ------- Message-Id: <20010525021018.01D54727(a)flux.etl.go.jp> Reply-To: akr(a)m17n.org X-Send-Pr-Version: 3.2 List-ID: <freebsd-bugs.FreeBSD.ORG> List-Archive: <http://docs.freebsd.org/mail/> (Web Archive) List-Help: <mailto:majordomo?subject=help> (List Instructions) List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-bugs> List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-bugs> X-Loop: FreeBSD.org Precedence: bulk From: akr(a)m17n.org Sender: owner-freebsd-bugs(a)FreeBSD.ORG To: FreeBSD-gnats-submit(a)FreeBSD.ORG Subject: bin/27630: mktime problem. Date: Fri, 25 May 2001 11:10:18 +0900 (JST) >Number: 27630 >Category: bin >Synopsis: mktime failure. >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu May 24 19:20:00 PDT 2001 >Closed-Date: >Last-Modified: >Originator: Tanaka Akira >Release: FreeBSD 4.2-RELEASE i386 >Organization: m17n >Environment: FreeBSD flux 4.2-RELEASE FreeBSD 4.2-RELEASE #2: Fri Jan 12 22:55:02 JST 2001 akr@flux:/usr/src/sys/compile/AKR i386 >Description: mktime(3) fails on some condition. For example, TZ=Africa/Monrovia, 1972/05/01 00:44:30 cannot be converted to time_t. Since this example is taken from `zdump -v Africa/Monrovia' and it is after Epoch, there is no reason to fail. Actually, I tested all time listed in `zdump -v' for each timezone in /usr/share/zoneinfo and found many failures. Above failure is one of them. >How-To-Repeat: % cat tst.c #include <stdio.h> #include <time.h> int main() { struct tm a; time_t t; a.tm_year = 1972 - 1900; a.tm_mon = 5 - 1; a.tm_mday = 1; a.tm_hour = 0; a.tm_min = 44; a.tm_sec = 30; a.tm_wday = 0; a.tm_yday = 0; a.tm_isdst = -1; t = mktime(&a); if (t == -1) { perror("mktime"); exit(1); } printf("no problem\n"); return 0; } % gcc tst.c % TZ=Africa/Monrovia ./a.out mktime: Undefined error: 0 % >Fix: >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo(a)FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message ------- end ------- This problem appears to result from the `saved_seconds' hackery in time2(): saved_seconds = yourtm.tm_sec; yourtm.tm_sec = 0; time2() then goes on to attempt to find (in this example) 1972-05-01T00:44:00, which does not exist in this time zone, and returns failure. -GAWollman

1 0

FW: Time Zone Converter
by Olson, Arthur David (NCI) May 16, 2001

May 16, 2001

Bob Niebergall is not on the time zone mailing list; direct replies appropriately. --ado -----Original Message----- From: Bob Niebergall [mailto:r.niebergall@sk.sympatico.ca] Sent: Saturday, May 12, 2001 2:31 PM To: stewart(a)parc.xerox.com Subject: Time Zone Converter I have used your time zone converter and I have to point out some errors. There is not such time zone as Canada/Saskatchewan and Canada/East Saskatchewan. As of the sending of this message the province of Saskatchewan, in Canada, is on Central Standart Time and we do not convert to daylight saving time for the summer. Bob Niebergall Saskatoon, Saskatchewan, Canada

1 0

[Fwd: Time Zone Converter]
by Bob Niebergall May 16, 2001

May 16, 2001

1 0

Mongolia
by Oscar van Vlijmen May 15, 2001

May 15, 2001

Reasonably reliable information about the administrative regions in Mongolia can be found on the web site of the National Statistical Office of Mongolia: http://statis.pmis.gov.mn/english/territory_fe.htm and http://statis.pmis.gov.mn/yearbook99/Territor/1_1.HTM The spelling of the places on the Mongolian web site is not extremely consistent (e.g. Zavkhan and Zavhan). The Times atlas uses a spelling which is more consistent with the Mongolian-Cyrillic names (Dzavhan). Of course, names with ö and ü have to be Posixified, for instance by dropping the diacritics. At the moment, still no better time zone information can be found on-line than on the web page: http://www.mongoliatourism.gov.mn/factpack.htm as referred to by Jesper Nørgard and saying: "Most of Mongolia is 8 hours ahead of GMT. However, the three western aimags of Khovd, Uvs and Bayan Ulgii are GMT+7. Mongolia no longer puts forward its clocks by 1 hour in the summer months." Khovd is spelled by the Times atlas as Hovd and Bayan Ulgii as Bayan-Ölgiy. Uvs is 'correct'. Regards, Oscar van Vlijmen 2001-05-16

1 0