- tz - lists.iana.org

Multi-timezone clock
by peter.verthez＠alcatel.be June 14, 2005

June 14, 2005

Hello all, I've been making a multi-timezone clock based on the Olson timezone database, which may be interesting to the people on this mailing list. The freshmeat project page can be found here: http://freshmeat.net/projects/intclock The tz database is used in the configuration window, to select a timezone for each clock. The program is written in Perl and requires perl-Gtk2 (actually, perl-Gtk will also work, but with a much less polished user interface). It is currently available in English, Dutch and German. Country names are translated via the CLDR (currently version 1.3) for all languages automatically. Manual translation is only needed for some 30 strings in the user interface. Note that the translations for timezone names in the CLDR (i.e. the exemplarCity entries) are currently not used, because the available data is too sparse: all city names are shown in English. If the CLDR includes more entries later, this may change. All suggestions, and translations to other languages, are very welcome (see web page for details). Best regards, Peter.

4 10

Tzcode2005j.tar.gz and tzdata2005j.tar.gz
by Olson, Arthur David (NIH/NCI) June 13, 2005

June 13, 2005

The files... ftp://elsie.nci.nih.gov/pub/tzcode2005j.tar.gz ...and... ftp://elsie.nci.nih.gov/pub/tzdata2005j.tar.gz ...are now available. These reflect changes to limit the length of time zone abbreviations and the characters used in those abbreviations. There are also changes to handle POSIX-style "quoted" time zone environment variables. The changes were circulated on the time zone mailing list; the only change since then was the removal of a couple of minimum-length of abbreviation checks. --ado

1 0

No 1980 discrepancy in Denmark
by Jesper Norgaard Welen June 12, 2005

June 12, 2005

>> in another related law, the effecting DST changes are stated >> explicitly: to be from 6.th. of April 1980 at 2.00 to 28.th. of >> September 1980 at 2.00. If this is true, this differs slightly from >> the EU rule in that DST runs to 2.00, not 3.00. > > It would have been odd for the 1980 transitions to disagree with both old Danish > tradition (1945-1948) and with the then-current EU rules. For now, how about if > we assume that the 02:00 of the above source refers to standard time, not > wall-clock time, and so the EU rules were in effect? It would indeed have been strange also to disagree with old Danish tradition, but I decided instead to take the investigation a bit further and contacted a number of danish newspapers by email. Unfortunately I did not get many answers, but one was conclusive, EU rules were indeed followed: ===================== BEGIN Hej J. Nørgaard Vedr. Sommertid som du har sendt en mail angående. I Herning Folkeblad 1980, 26.september står der: Natten mellem lørdag og søndag skal urene stilles ind på vintertid eller rettere normaltid. Det betyder at natten bliver en time længere. Rent praktisk foretages skiftet på den måde, at når klokken er tre natten mellem lørdag og søndag stilles urene en time tilbage. Venlig hilsen Anne-Marie Hansen e-mail: amh(a)herningfolkeblad.dk ===================== END This is a quote from Herning Folkeblad (News), the 26.th. of September 1980. Quoting from the end of the article the night between Saturday and Sunday the clock is set back from three to two. By the way, I agree with all of Paul Eggerts comments to my suggested corrections to the tz database. I will probably send some more observations on the tz database, but later at a more convenient time (for me). Just a little taster, I think that the Mataveri (Easter Island) time zone change in 1982 was at 13.th. of March 1982 21:00, instead of 14.th. of March at 0:00 as the tz database has it, which in reality means that the actual time was changed from GMT-6 to GMT-7 and then back to GMT-6 four hours later. If the change had taken place at 21:00 the 13.th. of March, then there would be no actual time change, but the time would stay as GMT-6 all of March in 1982 in Easter Island. Regards, Jesper Jesper Nørgaard Welen Email: jnorgard(a)Prodigy.Net.mx Project Leader (Líder de Proyecto) Software 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 Download the free program World Time Explorer, I made: http://www.cimmyt.org/timezone/index.htm

1 0

RE: revised proposed time zone abbreviation changes
by Olson, Arthur David (NIH/NCI) June 7, 2005

June 7, 2005

> That "stdlen < 3" remains, I'd make it just be "if (stdlen == 0)" > (for the error return). < 0 is impossible the way the code is > written, so there's no need to test that. Anything > 0 in that > context should be OK. It might be best to simply remove the test, relying on the common-case code to catch any problems. (This would avoid surprises down the line involving a need to change two length tests rather than one.) --ado

2 1

RE: 64-bit work
by Olson, Arthur David (NIH/NCI) June 7, 2005

June 7, 2005

> > There are a few places (Cairo, Godthab, Chile) that can't be > > represented by POSIX-conforming strings; for these we'd punt to the > > "write 400 years worth of data and work modulo 400" approach (leaving off the trailing TZ string). > I'm not sure what the problem is with those timezones. Can you explain? The problem isn't with the time zones; the problem is with POSIX limitations on describing time zones. The easy case to explain is Chile, where transitions occur in March and October on the first Sunday on or after the 9th of the month. This will sometimes be the second Sunday of the month; other times it will be the third Sunday of the month. POSIX, however, only allows for first Sunday or second Sunday or third Sunday or fourth Sunday or last Sunday. Avoid the temptation to try to "fix" POSIX; the inherent POSIX assumption is that all time zones can be described with two annual transitions that are historically invariant and that simply won't fly in the real world. --ado

1 0

Proposed time zone abbreviation changes
by Arthur David Olson June 7, 2005

June 7, 2005

