May 2005 - tz - lists.iana.org

proposed tz change for Latvia, Lithuania
by Paul Eggert May 25, 2015

May 25, 2015

It's March Madness time for daylight-saving rule changes. Here's a proposed change to the tz database to keep up with the latest political development, which affects time stamps starting March 29: * Latvia and Lithuania will not observe DST, starting this year. Thanks to Andrei Ivanov for this info. =================================================================== RCS file: RCS/europe,v retrieving revision 2000.3 retrieving revision 2000.3.0.1 diff -pu -r2000.3 -r2000.3.0.1 --- europe 2000/03/04 15:31:08 2000.3 +++ europe 2000/03/08 17:48:59 2000.3.0.1 @@ -1135,6 +1135,12 @@ Link Europe/Rome Europe/San_Marino # 1997-01-21 on transition to Summer time ... established the same order of # daylight savings time settings as in the States of the European Union. +# From Andrei Ivanov (2000-03-06): +# This year Latvia will not switch to Daylight Savings Time (as specified in +# <a href="http://www.lv-laiks.lv/wwwraksti/2000/071072/vd4.htm"> +# The Regulations of the Cabinet of Ministers of the Rep. of Latvia of +# 29-Feb-2000 (#79)</a>, in Latvian for subscribers only). + # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S Rule Latvia 1989 1996 - Mar lastSun 2:00s 1:00 S Rule Latvia 1989 1996 - Sep lastSun 2:00s 0 - @@ -1151,7 +1157,8 @@ Zone Europe/Riga 1:36:24 - LMT 1880 3:00 Russia MSK/MSD 1989 Mar lastSun 2:00s 2:00 1:00 EEST 1989 Sep lastSun 2:00s 2:00 Latvia EE%sT 1997 Jan 21 - 2:00 EU EE%sT + 2:00 EU EE%sT 2000 Feb 29 + 2:00 - EET # Liechtenstein # Zone NAME GMTOFF RULES FORMAT [UNTIL] @@ -1178,6 +1185,11 @@ Zone Europe/Vaduz 0:38:04 - LMT 1894 Jun # motion to give up shifting to summer time in spring, as it was # already done by Estonia. +# From Andrei Ivanov (2000-03-06): +# I've heard that Ministers of three Baltic countries on their summit +# somewhere in February decided not to switch to summer time starting from +# this spring. + # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Vilnius 1:41:16 - LMT 1880 1:24:00 - WMT 1917 # Warsaw Mean Time @@ -1192,7 +1204,8 @@ Zone Europe/Vilnius 1:41:16 - LMT 1880 2:00 C-Eur EE%sT 1998 2:00 - EET 1998 Mar 29 1:00u 1:00 EU CE%sT 1999 Oct 31 1:00u - 2:00 EU EE%sT + 2:00 EU EE%sT 2000 Feb + 2:00 - EET # Luxembourg # Whitman disagrees with most of these dates in minor ways; go with Shanks.

5 5

Australia - Broken Hill - Yancowinna
by Oscar van Vlijmen Dec. 16, 2006

Dec. 16, 2006

Broken Hill, or more precise, the whole county of Yancowinna, differs from the rest of New South Wales, as clearly stated in the TZ database. Problem is: what is the "county of Yancowinna"? The Australian Standard Time Act 1987 mentions this county, but doesn't mention the county boundaries. Once they were known, but they have disappeared from recent maps. Finally I found a scan of an old map from the Land Registry, showing the Yancowinna county. Found on the website of The Sydney Morning Herald: <http://www.smh.com.au/articles/2003/08/29/1062050651816.html?oneclick=true> Click on field number 2 or download the map directly: <http://www.smh.com.au/specials/leases/pdf/map2.pdf> The following places are within the county boundaries: Broken Hill, The Gorge, Mount Gipps, Silverton, Stephens Creek, Wahratta, Yanco Glen. The name "Wahratta" is not perfectly readable from the map, but I've checked the name and location against the Australia file from the GEOnet Names Server <http://earth-info.nga.mil/gns/> Oscar van Vlijmen 2005-04-23

4 8

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

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

FW: Kazakhstan has really two time zones
by Bill Bonnett May 12, 2005

May 12, 2005

I got this email from a wonderful helper. According to the embassy in the UK Kazakhstan only has 2 time zones, but like all info, it doesnt say WHERE the dividing line is _____ From: Risto Nykänen [mailto:ristonykanen@luukku.com] Sent: Tuesday, May 10, 2005 7:50 AM To: Contacts(a)abdicate.net Subject: Kazakhstan has really two time zones Hi, why do you not update information and show two times for Kazakhstan. See the next link: http://www.kazakhstanembassy.org.uk/cgi-bin/index/55 Risto from Helsinki P.S. Your map is also good, I like it and it put me to think about.