Here are changes (relative to what's currently available via ftp) to deal with time zone abbreviation issues. 1. The use of "??" as an abbreviation in the solar* files is eliminated. 2. The zic command warns about non-POSIX abbreviations. 3. The zdump command warns about non-POSIX abbreviations if its "-v" flag is used. 4. localtime.c is changed to restrict characters in abbreviations to [a-zA-Z0-9 :+-] (replacing other characters with 'X'), and to restrict abbreviation lengths to 16 (truncating longer abbreviations). Both zic.c and localtime.c have the long Factory "abbreviation" grandparented in. --ado diff -r -c old/Makefile new/Makefile *** old/Makefile Mon Apr 4 11:24:31 2005 --- new/Makefile Thu May 26 12:42:13 2005 *************** *** 1,4 **** ! # @(#)Makefile 7.108 # Change the line below for your time zone (after finding the zone you want in # the time zone files, or adding it to a time zone file). --- 1,4 ---- ! # @(#)Makefile 7.109 # Change the line below for your time zone (after finding the zone you want in # the time zone files, or adding it to a time zone file). *************** *** 111,117 **** # -DNO_RUN_TIME_WARNINGS_ABOUT_YEAR_2000_PROBLEMS_THANK_YOU=1 # if you do not want run time warnings about formats that may cause # year 2000 grief ! # GCC_DEBUG_FLAGS = -Dlint -g -O -fno-common \ -Wall -Wcast-qual -Wconversion -Wmissing-prototypes \ -Wnested-externs -Wpointer-arith -Wshadow \ --- 111,119 ---- # -DNO_RUN_TIME_WARNINGS_ABOUT_YEAR_2000_PROBLEMS_THANK_YOU=1 # if you do not want run time warnings about formats that may cause # year 2000 grief ! # -DZIC_MAX_ABBR_LEN_WO_WARN=3 ! # (or some other number) to set the maximum time zone abbreviation length ! # that zic will accept without a warning (the default is 6) GCC_DEBUG_FLAGS = -Dlint -g -O -fno-common \ -Wall -Wcast-qual -Wconversion -Wmissing-prototypes \ -Wnested-externs -Wpointer-arith -Wshadow \ diff -r -c old/localtime.c new/localtime.c *** old/localtime.c Mon Apr 4 11:24:32 2005 --- new/localtime.c Thu May 26 15:02:36 2005 *************** *** 5,11 **** #ifndef lint #ifndef NOID ! static char elsieid[] = "@(#)localtime.c 7.91"; #endif /* !defined NOID */ #endif /* !defined lint */ --- 5,11 ---- #ifndef lint #ifndef NOID ! static char elsieid[] = "@(#)localtime.c 7.93"; #endif /* !defined NOID */ #endif /* !defined lint */ *************** *** 22,27 **** --- 22,40 ---- #include "fcntl.h" #include "float.h" /* for FLT_MAX and DBL_MAX */ + #ifndef TZ_ABBR_MAX_LEN + #define TZ_ABBR_MAX_LEN 16 + #endif /* !defined TZ_ABBR_MAX_LEN */ + + #ifndef TZ_ABBR_CHAR_SET + #define TZ_ABBR_CHAR_SET \ + "abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789 :+-" + #endif /* !defined TZ_ABBR_CHAR_SET */ + + #ifndef TZ_ABBR_ERR_CHAR + #define TZ_ABBR_ERR_CHAR 'X' + #endif /* !defined TZ_ABBR_ERR_CHAR */ + /* ** SunOS 4.1.1 headers lack O_BINARY. */ *************** *** 124,129 **** --- 137,143 ---- static long detzcode P((const char * codep)); static const char * getzname P((const char * strp)); + static const char * getqzname P((const char * strp, const char delim)); static const char * getnum P((const char * strp, int * nump, int min, int max)); static const char * getsecs P((const char * strp, long * secsp)); *************** *** 269,274 **** --- 283,306 ---- tzname[ttisp->tt_isdst] = &sp->chars[ttisp->tt_abbrind]; } + /* + ** Finally, scrub the abbreviations. + ** First, replace bogus characters. + */ + for (i = 0; i < sp->charcnt; ++i) + if (strchr(TZ_ABBR_CHAR_SET, sp->chars[i]) == NULL) + sp->chars[i] = TZ_ABBR_ERR_CHAR; + /* + ** Second, truncate long abbreviations. + */ + for (i = 0; i < sp->typecnt; ++i) { + register const struct ttinfo * const ttisp = &sp->ttis[i]; + register char * cp = &sp->chars[ttisp->tt_abbrind]; + + if (strlen(cp) > TZ_ABBR_MAX_LEN && + strcmp(cp, GRANDPARENTED) != 0) + *(cp + TZ_ABBR_MAX_LEN) = '\0'; + } } static int *************** *** 470,475 **** --- 502,528 ---- } /* + ** Given a pointer into an extended time zone string, scan until the ending + ** delimiter of the zone name is located. Return a pointer to the delimiter. + ** + ** As with getzname above, the legal character set is actually quite + ** restricted, with other characters producing undefined results. + ** We choose not to care - allowing almost anything to be in the zone abbrev. + */ + + static const char * + getqzname(strp, delim) + register const char * strp; + const char delim; + { + register char c; + + while ((c = *strp) != '\0' && c != delim) + ++strp; + return strp; + } + + /* ** Given a pointer into a time zone string, extract a number from that string. ** Check that the number is within a specified range; if it is not, return ** NULL. *************** *** 753,760 **** stdlen = (sizeof sp->chars) - 1; stdoffset = 0; } else { ! name = getzname(name); ! stdlen = name - stdname; if (stdlen < 3) return -1; if (*name == '\0') --- 806,823 ---- stdlen = (sizeof sp->chars) - 1; stdoffset = 0; } else { ! if (*name == '<') { ! name++; ! stdname = name; ! name = getqzname(name, '>'); ! if (*name != '>') ! return (-1); ! stdlen = name - stdname; ! name++; ! } else { ! name = getzname(name); ! stdlen = name - stdname; ! } if (stdlen < 3) return -1; if (*name == '\0') *************** *** 767,775 **** if (load_result != 0) sp->leapcnt = 0; /* so, we're off a little */ if (*name != '\0') { ! dstname = name; ! name = getzname(name); ! dstlen = name - dstname; /* length of DST zone name */ if (dstlen < 3) return -1; if (*name != '\0' && *name != ',' && *name != ';') { --- 830,847 ---- if (load_result != 0) sp->leapcnt = 0; /* so, we're off a little */ if (*name != '\0') { ! if (*name == '<') { ! dstname = ++name; ! name = getqzname(name, '>'); ! if (*name != '>') ! return -1; ! dstlen = name - dstname; ! name++; ! } else { ! dstname = name; ! name = getzname(name); ! dstlen = name - dstname; /* length of DST zone name */ ! } if (dstlen < 3) return -1; if (*name != '\0' && *name != ',' && *name != ';') { diff -r -c old/private.h new/private.h *** old/private.h Mon Apr 4 11:24:32 2005 --- new/private.h Thu May 26 14:54:07 2005 *************** *** 25,30 **** --- 25,32 ---- #endif /* !defined NOID */ #endif /* !defined lint */ + #define GRANDPARENTED "Local time zone must be set--see zic manual page" + /* ** Defaults for preprocessor symbols. ** You can override these in your C compiler options, e.g. `-DHAVE_ADJTIME=0'. diff -r -c old/solar87 new/solar87 *** old/solar87 Thu Apr 21 15:04:16 2005 --- new/solar87 Thu May 26 12:42:35 2005 *************** *** 1,4 **** ! # @(#)solar87 7.3 # So much for footnotes about Saudi Arabia. # Apparent noon times below are for Riyadh; your mileage will vary. --- 1,4 ---- ! # @(#)solar87 7.4 # So much for footnotes about Saudi Arabia. # Apparent noon times below are for Riyadh; your mileage will vary. *************** *** 381,388 **** # Before and after 1987, we'll operate on local mean solar time. # Zone NAME GMTOFF RULES/SAVE FORMAT [UNTIL] ! Zone Asia/Riyadh87 3:07:04 - ?? 1987 ! 3:07:04 sol87 ?? 1988 ! 3:07:04 - ?? # For backward compatibility... Link Asia/Riyadh87 Mideast/Riyadh87 --- 381,388 ---- # Before and after 1987, we'll operate on local mean solar time. # Zone NAME GMTOFF RULES/SAVE FORMAT [UNTIL] ! Zone Asia/Riyadh87 3:07:04 - zzz 1987 ! 3:07:04 sol87 zzz 1988 ! 3:07:04 - zzz # For backward compatibility... Link Asia/Riyadh87 Mideast/Riyadh87 diff -r -c old/solar88 new/solar88 *** old/solar88 Thu Apr 21 15:04:16 2005 --- new/solar88 Thu May 26 12:42:35 2005 *************** *** 1,4 **** ! # @(#)solar88 7.3 # Apparent noon times below are for Riyadh; they're a bit off for other places. # Times were computed using formulas in the U.S. Naval Observatory's --- 1,4 ---- ! # @(#)solar88 7.4 # Apparent noon times below are for Riyadh; they're a bit off for other places. # Times were computed using formulas in the U.S. Naval Observatory's *************** *** 381,388 **** # Before and after 1988, we'll operate on local mean solar time. # Zone NAME GMTOFF RULES/SAVE FORMAT [UNTIL] ! Zone Asia/Riyadh88 3:07:04 - ?? 1988 ! 3:07:04 sol88 ?? 1989 ! 3:07:04 - ?? # For backward compatibility... Link Asia/Riyadh88 Mideast/Riyadh88 --- 381,388 ---- # Before and after 1988, we'll operate on local mean solar time. # Zone NAME GMTOFF RULES/SAVE FORMAT [UNTIL] ! Zone Asia/Riyadh88 3:07:04 - zzz 1988 ! 3:07:04 sol88 zzz 1989 ! 3:07:04 - zzz # For backward compatibility... Link Asia/Riyadh88 Mideast/Riyadh88 diff -r -c old/solar89 new/solar89 *** old/solar89 Thu Apr 21 15:04:16 2005 --- new/solar89 Thu May 26 12:42:35 2005 *************** *** 1,4 **** ! # @(#)solar89 7.4 # Apparent noon times below are for Riyadh; they're a bit off for other places. # Times were computed using a formula provided by the U. S. Naval Observatory: --- 1,4 ---- ! # @(#)solar89 7.5 # Apparent noon times below are for Riyadh; they're a bit off for other places. # Times were computed using a formula provided by the U. S. Naval Observatory: *************** *** 386,393 **** # Before and after 1989, we'll operate on local mean solar time. # Zone NAME GMTOFF RULES/SAVE FORMAT [UNTIL] ! Zone Asia/Riyadh89 3:07:04 - ?? 1989 ! 3:07:04 sol89 ?? 1990 ! 3:07:04 - ?? # For backward compatibility... Link Asia/Riyadh89 Mideast/Riyadh89 --- 386,393 ---- # Before and after 1989, we'll operate on local mean solar time. # Zone NAME GMTOFF RULES/SAVE FORMAT [UNTIL] ! Zone Asia/Riyadh89 3:07:04 - zzz 1989 ! 3:07:04 sol89 zzz 1990 ! 3:07:04 - zzz # For backward compatibility... Link Asia/Riyadh89 Mideast/Riyadh89 diff -r -c old/zdump.c new/zdump.c *** old/zdump.c Mon Apr 4 11:24:32 2005 --- new/zdump.c Thu May 26 12:48:56 2005 *************** *** 1,4 **** ! static char elsieid[] = "@(#)zdump.c 7.64"; /* ** This code has been made independent of the rest of the time --- 1,4 ---- ! static char elsieid[] = "@(#)zdump.c 7.65"; /* ** This code has been made independent of the rest of the time *************** *** 144,151 **** --- 144,153 ---- static time_t absolute_max_time; static size_t longest; static char * progname; + static int warned; static char * abbr P((struct tm * tmp)); + static void abbrok P((const char * abbr, const char * zone)); static long delta P((struct tm * newp, struct tm * oldp)); static void dumptime P((const struct tm * tmp)); static time_t hunt P((char * name, time_t lot, time_t hit)); *************** *** 191,196 **** --- 193,236 ---- } #endif /* !defined TYPECHECK */ + static void + abbrok(abbr, zone) + const char * const abbr; + const char * const zone; + { + register int i; + register const char * cp; + register char * wp; + + if (warned) + return; + cp = abbr; + wp = NULL; + while (isascii(*cp) && isalpha(*cp)) + ++cp; + if (cp - abbr == 0) + wp = _("lacks alphabetic at start"); + if (cp - abbr < 3) + wp = _("has fewer than 3 alphabetics"); + if (cp - abbr > 6) + wp = _("has more than 6 alphabetics"); + if (wp == NULL && (*cp == '+' || *cp == '-')) { + ++cp; + if (isascii(*cp) && isdigit(*cp)) + if (*cp++ == '1' && *cp >= '0' && *cp <= '4') + ++cp; + } + if (*cp != '\0') + wp = _("differs from POSIX standard"); + if (wp == NULL) + return; + (void) fflush(stdout); + (void) fprintf(stderr, + "%s: warning: zone \"%s\" abbreviation \"%s\" %s\n", + progname, zone, abbr, wp); + warned = TRUE; + } + int main(argc, argv) int argc; *************** *** 297,302 **** --- 337,343 ---- show(argv[i], now, FALSE); continue; } + warned = FALSE; t = absolute_min_time; show(argv[i], t, TRUE); t += SECSPERHOUR * HOURSPERDAY; *************** *** 527,532 **** --- 568,575 ---- } } (void) printf("\n"); + if (tmp != NULL && *abbr(tmp) != '\0') + abbrok(abbr(tmp), zone); } static char * diff -r -c old/zic.c new/zic.c *** old/zic.c Mon Apr 4 11:24:32 2005 --- new/zic.c Thu May 26 14:54:07 2005 *************** *** 1,4 **** ! static char elsieid[] = "@(#)zic.c 7.122"; /* ** Regardless of the type of time_t, we do our work using this type. --- 1,4 ---- ! static char elsieid[] = "@(#)zic.c 7.124"; /* ** Regardless of the type of time_t, we do our work using this type. *************** *** 10,15 **** --- 10,19 ---- #include "locale.h" #include "tzfile.h" + #ifndef ZIC_MAX_ABBR_LEN_WO_WARN + #define ZIC_MAX_ABBR_LEN_WO_WARN 6 + #endif /* !defined ZIC_MAX_ABBR_LEN_WO_WARN */ + #if HAVE_SYS_STAT_H #include "sys/stat.h" #endif *************** *** 2196,2201 **** --- 2200,2240 ---- { register int i; + if (strcmp(string, GRANDPARENTED) != 0) { + register const char * cp; + register char * wp; + + /* + ** Want one to ZIC_MAX_ABBR_LEN_WO_WARN alphabetics + ** optionally followed by a + or - and a number from 1 to 14. + */ + cp = string; + wp = NULL; + while (isascii(*cp) && isalpha(*cp)) + ++cp; + if (cp - string == 0) + wp = _("time zone abbreviation lacks alphabetic at start"); + if (noise && cp - string > 3) + wp = _("time zone abbreviation has more than 3 alphabetics"); + if (cp - string > ZIC_MAX_ABBR_LEN_WO_WARN) + wp = _("time zone abbreviation has too many alphabetics"); + if (wp == NULL && (*cp == '+' || *cp == '-')) { + ++cp; + if (isascii(*cp) && isdigit(*cp)) + if (*cp++ == '1' && *cp >= '0' && *cp <= '4') + ++cp; + } + if (*cp != '\0') + wp = _("time zone abbreviation differs from POSIX standard"); + if (wp != NULL) { + wp = ecpyalloc(wp); + wp = ecatalloc(wp, " ("); + wp = ecatalloc(wp, string); + wp = ecatalloc(wp, ")"); + warning(wp); + ifree(wp); + } + } i = strlen(string) + 1; if (charcnt + i > TZ_MAX_CHARS) { error(_("too many, or too long, time zone abbreviations"));

12 34

revised proposed time zone abbreviation changes
by Arthur David Olson June 7, 2005

June 7, 2005

Thanks to folks for feedback on time zone abbreviation changes. Below find revised changes reflecting the feedback. The changes are relative to what's now available in the ftp directory. The revisions: 1. the set of characters allowed in time zone abbreviations has been expanded to include '.' (as in "E.S.T.") and '_' (on general principles). 2. the character substituted for those outside the approved set has been changed to '_' (a character which does not appear in any of the abbreviations that currently appear in the time zone data files). Regarding abbreviation lengths: I agree that some folks might want to use abbreviations shorter than three letters (in particular the old-style single-letter names for zones), so localtime.c is set up to allow fewer than three. It also allows up to 16 (covering abbreviations such as "XSTDST+hh:mm:ss" that Sun accepts). However, since the data files generated by zic might end up being used on systems with stricter requirements, it seems prudent to issue warnings (note: not errors) regarding short and long abbreviations. --ado diff -r -c old/Makefile new/Makefile *** old/Makefile Mon Apr 4 11:24:31 2005 --- new/Makefile Thu May 26 12:42:13 2005 *************** *** 1,4 **** ! # @(#)Makefile 7.108 # Change the line below for your time zone (after finding the zone you want in # the time zone files, or adding it to a time zone file). --- 1,4 ---- ! # @(#)Makefile 7.109 # Change the line below for your time zone (after finding the zone you want in # the time zone files, or adding it to a time zone file). *************** *** 111,117 **** # -DNO_RUN_TIME_WARNINGS_ABOUT_YEAR_2000_PROBLEMS_THANK_YOU=1 # if you do not want run time warnings about formats that may cause # year 2000 grief ! # GCC_DEBUG_FLAGS = -Dlint -g -O -fno-common \ -Wall -Wcast-qual -Wconversion -Wmissing-prototypes \ -Wnested-externs -Wpointer-arith -Wshadow \ --- 111,119 ---- # -DNO_RUN_TIME_WARNINGS_ABOUT_YEAR_2000_PROBLEMS_THANK_YOU=1 # if you do not want run time warnings about formats that may cause # year 2000 grief ! # -DZIC_MAX_ABBR_LEN_WO_WARN=3 ! # (or some other number) to set the maximum time zone abbreviation length ! # that zic will accept without a warning (the default is 6) GCC_DEBUG_FLAGS = -Dlint -g -O -fno-common \ -Wall -Wcast-qual -Wconversion -Wmissing-prototypes \ -Wnested-externs -Wpointer-arith -Wshadow \ diff -r -c old/localtime.c new/localtime.c *** old/localtime.c Mon Apr 4 11:24:32 2005 --- new/localtime.c Mon Jun 6 11:12:54 2005 *************** *** 5,11 **** #ifndef lint #ifndef NOID ! static char elsieid[] = "@(#)localtime.c 7.91"; #endif /* !defined NOID */ #endif /* !defined lint */ --- 5,11 ---- #ifndef lint #ifndef NOID ! static char elsieid[] = "@(#)localtime.c 7.94"; #endif /* !defined NOID */ #endif /* !defined lint */ *************** *** 22,27 **** --- 22,40 ---- #include "fcntl.h" #include "float.h" /* for FLT_MAX and DBL_MAX */ + #ifndef TZ_ABBR_MAX_LEN + #define TZ_ABBR_MAX_LEN 16 + #endif /* !defined TZ_ABBR_MAX_LEN */ + + #ifndef TZ_ABBR_CHAR_SET + #define TZ_ABBR_CHAR_SET \ + "abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789 :+-._" + #endif /* !defined TZ_ABBR_CHAR_SET */ + + #ifndef TZ_ABBR_ERR_CHAR + #define TZ_ABBR_ERR_CHAR '_' + #endif /* !defined TZ_ABBR_ERR_CHAR */ + /* ** SunOS 4.1.1 headers lack O_BINARY. */ *************** *** 124,129 **** --- 137,143 ---- static long detzcode P((const char * codep)); static const char * getzname P((const char * strp)); + static const char * getqzname P((const char * strp, const char delim)); static const char * getnum P((const char * strp, int * nump, int min, int max)); static const char * getsecs P((const char * strp, long * secsp)); *************** *** 269,274 **** --- 283,306 ---- tzname[ttisp->tt_isdst] = &sp->chars[ttisp->tt_abbrind]; } + /* + ** Finally, scrub the abbreviations. + ** First, replace bogus characters. + */ + for (i = 0; i < sp->charcnt; ++i) + if (strchr(TZ_ABBR_CHAR_SET, sp->chars[i]) == NULL) + sp->chars[i] = TZ_ABBR_ERR_CHAR; + /* + ** Second, truncate long abbreviations. + */ + for (i = 0; i < sp->typecnt; ++i) { + register const struct ttinfo * const ttisp = &sp->ttis[i]; + register char * cp = &sp->chars[ttisp->tt_abbrind]; + + if (strlen(cp) > TZ_ABBR_MAX_LEN && + strcmp(cp, GRANDPARENTED) != 0) + *(cp + TZ_ABBR_MAX_LEN) = '\0'; + } } static int *************** *** 470,475 **** --- 502,528 ---- } /* + ** Given a pointer into an extended time zone string, scan until the ending + ** delimiter of the zone name is located. Return a pointer to the delimiter. + ** + ** As with getzname above, the legal character set is actually quite + ** restricted, with other characters producing undefined results. + ** We choose not to care - allowing almost anything to be in the zone abbrev. + */ + + static const char * + getqzname(strp, delim) + register const char * strp; + const char delim; + { + register char c; + + while ((c = *strp) != '\0' && c != delim) + ++strp; + return strp; + } + + /* ** Given a pointer into a time zone string, extract a number from that string. ** Check that the number is within a specified range; if it is not, return ** NULL. *************** *** 753,760 **** stdlen = (sizeof sp->chars) - 1; stdoffset = 0; } else { ! name = getzname(name); ! stdlen = name - stdname; if (stdlen < 3) return -1; if (*name == '\0') --- 806,823 ---- stdlen = (sizeof sp->chars) - 1; stdoffset = 0; } else { ! if (*name == '<') { ! name++; ! stdname = name; ! name = getqzname(name, '>'); ! if (*name != '>') ! return (-1); ! stdlen = name - stdname; ! name++; ! } else { ! name = getzname(name); ! stdlen = name - stdname; ! } if (stdlen < 3) return -1; if (*name == '\0') *************** *** 767,775 **** if (load_result != 0) sp->leapcnt = 0; /* so, we're off a little */ if (*name != '\0') { ! dstname = name; ! name = getzname(name); ! dstlen = name - dstname; /* length of DST zone name */ if (dstlen < 3) return -1; if (*name != '\0' && *name != ',' && *name != ';') { --- 830,847 ---- if (load_result != 0) sp->leapcnt = 0; /* so, we're off a little */ if (*name != '\0') { ! if (*name == '<') { ! dstname = ++name; ! name = getqzname(name, '>'); ! if (*name != '>') ! return -1; ! dstlen = name - dstname; ! name++; ! } else { ! dstname = name; ! name = getzname(name); ! dstlen = name - dstname; /* length of DST zone name */ ! } if (dstlen < 3) return -1; if (*name != '\0' && *name != ',' && *name != ';') { diff -r -c old/private.h new/private.h *** old/private.h Mon Apr 4 11:24:32 2005 --- new/private.h Thu May 26 14:54:07 2005 *************** *** 25,30 **** --- 25,32 ---- #endif /* !defined NOID */ #endif /* !defined lint */ + #define GRANDPARENTED "Local time zone must be set--see zic manual page" + /* ** Defaults for preprocessor symbols. ** You can override these in your C compiler options, e.g. `-DHAVE_ADJTIME=0'. diff -r -c old/solar87 new/solar87 *** old/solar87 Thu Apr 21 15:04:16 2005 --- new/solar87 Thu May 26 12:42:35 2005 *************** *** 1,4 **** ! # @(#)solar87 7.3 # So much for footnotes about Saudi Arabia. # Apparent noon times below are for Riyadh; your mileage will vary. --- 1,4 ---- ! # @(#)solar87 7.4 # So much for footnotes about Saudi Arabia. # Apparent noon times below are for Riyadh; your mileage will vary. *************** *** 381,388 **** # Before and after 1987, we'll operate on local mean solar time. # Zone NAME GMTOFF RULES/SAVE FORMAT [UNTIL] ! Zone Asia/Riyadh87 3:07:04 - ?? 1987 ! 3:07:04 sol87 ?? 1988 ! 3:07:04 - ?? # For backward compatibility... Link Asia/Riyadh87 Mideast/Riyadh87 --- 381,388 ---- # Before and after 1987, we'll operate on local mean solar time. # Zone NAME GMTOFF RULES/SAVE FORMAT [UNTIL] ! Zone Asia/Riyadh87 3:07:04 - zzz 1987 ! 3:07:04 sol87 zzz 1988 ! 3:07:04 - zzz # For backward compatibility... Link Asia/Riyadh87 Mideast/Riyadh87 diff -r -c old/solar88 new/solar88 *** old/solar88 Thu Apr 21 15:04:16 2005 --- new/solar88 Thu May 26 12:42:35 2005 *************** *** 1,4 **** ! # @(#)solar88 7.3 # Apparent noon times below are for Riyadh; they're a bit off for other places. # Times were computed using formulas in the U.S. Naval Observatory's --- 1,4 ---- ! # @(#)solar88 7.4 # Apparent noon times below are for Riyadh; they're a bit off for other places. # Times were computed using formulas in the U.S. Naval Observatory's *************** *** 381,388 **** # Before and after 1988, we'll operate on local mean solar time. # Zone NAME GMTOFF RULES/SAVE FORMAT [UNTIL] ! Zone Asia/Riyadh88 3:07:04 - ?? 1988 ! 3:07:04 sol88 ?? 1989 ! 3:07:04 - ?? # For backward compatibility... Link Asia/Riyadh88 Mideast/Riyadh88 --- 381,388 ---- # Before and after 1988, we'll operate on local mean solar time. # Zone NAME GMTOFF RULES/SAVE FORMAT [UNTIL] ! Zone Asia/Riyadh88 3:07:04 - zzz 1988 ! 3:07:04 sol88 zzz 1989 ! 3:07:04 - zzz # For backward compatibility... Link Asia/Riyadh88 Mideast/Riyadh88 diff -r -c old/solar89 new/solar89 *** old/solar89 Thu Apr 21 15:04:16 2005 --- new/solar89 Thu May 26 12:42:35 2005 *************** *** 1,4 **** ! # @(#)solar89 7.4 # Apparent noon times below are for Riyadh; they're a bit off for other places. # Times were computed using a formula provided by the U. S. Naval Observatory: --- 1,4 ---- ! # @(#)solar89 7.5 # Apparent noon times below are for Riyadh; they're a bit off for other places. # Times were computed using a formula provided by the U. S. Naval Observatory: *************** *** 386,393 **** # Before and after 1989, we'll operate on local mean solar time. # Zone NAME GMTOFF RULES/SAVE FORMAT [UNTIL] ! Zone Asia/Riyadh89 3:07:04 - ?? 1989 ! 3:07:04 sol89 ?? 1990 ! 3:07:04 - ?? # For backward compatibility... Link Asia/Riyadh89 Mideast/Riyadh89 --- 386,393 ---- # Before and after 1989, we'll operate on local mean solar time. # Zone NAME GMTOFF RULES/SAVE FORMAT [UNTIL] ! Zone Asia/Riyadh89 3:07:04 - zzz 1989 ! 3:07:04 sol89 zzz 1990 ! 3:07:04 - zzz # For backward compatibility... Link Asia/Riyadh89 Mideast/Riyadh89 diff -r -c old/zdump.c new/zdump.c *** old/zdump.c Mon Apr 4 11:24:32 2005 --- new/zdump.c Thu May 26 12:48:56 2005 *************** *** 1,4 **** ! static char elsieid[] = "@(#)zdump.c 7.64"; /* ** This code has been made independent of the rest of the time --- 1,4 ---- ! static char elsieid[] = "@(#)zdump.c 7.65"; /* ** This code has been made independent of the rest of the time *************** *** 144,151 **** --- 144,153 ---- static time_t absolute_max_time; static size_t longest; static char * progname; + static int warned; static char * abbr P((struct tm * tmp)); + static void abbrok P((const char * abbr, const char * zone)); static long delta P((struct tm * newp, struct tm * oldp)); static void dumptime P((const struct tm * tmp)); static time_t hunt P((char * name, time_t lot, time_t hit)); *************** *** 191,196 **** --- 193,236 ---- } #endif /* !defined TYPECHECK */ + static void + abbrok(abbr, zone) + const char * const abbr; + const char * const zone; + { + register int i; + register const char * cp; + register char * wp; + + if (warned) + return; + cp = abbr; + wp = NULL; + while (isascii(*cp) && isalpha(*cp)) + ++cp; + if (cp - abbr == 0) + wp = _("lacks alphabetic at start"); + if (cp - abbr < 3) + wp = _("has fewer than 3 alphabetics"); + if (cp - abbr > 6) + wp = _("has more than 6 alphabetics"); + if (wp == NULL && (*cp == '+' || *cp == '-')) { + ++cp; + if (isascii(*cp) && isdigit(*cp)) + if (*cp++ == '1' && *cp >= '0' && *cp <= '4') + ++cp; + } + if (*cp != '\0') + wp = _("differs from POSIX standard"); + if (wp == NULL) + return; + (void) fflush(stdout); + (void) fprintf(stderr, + "%s: warning: zone \"%s\" abbreviation \"%s\" %s\n", + progname, zone, abbr, wp); + warned = TRUE; + } + int main(argc, argv) int argc; *************** *** 297,302 **** --- 337,343 ---- show(argv[i], now, FALSE); continue; } + warned = FALSE; t = absolute_min_time; show(argv[i], t, TRUE); t += SECSPERHOUR * HOURSPERDAY; *************** *** 527,532 **** --- 568,575 ---- } } (void) printf("\n"); + if (tmp != NULL && *abbr(tmp) != '\0') + abbrok(abbr(tmp), zone); } static char * diff -r -c old/zic.c new/zic.c *** old/zic.c Mon Apr 4 11:24:32 2005 --- new/zic.c Thu May 26 14:54:07 2005 *************** *** 1,4 **** ! static char elsieid[] = "@(#)zic.c 7.122"; /* ** Regardless of the type of time_t, we do our work using this type. --- 1,4 ---- ! static char elsieid[] = "@(#)zic.c 7.124"; /* ** Regardless of the type of time_t, we do our work using this type. *************** *** 10,15 **** --- 10,19 ---- #include "locale.h" #include "tzfile.h" + #ifndef ZIC_MAX_ABBR_LEN_WO_WARN + #define ZIC_MAX_ABBR_LEN_WO_WARN 6 + #endif /* !defined ZIC_MAX_ABBR_LEN_WO_WARN */ + #if HAVE_SYS_STAT_H #include "sys/stat.h" #endif *************** *** 2196,2201 **** --- 2200,2240 ---- { register int i; + if (strcmp(string, GRANDPARENTED) != 0) { + register const char * cp; + register char * wp; + + /* + ** Want one to ZIC_MAX_ABBR_LEN_WO_WARN alphabetics + ** optionally followed by a + or - and a number from 1 to 14. + */ + cp = string; + wp = NULL; + while (isascii(*cp) && isalpha(*cp)) + ++cp; + if (cp - string == 0) + wp = _("time zone abbreviation lacks alphabetic at start"); + if (noise && cp - string > 3) + wp = _("time zone abbreviation has more than 3 alphabetics"); + if (cp - string > ZIC_MAX_ABBR_LEN_WO_WARN) + wp = _("time zone abbreviation has too many alphabetics"); + if (wp == NULL && (*cp == '+' || *cp == '-')) { + ++cp; + if (isascii(*cp) && isdigit(*cp)) + if (*cp++ == '1' && *cp >= '0' && *cp <= '4') + ++cp; + } + if (*cp != '\0') + wp = _("time zone abbreviation differs from POSIX standard"); + if (wp != NULL) { + wp = ecpyalloc(wp); + wp = ecatalloc(wp, " ("); + wp = ecatalloc(wp, string); + wp = ecatalloc(wp, ")"); + warning(wp); + ifree(wp); + } + } i = strlen(string) + 1; if (charcnt + i > TZ_MAX_CHARS) { error(_("too many, or too long, time zone abbreviations"));

2 1

Re: 64-bit work
by Robbin Kawabata June 1, 2005

June 1, 2005

> From: "Olson, Arthur David (NIH/NCI)" <olsona(a)dc37a.nci.nih.gov> > To: "Tz (tz(a)elsie.nci.nih.gov)" <tz(a)lecserver.nci.nih.gov> > Subject: 64-bit work > Date: Mon, 23 May 2005 10:36:03 -0400 > > Since the 5-byte (rather than 8-byte) extension to the time zone binary data > file format went over with an overwhelming thud, my current thinking is to > stick revert to the 8-byte approach. > > The name of the game would be to produce binary files with: > 1. data with 32-bit time values through 2037 (for use by old > systems) > 2. data with 64-bit time values for "historic" years Can you describe what 2. is? Is it 400 years of times below the year of the earliest rule? If so, could the algorithm approach be used for the early past too? > 3. a newline enclosed, POSIX-conforming > TZ-environment-variable-style string > telling what to do in years beyond those covered by 2 above. > > There are a few places (Cairo, Godthab, Chile) that can't be represented by > POSIX-conforming strings; for these we'd punt to the "write 400 years worth > of data and work modulo 400" approach (leaving off the trailing TZ string). I'm not sure what the problem is with those timezones. Can you explain? Robbin

1 0

DST rules for Poland: corrections for 1946-1949 and 1988-1998
by Przemyslaw Augustyniak May 30, 2005

May 30, 2005

Tzdata 2005i has two minor inaccuracies in historical DST rules for Poland: * 1946-1949 DST transition dates are partially incorrect, see patch below. * Poland reintroduced DST in 1977, together with European Economic Community, but with DST transitions 1h behind EC ones. This difference is incorrectly listed as being dropped only as late as in 1999, rather than in 1988. Sources: * Kazimierz M. Borkowski, "Wszystko o czasie" <http://www.astro.uni.torun.pl/~kb/Artykuly/U-PA/Czas2.htm#tth_tAb1> * Druk nr 2180 - o czasie urzędowym na obszarze Rzeczypospolitej Polskiej <http://www.senat.gov.pl/k5/dok/sejm/053/2180.pdf> * Uchwała nr 29 Rady Ministrów z dnia 7 marca 1995 r. w sprawie wprowadzenia czasu letniego i zimowego w 1995 r. [M.P. 1995 nr 13 poz. 162] <http://www.abc.com.pl/serwis/mp/1995/0162.htm> You are welcome to contact me if you have any questions. I'm not on the list, so please CC me when replying. Przemysław Augustyniak --- europe.2005i 2005-04-21 21:04:15.000000000 +0200 +++ europe 2005-05-28 13:32:51.555884081 +0200 @@ -1686,19 +1686,23 @@ # For 1944-1948 Whitman gives the previous day; go with Shanks. Rule Poland 1945 only - Apr 29 0:00 1:00 S Rule Poland 1945 only - Nov 1 0:00 0 - -Rule Poland 1946 only - Apr 14 0:00 1:00 S -Rule Poland 1946 only - Sep 7 0:00 0 - -Rule Poland 1947 only - May 4 0:00 1:00 S -Rule Poland 1947 1948 - Oct Sun>=1 0:00 0 - -Rule Poland 1948 only - Apr 18 0:00 1:00 S -# Whitman also gives 1949 Apr 9 - 1949 Oct 1; go with Shanks. +# dr Kazimierz M. Borkowski +# Torun Centre for Astronomy of Nicolaus Copernicus University +# Department of Radio Astronomy +# <http://www.astro.uni.torun.pl/~kb/Artykuly/U-PA/Czas2.htm#tth_tAb1> +Rule Poland 1946 only - Apr 14 0:00s 1:00 S +Rule Poland 1946 only - Oct 7 2:00s 0 - +Rule Poland 1947 only - May 4 2:00s 1:00 S +Rule Poland 1947 1949 - Oct Sun>=1 2:00s 0 - +Rule Poland 1948 only - Apr 18 2:00s 1:00 S +Rule Poland 1949 only - Apr 10 2:00s 1:00 S Rule Poland 1957 only - Jun 2 1:00s 1:00 S Rule Poland 1957 1958 - Sep lastSun 1:00s 0 - Rule Poland 1958 only - Mar 30 1:00s 1:00 S Rule Poland 1959 only - May 31 1:00s 1:00 S Rule Poland 1959 1961 - Oct Sun>=1 1:00s 0 - Rule Poland 1960 only - Apr 3 1:00s 1:00 S -Rule Poland 1961 1964 - May Sun>=25 1:00s 1:00 S +Rule Poland 1961 1964 - May lastSun 1:00s 1:00 S Rule Poland 1962 1964 - Sep lastSun 1:00s 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Warsaw 1:24:00 - LMT 1880 @@ -1707,24 +1711,8 @@ 2:00 Poland EE%sT 1922 Jun 1:00 Poland CE%sT 1940 Jun 23 2:00 1:00 C-Eur CE%sT 1944 Oct - 1:00 Poland CE%sT 1977 Apr 3 1:00 - 1:00 W-Eur CE%sT 1999 -# IATA SSIM (1991/1996) gives EU rules, but the _The Warsaw Voice_ -# <a href="http://www.warsawvoice.com.pl/v361/NewsInBrief.shtml"> -# http://www.warsawvoice.com/pl/v361/NewsInBrief.shtml (1995-09-24) -# </a> -# says the autumn 1995 switch was at 02:00. -# Stick with W-Eur for now. -# -# From Marcin.Kasperski(a)softax.com.pl (1999-06-10): -# According to my colleagues someone recently decided, that Poland would -# follow European Union regulations, so - I think - the matter is not -# worth further discussion. -# -# From Paul Eggert (1999-06-10): -# Kasperski also writes that the government futzed with the rules in 1997 -# or 1998 but he doesn't remember the details. Assume they switched to -# EU rules in 1999. + 1:00 Poland CE%sT 1977 + 1:00 W-Eur CE%sT 1988 1:00 EU CE%sT # Portugal

1 0

FW: Web pages using recent versions of the tz database
by Olson, Arthur David (NIH/NCI) May 26, 2005

May 26, 2005

Paul/Kate is not on the time zone mailing list; direct replies appropriately. (And...what are the odds on "Thank you in advance for your time" being intentionally humorous?) --ado From: paul [mailto:paul@world-stay.com] Sent: Wednesday, May 25, 2005 9:43 AM To: tz(a)lecserver.nci.nih.gov Subject: Web pages using recent versions of the tz database I thought you may be interested in placing a link on your site to our home page as we use the tz database to display times around the world. We provide information about the time in locations all over the world, including daylight maps, sunrise and sunset times and free clocks that can be added to a web page by simply pasting a few lines of HTML code. Please have a look at the site http://time.world-stay.com/en/ , any feedback is always gratefully received. Thank you in advance for your time, Kate http://time.world-stay.com/

1 0

Web pages using recent versions of the tz database
by paul May 25, 2005

May 25, 2005

I thought you may be interested in placing a link on your site to our home page as we use the tz database to display times around the world. We provide information about the time in locations all over the world, including daylight maps, sunrise and sunset times and free clocks that can be added to a web page by simply pasting a few lines of HTML code. Please have a look at the site http://time.world-stay.com/en/ , any feedback is always gratefully received. Thank you in advance for your time, Kate http://time.world-stay.com/

1 0

zic warnings about odd time zone abbreviations
by Arthur David Olson May 24, 2005

May 24, 2005

Here are changes to zic.c to produce warnings about non-POSIX time zone abbreviations. I've also included changes to the "solar" files to use a POSIX-compliant "zzz" abbreviation (rather than the non-compliant "??") for the zone whose name we don't know. --ado ------- Makefile ------- *** /tmp/geta10569 Tue May 24 13:21:00 2005 --- /tmp/getb10569 Tue May 24 13:21:00 2005 *************** *** 1,4 **** ! # @(#)Makefile 7.108 # Change the line below for your time zone (after finding the zone you want in # the time zone files, or adding it to a time zone file). --- 1,4 ---- ! # @(#)Makefile 7.109 # Change the line below for your time zone (after finding the zone you want in # the time zone files, or adding it to a time zone file). *************** *** 111,117 **** # -DNO_RUN_TIME_WARNINGS_ABOUT_YEAR_2000_PROBLEMS_THANK_YOU=1 # if you do not want run time warnings about formats that may cause # year 2000 grief ! # GCC_DEBUG_FLAGS = -Dlint -g -O -fno-common \ -Wall -Wcast-qual -Wconversion -Wmissing-prototypes \ -Wnested-externs -Wpointer-arith -Wshadow \ --- 111,119 ---- # -DNO_RUN_TIME_WARNINGS_ABOUT_YEAR_2000_PROBLEMS_THANK_YOU=1 # if you do not want run time warnings about formats that may cause # year 2000 grief ! # -DZIC_MAX_ABBR_LEN_WO_WARN=3 ! # (or some other number) to set the maximum time zone abbreviation length ! # that zic will accept without a warning (the default is 6) GCC_DEBUG_FLAGS = -Dlint -g -O -fno-common \ -Wall -Wcast-qual -Wconversion -Wmissing-prototypes \ -Wnested-externs -Wpointer-arith -Wshadow \ ------- zic.c ------- *** /tmp/geta10785 Tue May 24 13:32:28 2005 --- /tmp/getb10785 Tue May 24 13:32:29 2005 *************** *** 1,4 **** ! static char elsieid[] = "@(#)zic.c 7.122"; /* ** Regardless of the type of time_t, we do our work using this type. --- 1,4 ---- ! static char elsieid[] = "@(#)zic.c 7.123"; /* ** Regardless of the type of time_t, we do our work using this type. *************** *** 10,15 **** --- 10,21 ---- #include "locale.h" #include "tzfile.h" + #define GRANDPARENTED "Local time zone must be set--see zic manual page" + + #ifndef ZIC_MAX_ABBR_LEN_WO_WARN + #define ZIC_MAX_ABBR_LEN_WO_WARN 6 + #endif /* !defined ZIC_MAX_ABBR_LEN_WO_WARN */ + #if HAVE_SYS_STAT_H #include "sys/stat.h" #endif *************** *** 2196,2201 **** --- 2202,2242 ---- { register int i; + if (strcmp(string, GRANDPARENTED) != 0) { + register const char * cp; + register char * wp; + + /* + ** Want one to ZIC_MAX_ABBR_LEN_WO_WARN alphabetics + ** optionally followed by a + or - and a number from 1 to 14. + */ + cp = string; + wp = NULL; + while (isascii(*cp) && isalpha(*cp)) + ++cp; + if (cp - string == 0) + wp = _("time zone abbreviation lacks alphabetic at start"); + if (noise && cp - string > 3) + wp = _("time zone abbreviation has more than 3 alphabetics"); + if (cp - string > ZIC_MAX_ABBR_LEN_WO_WARN) + wp = _("time zone abbreviation has too many alphabetics"); + if (wp == NULL && (*cp == '+' || *cp == '-')) { + ++cp; + if (isascii(*cp) && isdigit(*cp)) + if (*cp++ == '1' && *cp >= '0' && *cp <= '4') + ++cp; + } + if (*cp != '\0') + wp = _("time zone abbreviation differs from POSIX standard"); + if (wp != NULL) { + wp = ecpyalloc(wp); + wp = ecatalloc(wp, " ("); + wp = ecatalloc(wp, string); + wp = ecatalloc(wp, ")"); + warning(wp); + ifree(wp); + } + } i = strlen(string) + 1; if (charcnt + i > TZ_MAX_CHARS) { error(_("too many, or too long, time zone abbreviations")); ------- solar87 ------- *** /tmp/geta10623 Tue May 24 13:21:32 2005 --- /tmp/getb10623 Tue May 24 13:21:32 2005 *************** *** 1,4 **** ! # @(#)solar87 7.3 # So much for footnotes about Saudi Arabia. # Apparent noon times below are for Riyadh; your mileage will vary. --- 1,4 ---- ! # @(#)solar87 7.4 # So much for footnotes about Saudi Arabia. # Apparent noon times below are for Riyadh; your mileage will vary. *************** *** 381,388 **** # Before and after 1987, we'll operate on local mean solar time. # Zone NAME GMTOFF RULES/SAVE FORMAT [UNTIL] ! Zone Asia/Riyadh87 3:07:04 - ?? 1987 ! 3:07:04 sol87 ?? 1988 ! 3:07:04 - ?? # For backward compatibility... Link Asia/Riyadh87 Mideast/Riyadh87 --- 381,388 ---- # Before and after 1987, we'll operate on local mean solar time. # Zone NAME GMTOFF RULES/SAVE FORMAT [UNTIL] ! Zone Asia/Riyadh87 3:07:04 - zzz 1987 ! 3:07:04 sol87 zzz 1988 ! 3:07:04 - zzz # For backward compatibility... Link Asia/Riyadh87 Mideast/Riyadh87 ------- solar88 ------- *** /tmp/geta10642 Tue May 24 13:21:36 2005 --- /tmp/getb10642 Tue May 24 13:21:36 2005 *************** *** 1,4 **** ! # @(#)solar88 7.3 # Apparent noon times below are for Riyadh; they're a bit off for other places. # Times were computed using formulas in the U.S. Naval Observatory's --- 1,4 ---- ! # @(#)solar88 7.4 # Apparent noon times below are for Riyadh; they're a bit off for other places. # Times were computed using formulas in the U.S. Naval Observatory's *************** *** 381,388 **** # Before and after 1988, we'll operate on local mean solar time. # Zone NAME GMTOFF RULES/SAVE FORMAT [UNTIL] ! Zone Asia/Riyadh88 3:07:04 - ?? 1988 ! 3:07:04 sol88 ?? 1989 ! 3:07:04 - ?? # For backward compatibility... Link Asia/Riyadh88 Mideast/Riyadh88 --- 381,388 ---- # Before and after 1988, we'll operate on local mean solar time. # Zone NAME GMTOFF RULES/SAVE FORMAT [UNTIL] ! Zone Asia/Riyadh88 3:07:04 - zzz 1988 ! 3:07:04 sol88 zzz 1989 ! 3:07:04 - zzz # For backward compatibility... Link Asia/Riyadh88 Mideast/Riyadh88 ------- solar89 ------- *** /tmp/geta10661 Tue May 24 13:21:44 2005 --- /tmp/getb10661 Tue May 24 13:21:44 2005 *************** *** 1,4 **** ! # @(#)solar89 7.4 # Apparent noon times below are for Riyadh; they're a bit off for other places. # Times were computed using a formula provided by the U. S. Naval Observatory: --- 1,4 ---- ! # @(#)solar89 7.5 # Apparent noon times below are for Riyadh; they're a bit off for other places. # Times were computed using a formula provided by the U. S. Naval Observatory: *************** *** 386,393 **** # Before and after 1989, we'll operate on local mean solar time. # Zone NAME GMTOFF RULES/SAVE FORMAT [UNTIL] ! Zone Asia/Riyadh89 3:07:04 - ?? 1989 ! 3:07:04 sol89 ?? 1990 ! 3:07:04 - ?? # For backward compatibility... Link Asia/Riyadh89 Mideast/Riyadh89 --- 386,393 ---- # Before and after 1989, we'll operate on local mean solar time. # Zone NAME GMTOFF RULES/SAVE FORMAT [UNTIL] ! Zone Asia/Riyadh89 3:07:04 - zzz 1989 ! 3:07:04 sol89 zzz 1990 ! 3:07:04 - zzz # For backward compatibility... Link Asia/Riyadh89 Mideast/Riyadh89

2 1

64-bit zic -s
by Robbin Kawabata May 23, 2005

May 23, 2005

The new 64-bit time zic has the -s flag removed. Can you give some details about its removal - do machines that have signed time_t and unsigned time_t no longer need to share timezone files? Is -s no longer needed to pass SVVS? Also, is there any reason the -s could not be supported by the new 64-bit zic? We usually give a 1-year warning before we remove functionality, so we might add this option back into the 64-bit zic locally (with a note we plan to remove it in the next release). thanks, Robbin

1 0

64-bit work
by Olson, Arthur David (NIH/NCI) May 23, 2005

May 23, 2005

Since the 5-byte (rather than 8-byte) extension to the time zone binary data file format went over with an overwhelming thud, my current thinking is to stick revert to the 8-byte approach. The name of the game would be to produce binary files with: 1. data with 32-bit time values through 2037 (for use by old systems) 2. data with 64-bit time values for "historic" years 3. a newline enclosed, POSIX-conforming TZ-environment-variable-style string telling what to do in years beyond those covered by 2 above. There are a few places (Cairo, Godthab, Chile) that can't be represented by POSIX-conforming strings; for these we'd punt to the "write 400 years worth of data and work modulo 400" approach (leaving off the trailing TZ string). --ado

1 0

Re: Maintainer of timezone/zdump.c
by Paul Eggert May 21, 2005

May 21, 2005

"Earl C. Ruby III" <earl(a)switchmanagement.com> writes: > I am trying to locate the maintainer of the timezone/zdump.c program. tz(a)elsie.nci.nih.gov is it. I'm removing the other CC's. > I am running several dozen SuSE Linux systems and all of them show the same > (incorrect) results when zdump is run for an "Etc/UTC+X" timezone. The sign convention for Etc/UTC+X is purposely backwards from what you expected. > I've written a set of Perl timezone conversion routines which pull > data from zdump. I've added a patch to my software which works > around this problem with zdump, but I feel that zdump itself should > be fixed to deal with this. As far as I can see, zdump is correct, and so is zic. My advice is to stay away from those TZ=Etc/* settings. For details, please see the long comment in the etcetera file in the tz distribution.

2 1

Re: TZ environment variable
by Olson, Arthur David (NIH/NCI) May 20, 2005

May 20, 2005

If the TZ environment variable needs to be checked for mischief-making time zone abbreviations, the same check needs to be applied to values derived from time zone files (since, at least on some systems, users can create arbitrary files and arrange for them to be used with an appropriate TZ setting.) --ado

9 11

Mongolia 2005 (3)
by Oscar van Vlijmen May 20, 2005

May 20, 2005

From: Embassy of Mongolia, Washington, D.C. - Tourism http://www.mongolianembassy.us/eng_tourism/tourism.php "Time Difference Mongolia is 8 hours ahead of GMT in winter and 9 hours ahead in summer. The three western aimags of Mongolia , Uvs, Bayan Ulgii and Khovd are one hour behind Ulaanbaatar and the rest of Mongolia." I found nothing of importance yet on: http://www.open-government.mn/ Oscar van Vlijmen 2005-05-20

1 0

Re: TZ environment variable
by Robbin Kawabata May 19, 2005

May 19, 2005

There was some discussion about localized tznames. SunOS currently doesn't support localized tzname's. If we were to implement it, we would probably take the approach of i18n messages. We could create message catalogs for Olson timezone tznames, which contain translated tznames for the locales. A message-id could be created, perhaps by concatenating the timezone name with the tzname (for example, "America/Los_Angeles_PST"). The message-id could be passed to dcgettext(), which would return the localized tzname according to the locale specified by LC_TIME. We might use a new specifier in strftime() (which would call dcgettext()) to return the localized tzname or the original tzname if no localized tzname exists. We would keep the values of TZ and tzname[] as elements from the portable character set. The TZ environment variable is inherited by applications. By default applications start in the C locale. If a time function is called before setlocale() is done (or if the application does not call setlocale()), the time function could fail if TZ is composed of invalid characters for the C locale. Also, if TZ or tzname[] is composed of multibyte characters, and the application changes locales, it could invalidate those characters. Robbin

2 1

RE: Mongolia has two time zones GMT +7 and GMT +8 (DST GMT +8 and DST GMT +9)
by Bill Bonnett May 19, 2005

May 19, 2005

This is what I got from the U.S. Embassy in Ulaanbaatar: All of Mongolia is on one time zone. It is 13 hours ahead of Washington, D.C. or +8 GMT. Mongolia does observe daylight savings time. Ulaanbaatar (and Irkukst, Russia) share a time zone entry, with daylight savings time option, on Windows XP. _____ From: Risto Nykänen [mailto:ristonykanen@luukku.com] Sent: Monday, May 16, 2005 5:38 PM To: Contacts(a)abdicate.net Subject: Mongolia has two time zones GMT +7 and GMT +8 (DST GMT +8 and DST GMT +9) See next link: http://www.miat.com/frame.php?page=travel_information http://www.travelmongolia.org/ Risto P.S. GMT +9 (DST GMT +10) not anylonger in use.

1 0

Mongolia 2005 (2)
by Oscar van Vlijmen May 18, 2005

May 18, 2005

Further research seems to indicate that the situation in Mongolia is even more complicated. See for instance a very short article plus reader comments on: <http://ubpost.mongolnews.mn/index.php?subaction=showcomments&id=1111634894& archive=&start_from=&ucat=1&> The UB Post is Mongolias independent weekly news bulletin. The article, dated 23 Mar 2005, says: "Mongolia will observe daylight savings time on March 26. Clocks will be moved forward one hour at 2:00am" A reader comment notes that parliament has decided that there are now 4 time zones: OLGII in the west, on UTC+7 ULAT, most of the country, on UTC+8 ..., a couple of aimags in the east, on UTC+9 SUKH, the Sukhbaatar aimag, on UTC+8.5 The SUKH time zone is new. Oscar van Vlijmen 2005-05-18

1 0

RE: TZ environment variable
by Olson, Arthur David (NIH/NCI) May 18, 2005

May 18, 2005

To aid the discussion of the TZ environment variable, here's a list of the time zone abbreviations that currently show up in binary time zone files if you do a "make install". (I'll put in a vote for changing the mixed-case "ChST" to a mono-case "CHST".) --ado ?? ACT ADT AFT AMT ANT AOT APT ART AST AWT AZT BDT BMT BNT BOT BRT BST BTT CAT CCT CDT CET CGT CIT CJT CKT CLT CMT COT CPT CST CUT CVT CWT CXT DMT EAT ECT EDT EET EGT EIT EPT EST EWT FJT FKT FMT FNT GET GFT GMT GST GYT HDT HKT HMT HPT HST HWT ICT IDT IMT IOT IST JMT JST KDT KGT KMT KST LKT LMT LRT LST MDT MET MHT MMT MOT MPT MSD MSK MST MUT MVT MWT MYT NCT NDT NET NFT NMT NPT NRT NST NUT NWT PDT PET PGT PHT PKT PMT PNT PPT PST PWT PYT QMT RET RMT SBT SCT SGT SMT SRT SST TFT TJT TKT TMT TOT TPT TRT TVT UCT UTC UYT UZT VET VUT WAT WET WFT WGT WIT WMT WST YDT YPT YST YWT zzz ACST ADDT ADMT AHDT AHST AKDT AKST AKTT ALMT AMST ANAT AQTT ARST ASHT AZOT AZST BAKT BDST BEAT BORT BOST BRST BURT CANT CAST CAWT CDDT CEMT CEST CGST CHAT CHDT CHOT ChST CLST COST CVST DACT DAVT DDUT DUST EAST EDDT EEST EGST EHDT FFMT FJST FKST FNST FORT FRUT GALT GAMT GBGT GEST GHST GILT HADT HAST HKST HOVT IDDT IHST IRDT IRKT IRST ISST JAVT KART KAST KGST KIZT KOST KRAT KUYT KWAT LHST LINT LONT MADT MAGT MALT MART MAWT MDDT MDST MEST MOST NCST NDDT NEGT NEST NOVT NZDT NZMT NZST OMST ORAT PDDT PEST PETT PHOT PHST PKST PMDT PMST PONT PPMT PYST QYZT ROTT SAKT SAMT SAST SDMT SHET SJMT SLST SVET SWAT SYOT TAHT TAST TBIT TBMT TOST TRST TRUT ULAT URAT URUT UYST UZST VLAT VOST VUST WAKT WART WAST WEMT WEST WGST YAKT YAPT YDDT YEKT YERT AKTST ALMST ANAST AQTST ASHST AZOMT AZOST BAKST BEAUT CHADT CHAST CHOST CKHST DUSST EASST FRUST GMT+1 GMT+2 GMT+3 GMT+4 GMT+5 GMT+6 GMT+7 GMT+8 GMT+9 GMT-1 GMT-2 GMT-3 GMT-4 GMT-5 GMT-6 GMT-7 GMT-8 GMT-9 HOVST IRKST KIZST KRAST KUYST MADMT MADST MAGST MALST NOVST OMSST ORAST PETST QYZST SAKST SAMST SHEST SVEST TASST TBIST ULAST URAST UYHST VLAST WARST YAKST YEKST YERST BORTST GMT+10 GMT+11 GMT+12 GMT-10 GMT-11 GMT-12 GMT-13 GMT-14 VLASST Local time zone must be set--see zic manual page

3 2

[07]
by retornoviral May 17, 2005

May 17, 2005

1 0

Mongolia 2005
by Oscar van Vlijmen May 16, 2005

May 16, 2005

Several sources say Mongolia has only 2 time zones with DST. The TZ asia file says 3 time zones. http://www.travelmongolia.org/travel.mongolia/travel.info.html reads: " Time Difference Mongolia is 8 hours ahead of GMT in winter and 9 hours ahead in summer. The three western aimags of Mongolia, Uvs, Bayan Ulgii and Khovd are one hour behind Ulaanbaatar and the rest of Mongolia. " MIAT Mongolian Airlines (http://www.miat.com/frame.php?page=travel_information ) also speak of 2 time zones, as does the usually well informed worldtimeserver.com Does anybody have more evidence on the real situation? Oscar van Vlijmen 2005-05-16

1 0

Indiana
by Garrett Wollman May 16, 2005

May 16, 2005

According to press reports I've seen elsewhere, the governor of Indiana signed the bill putting the entire state on DST effective next year. The bill also requires the governor to petition USDOT to relocate the ET/CT boundary, although the reports I've seen were a bit unclear as to where the new boundary would be, if it is even specified in the bill. So I guess at a minimum the database should be updated to show America/Indiana/* on "US" rules starting 2006 Jan 1. -GAWollman

1 0

Time-Keeping at Sea [from Mark Brader]
by Paul Eggert May 15, 2005

May 15, 2005

[Forwarded from Mark Brader. Please note that he is not on the mailing list; replies should be directed accordingly.] From: msb(a)vex.net (Mark Brader) Subject: Time-Keeping at Sea To: eggert(a)twinsun.com Date: Sun, 15 May 2005 00:52:33 -0400 (EDT) Please forward this to the tz mailing list. I am not on the list; people should direct replies accordingly. Your "australasia" file has this from Gwillim Law (2000-01-03): # An Anglo-French Conference on Time-Keeping at Sea (June, 1917) agreed that # legal time on the high seas would be zone time ... A while back I emailed Gwillim to ask about his source for this statement. At the time he didn't remeber, but later he wrote back and told me that it was Howse's "Greenwich Time and the Longitude". Gwillim kindly transcribed the passage from Howse, saving me from finding where my copy is: | In June 1917, therefore, an Anglo-French Conference on Timekeeping at Sea | assembled in London. This recommended that the zone-time system should be | used at sea, clock changes required by changes of longitude being made | preferably in one-hour steps. This recommendation was immediately adopted by | British and French ships, both naval and mercantile. Ships of most other | nations soon followed suit so that, by a few years after the war, zone time | was kept at sea, certainly by almost all naval ships and by many non-naval | ships as well. Nevertheless, up to the Second World War, the old practice of | changing ship's time at midday prevailed in many independent merchant | ships. So if this is correct, the conference said nothing at all about *legal* time; they only recommended a practice. It also isn't clear from this passage whether the recommendation was for the change to happen when the specific meridian was actually crossed, or whether it was okay to do it at a convenient time so long as you did it in one-hour steps. (On the cruise ships I've been on, time zone changes were always done overnight.) It would be interesting to find the conference proceedings and see how the conclusion was actually expressed, and to know whether there actually is such a thing as legal time for some or all ships in international waters. -- Mark Brader | "Debugging had to be discovered. I can remember Toronto | the exact instant when I realized that a large part msb(a)vex.net | of my life... was going to be spent in finding | mistakes in my own programs." -- Maurice Wilkes

1 0