1 0

Re: TZ environment variable
by Paul Eggert May 10, 2005

May 10, 2005

matthew green <mrg(a)eterna.com.au> writes: > i think it must be lowered to at least 2 - i use "TZ=GB" in a script > somewhere... But we're talking about the length of the time zone abbreviation (e.g., "GMT" or "BST"), which is distinct from the length of the TZ string itself. Another check, which Garrett Wollman alluded to, is that the GMT offset should be "sane". For example, it's reasonable to reject settings like TZ="XXX9999999999". However, that leaves the issue of what is "sane". For example, Solaris 8 supports a wide range of "sane" offsets: $ date -u; TZ=XXX24:59:59 date; TZ=XXX444444 date Tue May 10 03:51:24 GMT 2005 Mon May 9 02:51:25 XXX 2005 Fri Aug 27 15:51:24 XXX 1954 but this has been tightened up in Solaris 10: $ date -u; TZ=XXX24:59:59 date; TZ=XXX444444 date Tue May 10 03:50:45 GMT 2005 Mon May 9 02:50:46 XXX 2005 Tue May 10 03:50:45 GMT 2005 I suspect this is for reasons similar to what Garrett Wollman mentioned. POSIX requires support only for UTC offsets in the range -24:59:59 through +24:59:59. (The implied daylight-saving UTC offset can be as high as +25:59:59.) The GNU C library supports only the POSIX range. I don't know the range that Solaris 10 supports.

2 1

Re: Back-of-the-envelope cost of extra data :-)
by Robbin Kawabata May 9, 2005

May 9, 2005

Amending my previous email of 5/3/05 (where I said either method is OK), our preference is the algorithmic approach. Here are some comparisons (using the smaller 5-byte time storage proposed 5/9/05 by ado). The 400-year method requires in a larger timezone file (was 1K, now 6K). localtime() requires 3K/5K (32/64 bit) more memory per process for the state struct. There is more setup processing to initialize 400-years of the ats[] table. It requires about .8MB more hard disk space for the total zoneinfo directory. All processes encounter the overhead, but most processes would not make use of it. The performance for 64-bit transitions is probably better, as it is table-driven. The algorithmic approach requires a smaller timezone file than the 400-year approach. Some number of extra bytes are needed to store the variables to be used by the algorithm (and more space needed for a small 64-bit transition table, if one is used). There is a little setup for initialization of variables that would be used by the algorithm (and more setup for the small 64-bit transition table, if one is used). Additional hard disk space is minimal (or somewhat less than the 400-year file if a small 64-bit transition table is used). Performance for 64-bit transitions (past the 64-bit transition table if one is used) would probably not be as good as the 400-year cycle approach. We prefer the algorithmic method because it requires less overhead with disk space, process memory space, and setup processing time. We feel the possible slower performance for 64-bit transitions is acceptable since most applications won't use 64-bit transitions. Robbin

1 0

Re: Back-of-the-envelope cost of extra data :-)
by Arthur David Olson May 9, 2005

May 9, 2005

One way to reduce data file growth is to store just 5 bytes of time_t values rather than 8. Since 32 bits buys about 70 years of time on each side of 1970, 40 bits buys about 256 times 70 or about 17920 years of time on each side of 1970. There will be a need to change the file format in the future (the Y20K problem). Recall that the eight-bit files resulted in a "du" report value of 1709. With the changes attached below in place, we get... Script started on Mon May 09 11:02:55 2005 du lecserver$ du -s -k tz/tmp/etc/zoneinfo tzexp/tmp/etc/zoneinfo 489 tz/tmp/etc/zoneinfo 1281 tzexp/tmp/etc/zoneinfo lecserver$ exit script done on Mon May 09 11:03:07 2005 ...meaning that about 35% of the increase has been eliminated. --ado ------- tzfile.5 ------- *** /tmp/geta29273 Mon May 9 11:01:02 2005 --- /tmp/getb29273 Mon May 9 11:01:02 2005 *************** *** 137,145 **** For version-2-format time zone files, the above header and data is followed by a second header and data, identical in format except that ! eight bytes are used for each transition time or leap second time. .SH SEE ALSO newctime(3) ! .\" @(#)tzfile.5 7.13 .\" This file is in the public domain, so clarified as of .\" 1996-06-05 by Arthur David Olson (arthur_david_olson(a)nih.gov) --- 137,145 ---- For version-2-format time zone files, the above header and data is followed by a second header and data, identical in format except that ! five bytes are used for each transition time or leap second time. .SH SEE ALSO newctime(3) ! .\" @(#)tzfile.5 7.14 .\" This file is in the public domain, so clarified as of .\" 1996-06-05 by Arthur David Olson (arthur_david_olson(a)nih.gov) ------- tzfile.h ------- *** /tmp/geta29292 Mon May 9 11:01:15 2005 --- /tmp/getb29292 Mon May 9 11:01:15 2005 *************** *** 21,27 **** #ifndef lint #ifndef NOID ! static char tzfilehid[] = "@(#)tzfile.h 7.19"; #endif /* !defined NOID */ #endif /* !defined lint */ --- 21,27 ---- #ifndef lint #ifndef NOID ! static char tzfilehid[] = "@(#)tzfile.h 7.20"; #endif /* !defined NOID */ #endif /* !defined lint */ *************** *** 87,93 **** /* ** If tzh_version is '2' or greater, the above is followed by a second instance ** of tzhead and a second instance of the data in which each coded transition ! ** time uses 8 rather than 4 chars. */ /* --- 87,93 ---- /* ** If tzh_version is '2' or greater, the above is followed by a second instance ** of tzhead and a second instance of the data in which each coded transition ! ** time uses 5 rather than 4 chars. */ /* ------- zic.c ------- *** /tmp/geta29311 Mon May 9 11:01:25 2005 --- /tmp/getb29311 Mon May 9 11:01:25 2005 *************** *** 1,4 **** ! static char elsieid[] = "@(#)zic.c 7.127"; #include "private.h" #include "locale.h" --- 1,4 ---- ! static char elsieid[] = "@(#)zic.c 7.128"; #include "private.h" #include "locale.h" *************** *** 99,105 **** static void associate P((void)); static int ciequal P((const char * ap, const char * bp)); static void convert P((long val, char * buf)); ! static void convert64 P((zic_t val, char * buf)); static void dolink P((const char * fromfile, const char * tofile)); static void doabbr P((char * abbr, const char * format, const char * letters, int isdst)); --- 99,105 ---- static void associate P((void)); static int ciequal P((const char * ap, const char * bp)); static void convert P((long val, char * buf)); ! static void convert40 P((zic_t val, char * buf)); static void dolink P((const char * fromfile, const char * tofile)); static void doabbr P((char * abbr, const char * format, const char * letters, int isdst)); *************** *** 128,134 **** static long oadd P((long t1, long t2)); static void outzone P((const struct zone * zp, int ntzones)); static void puttzcode P((long code, FILE * fp)); ! static void puttzcode64 P((zic_t code, FILE * fp)); static int rcomp P((const void * leftp, const void * rightp)); static zic_t rpytime P((const struct rule * rp, int wantedy)); static void rulesub P((struct rule * rp, --- 128,134 ---- static long oadd P((long t1, long t2)); static void outzone P((const struct zone * zp, int ntzones)); static void puttzcode P((long code, FILE * fp)); ! static void puttzcode40 P((zic_t code, FILE * fp)); static int rcomp P((const void * leftp, const void * rightp)); static zic_t rpytime P((const struct rule * rp, int wantedy)); static void rulesub P((struct rule * rp, *************** *** 1397,1403 **** } static void ! convert64(val, buf) const zic_t val; char * const buf; { --- 1397,1403 ---- } static void ! convert40(val, buf) const zic_t val; char * const buf; { *************** *** 1404,1410 **** register int i; register int shift; ! for (i = 0, shift = 56; i < 8; ++i, shift -= 8) buf[i] = val >> shift; } --- 1404,1410 ---- register int i; register int shift; ! for (i = 0, shift = 32; i < 5; ++i, shift -= 8) buf[i] = val >> shift; } *************** *** 1420,1432 **** } static void ! puttzcode64(val, fp) const zic_t val; FILE * const fp; { ! char buf[8]; ! convert64(val, buf); (void) fwrite((void *) buf, (size_t) sizeof buf, (size_t) 1, fp); } --- 1420,1432 ---- } static void ! puttzcode40(val, fp) const zic_t val; FILE * const fp; { ! char buf[5]; ! convert40(val, buf); (void) fwrite((void *) buf, (size_t) sizeof buf, (size_t) 1, fp); } *************** *** 1603,1609 **** for (i = thistimei; i < thistimelim; ++i) if (pass == 1) puttzcode((long) ats[i], fp); ! else puttzcode64(ats[i], fp); if (thistimecnt > 0) (void) fwrite((void *) &types[thistimei], (size_t) sizeof types[0], --- 1603,1609 ---- for (i = thistimei; i < thistimelim; ++i) if (pass == 1) puttzcode((long) ats[i], fp); ! else puttzcode40(ats[i], fp); if (thistimecnt > 0) (void) fwrite((void *) &types[thistimei], (size_t) sizeof types[0], *************** *** 1638,1645 **** todo = tadd(trans[i], -gmtoffs[j]); } else todo = trans[i]; if (pass == 1) ! puttzcode(todo, fp); ! else puttzcode64(todo, fp); puttzcode(corr[i], fp); } for (i = 0; i < typecnt; ++i) --- 1638,1645 ---- todo = tadd(trans[i], -gmtoffs[j]); } else todo = trans[i]; if (pass == 1) ! puttzcode((long) todo, fp); ! else puttzcode40(todo, fp); puttzcode(corr[i], fp); } for (i = 0; i < typecnt; ++i) ------- localtime.c ------- *** /tmp/geta29330 Mon May 9 11:01:36 2005 --- /tmp/getb29330 Mon May 9 11:01:36 2005 *************** *** 5,11 **** #ifndef lint #ifndef NOID ! static char elsieid[] = "@(#)localtime.c 7.92"; #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 */ *************** *** 125,131 **** */ static long detzcode P((const char * codep)); ! static time_t detzcode64 P((const char * codep)); static const char * getzname P((const char * strp)); static const char * getnum P((const char * strp, int * nump, int min, int max)); --- 125,131 ---- */ static long detzcode P((const char * codep)); ! static time_t detzcode40 P((const char * codep)); static const char * getzname P((const char * strp)); static const char * getnum P((const char * strp, int * nump, int min, int max)); *************** *** 225,231 **** } static time_t ! detzcode64(codep) const char * const codep; { register signed64_t result; --- 225,231 ---- } static time_t ! detzcode40(codep) const char * const codep; { register signed64_t result; *************** *** 232,238 **** register int i; result = (codep[0] & 0x80) ? ~0L : 0L; ! for (i = 0; i < 8; ++i) result = (result << 8) | (codep[i] & 0xff); return (time_t) result; } --- 232,238 ---- register int i; result = (codep[0] & 0x80) ? ~0L : 0L; ! for (i = 0; i < 5; ++i) result = (result << 8) | (codep[i] & 0xff); return (time_t) result; } *************** *** 343,349 **** nread = read(fid, u.buf, sizeof u.buf); if (close(fid) < 0 || nread <= 0) return -1; ! for (stored = 4; stored <= 8; stored *= 2) { int ttisstdcnt; int ttisgmtcnt; --- 343,349 ---- nread = read(fid, u.buf, sizeof u.buf); if (close(fid) < 0 || nread <= 0) return -1; ! for (stored = 4; stored <= 5; ++stored) { int ttisstdcnt; int ttisgmtcnt; *************** *** 372,378 **** return -1; for (i = 0; i < sp->timecnt; ++i) { sp->ats[i] = (stored == 4) ? ! detzcode(p) : detzcode64(p); p += stored; } for (i = 0; i < sp->timecnt; ++i) { --- 372,378 ---- return -1; for (i = 0; i < sp->timecnt; ++i) { sp->ats[i] = (stored == 4) ? ! detzcode(p) : detzcode40(p); p += stored; } for (i = 0; i < sp->timecnt; ++i) { *************** *** 402,408 **** lsisp = &sp->lsis[i]; lsisp->ls_trans = (stored == 4) ? ! detzcode(p) : detzcode64(p); p += stored; lsisp->ls_corr = detzcode(p); p += 4; --- 402,408 ---- lsisp = &sp->lsis[i]; lsisp->ls_trans = (stored == 4) ? ! detzcode(p) : detzcode40(p); p += stored; lsisp->ls_corr = detzcode(p); p += 4;

2 1

Re: TZ environment variable
by kennykb＠crd.ge.com May 9, 2005

May 9, 2005

olsona(a)dc37a.nci.nih.gov said: > 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.) I always personally considered *that* a bit of a security bug. In the Tcl implementation, I restricted named timezones to combinations of alphanumerics, slashes and underscores, without a leading slash; in this way, paths from the root or from '..' couldn't be constructed. It's arguable that it's a feature rather than a bug, but I decided to err on the side of caution, since a programmer can augment the search path for the files if desired. -- 73 de ke9tv/2, Kevin KENNY GE Corporate Research & Development kennykb(a)crd.ge.com P. O. Box 8, Bldg. K-1, Rm. 5B36A Schenectady, New York 12301-0008 USA

1 0