- tz - lists.iana.org

[PROPOSED] New file tzdata.zi for text-format tzdata
by Paul Eggert May 26, 2017

May 26, 2017

* NEWS: Document this. * Makefile (TZDATA_TEXT, TZDATA_ZI_DEPS): New macros. (TABDATA): Use them. (DATA): Redo to not include tzdata.zi, since it is distributed as part of tzdb, not tzdata. (AWK_SCRIPTS): Add zishrink.awk. (ENCHILADA): Add tzdata.zi. (install): Install tzdata.zi and leapseconds, if requested by TZDATA_TEXT. (tzdata.zi): New rule. (install_data, $(TZS_NEW), zonenames): Use tzdata.zi instead of its inputs. (check_character_set, check_links): Check tzdata.zi. (clean): Remove tzdata.zi. (set-timestamps.out): Set tzdata.zi’s time stamp. (check_public): Check that tzdata.zi can be compiled. * zishrink.awk: New file. --- Makefile | 58 +++++++++++++++++++++++++------------- NEWS | 19 ++++++++++--- zishrink.awk | 91 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 3 files changed, 145 insertions(+), 23 deletions(-) create mode 100644 zishrink.awk diff --git a/Makefile b/Makefile index 6373920..e037b7c 100644 --- a/Makefile +++ b/Makefile @@ -92,6 +92,17 @@ LIBDIR= $(TOPDIR)/lib REDO= posix_right +# To install data in text form that has all the information of the binary data, +# (optionally incorporating leap second information), use +# TZDATA_TEXT= tzdata.zi leapseconds +# To install text data without leap second information (e.g., because +# REDO='posix_only'), use +# TZDATA_TEXT= tzdata.zi +# To avoid installing text data, use +# TZDATA_TEXT= + +TZDATA_TEXT= leapseconds tzdata.zi + # For backward-compatibility links for old zone names, use # BACKWARD= backward pacificnew # To omit these links, use @@ -395,18 +406,19 @@ YDATA= $(PRIMARY_YDATA) etcetera $(BACKWARD) NDATA= systemv factory TDATA= $(YDATA) $(NDATA) ZONETABLES= zone1970.tab zone.tab -TABDATA= iso3166.tab leapseconds $(ZONETABLES) +TABDATA= iso3166.tab $(TZDATA_TEXT) $(ZONETABLES) LEAP_DEPS= leapseconds.awk leap-seconds.list -DATA= $(YDATA) $(NDATA) backzone $(TABDATA) \ - leap-seconds.list yearistype.sh -AWK_SCRIPTS= checklinks.awk checktab.awk leapseconds.awk +TZDATA_ZI_DEPS= zishrink.awk $(TDATA) $(PACKRATDATA) +DATA= $(YDATA) $(NDATA) backzone iso3166.tab leap-seconds.list \ + leapseconds yearistype.sh $(ZONETABLES) +AWK_SCRIPTS= checklinks.awk checktab.awk leapseconds.awk zishrink.awk MISC= $(AWK_SCRIPTS) zoneinfo2tdf.pl TZS_YEAR= 2050 TZS= to$(TZS_YEAR).tzs TZS_NEW= to$(TZS_YEAR)new.tzs TZS_DEPS= $(PRIMARY_YDATA) asctime.c localtime.c \ private.h tzfile.h zdump.c zic.c -ENCHILADA= $(COMMON) $(DOCS) $(SOURCES) $(DATA) $(MISC) $(TZS) +ENCHILADA= $(COMMON) $(DOCS) $(SOURCES) $(DATA) $(MISC) $(TZS) tzdata.zi # Consult these files when deciding whether to rebuild the 'version' file. # This list is not the same as the output of 'git ls-files', since @@ -443,7 +455,7 @@ install: all $(DATA) $(REDO) $(MANS) $(DESTDIR)$(MANDIR)/man3 $(DESTDIR)$(MANDIR)/man5 \ $(DESTDIR)$(MANDIR)/man8 $(ZIC_INSTALL) -l $(LOCALTIME) -p $(POSIXRULES) - cp -f iso3166.tab $(ZONETABLES) $(DESTDIR)$(TZDIR)/. + cp -f $(TABDATA) $(DESTDIR)$(TZDIR)/. cp tzselect zic zdump $(DESTDIR)$(ETCDIR)/. cp libtz.a $(DESTDIR)$(LIBDIR)/. $(RANLIB) $(DESTDIR)$(LIBDIR)/libtz.a @@ -464,6 +476,13 @@ version: $(VERSION_DEPS) printf '%s\n' "$$V" >$@.out mv $@.out $@ +# This file can be tailored by setting BACKWARD, PACKRATDATA, etc. +tzdata.zi: $(TZDATA_ZI_DEPS) + $(AWK) -v PACKRATDATA='$(PACKRATDATA)' \ + -f zishrink.awk \ + $(TDATA) $(PACKRATDATA) >$@.out + mv $@.out $@ + version.h: version VERSION=`cat version` && printf '%s\n' \ 'static char const PKGVERSION[]="($(PACKAGE)) ";' \ @@ -498,10 +517,8 @@ INSTALLARGS = \ ZIC='$(ZIC)' # 'make install_data' installs one set of tz binary files. -# It can be tailored by setting LEAPSECONDS, PACKRATDATA, etc. -install_data: zic leapseconds yearistype $(PACKRATDATA) $(TDATA) - $(ZIC_INSTALL) $(TDATA) - $(AWK) '/^Rule/' $(TDATA) | $(ZIC_INSTALL) - $(PACKRATDATA) +install_data: zic leapseconds yearistype tzdata.zi + $(ZIC_INSTALL) tzdata.zi posix_only: $(MAKE) $(INSTALLARGS) LEAPSECONDS= install_data @@ -538,14 +555,14 @@ posix_packrat: zones: $(REDO) -$(TZS_NEW): $(TDATA) zdump zic +$(TZS_NEW): tzdata.zi zdump zic mkdir -p tzs.dir - $(zic) -d tzs.dir $(TDATA) + $(zic) -d tzs.dir tzdata.zi $(AWK) '/^Link/{print $$1 "\t" $$2 "\t" $$3}' \ - $(TDATA) | LC_ALL=C sort >$@.out + tzdata.zi | LC_ALL=C sort >$@.out wd=`pwd` && \ zones=`$(AWK) -v wd="$$wd" \ - '/^Zone/{print wd "/tzs.dir/" $$2}' $(TDATA) \ + '/^Zone/{print wd "/tzs.dir/" $$2}' tzdata.zi \ | LC_ALL=C sort` && \ ./zdump -i -c $(TZS_YEAR) $$zones >>$@.out sed 's,^TZ=".*tzs\.dir/,TZ=",' $@.out >$@.sed.out @@ -589,7 +606,8 @@ check_character_set: $(ENCHILADA) sharp='#' && \ ! grep -Env $(SAFE_LINE) $(MANS) date.1 $(MANTXTS) \ $(MISC) $(SOURCES) $(WEB_PAGES) \ - CONTRIBUTING LICENSE Makefile README version && \ + CONTRIBUTING LICENSE Makefile README \ + version tzdata.ic && \ ! grep -Env $(SAFE_SHARP_LINE) $(TDATA) backzone \ leapseconds yearistype.sh zone.tab && \ ! grep -Env $(OK_LINE) $(ENCHILADA) @@ -613,6 +631,7 @@ check_sorted: backward backzone iso3166.tab zone.tab zone1970.tab check_links: checklinks.awk $(TDATA) $(AWK) -f checklinks.awk $(TDATA) + $(AWK) -f checklinks.awk tzdata.zi check_tables: checktab.awk $(PRIMARY_YDATA) $(ZONETABLES) for tab in $(ZONETABLES); do \ @@ -630,7 +649,7 @@ clean_misc: rm -f core *.o *.out \ date tzselect version.h zdump zic yearistype libtz.a clean: clean_misc - rm -fr *.dir tzdb-*/ $(TZS_NEW) + rm -fr *.dir tzdata.zi tzdb-*/ $(TZS_NEW) maintainer-clean: clean @echo 'This command is intended for maintainers to use; it' @@ -684,6 +703,7 @@ set-timestamps.out: $(ENCHILADA) touch -cmr `ls -t $$file workman.sh | sed 1q` $$file.txt || \ exit; \ done + touch -cmr `ls -t $(TZDATA_ZI_DEPS) | sed 1q` tzdata.zi touch -cmr `ls -t $(TZS_DEPS) | sed 1q` $(TZS) touch -cmr `ls -t $(VERSION_DEPS) | sed 1q` version touch $@ @@ -695,7 +715,7 @@ check_public: $(MAKE) maintainer-clean $(MAKE) "CFLAGS=$(GCC_DEBUG_FLAGS)" ALL mkdir -p public.dir - for i in $(TDATA) ; do \ + for i in $(TDATA) tzdata.zi; do \ $(zic) -v -d public.dir $$i 2>&1 || exit; \ done $(zic) -v -d public.dir $(TDATA) @@ -789,8 +809,8 @@ typecheck: $(MAKE) clean ; \ done -zonenames: $(TDATA) - @$(AWK) '/^Zone/ { print $$2 } /^Link/ { print $$3 }' $(TDATA) +zonenames: tzdata.zi + @$(AWK) '/^Zone/ { print $$2 } /^Link/ { print $$3 }' tzdata.zi asctime.o: private.h tzfile.h date.o: private.h diff --git a/NEWS b/NEWS index d22d561..8c81caa 100644 --- a/NEWS +++ b/NEWS @@ -10,6 +10,21 @@ Unreleased, experimental changes Add 7 s to the UT offset in Asia/Yangon before 1920. + Changes to build procedure + + To support applications that prefer to read time zone data in text + form, two zic input files tzdata.zi and leapseconds are now + installed by default. The commands 'zic tzdata.zi' and 'zic -L + leapseconds tzdata.zi' can reproduce the tzdata binary files + without and with leap seconds, respectively. To prevent these two + new files from being installed, use 'make TZDATA_TEXT=', and to + suppress leap seconds from the tzdata text installation, use 'make + TZDATA_TEXT=tzdata.zi'. + + 'make BACKWARD=' now suppresses backward-compatibility names + like 'US/Pacific' that are defined in the 'backward' and + 'pacificnew' files. + Changes to code zic and the reference runtime now reject multiple leap seconds @@ -27,10 +42,6 @@ Unreleased, experimental changes Also, zic warns about the undocumented usage with a "last-" prefix, e.g., "last-Fri". - 'make BACKWARD=' now suppresses backward-compatibility names - like 'US/Pacific' that are defined in the 'backward' and - 'pacificnew' files. - Several minor changes have been made to the code to make it a bit easier to port to MS-Windows. (Thanks to Kees Dekker for reporting the problems.) diff --git a/zishrink.awk b/zishrink.awk new file mode 100644 index 0000000..42240f1 --- /dev/null +++ b/zishrink.awk @@ -0,0 +1,91 @@ +# Convert tzdata source into a smaller version of itself. + +# Contributed by Paul Eggert. This file is in the public domain. + +# This is not a general-purpose converter; it is designed for current tzdata. +# 'zic' should treat this script's output as if it were identical to +# this script's input. + +BEGIN { + print "# This zic input file is in the public domain." + if (PACKRATDATA) { + while (0 < (getline line <PACKRATDATA)) { + if (split(line, field)) { + if (field[1] == "Zone") packrat_zone[field[2]] = 1 + if (field[1] == "Link") packrat_zone[field[3]] = 1 + } + } + close (PACKRATDATA) + } +} + +# Remove comments, normalize spaces, and append a space to each line. +/^[[:space:]]*[^#[:space:]]/ { + line = $0 + sub(/#.*/, "", line) + line = line " " + gsub(/[[:space:]]+/, " ", line) + + # SystemV rules are not needed. + if (line ~ /^Rule SystemV /) next + + # Replace FooAsia rules with the same rules without "Asia", as they + # are duplicates. + if (n = match(line, /[^ ]Asia /)) { + if (line ~ /^Rule /) next + line = substr(line, 1, n) substr(line, n + 5) + } + + # Abbreviate times. + while (n = match(line, /[: ]0+[0-9]/)) { + line = substr(line, 1, n) substr(line, n + RLENGTH - 1) + } + while (n = match(line, /:0[^:]/)) { + line = substr(line, 1, n - 1) substr(line, n + 2) + } + + # Abbreviate weekday names. Do not abbreviate "Sun" and "Sat", as + # pre-2017c zic erroneously diagnoses "Su" and "Sa" as ambiguous. + while (n = match(line, /[ l]Mon[<>]/)) { + line = substr(line, 1, n + 1) substr(line, n + 4) + } + while (n = match(line, /[ l]Tue[<>]/)) { + line = substr(line, 1, n + 2) substr(line, n + 4) + } + while (n = match(line, /[ l]Wed[<>]/)) { + line = substr(line, 1, n + 1) substr(line, n + 4) + } + while (n = match(line, /[ l]Thu[<>]/)) { + line = substr(line, 1, n + 2) substr(line, n + 4) + } + while (n = match(line, /[ l]Fri[<>]/)) { + line = substr(line, 1, n + 1) substr(line, n + 4) + } + + # Abbreviate "only" and month names. + gsub(/ only /, " o ", line) + gsub(/ Jan /, " Ja ", line) + gsub(/ Feb /, " F ", line) + gsub(/ Apr /, " Ap ", line) + gsub(/ Aug /, " Au ", line) + gsub(/ Sep /, " S ", line) + gsub(/ Oct /, " O ", line) + gsub(/ Nov /, " N ", line) + gsub(/ Dec /, " D ", line) + + # Strip leading and trailing space. + sub(/^ /, "", line) + sub(/ $/, "", line) + + # Remove unnecessary trailing zero fields. + sub(/ 0+$/, "", line) + + # Output lines unless they are later overridden in PACKRATDATA. + if (FILENAME != PACKRATDATA && line ~ /^[LZ]/) { + overridden = 0 + split(line, field) + overridden = packrat_zone[field[2 + (field[1] == "Link")]] + } + if (!overridden) + print line +} -- 2.9.4

2 4

[PATCH] Shorten an overlong abbrevation in 'backzone'
by Paul Eggert May 26, 2017

May 26, 2017

* backzone (Africa/Luanda): Use 'LMT' for what was apparently Luanda Mean Time. '+005204' is so long that it now provokes a zic warning. --- backzone | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/backzone b/backzone index 9ce7831..a630129 100644 --- a/backzone +++ b/backzone @@ -181,7 +181,7 @@ Zone Africa/Lome 0:04:52 - LMT 1893 # with the date that it took effect, namely 1912-01-01. # Zone Africa/Luanda 0:52:56 - LMT 1892 - 0:52:04 - +005204 1912 Jan 1 + 0:52:04 - LMT 1912 Jan 1 # Luanda Mean Time? 1:00 - WAT # Democratic Republic of the Congo (east) -- 2.9.4

1 0

U.S. DST causes an estimated 30 traffic-accident deaths/year
by Paul Eggert May 25, 2017

May 25, 2017

Austin Smith of Miami University analyzed data from the U.S. Fatality Analysis Reporting System both before and after the 2007 daylight-saving rule change, and found that the spring-forward transition increased fatal crash risk by 5% to 6.5%, with four statistical tests suggesting that the increase is explained by sleep deprivation. Smith concludes, "Back-of-the-envelope calculations suggest that the spring transition into DST caused over 30 deaths annually at a social cost of $275 million." I assume this estimate is for just the U.S. Smith AC. Spring forward at your own risk: daylight saving time and fatal vehicle crashes. Am Econ J: Appl Econ. 2016;8(2):65-91. http://dx.doi.org/10.1257/app.20140100

1 0

[PATCH] Clarify LICENSE file
by Paul Eggert May 25, 2017

May 25, 2017

* LICENSE: Reword LICENSE so that it makes sense when only data files are distributed. --- LICENSE | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/LICENSE b/LICENSE index 148eb23..8ba4399 100644 --- a/LICENSE +++ b/LICENSE @@ -1,4 +1,5 @@ -With a few exceptions, all files in the tz code and data (including -this one) are in the public domain. The exceptions are date.c, -newstrftime.3, and strftime.c, which contain material derived from BSD -and which use the BSD 3-clause license. +Unless specified below, all files in the tz code and data (including +this LICENSE file) are in the public domain. + +If the files date.c, newstrftime.3, and strftime.c are present, they +contain material derived from BSD and use the BSD 3-clause license. -- 2.9.4

1 0

input needed on creation of a new sub-package for raw zone data
by Patsy Franklin May 24, 2017

May 24, 2017

Hi, I'd appreciate community input on this plan. Ideally if others decide to also ship a similar subpackage we can use a common naming convention and install directory. We are planning to ship a new subpackage for users who want to have access to the raw zone data files e.g. leapseconds, and in a pre-determined install location e.g. /usr/share/zoneinfo/zonedata/. The raw zone data is useful for users designing their own interfaces on top of this data. The broadest flexibility is offered by the raw zone data, and while the compiled binary data is versioned and more stable, some users have expressed a request for the raw zone data. The understanding is that the raw zone data format may change. In summary: Our current plan is to use -zonedata in naming the subpackage, For example, tzdata-zonedata-2017b-1.el7. We plan to install the files in this subpackage under /usr/share/zoneinfo/zonedata/. Just as an example we would ship the following files: LICENSE version africa antarctica asia australasia europe northamerica southamerica pacificnew etcetera backward systemv factory backzone iso3166.tab leapseconds leap-seconds.list zone1970.tab zone.tab Thank you! Patsy

5 11

[PROPOSED 1/5] New Makefile macro BACKWARD
by Paul Eggert May 24, 2017

May 24, 2017

* NEWS: Document this. * Makefile (BACKWARD): New macro. (YDATA, INSTALLARGS): Use it. --- Makefile | 10 +++++++++- NEWS | 4 ++++ 2 files changed, 13 insertions(+), 1 deletion(-) diff --git a/Makefile b/Makefile index c62d46f..6373920 100644 --- a/Makefile +++ b/Makefile @@ -92,6 +92,13 @@ LIBDIR= $(TOPDIR)/lib REDO= posix_right +# For backward-compatibility links for old zone names, use +# BACKWARD= backward pacificnew +# To omit these links, use +# BACKWARD= + +BACKWARD= backward pacificnew + # If you want out-of-scope and often-wrong data from the file 'backzone', use # PACKRATDATA= backzone # To omit this data, use @@ -384,7 +391,7 @@ WEB_PAGES= tz-art.htm tz-how-to.html tz-link.htm DOCS= $(MANS) date.1 $(MANTXTS) $(WEB_PAGES) PRIMARY_YDATA= africa antarctica asia australasia \ europe northamerica southamerica -YDATA= $(PRIMARY_YDATA) pacificnew etcetera backward +YDATA= $(PRIMARY_YDATA) etcetera $(BACKWARD) NDATA= systemv factory TDATA= $(YDATA) $(NDATA) ZONETABLES= zone1970.tab zone.tab @@ -482,6 +489,7 @@ leapseconds: $(LEAP_DEPS) # Arguments to pass to submakes of install_data. # They can be overridden by later submake arguments. INSTALLARGS = \ + BACKWARD=$(BACKWARD) \ DESTDIR=$(DESTDIR) \ LEAPSECONDS='$(LEAPSECONDS)' \ PACKRATDATA='$(PACKRATDATA)' \ diff --git a/NEWS b/NEWS index 4e8091b..dcd49eb 100644 --- a/NEWS +++ b/NEWS @@ -20,6 +20,10 @@ Unreleased, experimental changes in civil timekeeping. (Thanks to Robert Elz and Bradley White for noticing glitches in the code that uncovered this problem.) + 'make BACKWARD=' now suppresses backward-compatibility names + like 'US/Pacific' that are defined in the 'backward' and + 'pacificnew' files. + Several minor changes have been made to the code to make it a bit easier to port to MS-Windows. (Thanks to Kees Dekker for reporting the problems.) -- 2.9.4

1 4

Fwd: input needed on creation of a new sub-package for raw zone data
by Patsy Franklin May 23, 2017

May 23, 2017

Sorry, should have replied to all on this one. ---------- Forwarded message ---------- From: Patsy Franklin <pfrankli(a)redhat.com> Date: Tue, May 23, 2017 at 9:26 AM Subject: Re: [tz] input needed on creation of a new sub-package for raw zone data To: Brian.Inglis(a)systematicsw.ab.ca Hi Brian, Thanks for the feedback! On Mon, May 22, 2017 at 1:54 PM, Brian Inglis <Brian.Inglis(a)systematicsw.ab. ca> wrote: > On 2017-05-22 07:03, Patsy Franklin wrote: > > I'd appreciate community input on this plan. Ideally if others decide > > to also ship a similar subpackage we can use a common naming > > convention and install directory. > > > > We are planning to ship a new subpackage for users who want to have > > access to the raw zone data files e.g. leapseconds, and in a > > pre-determined install location e.g. /usr/share/zoneinfo/zonedata/. > > How about using /usr/share/tzdata{,-src}/ maybe with subdirectories > tzdata-2017b, etc. > > We really want to avoid using src to prevent any confusion between the full src rpm that we ship and this subset of the zone data. > > The raw zone data is useful for users designing their own interfaces > > on top of this data. The broadest flexibility is offered by the raw > > zone data, and while the compiled binary data is versioned and more > > stable, some users have expressed a request for the raw zone data. > > The understanding is that the raw zone data format may change. > > > > In summary: > > Our current plan is to use -zonedata in naming the subpackage, For > > example, tzdata-zonedata-2017b-1.el7. > > How about tzdata-src-2017b...? > > We already provide tzdata-2017b-1.el7.src.rpm which contains the full set of sources. The location of these sources is defined by the installer. > We plan to install the files in this subpackage under > > /usr/share/zoneinfo/zonedata/. > > Adding zonedata does not add any useful information about the contents > and storing under /usr/share/zoneinfo/ could be confusing as there are > already subdirectories posix and right holding copies of standard and > leapsecond compensated binary data files, so TZ=posix/... and > TZ=right/... are valid zones, and users may expect something similar to > happen using TZ=zonedata/... which would be unfortunate. > > That's a good point. I hadn't considered that case. We chose zonedata to clarify that it was only the zone data - not zic, zdump, binaries, etc. It was requested that we provide this subset of files in a consistent location at install time which is why we grouped it under the zoneinfo directory. Is there a more appropriate place to install it? Do you have any other suggestions for a name since I think src is ambiguous for our purposes? > Just as an example we would ship the following files: > > LICENSE > > version > > africa > > antarctica > > asia > > australasia > > europe > > northamerica > > southamerica > > pacificnew > > etcetera > > backward > > systemv > > factory > > backzone > > iso3166.tab > > leapseconds > > leap-seconds.list > > zone1970.tab > > zone.tab > > README, CONTRIBUTING, NEWS, and Theory should be included, also > tz-how-to.html which documents how to define and use the sources. > leap-seconds.list should be a (symbolic?) link to the canonical file > version leap-seconds.<timestamp> e.g. leap-seconds.3692908800. > We ship README and Theory with the base package. CONTRIBUTING, NEWS and tz-how-to.html is shipped with our src package. Do we still need to duplicate these in the optional subpackages? BTW, I forgot to mention that our spec file will not allow the new subpackage to be installed without the corresponding version of the base package. The base package does not require the optional new subpackage but will check to insure that it is in sync if it is installed. Do we still need to version the leap-seconds file if it is tied to a specific tzdata version? Thanks! Patsy > > -- > Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada >

2 1

Looking for a way to cut down binary zoneinfo size. Does anyone have the way to?
by Viktor Sergiienko May 19, 2017

May 19, 2017

Hello, I'm developing for a pretty small-sized embedded system, and 2.9M of binaries is a bit too much for us. The system never uses a date before 2007. I estimate I can slim it down too 500K by cutting down the old data. 1. I made a script to cut down the source data: all the rules and all the zonelines before 2001. Compiling this data, I get a lot of errors like: > "northamerica", line 2537: %s in ruleless zone > "northamerica", line 2618: unruly zone because some zones are left without rules, but with %s format in them. 2. I tried to modify zic itself, but apparently understanding it will take me days. Just setting min_year to 2001 results in bunch of > can't determine time zone abbreviation to use just after until time Does anyone have a ready solution? Thanks!

7 11

[PROPOSED 1/2] Rename ‘lint’ to ‘GCC_LINT’
by Paul Eggert May 18, 2017

May 18, 2017

* Makefile (GCC_DEBUG_FLAGS): * private.h (INITIALIZE): Rename ‘lint’ to ‘GCC_LINT’, as the macro is intended for GCC, not for traditional ‘lint’. --- Makefile | 2 +- private.h | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/Makefile b/Makefile index e7c6ac0..bcfdcb2 100644 --- a/Makefile +++ b/Makefile @@ -159,7 +159,7 @@ LDLIBS= # (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) if you are using recent GCC and want lots of checking -GCC_DEBUG_FLAGS = -Dlint -g3 -O3 -fno-common -fstrict-aliasing \ +GCC_DEBUG_FLAGS = -DGCC_LINT -g3 -O3 -fno-common -fstrict-aliasing \ -Wall -Wextra \ -Wbad-function-cast -Wcast-align -Wdate-time \ -Wdeclaration-after-statement \ diff --git a/private.h b/private.h index e9eb211..6886185 100644 --- a/private.h +++ b/private.h @@ -566,7 +566,7 @@ static time_t const time_t_max = MAXVAL(time_t, TYPE_BIT(time_t)); ** INITIALIZE(x) */ -#ifdef lint +#ifdef GCC_LINT # define INITIALIZE(x) ((x) = 0) #else # define INITIALIZE(x) -- 2.9.4

1 1

Morocco changes May 27th 2017 instead of May 21th
by Info - avisched.com May 17, 2017

May 17, 2017

Morocco is about to switch on May 27th back to UTC from +1. The current release doesn't reflect that (May 21st). Is there any update planned before the actual transition? Many thanks! Martin

5 5

Asia/Harbin, Asia/Chongqing and Asia/Kashgar
by Phake Nick May 13, 2017

May 13, 2017

iirc, according to past conversation on the mailing list, the reason why these timezones that are not in use for many years already still exists in tz database is because of legacy reason, however given that Asia/Ishigaki were deleted from this database in 1999 when it's found to be not in use, is there any reason preventing the same to be done to Asia/Harbin, Asia/Chongqing, and Asia/Kashgar?

2 1

gcc 8 demanded patch (from NetBSD)
by Robert Elz May 11, 2017

May 11, 2017

The following patch was recently added to NetBSD, to appease GCC 8 (apparently) ... "hit" is a bool, and it seems gcc 8 does not like ++ operators applied to one of those. (deleted parts of the diff which just showed the version ID string being updated...) kre Index: src/lib/libc/time/localtime.c diff -u src/lib/libc/time/localtime.c:1.106 src/lib/libc/time/localtime.c:1.107 --- src/lib/libc/time/localtime.c:1.106 Sat Mar 11 18:23:14 2017 +++ src/lib/libc/time/localtime.c Tue May 9 02:30:49 2017 @@ -1716,7 +1716,7 @@ timesub(const time_t *timep, int_fast32_ sp->lsis[i - 1].ls_trans + 1 && sp->lsis[i].ls_corr == sp->lsis[i - 1].ls_corr + 1) { - ++hit; + hit = true; --i; } }

8 13

TZDEFRULESTRING is increasingly out-of-date
by Tom Lane May 7, 2017

May 7, 2017

Due to a script's unintended failure to supply a -p option to zic, I recently had my nose rubbed in the fact that localtime.c still has this as the fallback when the "posixrules" link can't be loaded: /* ** The DST rules to use if TZ has no rules and we can't load TZDEFRULES. ** We default to US rules as of 1999-08-17. ** POSIX 1003.1 section 8.1.1 says that the default DST rules are ** implementation dependent; for historical reasons, US rules are a ** common default. */ #ifndef TZDEFRULESTRING #define TZDEFRULESTRING ",M4.1.0,M10.5.0" #endif /* !defined TZDEFDST */ It's now over ten years since the US last followed those rules; isn't it time to update TZDEFRULESTRING to match current law? I can't really think of any situation where the current default would be of any value now. Apologies if this policy is being followed intentionally; but I couldn't find any discussion of the point by googling. regards, tom lane

2 1

Potted history of timekeeping from the BBC
by John Haxby April 21, 2017

April 21, 2017

This is from a series of things that made the modern economy, it says on the web page: Tick tock: The importance of knowing the right time: http://www.bbc.co.uk/news/business-39129620 In one short page it manages to mention everything but DST :) and it includes a picture of Harrison No 1. (If you're ever near Greenwich I recommend visiting the Royal Observatory, taking the obligatory foot-in-both-hemispheres selfie and then going to look at the clocks.) >From the BBC web page though, I particularly noticed this: > Some financiers recently calculated it was worth spending $300m (£247m) drilling through mountains between Chicago and New York to lay fibre-optic cables in a slightly straighter line. That sped up communication between the two cities' exchanges by three milliseconds. jch

10 10

Re: [tz] leapseconds.awk, LEAP directives and references
by Chris Woodbury April 21, 2017

April 21, 2017

In the course of reviewing the AWK script leapseconds.awk, I was disturbed by the fact that it (1) operated on the comments (probably not a good idea) in the NIST produced leap-seconds.list file rather than the NTP timestamp itself and (2) that it assumed that leap seconds would only occur in December and June. The regulation that governs leap seconds, ITU-R TF.460-6 <https://www.itu.int/rec/R-REC-TF.460-6-200202-I/>, actually allows leap seconds to occur at the end of any UTC month. Annex 1, Section 2: Leap Seconds 2.1 A positive or negative leap-second should be the last second of a UTC month, but first preference should be given to the end of December and June, and second preference to the end of March and September. I note, in the event of a (highly unlikely) negative leap second, the LEAP directive generated is for 23:59:59 which, in the case of a negative leap second, doesn't exist. I reviewed the C code and, it seems to me, the transaction added should actually be for the second before, 23:59:58, as the transaction itself causes 23:59:59 to be skippedaltogether. (Kinda hard to skip an event if you're in it.) I bring this up as I've alrady written the changes necessary but I want to verify the correctness of this last beforesubmitting them. Also, I've an AWK script that uses the IERS file Leap_Seconds.dat rather than the NIST leap-seconds.listfile. Leap_Seconds.dat is a straight list of leap-seconds. USNO MAIA also has straight list of leap-seconds in a different format. See URLs: <http://hpiers.obspm.fr/iers/bul/bulc/Leap_Seconds.dat> <http://maia.usno.navy.mil/ser7/leapsec.dat> Either of these would, particularly the IERS file as it has few but excellent comments, be a better source of leap-second information than the once removed NIST file leap-seconds.list; which is purposed for another task. Lastly, thanks to Dr. Eggert for including the reference I gave him to the AAPT Resource Letter that included Terry Quinn's article in the NIST Time and Frequency Division's PDF archive (1168). Anyone wanting to know about Time and Frequency Measurement might want to read the other articles as well as Dr. Quinn's. Another good, comprehensive article is "The leap second: its history and possible future" by R.A. Nelson, et al, from Metrogia Vol 38, pp. 509-529 (2001). PDF available (with permission) at: <https://www.cl.cam.ac.uk/~mgk25/time/metrologia-leapsecond.pdf>

9 16

[PROPOSED] Use railway time for India from 1870-1941
by Paul Eggert April 20, 2017

April 20, 2017

From: Paul Eggert <eggert(a)Penguin.CS.UCLA.EDU> * NEWS: Document this. * asia (Asia/Yangon): Add 7 s to times from 1880 to 1920. (Asia/Kolkata): Switch from HMT to MMT in 1870, and from MMT to IST in 1906. --- NEWS | 11 +++++++++++ asia | 59 +++++++++++++++++++++++++++++++++++++++++++++++++++++------ 2 files changed, 64 insertions(+), 6 deletions(-) diff --git a/NEWS b/NEWS index f986cf6..ad099f4 100644 --- a/NEWS +++ b/NEWS @@ -1,5 +1,16 @@ News for the tz database +Unreleased, experimental changes + + Changes to past time stamps + + Use railway time for Asia/Kolkata before 1941, by switching to + Madras local time (UT +052110) in 1870, then to IST (UT +0530) in + 1906. Also, treat 1941-2's +0630 as DST, like 1942-5. + + Add 7 s to the UT offset in Asia/Yangon before 1920. + + Release 2017b - 2017-03-17 07:30:38 -0700 Briefly: Haiti has resumed DST. diff --git a/asia b/asia index 35774c6..f027071 100644 --- a/asia +++ b/asia @@ -258,9 +258,15 @@ Zone Asia/Brunei 7:39:40 - LMT 1926 Mar # Bandar Seri Begawan # Milne says 6:24:40 was the meridian of the time ball observatory at Rangoon. +# From Paul Eggert (2017-04-20): +# Page 27 of Reed & Low (cited for Asia/Kolkata) says "Rangoon local time is +# used upon the railways and telegraphs of Burma, and is 6h. 24m. 47s. ahead +# of Greenwich." This refers to the period before Burma's transition to +0630, +# a transition for which Shanks is the only source. + # Zone NAME GMTOFF RULES FORMAT [UNTIL] -Zone Asia/Yangon 6:24:40 - LMT 1880 # or Rangoon - 6:24:40 - RMT 1920 # Rangoon Mean Time? +Zone Asia/Yangon 6:24:47 - LMT 1880 # or Rangoon + 6:24:47 - RMT 1920 # Rangoon local time 6:30 - +0630 1942 May 9:00 - +09 1945 May 3 6:30 - +0630 @@ -887,14 +893,55 @@ Zone Asia/Dili 8:22:20 - LMT 1912 Jan 1 # local time in favor of Indian Standard Time.... Journalists called this # dispute the "Battle of the Clocks." It lasted nearly half a century. +# From Paul Eggert (2017-04-20): +# Good luck trying to nail down old timekeeping records in India. +# "... in the nineteenth century ... Madras Observatory took its magnetic +# measurements in Göttingen time, its meterological measurements on Madras +# (local) time, dropped its time ball on Greenwich (ocean navigator's) time, +# and distributed civil (local time)." -- Bartky IR. Selling the time: +# 19th-century timekeeping in america. Stanford U Press (2000), 247 note 19. +# "A more potent cause of resistance to the general adoption of the present +# standard time lies in the fact that it is Madras time. The citizen of +# Bombay, proud of being 'primus in Indis' and of Calcutta, equally proud of +# his city being the Capital of India, and - for a part of the year - the Seat +# of the Supreme Government, alike look down on Madras, and refuse to change +# the time they are using, for that of what they regard as a benighted +# Presidency; while Madras, having for long given the standard time to the +# rest of India, would resist the adoption of any other Indian standard in its +# place." -- Oldham RD. On Time in India: a suggestion for its improvement. +# Proceedings of the Asiatic Society of Bengal (April 1899), 49-55. +# +# "In 1870 ... Madras time - 'now used by the telegraph and regulated from the +# only government observatory' - was suggested as a standard railway time, +# first to be dopted on the Great Indian Peninsular Railway (GIPR).... +# Calcutta, Bombay, and Karachi, were to be allowed to continue with their +# local time for civil purposes." - Prasad R. Tracks of Change: Railways and +# Everyday Life in Colonial India. Cambridge University Press (2016), 145. +# +# Reed S, Low F. The Indian Year Book 1936-37. Bennett, Coleman, pp 27-8. +# https://archive.org/details/in.ernet.dli.2015.282212 +# This lists +052110 as Madras local time used in railways, and says that on +# 1906-01-01 railways and telegraphs in India switched to +0530. Some +# municipalities retained their former time, and the time in Calcutta +# continued to depend on whether you were at the railway station or at +# government offices. Government time was at +055320 (according to Shanks) or +# at +0554 (according to the Indian Year Book). Railway time is more +# appropriate for our purposes, as it was better documented, it is what we do +# elsewhere (e.g., Europe/London before 1880), and after 1906 it was +# consistent in the region now identified by Asia/Kolkata. So, use railway +# time for 1870-1941. Shanks is our only (and dubious) source for the +# 1941-1945 data. + # Zone NAME GMTOFF RULES FORMAT [UNTIL] -Zone Asia/Kolkata 5:53:28 - LMT 1880 # Kolkata - 5:53:20 - HMT 1941 Oct # Howrah Mean Time? - 6:30 - +0630 1942 May 15 +Zone Asia/Kolkata 5:53:28 - LMT 1854 Jun 28 # Kolkata + 5:53:20 - HMT 1870 # Howrah Mean Time? + 5:21:10 - MMT 1906 Jan 1 # Madras local time + 5:30 - IST 1941 Oct + 5:30 1:00 +0630 1942 May 15 5:30 - IST 1942 Sep 5:30 1:00 +0630 1945 Oct 15 5:30 - IST -# The following are like Asia/Kolkata: +# Since 1970 the following are like Asia/Kolkata: # Andaman Is # Lakshadweep (Laccadive, Minicoy and Amindivi Is) # Nicobar Is -- 2.9.3

1 0

Mouradconstantine@icloud.com
by Mourad Constantine April 13, 2017

April 13, 2017

Sent from my iPhone

1 0

Urumqi timezone.
by gfb hjjhjh April 13, 2017

April 13, 2017

As there are two different timmezones being used in Xinjiang, China, would it be a good idea to create another timezone named something like Asia/Urumqi2 to correspond to the different timezone being used in the area?

9 13

Fwd: [IANA #939704] Contributions to this list
by Erast Fandorin April 8, 2017

April 8, 2017

Dear Sir/Madam Please make the changes to time zone database: Ukraine: Kiev => Kyiv, Zaporozh'ye => Zaporizhia, Uzhgorod => Uzhhorod, Odessa => Odesa according to legal names and MORE COMMON USE in ENGLISH (like booking services or names of the airports, railway stations, river and sea ports and everyday speaking usage). Autonomous Republic of Crimea (Ukraine): Crimea, Republic of => Crimea, Autonomous Republic of according to legal name of the Ukrainian territory occupied by Russians terrorists forces. The name "Autonomous Republic of Crimea" is officially recognized by all of the countries (except the Russian Federation - the terrorist's country number one in the World) and in international COMMON USE in ENGLISH navigation systems of the air, sea and river transport systems. Sevastopol MSK => Sevastopol KMT Simferopol MSK => Simferopol KMT according to legal time usage on the Ukrainian territory -------- Forwarded Message -------- Тема: [IANA #939704] Contributions to this list Дата: Thu, 01 Dec 2016 20:16:50 +0000 Від: Amanda Baber via RT <iana-questions(a)iana.org> <iana-questions(a)iana.org> Відповісти: iana-questions(a)iana.org Кому: aristonomy(a)gmail.com Dear Sir/Madam, Thank you for contacting us. We host the Time Zone Database, but updates are made by the Time Zone Coordinator in consultation with the Time Zone mailing list, in accordance with RFC 6557. Questions about the contents of the database should be sent to the mailing list. For mailing list archives and subscription information, please see http://www.iana.org/time-zones Best regards, Amanda Baber Lead IANA Services Specialist PTI On Thu Dec 01 10:28:43 2016, aristonomy(a)gmail.com wrote: > To the holder of iana.org! > > Contributions to this list of time zones! > > "Uzhhorod International Airport", "Kyiv International Airport > (Zhuliany)", "Kyiv Boryspil international airport", "Zaporizhia > International Airport" which are MORE COMMON USE in every ENGLISH > booking service. The same names are used in the railway stations names > and booking services. > > Even more! Kyiv, Uzhhorod, Zaporizhia, Odesa are the international names > of the cityes, river and sea ports, airports and railway stations, parts > of the administration and state organizations names and etcetera. > > The only common use of the names: Kiev, Zaporozh'ye, Uzhgorod and Odessa > were in USSR - the country which is not exist any more (thanks to God!), > and in the country which are occupied the part of Ukraine. Supporting > such spelling is a direct support of the country which is now are the N1 > Country Terrorist of the World!! > > Europe/Simferopol and Europe/Sevastopol now are under Russian occupation > and NO legal international communications for hole Autonomous Republic > of Crimea (Ukraine) and this territory are legally under Ukrainians Law! > > Supporting of the time change to the MSK time zone is a direct support > of occupation!! > > This letter are public and will be shared to social network. > > Stop support of Russian invasion to Ukraine and Georgia!! Stop support > of the biggest terrorists organization which Russian Federation are! > > > # From Tim Parenti (2014-07-03): > > # Europe/Simferopol covers... > > # ** **** Crimea, Republic of > > # ** **** Sevastopol > > > > Zone Europe/Simferopol 2:16:24 - LMT 1880 > > 2:16 - SMT 1924 May 2 # Simferopol Mean T > > 2:00 - EET 1930 Jun 21 > > 3:00 - MSK 1941 Nov > > 1:00 C-Eur CE%sT 1944 Apr 13 > > 3:00 Russia MSK/MSD 1990 > > 3:00 - MSK 1990 Jul 1 2:00 > > 2:00 - EET 1992 > > # Central Crimea used Moscow time 1994/1997. > > # > > # From Paul Eggert (2006-03-22): > > # The _Economist_ (1994-05-28, p 45) reports that central Crimea switched > > # from Kiev to Moscow time sometime after the January 1994 elections. > > # Shanks (1999) says "date of change uncertain", but implies that it > > happened > > # sometime between the 1994 DST switches. Shanks & Pottenger simply say > > # 1994-09-25 03:00, but that can't be right. For now, guess it > > # changed in May. > > 2:00 E-Eur EE%sT 1994 May > > # From IATA SSIM (1994/1997), which also says that Kerch is still like > > Kiev. > > 3:00 E-Eur MSK/MSD 1996 Mar 31 0:00s > > 3:00 1:00 MSD 1996 Oct 27 3:00s > > # IATA SSIM (1997-09) says Crimea switched to EET/EEST. > > # Assume it happened in March by not changing the clocks. > > 3:00 Russia MSK/MSD 1997 > > 3:00 - MSK 1997 Mar lastSun 1:00u > > # From Alexander Krivenyshev (2014-03-17): > > # time change at 2:00 (2am) on March 30, 2014 > > # http://vz.ru/news/2014/3/17/677464.html > > # From Paul Eggert (2014-03-30): > > # Simferopol and Sevastopol reportedly changed their central town clocks > > # late the previous day, but this appears to have been ceremonial > > # and the discrepancies are small enough to not worry about. > > 2:00 EU EE%sT 2014 Mar 30 2:00 > > 4:00 - MSK 2014 Oct 26 2:00s > > 3:00 - MSK > > > > > > > > # Zone NAME GMTOFF RULES FORMAT [UNTIL] > > # Most of Ukraine since 1970 has been like Kiev. > > # "Kyiv" is the transliteration of the Ukrainian name, but > > # "Kiev" is more common in English. > > Zone Europe/Kiev 2:02:04 - LMT 1880 > > 2:02:04 - KMT 1924 May 2 # Kiev Mean Time > > > > # "Uzhhorod" is the transliteration of the Rusyn/Ukrainian > > pronunciation, but > > # "Uzhgorod" is more common in English. > > Zone Europe/Uzhgorod 1:29:12 - LMT 1890 Oct > > > > # Zaporozh'ye and eastern Lugansk oblasts observed DST 1990/1991. > > # "Zaporizhia" is the transliteration of the Ukrainian name, but > > # "Zaporozh'ye" is more common in English. Use the common English > > # spelling, except omit the apostrophe as it is not allowed in > > # portable Posix file names. > > Zone Europe/Zaporozhye 2:20:40 - LMT 1880 >

2 1

MS-Windows 10 and New Zealand yesterday
by Paul Eggert April 3, 2017

April 3, 2017

Chris Keall of the National Business Review (New Zealand) reports that laptops and phones running Microsoft Windows 10 missed the end of daylight saving time in New Zealand yesterday. Microsoft Windows 7 laptops operated correctly. This leads me to think that the problem has something to do with the tz database, as MS-Windows 7 does not use tzdata whereas MS-Windows 8.1 and later use tzdata, at least in some cases. Does anyone have technical information about why the glitch happened? Is there some way we can help avoid it in the future? Keall C. Living in the past: Windows 10 fails to update for end of daylight saving. NBR 2017-04-03. https://www.nbr.co.nz/article/living-past-windows-10-fails-update-end-dayli…

3 2

zone.tab / zone1970.tab inconsistency for TF/UM/VN
by Neil Fuller April 3, 2017

April 3, 2017

This may be a misunderstanding on my part about the file formats of zone.tab and zone1970.tab and how consistent they are expected to be. I expect the exact zone IDs to be different, but there are only a few cases where countries differ in the number of referenced zone IDs. I realize that zone.tab is intended for backward compatibility but it looks like it is being well maintained. Is this difference expected? If it is, can somebody explain? Details below the line. Thanks for all the hard work. Neil. ------------------- 2017b: TF zone.tab: TF -492110+0701303 Indian/Kerguelen zone1970.tab: RE,TF -2052+05528 Indian/Reunion Réunion, Crozet, Scattered Islands TF -492110+0701303 Indian/Kerguelen Kerguelen, St Paul Island, Amsterdam Island ------------------ UM zone.tab: UM +2813-17722 Pacific/Midway Midway Islands UM +1917+16637 Pacific/Wake Wake Island zone1970.tab: AS,UM -1416-17042 Pacific/Pago_Pago Samoa, Midway UM +1917+16637 Pacific/Wake Wake Island US,UM +211825-1575130 Pacific/Honolulu Hawaii ------------------ VN zone.tab: VN +1045+10640 Asia/Ho_Chi_Minh zone1970.tab: TH,KH,LA,VN +1345+10031 Asia/Bangkok Indochina (most areas) VN +1045+10640 Asia/Ho_Chi_Minh Vietnam (south) -- Google UK Limited Registered Office: 6 Pancras Square, London, N1C 4AG Registered in England Number: 3977902

2 2

[PATCH] Give free source for Quinn paper
by Paul Eggert April 2, 2017

April 2, 2017

* leapseconds.awk, zic.8: Mention the NIST-distributed copy of the Quinn paper, too. --- leapseconds.awk | 5 ++++- zic.8 | 5 ++++- 2 files changed, 8 insertions(+), 2 deletions(-) diff --git a/leapseconds.awk b/leapseconds.awk index 21fe540..8cd2f7e 100644 --- a/leapseconds.awk +++ b/leapseconds.awk @@ -20,7 +20,10 @@ BEGIN { print "# periodically uses leap seconds to keep UTC to within 0.9 s of UT1" print "# (which measures the true angular orientation of the earth in space); see" print "# Terry J Quinn, The BIPM and the accurate measure of time," - print "# Proc IEEE 79, 7 (July 1991), 894-905 <http://dx.doi.org/10.1109/5.84965>." + print "# Proc IEEE 79, 7 (July 1991), 894-905 <http://dx.doi.org/10.1109/5.84965>," + print "# reprinted in: Hackman C, Sullivan DB (eds), Time and frequency measurement," + print "# American Association of Physics Teachers (1996)," + print "# <http://tf.nist.gov/general/pdf/1168.pdf>, 75-86." print "# There were no leap seconds before 1972, because the official mechanism" print "# accounting for the discrepancy between atomic time and the earth's rotation" print "# did not exist until the early 1970s." diff --git a/zic.8 b/zic.8 index e5e71f5..25dac78 100644 --- a/zic.8 +++ b/zic.8 @@ -463,7 +463,10 @@ if a second was skipped. .\" than one leap second to be inserted or deleted at a time. .\" The C Standard is in error in suggesting the possibility. .\" See Terry J Quinn, The BIPM and the accurate measure of time, -.\" Proc IEEE 79, 7 (July 1991), 894-905. +.\" Proc IEEE 79, 7 (July 1991), 894-905, reprinted in +.\" Hackman C, Sullivan DB (eds), Time and frequency measurement, +.\" American Association of Physics Teachers (1996), +.\" <http://tf.nist.gov/general/pdf/1168.pdf>, 75-86." .\" or .\" .q ++ .\" if two seconds were added -- 2.9.3

1 0

Re: [tz] Israel Timezone query
by Vidyalakshmi Badiger March 29, 2017

March 29, 2017

Dear Tz Team, As per the below request the Time zone value for Israel need to be changed from “GMT +2 (Default Value) to (Default value). So how can we proceed to provide this change? Regards, Vidya From: 황주연 [mailto:juyeon.hwang@lge.com] Sent: Tuesday, March 28, 2017 5:16 AM To: Vidyalakshmi Badiger/LGSIA MPS-7(vidya.badiger(a)lge.com) Cc: 김성경/책임연구원/MC연구소 SW플랫폼실 1팀 1파트(sungkyoung.kim(a)lge.com); Divya Srivastava/LGSIA MPS-7(divya.srivastava(a)lge.com); 황주연/선임연구원/MC연구소 SW플랫폼실 1팀 2파트(juyeon.hwang(a)lge.com) Subject: RE: Israel Timezone query Dear Vidyalakshmi Badiger, We not modify tzdata manually. I think you can contact IANA (tz(a)iana.org<mailto:tz@iana.org>) Thank you. From: Vidyalakshmi Badiger [mailto:vidya.badiger@lge.com] Sent: Monday, March 27, 2017 6:51 PM To: juyeon.hwang(a)lge.com<mailto:juyeon.hwang@lge.com> Cc: sungkyoung.kim(a)lge.com<mailto:sungkyoung.kim@lge.com>; Divya Srivastava <divya.srivastava(a)lge.com<mailto:divya.srivastava@lge.com>> Subject: FW: Israel Timezone query Dear Juyeon, As per the below request the Time zone value for Israel need to be changed from “GMT +2 (Default Value) to (Default value). So how can we proceed to provide this change? Regards, Vidya From: Vidyalakshmi Badiger/LGSIA MPS-7(vidya.badiger(a)lge.com<mailto:vidya.badiger@lge.com>) Sent: Thursday, March 23, 2017 6:27 PM To: Raghavendra Revankar/LGSIA MPS-7(raghavendra.revankar(a)lge.com<mailto:raghavendra.revankar@lge.com>); Veena Kalasannavar/LGSIA DP PL(veena.kalasannavar(a)lge.com<mailto:veena.kalasannavar@lge.com>); Satish K R/LGSIA MPS-7(satish.babu(a)lge.com<mailto:satish.babu@lge.com>) Cc: Harish Mollin/LGSIA DP PL(harish.mollin(a)lge.com<mailto:harish.mollin@lge.com>); Bhavya SP/LGSIA DP PL(bhavya.sp(a)lge.com<mailto:bhavya.sp@lge.com>) Subject: RE: Israel Timezone query Dear Veena, Please find the details, Can you please confirm the current time zone value present in Google’s library for Israel all buyers? ---- GMT+02:00 Israel Standard Time [Jerusalem] what action need to be taken if the Google’s value is not matching with the above new GPRI change. ----- Need to check with HQ ,as we need to change time zone by modifying metaZones.txt Regards, Vidya From: Raghavendra Revankar/LGSIA MPS-7(raghavendra.revankar(a)lge.com<mailto:raghavendra.revankar@lge.com>) Sent: Thursday, March 23, 2017 5:56 PM To: Veena Kalasannavar/LGSIA DP PL(veena.kalasannavar(a)lge.com<mailto:veena.kalasannavar@lge.com>); Satish K R/LGSIA MPS-7(satish.babu(a)lge.com<mailto:satish.babu@lge.com>); Vidyalakshmi Badiger/LGSIA MPS-7(vidya.badiger(a)lge.com<mailto:vidya.badiger@lge.com>) Cc: Harish Mollin/LGSIA DP PL(harish.mollin(a)lge.com<mailto:harish.mollin@lge.com>); Nagappa Karajol/LGSIA MPS-7(nagappa.karajol(a)lge.com<mailto:nagappa.karajol@lge.com>); Bhavya SP/LGSIA DP PL(bhavya.sp(a)lge.com<mailto:bhavya.sp@lge.com>); Harshith C K/LGSIA MPS-7(harshith.ck(a)lge.com<mailto:harshith.ck@lge.com>) Subject: RE: Israel Timezone query ++ VIDYA From: Veena Kalasannavar/LGSIA DP PL(veena.kalasannavar(a)lge.com<mailto:veena.kalasannavar@lge.com>) Sent: Thursday, 23 March 2017 5:54 PM To: Satish K R/LGSIA MPS-7(satish.babu(a)lge.com<mailto:satish.babu@lge.com>); Raghavendra Revankar/LGSIA MPS-7(raghavendra.revankar(a)lge.com<mailto:raghavendra.revankar@lge.com>) Cc: Harish Mollin/LGSIA DP PL(harish.mollin(a)lge.com<mailto:harish.mollin@lge.com>); Nagappa Karajol/LGSIA MPS-7(nagappa.karajol(a)lge.com<mailto:nagappa.karajol@lge.com>); Bhavya SP/LGSIA DP PL(bhavya.sp(a)lge.com<mailto:bhavya.sp@lge.com>); Harshith C K/LGSIA MPS-7(harshith.ck(a)lge.com<mailto:harshith.ck@lge.com>) Subject: RE: Israel Timezone query ++ Raghavendra From: Veena Kalasannavar/LGSIA DP PL(veena.kalasannavar(a)lge.com<mailto:veena.kalasannavar@lge.com>) Sent: Thursday, March 23, 2017 10:01 AM To: Satish K R/LGSIA MPS-7(satish.babu(a)lge.com<mailto:satish.babu@lge.com>) Cc: Harish Mollin/LGSIA DP PL(harish.mollin(a)lge.com<mailto:harish.mollin@lge.com>); Nagappa Karajol/LGSIA MPS-7(nagappa.karajol(a)lge.com<mailto:nagappa.karajol@lge.com>); Bhavya SP/LGSIA DP PL(bhavya.sp(a)lge.com<mailto:bhavya.sp@lge.com>); Harshith C K/LGSIA MPS-7(harshith.ck(a)lge.com<mailto:harshith.ck@lge.com>) Subject: RE: Israel Timezone query Dear Satish, As requested in below mail, please let us know the Google’s IANA DB version used for all models for Timezone check. Regards, Veena. From: Harshith C K/LGSIA MPS-7(harshith.ck(a)lge.com<mailto:harshith.ck@lge.com>) Sent: Thursday, March 23, 2017 9:56 AM To: Veena Kalasannavar/LGSIA DP PL(veena.kalasannavar(a)lge.com<mailto:veena.kalasannavar@lge.com>) Cc: Harish Mollin/LGSIA DP PL(harish.mollin(a)lge.com<mailto:harish.mollin@lge.com>); Nagappa Karajol/LGSIA MPS-7(nagappa.karajol(a)lge.com<mailto:nagappa.karajol@lge.com>); Bhavya SP/LGSIA DP PL(bhavya.sp(a)lge.com<mailto:bhavya.sp@lge.com>) Subject: RE: Israel Timezone query Dear Veena, As you mentioned, timezone is picked from IANA database shared by Google which is part of frameworks. Please check with CFW team for DB version details. Thanks & Regards, Harshith From: Veena Kalasannavar/LGSIA DP PL(veena.kalasannavar(a)lge.com<mailto:veena.kalasannavar@lge.com>) Sent: Thursday, March 23, 2017 9:41 AM To: Harshith C K/LGSIA MPS-7(harshith.ck(a)lge.com<mailto:harshith.ck@lge.com>) Cc: Harish Mollin/LGSIA DP PL(harish.mollin(a)lge.com<mailto:harish.mollin@lge.com>); Nagappa Karajol/LGSIA MPS-7(nagappa.karajol(a)lge.com<mailto:nagappa.karajol@lge.com>); Bhavya SP/LGSIA DP PL(bhavya.sp(a)lge.com<mailto:bhavya.sp@lge.com>) Subject: Israel Timezone query Dear Harshit, Recently we observed that Israel FTE has updated timezone for Partner buyer. Please refer below screenshot. [cid:image001.png@01D2A7AB.923BBB40] But as we are aware, time zone is no more referred from GPRI and Google’s library is used to for the same. Can you please confirm the current time zone value present in Google’s library for Israel all buyers? Also please let us know, what action need to be taken if the Google’s value is not matching with the above new GPRI change. Regards, Veena.

5 4

[PATCH] Fix some word repetitions
by Paul Eggert March 25, 2017

March 25, 2017

* Makefile, europe, localtime.c, tz-art.htm, tzfile.5: Fix repeated instances of words in commentary. (Problem with 'Makefile'reported by Curtis Manwaring.) --- Makefile | 2 +- europe | 2 +- localtime.c | 2 +- tz-art.htm | 2 +- tzfile.5 | 2 +- 5 files changed, 5 insertions(+), 5 deletions(-) diff --git a/Makefile b/Makefile index 8067ba0..87fcfab 100644 --- a/Makefile +++ b/Makefile @@ -75,7 +75,7 @@ LIBDIR= $(TOPDIR)/lib # If you want only POSIX time, with time values interpreted as # seconds since the epoch (not counting leap seconds), use # REDO= posix_only -# below. If you want want only "right" time, with values interpreted +# below. If you want only "right" time, with values interpreted # as seconds since the epoch (counting leap seconds), use # REDO= right_only # below. If you want both sets of data available, with leap seconds not diff --git a/europe b/europe index 558b9f1..088d0a8 100644 --- a/europe +++ b/europe @@ -1524,7 +1524,7 @@ Zone Atlantic/Reykjavik -1:28 - LMT 1908 # From Paul Eggert (2016-10-27): # Go with INRiM for DST rules, except as corrected by Inglis for 1944 # for the Kingdom of Italy. This is consistent with Renzo Baldini. -# Model Rome's occupation by using using C-Eur rules from 1943-09-10 +# Model Rome's occupation by using C-Eur rules from 1943-09-10 # to 1944-06-04; although Rome was an open city during this period, it # was effectively controlled by Germany. # diff --git a/localtime.c b/localtime.c index afc7438..4bedb5c 100644 --- a/localtime.c +++ b/localtime.c @@ -639,7 +639,7 @@ tzloadbody(char const *name, struct state *sp, bool doextend, } } /* - ** If type 0 is is unused in transitions, + ** If type 0 is unused in transitions, ** it's the type to use for early times. */ for (i = 0; i < sp->timecnt; ++i) diff --git a/tz-art.htm b/tz-art.htm index f726cce..17b8719 100644 --- a/tz-art.htm +++ b/tz-art.htm @@ -24,7 +24,7 @@ into problems that programmers have with timekeeping.</li> Explaining The Mysteries Of Time Zones</a>" (2017; 2:15) briefly says why France has more time zones than Russia.</a> <li> -"About Time" (1962; 53 minutes) is part of the the +"About Time" (1962; 53 minutes) is part of the Bell Science extravaganza, with Frank Baxter, Richard Deacon, and Les Tremayne. Its advisor was Richard Feynman, and it was voiced by Mel Blanc. (<a href="http://www.imdb.com/title/tt0154110/">IMDb entry</a>.)</li> diff --git a/tzfile.5 b/tzfile.5 index 0c907bc..2e88763 100644 --- a/tzfile.5 +++ b/tzfile.5 @@ -145,7 +145,7 @@ POSIX-TZ-environment-variable-style string for use in handling instants after the last transition time stored in the file (with nothing between the newlines if there is no POSIX representation for such instants). -The POSIX-style string must must agree with the local time type after +The POSIX-style string must agree with the local time type after both data's last transition times; for example, given the string .q "WET0WEST,M3.5.0,M10.5.0/3" then if a last transition time is in July, the transition's local time -- 2.9.3

1 0

[tz-announce] 2017b release of tz code and data available
by Paul Eggert March 23, 2017

March 23, 2017

The 2017b release of the tz code and data is available. It reflects the following changes, which were either circulated on the tz mailing list or are relatively minor technical or administrative changes: Briefly: Haiti has resumed DST. Changes to past and future time stamps Haiti resumed observance of DST in 2017. (Thanks to Steffen Thorsen.) Changes to past time stamps Liberia changed from -004430 to +00 on 1972-01-07, not 1972-05-01. Use "MMT" to abbreviate Liberia's time zone before 1972, as "-004430" is one byte over the POSIX limit. (Problem reported by Derick Rethans.) Here are links to the release files: https://www.iana.org/time-zones/repository/releases/tzcode2017b.tar.gz https://www.iana.org/time-zones/repository/releases/tzdata2017b.tar.gz https://www.iana.org/time-zones/repository/releases/tzdb-2017b.tar.lz As usual, links to the latest release files are here: https://www.iana.org/time-zones/repository/tzcode-latest.tar.gz https://www.iana.org/time-zones/repository/tzdata-latest.tar.gz https://www.iana.org/time-zones/repository/tzdb-latest.tar.lz Links are also available via plain HTTP, and via FTP from ftp://ftp.iana.org/tz/releases with the same basenames as above. Each release file has a GPG signature, which can be retrieved by appending ".asc" to the above URLs. Copies of these signatures are appended to this message. This release corresponds to commit f8ebe3a644e12b294dfc3c06c5243c1b9c13a7e8 dated 2017-03-17 07:30:38 -0700 and tagged '2017b' in the development GitHub repository at <https://github.com/eggert/tz>. Here are the SHA-512 checksums for the release files: 9a73af4b868506d1f6287a8285dea489e68f6828da19509114f9144e2a2019c7fd28f4fb98ea907030d11d011ce3a87d99dbe43bca218beddafff151f0d61df1 tzcode2017b.tar.gz 3e090dba1f52e4c63b4930b28f4bf38b56aabd6728f23094cb5801d10f4e464f17231f17b75b8866714bf98199c166ea840de0787b75b2274aa419a4e14bbc4d tzdata2017b.tar.gz 5003caab927eccf1d8f13391f4658733b3cfa05be1fcc99e0ab127ef6673514239d906677ab9b64f51777d450262d1db1868647b6afa868ab0ef93dcc8934db3 tzdb-2017b.tar.lz Here are the GPG checksums for the release files: -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAABAgAGBQJYy/QVAAoJEO2X6Q5iqn40h2cQAJhVT8aErVfu5cdjXIHn97Zr igIlZT+Q+xF5lu8cZxcW6j9bUZ9TG3PVcCnT6ujGtMr4UiTsiPeCmNXmGwtPmMez ZNloo3CBO+kaFFVCijEeNqN3ouXEMdlkfDtbdKKQ3AobQejowu+G2E9Qhmb4rjDj M5naQ+42nmB0mM1j1n4tyc6jL70gRaqSMmTUxVH4B69/GyD4Og4nuM1anfDfq26t dzhesg4q6TrdO5JJUHObH1FAYH95ZxzgVZ5jkT5N4Txl9UukpxI8u49nDfac9QeO RlvKaXcR7WQgC5fNxqvF5DKBzGmnZI4gx4CJMa+7IsjssOTsVmH1nYXsUdgR4kCf x7zH6s0buLICDRCKPr3pep/IYxj2DXYRBT5ViqMlQf3A3wGIgRUF6EPMKI1vfppv fXjdixU4HsZiJS7Epe6kcezcJrZ8n1YWEQxjFe8qYEJs08mApsSC5DGBXcBchLQI 2S6Au6d6fwqO77K7eOgj8MbYjC/Orhz8dIUGtjAjeZ/qek9ON32l0rPt2QxSnODc 43qtY2H7Uvky45J2niyOEnRbSKLSr5NZPdng4pmp376iVCGTisHJlwtRRfdfPGQo 56LUq4x3UaM3zVDHcpCLHvc7VQKYt3uVVzxbf89PN3jHZ459EqpOtM2TJIHtniw+ 8Ytju9WAEg4OscZi6VnF =B5DX -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAABAgAGBQJYy/QVAAoJEO2X6Q5iqn40JJkP/2GuKex77gS9RXlx5iDbW+3x CAz6HEIcNGW2jEZCIM0zdvHH2Rw27/5CGixWWFGW4JWIQRu3Jtma4aCE++XUtYl0 +xHrnm43BmiYNUq7lNQsoGwLYTNMxvlOkk6vMBVRRQvODQGajdSgYC/D0Oc3VGG5 6X5ofl+vTyOpsDtGLtsJcqaaqE5hPf3rUfGWuEDVuwpoiKAckMoB4sNufOsf0DTT iNogrYCnGKLd4SM08xkPY56qipEONYh5u/4lZfcUCPkqtZmp3j3EVzuHS365aTwP 0jhSqTmAlCC7wL1eOQPY4Lot4WebSsdqVGqCfZCpwRfke39FCFCPHyZI8RwbIgRR gxNPV0U5V4FpjTXx1mVjv3m5ibp+4FetCKFvbtX5AKMikaGqujouOlKup899owH2 pFPQ/5O4fJGee51LQQRirnXSYftSplnu7Qz0ti2b43OIVq0JFyqkVCevoSRf1LqZ QXaDQtaVR2Vfm4p2yVD2hBwhpr/ZvTDLRAaynT8eZ1C8DUASAGA/LsplQ62x1mIO inGrNsuIs7MsSy4RAk/VruVnDeUZNnEAYE53dQB0uJHbFNo4FyOu6stp9JNy7k8X 98AuiLdnSPDmCJs69w8BqePcVxnNMgDcHbsDwaPGl/WcDEhLGFkSsHfp02QVTo1L Yi+G86lCBaDMrp4I7g5J =5tCY -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAABAgAGBQJYy/QVAAoJEO2X6Q5iqn40DxIQALEkQyPnAC3PCu10cf1+wPDh vEu8fkMbZ47klCgPbj+ZdtPWRASFc+9BJcE3KiRyxgCYPnMr7XfBlXgq1bPVsl+X h3RJXsQdh8N6hGkL4hPCQ/t+/5SNfFmHudDV71KjaGpERDyAdz2/D7cPY5nGe4r6 hr7SWPO3QXzpnY7qVW7ZCifE/XEr75o5/h9xyIPJanLLltwxE/XTLlwr4yBM91Yt PMQv0bJbyZ+l13QF1P/Rtt7gsOqWuxyNuH+lyPDOC/XN3YG0sTjt8QmpM+svo863 aZVqzjdfnJ7BkQNICc9W5WShXhK6bQNk/lvRinOwXgwzY2tYeqx+jdi2AqEWJK4c xRfUDOePyrDG731oIBKb2J4p1nKuw4MZ1G5RVIHVTk6xf7QL9+1MwRLpxb/o9fOl Vt+T1RZL2v12rLu0/orokeYR3mAsme73k4zBmQODDLXkD2j4GtRLqXroTB1+3y+X njmJRIB7N2SdKx1Kvn2QOkpn+FKpJatMg1B64qGbPgVM0Cf359tHu0G0eRP2SLgI 2e0buF88i3oj9sYJ4d4Nc11qc9W4MQ8qhVG0z9rqFeMronJ5RQoBwM1OkW5ew4Ei /4QWijN0P82fAFwfHUxCzqqLrKmbVSmW80bk9o5EsX1LTOUK4UVJuYazcpIXTj7B ThCKSUwrWbJF62oTuL71 =FavL -----END PGP SIGNATURE----- _______________________________________________ tz-announce mailing list tz-announce(a)iana.org https://mm.icann.org/mailman/listinfo/tz-announce

1 0

2017b announcement?
by Joachim Sauer March 21, 2017

March 21, 2017

Hello, I see that the 2017b update is available for download, but I don't see an announcement in the tz-announce archive. Am I missing something? cheers Joachim

2 1

When did the subdirectory decision get made?
by Matthew Donadio March 19, 2017

March 19, 2017

The northamerica file has this note in it: # From Paul Eggert (2007-08-17): # ... # Other than Indianapolis, the Indiana place names are so nondescript # that they would be ambiguous if we left them at the 'America' level. # So we reluctantly put them all in a subdirectory 'America/Indiana'. I have gone through the mailing list archives from around this time, and also the 8/2005 timeframe (when the Indiana changes were starting to become clear), but I can't find any discussion about this, and Google is failing me. Does anyone remember when the pros and cons of using three levels for names was discussed? I just want to read up on some of that background. Thanks. --Matthew Donadio (matt(a)mxd120.com)

2 1

[PROPOSED] Richard Feynman and Mel Blanc collaborated
by Paul Eggert March 19, 2017

March 19, 2017

* tz-art.htm (Documentaries): Mention Feynman and Blanc. --- tz-art.htm | 1 + 1 file changed, 1 insertion(+) diff --git a/tz-art.htm b/tz-art.htm index 4892412..f726cce 100644 --- a/tz-art.htm +++ b/tz-art.htm @@ -26,6 +26,7 @@ briefly says why France has more time zones than Russia.</a> <li> "About Time" (1962; 53 minutes) is part of the the Bell Science extravaganza, with Frank Baxter, Richard Deacon, and Les Tremayne. +Its advisor was Richard Feynman, and it was voiced by Mel Blanc. (<a href="http://www.imdb.com/title/tt0154110/">IMDb entry</a>.)</li> </ul> <h2>Movies</h2> -- 2.7.4

1 0

Time Zones explained by Radio Free Europe
by Donald MacQueen March 19, 2017

March 19, 2017

All The Time In The World: Explaining The Mysteries Of Time Zones http://www.rferl.org/a/28375932.html

2 1

Palestine Summer Time
by Sharef Mustafa March 19, 2017

March 19, 2017

Hi, Palestine summer time will start on Mar 25th 2017 as per many local news agencies which published the news of the Palestinian cabinet meeting of March 14th which included the government decision of starting the summer time on Mar 25th 2017. However the decree it self is still not uploaded on the cabinet website, also the exact time of the shift was not mentioned, this affects Asia/Gaza & Asia/Hebron time zones, please find below links to some news sites (in Arabic) https://www.maannews.net/Content.aspx?id=897248 https://www.alwatanvoice.com/arabic/news/2017/03/14/1028254.html http://www.arn.ps/archives/194854 http://www.palsawa.com/news/2017/03/14/main/107123.html http://www.rmix.ps/archives/84243 unfortunately I did not find an English resource Regards. Sharef Mustafa

2 1

Why the Ancient Britons did not use Daylight Saving Time
by Jonathan Leffler March 17, 2017

March 17, 2017

http://www.gocomics.com/nonsequitur/2017/03/12 -- Jonathan Leffler <jonathan.leffler(a)gmail.com> #include <disclaimer.h> Guardian of DBD::Informix - v2015.1101 - http://dbi.perl.org "Blessed are we who can laugh at ourselves, for we shall never cease to be amused."

2 1

mktime(): wrong value for DST taken?
by Kees Dekker March 14, 2017

March 14, 2017

Hi, Not sure whether it is related to mktime (see also http://mm.icann.org/pipermail/tz/2017-January/thread.html#24749) but I run into a similar issue. Consider the code below, and compile with (any) tz library (I tried with 2017A code). Save the source and compile with: gcc -o <out> <source> -L <tzdir> -ltz Running the produced exe results in: gcc -o ambigioustest2017a ambigioustest.c -L./tzcode2017a/ -ltz kdekker@nlbavlsm3.infor.com:/home/kdekker/downloads$ ./ambigioustest2017a enter mktime with: 1970/Jan/15278 00:119:30, week day: -858993460, year day: -858993460, dst: -1 the return value of mktime is: 1319957970 normalized times: 2011/Oct/30 01:59:30, week day: Sun, year day: 302, dst: 0 tz=EST, EDT Based on the provided TZ value, I expected that 01:59:30 is still in DST, and thus the returned value by mktime should be 1319954370 (i.e. one hour off). What I'm doing wrong, or what is wrong in the mktime() code? Please not that running the same source by using the built-in glibc mktime() function (i.e. gcc -o <exe> <sourcefile> and no additional flags), the result changes to: enter mktime with: 1970/Jan/15278 00:119:30, week day: -858993460, year day: -858993460, dst: -1 the return value of mktime is: 1319954370 normalized times: 2011/Oct/30 01:59:30, week day: Sun, year day: 302, dst: 1 tz=EST, EDT Note the minor differences with the previous output. Please let me know what should be correct? The provided source code is a part of our larger own test suite. Our test suite tests a wide range of values, especially near boundaries or ambiguous values. Regards, Kees /* start C-code */ #include <time.h> #include <stdio.h> int main(void) { int ret = 0; const char *months[] = { "Jan", "Feb", "Mar", "April", "May", "June", "July", "Aug", "Sep", "Oct", "Nov", "Dec" }; const char *days[] = { "Sun", "Mon", "Tue", "Wed", "Tur", "Fri", "Sat" }; // Back from daylight saving time to normal time. // In 2011, this happened October 30. // At 03:00 hours, local time was set back one hour. // So local time interval 02:00 - 03:00 hours is ambiguous: // It exists both in dayligth saving time and in normal time. putenv("TZ=EST5EDT,M4.1.0/02:00,M10.5.0/02:00"); struct tm tmp = { 30, 119, 0, 15278, 0, 70, -858993460, -858993460, -1}; printf("enter mktime with: %04d/%s/%02d %02d:%02d:%02d, week day: %d, year day: %d, dst: %d\n", tmp.tm_year + 1900, months[tmp.tm_mon], tmp.tm_mday, tmp.tm_hour, tmp.tm_min, tmp.tm_sec, tmp.tm_wday, tmp.tm_yday, tmp.tm_isdst); time_t t = mktime(&tmp); /* expect: t == 1319954370, DST is still on, because it still some seconds before 2:00 */ printf("the return value of mktime is: %lld\n", (long long)t); printf("normalized times: %04d/%s/%02d %02d:%02d:%02d, week day: %s, year day: %d, dst: %d\n", tmp.tm_year + 1900, months[tmp.tm_mon], tmp.tm_mday, tmp.tm_hour, tmp.tm_min, tmp.tm_sec, days[tmp.tm_wday], tmp.tm_yday, tmp.tm_isdst); if (t >= 0) { printf("tz=%s, %s\n", tzname[0], tzname[1]); } return 0; } /* End-of-C-Code */

2 1

Re: [tz] question about mktime_tzname()
by Kees Dekker March 14, 2017

March 14, 2017

Hi, Can anyone help me? In short, I set TZ to EST5EDT,M4.1.0/02:00,M10.5.0/02:00, which means daylight saving for EST (=GMT-5 or GMT-4 if DST is active), with switching DST at first Sunday of April and move to standard time at the last Sunday of October. The input to mktime is (See also attached source code) 1-1-1970, 19:00h (tm_min=1140 = 1140/60 = 19h) local EST time and tm_isdst set to -1. Because of this value, the tz code should figure out that 1-1-1970 is not in DST so the time difference with GMT/UTC is 5 hours. I would exect then mktime() to return 0. This is true if I use the system functions, but mktime() returns -3600 when using the tz library. The output of running the test case with system libraries is: ./tztestcase enter mktime with: 1970/Jan/00 00:1140:00, week day: -858993460, year day: -858993460, dst: -1 the return value of mktime is: 0 normalized times: 1969/Dec/31 19:00:00, week day: Wed, year day: 364, dst: 0 The output of the test case with the tz lib is: ./tztestcase2016j enter mktime with: 1970/Jan/00 00:1140:00, week day: -858993460, year day: -858993460, dst: -1 the return value of mktime is: -3600 normalized times: 1969/Dec/31 19:00:00, week day: Wed, year day: 364, dst: 1 Please correct me if I'm wrong. Is this a bug in the tz code? Please note the differences. From: Kees Dekker Sent: Thursday, January 05, 2017 15:03 To: 'tz(a)iana.org' <tz(a)iana.org> Subject: question about mktime_tzname() Hi, I'm running into a potential bug. Please also see the attached C-source file for a reproduction. Reproduction steps: 1. Build tz code, in such way that a libtz.a exists 2. Compile attached source with (e.g. on Linux): gcc -g -o tztestcase2016j tztestcase.c -L <tzlibdir> -ltz 3. Checking the same test case source code with a system library (instead of IANA libtz.a) can be achieved by omitting -L and -l flags in previous command (see #2). It does not make much sense which version of tzcode is used, I tried 2013i and 2016j and both show the same behavior. The mktime() code returns -3600, while I expect 0. Because the TZ zone is explicitly specified, EST5EDT is GMT-5. So the provided time stamp (31-Jan-1969, 19:00) is exactly the same as UTC value 0 (1-Jan-1970, 00:00 GMT). Both Linux and Windows with system libraries return 0 in this specific case (I used these for reference). The remainder of this email is based on the tzcode2016j source code (e.g. for used line numbers). The provided TZ value is parsed in tzparse() and results in sp->ttis[0] set as DST value, and sp->ttis[1] as standard time value. This is at least contrary to in the else part of the if (*name == ',' || *name == ';') block (there DST is saved in sp->ttis[1]). Just grep on init_ttinfo() calls in localtime.c. However, in localsub(), around line 1428, the i becomes sp->defaulttype (which is zero), i.e. points to the DST value of sp->ttis[], which is assigned to ttisp. As result, because t is below sp->ats[0], DST takes into effect, which is incorrect, as everything after the last Sunday in October and before the first Sunday in April (see attachment, TZ="EST5EDT,M4.1.0/02:00,M10.5.0/02:00") is assumed to be standard time. I'm not sure whether I draw the right conclusion, but because the incorrect assumption of using DST, mktime() returns -3600 (on hour off) instead of the expected 0. Is this conclusion correct? I'm not sure how to fix it. When changing the call to init_ttinfo() and effectively swapping DST and standard time (also for symmetry with the else part) in sp-ttis[] (0 to 1 and 1 to 0) + keeping sp->defaulttype = 0 solved this problem, but introduces other conversion errors around DSTchanges (I don't have yet an reproduction, but can make one if needed). The sp->default type is used (in localsub ()) when if (sp->timecnt == 0 || t < sp->ats[0]). The other approach is to assign sp->defaulttype = 1 when the init_ttinfo() calls are not swapped. Anyhow, there is a tight relationship between the value of sp->defaulttype and the order in which DST/standard times are written in sp->ttis[]. If the previous idea is incorrect (and I guess it is), additional code may be needed in time2sub() if yourtm.tm_isdst == -1. In that case, the provided data in yourtm should be checked whether DST is (or is not) into effect. The found mytm struct should match. Otherwise a DST correction is needed (one-hour shift). The current code mistakenly uses DST, and that is why (if I understand all well) mktime() now returns -3600. If I was not able to explain the issue correctly, please let me know. I'm not sure to understand what's going wrong now, but may be, the provided attachment will help in giving better understanding. Because the provided date is near 1970, quite few steps are needed to see what's happing in localtime.c. Regards, Kees Dekker PS. This email has been sent assuming that attachments will not get lost. Otherwise, just copy paste the code below and save to e.g. tztestcase.c. #ifdef _WIN32 #define _CRT_SECURE_NO_WARNINGS #endif #include <time.h> #include <stdio.h> #include <stdlib.h> int main(void) { int ret = 0; const char *months[] = { "Jan", "Feb", "Mar", "April", "May", "June", "July", "Aug", "Sep", "Oct", "Nov", "Dec" }; const char *days[] = { "Sun", "Mon", "Tue", "Wed", "Tur", "Fri", "Sat" }; /* DST switch in April in first Sunday and October, last Sunday */ putenv("TZ=EST5EDT,M4.1.0/02:00,M10.5.0/02:00"); /* January, 1970, invalid input for tm_mday (0 instead 1..31) */ /* non-normalized input for minutes: 1140/60 = 19, so 19:00 EST5EDT time, which is 5 hours before GMT, and should result in t == 0 below */ /* let system figure out whether DST is effect */ struct tm tmp = { 0, 1140, 0, 0, 0, 70, -858993460, -858993460, -1}; printf("enter mktime with: %04d/%s/%02d %02d:%02d:%02d, week day: %d, year day: %d, dst: %d\n", tmp.tm_year + 1900, months[tmp.tm_mon], tmp.tm_mday, tmp.tm_hour, tmp.tm_min, tmp.tm_sec, tmp.tm_wday, tmp.tm_yday, tmp.tm_isdst); time_t t = mktime(&tmp); /* expect: t == 0, DST is off, time is exactly at the boundary of lowest possible UTC value */ printf("the return value of mktime is: %lld\n", (long long)t); printf("normalized times: %04d/%s/%02d %02d:%02d:%02d, week day: %s, year day: %d, dst: %d\n", tmp.tm_year + 1900, months[tmp.tm_mon], tmp.tm_mday, tmp.tm_hour, tmp.tm_min, tmp.tm_sec, days[tmp.tm_wday], tmp.tm_yday, tmp.tm_isdst); if (t >= 0) { printf("tz=%s, %s\n", tzname[0], tzname[1]); } return 0; }

5 26

Re: [tz] State of Texas – A plan to end daylight saving time
by Steve Jones March 14, 2017

March 14, 2017

Folks: I've closely followed a few specific legislative topics in North America for many years, adding time zone to the list a few years ago. It seems to me that the body of legislation proposed to impact time zone or DST follows the general tendency to have no chance of ever coming to a vote, much less passing. In the US Congress only about one out of 20 bills is passed. I can't cite a similar statistic for state legislatures, but believe the phenomena is even more pronounced at the state level. The vast majority of bills are trial balloons, vanity projects, Quixotic, shots across some bow or another, or just plain crazy. So for no reason other than statistics I doubt this bill will go anywhere, though it is hard to know when we are hearing about a rare bill with "legs" — unless someone with specific inside knowledge shares it with the list. The only legislation I can imagine could ever achieve broad public support would be to abolish DST altogether at the national level, and even that is a long shot. Regards, Steve Jones

2 1

State of Texas – A plan to end daylight saving time
by Vance, Frank March 13, 2017

March 13, 2017

‘ “It’s really time to end this archaic practice of springing forward,” said Rep. Jason Isaac, R-Dripping Springs. And he has a plan. Isaac filed legislation to exempt Texas from daylight saving time.’ http://kxan.com/2017/03/11/state-of-texas-a-plan-to-end-daylight-saving-tim… Regards, F

4 4

NYTimes, New England Atlantic Time
by Steve Allen March 13, 2017

March 13, 2017

NY Times has noticed the New Englanders talking about moving to Atlantic time https://www.nytimes.com/2017/03/12/us/spring-forward-daylight-savings-time.… -- Steve Allen <sla(a)ucolick.org> WGS-84 (GPS) UCO/Lick Observatory--ISB 260 Natural Sciences II, Room 165 Lat +36.99855 1156 High Street Voice: +1 831 459 3046 Lng -122.06015 Santa Cruz, CA 95064 http://www.ucolick.org/~sla/ Hgt +250 m

1 0

Africa - Monrovia - 2017a
by Colin Ashley March 12, 2017

March 12, 2017

Hi, Please could I report a warning seen during ‘zic’ on the 2017 africa timezone file. The offset on line 434 for Monrovia is -004433 which causes the following message: warning: "africa", line 434: time zone abbreviation has too many characters (-004430) Thanks and regards Colin Ashley Actian Corporation

2 1

Haiti on DST again
by Steffen Thorsen March 12, 2017

March 12, 2017

We have received 4 mails from different people telling that Haiti has started DST again today, and this source seems to confirm that, I have not been able to find a more authoritative source: https://www.haitilibre.com/en/news-20319-haiti-notices-time-change-in-haiti… Best regards, Steffen Thorsen - timeanddate.com

2 1

Regarding mktime issue
by Gopesh Kumar Chaudhary March 9, 2017

March 9, 2017

Hello Everyone, This is Gopesh Kumar Chaudhary from India. I have couple of queries regarding mktime function. e.g. TZ=Europe/Berlin (Olson) struct tm prnt_time; prnt_time.tm_wday = 0; prnt_time.tm_mon = 10 - 1; prnt_time.tm_mday = 30; prnt_time.tm_hour = 2; prnt_time.tm_min = 0; prnt_time.tm_sec = 0; prnt_time.tm_year = 116; prnt_time.tm_isdst = -1; Above tm structure represent 30th OCT 2:30 2016 for Europe/Berlin in Olson . For Europe/Berlin DST fallback will happen on 30th Oct at 3 , so clock will show 2 to 3 time period twice. I have set the dst flag to -1 , for mktime to decide whether the given time in tm structure is DST time or non DST time. Now coming to my query : 1) In above mentioned scenario does mktime has the intelligence to decide whether above mentioned time in tm structure is in DST or not as dst flag is set to -1 ? 2) I have a sample code Sample code :- ----------------------- # cat gops.c #include<stdio.h> #include<time.h> int main(int argc,char **argv){ struct tm *at; time_t when,now; now=atoi(argv[1]); at=localtime(&now); at->tm_isdst = -1; when=mktime(at); printf("now=%d when=%d\n",now,when); return 0; } OS: Linux (RHEL 7.2) Platform:x86 TZ:Europe/Berlin (Olson) # ./gops 1477787940 ==============>This epoch is for 2:39 30th Oct 2016 DST now=1477787940 when=1477791540 ====>Here mktime is giving me the epoch for 2:39 30th Oct 2016 non-DST # ./gops 1477791540 ==============>This epoch is for 2:39 30th Oct 2016 non DST now=1477791540 when=1477791540 ====>Here mktime is giving me the epoch for 2:39 30th Oct 2016 non-DST With the above example it can be seen that irrespective of the DST/non-DST window , it is always giving non DST epoch only ---- Is this standard behavior or is this bug in mktime ? Thanks. Regards, Gopesh Kumar Chaudhary

2 3

USNO web site down
by Arthur David Olson March 9, 2017

March 9, 2017

Just in time for this weekend's winter forward in the US, as noted by Neal Augenstein on Twitter: "Hmph, wanna see when spring starts? US Naval Observatory site and master clock are down." https://twitter.com/AugensteinWTOP/status/839900149375774720 http://www.usno.navy.mil/USNO/time/display-clocks/simpletime @dashdashado

2 1

Re: [tz] tz abbr too long in 2017a Africa/Monrovia [was: zic throws warning for 2007a]
by Brian Inglis March 3, 2017

March 3, 2017

On 2017-03-02 18:47, Jonathan Leffler wrote: > On Wed, Mar 1, 2017 at 2:16 PM, Brian Inglis wrote: >On 2017-03-01 14:48, Tim Parenti wrote: >> On 1 March 2017 at 16:42, Brian Inglis wrote: >> Looks like it stores the over long abbreviation. >> So should probably patch: >> --- tz/releases/tzdata2017a/africa 2017-02-23 00:37:19.000000000 -0700 >> +++ tz/releases/tzdata2017b/africa 2017-03-01 14:36:43.479882200 -0700 >> @@ -431,7 +431,7 @@ Link Africa/Nairobi Indian/Mayotte >> # Zone NAME GMTOFF RULES FORMAT [UNTIL] >> Zone Africa/Monrovia -0:43:08 - LMT 1882 >> -0:43:08 - MMT 1919 Mar # Monrovia Mean Time >> - -0:44:30 - -004430 1972 May >> + -0:44:30 - -0044 1972 May >> 0:00 - GMT >> The above patch would be incorrect, though. It would be more correct >> to increase the allowed max abbreviation length. (Even better, >> numerical "abbreviations" like this should just be exempted from the >> caps, since they can technically be of almost any length, even though >> this is the longest they'll be in practice.) >POSIX limit in limits.h: >http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap08.html#tag… >under TZ definition for std and dst (abbrs) >"The interpretation of these fields is unspecified if either field is >less than three bytes (except for the case when dst is missing), more >than {TZNAME_MAX} bytes, or if they contain characters other than those >specified." >http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/limits.h.html#tag_… >"{_POSIX_TZNAME_MAX} >Maximum number of bytes supported for the name of a timezone (not of >the TZ variable). >Value: 6" > Note that the spiel above the entry for {_POSIX_TZNAME_MAX} says: > The /<limits.h>/ header shall define the following symbolic constants > with the values shown. These are the most restrictive values for > certain features on an implementation conforming to this volume of > POSIX.1-2008. Related symbolic constants are defined elsewhere in > this volume of POSIX.1-2008 which reflect the actual implementation > and which need not be as restrictive. For each of these limits, a > conforming implementation shall provide a value at least this large > or shall have no limit. A strictly conforming application must not > require a larger value for correct operation. > Is the code in tzcode intended to be a strictly conforming > application? From: http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap02.html#tag… the application is not a Strictly Conforming POSIX Application as it does not #define _POSIX_C_SOURCE 200809L, and is not a Conforming POSIX Application as it does not include a "statement of conformance that documents all options and limit dependencies, and all other ISO or IEC standards used", although commentary indicates POSIX compliance where notable. AFAICT like many packages, it is intended to be POSIX compliant and provide POSIX compliant implementations, to be portable to POSIX compliant and some non-POSIX systems. -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

1 0

Problem with historical Asia/Manila?
by Paul Goyette March 3, 2017

March 3, 2017

According to the asia file, the Philippines jumped 24 hours on May 11, 1899, from -15:56:00 to +8:04:00 (they moved the international date line?) # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Manila -15:56:00 - LMT 1844 Dec 31 8:04:00 - LMT 1899 May 11 8:00 Phil +08/+09 1942 May 9:00 - +09 1944 Nov 8:00 Phil +08/+09 Yet zdump shows only a 4-minute step in local time, rather than the expected 24-hour step: # zdump -c 1815,2018 -v Asia/Manila Asia/Manila -9223372036854775808 = NULL Asia/Manila -9223372036854689408 = NULL Asia/Manila Tue Dec 31 15:55:59 1844 UT = Mon Dec 30 23:59:59 1844 LMT isdst=0 gmtoff=-57360 Asia/Manila Tue Dec 31 15:56:00 1844 UT = Wed Jan 1 00:00:00 1845 LMT isdst=0 gmtoff=29040 Asia/Manila Wed May 10 15:55:59 1899 UT = Wed May 10 23:59:59 1899 LMT isdst=0 gmtoff=29040 Asia/Manila Wed May 10 15:56:00 1899 UT = Wed May 10 23:56:00 1899 +08 isdst=0 gmtoff=28800 Asia/Manila Sat Oct 31 15:59:59 1936 UT = Sat Oct 31 23:59:59 1936 +08 isdst=0 gmtoff=28800 ... Obviously a low-priority issue, since it's more than 100 years ago, but still would be nice to know why we have a problem. It's not totally out of the realm of probability that someone will move the dateline again, perhaps if the UTC+14 parts of Kiribati were to separate from the rest of the country? :) Data gathered on a NetBSD 7.99.64 system running on amd64 hardware, and using the 2017a tzdata. I think we're still running 2016i version of tzcode. So the question(s): * is zdump wrong? * is the compiled data file wrong? * (most likely) am I just misinterpreting the data? * is this something that has already been fixed in a more recent tzcode release? +------------------+--------------------------+------------------------+ | Paul Goyette | PGP Key fingerprint: | E-mail addresses: | | (Retired) | FA29 0E3B 35AF E8AE 6651 | paul at whooppee.com | | Kernel Developer | 0786 F758 55DE 53BA 7731 | pgoyette at netbsd.org | +------------------+--------------------------+------------------------+

3 3

zic throws warning for 2007a
by Derick Rethans March 1, 2017

March 1, 2017

Hi, I've just updated the PHP version of the TZ database, and while compiling with the current zic, I see: warning: "standard input", line 434: time zone abbreviation has too many characters (-004430) This is because of: 24 #ifndef ZIC_MAX_ABBR_LEN_WO_WARN 25 #define ZIC_MAX_ABBR_LEN_WO_WARN 6 26 #endif /* !defined ZIC_MAX_ABBR_LEN_WO_WARN */ 3108 if (cp - string > ZIC_MAX_ABBR_LEN_WO_WARN) 3109 mp = _("time zone abbreviation has too many characters"); That check was introduced in 2012j as per NEWS: Release 2012j - 2012-11-12 18:34:49 -0800 ... zic -v now complains about abbreviations that are less than 3 or more than 6 characters, as per Posix. Formerly, it checked for abbreviations that were more than 3. cheers, Derick -- https://derickrethans.nl | https://xdebug.org | https://dram.io Like Xdebug? Consider a donation: https://xdebug.org/donate.php twitter: @derickr and @xdebug

6 6

TZ changes
by Igor Trud Feb. 28, 2017

Feb. 28, 2017

Hi. Europe/Volgograd is not in MSK ( GMT+3) since 03 Dec 2016 Now, its MSK + 1 (GMT +4). Should tzinfo database accept this change ? Thanks. Igor.

2 1

[PATCH] Fix warnings if !ALL_STATE: address of gmtmem always, evaluates as true
by Andreas Stieger Feb. 28, 2017

Feb. 28, 2017

Hello, fixes some compiler warnings: If ALL_STATE is not defined, the address of gmtcheck always evaluates to true. Andreas -- Andreas Stieger <astieger(a)suse.com> Project Manager Security SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)

2 3

[tz-announce] 2017a release of tz code and data available
by Paul Eggert Feb. 28, 2017

Feb. 28, 2017

The 2017a release of the tz code and data is available. It reflects the following changes, which were either circulated on the tz mailing list or are relatively minor technical or administrative changes: Briefly: Southern Chile moves from -04/-03 to -03, and Mongolia discontinues DST. Changes to future time stamps Mongolia no longer observes DST. (Thanks to Ganbold Tsagaankhuu.) Chile's Region of Magallanes moves from -04/-03 to -03 year-round. Its clocks diverge from America/Santiago starting 2017-05-13 at 23:00, hiving off a new zone America/Punta_Arenas. Although the Chilean government says this change expires in May 2019, for now assume it's permanent. (Thanks to Juan Correa and Deborah Goldsmith.) This also affects Antarctica/Palmer. Changes to past time stamps Fix many entries for historical time stamps for Europe/Madrid before 1979, to agree with tables compiled by Pere Planesas of the National Astronomical Observatory of Spain. As a side effect, this changes some time stamps for Africa/Ceuta before 1929, which are probably guesswork anyway. (Thanks to Steve Allen and Pierpaolo Bernardi for the heads-ups, and to Michael Deckers for correcting the 1901 transition.) Ecuador observed DST from 1992-11-28 to 1993-02-05. (Thanks to Alois Treindl.) Asia/Atyrau and Asia/Oral were at +03 (not +04) before 1930-06-21. (Thanks to Stepan Golosunov.) Changes to past and future time zone abbreviations Switch to numeric time zone abbreviations for South America, as part of the ongoing project of removing invented abbreviations. This avoids the need to invent an abbreviation for the new Chilean new zone. Similarly, switch from invented to numeric time zone abbreviations for Afghanistan, American Samoa, the Azores, Bangladesh, Bhutan, the British Indian Ocean Territory, Brunei, Cape Verde, Chatham Is, Christmas I, Cocos (Keeling) Is, Cook Is, Dubai, East Timor, Eucla, Fiji, French Polynesia, Greenland, Indochina, Iran, Iraq, Kiribati, Lord Howe, Macquarie, Malaysia, the Maldives, Marshall Is, Mauritius, Micronesia, Mongolia, Myanmar, Nauru, Nepal, New Caledonia, Niue, Norfolk I, Palau, Papua New Guinea, the Philippines, Pitcairn, Qatar, Réunion, St Pierre & Miquelon, Samoa, Saudi Arabia, Seychelles, Singapore, Solomon Is, Tokelau, Tuvalu, Wake, Vanuatu, Wallis & Futuna, and Xinjiang; for 20-minute daylight saving time in Ghana before 1943; for half-hour daylight saving time in Belize before 1944 and in the Dominican Republic before 1975; and for Canary Islands before 1946, for Guinea-Bissau before 1975, for Iceland before 1969, for Indian Summer Time before 1942, for Indonesia before around 1964, for Kenya before 1960, for Liberia before 1973, for Madeira before 1967, for Namibia before 1943, for the Netherlands in 1937-9, for Pakistan before 1971, for Western Sahara before 1977, and for Zaporozhye in 1880-1924. For Alaska time from 1900 through 1967, instead of "CAT" use the abbreviation "AST", the abbreviation commonly used at the time (Atlantic Standard Time had not been standardized yet). Use "AWT" and "APT" instead of the invented abbreviations "CAWT" and "CAPT". Use "CST" and "CDT" instead of invented abbreviations for Macau before 1999 and Taiwan before 1938, and use "JST" instead of the invented abbreviation "JCST" for Japan and Korea before 1938. Change to database entry category Move the Pacific/Johnston link from 'australasia' to 'backward', since Johnston is now uninhabited. Changes to code zic no longer mishandles some transitions in January 2038 when it attempts to work around Qt bug 53071. This fixes a bug affecting Pacific/Tongatapu that was introduced in zic 2016e. localtime.c now contains a workaround, useful when loading a file generated by a buggy zic. (Problem and localtime.c fix reported by Bradley White.) zdump -i now outputs non-hour numeric time zone abbreviations without a colon, e.g., "+0530" rather than "+05:30". This agrees with zic %z and with common practice, and simplifies auditing of zdump output. zdump is now buildable again with -DUSE_LTZ=0. (Problem reported by Joseph Myers.) zdump.c now always includes private.h, to avoid code duplication with private.h. (Problem reported by Kees Dekker.) localtime.c no longer mishandles early or late timestamps when TZ is set to a POSIX-style string that specifies DST. (Problem reported by Kees Dekker.) date and strftime now cause %z to generate "-0000" instead of "+0000" when the UT offset is zero and the time zone abbreviation begins with "-". Changes to documentation and commentary The 'Theory' file now better documents choice of historical time zone abbreviations. (Problems reported by Michael Deckers.) tz-link.htm now covers leap smearing, which is popular in clouds. Here are links to the release files: https://www.iana.org/time-zones/repository/releases/tzcode2017a.tar.gz https://www.iana.org/time-zones/repository/releases/tzdata2017a.tar.gz https://www.iana.org/time-zones/repository/releases/tzdb-2017a.tar.lz As usual, links to the latest release files are here: https://www.iana.org/time-zones/repository/tzcode-latest.tar.gz https://www.iana.org/time-zones/repository/tzdata-latest.tar.gz https://www.iana.org/time-zones/repository/tzdb-latest.tar.lz Links are also available via plain HTTP, and via FTP from ftp://ftp.iana.org/tz/releases with the same basenames as above. Each release file has a GPG signature, which can be retrieved by appending ".asc" to the above URLs. Copies of these signatures are appended to this message. This release corresponds to commit 8beaf3b064b8edcb09babb62e530993808003802 dated 2017-02-28 00:05:36 -0800 and tagged '2017a' in the development GitHub repository at <https://github.com/eggert/tz>. Here are the SHA-512 checksums for the release files: 36d744debd5263b6be39b3a9a146b7db1876f216a4bfc62b46631745861a9c03eda3220f213def86c724d3a11c41398c65c2e5d013ff2c1900e7bfc5e7844025 tzcode2017a.tar.gz fe57930711998a0755749a2bf1b32fdbc9e6ee249762017beea52eae7e521236396300fe2d79298fd81eb6d73fb7567884c35995ed248be06188329d937e3873 tzdata2017a.tar.gz 9004e74718455e8199f4dc301a7e3f74dfa37b5ed9de4a41f2cd88a97e759f8f2aea7bb92c0c022515eab88a2169f08606c47c621479374f884130a34bfc188c tzdb-2017a.tar.lz Here are the GPG checksums for the release files: -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAABAgAGBQJYtTBSAAoJEO2X6Q5iqn40sWUQAJ8XTHkp/BXYPfwQf3SXJkog e2jXeW4U5CtmBvo5SmENeWVd69piEBsbgVYmzfIIQy9kXt/jJcHIuBAIUVF6UqSx 4MOeogfrM0+cqXNWZMza26aHivOf8ypqnyekVtrHf0z3oC7EhwPcfZWIeVqgS0Oc 5PAja8V/jewcq1vaIk8lp7cJ2eUGJRNQSco4Vd0jsoltrb52Vn7WJ/sf/EYS+gTs B/iEiSN+SFHhnkNLUlm5xoJib0+wBrZzEqowoPel54h0XT9pA+sUdbeW+w6VeQPz JiJbFQwKvZIdADcPseGyYaexEiSHuUokwGOGsoB14kEUwlIjvSgUq7l2CuIvmLFA fH7edetBYmedN9sbO1Sa2dJAiL4W0kbERW9EtKZ1G5ixOEVz/dtTEMznj2JTi3bl yTs1rSBMeZogjo0nySZeK4KpoL5VOxdze05g+DQ/jbeksCOwPPTtHtNf9tK1fwgy GyBt5R0U6j/Hjm0mQgiK4enmVxa55HVCCXnbyo/A08u0x7U5g16ebiSax/q5bW5I IAgYRBYzanccBVjIg0bW0pQXzJ5fmPnHo20dxkRlIqTAkoVTF62fOio5LCN4XQRK dt57WuvEHj4MIwj/12dipcCY1qFlqxOx3BegEQNvVd67z0Z4cBVW/Ng2RmjSGtEl 0DBAIPPrMvZ5pwWJZiJF =EVYD -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAABAgAGBQJYtTBSAAoJEO2X6Q5iqn40qlgP/i6xLqi7ojaiKm9x7ZmYDVxh ggMmRyR8YDE8/eSSZB03fayVCIdVNj96J2t9beJXnyRISZbhOj3vPrlSziCBNR29 QjX6Sbh3N7y2QlWvgdExqqKCM69zV3Q9Zz51cFz4kiACue0dvmPYWPjUqvV1m42W BiqL9oVwhvbnp14kJVcLOQINrlhWOTY4/MDfBQAVMPpvntJSpitOnC4y30xLsie2 1MR6/oHVuEhmrfk8ePhgwVm64lg6o8sVl26kO/baNeqo0ST/LAP2CJqhM+54YB+c 0IK7kXk4Te97Hq0/0G7ZHugySjVIQGvrcI7bIcam9pXVRCveRJvdGH5OZpY1MD09 RF66Y4n9E1iD4MlQEgaizjAIjy8JrwJUc0W9m/GHSJecwYZXKbZYkqQpgQGfpA4/ fz3+BUr0AaUh/JGtdyXTm9v/JEwvJsJvu77wtSNLyA4+XR3cZOfhgJ5syw7tDCXy tBHIl74845Ky/FrheXp7vfOUayEn623r7RyLEOt65v7Qn2AwDwc+u73qpVW/e25r bD7mWDLXOyFgERhTLZafRahMxugFTl1mFikygI12TvDPvsgcBwAEDUDdu8e3MU1+ HdoBu6aGIMP8OLqN3cqrJlUF/dqn/JeeGnUAVQZlXHb7oWu7mf7OOrIzjQC5xG8y KDL+94hpsq/thK712LfA =+3fY -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAABAgAGBQJYtTBSAAoJEO2X6Q5iqn40xF0P/33nPe1C0P4EGhqzkXce/Bee iKYHWfeYXzXdRoQrjLGWuzUP2hJhZVq0Sw6ylYXwHwf0lVs2PfkFnkDfeV+5z7Fw cABcJO35B9GeSxXFhYvznvK2Azes0YYQ1ltBcNxaLeDTyi/a+vVexvzxrkbh+Vx7 wDf5ZS0Xn7Jtq+fTG1K7WVSzETw39Bw29E2K/ITWSEg83WJ8Db3IuhlC6hmu6lyF C6cMY+6qY7XylvOLqZkF2b1+l6d+TNI+5s+wNchq/tZQzShGKsjCPAx4xj7ebUtt JJAJzWuw6OHkXsor2dKpcRuqhrTQx6Oybfj85WA3+kNWaTTdDa2oxWOXGDzK5ySU hFxJFD1Q1U5nUkxMBdEKsuG2P3JPLEH0sVJX9TwMnyAlZM3mI9sJMGnP9ssOearG 0mF+kL7fQB3Y2+y67i9cFNJRNchK6O4/FiBe+PdNYXwSrlPqt+9VlEdqq6B3jkJe /gBJCi1lMpk9tVAntxtMWCvYr9pZn6eQnyBGW8urdUMdNcsr1w1SxGf1bPT5zpKM zhPfHlVJxS0lP6aTwxEMUKhM5WXZcw10kR3oabLZOmQUGuZPG7JUWL1T7hie6FAf Wso1rz/Pw08dMvLsU8R0lSj5IQFCioOm0NP/seo/dG032CY2AGh32PpPfegziiA5 N0j4ihRNDSRAKySyK1WY =TwWB -----END PGP SIGNATURE----- _______________________________________________ tz-announce mailing list tz-announce(a)iana.org https://mm.icann.org/mailman/listinfo/tz-announce

1 0

ISO 3166 (GB): United Kingdom
by Andreas Stieger Feb. 28, 2017

Feb. 28, 2017

Hello, the attached corrects the ISO 3166 short name from "Britain (UK)" to "United Kingdom". Andreas -- Andreas Stieger <astieger(a)suse.com> Project Manager Security SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)

5 4

Montana proposed DST cancellation
by Andreas Stieger Feb. 27, 2017

Feb. 27, 2017

Hello, The proposed Montana DST changes was mentioned before: http://mm.icann.org/pipermail/tz/2017-February/024849.html Just noting that SB 206 [1] passed 3rd Reading [2] in the Montana Senate and is now in House Committee. [1] http://leg.mt.gov/bills/2017/billpdf/SB0206.pdf [2] http://laws.leg.mt.gov/legprd/LAW0203W$BSRV.ActionQuery?P_SESS=20171&P_BLTP… Andreas -- Andreas Stieger <astieger(a)suse.com> Project Manager Security SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)

2 1

[PROPOSED] Fix Sierra Leone typo for 1957
by Paul Eggert Feb. 23, 2017

Feb. 23, 2017

* backzone (Africa/Freetown): Fix typo in time zone abbreviation for January through May 1957. (Thanks to Michael Deckers.) --- backzone | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/backzone b/backzone index 119584a..9ce7831 100644 --- a/backzone +++ b/backzone @@ -129,7 +129,7 @@ Rule SL 1957 1962 - Sep 1 0:00 0 GMT Zone Africa/Freetown -0:53:00 - LMT 1882 -0:53:00 - FMT 1913 Jun # Freetown Mean Time -1:00 SL %s 1957 - 0:00 SL %s + 0:00 SL GMT/+01 # Botswana # From Paul Eggert (2013-02-21): -- 2.9.3

1 0

TIme zones in the arts: xkcd #1799
by Ice Karma (J. Connell) 「氷宿縁」 Feb. 23, 2017

Feb. 23, 2017

Many of you may have already seen this, but for the benefit of those who have not: Bad Map Projection: Time Zones <https://xkcd.com/1799/> —Ice Karma

1 0

[PROPOSED 1/7] Remove many invented abbrs in 'africa', 'backzone'
by Paul Eggert Feb. 23, 2017

Feb. 23, 2017

* NEWS: Document this. * africa (Atlantic/Cape_Verde, Africa/Accra, Africa/Bissau) (Africa/Nairobi, Africa/Monrovia, Indian/Mauritius, Africa/El_Aaiun) (Africa/Windhoek, Indian/Reunion, Indian/Mahe): * backzone (Africa/Bamako, Africa/Banjul, Africa/Conakry) (Africa/Dakar, Africa/Dar_es_Salaam, SL, Africa/Kampala): (Africa/Luanda, Africa/Mogadishu, Africa/Niamey, Africa/Nouakchott) (America/Argentina/ComodRivadavia, America/Aruba, America/Rosario) (Asia/Aden, Asia/Bahrain, Asia/Chongqing, Asia/Hanoi, Asia/Harbin) (Asia/Kashgar, Asia/Kuwait, Asia/Muscat, Asia/Phnom_Penh) (Asia/Vientiane, Atlantic/Jan_Mayen, Pacific/Midway, Pacific/Saipan): Prefer numeric time zone abbreviations to invented or dubious ones. --- NEWS | 30 ++++++++------ africa | 90 ++++++++++++++++++++---------------------- backzone | 136 +++++++++++++++++++++++++++++++-------------------------------- 3 files changed, 126 insertions(+), 130 deletions(-) diff --git a/NEWS b/NEWS index b3273ce..185524f 100644 --- a/NEWS +++ b/NEWS @@ -39,19 +39,23 @@ Unreleased, experimental changes new zone. Similarly, switch from invented to numeric time zone abbreviations for Afghanistan, American Samoa, the Azores, Bangladesh, Bhutan, the British Indian Ocean Territory, Brunei, - Chatham Is, Christmas I, Cocos (Keeling) Is, Cook Is, Dubai, East - Timor, Eucla, Fiji, French Polynesia, Greenland, Indochina, Iran, - Iraq, Kiribati, Lord Howe, Macquarie, Malaysia, the Maldives, - Marshall Is, Micronesia, Mongolia, Myanmar, Nauru, Nepal, New - Caledonia, Niue, Norfolk I, Palau, Papua New Guinea, the - Philippines, Pitcairn, Qatar, St Pierre & Miquelon, Samoa, Saudi - Arabia, Singapore, Solomon Is, Tokelau, Tuvalu, Wake, Vanuatu, - Wallis & Futuna, and Xinjiang; for half-hour daylight saving time - in Belize before 1944 and in the Dominican Republic before 1975; - and for Canary Islands before 1946, for Madeira before 1967, for - Iceland before 1969, for Indian Summer Time before 1942, for - Indonesia before around 1964, for the Netherlands in 1937-9, for - Pakistan before 1971, and for Zaporozhye in 1880-1924. + Cape Verde, Chatham Is, Christmas I, Cocos (Keeling) Is, Cook Is, + Dubai, East Timor, Eucla, Fiji, French Polynesia, Greenland, + Indochina, Iran, Iraq, Kiribati, Lord Howe, Macquarie, Malaysia, + the Maldives, Marshall Is, Mauritius, Micronesia, Mongolia, + Myanmar, Nauru, Nepal, New Caledonia, Niue, Norfolk I, Palau, + Papua New Guinea, the Philippines, Pitcairn, Qatar, Réunion, St + Pierre & Miquelon, Samoa, Saudi Arabia, Seychelles, Singapore, + Solomon Is, Tokelau, Tuvalu, Wake, Vanuatu, Wallis & Futuna, and + Xinjiang; for 20-minute daylight saving time in Ghana before 1943; + for half-hour daylight saving time in Belize before 1944 and in + the Dominican Republic before 1975; and for Canary Islands before + 1946, for Guinea-Bissau before 1975, for Iceland before 1969, for + Indian Summer Time before 1942, for Indonesia before around 1964, + for Kenya before 1960, for Liberia before 1973, for Madeira before + 1967, for Namibia before 1943, for the Netherlands in 1937-9, for + Pakistan before 1971, for Western Sahara before 1977, and for + Zaporozhye in 1880-1924. For Alaska time from 1900 through 1967, instead of "CAT" use the abbreviation "AST", the abbreviation commonly used at the time diff --git a/africa b/africa index 010050e..2faeb27 100644 --- a/africa +++ b/africa @@ -6,7 +6,7 @@ # tz(a)iana.org for general use in the future). For more, please see # the file CONTRIBUTING in the tz distribution. -# From Paul Eggert (2017-02-10): +# From Paul Eggert (2017-02-20): # # Unless otherwise specified, the source for data through 1990 is: # Thomas G. Shanks and Rique Pottenger, The International Atlas (6th edition), @@ -31,39 +31,33 @@ # A reliable and entertaining source about time zones is # Derek Howse, Greenwich time and longitude, Philip Wilson Publishers (1997). # +# European-style abbreviations are commonly used along the Mediterranean. +# For sub-Saharan Africa abbreviations were less standardized. # Previous editions of this database used WAT, CAT, SAT, and EAT -# for +0:00 through +3:00, respectively, -# but Mark R V Murray reports that -# 'SAST' is the official abbreviation for +2:00 in the country of South Africa, -# 'CAT' is commonly used for +2:00 in countries north of South Africa, and -# 'WAT' is probably the best name for +1:00, as the common phrase for +# for UT +00 through +03, respectively, +# but in 1997 Mark R V Murray reported that +# 'SAST' is the official abbreviation for +02 in the country of South Africa, +# 'CAT' is commonly used for +02 in countries north of South Africa, and +# 'WAT' is probably the best name for +01, as the common phrase for # the area that includes Nigeria is "West Africa". -# He has heard of "Western Sahara Time" for +0:00 but can find no reference. -# -# To make things confusing, 'WAT' seems to have been used for -1:00 long ago; -# I'd guess that this was because people needed _some_ name for -1:00, -# and at the time, far west Africa was the only major land area in -1:00. -# This usage is now obsolete, as the last use of -1:00 on the African -# mainland seems to have been 1976 in Western Sahara. -# -# To summarize, the following abbreviations seem to have some currency: -# -1:00 WAT West Africa Time (no longer used) -# 0:00 GMT Greenwich Mean Time -# 2:00 CAT Central Africa Time -# 2:00 SAST South Africa Standard Time -# and Murray suggests the following abbreviation: -# 1:00 WAT West Africa Time -# I realize that this leads to 'WAT' being used for both -1:00 and 1:00 -# for times before 1976, but this is the best I can think of -# until we get more information. +# +# To summarize, the following abbreviations seemed to have some currency: +# +00 GMT Greenwich Mean Time +# +02 CAT Central Africa Time +# +02 SAST South Africa Standard Time +# and Murray suggested the following abbreviation: +# +01 WAT West Africa Time +# Murray's suggestion seems to have caught on in news reports and the like. +# I vaguely recall 'WAT' also being used for -01 in the past but +# cannot now come up with solid citations. # # I invented the following abbreviations; corrections are welcome! -# 2:00 WAST West Africa Summer Time -# 2:30 BEAT British East Africa Time (no longer used) -# 2:45 BEAUT British East Africa Unified Time (no longer used) -# 3:00 CAST Central Africa Summer Time (no longer used) -# 3:00 SAST South Africa Summer Time (no longer used) -# 3:00 EAT East Africa Time +# +02 WAST West Africa Summer Time +# +03 CAST Central Africa Summer Time (no longer used) +# +03 SAST South Africa Summer Time (no longer used) +# +03 EAT East Africa Time +# 'EAT' also seems to have caught on; the others are rare but are paired +# with better-attested non-DST abbreviations. # Algeria # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S @@ -121,17 +115,17 @@ Zone Africa/Algiers 0:12:12 - LMT 1891 Mar 15 0:01 # Cape Verde / Cabo Verde # -# Shanks gives 1907 for the transition to CVT. +# Shanks gives 1907 for the transition to +02. # Perhaps the 1911-05-26 Portuguese decree -# http://dre.pt/pdf1sdip/1911/05/12500/23132313.pdf +# https://dre.pt/pdf1sdip/1911/05/12500/23132313.pdf # merely made it official? # # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Atlantic/Cape_Verde -1:34:04 - LMT 1907 # Praia - -2:00 - CVT 1942 Sep - -2:00 1:00 CVST 1945 Oct 15 - -2:00 - CVT 1975 Nov 25 2:00 - -1:00 - CVT + -2:00 - -02 1942 Sep + -2:00 1:00 -01 1945 Oct 15 + -2:00 - -02 1975 Nov 25 2:00 + -1:00 - -01 # Central African Republic # See Africa/Lagos. @@ -388,7 +382,7 @@ Rule Ghana 1920 1942 - Sep 1 0:00 0:20 GHST Rule Ghana 1920 1942 - Dec 31 0:00 0 GMT # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Africa/Accra -0:00:52 - LMT 1918 - 0:00 Ghana %s + 0:00 Ghana GMT/+0020 # Guinea # See Africa/Abidjan. @@ -397,20 +391,20 @@ Zone Africa/Accra -0:00:52 - LMT 1918 # # Shanks gives 1911-05-26 for the transition to WAT, # evidently confusing the date of the Portuguese decree -# http://dre.pt/pdf1sdip/1911/05/12500/23132313.pdf +# https://dre.pt/pdf1sdip/1911/05/12500/23132313.pdf # with the date that it took effect, namely 1912-01-01. # # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Africa/Bissau -1:02:20 - LMT 1912 Jan 1 - -1:00 - WAT 1975 + -1:00 - -01 1975 0:00 - GMT # Kenya # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Africa/Nairobi 2:27:16 - LMT 1928 Jul 3:00 - EAT 1930 - 2:30 - BEAT 1940 - 2:45 - BEAUT 1960 + 2:30 - +0230 1940 + 2:45 - +0245 1960 3:00 - EAT Link Africa/Nairobi Africa/Addis_Ababa # Ethiopia Link Africa/Nairobi Africa/Asmara # Eritrea @@ -437,7 +431,7 @@ Link Africa/Nairobi Indian/Mayotte # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Africa/Monrovia -0:43:08 - LMT 1882 -0:43:08 - MMT 1919 Mar # Monrovia Mean Time - -0:44:30 - LRT 1972 May # Liberia Time + -0:44:30 - -004430 1972 May 0:00 - GMT ############################################################################### @@ -596,7 +590,7 @@ Rule Mauritius 2008 only - Oct lastSun 2:00 1:00 S Rule Mauritius 2009 only - Mar lastSun 2:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Indian/Mauritius 3:50:00 - LMT 1907 # Port Louis - 4:00 Mauritius MU%sT # Mauritius Time + 4:00 Mauritius +04/+05 # Agalega Is, Rodriguez # no information; probably like Indian/Mauritius @@ -915,14 +909,14 @@ Zone Africa/Casablanca -0:30:20 - LMT 1913 Oct 26 # since most of it was then controlled by Morocco. Zone Africa/El_Aaiun -0:52:48 - LMT 1934 Jan # El Aaiún - -1:00 - WAT 1976 Apr 14 + -1:00 - -01 1976 Apr 14 0:00 Morocco WE%sT # Mozambique # # Shanks gives 1903-03-01 for the transition to CAT. # Perhaps the 1911-05-26 Portuguese decree -# http://dre.pt/pdf1sdip/1911/05/12500/23132313.pdf +# https://dre.pt/pdf1sdip/1911/05/12500/23132313.pdf # merely made it official? # # Zone NAME GMTOFF RULES FORMAT [UNTIL] @@ -958,7 +952,7 @@ Rule Namibia 1994 max - Sep Sun>=1 2:00 1:00 S Rule Namibia 1995 max - Apr Sun>=1 2:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Africa/Windhoek 1:08:24 - LMT 1892 Feb 8 - 1:30 - SWAT 1903 Mar # SW Africa Time + 1:30 - +0130 1903 Mar 2:00 - SAST 1942 Sep 20 2:00 2:00 1:00 SAST 1943 Mar 21 2:00 2:00 - SAST 1990 Mar 21 # independence @@ -985,7 +979,7 @@ Link Africa/Lagos Africa/Porto-Novo # Benin # Réunion # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Indian/Reunion 3:41:52 - LMT 1911 Jun # Saint-Denis - 4:00 - RET # Réunion Time + 4:00 - +04 # # Crozet Islands also observes Réunion time; see the 'antarctica' file. # @@ -1020,7 +1014,7 @@ Zone Indian/Reunion 3:41:52 - LMT 1911 Jun # Saint-Denis # Seychelles # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Indian/Mahe 3:41:48 - LMT 1906 Jun # Victoria - 4:00 - SCT # Seychelles Time + 4:00 - +04 # From Paul Eggert (2001-05-30): # Aldabra, Farquhar, and Desroches, originally dependencies of the # Seychelles, were transferred to the British Indian Ocean Territory diff --git a/backzone b/backzone index 4a5085f..119584a 100644 --- a/backzone +++ b/backzone @@ -65,7 +65,7 @@ Link Africa/Asmara Africa/Asmera # Mali (southern) Zone Africa/Bamako -0:32:00 - LMT 1912 0:00 - GMT 1934 Feb 26 - -1:00 - WAT 1960 Jun 20 + -1:00 - -01 1960 Jun 20 0:00 - GMT # Central African Republic @@ -75,7 +75,7 @@ Zone Africa/Bangui 1:14:20 - LMT 1912 # Gambia Zone Africa/Banjul -1:06:36 - LMT 1912 -1:06:36 - BMT 1935 # Banjul Mean Time - -1:00 - WAT 1964 + -1:00 - -01 1964 0:00 - GMT # Malawi @@ -93,18 +93,18 @@ Zone Africa/Bujumbura 1:57:28 - LMT 1890 # Guinea Zone Africa/Conakry -0:54:52 - LMT 1912 0:00 - GMT 1934 Feb 26 - -1:00 - WAT 1960 + -1:00 - -01 1960 0:00 - GMT # Senegal Zone Africa/Dakar -1:09:44 - LMT 1912 - -1:00 - WAT 1941 Jun + -1:00 - -01 1941 Jun 0:00 - GMT # Tanzania Zone Africa/Dar_es_Salaam 2:37:08 - LMT 1931 3:00 - EAT 1948 - 2:45 - BEAUT 1961 + 2:45 - +0245 1961 3:00 - EAT # Djibouti @@ -122,9 +122,9 @@ Zone Africa/Douala 0:38:48 - LMT 1912 # The International Hydrographic Bulletin, 1932-33, p 63 says that # Sierra Leone would advance its clocks by 20 minutes on 1933-10-01. # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S -Rule SL 1935 1942 - Jun 1 0:00 0:40 SLST -Rule SL 1935 1942 - Oct 1 0:00 0 WAT -Rule SL 1957 1962 - Jun 1 0:00 1:00 SLST +Rule SL 1935 1942 - Jun 1 0:00 0:40 -0020 +Rule SL 1935 1942 - Oct 1 0:00 0 -01 +Rule SL 1957 1962 - Jun 1 0:00 1:00 +01 Rule SL 1957 1962 - Sep 1 0:00 0 GMT Zone Africa/Freetown -0:53:00 - LMT 1882 -0:53:00 - FMT 1913 Jun # Freetown Mean Time @@ -153,8 +153,8 @@ Zone Africa/Juba 2:06:24 - LMT 1931 # Uganda Zone Africa/Kampala 2:09:40 - LMT 1928 Jul 3:00 - EAT 1930 - 2:30 - BEAT 1948 - 2:45 - BEAUT 1957 + 2:30 - +0230 1948 + 2:45 - +0245 1957 3:00 - EAT # Rwanda @@ -177,11 +177,11 @@ Zone Africa/Lome 0:04:52 - LMT 1893 # # Shanks gives 1911-05-26 for the transition to WAT, # evidently confusing the date of the Portuguese decree -# http://dre.pt/pdf1sdip/1911/05/12500/23132313.pdf +# https://dre.pt/pdf1sdip/1911/05/12500/23132313.pdf # with the date that it took effect, namely 1912-01-01. # Zone Africa/Luanda 0:52:56 - LMT 1892 - 0:52:04 - AOT 1912 Jan 1 # Angola Time + 0:52:04 - +005204 1912 Jan 1 1:00 - WAT # Democratic Republic of the Congo (east) @@ -216,19 +216,19 @@ Zone Africa/Mbabane 2:04:24 - LMT 1903 Mar # Somalia Zone Africa/Mogadishu 3:01:28 - LMT 1893 Nov 3:00 - EAT 1931 - 2:30 - BEAT 1957 + 2:30 - +0230 1957 3:00 - EAT # Niger Zone Africa/Niamey 0:08:28 - LMT 1912 - -1:00 - WAT 1934 Feb 26 + -1:00 - -01 1934 Feb 26 0:00 - GMT 1960 1:00 - WAT # Mauritania Zone Africa/Nouakchott -1:03:48 - LMT 1912 0:00 - GMT 1934 Feb 26 - -1:00 - WAT 1960 Nov 28 + -1:00 - -01 1960 Nov 28 0:00 - GMT # Burkina Faso @@ -264,19 +264,19 @@ Zone America/Antigua -4:07:12 - LMT 1912 Mar 2 # The name "Comodoro Rivadavia" exceeds the 14-byte POSIX limit. Zone America/Argentina/ComodRivadavia -4:30:00 - LMT 1894 Oct 31 -4:16:48 - CMT 1920 May - -4:00 - ART 1930 Dec - -4:00 Arg AR%sT 1969 Oct 5 - -3:00 Arg AR%sT 1991 Mar 3 - -4:00 - WART 1991 Oct 20 - -3:00 Arg AR%sT 1999 Oct 3 - -4:00 Arg AR%sT 2000 Mar 3 - -3:00 - ART 2004 Jun 1 - -4:00 - WART 2004 Jun 20 - -3:00 - ART + -4:00 - -04 1930 Dec + -4:00 Arg -04/-03 1969 Oct 5 + -3:00 Arg -03/-02 1991 Mar 3 + -4:00 - -04 1991 Oct 20 + -3:00 Arg -03/-02 1999 Oct 3 + -4:00 Arg -04/-03 2000 Mar 3 + -3:00 - -03 2004 Jun 1 + -4:00 - -04 2004 Jun 20 + -3:00 - -03 # Aruba Zone America/Aruba -4:40:24 - LMT 1912 Feb 12 # Oranjestad - -4:30 - ANT 1965 # Netherlands Antilles Time + -4:30 - -0430 1965 -4:00 - AST # Cayman Is @@ -365,12 +365,12 @@ Zone America/Montserrat -4:08:52 - LMT 1911 Jul 1 0:01 # Cork Hill # Formosa (FM), La Pampa (LP), Chubut (CH) Zone America/Rosario -4:02:40 - LMT 1894 Nov -4:16:44 - CMT 1920 May - -4:00 - ART 1930 Dec - -4:00 Arg AR%sT 1969 Oct 5 - -3:00 Arg AR%sT 1991 Jul - -3:00 - ART 1999 Oct 3 0:00 - -4:00 Arg AR%sT 2000 Mar 3 0:00 - -3:00 - ART + -4:00 - -04 1930 Dec + -4:00 Arg -04/-03 1969 Oct 5 + -3:00 Arg -03/-02 1991 Jul + -3:00 - -03 1999 Oct 3 0:00 + -4:00 Arg -04/-03 2000 Mar 3 0:00 + -3:00 - -03 # St Kitts-Nevis Zone America/St_Kitts -4:10:52 - LMT 1912 Mar 2 # Basseterre @@ -403,12 +403,12 @@ Link Antarctica/McMurdo Antarctica/South_Pole # Milne says 2:59:54 was the meridian of the saluting battery at Aden, # and that Yemen was at 1:55:56, the meridian of the Hagia Sophia. Zone Asia/Aden 2:59:54 - LMT 1950 - 3:00 - AST + 3:00 - +03 # Bahrain Zone Asia/Bahrain 3:22:20 - LMT 1920 # Manamah - 4:00 - GST 1972 Jun - 3:00 - AST + 4:00 - +04 1972 Jun + 3:00 - +03 # India # @@ -431,7 +431,7 @@ Zone Asia/Bahrain 3:22:20 - LMT 1920 # Manamah # counties Deqing, Enping, Kaiping, Luoding, Taishan, Xinxing, # Yangchun, Yangjiang, Yu'nan, and Yunfu. Zone Asia/Chongqing 7:06:20 - LMT 1928 # or Chungking - 7:00 - LONT 1980 May # Long-shu Time + 7:00 - +07 1980 May 8:00 PRC C%sT Link Asia/Chongqing Asia/Chungking @@ -442,43 +442,43 @@ Link Asia/Chongqing Asia/Chungking # October 1954, with exact date and time unspecified. Zone Asia/Hanoi 7:03:24 - LMT 1906 Jul 1 7:06:30 - PLMT 1911 May 1 - 7:00 - ICT 1942 Dec 31 23:00 - 8:00 - IDT 1945 Mar 14 23:00 - 9:00 - JST 1945 Sep 2 - 7:00 - ICT 1947 Apr 1 - 8:00 - IDT 1954 Oct - 7:00 - ICT + 7:00 - +07 1942 Dec 31 23:00 + 8:00 - +08 1945 Mar 14 23:00 + 9:00 - +09 1945 Sep 2 + 7:00 - +07 1947 Apr 1 + 8:00 - +08 1954 Oct + 7:00 - +07 # China # Changbai Time ("Long-white Time", Long-white = Heilongjiang area) # Heilongjiang (except Mohe county), Jilin Zone Asia/Harbin 8:26:44 - LMT 1928 # or Haerbin - 8:30 - CHAT 1932 Mar # Changbai Time + 8:30 - +0830 1932 Mar 8:00 - CST 1940 - 9:00 - CHAT 1966 May - 8:30 - CHAT 1980 May + 9:00 - +09 1966 May + 8:30 - +0830 1980 May 8:00 PRC C%sT # far west China Zone Asia/Kashgar 5:03:56 - LMT 1928 # or Kashi or Kaxgar - 5:30 - KAST 1940 # Kashgar Time - 5:00 - KAST 1980 May + 5:30 - +0530 1940 + 5:00 - +05 1980 May 8:00 PRC C%sT # Kuwait Zone Asia/Kuwait 3:11:56 - LMT 1950 - 3:00 - AST + 3:00 - +03 # Oman # Milne says 3:54:24 was the meridian of the Muscat Tidal Observatory. Zone Asia/Muscat 3:54:24 - LMT 1920 - 4:00 - GST + 4:00 - +04 # India # From Paul Eggert (2014-08-11), after a heads-up from Stephen Colebourne: # According to a Portuguese decree (1911-05-26) -# http://dre.pt/pdf1sdip/1911/05/12500/23132313.pdf +# https://dre.pt/pdf1sdip/1911/05/12500/23132313.pdf # Portuguese India switched to UT +05 on 1912-01-01. #Zone Asia/Panaji [not enough info to complete] @@ -491,12 +491,12 @@ Zone Asia/Muscat 3:54:24 - LMT 1920 # transitions there. Zone Asia/Phnom_Penh 6:59:40 - LMT 1906 Jul 1 7:06:30 - PLMT 1911 May 1 - 7:00 - ICT 1942 Dec 31 23:00 - 8:00 - IDT 1945 Mar 14 23:00 - 9:00 - JST 1945 Sep 2 - 7:00 - ICT 1947 Apr 1 - 8:00 - IDT 1953 Nov 9 - 7:00 - ICT + 7:00 - +07 1942 Dec 31 23:00 + 8:00 - +08 1945 Mar 14 23:00 + 9:00 - +09 1945 Sep 2 + 7:00 - +07 1947 Apr 1 + 8:00 - +08 1953 Nov 9 + 7:00 - +07 # Israel Zone Asia/Tel_Aviv 2:19:04 - LMT 1880 @@ -511,16 +511,16 @@ Zone Asia/Tel_Aviv 2:19:04 - LMT 1880 # this is probably wrong but it's better than guessing no transition. Zone Asia/Vientiane 6:50:24 - LMT 1906 Jul 1 7:06:30 - PLMT 1911 May 1 - 7:00 - ICT 1942 Dec 31 23:00 - 8:00 - IDT 1945 Mar 14 23:00 - 9:00 - JST 1945 Sep 2 - 7:00 - ICT 1947 Apr 1 - 8:00 - IDT 1955 Apr 15 - 7:00 - ICT + 7:00 - +07 1942 Dec 31 23:00 + 8:00 - +08 1945 Mar 14 23:00 + 9:00 - +09 1945 Sep 2 + 7:00 - +07 1947 Apr 1 + 8:00 - +08 1955 Apr 15 + 7:00 - +07 # Jan Mayen # From Whitman: -Zone Atlantic/Jan_Mayen -1:00 - EGT +Zone Atlantic/Jan_Mayen -1:00 - -01 # St Helena Zone Atlantic/St_Helena -0:22:48 - LMT 1890 # Jamestown @@ -663,15 +663,13 @@ Zone Pacific/Johnston -10:00 - HST # " 3:00P Ar. MIDWAY ISLAND . . . . . . . . . M.L.T. Lv. 6:00A " # Zone Pacific/Midway -11:49:28 - LMT 1901 - -11:00 - NST 1956 Jun 3 - -11:00 1:00 NDT 1956 Sep 2 - -11:00 - NST 1967 Apr # N=Nome - -11:00 - BST 1983 Nov 30 # B=Bering - -11:00 - SST # S=Samoa + -11:00 - -11 1956 Jun 3 + -11:00 1:00 -10 1956 Sep 2 + -11:00 - -11 # N Mariana Is Zone Pacific/Saipan -14:17:00 - LMT 1844 Dec 31 9:43:00 - LMT 1901 - 9:00 - MPT 1969 Oct # N Mariana Is Time - 10:00 - MPT 2000 Dec 23 + 9:00 - +09 1969 Oct + 10:00 - +10 2000 Dec 23 10:00 - ChST # Chamorro Standard Time -- 2.9.3

1 6

ID string in zic's output files
by Arthur David Olson Feb. 22, 2017

Feb. 22, 2017

So much for the idea of storing ID strings in zic output files as (unused) abbreviations. The zone America/Pangnirtung needs 41 bytes to store all the abbreviations it uses: -00 AWT APT AST ADDT ADT EDT EST CST CDT A zic output file can have at most 50 bytes of abbreviations, as set by TZ_MAX_CHARS in tzfile.h The 9 bytes remaining isn't enough for our purposes. (We don't want to boost TZ_MAX_CHARS; localtime.c checks files to ensure they have at most that many abbreviation characters; files with more would be rejected, at least by now-in-the-field binaries compiled from localtime.c) Note that the last component of "Zone" names (such as the "Vevay" in "America/Indiana/Vevay") would fit in the 15 "reserved for future use" bytes at the front of zic output files; full names would not (always) fit, and there would not (always) be room for a prefix such as "@(#)." @dashdashado

2 1

Spaniards’ lack of sleep isn’t a cultural thing – they’re in the wrong time zone
by BASTIAN Michelle Feb. 22, 2017

Feb. 22, 2017

Interesting article in the Guardian on proposed time zone changes in Spain. https://www.theguardian.com/commentisfree/2017/feb/22/spaniards-sleep-time-… --- Dr Michelle Bastian Chancellor’s Fellow, Edinburgh School of Architecture and Landscape Architecture Edinburgh College of Art, University of Edinburgh Level 1, Room 303B The Maltings 20-22 Chambers Street, Edinburgh, EH1 1JZ Phone: +44 (0)131 651 5779 Email: michelle.bastian(a)ed.ac.uk Website: www.michellebastian.net -- The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336.

1 0

[PROPOSED] Mongolia no longer observes DST
by Paul Eggert Feb. 16, 2017

Feb. 16, 2017

* NEWS: Mention this. * asia (Mongolia): DST expires after 2016. --- NEWS | 2 ++ asia | 8 ++++++-- 2 files changed, 8 insertions(+), 2 deletions(-) diff --git a/NEWS b/NEWS index 10c2cd4..3179d57 100644 --- a/NEWS +++ b/NEWS @@ -6,6 +6,8 @@ Unreleased, experimental changes Changes to future time stamps + Mongolia no longer observes DST. (Thanks to Ganbold Tsagaankhuu.) + Chile's Region of Magallanes moves from -04/-03 to -03 year-round. Its clocks diverge from America/Santiago starting 2017-05-13 at 23:00, hiving off a new zone America/Punta_Arenas. Although the diff --git a/asia b/asia index 26b6a5b..35774c6 100644 --- a/asia +++ b/asia @@ -2137,14 +2137,18 @@ Rule Mongol 1983 only - Oct 1 0:00 0 - # correction of 02:00 (in the previous edition) not being done correctly # in the latest edition; so ignore it for now. +# From Ganbold Tsagaankhuu (2017-02-09): +# Mongolian Government meeting has concluded today to cancel daylight +# saving time adoption in Mongolia. Source: http://zasag.mn/news/view/16192 + Rule Mongol 1985 1998 - Mar lastSun 0:00 1:00 S Rule Mongol 1984 1998 - Sep lastSun 0:00 0 - # IATA SSIM (1999-09) says Mongolia no longer observes DST. Rule Mongol 2001 only - Apr lastSat 2:00 1:00 S Rule Mongol 2001 2006 - Sep lastSat 2:00 0 - Rule Mongol 2002 2006 - Mar lastSat 2:00 1:00 S -Rule Mongol 2015 max - Mar lastSat 2:00 1:00 S -Rule Mongol 2015 max - Sep lastSat 0:00 0 - +Rule Mongol 2015 2016 - Mar lastSat 2:00 1:00 S +Rule Mongol 2015 2016 - Sep lastSat 0:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] # Hovd, a.k.a. Chovd, Dund-Us, Dzhargalant, Khovd, Jirgalanta -- 2.9.3

4 9

New NIST leap-seconds.list
by Tony Finch Feb. 16, 2017

Feb. 16, 2017

The file at ftp://time.nist.gov/pub/leap-seconds.list has been updated to reflect Bulletin C53 and now has an expiry date of 28 December 2017. Tony. -- f.anthony.n.finch <dot(a)dotat.at> http://dotat.at/ - I xn--zr8h punycode Fair Isle: Cyclonic becoming northwest 5 or 6, then variable 4 later. Moderate, occasionally slight. Showers until later. Moderate or good.

3 2

Bad Map Projection #79
by Guy Harris Feb. 15, 2017

Feb. 15, 2017

https://xkcd.com/1799/ "Where each country *should* be, based on its time zone(s)"

3 2

[PROPOSED 1/3] Remove many invented abbreviations in 'australasia'
by Paul Eggert Feb. 14, 2017

Feb. 14, 2017

* NEWS: Document this. * australasia (Australia/Eucla, Australia/Lord_Howe) (Antarctica/Macquarie, Indian/Christmas, Indian/Cocos, Pacific/Fiji) (Pacific/Gambier, Pacific/Marquesas, Pacific/Tahiti, Pacific/Tarawa) (Pacific/Enderbury, Pacific/Kiritimati, Pacific/Majuro) (Pacific/Kwajalein, Pacific/Chuuk, Pacific/Pohnpei, Pacific/Kosrae) (Pacific/Nauru, Pacific/Noumea, Pacific/Chatham, Pacific/Rarotonga) (Pacific/Niue, Pacific/Norfolk, Pacific/Palau, Pacific/Port_Moresby) (Pacific/Bougainville, Pacific/Pitcairn, Pacific/Pago_Pago) (Pacific/Apia, Pacific/Guadalcanal, Pacific/Fakaofo, Pacific/Funafuti): (Pacific/Wake, Pacific/Efate, Pacific/Wallis): Use numeric time zone abbreviations instead of invented ones, for time zones with UT offsets that are integer minutes. --- NEWS | 15 ++++-- australasia | 148 ++++++++++++++++++++++++++++-------------------------------- 2 files changed, 79 insertions(+), 84 deletions(-) diff --git a/NEWS b/NEWS index 3179d57..23bcd8f 100644 --- a/NEWS +++ b/NEWS @@ -37,11 +37,16 @@ Unreleased, experimental changes part of the ongoing project of removing invented abbreviations. This avoids the need to invent an abbreviation for the new Chilean new zone. Similarly, switch from invented to numeric time zone - abbreviations for Afghanistan, the Azores, Bangladesh, Bhutan, the - British Indian Ocean Territory, Brunei, Dubai, East Timor, - Greenland, Indochina, Iran, Iraq, Malaysia, the Maldives, - Mongolia, Myanmar, Nepal, the Philippines, Qatar, St Pierre and - Miquelon, Saudi Arabia, Singapore, and Xinjiang; for half-hour DST + abbreviations for Afghanistan, American Samoa, the Azores, + Bangladesh, Bhutan, the British Indian Ocean Territory, Brunei, + Chatham Is, Christmas I, Cocos (Keeling) Is, Cook Is, Dubai, East + Timor, Eucla, Fiji, French Polynesia, Greenland, Indochina, Iran, + Iraq, Kiribati, Lord Howe, Macquarie, Malaysia, the Maldives, + Marshall Is, Micronesia, Mongolia, Myanmar, Nauru, Nepal, New + Caledonia, Niue, Norfolk I, Palau, Papua New Guinea, the + Philippines, Pitcairn, Qatar, St Pierre & Miquelon, Samoa, Saudi + Arabia, Singapore, Solomon Is, Tokelau, Tuvalu, Wake, Vanuatu, + Wallis & Futuna, and Xinjiang; for half-hour daylight saving time in Belize before 1944 and in the Dominican Republic before 1975; and for Canary Islands before 1946, for Madeira before 1967, for Iceland before 1969, for Indian Summer Time before 1942, for diff --git a/australasia b/australasia index 0bca53e..1280022 100644 --- a/australasia +++ b/australasia @@ -44,8 +44,8 @@ Zone Australia/Perth 7:43:24 - LMT 1895 Dec 8:00 Aus AW%sT 1943 Jul 8:00 AW AW%sT Zone Australia/Eucla 8:35:28 - LMT 1895 Dec - 8:45 Aus ACW%sT 1943 Jul - 8:45 AW ACW%sT + 8:45 Aus +0845/+0945 1943 Jul + 8:45 AW +0845/+0945 # Queensland # @@ -212,7 +212,8 @@ Rule LH 2008 max - Apr Sun>=1 2:00 0 S Rule LH 2008 max - Oct Sun>=1 2:00 0:30 D Zone Australia/Lord_Howe 10:36:20 - LMT 1895 Feb 10:00 - AEST 1981 Mar - 10:30 LH LH%sT + 10:30 LH +1030/+1130 1985 Jul + 10:30 LH +1030/+11 # Australian miscellany # @@ -250,19 +251,19 @@ Zone Antarctica/Macquarie 0 - -00 1899 Nov 0 - -00 1948 Mar 25 10:00 Aus AE%sT 1967 10:00 AT AE%sT 2010 Apr 4 3:00 - 11:00 - MIST # Macquarie I Standard Time + 11:00 - +11 # Christmas # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Indian/Christmas 7:02:52 - LMT 1895 Feb - 7:00 - CXT # Christmas Island Time + 7:00 - +07 # Cocos (Keeling) Is # These islands were ruled by the Ross family from about 1830 to 1978. # We don't know when standard time was introduced; for now, we guess 1900. # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Indian/Cocos 6:27:40 - LMT 1900 - 6:30 - CCT # Cocos Islands Time + 6:30 - +0630 # Fiji @@ -375,16 +376,16 @@ Rule Fiji 2014 max - Nov Sun>=1 2:00 1:00 S Rule Fiji 2015 max - Jan Sun>=15 3:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Pacific/Fiji 11:55:44 - LMT 1915 Oct 26 # Suva - 12:00 Fiji FJ%sT # Fiji Time + 12:00 Fiji +12/+13 # French Polynesia # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Pacific/Gambier -8:59:48 - LMT 1912 Oct # Rikitea - -9:00 - GAMT # Gambier Time + -9:00 - -09 Zone Pacific/Marquesas -9:18:00 - LMT 1912 Oct - -9:30 - MART # Marquesas Time + -9:30 - -0930 Zone Pacific/Tahiti -9:58:16 - LMT 1912 Oct # Papeete - -10:00 - TAHT # Tahiti Time + -10:00 - -10 # Clipperton (near North America) is administered from French Polynesia; # it is uninhabited. @@ -399,15 +400,15 @@ Link Pacific/Guam Pacific/Saipan # N Mariana Is # Kiribati # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Pacific/Tarawa 11:32:04 - LMT 1901 # Bairiki - 12:00 - GILT # Gilbert Is Time + 12:00 - +12 Zone Pacific/Enderbury -11:24:20 - LMT 1901 - -12:00 - PHOT 1979 Oct # Phoenix Is Time - -11:00 - PHOT 1995 - 13:00 - PHOT + -12:00 - -12 1979 Oct + -11:00 - -11 1995 + 13:00 - +13 Zone Pacific/Kiritimati -10:29:20 - LMT 1901 - -10:40 - LINT 1979 Oct # Line Is Time - -10:00 - LINT 1995 - 14:00 - LINT + -10:40 - -1040 1979 Oct + -10:00 - -10 1995 + 14:00 - +14 # N Mariana Is # See Pacific/Guam. @@ -415,31 +416,31 @@ Zone Pacific/Kiritimati -10:29:20 - LMT 1901 # Marshall Is # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Pacific/Majuro 11:24:48 - LMT 1901 - 11:00 - MHT 1969 Oct # Marshall Islands Time - 12:00 - MHT + 11:00 - +11 1969 Oct + 12:00 - +12 Zone Pacific/Kwajalein 11:09:20 - LMT 1901 - 11:00 - MHT 1969 Oct - -12:00 - KWAT 1993 Aug 20 # Kwajalein Time - 12:00 - MHT + 11:00 - +11 1969 Oct + -12:00 - -12 1993 Aug 20 + 12:00 - +12 # Micronesia # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Pacific/Chuuk 10:07:08 - LMT 1901 - 10:00 - CHUT # Chuuk Time + 10:00 - +10 Zone Pacific/Pohnpei 10:32:52 - LMT 1901 # Kolonia - 11:00 - PONT # Pohnpei Time + 11:00 - +11 Zone Pacific/Kosrae 10:51:56 - LMT 1901 - 11:00 - KOST 1969 Oct # Kosrae Time - 12:00 - KOST 1999 - 11:00 - KOST + 11:00 - +11 1969 Oct + 12:00 - +12 1999 + 11:00 - +11 # Nauru # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Pacific/Nauru 11:07:40 - LMT 1921 Jan 15 # Uaobe - 11:30 - NRT 1942 Mar 15 # Nauru Time - 9:00 - JST 1944 Aug 15 - 11:30 - NRT 1979 May - 12:00 - NRT + 11:30 - +1130 1942 Mar 15 + 9:00 - +09 1944 Aug 15 + 11:30 - +1130 1979 May + 12:00 - +12 # New Caledonia # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S @@ -450,7 +451,7 @@ Rule NC 1996 only - Dec 1 2:00s 1:00 S Rule NC 1997 only - Mar 2 2:00s 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Pacific/Noumea 11:05:48 - LMT 1912 Jan 13 # Nouméa - 11:00 NC NC%sT + 11:00 NC +11/+12 ############################################################################### @@ -491,8 +492,8 @@ Zone Pacific/Auckland 11:39:04 - LMT 1868 Nov 2 11:30 NZ NZ%sT 1946 Jan 1 12:00 NZ NZ%sT Zone Pacific/Chatham 12:13:48 - LMT 1868 Nov 2 - 12:15 - CHAST 1946 Jan 1 - 12:45 Chatham CHA%sT + 12:15 - +1215 1946 Jan 1 + 12:45 Chatham +1245/+1345 Link Pacific/Auckland Antarctica/McMurdo @@ -514,8 +515,8 @@ Rule Cook 1979 1991 - Mar Sun>=1 0:00 0 - Rule Cook 1979 1990 - Oct lastSun 0:00 0:30 HS # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Pacific/Rarotonga -10:39:04 - LMT 1901 # Avarua - -10:30 - CKT 1978 Nov 12 # Cook Is Time - -10:00 Cook CK%sT + -10:30 - -1030 1978 Nov 12 + -10:00 Cook -10/-0930 ############################################################################### @@ -523,29 +524,29 @@ Zone Pacific/Rarotonga -10:39:04 - LMT 1901 # Avarua # Niue # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Pacific/Niue -11:19:40 - LMT 1901 # Alofi - -11:20 - NUT 1951 # Niue Time - -11:30 - NUT 1978 Oct 1 - -11:00 - NUT + -11:20 - -1120 1951 + -11:30 - -1130 1978 Oct 1 + -11:00 - -11 # Norfolk # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Pacific/Norfolk 11:11:52 - LMT 1901 # Kingston - 11:12 - NMT 1951 # Norfolk Mean Time - 11:30 - NFT 1974 Oct 27 02:00 # Norfolk T. - 11:30 1:00 NFST 1975 Mar 2 02:00 - 11:30 - NFT 2015 Oct 4 02:00 - 11:00 - NFT + 11:12 - +1112 1951 + 11:30 - +1130 1974 Oct 27 02:00 + 11:30 1:00 +1230 1975 Mar 2 02:00 + 11:30 - +1130 2015 Oct 4 02:00 + 11:00 - +11 # Palau (Belau) # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Pacific/Palau 8:57:56 - LMT 1901 # Koror - 9:00 - PWT # Palau Time + 9:00 - +09 # Papua New Guinea # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Pacific/Port_Moresby 9:48:40 - LMT 1880 9:48:32 - PMMT 1895 # Port Moresby Mean Time - 10:00 - PGT # Papua New Guinea Time + 10:00 - +10 # # From Paul Eggert (2014-10-13): # Base the Bougainville entry on the Arawa-Kieta region, which appears to have @@ -560,28 +561,26 @@ Zone Pacific/Port_Moresby 9:48:40 - LMT 1880 # and seem to have controlled it until their 1945-08-21 surrender. # # The Autonomous Region of Bougainville switched from UT +10 to +11 -# on 2014-12-28 at 02:00. They call +11 "Bougainville Standard Time"; -# abbreviate this as BST. See: +# on 2014-12-28 at 02:00. They call +11 "Bougainville Standard Time". +# See: # http://www.bougainville24.com/bougainville-issues/bougainville-gets-own-tim… # Zone Pacific/Bougainville 10:22:16 - LMT 1880 9:48:32 - PMMT 1895 - 10:00 - PGT 1942 Jul - 9:00 - JST 1945 Aug 21 - 10:00 - PGT 2014 Dec 28 2:00 - 11:00 - BST + 10:00 - +10 1942 Jul + 9:00 - +09 1945 Aug 21 + 10:00 - +10 2014 Dec 28 2:00 + 11:00 - +11 # Pitcairn # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Pacific/Pitcairn -8:40:20 - LMT 1901 # Adamstown - -8:30 - PNT 1998 Apr 27 0:00 - -8:00 - PST # Pitcairn Standard Time + -8:30 - -0830 1998 Apr 27 0:00 + -8:00 - -08 # American Samoa Zone Pacific/Pago_Pago 12:37:12 - LMT 1879 Jul 5 -11:22:48 - LMT 1911 - -11:00 - NST 1967 Apr # N=Nome - -11:00 - BST 1983 Nov 30 # B=Bering -11:00 - SST # S=Samoa Link Pacific/Pago_Pago Pacific/Midway # in US minor outlying islands @@ -662,17 +661,17 @@ Rule WS 2012 max - Sep lastSun 3:00 1 D # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Pacific/Apia 12:33:04 - LMT 1879 Jul 5 -11:26:56 - LMT 1911 - -11:30 - WSST 1950 - -11:00 WS S%sT 2011 Dec 29 24:00 # S=Samoa - 13:00 WS WS%sT + -11:30 - -1130 1950 + -11:00 WS -11/-10 2011 Dec 29 24:00 + 13:00 WS +13/+14 # Solomon Is # excludes Bougainville, for which see Papua New Guinea # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Pacific/Guadalcanal 10:39:48 - LMT 1912 Oct # Honiara - 11:00 - SBT # Solomon Is Time + 11:00 - +11 -# Tokelau Is +# Tokelau # # From Gwillim Law (2011-12-29) # A correspondent informed me that Tokelau, like Samoa, will be skipping @@ -693,8 +692,8 @@ Zone Pacific/Guadalcanal 10:39:48 - LMT 1912 Oct # Honiara # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Pacific/Fakaofo -11:24:56 - LMT 1901 - -11:00 - TKT 2011 Dec 30 # Tokelau Time - 13:00 - TKT + -11:00 - -11 2011 Dec 30 + 13:00 - +13 # Tonga # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S @@ -713,7 +712,7 @@ Zone Pacific/Tongatapu 12:19:20 - LMT 1901 # Tuvalu # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Pacific/Funafuti 11:56:52 - LMT 1901 - 12:00 - TVT # Tuvalu Time + 12:00 - +12 # US minor outlying islands @@ -775,7 +774,7 @@ Zone Pacific/Funafuti 11:56:52 - LMT 1901 # Wake # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Pacific/Wake 11:06:28 - LMT 1901 - 12:00 - WAKT # Wake Time + 12:00 - +12 # Vanuatu @@ -788,12 +787,12 @@ Rule Vanuatu 1992 1993 - Jan Sun>=23 0:00 0 - Rule Vanuatu 1992 only - Oct Sun>=23 0:00 1:00 S # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Pacific/Efate 11:13:16 - LMT 1912 Jan 13 # Vila - 11:00 Vanuatu VU%sT # Vanuatu Time + 11:00 Vanuatu +11/+12 # Wallis and Futuna # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Pacific/Wallis 12:15:20 - LMT 1901 - 12:00 - WFT # Wallis & Futuna Time + 12:00 - +12 ############################################################################### @@ -804,7 +803,7 @@ Zone Pacific/Wallis 12:15:20 - LMT 1901 # tz(a)iana.org for general use in the future). For more, please see # the file CONTRIBUTING in the tz distribution. -# From Paul Eggert (2014-10-31): +# From Paul Eggert (2017-02-10): # # Unless otherwise specified, the source for data through 1990 is: # Thomas G. Shanks and Rique Pottenger, The International Atlas (6th edition), @@ -829,28 +828,19 @@ Zone Pacific/Wallis 12:15:20 - LMT 1901 # A reliable and entertaining source about time zones is # Derek Howse, Greenwich time and longitude, Philip Wilson Publishers (1997). # -# I invented the abbreviations marked '*' in the following table; -# the rest are from earlier versions of this file, or from other sources. +# The following abbreviations are from other sources. # Corrections are welcome! # std dst # LMT Local Mean Time # 8:00 AWST AWDT Western Australia -# 8:45 ACWST ACWDT Central Western Australia* -# 9:00 JST Japan # 9:30 ACST ACDT Central Australia # 10:00 AEST AEDT Eastern Australia +# 10:00 GST Guam through 2000 # 10:00 ChST Chamorro -# 10:30 LHST LHDT Lord Howe* -# 11:00 BST Bougainville* # 11:30 NZMT NZST New Zealand through 1945 # 12:00 NZST NZDT New Zealand 1946-present -# 12:15 CHAST Chatham through 1945* -# 12:45 CHAST CHADT Chatham 1946-present* -# 13:00 WSST WSDT (western) Samoa 2011-present* -# -11:30 WSST Western Samoa through 1950* # -11:00 SST Samoa # -10:00 HST Hawaii -# - 8:00 PST Pitcairn* # # See the 'northamerica' file for Hawaii. # See the 'southamerica' file for Easter I and the Galápagos Is. -- 2.9.3

3 5

tzid in zoneinfo?
by Steven R. Loomis Feb. 13, 2017

Feb. 13, 2017

Dear TZ list, I would like to propose that zic-compiled binaries (such as what shows up in /etc/zoneinfo) include the tzid (such as ‘America/New_York’). I work on the ICU project (Unicode’s International Components for Unicode) and also CLDR (Unicode’s Common Locale Data Repository). The ICU library consumes tz data, and uses the localized data from CLDR to (among other things) display translated time zone names of various sorts, and format different types of dates. A perpetual problem is trying to detect the actual timezone of a platform. Ideally something like the TZ variable is set to a valid tz id such as America/New_York which we can use directly. Otherwise, we try various approaches - including trying to resolve /etc/localtime’s symlink to see if it points to a file which appears to be in some sort of zic-compiled tree. This brings up bugs such as http://bugs.icu-project.org/trac/ticket/12770 because various platforms use different paths as the targets of /etc/localtime - and some times, it's a doubly linked symlink. In other cases, the file is just copied, and we have to trawl through /usr/share/zoneinfo looking for a binary file which matches. There are other methods employed if these fail, but I think this will suffice for our purposes. Even if ICU consumed the /etc/zoneinfo file directly, or was able to call the host to perform the calculations it needs, that would not suffice in terms of localized content. As I think has been noted on this list before, it does not seem to be a goal of the tz database to collect these translated names, and tz-link.html does link to CLDR as one possible source of translations. I think that this would benefit other users as well, by making zone files self identifiable. I think the JDK has to do similar analysis. Some JavaScript containers (Mozilla especially) now support IANA tz ids, such as in https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Ob… Any thoughts or comments? Thanks, Steven

5 5

Re: [tz] Version in zoneinfo files?
by Guy Harris Feb. 10, 2017

Feb. 10, 2017

On Oct 25, 2015, at 10:55 AM, Paul G <paul(a)ganssle.io> wrote: > I'm not suggesting that it be impossible to create a weird result when asking for the version, just that there's a standard place for the version to go, and preferably the standard default gives you something that you expected. I.e., something that works most of the time is sufficient? So what exactly is the intended use of this version field? > As it is now, you're virtually guaranteed to have a lot of incompatibility because there's nothing you can point to that says, "This is the canonical way to store version information about zoneinfo files", and no standard has emerged on how to do this as is. > > On 10/25/2015 01:51 PM, Guy Harris wrote: >> >> On Oct 25, 2015, at 10:37 AM, Paul G <paul(a)ganssle.io> wrote: >> >>> On 10/25/2015 01:35 PM, Guy Harris wrote: >>> >>>> So where would zic get the version information to put into the binary files? >>> >>> My understanding is that it's the VERSION= line of the Makefile in the tzdata tarballs. >> >> I.e., you're proposing that the value of the VERSION value in the Makefile be passed as an argument to zic, and zic would put the value of that argument into a field in the files? >> >> So, if the goal is to provide a "reliable way to get the version information in a cross-platform way", what would ensure that this field be set properly, for some value of "properly", everywhere that binary tzdata files are generated? >> >> I.e., what is to guarantee that >> >> 1) nobody downstream change VERSION if they aren't changing the zic files from what's distributed >> >> and >> >> 2) people change it "properly" if the files don't correspond to a particular version of files that were distributed (e.g., if some downstream supplier takes 2015q and adds some changes mentioned on the list to it before 2015r comes out with those changes plus other changes, they should call the resulting files something other than "2015q" or "2015r")? >> >

20 55

Re: [tz] Help needed on Tz database
by Bill Seymour Feb. 2, 2017

Feb. 2, 2017

Hi, François, I'm surprised that that old paper is still around. I wrote it mainly for my own benefit when I was trying to understand the tz source files. The way I read the C-EUR rules is that there was a switch to summer time in 1940, but no change back until 1942; so when Minsk changed to C-EUR, the steady state implied by the most recent C-EUR transition would be UTC+1:00; and so the wall clock time in Minsk would be UTC+2:00 and the abbreviation would be CEST. But I'm just an amateur at civil time. I'm including the tz mailing list in this message's recipients in case somebody who really knows will correct me if I'm wrong. 8-) --Bill On Thu, Feb 2, 2017 at 1:25 AM, Francois Rouleau <rouf0007(a)gmail.com> wrote: > Hi > I read "How to read the Tz Database" but there is a case (maybe more later) > that I dont understand. From https://www.timeanddate.com, for Minsk, I see > that: > > "Saturday, June 28, 1941, 12:00:00 midnight clocks were > turned backward 1 hour to Friday, June 27, 1941, 11:00:00 pm local > daylight time instead" > > > > Zone: > ===== > > # Zone NAME GMTOFF RULES FORMAT [UNTIL] > Zone Europe/Minsk 1:50:16 - LMT 1880 > 1:50 - MMT 1924 May 2 # Minsk Mean Time > 2:00 - EET 1930 Jun 21 > 3:00 - MSK 1941 Jun 28 > 1:00 C-Eur CE%sT 1944 Jul 3 > 3:00 Russia MSK/MSD 1990 > 3:00 - MSK 1991 Mar 31 2:00s > 2:00 Russia EE%sT 2011 Mar 27 2:00s > 3:00 - +03 > > Rules: > > RuleName From To Month Day Start Add S/D > Rule C-Eur 1917 1918 - Sep Mon>=15 2:00s 0 - > Rule C-Eur 1940 only - Apr 1 2:00s 1:00 S > Rule C-Eur 1942 only - Nov 2 2:00s 0 - > Rule C-Eur 1943 only - Mar 29 2:00s 1:00 S > Rule C-Eur 1943 only - Oct 4 2:00s 0 - > Rule C-Eur 1944 1945 - Apr Mon>=1 2:00s 1:00 S > Rule C-Eur 1944 only - Oct 2 2:00s 0 - > > > Question: > > On June 28, 1941, the C-Eur rule takes over. What row of the rule section > should I look at? > > Is it the letter column (in rule) that will tell me if this new time is STD > or DST ? > > > Thanks > > François >

3 2

Magallanes region from Chile will keep DST all year round
by Juan Correa Jan. 30, 2017

Jan. 30, 2017

There is no official decree published yet, but it has been reported by official Chilean government Twitter accounts that Magallanes región ( https://en.wikipedia.org/wiki/Magallanes_Region) will keep DST (UTC -3) all year round Sources: - https://twitter.com/presidencia_cl/status/805398903604576256 (from Press Office of the Presidency of Chile, "President Michelle Bachelet signs the decree that establishes a single timezone for Magallanes región") - https://twitter.com/AndresReboll/status/805398964690386944 (from Minister of Energy, "after a participative (sic) process and thoughtful investigation, decided to establish a single timezone (*summer*) for Magallanes) - http://www.soychile.cl/Santiago/Sociedad/2016/12/04/433428/Bachelet-firmo-e… As a reminder, Chile has (since 2016) DST from August to May following year The biggest city in the region is Punta Arenas, with over 123 thousand inhabitants. The whole population for Magallanes region is 164.661 people As soon as the decree gets published, I'll share it here -- Juan Correa Poblete PS Labs (http://www.pslabs.cl)

10 25

[PROPOSED] Remove many invented abbreviations in 'asia'
by Paul Eggert Jan. 20, 2017

Jan. 20, 2017

* NEWS: Document this. List areas changed rather than each individual zone, as there are so many. * asia (Asia/Kabul, Asia/Dhaka, Asia/Thimphu, Indian/Chagos) (Asia/Brunei, Asia/Yangon, Asia/Urumqi, Asia/Taipei, Asia/Dili) (Asia/Kolkata, Asia/Jakarta, Asia/Pontianak, Asia/Makassar) (Asia/Jayapura, Asia/Tehran, Asia/Baghdad, Asia/Kuala_Lumpur) (Asia/Kuching, Indian/Maldives, Asia/Hovd, Asia/Ulaanbaatar) (Asia/Choibalsan, Asia/Kathmandu, Asia/Karachi, Asia/Manila, Asia/Qatar) (Asia/Riyadh, Asia/Singapore, Asia/Bangkok, Asia/Dubai) (Asia/Ho_Chi_Minh): Use numeric rather than invented abbreviations. (Asia/Taipei, Macau, Asia/Macau, Asia/Tokyo, Asia/Seoul, Asia/Pyongyang): Use common (e.g., "JST") rather than invented (e.g., "JCST") abbreviations. (Asia/Colombo): Remove unused abbreviations. --- NEWS | 39 ++++------ asia | 258 +++++++++++++++++++++++++++++++------------------------------------ 2 files changed, 136 insertions(+), 161 deletions(-) diff --git a/NEWS b/NEWS index 79620eb..8276cc7 100644 --- a/NEWS +++ b/NEWS @@ -32,36 +32,27 @@ Unreleased, experimental changes Switch to numeric time zone abbreviations for South America, as part of the ongoing project of removing invented abbreviations. This avoids the need to invent an abbreviation for the new Chilean - new zone. This change affects America/Araguaina, - America/Argentina/Buenos_Aires, America/Argentina/Catamarca, - America/Argentina/Cordoba, America/Argentina/Jujuy, - America/Argentina/La_Rioja, America/Argentina/Mendoza, - America/Argentina/Rio_Gallegos, America/Argentina/Salta, - America/Argentina/San_Juan, America/Argentina/San_Luis, - America/Argentina/Tucuman, America/Argentina/Ushuaia, - America/Asuncion, America/Bahia, America/Belem, America/Boa_Vista, - America/Bogota, America/Campo_Grande, America/Caracas, - America/Cayenne, America/Cuiaba, America/Curacao, - America/Eirunepe, America/Fortaleza, America/Guayaquil, - America/Guyana, America/La_Paz, America/Lima, America/Maceio, - America/Manaus, America/Montevideo, America/Noronha, - America/Paramaribo, America/Porto_Velho, America/Recife, - America/Rio_Branco, America/Santarem, America/Santiago, - America/Sao_Paulo, Antarctica/Palmer, Atlantic/South_Georgia, - Atlantic/Stanley, Pacific/Easter, and Pacific/Galapagos. - - Similarly, switch from invented to numeric time zone abbreviations - for Greenland, the Azores, and St Pierre and Miquelon; for - half-hour DST in Belize before 1944 and in the Dominican Republic - before 1975; and for Canary Islands before 1946, for Madeira - before 1967, for Iceland before 1969, for the Netherlands in - 1937-9, and for Zaporozhye in 1880-1924. + new zone. Similarly, switch from invented to numeric time zone + abbreviations for Afghanistan, the Azores, Bangladesh, Bhutan, the + British Indian Ocean Territory, Brunei, Dubai, East Timor, + Greenland, Indochina, Iran, Iraq, Malaysia, the Maldives, + Mongolia, Myanmar, Nepal, the Philippines, Qatar, St Pierre and + Miquelon, Saudi Arabia, Singapore, and Xinjiang; for half-hour DST + in Belize before 1944 and in the Dominican Republic before 1975; + and for Canary Islands before 1946, for Madeira before 1967, for + Iceland before 1969, for Indian Summer Time before 1942, for + Indonesia before around 1964, for the Netherlands in 1937-9, for + Pakistan before 1971, and for Zaporozhye in 1880-1924. For Alaska time from 1900 through 1967, instead of "CAT" use the abbreviation "AST", the abbreviation commonly used at the time (Atlantic Standard Time had not been standardized yet). Use "AWT" and "APT" instead of the invented abbreviations "CAWT" and "CAPT". + Use "CST" and "CDT" instead of invented abbreviations for Macau + before 1999 and Taiwan before 1938, and use "JST" instead of the + invented abbreviation "JCST" for Japan and Korea before 1938. + Changes to code zic no longer mishandles some transitions in January 2038 when it diff --git a/asia b/asia index 6129614..26b6a5b 100644 --- a/asia +++ b/asia @@ -6,15 +6,15 @@ # tz(a)iana.org for general use in the future). For more, please see # the file CONTRIBUTING in the tz distribution. -# From Paul Eggert (2015-08-08): +# From Paul Eggert (2017-01-13): # # Unless otherwise specified, the source for data through 1990 is: # Thomas G. Shanks and Rique Pottenger, The International Atlas (6th edition), # San Diego: ACS Publications, Inc. (2003). # Unfortunately this book contains many errors and cites no sources. # -# Gwillim Law writes that a good source -# for recent time zone data is the International Air Transport +# Many years ago Gwillim Law wrote that a good source +# for time zone data was the International Air Transport # Association's Standard Schedules Information Manual (IATA SSIM), # published semiannually. Law sent in several helpful summaries # of the IATA's data after 1990. Except where otherwise noted, @@ -35,29 +35,24 @@ # A reliable and entertaining source about time zones is # Derek Howse, Greenwich time and longitude, Philip Wilson Publishers (1997). # -# I invented the abbreviations marked '*' in the following table; -# the rest are from earlier versions of this file, or from other sources. -# Corrections are welcome! +# The following alphabetic abbreviations appear in these tables: # std dst # LMT Local Mean Time # 2:00 EET EEST Eastern European Time # 2:00 IST IDT Israel -# 3:00 AST ADT Arabia* -# 3:30 IRST IRDT Iran* -# 4:00 GST Gulf* # 5:30 IST India -# 7:00 ICT Indochina, most times and locations* # 7:00 WIB west Indonesia (Waktu Indonesia Barat) # 8:00 WITA central Indonesia (Waktu Indonesia Tengah) # 8:00 CST China -# 8:00 IDT Indochina, 1943-45, 1947-55, 1960-75 (some locations)* -# 8:00 JWST Western Standard Time (Japan, 1896/1937)* -# 8:30 KST KDT Korea when at +0830* -# 9:00 JCST Central Standard Time (Japan, 1896/1937) +# 8:30 KST KDT Korea when at +0830 # 9:00 WIT east Indonesia (Waktu Indonesia Timur) # 9:00 JST JDT Japan # 9:00 KST KDT Korea when at +09 # 9:30 ACST Australian Central Standard Time +# Otherwise, these tables typically use numeric abbreviations like +03 +# and +0330 for integer hour and minute UTC offsets. Although earlier +# editions invented alphabetic time zone abbreviations for every +# offset, this did not reflect common practice. # # See the 'europe' file for Russia and Turkey in Asia. @@ -65,7 +60,7 @@ # Incorporates data for Singapore from Robert Elz' asia 1.1, as well as # additional information from Tom Yap, Sun Microsystems Intercontinental # Technical Support (including a page from the Official Airline Guide - -# Worldwide Edition). The names for time zones are guesses. +# Worldwide Edition). ############################################################################### @@ -86,8 +81,8 @@ Rule RussiaAsia 1996 2011 - Oct lastSun 2:00s 0 - # Afghanistan # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Kabul 4:36:48 - LMT 1890 - 4:00 - AFT 1945 - 4:30 - AFT + 4:00 - +04 1945 + 4:30 - +0430 # Armenia # From Paul Eggert (2006-03-22): @@ -230,18 +225,17 @@ Rule Dhaka 2009 only - Dec 31 24:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Dhaka 6:01:40 - LMT 1890 5:53:20 - HMT 1941 Oct # Howrah Mean Time? - 6:30 - BURT 1942 May 15 # Burma Time - 5:30 - IST 1942 Sep - 6:30 - BURT 1951 Sep 30 - 6:00 - DACT 1971 Mar 26 # Dacca Time - 6:00 - BDT 2009 - 6:00 Dhaka BD%sT + 6:30 - +0630 1942 May 15 + 5:30 - +0530 1942 Sep + 6:30 - +0630 1951 Sep 30 + 6:00 - +06 2009 + 6:00 Dhaka +06/+07 # Bhutan # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Thimphu 5:58:36 - LMT 1947 Aug 15 # or Thimbu - 5:30 - IST 1987 Oct - 6:00 - BTT # Bhutan Time + 5:30 - +0530 1987 Oct + 6:00 - +06 # British Indian Ocean Territory # Whitman and the 1995 CIA time zone map say 5:00, but the @@ -251,14 +245,14 @@ Zone Asia/Thimphu 5:58:36 - LMT 1947 Aug 15 # or Thimbu # then contained the Chagos Archipelago). # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Indian/Chagos 4:49:40 - LMT 1907 - 5:00 - IOT 1996 # BIOT Time - 6:00 - IOT + 5:00 - +05 1996 + 6:00 - +06 # Brunei # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Brunei 7:39:40 - LMT 1926 Mar # Bandar Seri Begawan - 7:30 - BNT 1933 - 8:00 - BNT + 7:30 - +0730 1933 + 8:00 - +08 # Burma / Myanmar @@ -267,9 +261,9 @@ Zone Asia/Brunei 7:39:40 - LMT 1926 Mar # Bandar Seri Begawan # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Yangon 6:24:40 - LMT 1880 # or Rangoon 6:24:40 - RMT 1920 # Rangoon Mean Time? - 6:30 - BURT 1942 May # Burma Time - 9:00 - JST 1945 May 3 - 6:30 - MMT # Myanmar Time + 6:30 - +0630 1942 May + 9:00 - +09 1945 May 3 + 6:30 - +0630 # Cambodia # See Asia/Bangkok. @@ -521,7 +515,7 @@ Zone Asia/Shanghai 8:05:43 - LMT 1901 # Xinjiang time, used by many in western China; represented by Ürümqi / Ürümchi # / Wulumuqi. (Please use Asia/Shanghai if you prefer Beijing time.) Zone Asia/Urumqi 5:50:20 - LMT 1928 - 6:00 - XJT + 6:00 - +06 # Hong Kong (Xianggang) @@ -740,30 +734,29 @@ Rule Taiwan 1979 only - Oct 1 0:00 0 S # Zone NAME GMTOFF RULES FORMAT [UNTIL] # Taipei or Taibei or T'ai-pei Zone Asia/Taipei 8:06:00 - LMT 1896 Jan 1 - 8:00 - JWST 1937 Oct 1 + 8:00 - CST 1937 Oct 1 9:00 - JST 1945 Sep 21 1:00 8:00 Taiwan C%sT # Macau (Macao, Aomen) # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S -Rule Macau 1961 1962 - Mar Sun>=16 3:30 1:00 S -Rule Macau 1961 1964 - Nov Sun>=1 3:30 0 - -Rule Macau 1963 only - Mar Sun>=16 0:00 1:00 S -Rule Macau 1964 only - Mar Sun>=16 3:30 1:00 S -Rule Macau 1965 only - Mar Sun>=16 0:00 1:00 S -Rule Macau 1965 only - Oct 31 0:00 0 - -Rule Macau 1966 1971 - Apr Sun>=16 3:30 1:00 S -Rule Macau 1966 1971 - Oct Sun>=16 3:30 0 - -Rule Macau 1972 1974 - Apr Sun>=15 0:00 1:00 S -Rule Macau 1972 1973 - Oct Sun>=15 0:00 0 - -Rule Macau 1974 1977 - Oct Sun>=15 3:30 0 - -Rule Macau 1975 1977 - Apr Sun>=15 3:30 1:00 S -Rule Macau 1978 1980 - Apr Sun>=15 0:00 1:00 S -Rule Macau 1978 1980 - Oct Sun>=15 0:00 0 - +Rule Macau 1961 1962 - Mar Sun>=16 3:30 1:00 D +Rule Macau 1961 1964 - Nov Sun>=1 3:30 0 S +Rule Macau 1963 only - Mar Sun>=16 0:00 1:00 D +Rule Macau 1964 only - Mar Sun>=16 3:30 1:00 D +Rule Macau 1965 only - Mar Sun>=16 0:00 1:00 D +Rule Macau 1965 only - Oct 31 0:00 0 S +Rule Macau 1966 1971 - Apr Sun>=16 3:30 1:00 D +Rule Macau 1966 1971 - Oct Sun>=16 3:30 0 S +Rule Macau 1972 1974 - Apr Sun>=15 0:00 1:00 D +Rule Macau 1972 1973 - Oct Sun>=15 0:00 0 S +Rule Macau 1974 1977 - Oct Sun>=15 3:30 0 S +Rule Macau 1975 1977 - Apr Sun>=15 3:30 1:00 D +Rule Macau 1978 1980 - Apr Sun>=15 0:00 1:00 D +Rule Macau 1978 1980 - Oct Sun>=15 0:00 0 S # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Macau 7:34:20 - LMT 1912 Jan 1 - 8:00 Macau MO%sT 1999 Dec 20 # return to China - 8:00 PRC C%sT + 8:00 Macau C%sT ############################################################################### @@ -879,11 +872,10 @@ Zone Asia/Tbilisi 2:59:11 - LMT 1880 # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Dili 8:22:20 - LMT 1912 Jan 1 - 8:00 - TLT 1942 Feb 21 23:00 # E Timor Time - 9:00 - JST 1945 Sep 23 - 9:00 - TLT 1976 May 3 - 8:00 - WITA 2000 Sep 17 0:00 - 9:00 - TLT + 8:00 - +08 1942 Feb 21 23:00 + 9:00 - +09 1976 May 3 + 8:00 - +08 2000 Sep 17 0:00 + 9:00 - +09 # India @@ -898,9 +890,9 @@ Zone Asia/Dili 8:22:20 - LMT 1912 Jan 1 # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Kolkata 5:53:28 - LMT 1880 # Kolkata 5:53:20 - HMT 1941 Oct # Howrah Mean Time? - 6:30 - BURT 1942 May 15 # Burma Time + 6:30 - +0630 1942 May 15 5:30 - IST 1942 Sep - 5:30 1:00 IST 1945 Oct 15 + 5:30 1:00 +0630 1945 Oct 15 5:30 - IST # The following are like Asia/Kolkata: # Andaman Is @@ -951,33 +943,33 @@ Zone Asia/Jakarta 7:07:12 - LMT 1867 Aug 10 # Shanks & Pottenger say the next transition was at 1924 Jan 1 0:13, # but this must be a typo. 7:07:12 - BMT 1923 Dec 31 23:47:12 # Batavia - 7:20 - JAVT 1932 Nov # Java Time - 7:30 - WIB 1942 Mar 23 - 9:00 - JST 1945 Sep 23 - 7:30 - WIB 1948 May - 8:00 - WIB 1950 May - 7:30 - WIB 1964 + 7:20 - +0720 1932 Nov + 7:30 - +0730 1942 Mar 23 + 9:00 - +09 1945 Sep 23 + 7:30 - +0730 1948 May + 8:00 - +08 1950 May + 7:30 - +0730 1964 7:00 - WIB # west and central Borneo Zone Asia/Pontianak 7:17:20 - LMT 1908 May 7:17:20 - PMT 1932 Nov # Pontianak MT - 7:30 - WIB 1942 Jan 29 - 9:00 - JST 1945 Sep 23 - 7:30 - WIB 1948 May - 8:00 - WIB 1950 May - 7:30 - WIB 1964 + 7:30 - +0730 1942 Jan 29 + 9:00 - +09 1945 Sep 23 + 7:30 - +0730 1948 May + 8:00 - +08 1950 May + 7:30 - +0730 1964 8:00 - WITA 1988 Jan 1 7:00 - WIB # Sulawesi, Lesser Sundas, east and south Borneo Zone Asia/Makassar 7:57:36 - LMT 1920 7:57:36 - MMT 1932 Nov # Macassar MT - 8:00 - WITA 1942 Feb 9 - 9:00 - JST 1945 Sep 23 + 8:00 - +08 1942 Feb 9 + 9:00 - +09 1945 Sep 23 8:00 - WITA # Maluku Islands, West Papua, Papua Zone Asia/Jayapura 9:22:48 - LMT 1932 Nov - 9:00 - WIT 1944 Sep 1 - 9:30 - ACST 1964 + 9:00 - +09 1944 Sep 1 + 9:30 - +0930 1964 9:00 - WIT # Iran @@ -1009,8 +1001,6 @@ Zone Asia/Jayapura 9:22:48 - LMT 1932 Nov # for at least the last 5 years. Before that, for a few years, the # date used was the first Thursday night of Farvardin and the last # Thursday night of Shahrivar, but I can't give exact dates.... -# I have also changed the abbreviations to what is considered correct -# here in Iran, IRST for regular time and IRDT for daylight saving time. # # From Roozbeh Pournader (2005-04-05): # The text of the Iranian law, in effect since 1925, clearly mentions @@ -1117,9 +1107,9 @@ Rule Iran 2036 max - Sep 21 0:00 0 S # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Tehran 3:25:44 - LMT 1916 3:25:44 - TMT 1946 # Tehran Mean Time - 3:30 - IRST 1977 Nov - 4:00 Iran IR%sT 1979 - 3:30 Iran IR%sT + 3:30 - +0330 1977 Nov + 4:00 Iran +04/+05 1979 + 3:30 Iran +0330/+0430 # Iraq @@ -1162,8 +1152,8 @@ Rule Iraq 1991 2007 - Oct 1 3:00s 0 S # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Baghdad 2:57:40 - LMT 1890 2:57:36 - BMT 1918 # Baghdad Mean Time? - 3:00 - AST 1982 May - 3:00 Iraq A%sT + 3:00 - +03 1982 May + 3:00 Iraq +03/+04 ############################################################################### @@ -1462,8 +1452,6 @@ Rule Japan 1950 1951 - May Sun>=1 2:00 1:00 D # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Tokyo 9:18:59 - LMT 1887 Dec 31 15:00u - 9:00 - JST 1896 Jan 1 - 9:00 - JCST 1937 Oct 1 9:00 Japan J%sT # Since 1938, all Japanese possessions have been like Asia/Tokyo. @@ -1940,14 +1928,12 @@ Rule ROK 1987 1988 - Oct Sun>=8 3:00 0 S # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Seoul 8:27:52 - LMT 1908 Apr 1 8:30 - KST 1912 Jan 1 - 9:00 - JCST 1937 Oct 1 9:00 - JST 1945 Sep 8 9:00 - KST 1954 Mar 21 8:30 ROK K%sT 1961 Aug 10 9:00 ROK K%sT Zone Asia/Pyongyang 8:23:00 - LMT 1908 Apr 1 8:30 - KST 1912 Jan 1 - 9:00 - JCST 1937 Oct 1 9:00 - JST 1945 Aug 24 9:00 - KST 2015 Aug 15 00:00 8:30 - KST @@ -2002,30 +1988,29 @@ Rule NBorneo 1935 1941 - Dec 14 0:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Kuala_Lumpur 6:46:46 - LMT 1901 Jan 1 6:55:25 - SMT 1905 Jun 1 # Singapore M.T. - 7:00 - MALT 1933 Jan 1 # Malaya Time - 7:00 0:20 MALST 1936 Jan 1 - 7:20 - MALT 1941 Sep 1 - 7:30 - MALT 1942 Feb 16 - 9:00 - JST 1945 Sep 12 - 7:30 - MALT 1982 Jan 1 - 8:00 - MYT # Malaysia Time + 7:00 - +07 1933 Jan 1 + 7:00 0:20 +0720 1936 Jan 1 + 7:20 - +0720 1941 Sep 1 + 7:30 - +0730 1942 Feb 16 + 9:00 - +09 1945 Sep 12 + 7:30 - +0730 1982 Jan 1 + 8:00 - +08 # Sabah & Sarawak # From Paul Eggert (2014-08-12): # The data entries here are mostly from Shanks & Pottenger, but the 1942, 1945 # and 1982 transition dates are from Mok Ly Yng. # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Kuching 7:21:20 - LMT 1926 Mar - 7:30 - BORT 1933 # Borneo Time - 8:00 NBorneo BOR%sT 1942 Feb 16 - 9:00 - JST 1945 Sep 12 - 8:00 - BORT 1982 Jan 1 - 8:00 - MYT + 7:30 - +0730 1933 + 8:00 NBorneo +08/+0820 1942 Feb 16 + 9:00 - +09 1945 Sep 12 + 8:00 - +08 # Maldives # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Indian/Maldives 4:54:00 - LMT 1880 # Male 4:54:00 - MMT 1960 # Male Mean Time - 5:00 - MVT # Maldives Time + 5:00 - +05 # Mongolia @@ -2164,25 +2149,25 @@ Rule Mongol 2015 max - Sep lastSat 0:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] # Hovd, a.k.a. Chovd, Dund-Us, Dzhargalant, Khovd, Jirgalanta Zone Asia/Hovd 6:06:36 - LMT 1905 Aug - 6:00 - HOVT 1978 # Hovd Time - 7:00 Mongol HOV%sT + 6:00 - +06 1978 + 7:00 Mongol +07/+08 # Ulaanbaatar, a.k.a. Ulan Bataar, Ulan Bator, Urga Zone Asia/Ulaanbaatar 7:07:32 - LMT 1905 Aug - 7:00 - ULAT 1978 # Ulaanbaatar Time - 8:00 Mongol ULA%sT + 7:00 - +07 1978 + 8:00 Mongol +08/+09 # Choibalsan, a.k.a. Bajan Tümen, Bajan Tumen, Chojbalsan, # Choybalsan, Sanbejse, Tchoibalsan Zone Asia/Choibalsan 7:38:00 - LMT 1905 Aug - 7:00 - ULAT 1978 - 8:00 - ULAT 1983 Apr - 9:00 Mongol CHO%sT 2008 Mar 31 # Choibalsan Time - 8:00 Mongol CHO%sT + 7:00 - +07 1978 + 8:00 - +08 1983 Apr + 9:00 Mongol +09/+10 2008 Mar 31 + 8:00 Mongol +08/+09 # Nepal # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Kathmandu 5:41:16 - LMT 1920 - 5:30 - IST 1986 - 5:45 - NPT # Nepal Time + 5:30 - +0530 1986 + 5:45 - +0545 # Oman # See Asia/Dubai. @@ -2331,10 +2316,10 @@ Rule Pakistan 2009 only - Apr 15 0:00 1:00 S # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Karachi 4:28:12 - LMT 1907 - 5:30 - IST 1942 Sep - 5:30 1:00 IST 1945 Oct 15 - 5:30 - IST 1951 Sep 30 - 5:00 - KART 1971 Mar 26 # Karachi Time + 5:30 - +0530 1942 Sep + 5:30 1:00 +0630 1945 Oct 15 + 5:30 - +0530 1951 Sep 30 + 5:00 - +05 1971 Mar 26 5:00 Pakistan PK%sT # Pakistan Time # Palestine @@ -2699,15 +2684,15 @@ Rule Phil 1978 only - Sep 21 0:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Manila -15:56:00 - LMT 1844 Dec 31 8:04:00 - LMT 1899 May 11 - 8:00 Phil PH%sT 1942 May - 9:00 - JST 1944 Nov - 8:00 Phil PH%sT + 8:00 Phil +08/+09 1942 May + 9:00 - +09 1944 Nov + 8:00 Phil +08/+09 # Qatar # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Qatar 3:26:08 - LMT 1920 # Al Dawhah / Doha - 4:00 - GST 1972 Jun - 3:00 - AST + 4:00 - +04 1972 Jun + 3:00 - +03 Link Asia/Qatar Asia/Bahrain # Saudi Arabia @@ -2734,7 +2719,7 @@ Link Asia/Qatar Asia/Bahrain # # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Riyadh 3:06:52 - LMT 1947 Mar 14 - 3:00 - AST + 3:00 - +03 Link Asia/Riyadh Asia/Aden # Yemen Link Asia/Riyadh Asia/Kuwait @@ -2744,14 +2729,13 @@ Link Asia/Riyadh Asia/Kuwait # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Singapore 6:55:25 - LMT 1901 Jan 1 6:55:25 - SMT 1905 Jun 1 # Singapore M.T. - 7:00 - MALT 1933 Jan 1 # Malaya Time - 7:00 0:20 MALST 1936 Jan 1 - 7:20 - MALT 1941 Sep 1 - 7:30 - MALT 1942 Feb 16 - 9:00 - JST 1945 Sep 12 - 7:30 - MALT 1965 Aug 9 # independence - 7:30 - SGT 1982 Jan 1 # Singapore Time - 8:00 - SGT + 7:00 - +07 1933 Jan 1 + 7:00 0:20 +0720 1936 Jan 1 + 7:20 - +0720 1941 Sep 1 + 7:30 - +0730 1942 Feb 16 + 9:00 - +09 1945 Sep 12 + 7:30 - +0730 1982 Jan 1 + 8:00 - +08 # Spratly Is # no information @@ -2810,8 +2794,8 @@ Zone Asia/Singapore 6:55:25 - LMT 1901 Jan 1 Zone Asia/Colombo 5:19:24 - LMT 1880 5:19:32 - MMT 1906 # Moratuwa Mean Time 5:30 - +0530 1942 Jan 5 - 5:30 0:30 +0530/+06 1942 Sep - 5:30 1:00 +0530/+0630 1945 Oct 16 2:00 + 5:30 0:30 +06 1942 Sep + 5:30 1:00 +0630 1945 Oct 16 2:00 5:30 - +0530 1996 May 25 0:00 6:30 - +0630 1996 Oct 26 0:30 6:00 - +06 2006 Apr 15 0:30 @@ -2993,7 +2977,7 @@ Zone Asia/Dushanbe 4:35:12 - LMT 1924 May 2 # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Bangkok 6:42:04 - LMT 1880 6:42:04 - BMT 1920 Apr # Bangkok Mean Time - 7:00 - ICT + 7:00 - +07 Link Asia/Bangkok Asia/Phnom_Penh # Cambodia Link Asia/Bangkok Asia/Vientiane # Laos @@ -3009,7 +2993,7 @@ Zone Asia/Ashgabat 3:53:32 - LMT 1924 May 2 # or Ashkhabad # United Arab Emirates # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Dubai 3:41:12 - LMT 1920 - 4:00 - GST + 4:00 - +04 Link Asia/Dubai Asia/Muscat # Oman # Uzbekistan @@ -3082,15 +3066,15 @@ Zone Asia/Tashkent 4:37:11 - LMT 1924 May 2 # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Ho_Chi_Minh 7:06:40 - LMT 1906 Jul 1 - 7:06:30 - PLMT 1911 May 1 - 7:00 - ICT 1942 Dec 31 23:00 - 8:00 - IDT 1945 Mar 14 23:00 - 9:00 - JST 1945 Sep 2 - 7:00 - ICT 1947 Apr 1 - 8:00 - IDT 1955 Jul 1 - 7:00 - ICT 1959 Dec 31 23:00 - 8:00 - IDT 1975 Jun 13 - 7:00 - ICT + 7:06:30 - PLMT 1911 May 1 # Phù Liễn MT + 7:00 - +07 1942 Dec 31 23:00 + 8:00 - +08 1945 Mar 14 23:00 + 9:00 - +09 1945 Sep 2 + 7:00 - +07 1947 Apr 1 + 8:00 - +08 1955 Jul 1 + 7:00 - +07 1959 Dec 31 23:00 + 8:00 - +08 1975 Jun 13 + 7:00 - +07 # Yemen # See Asia/Riyadh. -- 2.9.3

5 7

[PROPOSED] date +%z now outputs -0000 for uninhabited
by Paul Eggert Jan. 16, 2017

Jan. 16, 2017

When the time zone has UT offset 0 and the time zone abbreviation begins with "-", the %z spec now expands to -0000 instead of to +0000. This conveys more-useful info, and is what the next version of GNU 'date' is intended to do. * NEWS, newstrftime.3: Document change. * date.1: Document %z. * strftime.c (_fmt): Implement change. --- NEWS | 4 ++++ date.1 | 1 + newstrftime.3 | 12 ++++++++++++ strftime.c | 13 ++++++++++++- 4 files changed, 29 insertions(+), 1 deletion(-) diff --git a/NEWS b/NEWS index 8276cc7..3975295 100644 --- a/NEWS +++ b/NEWS @@ -74,6 +74,10 @@ Unreleased, experimental changes when TZ is set to a POSIX-style string that specifies DST. (Problem reported by Kees Dekker.) + date and strftime now cause %z to generate "-0000" instead of + "+0000" when the UT offset is zero and the time zone abbreviation + begins with "-". + Changes to documentation and commentary tz-link.htm now covers leap smearing, which is popular in clouds. diff --git a/date.1 b/date.1 index 7fd4848..579ab92 100644 --- a/date.1 +++ b/date.1 @@ -90,6 +90,7 @@ to be output in a particular way %X 14:54:40 Time* %y 89 Last two digits of year %Y 1989 Year in full +%z -0500 Numeric time zone %Z EST Time zone abbreviation %+ Wed Mar 8 14:54:40 EST 1989 Default output format* .if t .in -.5i diff --git a/newstrftime.3 b/newstrftime.3 index 9a60ee3..8f1be34 100644 --- a/newstrftime.3 +++ b/newstrftime.3 @@ -50,6 +50,13 @@ strftime \- format date and time .SH DESCRIPTION .ie '\(en'' .ds en \- .el .ds en \(en +.ie '\(lq'' .ds lq \&"\" +.el .ds lq \(lq\" +.ie '\(rq'' .ds rq \&"\" +.el .ds rq \(rq\" +.de q +\\$3\*(lq\\$1\*(rq\\$2 +.. The .I strftime function formats the information from @@ -211,6 +218,11 @@ is replaced by the offset from the Prime Meridian in the format +HHMM or \*-HHMM as appropriate, with positive values representing locations east of Greenwich, or by the empty string if this is not determinable. +The numeric time zone \*-0000 is used when the time is Universal Time +but local time is indeterminate; by convention this is used for +locations while uninhabited, and corresponds to a zero offset when the +time zone abbreviation begins with +.q "\*-" . .TP %% is replaced by a single %. diff --git a/strftime.c b/strftime.c index 984ead5..2bfb6c1 100644 --- a/strftime.c +++ b/strftime.c @@ -500,6 +500,7 @@ label: { long diff; char const * sign; + bool negative; # ifdef TM_GMTOFF diff = t->TM_GMTOFF; @@ -538,7 +539,17 @@ label: continue; # endif # endif - if (diff < 0) { + negative = diff < 0; + if (diff == 0) { +#ifdef TM_ZONE + negative = t->TM_ZONE[0] == '-'; +#else + negative + = (t->tm_isdst < 0 + || tzname[t->tm_isdst != 0][0] == '-'); +#endif + } + if (negative) { sign = "-"; diff = -diff; } else sign = "+"; -- 2.7.4

3 5

Problem with WORK_AROUND_QTBUG_53071
by Bradley White Jan. 8, 2017

Jan. 8, 2017

Happy leap second. In 2016i Pacific/Tongatapu changed to: (1) use numeric time zone abbreviations, and (2) observe DST from the first Sunday in November through the third Sunday in January. That is, its POSIX future rule became "<+13>-13<+14>,M11.1.0,M1.3.0/3". (1) results, under WORK_AROUND_QTBUG_53071, in zic adding a "y2038_boundary - 1" (i.e., 2038-01-19 03:14:07 +00:00) no-op transition to the end of the generated transitions. So, the Pacific/Tongatapu zoneinfo file looks like ... : 2115810000 gmtoff=46800 is_dst=F abbr="+13" 2140606800 gmtoff=50400 is_dst=T abbr="+14" 2147483647 gmtoff=50400 is_dst=T abbr="+14" When loading Pacific/Tongatapu at runtime, (2) results in tzloadbody() generating additional transitions ... : 2140606800 gmtoff=50400 is_dst=T abbr="+14" 2147259600 gmtoff=46800 is_dst=F abbr="+13" 2172661200 gmtoff=50400 is_dst=T abbr="+14" 2178709200 gmtoff=46800 is_dst=F abbr="+13" : When those generated transitions are patched onto the end of the zic transitions, we end up with ... 2115810000 gmtoff=46800 is_dst=F abbr="+13" 2140606800 gmtoff=50400 is_dst=T abbr="+14" 2147483647 gmtoff=50400 is_dst=T abbr="+14" 2172661200 gmtoff=50400 is_dst=T abbr="+14" 2178709200 gmtoff=46800 is_dst=F abbr="+13" This is wrong. The presence of the 2147483647 transition caused us to drop the 2147259600 transition. That is, we lost the shift out of DST at 2038-01-17 02:00:00 +13:00 (2038-01-16 13:00:00 +00:00). One solution would be to trim trailing, no-op transitions from the end of the zic transitions before adding the rule-generated ones. The reference implementation doesn't need them. Bradley

2 7

[PATCH] Update to cite current version of POSIX.1
by Sanjeev Jan. 7, 2017

Jan. 7, 2017

There has been a new Technical Corrigendum issued, and incorporated in the 2016 Edition. Slight reorder of the citation to conform to how Opengroup likes it. --- Theory | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/Theory b/Theory index 22164f4..f2a8dde 100644 --- a/Theory +++ b/Theory @@ -39,10 +39,11 @@ also available. The tz code is upwards compatible with POSIX, an international standard for UNIX-like systems. As of this writing, the current edition of POSIX is: - The Open Group Base Specifications Issue 7 - IEEE Std 1003.1, 2013 Edition - <http://pubs.opengroup.org/onlinepubs/9699919799/> - + IEEE Std 1003.1,2016 Edition + The Open Group Technical Standard Base Specifications, Issue 7 + incorporates IEEE Std 1003.1-2008, + IEEE Std 1003.1-2008/Cor 1-2013, + IEEE Std 1003.1-2008/Cor 2-2016 ----- Names of time zone rules ----- -- 2.10.2

5 4

[PROPOSED] Remove invented North American abbreviations
by Paul Eggert Jan. 5, 2017

Jan. 5, 2017

* NEWS: Document this. * northamerica (America/Anchorage): Use AST/AWT/APT instead of CAT/CAWT/CADT for time stamps before 1968. (Belize, America/Belize, DR, America/Santo_Domingo, America/Miquelon): Use numeric time zone abbreviations instead of invented one. --- NEWS | 11 ++++++++-- northamerica | 71 +++++++++++++++++++++++++++++------------------------------- 2 files changed, 43 insertions(+), 39 deletions(-) diff --git a/NEWS b/NEWS index 5e04e01..780c81c 100644 --- a/NEWS +++ b/NEWS @@ -50,8 +50,15 @@ Unreleased, experimental changes America/Sao_Paulo, Antarctica/Palmer, Atlantic/South_Georgia, Atlantic/Stanley, Pacific/Easter, and Pacific/Galapagos. - Similarly, switch to a numeric time zone abbreviation for Canary - Island time before 1946. + Similarly, switch to numeric time zone abbreviations for St Pierre + and Miquelon time, for half-hour DST in Belize before 1944 and in + the Dominican Republic before 1975, and for Canary Island time + before 1946. + + For Alaska time from 1900 through 1967, instead of "CAT" use the + abbreviation "AST", the abbreviation commonly used at the time + (Atlantic Standard Time had not been standardized yet). Use "AWT" + and "APT" instead of the invented abbreviations "CAWT" and "CAPT". Changes to code diff --git a/northamerica b/northamerica index e1ed9e4..bb0af6c 100644 --- a/northamerica +++ b/northamerica @@ -178,22 +178,6 @@ Zone CST6CDT -6:00 US C%sT Zone MST7MDT -7:00 US M%sT Zone PST8PDT -8:00 US P%sT -# From Bob Devine (1988-01-28): -# ...Alaska (and Hawaii) had the timezone names changed in 1967. -# old new -# Pacific Standard Time(PST) -same- -# Yukon Standard Time(YST) -same- -# Central Alaska S.T. (CAT) Alaska-Hawaii St[an]dard Time (AHST) -# Nome Standard Time (NT) Bering Standard Time (BST) -# -# ...Alaska's timezone lines were redrawn in 1983 to give only 2 tz. -# The YST zone now covers nearly all of the state, AHST just part -# of the Aleutian islands. No DST. - -# From Paul Eggert (1995-12-19): -# The tables below use 'NST', not 'NT', for Nome Standard Time. -# I invented 'CAWT' for Central Alaska War Time. - # From U. S. Naval Observatory (1989-01-19): # USA EASTERN 5 H BEHIND UTC NEW YORK, WASHINGTON # USA EASTERN 4 H BEHIND UTC APR 3 - OCT 30 @@ -250,6 +234,21 @@ Zone PST8PDT -8:00 US P%sT # Samoa standard time # The law doesn't give abbreviations. # +# From Paul Eggert (2016-12-19): +# Here are URLs for the 1918 and 1966 legislation: +# http://uscode.house.gov/statviewer.htm?volume=40&page=451 +# http://uscode.house.gov/statviewer.htm?volume=80&page=108 +# Although the 1918 names were officially "United States Standard +# Eastern Time" and similarly for "Central", "Mountain", "Pacific", +# and "Alaska", in practice "Standard" was placed just before "Time", +# as codified in 1966. In practice, Alaska time was abbreviated "AST" +# before 1968. Summarizing the 1967 name changes: +# 1918 names 1967 names +# -08 Standard Pacific Time (PST) Pacific standard time (PST) +# -09 (unofficial) Yukon (YST) Yukon standard time (YST) +# -10 Standard Alaska Time (AST) Alaska-Hawaii standard time (AHST) +# -11 (unofficial) Nome (NST) Bering standard time (BST) +# # From Paul Eggert (2000-01-08), following a heads-up from Rives McDow: # Public law 106-564 (2000-12-23) introduced ... "Chamorro Standard Time" # for time in Guam and the Northern Marianas. See the file "australasia". @@ -482,7 +481,7 @@ Zone America/Los_Angeles -7:52:58 - LMT 1883 Nov 18 12:07:02 -8:00 US P%sT # Alaska -# AK%sT is the modern abbreviation for -9:00 per USNO. +# AK%sT is the modern abbreviation for -09 per USNO. # # From Paul Eggert (2001-05-30): # Howse writes that Alaska switched from the Julian to the Gregorian calendar, @@ -588,10 +587,8 @@ Zone America/Yakutat 14:41:05 - LMT 1867 Oct 18 -9:00 US AK%sT Zone America/Anchorage 14:00:24 - LMT 1867 Oct 18 -9:59:36 - LMT 1900 Aug 20 12:00 - -10:00 - CAT 1942 - -10:00 US CAT/CAWT 1945 Aug 14 23:00u - -10:00 US CAT/CAPT 1946 # Peace - -10:00 - CAT 1967 Apr + -10:00 - AST 1942 + -10:00 US A%sT 1967 Apr -10:00 - AHST 1969 -10:00 US AH%sT 1983 Oct 30 2:00 -9:00 US Y%sT 1983 Nov 30 @@ -2734,15 +2731,15 @@ Zone America/Barbados -3:58:29 - LMT 1924 # Bridgetown # Belize # Whitman entirely disagrees with Shanks; go with Shanks & Pottenger. # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S -Rule Belize 1918 1942 - Oct Sun>=2 0:00 0:30 HD -Rule Belize 1919 1943 - Feb Sun>=9 0:00 0 S -Rule Belize 1973 only - Dec 5 0:00 1:00 D -Rule Belize 1974 only - Feb 9 0:00 0 S -Rule Belize 1982 only - Dec 18 0:00 1:00 D -Rule Belize 1983 only - Feb 12 0:00 0 S +Rule Belize 1918 1942 - Oct Sun>=2 0:00 0:30 -0530 +Rule Belize 1919 1943 - Feb Sun>=9 0:00 0 CST +Rule Belize 1973 only - Dec 5 0:00 1:00 CDT +Rule Belize 1974 only - Feb 9 0:00 0 CST +Rule Belize 1982 only - Dec 18 0:00 1:00 CDT +Rule Belize 1983 only - Feb 12 0:00 0 CST # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Belize -5:52:48 - LMT 1912 Apr - -6:00 Belize C%sT + -6:00 Belize %s # Bermuda @@ -3014,16 +3011,16 @@ Zone America/Havana -5:29:28 - LMT 1890 # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S -Rule DR 1966 only - Oct 30 0:00 1:00 D -Rule DR 1967 only - Feb 28 0:00 0 S -Rule DR 1969 1973 - Oct lastSun 0:00 0:30 HD -Rule DR 1970 only - Feb 21 0:00 0 S -Rule DR 1971 only - Jan 20 0:00 0 S -Rule DR 1972 1974 - Jan 21 0:00 0 S +Rule DR 1966 only - Oct 30 0:00 1:00 EDT +Rule DR 1967 only - Feb 28 0:00 0 EST +Rule DR 1969 1973 - Oct lastSun 0:00 0:30 -0430 +Rule DR 1970 only - Feb 21 0:00 0 EST +Rule DR 1971 only - Jan 20 0:00 0 EST +Rule DR 1972 1974 - Jan 21 0:00 0 EST # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Santo_Domingo -4:39:36 - LMT 1890 -4:40 - SDMT 1933 Apr 1 12:00 # S. Dom. MT - -5:00 DR E%sT 1974 Oct 27 + -5:00 DR %s 1974 Oct 27 -4:00 - AST 2000 Oct 29 2:00 -5:00 US E%sT 2000 Dec 3 1:00 -4:00 - AST @@ -3313,8 +3310,8 @@ Zone America/Puerto_Rico -4:24:25 - LMT 1899 Mar 28 12:00 # San Juan # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Miquelon -3:44:40 - LMT 1911 May 15 # St Pierre -4:00 - AST 1980 May - -3:00 - PMST 1987 # Pierre & Miquelon Time - -3:00 Canada PM%sT + -3:00 - -03 1987 # Pierre & Miquelon Time + -3:00 Canada -03/-02 # St Vincent and the Grenadines # See America/Port_of_Spain. -- 2.7.4

3 6

question about mktime_tzname()
by Kees Dekker Jan. 5, 2017

Jan. 5, 2017

Hi, I'm running into a potential bug. Please also see the attached C-source file for a reproduction. Reproduction steps: 1. Build tz code, in such way that a libtz.a exists 2. Compile attached source with (e.g. on Linux): gcc -g -o tztestcase2016j tztestcase.c -L <tzlibdir> -ltz 3. Checking the same test case source code with a system library (instead of IANA libtz.a) can be achieved by omitting -L and -l flags in previous command (see #2). It does not make much sense which version of tzcode is used, I tried 2013i and 2016j and both show the same behavior. The mktime() code returns -3600, while I expect 0. Because the TZ zone is explicitly specified, EST5EDT is GMT-5. So the provided time stamp (31-Jan-1969, 19:00) is exactly the same as UTC value 0 (1-Jan-1970, 00:00 GMT). Both Linux and Windows with system libraries return 0 in this specific case (I used these for reference). The remainder of this email is based on the tzcode2016j source code (e.g. for used line numbers). The provided TZ value is parsed in tzparse() and results in sp->ttis[0] set as DST value, and sp->ttis[1] as standard time value. This is at least contrary to in the else part of the if (*name == ',' || *name == ';') block (there DST is saved in sp->ttis[1]). Just grep on init_ttinfo() calls in localtime.c. However, in localsub(), around line 1428, the i becomes sp->defaulttype (which is zero), i.e. points to the DST value of sp->ttis[], which is assigned to ttisp. As result, because t is below sp->ats[0], DST takes into effect, which is incorrect, as everything after the last Sunday in October and before the first Sunday in April (see attachment, TZ="EST5EDT,M4.1.0/02:00,M10.5.0/02:00") is assumed to be standard time. I'm not sure whether I draw the right conclusion, but because the incorrect assumption of using DST, mktime() returns -3600 (on hour off) instead of the expected 0. Is this conclusion correct? I'm not sure how to fix it. When changing the call to init_ttinfo() and effectively swapping DST and standard time (also for symmetry with the else part) in sp-ttis[] (0 to 1 and 1 to 0) + keeping sp->defaulttype = 0 solved this problem, but introduces other conversion errors around DSTchanges (I don't have yet an reproduction, but can make one if needed). The sp->default type is used (in localsub ()) when if (sp->timecnt == 0 || t < sp->ats[0]). The other approach is to assign sp->defaulttype = 1 when the init_ttinfo() calls are not swapped. Anyhow, there is a tight relationship between the value of sp->defaulttype and the order in which DST/standard times are written in sp->ttis[]. If the previous idea is incorrect (and I guess it is), additional code may be needed in time2sub() if yourtm.tm_isdst == -1. In that case, the provided data in yourtm should be checked whether DST is (or is not) into effect. The found mytm struct should match. Otherwise a DST correction is needed (one-hour shift). The current code mistakenly uses DST, and that is why (if I understand all well) mktime() now returns -3600. If I was not able to explain the issue correctly, please let me know. I'm not sure to understand what's going wrong now, but may be, the provided attachment will help in giving better understanding. Because the provided date is near 1970, quite few steps are needed to see what's happing in localtime.c. Regards, Kees Dekker PS. This email has been sent assuming that attachments will not get lost. Otherwise, just copy paste the code below and save to e.g. tztestcase.c. #ifdef _WIN32 #define _CRT_SECURE_NO_WARNINGS #endif #include <time.h> #include <stdio.h> #include <stdlib.h> int main(void) { int ret = 0; const char *months[] = { "Jan", "Feb", "Mar", "April", "May", "June", "July", "Aug", "Sep", "Oct", "Nov", "Dec" }; const char *days[] = { "Sun", "Mon", "Tue", "Wed", "Tur", "Fri", "Sat" }; /* DST switch in April in first Sunday and October, last Sunday */ putenv("TZ=EST5EDT,M4.1.0/02:00,M10.5.0/02:00"); /* January, 1970, invalid input for tm_mday (0 instead 1..31) */ /* non-normalized input for minutes: 1140/60 = 19, so 19:00 EST5EDT time, which is 5 hours before GMT, and should result in t == 0 below */ /* let system figure out whether DST is effect */ struct tm tmp = { 0, 1140, 0, 0, 0, 70, -858993460, -858993460, -1}; printf("enter mktime with: %04d/%s/%02d %02d:%02d:%02d, week day: %d, year day: %d, dst: %d\n", tmp.tm_year + 1900, months[tmp.tm_mon], tmp.tm_mday, tmp.tm_hour, tmp.tm_min, tmp.tm_sec, tmp.tm_wday, tmp.tm_yday, tmp.tm_isdst); time_t t = mktime(&tmp); /* expect: t == 0, DST is off, time is exactly at the boundary of lowest possible UTC value */ printf("the return value of mktime is: %lld\n", (long long)t); printf("normalized times: %04d/%s/%02d %02d:%02d:%02d, week day: %s, year day: %d, dst: %d\n", tmp.tm_year + 1900, months[tmp.tm_mon], tmp.tm_mday, tmp.tm_hour, tmp.tm_min, tmp.tm_sec, days[tmp.tm_wday], tmp.tm_yday, tmp.tm_isdst); if (t >= 0) { printf("tz=%s, %s\n", tzname[0], tzname[1]); } return 0; }

1 0

Definition for timezone Asia/Urumqi and Asia/Kashgar, CST, and other questions about Chinese timezones.
by gfb hjjhjh Jan. 5, 2017

Jan. 5, 2017

1. Currently, Asia/Urumqi and Asia/Kashgar are defined as UTC+6, covering most of Xinjiang and Tibet. However, from brief search result, I cannot see any indication about the UTC+6 usage by ethnic non-han in Xinjiang also exists in Tibet, and Lhasa resident daily activities are apparently only one hours later than those in inner China too. The official announcement about UTC+6 usage in Xinjiang also does not cover Tibet. Thus it seems like those UTC+6 timezones in tz database should not cover Tibet. However, there might be some undocumented official announcement or on the ground usage that I does not notice and require further validation. 2. Actually, which file define the boundary of timezones in tz database? I see they are in comments for China but how about generally? 3. And given Asia/Urumqi is currently defined differently from Asia/Shanghai, and Maoming, Guandong is now using UTC+8, no matter what historical reason might be behind the consideration of putting Maoming, Guangdong in Asia/Urumqi, its current time usage along should have justified putting it in Asia/Shanghai instead 3.a. In http://mm.icann.org/pipermail/tz/2006-July/013704.html , it said Maoming and etc. are in Xinjiang tinezone with data from astro.com but I cannot find anywhere on the site that include historical timezone info and what are their sources? 4. as the name "Central Standard Time" in China was created by ROC, the current main use of this term is for the time in Taiwan and thus it might be unsuitable to use the name for timzone in mainland china area. 5. Why there are 5 different zones in China when the theory file say "if all the clocks in the region have agreed since 1970, don't bother to inclide more than one location even if subregions' clocks disagreed before 1970" ?

5 7

zdump broken with -DUSE_LTZ=0
by Joseph Myers Dec. 21, 2016

Dec. 21, 2016

I tried updating the copy of tzcode in glibc. I found that as of the latest release and current git, zdump doesn't build with -DUSE_LTZ=0, because that configuration disables the inclusion of private.h, which defines the INITIALIZE macro which zdump now uses unconditionally. (There's also a -Wundef issue with the "#if !HAVE_POSIX_DECLS", as that's also only defined in private.h, but that's easy to work around.) -- Joseph S. Myers joseph(a)codesourcery.com

2 1

Minor fixes to commentary
by Tim Parenti Dec. 19, 2016

Dec. 19, 2016

The attached patch fixes a few minor issues left in commentary, and also adds a note about the constructed lines for America/Montevideo which currently work around the non-prevalence of zic which supports %z. -- Tim Parenti

2 1

Proposal: validation text file with releases
by Jon Skeet Dec. 19, 2016

Dec. 19, 2016

Background: I'm the primary developer for Noda Time <http://nodatime.org> which consumes the tz data. I'm currently refactoring the code to do this... and I've come across some code (originally ported from Joda Time) which I now understand in terms of what it's doing, but not exactly why. For a little while now, the Noda Time source repo has included a text dump file <https://github.com/nodatime/nodatime/blob/master/src/NodaTime.Test/TestData…>, containing a text dump of every transition (up to 2100, at the moment) for every time zone. It looks like this, picking just one example: Zone: Africa/Maseru LMT: [StartOfTime, 1892-02-07T22:08:00Z) +01:52 (+00) SAST: [1892-02-07T22:08:00Z, 1903-02-28T22:30:00Z) +01:30 (+00) SAST: [1903-02-28T22:30:00Z, 1942-09-20T00:00:00Z) +02 (+00) SAST: [1942-09-20T00:00:00Z, 1943-03-20T23:00:00Z) +03 (+01) SAST: [1943-03-20T23:00:00Z, 1943-09-19T00:00:00Z) +02 (+00) SAST: [1943-09-19T00:00:00Z, 1944-03-18T23:00:00Z) +03 (+01) SAST: [1944-03-18T23:00:00Z, EndOfTime) +02 (+00) I use this file for confidence when refactoring my time zone handling code - if the new code comes up with the same set of transitions as the old code, it's probably okay. (This is just one line of defence, of course - there are unit tests, though not as many as I'd like.) It strikes me that having a similar file (I'm not wedded to the format, but it should have all the same information, one way or another) released alongside the main data files would be really handy for *all* implementors - it would be a good way of validating consistency across multiple platforms, with the release data being canonical. For any platforms which didn't want to actually consume the rules as rules, but just wanted a list of transitions, it could even effectively replace their use of the data. One other benefit: diffing the dump between two releases would make it clear what had changed in *effect*, rather than just in terms of rules. One sticking point is size. The current file for Noda Time is about 4MB, although it zips down to about 300K. Some thoughts around this: - We wouldn't need to distribute it in the same file as the data - just as we have data and code file, there could be a "textdump" file or whatever we'd want to call it. These could be retroactively generated for previous releases, too. - As you can see, there's redundancy in the format above, in that it's a list of "zone intervals" (as I call them in Noda Time) rather than a list of transitions - the end of each interval is always the start of the next interval. - For zones which settle into an infinite daylight saving pattern, I currently generate from the start of time to 2100 (and then a single zone interval for the end of time as Noda Time understands it; we'd need to work out what form that would take, if any). If we decided that "year of release + 30 years" was enough, that would cut down the size considerably. Any thoughts? If the feeling is broadly positive, the next step would be to nail down the text format, then find a willing victim/volunteer to write the C code. (You really don't want me writing C...) Jon

18 92

[PROPOSED] Pacify ‘make check_character_set’
by Paul Eggert Dec. 19, 2016

Dec. 19, 2016

* tz-art.htm: Convert to ASCII. --- tz-art.htm | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/tz-art.htm b/tz-art.htm index de56b07..296a2d9 100644 --- a/tz-art.htm +++ b/tz-art.htm @@ -376,12 +376,13 @@ line is "Lights go out and I can't be saved".</td></tr> <tr><td> </td></tr> <tr><td>Artist</td><td>Jaime Guevara</td></tr> -<tr><td>Song</td><td><a href="https://www.youtube.com/watch?v=ZfN4Fe_A50U">Qué +<tr><td>Song</td><td><a +href="https://www.youtube.com/watch?v=ZfN4Fe_A50U">Qué hora es</a></td></tr> <tr><td>Date</td><td>1993</td></tr> <tr><td>Total Time</td><td>3:04</td></tr> <tr><td>Notes</td><td>The song protested "Sixto Hour" in Ecuador -(1992–3). Its lyrics include "Amanecía en mitad de la noche, los +(1992–3). Its lyrics include "Amanecía en mitad de la noche, los guaguas iban a clase sin sol" ("It was dawning in the middle of the night, the buses went to class without sun"). <tr><td> </td></tr> -- 2.7.4

1 0

Havranek et al. on DST's effect on energy consumption
by Paul Eggert Dec. 18, 2016

Dec. 18, 2016

A recent meta-analysis of energy savings due to daylight-saving time found a mean effect close to zero (the weighted mean of 0.343% was less than the estimated standard error). The largest energy savings from DST was found in high-latitude countries; areas closer to the equator tended to have negative energy savings. Studies published in journals with high impact factors tended to be more pessimistic about energy-savings benefits. The study concluded, "the effects of daylight saving time on energy consumption are too small to justify the biannual time-shifting." Havranek T, Herman D, Irsova Z. Does daylight saving save energy? a meta-analysis. MPRA Paper No. 74518 (2016-10-12). https://mpra.ub.uni-muenchen.de/74518/1/MPRA_paper_74518.pdf

1 0

Re: [tz] Request to add entry to "Programmatic interfaces that map geographical coordinates"
by Evan Siroky Dec. 17, 2016

Dec. 17, 2016

The package tz-lookup and geo-tz are independent of each other. As far as I know, the major difference between the two is the data source that is used. geo-tz is released under the MIT license. Feel free to link to the timezone tag. Although in my opinion a lot of the packages aren't the best because they don't get updated frequently enough with changes to the timezone db. Evan On Saturday, 10 December 2016, 12:02, Paul Eggert <eggert(a)cs.ucla.edu> wrote: Evan Siroky via tz wrote: > I maintain a node.js library that looks up the timezone name at a GPS coordinate. The project is called geo-tz: https://www.npmjs.com/package/geo-tz My library uses data produced from timezone-boundary-builder. Can you please add an entry to tz-link.html for my project? What's a good way to do that? Currently tz-link.htm says: <li>The <a href="https://www.npmjs.com/package/tz-lookup">tz-lookup module</a> for <a href="https://nodejs.org/en/">Node.js</a> is in the public domain.</li> How should the relationship between tz-lookup and geo-tz be described? Also, what's the license for geo-tz? It is not obvious from its web page. In looking at <https://www.npmjs.com/browse/keyword/timezone> I see several more Node.js time zone packages that seem relevant. Perhaps we should link to that page?

3 6

Spain may change time
by Steve Allen Dec. 15, 2016

Dec. 15, 2016

Lots of news agencies are picking up a possible change of time in Spain. http://www.reuters.com/article/spain-timezone-idUSL5N1E744D -- Steve Allen <sla(a)ucolick.org> WGS-84 (GPS) UCO/Lick Observatory--ISB 260 Natural Sciences II, Room 165 Lat +36.99855 1156 High Street Voice: +1 831 459 3046 Lng -122.06015 Santa Cruz, CA 95064 http://www.ucolick.org/~sla/ Hgt +250 m

11 18

Ecuador DST in 1992/93
by Alois Treindl Dec. 15, 2016

Dec. 15, 2016

A client born in Ecuador wrote to me: "I need a little help with something plus I don't know who else can help me besides Astro! When I was born, the President of Ecuador changed the time zone (one hour ahead) from Nov/28/1992 to Feb/05/1993 because of problems with energy and there were a lot of power cuts across the country. " I checked the tzdata/southamerica file which holds for Ecuador: # Ecuador # # Milne says the Central and South American Telegraph Company used -5:24:15. # # From Paul Eggert (2007-03-04): # Apparently Ecuador had a failed experiment with DST in 1992. # <http://midena.gov.ec/content/view/1261/208/> (2007-02-27) and # <http://www.hoy.com.ec/NoticiaNue.asp?row_id=249856> (2006-11-06) both # talk about "hora Sixto". Leave this alone for now, as we have no data. # # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Guayaquil -5:19:20 - LMT 1890 -5:14:00 - QMT 1931 # Quito Mean Time -5:00 - ECT # Ecuador Time The two links in the comment to not work. I search the web and came up with this link: http://www.elcomercio.com/actualidad/hora-sixto-1993.html which says: Al inicio de su mandato, el Gobierno Nacional, mediante Decreto Presidencial no. 285, obligó que todos los ecuatorianos adelantaran una hora en sus relojes para “ aprovechar la luz solar” y disminuir el consumo de energía. Fue la llamada ‘hora de Sixto’, que se aplicó desde el 28 de noviembre de 1992 hasta el 5 de febrero de 1993. Incluso, los estudiantes de todos los niveles educativos estuvieron obligados a iniciar clases a las 06:00 y terminar antes del mediodía. Google translation: At the beginning of his term, the National Government, through Presidential Decree no. 285, forced all Ecuadorians to advance an hour in their watches to "take advantage of sunlight" and reduce energy consumption. It was the so-called 'Sixtus hour', which was applied from November 28, 1992 until February 5, 1993. Even students of all educational levels were forced to start classes at 06:00 and finish before midday. There should probably be a rule: Rule ECU 1992 only - Nov 28 0:00 1:00 S Rule ECU 1993 only - Feb 5 0:00 0 - and the last lines of the existing entry should refer to this rule. Whether the law applied also to Galapagos, I do not know.

3 4

Washington Post coverage of Spanish time zone
by Arthur David Olson Dec. 15, 2016

Dec. 15, 2016

"Fascism helped create a time zone oddity in Spain. 70 years later, it may finally be undone." https://www.washingtonpost.com/news/worldviews/wp/2016/12/14/fascism-helped… @dashdashado

1 0

Request to add entry to "Programmatic interfaces that map geographical coordinates"
by Evan Siroky Dec. 10, 2016

Dec. 10, 2016

Hello, I maintain a node.js library that looks up the timezone name at a GPS coordinate. The project is called geo-tz: https://www.npmjs.com/package/geo-tz My library uses data produced from timezone-boundary-builder. Can you please add an entry to tz-link.html for my project? Thanks,Evan

2 1

west Qinghai listed in two different time zones
by Jeffrey Oldham Dec. 9, 2016

Dec. 9, 2016

In tzdata2016f.tar.gz / asia, "west Qinghai" is listed under Asia/Chongqing (line 410) and also under Asia/Urumqi (line 418). I believe the former should be east Qinghai. Thanks, Jeffrey D. Oldham oldham(a)google.com

2 2

Earth's day lengthens by two milliseconds a century
by J William Piggott Dec. 9, 2016

Dec. 9, 2016

https://www.theguardian.com/science/2016/dec/07/earths-day-lengthens-by-two… Also an interesting explanation on why Earth's deceleration rate has decreased recently.

6 10

hundreds demonstrate against clock changes in Northern Cyprus
by Paul Eggert Dec. 6, 2016

Dec. 6, 2016

Hundreds of union members and students demonstrated yesterday in northern Cyprus, protesting the decision to remain on +03 all year. This follows a school bus collision Tuesday morning, which killed the driver and two schoolgirls, and which was blamed in part on early-morning darkness. Sources: Turkish Cypriots protest daylight saving time after deadly crash. Agence France Presse 2016-12-01. http://www.naharnet.com/stories/en/221371-turkish-cypriots-protest-daylight… Anastasiou A. Unions call for more strikes in north until clock is changed back. Cyprus Mail 2016-12-02. http://cyprus-mail.com/2016/12/02/unions-call-strikes-north-clock-changed-b…

2 2

[PROPOSED] New zone Asia/Atyrau
by Paul Eggert Dec. 6, 2016

Dec. 6, 2016

(Thanks to Stepan Golosunov.) * NEWS: Document this. * asia, zone.tab, zone1970.tab (Asia/Atyrau): New zone. In comments, prefer what I assume to be Library of Congress romanization for place names in Kazakhstan. * asia (Asia/Aqtau): Omit now-redundant transition. --- NEWS | 6 ++++ asia | 91 +++++++++++++++++++++++++++++++++++------------------------- zone.tab | 3 +- zone1970.tab | 5 ++-- 4 files changed, 64 insertions(+), 41 deletions(-) diff --git a/NEWS b/NEWS index d5f7217..24faeaf 100644 --- a/NEWS +++ b/NEWS @@ -2,6 +2,12 @@ News for the tz database Unreleased, experimental changes + Changes to past time stamps + + The new zone Asia/Atyrau for Atyraū Region, Kazakhstan, is like + Asia/Aqtau except it switched from +04/+05 to +05/+06 in spring + 1999, not fall 1994. (Thanks to Stepan Golosunov.) + Changes to past time zone abbreviations Asia/Gaza and Asia/Hebron now use "EEST", not "EET", to denote diff --git a/asia b/asia index bb7534a..c6f63b5 100644 --- a/asia +++ b/asia @@ -1583,12 +1583,12 @@ Zone Asia/Amman 2:23:44 - LMT 1931 # was "blended" with the Central zone. Therefore, Kazakhstan now has # two time zones, and difference between them is one hour. The zone # closer to UTC is the former Western zone (probably still called the -# same), encompassing four provinces in the west: Aqtobe, Atyrau, -# Mangghystau, and West Kazakhstan. The other zone encompasses +# same), encompassing four provinces in the west: Aqtöbe, Atyraū, +# Mangghystaū, and West Kazakhstan. The other zone encompasses # everything else.... I guess that would make Kazakhstan time zones # de jure UTC+5 and UTC+6 respectively. -# From Stepan Golosunov (2016-03-27) ([*] means see later comments below): +# From Stepan Golosunov (2016-03-27): # Review of the linked documents from http://adilet.zan.kz/ # produced the following data for post-1991 Kazakhstan: # @@ -1634,7 +1634,7 @@ Zone Asia/Amman 2:23:44 - LMT 1931 # # This implies that on 1991-03-31 Asia/Oral remained on +04/+05 while # the rest of Kazakhstan switched from +06/+07 to +05/06 or from +05/06 -# to +04/+05. It's unclear how Kzyl-Orda oblast moved into the fifth +# to +04/+05. It's unclear how Qyzylorda oblast moved into the fifth # time belt. (By switching from +04/+05 to +05/+06 on 1991-09-29?) ... # # 1. Act of the Cabinet of Ministers of the Republic of Kazakhstan @@ -1647,25 +1647,25 @@ Zone Asia/Amman 2:23:44 - LMT 1931 # on the whole territory of Kazakhstan 1 hour forward on 1992-01-19 at # 2:00, specified DST rules. It acknowledged that Kazakhstan was # located in the fourth and the fifth time belts and specified the -# border between them to be located east of Kustanay and Aktyubinsk -# oblasts (notably including Turgai and Kzyl-Orda oblasts into the fifth +# border between them to be located east of Qostanay and Aktyubinsk +# oblasts (notably including Turgai and Qyzylorda oblasts into the fifth # time belt). # # This means switch on 1992-01-19 at 2:00 from +04/+05 to +05/+06 for -# Asia/Aqtau, Asia/Aqtobe, Asia/Oral, Atyrau and Kustanay oblasts; from -# +05/+06 to +06/+07 for Asia/Almaty and Asia/Qyzylorda (and Arkalyk) [*].... +# Asia/Aqtau, Asia/Aqtobe, Asia/Oral, Atyraū and Qostanay oblasts; from +# +05/+06 to +06/+07 for Asia/Almaty and Asia/Qyzylorda (and Arkalyk).... # # 2. Act of the Cabinet of Ministers of the Republic of Kazakhstan # from 1992-03-27 No. 284 # http://adilet.zan.kz/rus/docs/P920000284_ -# cancels extra hour ("decree time") for Uralsk and Kzyl-Orda oblasts +# cancels extra hour ("decree time") for Uralsk and Qyzylorda oblasts # since the last Sunday of March 1992, while keeping them in the fourth # and the fifth time belts respectively. # # 3. Order of the Prime Minister of the Republic of Kazakhstan # from 1994-09-23 No. 384 # http://adilet.zan.kz/rus/docs/R940000384_ -# cancels the extra hour ("decree time") on the territory of Mangystau +# cancels the extra hour ("decree time") on the territory of Mangghystaū # oblast since the last Sunday of September 1994 (saying that time on # the territory would correspond to the third time belt as a # result).... @@ -1679,14 +1679,11 @@ Zone Asia/Amman 2:23:44 - LMT 1931 # 5. Act of the Government of the Republic of Kazakhstan # from 1999-03-26 No. 305 # http://adilet.zan.kz/rus/docs/P990000305_ -# cancels the extra hour ("decree time") for Atyrau oblast since the +# cancels the extra hour ("decree time") for Atyraū oblast since the # last Sunday of March 1999 while retaining the oblast in the fourth # time belt. # -# This means change from +05/+06 to +04/+05. -# -# There is no zone for Atyrau currently (listed under Asia/Aqtau in -# zone1970.tab).[*] +# This means change from +05/+06 to +04/+05.... # # 6. Act of the Government of the Republic of Kazakhstan # from 2000-11-23 No. 1749 @@ -1696,10 +1693,10 @@ Zone Asia/Amman 2:23:44 - LMT 1931 # The only changes I noticed are in definition of the border between the # fourth and the fifth time belts. They account for changes in spelling # and administrative division (splitting of Turgai oblast in 1997 -# probably changed time in territories incorporated into Kostanay oblast -# (including Arkalyk) from +06/+07 to +05/+06) and move Kyzylorda oblast +# probably changed time in territories incorporated into Qostanay oblast +# (including Arkalyk) from +06/+07 to +05/+06) and move Qyzylorda oblast # from being in the fifth time belt and not using decree time into the -# fourth time belt (no change in practice).[*] +# fourth time belt (no change in practice). # # 7. Act of the Government of the Republic of Kazakhstan # from 2003-12-29 No. 1342 @@ -1709,7 +1706,7 @@ Zone Asia/Amman 2:23:44 - LMT 1931 # 8. Act of the Government of the Republic of Kazakhstan # from 2004-07-20 No. 775 # http://adilet.zan.kz/rus/archive/docs/P040000775_/20.07.2004 -# modified the 2000-11-23 act to move Kostanay and Kyzylorda oblasts into +# modified the 2000-11-23 act to move Qostanay and Qyzylorda oblasts into # the fifth time belt and add Aktobe oblast to the list of regions not # using extra hour ("decree time"), leaving Kazakhstan with only 2 time # zones (+04/+05 and +06/+07). The changes were to be implemented @@ -1721,14 +1718,14 @@ Zone Asia/Amman 2:23:44 - LMT 1931 # http://adilet.zan.kz/rus/docs/P040001059_ # modified the 2000-11-23 act to remove exceptions from the "decree time" # (leaving Kazakhstan in +05/+06 and +06/+07 zones), amended the -# 2004-07-20 act to implement changes for Atyrau, West Kazakhstan, -# Kostanay, Kyzylorda and Mangystau oblasts by not moving clocks -# during the 2014 transition to "winter" time. +# 2004-07-20 act to implement changes for Atyraū, West Kazakhstan, +# Qostanay, Qyzylorda and Mangghystaū oblasts by not moving clocks +# during the 2004 transition to "winter" time. # -# This means transition from +04/+05 to +05/+06 for Atyrau oblast (no +# This means transition from +04/+05 to +05/+06 for Atyraū oblast (no # zone currently), Asia/Oral, Asia/Aqtau and transition from +05/+06 to -# +06/+07 for Kostanay oblast (Kostanay and Arkalyk, no zones currently) -# and Asia/Qyzylorda on 2004-10-31 at 3:00....[*] +# +06/+07 for Qostanay oblast (Qostanay and Arkalyk, no zones currently) +# and Asia/Qyzylorda on 2004-10-31 at 3:00.... # # 10. Act of the Government of the Republic of Kazakhstan # from 2005-03-15 No. 231 @@ -1744,14 +1741,9 @@ Zone Asia/Amman 2:23:44 - LMT 1931 # Kazakh 1992-01-13 act appears to provide the same rules and 1992-03-27 # act was to be enacted on the last Sunday of March 1992. -# From Paul Eggert (2016-04-15): -# The tables below should reflect Stepan Golosunov's remarks above, -# except for the items marked "[*]" which I haven't gotten to yet. -# It looks like we will need new zones Asia/Atyrau and Asia/Qostanay -# to handle changes from 1992 through 2004 that we did not previously -# know about. +# From Paul Eggert (2016-11-07): +# The tables below reflect Golosunov's remarks, with exceptions as noted. -# # Zone NAME GMTOFF RULES FORMAT [UNTIL] # # Almaty (formerly Alma-Ata), representing most locations in Kazakhstan @@ -1764,6 +1756,8 @@ Zone Asia/Almaty 5:07:48 - LMT 1924 May 2 # or Alma-Ata 6:00 RussiaAsia +06/+07 2004 Oct 31 2:00s 6:00 - +06 # Qyzylorda (aka Kyzylorda, Kizilorda, Kzyl-Orda, etc.) (KZ-KZY) +# This currently includes Qostanay (aka Kostanay, Kustanay) (KZ-KUS); +# see comments below. Zone Asia/Qyzylorda 4:21:52 - LMT 1924 May 2 4:00 - +04 1930 Jun 21 5:00 - +05 1981 Apr 1 @@ -1775,7 +1769,21 @@ Zone Asia/Qyzylorda 4:21:52 - LMT 1924 May 2 6:00 RussiaAsia +06/+07 1992 Mar 29 2:00s 5:00 RussiaAsia +05/+06 2004 Oct 31 2:00s 6:00 - +06 -# Aqtobe (aka Aktobe, formerly Aktyubinsk) (KZ-AKT) +# The following zone is like Asia/Qyzylorda except for being one +# hour earlier from 1991-09-29 to 1992-03-29. The 1991/2 rules for +# Qostenay are unclear partly because of the 1997 Turgai +# reorganization, so this zone is commented out for now. +#Zone Asia/Qostanay 4:14:20 - LMT 1924 May 2 +# 4:00 - +04 1930 Jun 21 +# 5:00 - +05 1981 Apr 1 +# 5:00 1:00 +06 1981 Oct 1 +# 6:00 - +06 1982 Apr 1 +# 5:00 RussiaAsia +05/+06 1991 Mar 31 2:00s +# 4:00 RussiaAsia +04/+05 1992 Jan 19 2:00s +# 5:00 RussiaAsia +05/+06 2004 Oct 31 2:00s +# 6:00 - +06 +# +# Aqtöbe (aka Aktobe, formerly Aktyubinsk) (KZ-AKT) Zone Asia/Aqtobe 3:48:40 - LMT 1924 May 2 4:00 - +04 1930 Jun 21 5:00 - +05 1981 Apr 1 @@ -1785,14 +1793,11 @@ Zone Asia/Aqtobe 3:48:40 - LMT 1924 May 2 4:00 RussiaAsia +04/+05 1992 Jan 19 2:00s 5:00 RussiaAsia +05/+06 2004 Oct 31 2:00s 5:00 - +05 -# Qostanay (KZ-KUS) - -# Mangghystau (KZ-MAN) +# Mangghystaū (KZ-MAN) # Aqtau was not founded until 1963, but it represents an inhabited region, # so include time stamps before 1963. Zone Asia/Aqtau 3:21:04 - LMT 1924 May 2 4:00 - +04 1930 Jun 21 - 5:00 - +05 1963 5:00 - +05 1981 Oct 1 6:00 - +06 1982 Apr 1 5:00 RussiaAsia +05/+06 1991 Mar 31 2:00s @@ -1800,7 +1805,17 @@ Zone Asia/Aqtau 3:21:04 - LMT 1924 May 2 5:00 RussiaAsia +05/+06 1994 Sep 25 2:00s 4:00 RussiaAsia +04/+05 2004 Oct 31 2:00s 5:00 - +05 - +# Atyraū (KZ-ATY) is like Mangghystaū except it switched from +# +04/+05 to +05/+06 in spring 1999, not fall 1994. +Zone Asia/Atyrau 3:27:44 - LMT 1924 May 2 + 4:00 - +04 1930 Jun 21 + 5:00 - +05 1981 Oct 1 + 6:00 - +06 1982 Apr 1 + 5:00 RussiaAsia +05/+06 1991 Mar 31 2:00s + 4:00 RussiaAsia +04/+05 1992 Jan 19 2:00s + 5:00 RussiaAsia +05/+06 1999 Mar 28 2:00s + 4:00 RussiaAsia +04/+05 2004 Oct 31 2:00s + 5:00 - +05 # West Kazakhstan (KZ-ZAP) # From Paul Eggert (2016-03-18): # The 1989 transition is from USSR act No. 227 (1989-03-14). diff --git a/zone.tab b/zone.tab index f4969d2..bf78be7 100644 --- a/zone.tab +++ b/zone.tab @@ -239,7 +239,8 @@ KY +1918-08123 America/Cayman KZ +4315+07657 Asia/Almaty Kazakhstan (most areas) KZ +4448+06528 Asia/Qyzylorda Qyzylorda/Kyzylorda/Kzyl-Orda KZ +5017+05710 Asia/Aqtobe Aqtobe/Aktobe -KZ +4431+05016 Asia/Aqtau Atyrau/Atirau/Gur'yev, Mangghystau/Mankistau +KZ +4431+05016 Asia/Aqtau Mangghystau/Mankistau +KZ +4707+05156 Asia/Atyrau Atyrau/Atirau/Gur'yev KZ +5113+05121 Asia/Oral West Kazakhstan LA +1758+10236 Asia/Vientiane LB +3353+03530 Asia/Beirut diff --git a/zone1970.tab b/zone1970.tab index f48f7a6..ea2e1e5 100644 --- a/zone1970.tab +++ b/zone1970.tab @@ -210,8 +210,9 @@ KP +3901+12545 Asia/Pyongyang KR +3733+12658 Asia/Seoul KZ +4315+07657 Asia/Almaty Kazakhstan (most areas) KZ +4448+06528 Asia/Qyzylorda Qyzylorda/Kyzylorda/Kzyl-Orda -KZ +5017+05710 Asia/Aqtobe Aqtobe/Aktobe -KZ +4431+05016 Asia/Aqtau Atyrau/Atirau/Gur'yev, Mangghystau/Mankistau +KZ +5017+05710 Asia/Aqtobe Aqtöbe/Aktobe +KZ +4431+05016 Asia/Aqtau Mangghystaū/Mankistau +KZ +4707+05156 Asia/Atyrau Atyraū/Atirau/Gur'yev KZ +5113+05121 Asia/Oral West Kazakhstan LB +3353+03530 Asia/Beirut LK +0656+07951 Asia/Colombo -- 2.7.4

2 2

Fwd: [IANA #939704] Contributions to this list
by panda Dec. 6, 2016

Dec. 6, 2016

Dear Sir/Madam Please make the changes to time zone database: Ukraine: Kiev => Kyiv, Zaporozh'ye => Zaporizhia, Uzhgorod => Uzhhorod, Odessa => Odesa according to legal names and MORE COMMON USE in ENGLISH (like booking services or names of the airports, railway stations, river and sea ports and everyday speaking usage). Autonomous Republic of Crimea (Ukraine): Crimea, Republic of => Crimea, Autonomous Republic of according to legal name of the Ukrainian territory occupied by Russians terrorists forces. The name "Autonomous Republic of Crimea" is officially recognized by all of the countries (except the Russian Federation - the terrorist's country number one in the World) and in international COMMON USE in ENGLISH navigation systems of the air, sea and river transport systems. Sevastopol MSK => Sevastopol KMT Simferopol MSK => Simferopol KMT according to legal time usage on the Ukrainian territory. Andrii Pertsiukh -------- Forwarded Message -------- Тема: [IANA #939704] Contributions to this list Дата: Thu, 01 Dec 2016 20:16:50 +0000 Від: Amanda Baber via RT <iana-questions(a)iana.org> Відповісти: iana-questions(a)iana.org Кому: aristonomy(a)gmail.com Dear Sir/Madam, Thank you for contacting us. We host the Time Zone Database, but updates are made by the Time Zone Coordinator in consultation with the Time Zone mailing list, in accordance with RFC 6557. Questions about the contents of the database should be sent to the mailing list. For mailing list archives and subscription information, please see http://www.iana.org/time-zones Best regards, Amanda Baber Lead IANA Services Specialist PTI On Thu Dec 01 10:28:43 2016, aristonomy(a)gmail.com wrote: > To the holder of iana.org! > > Contributions to this list of time zones! > > "Uzhhorod International Airport", "Kyiv International Airport > (Zhuliany)", "Kyiv Boryspil international airport", "Zaporizhia > International Airport" which are MORE COMMON USE in every ENGLISH > booking service. The same names are used in the railway stations names > and booking services. > > Even more! Kyiv, Uzhhorod, Zaporizhia, Odesa are the international names > of the cityes, river and sea ports, airports and railway stations, parts > of the administration and state organizations names and etcetera. > > The only common use of the names: Kiev, Zaporozh'ye, Uzhgorod and Odessa > were in USSR - the country which is not exist any more (thanks to God!), > and in the country which are occupied the part of Ukraine. Supporting > such spelling is a direct support of the country which is now are the N1 > Country Terrorist of the World!! > > Europe/Simferopol and Europe/Sevastopol now are under Russian occupation > and NO legal international communications for hole Autonomous Republic > of Crimea (Ukraine) and this territory are legally under Ukrainians Law! > > Supporting of the time change to the MSK time zone is a direct support > of occupation!! > > This letter are public and will be shared to social network. > > Stop support of Russian invasion to Ukraine and Georgia!! Stop support > of the biggest terrorists organization which Russian Federation are! > > > # From Tim Parenti (2014-07-03): > > # Europe/Simferopol covers... > > # ** **** Crimea, Republic of > > # ** **** Sevastopol > > > > Zone Europe/Simferopol 2:16:24 - LMT 1880 > > 2:16 - SMT 1924 May 2 # Simferopol Mean T > > 2:00 - EET 1930 Jun 21 > > 3:00 - MSK 1941 Nov > > 1:00 C-Eur CE%sT 1944 Apr 13 > > 3:00 Russia MSK/MSD 1990 > > 3:00 - MSK 1990 Jul 1 2:00 > > 2:00 - EET 1992 > > # Central Crimea used Moscow time 1994/1997. > > # > > # From Paul Eggert (2006-03-22): > > # The _Economist_ (1994-05-28, p 45) reports that central Crimea switched > > # from Kiev to Moscow time sometime after the January 1994 elections. > > # Shanks (1999) says "date of change uncertain", but implies that it > > happened > > # sometime between the 1994 DST switches. Shanks & Pottenger simply say > > # 1994-09-25 03:00, but that can't be right. For now, guess it > > # changed in May. > > 2:00 E-Eur EE%sT 1994 May > > # From IATA SSIM (1994/1997), which also says that Kerch is still like > > Kiev. > > 3:00 E-Eur MSK/MSD 1996 Mar 31 0:00s > > 3:00 1:00 MSD 1996 Oct 27 3:00s > > # IATA SSIM (1997-09) says Crimea switched to EET/EEST. > > # Assume it happened in March by not changing the clocks. > > 3:00 Russia MSK/MSD 1997 > > 3:00 - MSK 1997 Mar lastSun 1:00u > > # From Alexander Krivenyshev (2014-03-17): > > # time change at 2:00 (2am) on March 30, 2014 > > # http://vz.ru/news/2014/3/17/677464.html > > # From Paul Eggert (2014-03-30): > > # Simferopol and Sevastopol reportedly changed their central town clocks > > # late the previous day, but this appears to have been ceremonial > > # and the discrepancies are small enough to not worry about. > > 2:00 EU EE%sT 2014 Mar 30 2:00 > > 4:00 - MSK 2014 Oct 26 2:00s > > 3:00 - MSK > > > > > > > > # Zone NAME GMTOFF RULES FORMAT [UNTIL] > > # Most of Ukraine since 1970 has been like Kiev. > > # "Kyiv" is the transliteration of the Ukrainian name, but > > # "Kiev" is more common in English. > > Zone Europe/Kiev 2:02:04 - LMT 1880 > > 2:02:04 - KMT 1924 May 2 # Kiev Mean Time > > > > # "Uzhhorod" is the transliteration of the Rusyn/Ukrainian > > pronunciation, but > > # "Uzhgorod" is more common in English. > > Zone Europe/Uzhgorod 1:29:12 - LMT 1890 Oct > > > > # Zaporozh'ye and eastern Lugansk oblasts observed DST 1990/1991. > > # "Zaporizhia" is the transliteration of the Ukrainian name, but > > # "Zaporozh'ye" is more common in English. Use the common English > > # spelling, except omit the apostrophe as it is not allowed in > > # portable Posix file names. > > Zone Europe/Zaporozhye 2:20:40 - LMT 1880 >

2 1

[PROPOSED] Use numeric abbrs for South American zones
by Paul Eggert Dec. 6, 2016

Dec. 6, 2016

Among other things, this treats Argentina (and Palmer) more consistently with respect to Chile. * NEWS: Document this. * southamerica (America/Argentina/Buenos_Aires) (America/Argentina/Cordoba, America/Argentina/Salta) (America/Argentina/Tucuman, America/Argentina/La_Rioja) (America/Argentina/San_Juan, America/Argentina/Jujuy) (America/Argentina/Catamarca, America/Argentina/Mendoza) (America/Argentina/San_Luis, America/Argentina/Rio_Gallegos) (America/Argentina/Ushuaia, America/La_Paz, America/Noronha) (America/Belem, America/Santarem, America/Fortaleza) (America/Recife, America/Araguaina, America/Maceio, America/Bahia) (America/Sao_Paulo, America/Campo_Grande, America/Cuiaba) (America/Porto_Velho, America/Boa_Vista, America/Manaus) (America/Eirunepe, America/Rio_Branco, America/Bogota) (America/Curacao, America/Guayaquil, Pacific/Galapagos) (Atlantic/Stanley, America/Cayenne, America/Guyana) (America/Asuncion, America/Lima, Atlantic/South_Georgia) (America/Paramaribo, America/Montevideo, America/Caracas): Use numeric rather than invented time zone abbreviations for integer-minutes UT offsets. --- NEWS | 25 +++- southamerica | 472 ++++++++++++++++++++++++++++------------------------------- 2 files changed, 244 insertions(+), 253 deletions(-) diff --git a/NEWS b/NEWS index 144a34b..31d96e8 100644 --- a/NEWS +++ b/NEWS @@ -11,11 +11,28 @@ Unreleased, experimental changes 23:00, hiving off a new zone America/Punta_Arenas. (Thanks to Juan Correa.) This also affects Antarctica/Palmer. - Changes to current and future time zone abbreviations + Changes to past and future time zone abbreviations - Switch to numeric time zones for Chile, so as to not invent an - abbreviation for its new zone. This affects America/Santiago, - Pacific/Easter, and Antarctica/Palmer. + Switch to numeric time zone abbreviations for South America, as + part of the ongoing project of removing invented abbreviations. + This avoids the need to invent an abbreviation for the new Chilean + new zone. This change affects America/Araguaina, + America/Argentina/Buenos_Aires, America/Argentina/Catamarca, + America/Argentina/Cordoba, America/Argentina/Jujuy, + America/Argentina/La_Rioja, America/Argentina/Mendoza, + America/Argentina/Rio_Gallegos, America/Argentina/Salta, + America/Argentina/San_Juan, America/Argentina/San_Luis, + America/Argentina/Tucuman, America/Argentina/Ushuaia, + America/Asuncion, America/Bahia, America/Belem, America/Boa_Vista, + America/Bogota, America/Campo_Grande, America/Caracas, + America/Cayenne, America/Cuiaba, America/Curacao, + America/Eirunepe, America/Fortaleza, America/Guayaquil, + America/Guyana, America/La_Paz, America/Lima, America/Maceio, + America/Manaus, America/Montevideo, America/Noronha, + America/Paramaribo, America/Porto_Velho, America/Recife, + America/Rio_Branco, America/Santarem, America/Santiago, + America/Sao_Paulo, Antarctica/Palmer, Atlantic/South_Georgia, + Atlantic/Stanley, Pacific/Easter, and Pacific/Galapagos. Changes to documentation and commentary diff --git a/southamerica b/southamerica index 43bc67e..a6820ac 100644 --- a/southamerica +++ b/southamerica @@ -6,15 +6,15 @@ # tz(a)iana.org for general use in the future). For more, please see # the file CONTRIBUTING in the tz distribution. -# From Paul Eggert (2014-10-31): +# From Paul Eggert (2016-12-05): # # Unless otherwise specified, the source for data through 1990 is: # Thomas G. Shanks and Rique Pottenger, The International Atlas (6th edition), # San Diego: ACS Publications, Inc. (2003). # Unfortunately this book contains many errors and cites no sources. # -# Gwillim Law writes that a good source -# for recent time zone data is the International Air Transport +# Many years ago Gwillim Law wrote that a good source +# for time zone data was the International Air Transport # Association's Standard Schedules Information Manual (IATA SSIM), # published semiannually. Law sent in several helpful summaries # of the IATA's data after 1990. Except where otherwise noted, @@ -24,32 +24,10 @@ # Milne J. Civil time. Geogr J. 1899 Feb;13(2):173-94. # http://www.jstor.org/stable/1774359 # -# Earlier editions of these tables used the North American style (e.g. ARST and -# ARDT for Argentine Standard and Daylight Time), but the following quote -# suggests that it's better to use European style (e.g. ART and ARST). -# I suggest the use of _Summer time_ instead of the more cumbersome -# _daylight-saving time_. _Summer time_ seems to be in general use -# in Europe and South America. -# -- E O Cutler, _New York Times_ (1937-02-14), quoted in -# H L Mencken, _The American Language: Supplement I_ (1960), p 466 -# -# Earlier editions of these tables also used the North American style -# for time zones in Brazil, but this was incorrect, as Brazilians say -# "summer time". Reinaldo Goulart, a São Paulo businessman active in -# the railroad sector, writes (1999-07-06): -# The subject of time zones is currently a matter of discussion/debate in -# Brazil. Let's say that "the Brasília time" is considered the -# "official time" because Brasília is the capital city. -# The other three time zones are called "Brasília time "minus one" or -# "plus one" or "plus two". As far as I know there is no such -# name/designation as "Eastern Time" or "Central Time". -# So I invented the following (English-language) abbreviations for now. -# Corrections are welcome! -# std dst -# -2:00 FNT FNST Fernando de Noronha -# -3:00 BRT BRST Brasília -# -4:00 AMT AMST Amazon -# -5:00 ACT ACST Acre +# These tables use numeric abbreviations like -03 and -0330 for +# integer hour and minute UTC offsets. Although earlier editions used +# alphabetic time zone abbreviations, these abbreviations were +# invented and did not reflect common practice. ############################################################################### @@ -384,12 +362,6 @@ Rule Arg 2008 only - Oct Sun>=15 0:00 1:00 S # # So I guess a new set of rules, besides "Arg", must be made and the last # America/Argentina/San_Luis entries should change to use these... -# -# I'm enclosing a patch that does what I say... regretfully, the San Luis -# timezone must be called "WART/WARST" even when most of the time (like, -# right now) WARST == ART... that is, since last Sunday, all the country -# is using UTC-3, but in my patch, San Luis calls it "WARST" and the rest -# of the country calls it "ART". # ... # From Alexander Krivenyshev (2010-04-09): @@ -428,11 +400,11 @@ Rule Arg 2008 only - Oct Sun>=15 0:00 1:00 S # Buenos Aires (BA), Capital Federal (CF), Zone America/Argentina/Buenos_Aires -3:53:48 - LMT 1894 Oct 31 -4:16:48 - CMT 1920 May # Córdoba Mean Time - -4:00 - ART 1930 Dec - -4:00 Arg AR%sT 1969 Oct 5 - -3:00 Arg AR%sT 1999 Oct 3 - -4:00 Arg AR%sT 2000 Mar 3 - -3:00 Arg AR%sT + -4:00 - -04 1930 Dec + -4:00 Arg -04/-03 1969 Oct 5 + -3:00 Arg -03/-02 1999 Oct 3 + -4:00 Arg -04/-03 2000 Mar 3 + -3:00 Arg -03/-02 # # Córdoba (CB), Santa Fe (SF), Entre Ríos (ER), Corrientes (CN), Misiones (MN), # Chaco (CC), Formosa (FM), Santiago del Estero (SE) @@ -446,113 +418,113 @@ Zone America/Argentina/Buenos_Aires -3:53:48 - LMT 1894 Oct 31 # Zone America/Argentina/Cordoba -4:16:48 - LMT 1894 Oct 31 -4:16:48 - CMT 1920 May - -4:00 - ART 1930 Dec - -4:00 Arg AR%sT 1969 Oct 5 - -3:00 Arg AR%sT 1991 Mar 3 - -4:00 - WART 1991 Oct 20 - -3:00 Arg AR%sT 1999 Oct 3 - -4:00 Arg AR%sT 2000 Mar 3 - -3:00 Arg AR%sT + -4:00 - -04 1930 Dec + -4:00 Arg -04/-03 1969 Oct 5 + -3:00 Arg -03/-02 1991 Mar 3 + -4:00 - -04 1991 Oct 20 + -3:00 Arg -03/-02 1999 Oct 3 + -4:00 Arg -04/-03 2000 Mar 3 + -3:00 Arg -03/-02 # # Salta (SA), La Pampa (LP), Neuquén (NQ), Rio Negro (RN) Zone America/Argentina/Salta -4:21:40 - LMT 1894 Oct 31 -4:16:48 - CMT 1920 May - -4:00 - ART 1930 Dec - -4:00 Arg AR%sT 1969 Oct 5 - -3:00 Arg AR%sT 1991 Mar 3 - -4:00 - WART 1991 Oct 20 - -3:00 Arg AR%sT 1999 Oct 3 - -4:00 Arg AR%sT 2000 Mar 3 - -3:00 Arg AR%sT 2008 Oct 18 - -3:00 - ART + -4:00 - -04 1930 Dec + -4:00 Arg -04/-03 1969 Oct 5 + -3:00 Arg -03/-02 1991 Mar 3 + -4:00 - -04 1991 Oct 20 + -3:00 Arg -03/-02 1999 Oct 3 + -4:00 Arg -04/-03 2000 Mar 3 + -3:00 Arg -03/-02 2008 Oct 18 + -3:00 - -03 # # Tucumán (TM) Zone America/Argentina/Tucuman -4:20:52 - LMT 1894 Oct 31 -4:16:48 - CMT 1920 May - -4:00 - ART 1930 Dec - -4:00 Arg AR%sT 1969 Oct 5 - -3:00 Arg AR%sT 1991 Mar 3 - -4:00 - WART 1991 Oct 20 - -3:00 Arg AR%sT 1999 Oct 3 - -4:00 Arg AR%sT 2000 Mar 3 - -3:00 - ART 2004 Jun 1 - -4:00 - WART 2004 Jun 13 - -3:00 Arg AR%sT + -4:00 - -04 1930 Dec + -4:00 Arg -04/-03 1969 Oct 5 + -3:00 Arg -03/-02 1991 Mar 3 + -4:00 - -04 1991 Oct 20 + -3:00 Arg -03/-02 1999 Oct 3 + -4:00 Arg -04/-03 2000 Mar 3 + -3:00 - -03 2004 Jun 1 + -4:00 - -04 2004 Jun 13 + -3:00 Arg -03/-02 # # La Rioja (LR) Zone America/Argentina/La_Rioja -4:27:24 - LMT 1894 Oct 31 -4:16:48 - CMT 1920 May - -4:00 - ART 1930 Dec - -4:00 Arg AR%sT 1969 Oct 5 - -3:00 Arg AR%sT 1991 Mar 1 - -4:00 - WART 1991 May 7 - -3:00 Arg AR%sT 1999 Oct 3 - -4:00 Arg AR%sT 2000 Mar 3 - -3:00 - ART 2004 Jun 1 - -4:00 - WART 2004 Jun 20 - -3:00 Arg AR%sT 2008 Oct 18 - -3:00 - ART + -4:00 - -04 1930 Dec + -4:00 Arg -04/-03 1969 Oct 5 + -3:00 Arg -03/-02 1991 Mar 1 + -4:00 - -04 1991 May 7 + -3:00 Arg -03/-02 1999 Oct 3 + -4:00 Arg -04/-03 2000 Mar 3 + -3:00 - -03 2004 Jun 1 + -4:00 - -04 2004 Jun 20 + -3:00 Arg -03/-02 2008 Oct 18 + -3:00 - -03 # # San Juan (SJ) Zone America/Argentina/San_Juan -4:34:04 - LMT 1894 Oct 31 -4:16:48 - CMT 1920 May - -4:00 - ART 1930 Dec - -4:00 Arg AR%sT 1969 Oct 5 - -3:00 Arg AR%sT 1991 Mar 1 - -4:00 - WART 1991 May 7 - -3:00 Arg AR%sT 1999 Oct 3 - -4:00 Arg AR%sT 2000 Mar 3 - -3:00 - ART 2004 May 31 - -4:00 - WART 2004 Jul 25 - -3:00 Arg AR%sT 2008 Oct 18 - -3:00 - ART + -4:00 - -04 1930 Dec + -4:00 Arg -04/-03 1969 Oct 5 + -3:00 Arg -03/-02 1991 Mar 1 + -4:00 - -04 1991 May 7 + -3:00 Arg -03/-02 1999 Oct 3 + -4:00 Arg -04/-03 2000 Mar 3 + -3:00 - -03 2004 May 31 + -4:00 - -04 2004 Jul 25 + -3:00 Arg -03/-02 2008 Oct 18 + -3:00 - -03 # # Jujuy (JY) Zone America/Argentina/Jujuy -4:21:12 - LMT 1894 Oct 31 -4:16:48 - CMT 1920 May - -4:00 - ART 1930 Dec - -4:00 Arg AR%sT 1969 Oct 5 - -3:00 Arg AR%sT 1990 Mar 4 - -4:00 - WART 1990 Oct 28 - -4:00 1:00 WARST 1991 Mar 17 - -4:00 - WART 1991 Oct 6 - -3:00 1:00 ARST 1992 - -3:00 Arg AR%sT 1999 Oct 3 - -4:00 Arg AR%sT 2000 Mar 3 - -3:00 Arg AR%sT 2008 Oct 18 - -3:00 - ART + -4:00 - -04 1930 Dec + -4:00 Arg -04/-03 1969 Oct 5 + -3:00 Arg -03/-02 1990 Mar 4 + -4:00 - -04 1990 Oct 28 + -4:00 1:00 -03 1991 Mar 17 + -4:00 - -04 1991 Oct 6 + -3:00 1:00 -02 1992 + -3:00 Arg -03/-02 1999 Oct 3 + -4:00 Arg -04/-03 2000 Mar 3 + -3:00 Arg -03/-02 2008 Oct 18 + -3:00 - -03 # # Catamarca (CT), Chubut (CH) Zone America/Argentina/Catamarca -4:23:08 - LMT 1894 Oct 31 -4:16:48 - CMT 1920 May - -4:00 - ART 1930 Dec - -4:00 Arg AR%sT 1969 Oct 5 - -3:00 Arg AR%sT 1991 Mar 3 - -4:00 - WART 1991 Oct 20 - -3:00 Arg AR%sT 1999 Oct 3 - -4:00 Arg AR%sT 2000 Mar 3 - -3:00 - ART 2004 Jun 1 - -4:00 - WART 2004 Jun 20 - -3:00 Arg AR%sT 2008 Oct 18 - -3:00 - ART + -4:00 - -04 1930 Dec + -4:00 Arg -04/-03 1969 Oct 5 + -3:00 Arg -03/-02 1991 Mar 3 + -4:00 - -04 1991 Oct 20 + -3:00 Arg -03/-02 1999 Oct 3 + -4:00 Arg -04/-03 2000 Mar 3 + -3:00 - -03 2004 Jun 1 + -4:00 - -04 2004 Jun 20 + -3:00 Arg -03/-02 2008 Oct 18 + -3:00 - -03 # # Mendoza (MZ) Zone America/Argentina/Mendoza -4:35:16 - LMT 1894 Oct 31 -4:16:48 - CMT 1920 May - -4:00 - ART 1930 Dec - -4:00 Arg AR%sT 1969 Oct 5 - -3:00 Arg AR%sT 1990 Mar 4 - -4:00 - WART 1990 Oct 15 - -4:00 1:00 WARST 1991 Mar 1 - -4:00 - WART 1991 Oct 15 - -4:00 1:00 WARST 1992 Mar 1 - -4:00 - WART 1992 Oct 18 - -3:00 Arg AR%sT 1999 Oct 3 - -4:00 Arg AR%sT 2000 Mar 3 - -3:00 - ART 2004 May 23 - -4:00 - WART 2004 Sep 26 - -3:00 Arg AR%sT 2008 Oct 18 - -3:00 - ART + -4:00 - -04 1930 Dec + -4:00 Arg -04/-03 1969 Oct 5 + -3:00 Arg -03/-02 1990 Mar 4 + -4:00 - -04 1990 Oct 15 + -4:00 1:00 -03 1991 Mar 1 + -4:00 - -04 1991 Oct 15 + -4:00 1:00 -03 1992 Mar 1 + -4:00 - -04 1992 Oct 18 + -3:00 Arg -03/-02 1999 Oct 3 + -4:00 Arg -04/-03 2000 Mar 3 + -3:00 - -03 2004 May 23 + -4:00 - -04 2004 Sep 26 + -3:00 Arg -03/-02 2008 Oct 18 + -3:00 - -03 # # San Luis (SL) @@ -561,44 +533,44 @@ Rule SanLuis 2007 2008 - Oct Sun>=8 0:00 1:00 S Zone America/Argentina/San_Luis -4:25:24 - LMT 1894 Oct 31 -4:16:48 - CMT 1920 May - -4:00 - ART 1930 Dec - -4:00 Arg AR%sT 1969 Oct 5 - -3:00 Arg AR%sT 1990 - -3:00 1:00 ARST 1990 Mar 14 - -4:00 - WART 1990 Oct 15 - -4:00 1:00 WARST 1991 Mar 1 - -4:00 - WART 1991 Jun 1 - -3:00 - ART 1999 Oct 3 - -4:00 1:00 WARST 2000 Mar 3 - -3:00 - ART 2004 May 31 - -4:00 - WART 2004 Jul 25 - -3:00 Arg AR%sT 2008 Jan 21 - -4:00 SanLuis WAR%sT 2009 Oct 11 - -3:00 - ART + -4:00 - -04 1930 Dec + -4:00 Arg -04/-03 1969 Oct 5 + -3:00 Arg -03/-02 1990 + -3:00 1:00 -02 1990 Mar 14 + -4:00 - -04 1990 Oct 15 + -4:00 1:00 -03 1991 Mar 1 + -4:00 - -04 1991 Jun 1 + -3:00 - -03 1999 Oct 3 + -4:00 1:00 -03 2000 Mar 3 + -3:00 - -03 2004 May 31 + -4:00 - -04 2004 Jul 25 + -3:00 Arg -03/-02 2008 Jan 21 + -4:00 SanLuis -04/-03 2009 Oct 11 + -3:00 - -03 # # Santa Cruz (SC) Zone America/Argentina/Rio_Gallegos -4:36:52 - LMT 1894 Oct 31 - -4:16:48 - CMT 1920 May # Córdoba Mean Time - -4:00 - ART 1930 Dec - -4:00 Arg AR%sT 1969 Oct 5 - -3:00 Arg AR%sT 1999 Oct 3 - -4:00 Arg AR%sT 2000 Mar 3 - -3:00 - ART 2004 Jun 1 - -4:00 - WART 2004 Jun 20 - -3:00 Arg AR%sT 2008 Oct 18 - -3:00 - ART + -4:16:48 - CMT 1920 May + -4:00 - -04 1930 Dec + -4:00 Arg -04/-03 1969 Oct 5 + -3:00 Arg -03/-02 1999 Oct 3 + -4:00 Arg -04/-03 2000 Mar 3 + -3:00 - -03 2004 Jun 1 + -4:00 - -04 2004 Jun 20 + -3:00 Arg -03/-02 2008 Oct 18 + -3:00 - -03 # # Tierra del Fuego, Antártida e Islas del Atlántico Sur (TF) Zone America/Argentina/Ushuaia -4:33:12 - LMT 1894 Oct 31 - -4:16:48 - CMT 1920 May # Córdoba Mean Time - -4:00 - ART 1930 Dec - -4:00 Arg AR%sT 1969 Oct 5 - -3:00 Arg AR%sT 1999 Oct 3 - -4:00 Arg AR%sT 2000 Mar 3 - -3:00 - ART 2004 May 30 - -4:00 - WART 2004 Jun 20 - -3:00 Arg AR%sT 2008 Oct 18 - -3:00 - ART + -4:16:48 - CMT 1920 May + -4:00 - -04 1930 Dec + -4:00 Arg -04/-03 1969 Oct 5 + -3:00 Arg -03/-02 1999 Oct 3 + -4:00 Arg -04/-03 2000 Mar 3 + -3:00 - -03 2004 May 30 + -4:00 - -04 2004 Jun 20 + -3:00 Arg -03/-02 2008 Oct 18 + -3:00 - -03 # Aruba Link America/Curacao America/Aruba @@ -608,7 +580,7 @@ Link America/Curacao America/Aruba Zone America/La_Paz -4:32:36 - LMT 1890 -4:32:36 - CMT 1931 Oct 15 # Calamarca MT -4:32:36 1:00 BOST 1932 Mar 21 # Bolivia ST - -4:00 - BOT # Bolivia Time + -4:00 - -04 # Brazil @@ -960,12 +932,12 @@ Rule Brazil 2038 max - Feb Sun>=15 0:00 0 - # # Fernando de Noronha (administratively part of PE) Zone America/Noronha -2:09:40 - LMT 1914 - -2:00 Brazil FN%sT 1990 Sep 17 - -2:00 - FNT 1999 Sep 30 - -2:00 Brazil FN%sT 2000 Oct 15 - -2:00 - FNT 2001 Sep 13 - -2:00 Brazil FN%sT 2002 Oct 1 - -2:00 - FNT + -2:00 Brazil -02/-01 1990 Sep 17 + -2:00 - -02 1999 Sep 30 + -2:00 Brazil -02/-01 2000 Oct 15 + -2:00 - -02 2001 Sep 13 + -2:00 Brazil -02/-01 2002 Oct 1 + -2:00 - -02 # Other Atlantic islands have no permanent settlement. # These include Trindade and Martim Vaz (administratively part of ES), # Rocas Atoll (RN), and the St Peter and St Paul Archipelago (PE). @@ -978,119 +950,119 @@ Zone America/Noronha -2:09:40 - LMT 1914 # In the north a very small part from the river Javary (now Jari I guess, # the border with Amapá) to the Amazon, then to the Xingu. Zone America/Belem -3:13:56 - LMT 1914 - -3:00 Brazil BR%sT 1988 Sep 12 - -3:00 - BRT + -3:00 Brazil -03/-02 1988 Sep 12 + -3:00 - -03 # # west Pará (PA) # West Pará includes Altamira, Óbidos, Prainha, Oriximiná, and Santarém. Zone America/Santarem -3:38:48 - LMT 1914 - -4:00 Brazil AM%sT 1988 Sep 12 - -4:00 - AMT 2008 Jun 24 0:00 - -3:00 - BRT + -4:00 Brazil -04/-03 1988 Sep 12 + -4:00 - -04 2008 Jun 24 0:00 + -3:00 - -03 # # Maranhão (MA), Piauí (PI), Ceará (CE), Rio Grande do Norte (RN), # Paraíba (PB) Zone America/Fortaleza -2:34:00 - LMT 1914 - -3:00 Brazil BR%sT 1990 Sep 17 - -3:00 - BRT 1999 Sep 30 - -3:00 Brazil BR%sT 2000 Oct 22 - -3:00 - BRT 2001 Sep 13 - -3:00 Brazil BR%sT 2002 Oct 1 - -3:00 - BRT + -3:00 Brazil -03/-02 1990 Sep 17 + -3:00 - -03 1999 Sep 30 + -3:00 Brazil -03/-02 2000 Oct 22 + -3:00 - -03 2001 Sep 13 + -3:00 Brazil -03/-02 2002 Oct 1 + -3:00 - -03 # # Pernambuco (PE) (except Atlantic islands) Zone America/Recife -2:19:36 - LMT 1914 - -3:00 Brazil BR%sT 1990 Sep 17 - -3:00 - BRT 1999 Sep 30 - -3:00 Brazil BR%sT 2000 Oct 15 - -3:00 - BRT 2001 Sep 13 - -3:00 Brazil BR%sT 2002 Oct 1 - -3:00 - BRT + -3:00 Brazil -03/-02 1990 Sep 17 + -3:00 - -03 1999 Sep 30 + -3:00 Brazil -03/-02 2000 Oct 15 + -3:00 - -03 2001 Sep 13 + -3:00 Brazil -03/-02 2002 Oct 1 + -3:00 - -03 # # Tocantins (TO) Zone America/Araguaina -3:12:48 - LMT 1914 - -3:00 Brazil BR%sT 1990 Sep 17 - -3:00 - BRT 1995 Sep 14 - -3:00 Brazil BR%sT 2003 Sep 24 - -3:00 - BRT 2012 Oct 21 - -3:00 Brazil BR%sT 2013 Sep - -3:00 - BRT + -3:00 Brazil -03/-02 1990 Sep 17 + -3:00 - -03 1995 Sep 14 + -3:00 Brazil -03/-02 2003 Sep 24 + -3:00 - -03 2012 Oct 21 + -3:00 Brazil -03/-02 2013 Sep + -3:00 - -03 # # Alagoas (AL), Sergipe (SE) Zone America/Maceio -2:22:52 - LMT 1914 - -3:00 Brazil BR%sT 1990 Sep 17 - -3:00 - BRT 1995 Oct 13 - -3:00 Brazil BR%sT 1996 Sep 4 - -3:00 - BRT 1999 Sep 30 - -3:00 Brazil BR%sT 2000 Oct 22 - -3:00 - BRT 2001 Sep 13 - -3:00 Brazil BR%sT 2002 Oct 1 - -3:00 - BRT + -3:00 Brazil -03/-02 1990 Sep 17 + -3:00 - -03 1995 Oct 13 + -3:00 Brazil -03/-02 1996 Sep 4 + -3:00 - -03 1999 Sep 30 + -3:00 Brazil -03/-02 2000 Oct 22 + -3:00 - -03 2001 Sep 13 + -3:00 Brazil -03/-02 2002 Oct 1 + -3:00 - -03 # # Bahia (BA) # There are too many Salvadors elsewhere, so use America/Bahia instead # of America/Salvador. Zone America/Bahia -2:34:04 - LMT 1914 - -3:00 Brazil BR%sT 2003 Sep 24 - -3:00 - BRT 2011 Oct 16 - -3:00 Brazil BR%sT 2012 Oct 21 - -3:00 - BRT + -3:00 Brazil -03/-02 2003 Sep 24 + -3:00 - -03 2011 Oct 16 + -3:00 Brazil -03/-02 2012 Oct 21 + -3:00 - -03 # # Goiás (GO), Distrito Federal (DF), Minas Gerais (MG), # Espírito Santo (ES), Rio de Janeiro (RJ), São Paulo (SP), Paraná (PR), # Santa Catarina (SC), Rio Grande do Sul (RS) Zone America/Sao_Paulo -3:06:28 - LMT 1914 - -3:00 Brazil BR%sT 1963 Oct 23 0:00 - -3:00 1:00 BRST 1964 - -3:00 Brazil BR%sT + -3:00 Brazil -03/-02 1963 Oct 23 0:00 + -3:00 1:00 -02 1964 + -3:00 Brazil -03/-02 # # Mato Grosso do Sul (MS) Zone America/Campo_Grande -3:38:28 - LMT 1914 - -4:00 Brazil AM%sT + -4:00 Brazil -04/-03 # # Mato Grosso (MT) Zone America/Cuiaba -3:44:20 - LMT 1914 - -4:00 Brazil AM%sT 2003 Sep 24 - -4:00 - AMT 2004 Oct 1 - -4:00 Brazil AM%sT + -4:00 Brazil -04/-03 2003 Sep 24 + -4:00 - -04 2004 Oct 1 + -4:00 Brazil -04/-03 # # Rondônia (RO) Zone America/Porto_Velho -4:15:36 - LMT 1914 - -4:00 Brazil AM%sT 1988 Sep 12 - -4:00 - AMT + -4:00 Brazil -04/-03 1988 Sep 12 + -4:00 - -04 # # Roraima (RR) Zone America/Boa_Vista -4:02:40 - LMT 1914 - -4:00 Brazil AM%sT 1988 Sep 12 - -4:00 - AMT 1999 Sep 30 - -4:00 Brazil AM%sT 2000 Oct 15 - -4:00 - AMT + -4:00 Brazil -04/-03 1988 Sep 12 + -4:00 - -04 1999 Sep 30 + -4:00 Brazil -04/-03 2000 Oct 15 + -4:00 - -04 # # east Amazonas (AM): Boca do Acre, Jutaí, Manaus, Floriano Peixoto # The great circle line from Tabatinga to Porto Acre divides # east from west Amazonas. Zone America/Manaus -4:00:04 - LMT 1914 - -4:00 Brazil AM%sT 1988 Sep 12 - -4:00 - AMT 1993 Sep 28 - -4:00 Brazil AM%sT 1994 Sep 22 - -4:00 - AMT + -4:00 Brazil -04/-03 1988 Sep 12 + -4:00 - -04 1993 Sep 28 + -4:00 Brazil -04/-03 1994 Sep 22 + -4:00 - -04 # # west Amazonas (AM): Atalaia do Norte, Boca do Maoco, Benjamin Constant, # Eirunepé, Envira, Ipixuna Zone America/Eirunepe -4:39:28 - LMT 1914 - -5:00 Brazil AC%sT 1988 Sep 12 - -5:00 - ACT 1993 Sep 28 - -5:00 Brazil AC%sT 1994 Sep 22 - -5:00 - ACT 2008 Jun 24 0:00 - -4:00 - AMT 2013 Nov 10 - -5:00 - ACT + -5:00 Brazil -05/-04 1988 Sep 12 + -5:00 - -05 1993 Sep 28 + -5:00 Brazil -05/-04 1994 Sep 22 + -5:00 - -05 2008 Jun 24 0:00 + -4:00 - -04 2013 Nov 10 + -5:00 - -05 # # Acre (AC) Zone America/Rio_Branco -4:31:12 - LMT 1914 - -5:00 Brazil AC%sT 1988 Sep 12 - -5:00 - ACT 2008 Jun 24 0:00 - -4:00 - AMT 2013 Nov 10 - -5:00 - ACT + -5:00 Brazil -05/-04 1988 Sep 12 + -5:00 - -05 2008 Jun 24 0:00 + -4:00 - -04 2013 Nov 10 + -5:00 - -05 # Chile @@ -1343,7 +1315,7 @@ Rule CO 1993 only - Apr 4 0:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Bogota -4:56:16 - LMT 1884 Mar 13 -4:56:16 - BMT 1914 Nov 23 # Bogotá Mean Time - -5:00 CO CO%sT # Colombia Time + -5:00 CO -05/-04 # Malpelo, Providencia, San Andres # no information; probably like America/Bogota @@ -1367,7 +1339,7 @@ Zone America/Bogota -4:56:16 - LMT 1884 Mar 13 # # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Curacao -4:35:47 - LMT 1912 Feb 12 # Willemstad - -4:30 - ANT 1965 # Netherlands Antilles Time + -4:30 - -0430 1965 -4:00 - AST # From Arthur David Olson (2011-06-15): @@ -1391,10 +1363,10 @@ Link America/Curacao America/Kralendijk # Caribbean Netherlands # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Guayaquil -5:19:20 - LMT 1890 -5:14:00 - QMT 1931 # Quito Mean Time - -5:00 - ECT # Ecuador Time + -5:00 - -05 Zone Pacific/Galapagos -5:58:24 - LMT 1931 # Puerto Baquerizo Moreno - -5:00 - ECT 1986 - -6:00 - GALT # Galápagos Time + -5:00 - -05 1986 + -6:00 - -06 # Falklands @@ -1494,25 +1466,24 @@ Rule Falk 2001 2010 - Sep Sun>=1 2:00 1:00 S # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Atlantic/Stanley -3:51:24 - LMT 1890 -3:51:24 - SMT 1912 Mar 12 # Stanley Mean Time - -4:00 Falk FK%sT 1983 May # Falkland Is Time - -3:00 Falk FK%sT 1985 Sep 15 - -4:00 Falk FK%sT 2010 Sep 5 2:00 - -3:00 - FKST + -4:00 Falk -04/-03 1983 May # Falkland Is Time + -3:00 Falk -03/-02 1985 Sep 15 + -4:00 Falk -04/-03 2010 Sep 5 2:00 + -3:00 - -03 # French Guiana # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Cayenne -3:29:20 - LMT 1911 Jul - -4:00 - GFT 1967 Oct # French Guiana Time - -3:00 - GFT + -4:00 - -04 1967 Oct + -3:00 - -03 # Guyana # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Guyana -3:52:40 - LMT 1915 Mar # Georgetown - -3:45 - GBGT 1966 May 26 # Br Guiana Time - -3:45 - GYT 1975 Jul 31 # Guyana Time - -3:00 - GYT 1991 + -3:45 - -0345 1975 Jul 31 + -3:00 - -03 1991 # IATA SSIM (1996-06) says -4:00. Assume a 1991 switch. - -4:00 - GYT + -4:00 - -04 # Paraguay # @@ -1604,9 +1575,9 @@ Rule Para 2013 max - Mar Sun>=22 0:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Asuncion -3:50:40 - LMT 1890 -3:50:40 - AMT 1931 Oct 10 # Asunción Mean Time - -4:00 - PYT 1972 Oct # Paraguay Time - -3:00 - PYT 1974 Apr - -4:00 Para PY%sT + -4:00 - -04 1972 Oct + -3:00 - -03 1974 Apr + -4:00 Para -04/-03 # Peru # @@ -1633,12 +1604,12 @@ Rule Peru 1994 only - Apr 1 0:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Lima -5:08:12 - LMT 1890 -5:08:36 - LMT 1908 Jul 28 # Lima Mean Time? - -5:00 Peru PE%sT # Peru Time + -5:00 Peru -05/-04 # South Georgia # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Atlantic/South_Georgia -2:26:08 - LMT 1890 # Grytviken - -2:00 - GST # South Georgia Time + -2:00 - -02 # South Sandwich Is # uninhabited; scientific personnel have wintered @@ -1648,9 +1619,8 @@ Zone Atlantic/South_Georgia -2:26:08 - LMT 1890 # Grytviken Zone America/Paramaribo -3:40:40 - LMT 1911 -3:40:52 - PMT 1935 # Paramaribo Mean Time -3:40:36 - PMT 1945 Oct # The capital moved? - -3:30 - NEGT 1975 Nov 20 # Dutch Guiana Time - -3:30 - SRT 1984 Oct # Suriname Time - -3:00 - SRT + -3:30 - -0330 1984 Oct + -3:00 - -03 # Trinidad and Tobago # Zone NAME GMTOFF RULES FORMAT [UNTIL] @@ -1756,8 +1726,12 @@ Rule Uruguay 2007 2015 - Mar Sun>=8 2:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Montevideo -3:44:44 - LMT 1898 Jun 28 -3:44:44 - MMT 1920 May 1 # Montevideo MT - -3:30 Uruguay UY%sT 1942 Dec 14 # Uruguay Time - -3:00 Uruguay UY%sT + -3:30 Uruguay -0330/-03 1942 Dec 14 + -3:00 Uruguay -03/-02 1968 + -3:00 Uruguay -03/-0230 1971 + -3:00 Uruguay -03/-02 1974 + -3:00 Uruguay -03/-0230 1974 Dec 22 + -3:00 Uruguay -03/-02 # Venezuela # @@ -1791,7 +1765,7 @@ Zone America/Montevideo -3:44:44 - LMT 1898 Jun 28 # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Caracas -4:27:44 - LMT 1890 -4:27:40 - CMT 1912 Feb 12 # Caracas Mean Time? - -4:30 - VET 1965 Jan 1 0:00 # Venezuela T. - -4:00 - VET 2007 Dec 9 3:00 - -4:30 - VET 2016 May 1 2:30 - -4:00 - VET + -4:30 - -0430 1965 Jan 1 0:00 + -4:00 - -04 2007 Dec 9 3:00 + -4:30 - -0430 2016 May 1 2:30 + -4:00 - -04 -- 2.7.4

1 0

[PATCH] * Theory: reword to avoid no-longer-used VLAST
by Paul Eggert Dec. 6, 2016

Dec. 6, 2016

--- Theory | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Theory b/Theory index ea4b35d..e40f124 100644 --- a/Theory +++ b/Theory @@ -226,7 +226,7 @@ in decreasing order of importance: for double summer time append 'DST'; etc. Otherwise, take the first three letters of an English place name identifying each zone and append 'T', 'ST', etc. - as before; e.g. 'VLAST' for VLAdivostok Summer Time. + as before; e.g. 'CHAST' for CHAtham Summer Time. Use UT (with time zone abbreviation '-00') for locations while uninhabited. The leading '-' is a flag that the time -- 2.7.4

1 0

Google public NTP servers to 'smear' leap seconds.
by J William Piggott Dec. 5, 2016

Dec. 5, 2016

"For timekeeping purposes, December 31 will seem like any other day." https://cloudplatform.googleblog.com/2016/11/making-every-leap-second-count…

5 12

Zone name policy
by Maksym Besida Dec. 2, 2016

Dec. 2, 2016

Hello, In all versions of TZ data Ukraine zones are named using Russian language transliteration (e.g Europe/Kiev, Europe/Uzhgorod, Europe/Zaporozhye). In *tzdata2016j* in file *europe *it is said *"Kyiv is the transliteration of the Ukrainian name, but "Kiev" is more common in English".* But this is a mistake, because *"more common"* is a very subjective measure and in this case is imposed by russian speaking community which is larger than ukrainian one. Believe that in most groups of Chinese language the mentioned names are pronounced differently from Russian transliteration(even if chinese speaking population is greater than russian one). The official language in Ukraine is Ukrainian, so the proper names of mentioned cities are Kyiv, Uzhhorod and Zaporizhia respectively. Who is responsible for editing this data? -- Regards, Maksym Besida.

9 12

Doubt about releases/updates
by Pablo Sánchez Dec. 1, 2016

Dec. 1, 2016

Greetings, everyone! I have a doubt about the TZ database release or updates, and maybe you can help me to solve it. So, is the database update BEFORE or AFTER a new DST has started? The reason why I need to know it is because we are having issues about calculating some ETAs and presenting the information on reports, because PHP internal database doesn't get updates automatically. So we decided to use an extension that uses IANA's Timezone Database (updated approximatelly 23 times an year). So, we need to know if those updates are released before the daylight saving time starts or if you release it before it starts. Since there are usually political decisions that delays or rushes the DST beginning, I believe those updates comes prior to the actual fact, with a data on wich day begin, so I should not worry on using the extension that updates itself with 24 hours delay, right? So, do you update it before DST comes, or after? -- *Pablo Santiago Sánchez* ZCE ZEND006757 phackwer(a)gmail.com (61) 9843-0883 http://www.sansis.com.br *"Pluralitas non est ponenda sine necessitate"*

6 7

Re: [tz] DST cancelled for Asia/Baku since 17 March 2016
by Ariel Dor Nov. 30, 2016

Nov. 30, 2016

Ahh. Nm. Found it under thread "Azerbaijan canceled daylight saving time" >From March. BR Ariel From: Ariel Dor Sent: Wednesday, November 30, 2016 16:30 To: 'tz(a)iana.org' Subject: DST cancelled for Asia/Baku since 17 March 2016 Hi, I couldn't find a reference for this change from 17/Mar/2016 to be implemented in any tzdata revision. I did see that there was a minor correction for Asia/Baku in 2016e DB (for 1992), but not for the change from 2016 and on. Source https://www.timeanddate.com/news/time/no-dst-azerbaijan.html BR, Ariel

1 0

DST cancelled for Asia/Baku since 17 March 2016
by Ariel Dor Nov. 30, 2016

Nov. 30, 2016

Hi, I couldn't find a reference for this change from 17/Mar/2016 to be implemented in any tzdata revision. I did see that there was a minor correction for Asia/Baku in 2016e DB (for 1992), but not for the change from 2016 and on. Source https://www.timeanddate.com/news/time/no-dst-azerbaijan.html BR, Ariel

1 0

Happy 30th anniversary!
by Arthur David Olson Nov. 29, 2016

Nov. 29, 2016

------------------------------ > ...*Tue Nov 25 00:58:12 UTC 1986* > ... > Now that we've moved from 4.1BSD to 4.3BSD here at elsie, > I've set things up so that mail sent to > seismo!elsie!tz > will go to folks who've expressed an interest in time zone matters. http://mm.icann.org/pipermail/tz/1986-November/008946.html (Note that it was really the 24th local time.) @dashdashado

5 4

[tz-announce] 2016j release of tz code and data available
by Paul Eggert Nov. 24, 2016

Nov. 24, 2016

The 2016j release of the tz code and data is available. It reflects the following changes, which were either circulated on the tz mailing list or are relatively minor technical or administrative changes: Briefly: Saratov, Russia moves from +03 to +04 on 2016-12-04. Changes to future time stamps Saratov, Russia switches from +03 to +04 on 2016-12-04 at 02:00. This hives off a new zone Europe/Saratov from Europe/Volgograd. (Thanks to Yuri Konotopov and Stepan Golosunov.) Changes to past time stamps The new zone Asia/Atyrau for Atyraū Region, Kazakhstan, is like Asia/Aqtau except it switched from +04/+05 to +05/+06 in spring 1999, not fall 1994. (Thanks to Stepan Golosunov.) Changes to past time zone abbreviations Asia/Gaza and Asia/Hebron now use "EEST", not "EET", to denote summer time before 1948. The old use of "EET" was a typo. Changes to code zic no longer mishandles file systems that lack hard links, fixing bugs introduced in 2016g. (Problems reported by Tom Lane.) Also, when the destination already contains symbolic links, zic should now work better on systems where the 'link' system call does not follow symbolic links. Changes to documentation and commentary tz-link.htm now documents the relationship between release version numbers and development-repository commit tags. (Suggested by Paul Koning.) The 'Theory' file now documents UT. iso3166.tab now accents "Curaçao", and commentary now mentions the names "Cabo Verde" and "Czechia". (Thanks to Jiří Boháč.) Here are links to the release files: ftp://ftp.iana.org/tz/releases/tzcode2016j.tar.gz ftp://ftp.iana.org/tz/releases/tzdata2016j.tar.gz ftp://ftp.iana.org/tz/releases/tzdb-2016j.tar.lz The files are also available via HTTP as follows: http://www.iana.org/time-zones/repository/releases/tzcode2016j.tar.gz http://www.iana.org/time-zones/repository/releases/tzdata2016j.tar.gz http://www.iana.org/time-zones/repository/releases/tzdb-2016j.tar.lz As usual, links to the latest release files are here: http://www.iana.org/time-zones/repository/tzcode-latest.tar.gz http://www.iana.org/time-zones/repository/tzdata-latest.tar.gz http://www.iana.org/time-zones/repository/tzdb-latest.tar.lz ftp://ftp.iana.org/tz/tzcode-latest.tar.gz ftp://ftp.iana.org/tz/tzdata-latest.tar.gz ftp://ftp.iana.org/tz/tzdb-latest.tar.lz Each release file has a GPG signature, which can be retrieved by appending ".asc" to the above URLs. Copies of these signatures are appended to this message. This release corresponds to commit eeff212d0f2b94a8c08d7ce2e1ff2278c027936b dated 2016-11-22 23:17:13 -0800 and tagged '2016j' in the experimental github repository at <https://github.com/eggert/tz>. Here are the SHA-512 checksums for the release files: cac19dded22ff80cd784641ac239358c28cce535ac1eb60b52b7e51c6e9e5fe5f795ea0252daf32c949dddb9c5b24d7e4456d7869aa2725d49c5af58b564822a tzcode2016j.tar.gz ce0b9958b764479fac7df6b5ba0933fc4c6d815ebccc2537c75c4be105691cd58054704eebfb50ca755d7d48504480d4925ce8836eb499ae4798e3d5503d7e0e tzdata2016j.tar.gz d6ea53bb23ebc1a41ae5ccfa198aec50b8c3836ee8e2dbe8ac0dd77b410884055df87fe9ca926aa8683c6593d2f08ce18b552cf5996d484b2a526c97c67f8419 tzdb-2016j.tar.lz Here are the GPG checksums for the release files: -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAABAgAGBQJYNUONAAoJEO2X6Q5iqn40TiAQAIepGbE9Wt41kBEuehf8LMfh 5qH25z0XDnETV88qofo+Eo8C1eFpueohL6xcHO3L1eCKSt+DJ/kphdvLJaFr+l6Q Kj6HisrJZxQcs8A98M29oydwZ9s9Zsu0igZQlmkhFgh9/NOnsuByoMwZpB0yGGaU zHd2O6hJEQt5IPimEmm7n7awwjzoUctNAjKQISHXApZqpSH14/cYKltwBeR4Up4r F8NmFIbrfstnETUSPPAJsvHntD+98gR7EfwoFYeCmmorDgD65Q5DxqpYuzt67upI Xd3rxD6UUmOmzJwmJ4sO/cEQuxim+kRrnGFOONlavtt1j7FUFRzL762bNpC94byj pMqJNUNy37L+uqucFEORLeqlLvfQA0GVHxcT508aACbht0QMmw5+qcY6rmjEKVqq AA7ZpxX1GhQyk4r7xUth4sMvJjG9ZHa7esv4Uq6lTAVx+IQu1M/kXD3VHfyV0Pb1 LJxz6btSA2PEJmHsFlZtxdp/sinvT2BItN5bBN0JU7lcINalKTBud61dCaa/bt5P 6lHeA6c8R023rHl6ZyHhL6MVME/7DhBKZO+ltbW42Oaul077joyHi8KbuWC4OB4Y 5WqkOI9slIqqwG7DN85uxkgKp4S0puxDDQbmfK4ndkJOSgWhb5ihdvATrvF/CBHZ JKSipGEJ35Sh56Z8qnT1 =L0s/ -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAABAgAGBQJYNUONAAoJEO2X6Q5iqn407TUP/Aib3PFeaTwL3/LnUliah908 GCckZElj1wCc5YwBSfJp3LuYq3OEBQez+EQgUU6TkbEmYhL0mw8le+JU7idI8k3G Qxsy2qKLpUfaLMyXxEsdwWMVIbazK5psEoX2HQna+/DG6oEsDYJ2L9TF4Vf7QVbk rmlqcezdKejOdKmiWz4ksD5VpfzL99ncLmSF+jTof/wuQheSJoGvTyhklVWdNxfj FMANsVXKhKFdajxr71pkehBqQOOGjyQyf4FcIaWDcDbnhKuew/z2JCXUOcymNGU2 bRp5fXawJTV8S7Q865npe5zBjf0exklRUhWp39W+LMwisKjO9sWOrIbgzQPkaqEG VCQq+TA8kDDH1fs4KB7v90DJjoZGLeFDSrfAsaEaFCQV6lwuDAFwFgaZ/tHgSdaC w6NnvD9kFM/1xKAi08kOHhDwyrcD8l12j17BKRS6JSEWo7h3dT7y74Mv6BIAfzLL TgiOperwW8076aVHYXM/7yc4i5pjqDGemJVp0iiZPQhm9zWR6IO3evIZ2zoi2xUw uSBF+p640JgZtVCKCYP3/wFmxdmnk+CcWX+k9LVcwErkXEn+YyREeD6uGsMlAyuB JSb0ea7FhMiazRjXTQLM4wjbBXVVfjfCyVNBB+vF3VBxw1bzxhP/zdhd6kujelH4 I3I4D5bwHXBuxh4ILLjg =05b3 -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAABAgAGBQJYNUONAAoJEO2X6Q5iqn40cWgQAJaQfb8jBiTlYU59s5s/Thh/ OO+pfNAJum2naV4WtCK/gsM/GayFrT3hlPo/ju9/haz05tz1Ejnlj7qxYe1t+HXp xFrm202OhTwn8aGrrITtvrdlQW/dgYyH6otx5wQ9xFe9MR+J9/CViaL7riY1thcg q9z4VbesRG3RSzsqq4NrnmXK2TY+YyV+kg0qf4Nb3O9k4lD5US+ArTZTxz5KGu42 QhllZrTKWN5fe10ME5v8WOsefrkJRhxqrqTbAS5iaNvuCVT40XWjMt8JstLJmdaq PnSGO0s7WoHRxqSpU9yiHA+YviGqPpp+W+CYap53AfzNAXsAT/4x9cqPlbvYgIwt ki6qzFEvK0qfUqTadDbykFBtvri7e8KsZj+zjyd75bdt+MVe4dpkGHhFLoUz6rD6 9trj+sUwLPZFhFAriBes0FduZ8iMi1c08kTzzePSuIkKlaZbhrKs6Focxo1DohB2 8ocCh8uUgkumwfBbcRuQ8HYZJsQLBLgFXYWz9612hNPGjX5EO7Jyyyux9qkEHLF+ upD08YpROhDsZ6XH4OYnAct1O3WL4xO5Vj/EJnyf1bhYglbjZkT4gDth3RnTqGlI tlQU9I7Yf4ZOi9Vv1Nr+TmlYEHZ6rH6u/sLR5MX9O2vRuY2KNh3uqOFxLqL2dOfq 3jbRBjzbPl/oUfEoaTC/ =3EO0 -----END PGP SIGNATURE----- _______________________________________________ tz-announce mailing list tz-announce(a)iana.org https://mm.icann.org/mailman/listinfo/tz-announce

1 0

Switching to DST in Australia could save Koalas
by Eliot Lear Nov. 23, 2016

Nov. 23, 2016

The problem isn't the Koalas telling time, but humans being on the road at certain times... http://www.latimes.com/science/sciencenow/la-sci-sn-daylight-savings-koalas…

1 0

[PATCH] * NEWS: Add "Briefly:" section.
by Paul Eggert Nov. 23, 2016

Nov. 23, 2016

--- NEWS | 2 ++ 1 file changed, 2 insertions(+) diff --git a/NEWS b/NEWS index 1682709..e018862 100644 --- a/NEWS +++ b/NEWS @@ -2,6 +2,8 @@ News for the tz database Unreleased, experimental changes + Briefly: Saratov, Russia moves from +03 to +04 on 2016-12-04. + Changes to future time stamps Saratov, Russia switches from +03 to +04 on 2016-12-04 at 02:00. -- 2.7.4

1 0

Re: [tz] Regarding Turkey DST change
by Brian Inglis Nov. 23, 2016

Nov. 23, 2016

On 2016-11-22 13:24, Meno Hochschild wrote: > Am 22.11.2016 um 19:06 schrieb Brian Inglis: >> On 2016-11-22 10:27, Paul Eggert wrote: >>> On 11/22/2016 03:18 AM, Peddi, Radhika (Radhika) wrote: >>>> I am using tzdata along with joda. >>> If the 'date' command works but Joda does not, it must be a Joda >>> problem and not a tzdata problem, so I suggest looking for Joda >>> support. http://www.joda.org/joda-time/ >> Joda runs on Java which has tzupdater problems, so the OP should >> read recent threads and the Oracle page on the Java tzupdater to >> update Java time zones and see correct time, update your JDK/JRE >> to a current release, or submit a TAR to Oracle support. >> Also the OP should note on the Joda page that the Joda API has >> been incorporated into the Java SE 8 java.time class and Joda >> time now deprecates using itself. > Two corrections: > a) Joda Time has nothing to do with tzupdater tool distributed by > Oracle but manages its own independent tz data repository which is > based on analysis of tzdb-sources. > b) The Joda API has NOT been incorporated into Java SE 8 but only > inspired it. Both APIs are really different. > If something with Joda tz-interpretation might be wrong then someone > could check it via Jon Skeets tz-validation-project. But I rather > suspect that there was an outdated Joda-version. The newest version > 2.9.6 is declared to support tzdb-version 2016i. Two problems: - one language product with two sources of time information - no wonder the OP is confused why their time is wrong: perhaps you could post how the OP can correct their Joda time, walk them thru difficulties that may be encountered in http://www.joda.org/joda-time/tz_update.html; - Joda time says the project is finished, and advises migration to Java SE 8 java.time, so it may not be reasonable to expect prompt future releases or tz updates. Like Adobe products, Java has become such a source of security holes and vulnerabilities requiring frequent updates, blocked by various products, that it's safer to uninstall them, eliminate the annoyances and vulnerabilities, and do without what they provide, or use alternatives that don't suffer the same issues. -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

1 0

[Russia] Saratov region is moving to UTC+4 at [preliminary] Nov 27, 2016
by Yuri Konotopov Nov. 22, 2016

Nov. 22, 2016

Hello. Today Russian Duma has approved in 1st read (of 3) Law project №1058438-6 that will move Saratov region to UTC+4. Project card: http://asozd2.duma.gov.ru/main.nsf/%28SpravkaNew%29?OpenAgent&RN=1058438-6&… Preliminary date of change is November 27, 2016. As I think new timezone "Europe/Saratov" should be created in tzdata. I will inform you as soon as President will approve Law project. -- Best regards, Yuri Konotopov

4 16

Re: [tz] Regarding Turkey DST change
by Paul Eggert Nov. 22, 2016

Nov. 22, 2016

On 11/22/2016 03:18 AM, Peddi, Radhika (Radhika) wrote: > I am using tzdata along with joda. If the 'date' command works but Joda does not, it must be a Joda problem and not a tzdata problem, so I suggest looking for Joda support. http://www.joda.org/joda-time/

2 1

Regarding Turkey DST change
by Peddi, Radhika (Radhika) Nov. 22, 2016

Nov. 22, 2016

Hi, Could you please tell me whether Turkey DST changes are fixed in tzdata or not? If fixed could you please let me know which tzdata*.tar.gz contains the changes? I have downloaded the latest one available on https://www.iana.org/time-zones. However still UTCOffString value showing as +2.00 instead of +3.00 for November dates. Thanks & Regards, Radhika Peddi|Avaya India Pvt. Ltd.| Wing 'A', Level -5, Tower-11, Cybercity, Magarpatta City, Hadapsar | Pune, 411028|India Voice +91 20 4101 8311| Email: rpeddi<mailto:rpeddi@avaya.com>@avaya.com [Please consider the environment before printing this email]|7 Switch off POWER |[cid:image008.jpg@01CD293C.65903AA0] Save Water |q RECYCLE |P PRESERVE trees |

4 7

[PATCH] Minor changes to iso3166.tab
by Jiri Bohac Nov. 17, 2016

Nov. 17, 2016

As noted in the file, the table intentionally differs from the ISO 3166 English names, mostly using even shorter names than the official short name. In a few cases, it seems to be out of sync with ISO for no good reason: Official changes in ISO, where new is same length or shorter than original: Cape Verde -> Cabo Verde Czech Republic -> Czechia UTF-8 now used elsewhere, so why not for Curaçao: Curacao -> Curaçao No good reason to differ from the standard?: Macau -> Macao Personally, I would also change "Britain" to "United Kingdom", I think it's where people would look first. But it would go from shorter to longer, so I did not include it in the patch. It's still much shorter than many other names. Would "United Kingdom" make sense here? --- iso3166.tab | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/iso3166.tab b/iso3166.tab index 7a8df2c..0e07afd 100644 --- a/iso3166.tab +++ b/iso3166.tab @@ -74,11 +74,11 @@ CN China CO Colombia CR Costa Rica CU Cuba -CV Cape Verde -CW Curacao +CV Cabo Verde +CW Curaçao CX Christmas Island CY Cyprus -CZ Czech Republic +CZ Czechia DE Germany DJ Djibouti DK Denmark @@ -170,7 +170,7 @@ MK Macedonia ML Mali MM Myanmar (Burma) MN Mongolia -MO Macau +MO Macao MP Northern Mariana Islands MQ Martinique MR Mauritania -- Jiri Bohac <jbohac(a)suse.cz> SUSE Labs, SUSE CZ

6 11

Hungary considers moving to +02 year-round
by Paul Eggert Nov. 17, 2016

Nov. 17, 2016

A bill to put Hungary on permanent EET (+02) has passed a parliament committee unanimously. The full parliament is scheduled to vote on it next week. Presumably this would require coordination with the EU, which may mean delays before the change would take effect. See: End of Hungaro-pessimism? - the times they are changing in the Hungarian Parliament. Hungary Today 2016-11-16. http://hungarytoday.hu/news/may-end-hungaro-pessimism-time-changing-questio… Horváth A. Vége az óraátállításnak? Magyar Nemzet 2016-11-16. http://mno.hu/gazdasag/vege-az-oraatallitasnak-1371621

1 0

Turkey ZoneInfo
by Sundeep Dasari Nov. 16, 2016

Nov. 16, 2016

Hi Iam trying to extract turkey zoneinfo from "tzdata2016i.tar.gz" package and is not successfully. I have done the following to extract turkey zone info: zic -d ./mytemp/ asia zic -d ./mytemp/ europe Turkey should be either in Europe or in Asia. Please provide me with your support in this regard. -- Thanks Sundeep.

3 2

tzdata2016g missing version information
by Howard Hinnant Nov. 12, 2016

Nov. 12, 2016

As is known, the version number no longer appears in the Makefile. The release notes in NEWS say: > To support the more-accurate version number, its > specification has moved from a line in the Makefile to a new > source file 'version’. The version file does not appear in the uncompressed tzdata2016g database. This is hurting my ability to report the version of the database to my clients. Can we please put a version file in the database? Howard

18 49

"impossible" glitch right at the DST changeover: it had to happen
by scs＠eskimo.com Nov. 11, 2016

Nov. 11, 2016

The mother in this story says she had a hard time "wrapping her head around it", but readers of this list will have little trouble: "Twins' Daylight Saving Time Birth Results in Bizarre Age Twist" http://abcnews.go.com/Lifestyle/twins-daylight-saving-time-birth-results-bi… Yes, one twin was born on the early morning of November 6 at 1:39, and his little brother was born 31 minutes later, at 1:10.

1 0

[PROPOSED] * CONTRIBUTING: Call the GitHub repository "development"
by Paul Eggert Nov. 11, 2016

Nov. 11, 2016

Instead of the old adjective "experimental". --- CONTRIBUTING | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/CONTRIBUTING b/CONTRIBUTING index e40102e..22addd2 100644 --- a/CONTRIBUTING +++ b/CONTRIBUTING @@ -18,10 +18,10 @@ data should contain commentary citing reliable sources as justification. Please submit changes against either the latest release in -<ftp://ftp.iana.org/tz/> or the master branch of the experimental -Git repository. If you use Git the following workflow may be helpful: +<ftp://ftp.iana.org/tz/> or the master branch of the development +repository. If you use Git the following workflow may be helpful: - * Copy the experimental repository. + * Copy the development repository. git clone https://github.com/eggert/tz.git cd tz -- 2.7.4

1 0

Re: [tz] tzdata2016g missing version information
by Dempsey, Peter Nov. 10, 2016

Nov. 10, 2016

Hi, On 09/29/2016 08:590 AM, Eggert, Paul wrote: >Yes, it appears that the Oracle software assumed that the Makefile would have a VERSION line that specifies the version number. That assumption was never documented or guaranteed and is no longer valid. >Perhaps you can work around the problem by modifying the Makefile to say "VERSION = 2016g" (I don't have the Oracle software and so can't easily test this). >We are discussing a better way to address this problem in the future. @Paul Eggert: The Oracle Timezone Update Tool can be downloaded from here: http://www.oracle.com/technetwork/java/javase/documentation/tzupdater-readm…. This tool has two ways of updating the timezone database: 1. Online where the timezone database is downloaded from: -l http://www.iana.org/time-zones/repository/tzdata-latest.tar.gz 2. Offline where the timezone database is loaded locally: -l file:///tmp/tzdata2016g.tar.gz The tzdata file published on the IANA site needs to include the VERSION information so that this tool can work. When do you think this can be provided? I need to test the Oracle Timezone Updater Tool as soon as possible because I have customers with critical systems dependent on the time zone database. @Susan Abraham: I don't know if you are involved with the Timezone Updater Tool but this tool currently can't update the timezone because the database doesn't contain the VERSION information. @Kim Davies: I am adding you to keep you directly in the loop. Best regards, Pete -- This electronic message may contain proprietary and confidential information of Verint Systems Inc., its affiliates and/or subsidiaries. The information is intended to be for the use of the individual(s) or entity(ies) named above. If you are not the intended recipient (or authorized to receive this e-mail for the intended recipient), you may not use, copy, disclose or distribute to anyone this message or any information contained in this message. If you have received this electronic message in error, please notify us by replying to this e-mail.

7 15

Danish Time not UTC
by Brian Inglis Nov. 10, 2016

Nov. 10, 2016

According to the DK NMI DANIAmet: https://daniamet.dk/en/nmi/time-and-frequency/ "The law on time (Law No 83, 29/03/1893) prescribe that the time in Denmark is determined by mean solar time and not the UTC time." -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

6 10

Failed to update tzdata2016g and higer with tzupdater
by Sawadee.Prakayphetchara＠thomsonreuters.com Nov. 9, 2016

Nov. 9, 2016

Hi, We found an issue when try to update timezone with the tzdata2016g.tar.gz - tzdata2016i.tar.gz The problem is that VERSION in the Makefile is not correct, the correct value should match with tz version i.e. 2016i not unknown. # Version number for the distribution, overridden in the 'tarballs' rule below. VERSION= unknown The workaround has been mention in, http://stackoverflow.com/questions/39832866/tzupdater-failing-with-tzdata20… * Update Makefile of http://www.iana.org/time-zones/repository/releases/tzdata2016g.tar.gz: Original value of VERSION variable is unknown and you need to update it to 2016g. * Regenerate tzdata2016g.tar.gz.sha512 file So far we need to apply the workaround on each release. It would be great if you can correct the version in next release? Regards, Sawadee M.

2 1

Timezones - what's so hard?
by Michael Douglass Nov. 7, 2016

Nov. 7, 2016

http://www.gocomics.com/pearlsbeforeswine#mutable_1511244

3 2

[PROPOSED] Port ar usage to POSIX
by Paul Eggert Nov. 7, 2016

Nov. 7, 2016

* Makefile (libtz.a): Use 'ar -rc' instead of 'ar ru', as 'ar -rc' is standardized by POSIX and GNU 'ar' 2.26.1 (Ubuntu 16.04.1) warns about the obsolete form 'ar ru'. --- Makefile | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/Makefile b/Makefile index 74b950c..1b714a8 100644 --- a/Makefile +++ b/Makefile @@ -542,7 +542,8 @@ force_tzs: $(TZS_NEW) cp $(TZS_NEW) $(TZS) libtz.a: $(LIBOBJS) - $(AR) ru $@ $(LIBOBJS) + rm -f $@ + $(AR) -rc $@ $(LIBOBJS) $(RANLIB) $@ date: $(DATEOBJS) -- 2.7.4

1 0

Compiler warning in tzcode2016g about SIZE_MAX being wider than int
by Tom Lane Nov. 6, 2016

Nov. 6, 2016

When trying to build 2016g using macOS's current compiler (or, probably, any reasonably late-model version of clang), I get cc -DTZDIR=\"/usr/local/etc/zoneinfo\" -c -o zic.o zic.c zic.c:434:51: warning: implicit conversion from 'unsigned long long' to 'int' changes value from 18446744073709551615 to -1 [-Wconstant-conversion] int amax = nitems_max < SIZE_MAX ? nitems_max : SIZE_MAX; ~~~~ ^~~~~~~~ /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.12.sdk/usr/include/stdint.h:153:20: note: expanded from macro 'SIZE_MAX' #define SIZE_MAX UINT64_MAX ^~~~~~~~~~ /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.12.sdk/usr/include/stdint.h:87:27: note: expanded from macro 'UINT64_MAX' #define UINT64_MAX 18446744073709551615ULL ^~~~~~~~~~~~~~~~~~~~~~~ 1 warning generated. Or in other words, clang is pointing out, quite correctly, that SIZE_MAX won't fit in an int. This doesn't represent a runtime bug because the condition "nitems_max < SIZE_MAX" can never fail, but that just begs the question why have it. I am not aware of any C implementation that has ever had INT_MAX > SIZE_MAX, and surely there are none in use today. I suggest, therefore, a fix along the lines of $ diff -u zic.c~ zic.c --- zic.c~ 2016-09-06 00:39:50.000000000 -0400 +++ zic.c 2016-10-20 13:06:39.000000000 -0400 @@ -431,8 +431,7 @@ return ptr; else { int nitems_max = INT_MAX - WORK_AROUND_QTBUG_53071; - int amax = nitems_max < SIZE_MAX ? nitems_max : SIZE_MAX; - if ((amax - 1) / 3 * 2 < *nitems_alloc) + if ((nitems_max - 1) / 3 * 2 < *nitems_alloc) memory_exhausted(_("int overflow")); *nitems_alloc = *nitems_alloc + (*nitems_alloc >> 1) + 1; return erealloc(ptr, size_product(*nitems_alloc, itemsize)); Alternatively one might think of changing the types of nitems_max and amax to size_t --- but that would just make it even more crystal clear that the "nitems_max < SIZE_MAX" conditional is useless. And if, somewhere, one did find a C implementation in which size_t is narrower than int, that coding wouldn't work at all. Basically I don't see a way of dealing with this that is superior to just assuming that INT_MAX is less than or equal to SIZE_MAX. regards, tom lane

4 8

Daylight saving in Trkey problem
by Caner Aydinbey Nov. 6, 2016

Nov. 6, 2016

Hello. We have linux machine and we have app in there. FOr date command, it shows true date but in spring boot application, we cant get true date. It iss 1 hour later. So we follow guides to update but we cant manage. for example here http://www.oracle.com/technetwork/java/javase/tzupdater-readme-136440.html#… Please suggest us something to do. -- Caner Aydin Software Developer Infoowl Software Solutions & Consultancy +90 542 788 62 64 <%2B90%20530%20960%2035%2053> www.infoowl.net

3 4

Tonga returns to DST on 2016-11-06
by Tim Parenti Nov. 6, 2016

Nov. 6, 2016

Tonga will observe DST from 2016-11-06 02:00 until 2017-01-15 03:00, in line with Fiji. http://mic.gov.to/news-today/press-releases/6375-daylight-saving-set-to-run… This came through as a pull request on the Github repo: https://github.com/eggert/tz/pull/19 Originally submitted patch and proposed follow-up attached. -- Tim Parenti

10 27

zic fails for soft-links-only target volume
by Tom Lane Nov. 4, 2016

Nov. 4, 2016

I received a complaint that zic recently started to fail when the target directory is on a volume that doesn't support hard links. (The complainant is using some weird VMware Fusion setup, but I think this might be true on Windows generally.) It used to go through just fine, creating symlinks instead, but as of 2016g it fails with something like ./zic: link from /home/postgres/testversion/share/timezone/US/Eastern failed: Operation not permitted It appears to me that the problem is that commit 35484e98c broke the case of linking to an existing symlink. This happened because itsdir() was modified to return 2 not 0 for a symlink, but dolink() throws an EPERM error for that, because it wasn't taught about the change. There's no reason to disallow that case, so I propose this patch: diff --git a/zic.c b/zic.c *** a/zic.c --- b/zic.c *************** dolink(char const *fromfield, char const *** 824,830 **** ** there's a fair chance of root running us. */ fromisdir = itsdir(fromfield); ! if (fromisdir) { char const *e = strerror(fromisdir < 0 ? errno : EPERM); fprintf(stderr, _("%s: link from %s/%s failed: %s\n"), progname, directory, fromfield, e); --- 824,830 ---- ** there's a fair chance of root running us. */ fromisdir = itsdir(fromfield); ! if (fromisdir < 0 || fromisdir == 1) { char const *e = strerror(fromisdir < 0 ? errno : EPERM); fprintf(stderr, _("%s: link from %s/%s failed: %s\n"), progname, directory, fromfield, e); BTW, you can test this behavior without needing to have such a volume at hand, by forcing the link() attempt to fail like this: *************** dolink(char const *fromfield, char const *** 840,845 **** --- 840,846 ---- progname, directory, tofield, e); exit(EXIT_FAILURE); } + staysymlink = true; // for testing purposes only!! link_errno = (staysymlink ? ENOTSUP : link(fromfield, tofield) == 0 ? 0 : errno); if (link_errno == ENOENT && !todirs_made) { regards, tom lane

2 7

Why did you rename Russian zone name abbreviations
by Sergei Turchanov Nov. 3, 2016

Nov. 3, 2016

Hello! https://github.com/eggert/tz/commit/1ac038c2c3f25f7211474ae08feb6afb820 e35fe Why did you rename Russian zone name abbreviations? Can you provide a rationale for this change? This change breaks date parsing, etc... With best regards, Sergei Turchanov.

9 22

[PROPOSED] Fix EEST typos in Palestine before 1948
by Paul Eggert Nov. 3, 2016

Nov. 3, 2016

* NEWS: Document this. * asia (Asia/Gaza, Asia/Hebron): Fix typos, to use "EEST" instead of "EET" when abbreviating summer time before 1948. --- NEWS | 8 ++++++++ asia | 4 ++-- 2 files changed, 10 insertions(+), 2 deletions(-) diff --git a/NEWS b/NEWS index da5c2a5..db9f03d 100644 --- a/NEWS +++ b/NEWS @@ -1,5 +1,13 @@ News for the tz database +Unreleased, experimental changes + + Changes to past time zone abbreviations + + Asia/Gaza and Asia/Hebron now use "EEST", not "EET", to denote + summer time before 1948. The old use of "EET" was a typo. + + Release 2016i - 2016-11-01 23:19:52 -0700 Briefly: Cyprus split into two time zones on 2016-10-30, and Tonga diff --git a/asia b/asia index 67164b3..bb7534a 100644 --- a/asia +++ b/asia @@ -2616,7 +2616,7 @@ Rule Palestine 2016 max - Oct lastSat 1:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Gaza 2:17:52 - LMT 1900 Oct - 2:00 Zion EET 1948 May 15 + 2:00 Zion EET/EEST 1948 May 15 2:00 EgyptAsia EE%sT 1967 Jun 5 2:00 Zion I%sT 1996 2:00 Jordan EE%sT 1999 @@ -2629,7 +2629,7 @@ Zone Asia/Gaza 2:17:52 - LMT 1900 Oct 2:00 Palestine EE%sT Zone Asia/Hebron 2:20:23 - LMT 1900 Oct - 2:00 Zion EET 1948 May 15 + 2:00 Zion EET/EEST 1948 May 15 2:00 EgyptAsia EE%sT 1967 Jun 5 2:00 Zion I%sT 1996 2:00 Jordan EE%sT 1999 -- 2.7.4

1 0

Re: [tz] Why did you rename Russian zone name abbreviations
by Paul Eggert Nov. 3, 2016

Nov. 3, 2016

On 11/02/2016 08:50 AM, turchanov(a)vl.ru wrote: > ... having "date" command output "Wed Nov 2 09:54:58 +10 2016" make > it very difficult to understand where the system is. That's fine, as the "date" command is supposed to be about *when*, not about *where*. > 2. Since the inception of tzdata Olson stated rules for abbreviated > names clearly and unambiguously > (https://github.com/eggert/tz/blob/master/Theory) That old guideline has been deprecated, as mentioned in the Theory file. > 3. I have an impression that you (un-)intentionally confuse an > abbreviated name with a GMT offset. No, the idea is that if there is no common English-language abbreviation for a time zone, tzdata uses a numeric abbreviation instead. > > if one needed a GMT offset it would have used %z-family flags. The problem is not that software needs a GMT offset. It's that software unwisely requires a time zone abbreviation even when no such abbreviation exists in common English-language practice. Although we could simply leave the abbreviation empty in this case, it's more useful to fill it with a placeholder that conveys information to users of applications that unwisely output the abbreviation as-is. > By changing the abbreviated zone name you in effect change the > original full zone name. Why didn't change Asia/Vladivostok to > Asia/+10 as well?! That wouldn't work, as Vladivostok was at +11 before 2014, and at +09 before 2011. Even in the US, where alphabetic time zone abbreviations are common, we wouldn't link America/Indiana/Petersburg to US/Eastern, because Petersburg observed Central Time before 2007. > > 5. You justify your decision to remove abbreviated names by declaring > them as an "invention". Yes. I invented these abbreviations. I didn't use any formal procedure. The (now-deprecated) guideline about them in the Theory file was written after the fact, partly in an attempt to justify them. When I invented those abbreviations, POSIX supported only alphabetic-only abbreviations. Also, I was naive about Russia: I thought that it kept time zones like the US does and that US-style alphabetic abbreviations therefore made sense for it. Nowadays, though, POSIX allows numeric abbreviations, and I know more about Russian practice. From an English-speaking point of view, abbreviations like VLAT are misleading because they imply that there is a time zone at a fixed offset from UTC called "VLAT", which is how abbreviations like "PST", "GMT", and "CET" work. However, abbreviations like "VLAT" do not correspond to fixed UTC offsets, and this is something that English-speakers are typically not expecting or accustomed to. So even if "VLAT" were widely used by Russian speakers, it would still be dubious as an abbreviation in English-language tzdata. I agree that the current situation could be improved, and that there could be a better way to localize time zone abbreviations. I expect this is an effort that should be under the CLDR umbrella, as they're the localization gurus. It may be that we need a better API for getting at localized abbreviations. Certainly the tzcode strftime.c is incomplete here, as it doesn't even support Russian month names, much less genitive-case Russian dates (does CLDR handle that correctly? if not, it should...).

6 10

Latest tzdata2016
by Raymond Kumar Nov. 3, 2016

Nov. 3, 2016

Hi I would like to have a latest patch for tzdata. There were some changes performed on Tonga time zone and we need this patch as Tonga DST is from this week 5th November and we would like to apply this patch on systems. Thanks, Raymond Kumar Head of Billing & Products +6797015315 ________________________________ Notice of Confidentiality: The information contained in this communication is intended solely for the use of the individual or entity to whom it is addressed and others authorized to receive it. It may contain confidential or legally privileged information. If you are not the intended recipient you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this information is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by responding to this email and then delete it from your system.

2 1

[tz-announce] 2016i release of tz code and data available
by Paul Eggert Nov. 3, 2016

Nov. 3, 2016

The 2016i release of the tz code and data is available. It reflects the following changes, which were either circulated on the tz mailing list or are relatively minor technical or administrative changes: Briefly: Cyprus split into two time zones on 2016-10-30, and Tonga reintroduces DST on 2016-11-06. Changes to future time stamps Pacific/Tongatapu begins DST on 2016-11-06 at 02:00, ending on 2017-01-15 at 03:00. Assume future observances in Tonga will be from the first Sunday in November through the third Sunday in January, like Fiji. (Thanks to Pulu ʻAnau.) Switch to numeric time zone abbreviations for this zone. Changes to past and future time stamps Northern Cyprus is now +03 year round, causing a split in Cyprus time zones starting 2016-10-30 at 04:00. This creates a zone Asia/Famagusta. (Thanks to Even Scharning and Matt Johnson.) Antarctica/Casey switched from +08 to +11 on 2016-10-22. (Thanks to Steffen Thorsen.) Changes to past time stamps Several corrections were made for pre-1975 time stamps in Italy. These affect Europe/Malta, Europe/Rome, Europe/San_Marino, and Europe/Vatican. First, the 1893-11-01 00:00 transition in Italy used the new UT offset (+01), not the old (+00:49:56). (Thanks to Michael Deckers.) Second, rules for daylight saving in Italy were changed to agree with Italy's National Institute of Metrological Research (INRiM) except for 1944, as follows (thanks to Pierpaolo Bernardi, Brian Inglis, and Michael Deckers): The 1916-06-03 transition was at 24:00, not 00:00. The 1916-10-01, 1919-10-05, and 1920-09-19 transitions were at 00:00, not 01:00. The 1917-09-30 and 1918-10-06 transitions were at 24:00, not 01:00. The 1944-09-17 transition was at 03:00, not 01:00. This particular change is taken from Italian law as INRiM's table, (which says 02:00) appears to have a typo here. Also, keep the 1944-04-03 transition for Europe/Rome, as Rome was controlled by Germany then. The 1967-1970 and 1972-1974 fallback transitions were at 01:00, not 00:00. Changes to code The code should now be buildable on AmigaOS merely by setting the appropriate Makefile variables. (From a patch by Carsten Larsen.) Here are links to the release files: ftp://ftp.iana.org/tz/releases/tzcode2016i.tar.gz ftp://ftp.iana.org/tz/releases/tzdata2016i.tar.gz ftp://ftp.iana.org/tz/releases/tzdb-2016i.tar.lz The files are also available via HTTP as follows: http://www.iana.org/time-zones/repository/releases/tzcode2016i.tar.gz http://www.iana.org/time-zones/repository/releases/tzdata2016i.tar.gz http://www.iana.org/time-zones/repository/releases/tzdb-2016i.tar.lz As usual, links to the latest release files are here: http://www.iana.org/time-zones/repository/tzcode-latest.tar.gz http://www.iana.org/time-zones/repository/tzdata-latest.tar.gz http://www.iana.org/time-zones/repository/tzdb-latest.tar.lz ftp://ftp.iana.org/tz/tzcode-latest.tar.gz ftp://ftp.iana.org/tz/tzdata-latest.tar.gz ftp://ftp.iana.org/tz/tzdb-latest.tar.lz Each release file has a GPG signature, which can be retrieved by appending ".asc" to the above URLs. Copies of these signatures are appended to this message. This release corresponds to commit 9774c293b7ea6ec7be851cb0b2a0807840e6793e dated 2016-11-01 23:19:52 -0700 and tagged '2016i' in the experimental github repository at <https://github.com/eggert/tz>. Here are the SHA-512 checksums for the release files: 93be791491a76f9d489f4bce8b392b2af6bdfb9a21f7efb7c6948da5c27db9782f7a725dd53d755e9488de000a4af5b75de650e7dac8c01ef8fbbd2719f9cd07 tzcode2016i.tar.gz 801059f43c91798cf69fb2ae77c1ffab8d06987325081511d573febde19ae423e7432c2b65c7c256077bbdb1b359e010302955786e18f2697bb263c4e0f1cc91 tzdata2016i.tar.gz 7e71521ed61ae2aca941b88c6308f3e6f90dc3356fef323c15b6907aefb827c11d19e2516b07c205f0365be736fbce3023bb9717a6a6a50964584b3f7b3baa81 tzdb-2016i.tar.lz Here are the GPG checksums for the release files: -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAABAgAGBQJYGYaQAAoJEO2X6Q5iqn402R0P/3AMlJCx/gABznqJhidPNCph dQikzUgHZaYyMNHdUYmxVV8gxjopMrFhKdJPalnb2mUcekAthc6h13TpDFvo0xKJ plBDNvA1hFXuHgLBrEJbtABFEIWLplfSJREAlvu41/OdtmXKnKINcg9pVD9Xm2hT TRWQVTXEc3wOFxGctfefXfGmyGK4Fc1UI2dYM8sS22pJrXeFrHZmJOfxL7r06qtM TSyDlL2o43V1i3IQVhwgkTKE8Q8cxOZVGqFjUu4urWGYIyK4x2ap0ZYaEqLeYBgx qzdTrINYIiSG5Qr9g/Uf4hNQ0fH2Vif+GaJOVCAJet+DL3Rj32hKLJC0x3L4+xx3 KmlYGOGh869kWu8h2qu/2ac4b0657SchgCx9BrZZ5m/bVYQeqOKLU5b2g/WLILv8 Tj0UPQqB6Lj0wzdSwUZN8V20nUaaQmoDpMDrt8/oZ5pwGCUSigLPPINu4Po6Iiyk leHfnAZj28xEoeJI77O2DJ4HO9nz8XvtOQUMxvixLvcIiLhUpeKFwrF+B5TXtOzZ pQ3M/pON7DytxM36ykArTwj7Pct+uwOJbkIVUIAdVE/cXmtlLR2f1VC6DQhO8x4N aaeKIXEYVioWCDWETi+OUWUyd+A2Fn0ykls6oGwhCdeHAeTRINsTesoBoQbh6/i4 1f6Fg4z5hNUZZyYfwp/j =V12P -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAABAgAGBQJYGYaQAAoJEO2X6Q5iqn40uykQAIlYwx+ZXwTh7f5GncBFvbkB A+zrwU2qFqLqy2ikyccUcs6LXbdxw5q9xb1pT1AEt7nKGqK2n7EF4TtbnYTLPijr e/A9WWzDozBDl4ExyG8TH/Zz8KcwPhbX9oq6+he7KYN2FwLwj/JEKWfp7esAsjqa CvMFGElUQMnRtv6PGfjYifU+5BYf0K6VhJ+iPpfb7NHiAEMBztt0mIlWKNB/hxuD 4ucWsr+k32NdlKgfxTDwfcEq9hd4wMmYfaTmxi1JUYmZ2UUr/ofns5VNYn4LKYz4 l7tN5cITS01fbcb/lYMMdeKnurxpNXvhjFiYJvCUGo1/ZOxBrUSF76JvjqLhKECw tD69X4zWEuAdgFIJfnpK7PAquW9YpkYhyeGLGvYQxIQTZVTRnyxlVJGFMinD2XFT /yjDMZDsdGReN0oTkxJ/vTnh45lNezBs9JJ2Quuxe/ZvT6ujRqK0yGSReYhpiKzz 6CS9PS5Ojgo0mvKJszccKgxu8nYAL3Odfr8CuVnWPPbhHBzM2TKQU9aXeJa7Nd6t MZZD6fp2qEFUd9qGRdz3E8UYSGCIYJfm85lx/DjxHiLQWdglfvwdGx4b3fsbCoKy iOUChS+12qShRHreKcNOnkaRe18J+5/unN3uh6aJoXmoCGbjcYjSIl5kF5Mb/iaN Fb0MCCcov7527m9ZVHNp =O/rc -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAABAgAGBQJYGYaQAAoJEO2X6Q5iqn40P7YQALUKbftldhSEHGo7WcQFBqO4 oKF3KbnbxgU1kKS3sMPjM2WfFbPSGotBZwAmRiJSuAhCQuT7IOdzlnH0A+gNHv1F SOz/w7qJPDPOze9hxy9oVLHK7kz2NsIqLoCQUKb48Bo/6CakhQXf0Bh/OgsAYCUe DtXk7AEJvRRb3V5z448cUqjPCW55zIEdiG7hC23rRQr4ETnCU5rfMXDLGD176NQl wm8uWGClqqPIFG1T5G9I3yKUZemlTjPi6dCRFWtCzGM1yKhCXceAA2OBx//LG8K2 nOhDwUwNMXdh7hRPMQQq/tbP1etkeNopMCQU+z0+eNGPR26IsWL3ouEAKO0j6DKy 1NoykCXjEZV0V8dNxU0mPWZ+oESbxgSML3FDlMPsuDar40eTTLpz3kg7aAb+fxTB FgL+HD3LPalOfIu/BM494EwggCsM3waAjRvhASNguWCOxGQVDQTVQoASpyPlyw2X d3Sdpot0o0ed998lDEFAvBOILW19lTDxgHYBKMTK8McE/UW/UGFHliH1oxFz+H1g kyMlJ7LWYaFN+G1p4qo6+LHddUa4hl50x8QYv3FZe6q5UOGEB7qMQq/40mMtFQWU yuvL/bmPqeYgsp3slZM9t/trzxwIDYe+S4508tn+6zQ0Ddg37COXoLvozGFI8g7R cqjLOztN8+7qZcotVR88 =BqkM -----END PGP SIGNATURE----- _______________________________________________ tz-announce mailing list tz-announce(a)iana.org https://mm.icann.org/mailman/listinfo/tz-announce

1 0

[PROPOSED PATCH] Cyprus is splitting into two time zones
by Paul Eggert Nov. 2, 2016

Nov. 2, 2016

Add a zone Asia/North_Nicosia for North Cyprus. * NEWS: Document this. * asia, zone.tab, zone1970.tab (Asia/North_Nicosia): New zone. --- NEWS | 5 +++-- asia | 11 ++++++++++- zone.tab | 3 ++- zone1970.tab | 3 ++- 4 files changed, 17 insertions(+), 5 deletions(-) diff --git a/NEWS b/NEWS index a4af3b2..64233bf 100644 --- a/NEWS +++ b/NEWS @@ -5,8 +5,9 @@ Unreleased, experimental changes Changes to future time stamps Turkey switched from EET/EEST (+02/+03) to permanent +03, - effective 2016-09-07. (Thanks to Burak AYDIN.) Use "+03" rather - than an invented abbreviation for the new time. + effective 2016-09-07. (Thanks to Burak AYDIN.) Northern Cyprus + followed suit the next day, which creates a zone Asia/North_Nicosia. + Use "+03" rather than an invented abbreviation for the new time. New leap second 2016-12-31 23:59:60 UTC as per IERS Bulletin C 52. (Thanks to Tim Parenti.) diff --git a/asia b/asia index e285326..4462cd4 100644 --- a/asia +++ b/asia @@ -773,6 +773,12 @@ Zone Asia/Macau 7:34:20 - LMT 1912 Jan 1 # Cyprus # # Milne says the Eastern Telegraph Company used 2:14:00. Stick with LMT. +# IATA SSIM (1998-09) has Cyprus using EU rules for the first time. +# +# From Paul Eggert (2016-09-09): +# Yesterday's Cyprus Mail reports that Northern Cyprus followed Turkey's +# lead and switched from +02/+03 to +03 year-round. +# http://cyprus-mail.com/2016/09/08/two-time-zones-cyprus-turkey-will-not-tur… # # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S Rule Cyprus 1975 only - Apr 13 0:00 1:00 S @@ -788,7 +794,10 @@ Rule Cyprus 1981 1998 - Mar lastSun 0:00 1:00 S Zone Asia/Nicosia 2:13:28 - LMT 1921 Nov 14 2:00 Cyprus EE%sT 1998 Sep 2:00 EUAsia EE%sT -# IATA SSIM (1998-09) has Cyprus using EU rules for the first time. +Zone Asia/North_Nicosia 2:13:27 - LMT 1921 Nov 14 + 2:00 Cyprus EE%sT 1998 Sep + 2:00 EUAsia EE%sT 2016 Sep 8 + 3:00 - +03 # Classically, Cyprus belongs to Asia; e.g. see Herodotus, Histories, I.72. # However, for various reasons many users expect to find it under Europe. diff --git a/zone.tab b/zone.tab index bf1bb71..15989f4 100644 --- a/zone.tab +++ b/zone.tab @@ -152,7 +152,8 @@ CU +2308-08222 America/Havana CV +1455-02331 Atlantic/Cape_Verde CW +1211-06900 America/Curacao CX -1025+10543 Indian/Christmas -CY +3510+03322 Asia/Nicosia +CY +3510+03322 Asia/Nicosia Cyprus (most areas) +CY +3511+03322 Asia/North_Nicosia North Cyprus CZ +5005+01426 Europe/Prague DE +5230+01322 Europe/Berlin Germany (most areas) DE +4742+00841 Europe/Busingen Busingen diff --git a/zone1970.tab b/zone1970.tab index 49f0b0b..efe27b1 100644 --- a/zone1970.tab +++ b/zone1970.tab @@ -144,7 +144,8 @@ CU +2308-08222 America/Havana CV +1455-02331 Atlantic/Cape_Verde CW,AW,BQ,SX +1211-06900 America/Curacao CX -1025+10543 Indian/Christmas -CY +3510+03322 Asia/Nicosia +CY +3510+03322 Asia/Nicosia Cyprus (most areas) +CY +3511+03322 Asia/North_Nicosia North Cyprus CZ,SK +5005+01426 Europe/Prague DE +5230+01322 Europe/Berlin Germany (most areas) DK +5540+01235 Europe/Copenhagen -- 2.7.4

11 23

Re: [tz] Cyprus is splitting into two time zones
by Evan Siroky Nov. 2, 2016

Nov. 2, 2016

Regarding the buffer zone, according to this Wikipedia Article (https://en.wikipedia.org/wiki/United_Nations_Buffer_Zone_in_Cyprus) "Turkish forces built a barrier on the zone's northern side". So maybe everything north of the buffer zone would be considered Asia/Famagusta and the whole buffer zone plus south of the buffer zone would be Asia/Nicosia.

1 0

www.timeanddate.com provides different data
by Gintare Statkute Nov. 2, 2016

Nov. 2, 2016

Dear sir/madam On this website i find the following data: https://www.timeanddate.com/time/zone/uk/london 2015Sun, 29 Mar, 01:00GMT <https://www.timeanddate.com/time/zones/gmt> → BST <https://www.timeanddate.com/time/zones/bst>+1 hour (DST start)UTC+1h Sun, 25 Oct, 02:00BST <https://www.timeanddate.com/time/zones/bst> → GMT <https://www.timeanddate.com/time/zones/gmt>-1 hour (DST end) <https://www.timeanddate.com/news/time/europe-dst-end-2015.html>UTC 2016 Sun, 27 Mar, 01:00GMT <https://www.timeanddate.com/time/zones/gmt> → BST <https://www.timeanddate.com/time/zones/bst>+1 hour (DST start) <https://www.timeanddate.com/news/time/europe-starts-dst-2016.html>UTC+1h Sun, 30 Oct, 02:00BST <https://www.timeanddate.com/time/zones/bst> → GMT <https://www.timeanddate.com/time/zones/gmt>-1 hour (DST end) <https://www.timeanddate.com/news/time/eu-debate-dst.html>UTC 2017 Sun, 26 Mar, 01:00GMT <https://www.timeanddate.com/time/zones/gmt> → BST <https://www.timeanddate.com/time/zones/bst>+1 hour (DST start)UTC+1h Sun, 29 Oct, 02:00BST <https://www.timeanddate.com/time/zones/bst> → GMT <https://www.timeanddate.com/time/zones/gmt>-1 hour (DST end)UTC 2018 Sun, 25 Mar, 01:00GMT <https://www.timeanddate.com/time/zones/gmt> → BST <https://www.timeanddate.com/time/zones/bst>+1 hour (DST start)UTC+1h Sun, 28 Oct, 02:00BST <https://www.timeanddate.com/time/zones/bst> → GMT <https://www.timeanddate.com/time/zones/gmt>-1 hour (DST end)UTC 2019 Sun, 31 Mar, 01:00GMT <https://www.timeanddate.com/time/zones/gmt> → BST <https://www.timeanddate.com/time/zones/bst>+1 hour (DST start)UTC+1h Sun, 27 Oct, 02:00BST <https://www.timeanddate.com/time/zones/bst> → GMT <https://www.timeanddate.com/time/zones/gmt>-1 hour (DST end)UTC As you can see, the Europe/London time change rule is different every year . But i can not find this information on yor data distribution. https://www.iana.org/time-zones For europe, london you give: # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/London -0:01:15 - LMT 1847 Dec 1 0:00s 0:00 GB-Eire %s 1968 Oct 27 1:00 - BST 1971 Oct 31 2:00u 0:00 GB-Eire %s 1996 0:00 EU GMT/BST Maybe i do not understand how to use your data? I put the question on stackoverflow: http://stackoverflow.com/questions/40360032/iana-internet-assigned-numbers-… regards, -- *Gintare Statkute*

4 3

[PATCH] Minor web page updates
by Paul Eggert Nov. 2, 2016

Nov. 2, 2016

* tz-art.htm (Comics): Add xkcd 1179. * tz-link.htm: Remove link to gmane, which no longer works. Update other links. Mention RFC 5905. --- tz-art.htm | 3 ++- tz-link.htm | 10 ++++------ 2 files changed, 6 insertions(+), 7 deletions(-) diff --git a/tz-art.htm b/tz-art.htm index 0a2b427..8ec9e21 100644 --- a/tz-art.htm +++ b/tz-art.htm @@ -438,7 +438,8 @@ Supernaw.</td></tr> The webcomic <em>xkcd</em> has the strip "<a href='http://xkcd.com/673/'>The Sun</a>" (2009-12-09) and the panels "<a href='http://xkcd.com/1017/'>Backward in Time</a>" (2012-02-14), -"<a href='http://xkcd.com/1061/'>EST</a>" (2012-05-28), and +"<a href='http://xkcd.com/1061/'>EST</a>" (2012-05-28), +"<a href='http://xkcd.com/1179/'>ISO 8601</a>" (2013-02-27), "<a href='http://xkcd.com/1335/'>Now</a>" (2014-02-26), and "<a href='http://xkcd.com/1655/'>Doomsday Clock</a>" (2016-03-14). The related book <em>What If?</em> has an entry diff --git a/tz-link.htm b/tz-link.htm index 088ba2d..aec8a1c 100644 --- a/tz-link.htm +++ b/tz-link.htm @@ -10,7 +10,7 @@ content="Sources for time zone and daylight saving time data"> <meta name="DC.Creator" content="Eggert, Paul"> <meta name="DC.Contributor" content="Olson, Arthur David"> -<meta name="DC.Date" content="2016-10-21"> +<meta name="DC.Date" content="2016-11-01"> <meta name="DC.Description" content="Sources of information about time zones and daylight saving time"> <meta name="DC.Identifier" @@ -158,9 +158,7 @@ The <code><abbr>tz</abbr></code> code and data are by no means authoritative. If you find errors, please send changes to the <a href="mailto:tz@iana.org">time zone mailing list</a>. You can also <a -href="http://news.gmane.org/gmane.comp.time.tz">browse recent -messages</a> sent to the mailing list, <a -href="https://mm.icann.org/mailman/listinfo/tz">subscribe</a> to it, +href="https://mm.icann.org/mailman/listinfo/tz">subscribe</a> to it and browse the <a href="http://mm.icann.org/pipermail/tz/">archive of old messages</a>.</p> @@ -736,7 +734,7 @@ href="https://www.polyomino.org.uk/british-time/">History of legal time in Britain</a> discusses in detail the country with perhaps the best-documented history of clock adjustments. The National Physical Laboratory also maintains an <a -href="http://www.npl.co.uk/educate-explore/what-is-time/archive-of-summer-time-da…">Archive +href="http://www.npl.co.uk/educate-explore/what-is-time/archive-of-summer-time-da…">Archive of Summer time dates</a>.</dd> <dt>United States</dt> <dd>The Department of Transportation's <a @@ -751,7 +749,7 @@ Science of Timekeeping</a> is a thorough introduction to the theory and practice of precision timekeeping.</li> <li><a href="http://www.ntp.org"><abbr title="Network Time Protocol">NTP</abbr>: The Network -Time Protocol</a> +Time Protocol</a> (Internet <abbr>RFC</abbr> 5905) discusses how to synchronize clocks of Internet hosts.</li> <li>The <a -- 2.7.4

1 0

Set up correct name to Zone Europe/Kyiv
by Alexey Furashev Oct. 31, 2016

Oct. 31, 2016

Hello All, In source file https://github.com/eggert/tz/blob/master/europe please change city name to correspondent standards ISO 3166-2:UA and UNGEGN. We have to write bug reports to software developers, because time zone entry names are incorrect. Incorrect name of time zone entries can't be used for our practical needs. ------------- str: 3663 from 'Zone Europe/Kiev' to 'Zone Europe/Kyiv' # ISO city code is UA-30 (https://www.iso.org/obp/ui/#iso:code:3166:UA ) ------------- str: 3691 from 'Zone Europe/Zaporozhye' to 'Zone Europe/Zaporizhzhia' ------------- Rules transliteraion from Ukranian to Latin see on site http://zakon4.rada.gov.ua/laws/show/55-2010-%D0%BF On-line service transliteration: https://dmsu.gov.ua/transliteration.html Oleksii. Kyiv.

2 1

Casey time zone change
by Steffen Thorsen Oct. 30, 2016

Oct. 30, 2016

Australian Antarctica Division informed us that Casey changed time zone to UTC+11 in "the morning of 22nd October 2016". The other Antarctic stations were not changed. Best regards, Steffen Thorsen - timeanddate.com

2 1

EU Parliament debates DST
by Matt Johnson Oct. 28, 2016

Oct. 28, 2016

Yesterday there was an extensive debate in the European Union Parliament concerning daylight saving time. The recordings and text are available here: http://www.europarl.europa.eu/plenary/en/debate-details.html?date=20161027&… Expand the section titled: "15:04 - 16:05 Switch between summer and winter time (debate)" My favorite is the passionate argument made by Indrek Tarand, MEP from Estonia, at 15:34:21. Though I'm not sure his history is quite so accurate. ;-) Thanks to http://www.timeanddate.com/news/time/eu-debate-dst.html for the heads up. -Matt

2 1

Historical discrepancies for Italy.
by Pierpaolo Bernardi Oct. 27, 2016

Oct. 27, 2016

Hello, about Italian time, I see: # From Paul Eggert (2006-03-22): # For Italian DST we have three sources: Shanks & Pottenger, Whitman, and # F. Pollastri # Day-light Saving Time in Italy (2006-02-03) # http://toi.iriti.cnr.it/uk/ienitlt.html # ('FP' below), taken from an Italian National Electrotechnical Institute # publication. When the three sources disagree, guess who's right, as follows: I don't know about the other sources, but: - the url given to cnr.it is dead. - The authoritative source for time in Italy is the national metrological institute, which has a summary page of historical DST data at http://www.inrim.it/res/tf/ora_legale_i.shtml - Some of the data in TZ does not agree with this page. I think that there must be VERY strong evidence that the INRIM is wrong before preferring other sources? Cheers

7 16

time update
by Tauʻolunga komipiuta Oct. 27, 2016

Oct. 27, 2016

Malo e lelei, people Are you already aware of the Tongan government's decision to introduce summertime? http://www.pmo.gov.to/daylight-saving-set-to-run-from-6-november-2016-to-15… Please update the tz database if you have not already done so. ʻOfa atu, Firitia >> Tauʻolunga komipiuta limited, Apple authorised reseller >> p.o.box 3060, Nukuʻalofa, Tonga >> Salote road, Fasi & afi; tel: 24828; fax: (+676)-24868, web: www.tau.olunga.to & facebook.tau.olunga.to

2 1

[PATCH] Introduce Epoch offset and local time Epoch
by Carsten Larsen Oct. 26, 2016

Oct. 26, 2016

--- localtime.c | 22 +++++++++++++++++++++- 1 file changed, 21 insertions(+), 1 deletion(-) diff --git a/localtime.c b/localtime.c index 6c00c45..3465248 100644 --- a/localtime.c +++ b/localtime.c @@ -58,6 +58,15 @@ static void unlock(void) { } #define OPEN_MODE O_RDONLY #endif /* !defined O_BINARY */ +/* +** AmigaOS Epoch is local time January 1, 1978 +*/ + +#ifdef AMIGAOS +#define TZEPOCH_OFFSET -252460800 +#define TZLOCAL_EPOCH 1 +#endif /* defined AMIGAOS */ + #ifndef WILDABBR /* ** Someone might make incorrect use of a time zone abbreviation: @@ -118,6 +127,12 @@ struct lsinfo { /* leap second information */ #ifndef TZNAME_MAX #define MY_TZNAME_MAX 255 #endif /* !defined TZNAME_MAX */ +#ifndef TZEPOCH_OFFSET +#define TZEPOCH_OFFSET 0 +#endif /* !defined TZEPOCH_OFFSET */ +#ifdef TZLOCAL_EPOCH +#define ALTZONE 1 +#endif /* defined TZLOCAL_EPOCH */ struct state { int leapcnt; @@ -2262,7 +2277,12 @@ posix2time(time_t t) time_t time(time_t *p) { - time_t r = sys_time(0); + time_t r = sys_time(0) + TZEPOCH_OFFSET; +#ifdef TZLOCAL_EPOCH + if(lcl_is_set) { + r += (!daylight ? timezone : altzone); + } +#endif if (p) *p = r; return r; -- 2.7.4

4 12

Balearics: Institutional declaration in favor of keeping the summer time
by Martin Kaistra Oct. 25, 2016

Oct. 25, 2016

Hello, According to https://www.theguardian.com/world/2016/oct/24/happy-hour-balearics-try-to-k… the Balearic Parliament will ask the central government to stay on summer time. Even though I don't think that this is happening this year, it might still be of interest to you. Parliament website (in Catalan?): http://www.parlamentib.es/webdocs/NoticiaPIB.aspx?id=2031 martin

1 0

Crimea time zone name
by Ilya Dogolazky Oct. 23, 2016

Oct. 23, 2016

Hello! According to Wikipedia the biggest city of Crimea is not Simferopol (2014 population: 332,317 [1]), because Sevastopol is a larger one (2016 population: 418,987 [2]). According to "Crimea" article, Sevastopol indeed is the biggest city of Crimea [3]. Is there any reason why the Crimea zone name is Europe/Simferopol and there is neither Europe/Sevastopol zone nor a symlink. Cheers, Ilya D. [1] https://en.wikipedia.org/wiki/Simferopol [2] https://en.wikipedia.org/wiki/Sevastopol [3] https://en.wikipedia.org/wiki/Crimea

2 1

Re: [tz] DST in the Netherlands before 1945
by Paul Eggert Oct. 21, 2016

Oct. 21, 2016

Thanks for spotting that typo. I installed the attached fix into the development repository.

1 0

Gwillim Law
by Paul Eggert Oct. 21, 2016

Oct. 21, 2016

I recently found out about Gwillim Law's passing by reading his family's web page <http://statoids.com/mgtletter.html>. Gwillim was a long time contributor to the tz project. He is credited in dozens of places, ranging from a 1993 decoding of entries for Tocantins in the International Air Transport Association's Standard Schedules Information Manual, to a 2015 translation of an article about a new time zone for Quintana Roo. Although I never met Gwillim in person, his expert, careful, and warm presence on the tz mailing list will be greatly missed. My condolences to his friends and family.

1 0

[tz-announce] 2016h release of tz code and data available
by Paul Eggert Oct. 20, 2016

Oct. 20, 2016

The 2016h release of the tz code and data is available. Its primary motivation is to update to the new rules for Palestine, where 2016g becomes incorrect starting about four hours from now (sorry, we didn't get much notice). More generally, the 2016h release reflects the following changes, which were either circulated on the tz mailing list or are relatively minor technical or administrative changes: Changes to future time stamps Asia/Gaza and Asia/Hebron end DST on 2016-10-29 at 01:00, not 2016-10-21 at 00:00. (Thanks to Sharef Mustafa.) Predict that future fall transitions will be on the last Saturday of October at 01:00, which is consistent with predicted spring transitions on the last Saturday of March. (Thanks to Tim Parenti.) Changes to past time stamps In Turkey, transitions in 1986-1990 were at 01:00 standard time not at 02:00, and the spring 1994 transition was on March 20, not March 27. (Thanks to Kıvanç Yazan.) Changes to past and future time zone abbreviations Asia/Colombo now uses numeric time zone abbreviations like "+0530" instead of alphabetic ones like "IST" and "LKT". Various English-language sources use "IST", "LKT" and "SLST", with no working consensus. (Usage of "SLST" mentioned by Sadika Sumanapala.) Changes to code zic no longer mishandles relativizing file names when creating symbolic links like /etc/localtime, when these symbolic links are outside the usual directory hierarchy. This fixes a bug introduced in 2016g. (Problem reported by Andreas Stieger.) Changes to build procedure New rules 'traditional_tarballs' and 'traditional_signatures' for building just the traditional-format distribution. (Requested by Deborah Goldsmith.) The file 'version' is now put into the tzdata tarball too. (Requested by Howard Hinnant.) Changes to documentation and commentary The 'Theory' file now has a section on interface stability. (Requested by Paul Koning.) It also mentions features like tm_zone and localtime_rz that have long been supported by the reference code. tz-link.htm has improved coverage of time zone boundaries suitable for geolocation. (Thanks to heads-ups from Evan Siroky and Matt Johnson.) The US commentary now mentions Allen and the "day of two noons". The Fiji commentary mentions the government's 2016-10-03 press release. (Thanks to Raymond Kumar.) Here are links to the release files: ftp://ftp.iana.org/tz/releases/tzcode2016h.tar.gz ftp://ftp.iana.org/tz/releases/tzdata2016h.tar.gz ftp://ftp.iana.org/tz/releases/tzdb-2016h.tar.lz The files are also available via HTTP as follows: http://www.iana.org/time-zones/repository/releases/tzcode2016h.tar.gz http://www.iana.org/time-zones/repository/releases/tzdata2016h.tar.gz http://www.iana.org/time-zones/repository/releases/tzdb-2016h.tar.lz As usual, links to the latest release files are here: http://www.iana.org/time-zones/repository/tzcode-latest.tar.gz http://www.iana.org/time-zones/repository/tzdata-latest.tar.gz http://www.iana.org/time-zones/repository/tzdb-latest.tar.lz ftp://ftp.iana.org/tz/tzcode-latest.tar.gz ftp://ftp.iana.org/tz/tzdata-latest.tar.gz ftp://ftp.iana.org/tz/tzdb-latest.tar.lz Each release file has a GPG signature, which can be retrieved by appending ".asc" to the above URLs. Copies of these signatures are appended to this message. This release corresponds to commit 6349f541e2183a00b9909af00b480c58955474cf dated 2016-10-19 23:17:57 -0700 and tagged '2016h' in the experimental github repository at <https://github.com/eggert/tz>. Here are the SHA-512 checksums for the release files: 109204356f8105b50d1e563c9a33f140a4af7ea38bfb720756f1fce863a346387d3897dfbd506da94fadcd10f35dc50d6475c6dfc047764dd308e21ee6291c18 tzcode2016h.tar.gz 8d4eeaebe39392ca9163d03601d1178597b3f0092419d1f54ebd34944110a0b10cb22d4ab8bacfb48bce3f6f7175177105e204f1b4edeadc38ad4ac2d6ded835 tzdata2016h.tar.gz fab2dd36b2c85a48d15cdbdbceb70ae6b30077cb83e582706b56d1e4dd24f945dede25ebd115b4bafa3e514a1d628c3d7f9a2da63f19f10942cd38dc8a16c155 tzdb-2016h.tar.lz Here are the GPG checksums for the release files: -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAABAgAGBQJYCGLlAAoJEO2X6Q5iqn40hxQP/iamwTHAfVWNxb9yu+Xz8DeV 3kYZJF1ln6kkgmTqASn/L1m5VnaO8e4gVjwpYmkUavYUKZBCHkw9GxclNS5Qt3hI tDm2yE7vAvH23/zgo/NWeFtIzpp476W+VcIlCaSCo0iJ008rPxvIiBmFfgAg9Jji xUPYBBNHH1fLVIpyD2xCzwdeoDiJITX45CtWeGoT2uwA+4xbtfv1/NVMu8j7SN9w 7mpUTF2sAoMUdmG56TE0B8Y4vP3BwlqmVq8CadA4yj0DDwg+vyHKI7wkk9uP44+g DDmcZc9vK8P934veSsexNDLjdAxWSHkgcZ1IwGIPjl5/nquosPy5CdF6VqZFS+IX 9ruapyouZlXlfgg+I6pofkQw4WInO+tn0mIZxJHKXfv33aIxMU22m5ddvCJ0+hUf JIMgrkf0dGzlc8g2FT0DYVtDRg7Zik0GrszjmPc8jzeLi31oGxWA4Xjpwm8rYX/p 7kwIGwg3R19OwUaSgDjpEzXgXi3+iyNeLgq28YjhXj9p4iDhVUo+Njl8Kl31H1Vt 7gpo3utpRcT41nX/5yVUVcx4mJjvNwzD36/zc7hoTTQIInyrR5jQAZ5danDr/HCp NoK16D7WgbMaZMD0M0UV4RyTBlHKc0qeyL++xT7WLESCLxOpmVQdB/CYLjx0BZUr UAq95YoKcMMv+3KHjsDG =aC8a -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAABAgAGBQJYCGLlAAoJEO2X6Q5iqn40FNcP/RX7P5yEnZCRQ4FHHSFg9oIN Hsbp+7R9J9ap5egW8qPVu4HXzmbIzVbED/iCYWah+OMHI9ivJhRTVgPMhHcGco/k Qe8cb72EJIFc/N62BJyPoi48XqrDlw7bJGUuP0+bQGDG8Mik6RqTfOw3kUiUZT+y 9d/NfjQv8k/ASVxaag4FTKhcC9GeKHT51GDdFY9cRam4dgADXdqqsDAhPPeBeKrU hcZEtXaFYZzYvdBjmR7jK/2OYsSGatFeZY5aHxUi4dEmQ2WTv5/3nj6uOe1oHTjw X+xxrYcqINxPC3ss/VHT1fn8X1gQSsbAo/Vp9M9njdXCXCoOu/pSvpnyS4TZi/a6 CGSeGOr3Bz2hYQ1zIegr1QQgcgaK8LP/kl9IJ7dm6yBLVo0NZulzsJ9hRyZwDgWV +BhaPt5IZ0ktQNW8vU5HXrF7ic4qGdCKbcZOUr3DJaOcGHN92QpXS2cgvfZN/+8S uOWGdbCJIcaBmdfe3v9m4I/CKXi8ymb5ZXMDrPwkY6mDokqCG6s6Wfo++zlh1PPT E3Ix3HXfgYBrmByRxtJFwvI/l0VbzpfvOd4HcKuzWQltR5WYvPzdPB6HHLQGdsj7 2BFVXkFPKm1c0NMwB7u5xxvQiVRn1fjz+nLcP9BgZqASCVtREDu91GbRsNntFjzM MbBfIJc99AZIjc9hBjeI =dGny -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAABAgAGBQJYCGLlAAoJEO2X6Q5iqn40aGAP/iN1k3MtoTiYqnUR5NZyR6it c8grrRznviOPpjEk8/bfT0XpPGY1hwq1ctuuwHbylAFMVT7D4tM9csvDErP3bMNg ewDqBltrtLUzYEA66041AM3wLDTqe/lRqEXiNAPKSmulY4UM1FYHs9qpJ5rFXyOD bD6hkB0mppG/stQ3odfqM0EBZMPCjIZyPqZE4UcE4CY56ZN9R4Fa+R4urtyLRjhL OZqApSDeNtxX+cOPg5QlLO0jxhpO5649zjr7hCkHwXSi9Ji6CzKhiMz3RwJ9L4os VsX6Jg0QTZ68JVa3Zf+i/ysRCMvWQHvBxT3lG5aWrrrCpqvZKVgplFe/MSwbsMDH 3+5ws/+7aPS/QkeZo3WYS/0NisVgKUiKq5zH6PmhzfcfD0CMUUqS/fuHmP3cf1Vl rVRubxg0PgpThFLNdOMNa6c8L7lqzuV5Hwelq3yknM+1V02aTBHRFaU3Sh/gmest qRhb1GD+DO84Qm2JXL3kZXL1UGQq7EbH25r8DJAHHObx1TWyGTrLIE0MmS3LMZz5 zNzXMhaEBNufOQQz8LFwLJEiY4+WFem5VZAjE62GMl8iHhxCYJbuu+J3GeOcuP/l IFVLevVfoqa70CQTzKG7iEDhGwWmO3QdcmC261opbW1FPGnjiy+gOilayHse6ITX gt2dd+COJxgg7TlYv/vB =nbsq -----END PGP SIGNATURE----- _______________________________________________ tz-announce mailing list tz-announce(a)iana.org https://mm.icann.org/mailman/listinfo/tz-announce

1 0

Geolocation extension to tzdist
by Ken Murchison Oct. 20, 2016

Oct. 20, 2016

All, (sending to tz(a)iana.org since tzdist(a)ietf.org appears to be dead) I was bored today (actually avoiding "real" work) and was playing around with the ESRI shapefile for timezones <http://efele.net/maps/tz/world/> I hacked up a quick extension to my tzdist implementation using the tz_world shapefile and basic ray tracing to be able to query a time zone by geo coordinates, similar to what Google offers in their Time Zone API. Note that I have yet to spend any time writing code to account for "holes" in time zones like the Navajo Reservation in Arizona. I modeled the extension after the "find" action in RFC 7808 but with lat/long query params rather than a glob pattern. A request and response for the timezone in which my home is located looks something like this: GET /tzdist/zones?latitude=43.070833&longitude=-78.831667 HTTP/1.1 { "synctoken": "890939292-1466089793", "timezones": [ { "tzid": "America/New_York", "etag": "6602582-1466089793", "last-modified": "2016-06-16T15:09:53Z", "publisher": "IANA Time Zone Database", "version": "2016e", "aliases": [ "US/Eastern" ] } ] } The definition of the extension looks like this in the capabilities response: { "name": "geolocate", "uri-template": "/zones{?latitude,longitude}", "parameters": [ { "name": "latitude", "required": true }, { "name": "longitude", "required": true } ] } Currently my code only accepts coordinates in decimal degrees, but I think it should probably support ISO 6709 formats. Is this something that folks would like to see documented as a formal extension to tzdist, either as specified above or with some modification? If so, I'd be willing to write it up as a draft and then move it through IETF in whatever fashion the ADs recommend. -- Kenneth Murchison Principal Systems Software Engineer Carnegie Mellon University

4 5

[PATCH] Change abbreviation of Sri Lanka standard time to SLST
by Sadika Sumanapala Oct. 20, 2016

Oct. 20, 2016

According to http://www.sltime.org (maintained by Measurement Units, Standards & Services Department, Sri Lanka) abbreviation for Sri Lanka standard time is SLST. --- asia | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/asia b/asia index 71ef878..dcc8465 100644 --- a/asia +++ b/asia @@ -2768,6 +2768,10 @@ Zone Asia/Singapore 6:55:25 - LMT 1901 Jan 1 # One possibility is that we wait for a bit for the dust to settle down # and then see what people actually say in practice. +# From Sadika Sumanapala (2016-10-18): +# According to http://www.sltime.org (Official web site of dissemation +# of standard time of Sri Lanka) abbreviation is SLST. + # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Colombo 5:19:24 - LMT 1880 5:19:32 - MMT 1906 # Moratuwa Mean Time @@ -2777,7 +2781,7 @@ Zone Asia/Colombo 5:19:24 - LMT 1880 5:30 - IST 1996 May 25 0:00 6:30 - LKT 1996 Oct 26 0:30 6:00 - LKT 2006 Apr 15 0:30 - 5:30 - IST + 5:30 - SLST # Syria # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S -- 2.10.0

7 18

Palestine Summer Time wrong ending date
by Sharef Mustafa Oct. 19, 2016

Oct. 19, 2016

Hi, Regarding Palestine end of summer time (Asia/Gaza + Asia/Hebron), the current tz database shows that summer time will end on Oct 20th 2016, sharef@plug.ps:/usr/share/zoneinfo$ zdump -v Asia/Gaza | grep 2016 Asia/Gaza Fri Mar 25 22:59:59 2016 UT = Sat Mar 26 00:59:59 2016 EET isdst=0 gmtoff=7200 Asia/Gaza Fri Mar 25 23:00:00 2016 UT = Sat Mar 26 02:00:00 2016 EEST isdst=1 gmtoff=10800 Asia/Gaza Thu Oct 20 20:59:59 2016 UT = Thu Oct 20 23:59:59 2016 EEST isdst=1 gmtoff=10800 Asia/Gaza Thu Oct 20 21:00:00 2016 UT = Thu Oct 20 23:00:00 2016 EET isdst=0 gmtoff=7200 also for westbank Hebron sharef@plug.ps:/usr/share/zoneinfo$ zdump -v Asia/Hebron | grep 2016 Asia/Hebron Fri Mar 25 22:59:59 2016 UT = Sat Mar 26 00:59:59 2016 EET isdst=0 gmtoff=7200 Asia/Hebron Fri Mar 25 23:00:00 2016 UT = Sat Mar 26 02:00:00 2016 EEST isdst=1 gmtoff=10800 Asia/Hebron Thu Oct 20 20:59:59 2016 UT = Thu Oct 20 23:59:59 2016 EEST isdst=1 gmtoff=10800 Asia/Hebron Thu Oct 20 21:00:00 2016 UT = Thu Oct 20 23:00:00 2016 EET isdst=0 gmtoff=7200 However the Palestinian cabinet decision ( Mar 8th 2016) published on http://www.palestinecabinet.gov.ps/WebSite/Upload/Decree/GOV_17/16032016134… states that summer time will end on Oct 29th at 01:00 . There has been no recent updates from the government in this regard, I suggest to correct the end date accordingly. BR Sharef Mustafa

3 3

Suggestion for addition of America/Brasilia entry to time zone database
by Gabriel Gaspar Oct. 19, 2016

Oct. 19, 2016

Hello there, and sorry for the intrusion. I presently write to this list with a suggestion for addition of an entry in the time zone database, America/Brasilia, or at least for a clarification on why there may not be one. Being the standard official time in Brazil, I firmly believe there should be one such entry (unless, of course, matters of greater power disallow it). The official time used in Brazil is called "the Brasilia official time" (UTC -3:00), Brasilia being the capital of Brazil. Note that the official country name is Brasil, with an 's', and the official capital name is Brasília, with an acute on the first 'i'. I am writing the country name with 'z' and leaving the aforementioned acute out for internationalization purposes. Inside Brazilian territory, the remainder time zones are usually referred and adjusted having Brasilia time as a referential base, e.g. "Brasilia time +1", "Brasilia time -1" etc. Even more, event times in Brazil (games, DST start/end, official announcements) are all informed, be it via government official channels or mass media, in Brasilia's official time, further evidencing the importance of Brasilia as a reference for setting times inside country territory. That being said, I have always wondered why it is that Brasilia is not listed as one of the time zones in the data base for South America. It is the official time for Brazil and the name does not clash with any other name in the database (America/Brasilia). Instead, it is relegated to an indirect mention, (Brasilia is located inside Distrito Federal (DF)), in a comment for the time zone America/Sao_Paulo. São Paulo is a major city in Brazil, but by no means the capital itself, nor does it retain any authoritative power in setting or representing the official time, which Brasilia does. Actually, the America/Sao_Paulo time zone entry seems to be doing what an America/Brasilia time zone entry should be doing. Thus, my suggestion would be either for the addition of something such as America/Brasilia to the time zone database, or for the renaming of America/Sao_Paulo to America/Brasilia in order to more accurately represent what that time zone entry stands for. The former suggestion would add more information to the database, but other than occupying more space I fail to see further problems with that addition. The latter suggestion could break some scripts that rely on the time zone name for correct operation, although I currently have no knowledge of one such script nor how crucial its operation could be. Without further ado, I thank you for the time to read this, and appreciate the time for such considerations. Regards, Gabriel G. Gaspar

3 2

Crimea status
by Adam Golovenko Oct. 15, 2016

Oct. 15, 2016

Hello, last time I used data from unicode.org which use time zone information from your time zones database. I found one moment: RU +4457+03406 Europe/Simferopol MSK+00 - Crimea Timezone "Europe/Simferopol" (and Simferopol city itself) should belong to Ukraine (UA), not Russia (RU). Crimea, as temporary occupied area in all international documents states as ukrainian territory. More details can be found here: http://usa.mfa.gov.ua/en/legal_aspects https://en.wikipedia.org/wiki/United_Nations_General_Assembly_Resolution_68… It's not political position or some other sort of things to argue with. In this case one country (Russia) temporarily occupied part of another country (Ukraine), but no countries except Russia itself treat it legal. So UN with most votes (countries) decided to treat Crimea still as a part of Ukraine and this position should be used for all international materials and communications. Please make changes to your data, returning Europe/Simferopol to correct country. Otherwise ukrainian government (if officially notified) will insist on making changes in documents in juridical manner (there were some precedents with Coca-Cola company, french national maps agency and several more). Thanks in advance, will be glad to receive a responce!

2 1

New shapefile of world's timezones based off of Open Street Map data
by Evan Siroky Oct. 11, 2016

Oct. 11, 2016

Hello All, I have just made a first release of a shapefile of the geographic extent of the timezone database based mostly off of Open Street Map data. All of the borders between countries, states and cities come directly from Open Street Map. This shapefile also includes the territorial waters of countries as defined in Open Street Map. Please see my github project for more details. The shapefile can be found in the project releases. https://github.com/evansiroky/timezone-boundary-builder Evan.

4 3

[PROPOSED PATCH] * tz-link.htm: Add section IDs.
by Paul Eggert Oct. 11, 2016

Oct. 11, 2016

--- tz-link.htm | 35 ++++++++++++++++++----------------- 1 file changed, 18 insertions(+), 17 deletions(-) diff --git a/tz-link.htm b/tz-link.htm index ed926c7..43188a4 100644 --- a/tz-link.htm +++ b/tz-link.htm @@ -10,7 +10,7 @@ content="Sources for time zone and daylight saving time data"> <meta name="DC.Creator" content="Eggert, Paul"> <meta name="DC.Contributor" content="Olson, Arthur David"> -<meta name="DC.Date" content="2016-09-21"> +<meta name="DC.Date" content="2016-10-11"> <meta name="DC.Description" content="Sources of information about time zones and daylight saving time"> <meta name="DC.Identifier" @@ -27,7 +27,7 @@ histories and planned futures are often recorded only fitfully. Here is a summary of attempts to organize and record relevant data in this area. </p> -<h2>The <code><abbr title="time zone">tz</abbr></code> database</h2> +<h2 id="tzdb">The <code><abbr title="time zone">tz</abbr></code> database</h2> <p> The <a href="https://en.wikipedia.org/wiki/Public_domain">public-domain</a> time zone database contains code and data @@ -152,7 +152,7 @@ The code lets you compile the <code><abbr>tz</abbr></code> source files into machine-readable binary files, one for each location. It also lets you read a <code><abbr>tz</abbr></code> binary file and interpret time stamps for that location.</p> -<h2>Changes to the <code><abbr>tz</abbr></code> database</h2> +<h2 id="changes">Changes to the <code><abbr>tz</abbr></code> database</h2> <p> The <code><abbr>tz</abbr></code> code and data are by no means authoritative. If you find errors, please @@ -194,7 +194,7 @@ For further information about updates, please see <a href="https://tools.ietf.org/html/rfc6557">Procedures for Maintaining the Time Zone Database</a> (Internet <abbr title="Request For Comments">RFC</abbr> 6557).</p> -<h2>Commentary on the <code><abbr>tz</abbr></code> database</h2> +<h2 id="commentary">Commentary on the <code><abbr>tz</abbr></code> database</h2> <ul> <li>The article <a href="https://en.wikipedia.org/wiki/Tz_database">tz database</a> is @@ -212,7 +212,8 @@ href="https://blog.jonudell.net/2009/10/23/a-literary-appreciation-of-the-olsonz literary appreciation of the Olson/Zoneinfo/tz database</a> comments on the database's style.</li> </ul> -<h2>Web sites using recent versions of the <code><abbr>tz</abbr></code> database</h2> +<h2 id="web">Web sites using recent versions of the +<code><abbr>tz</abbr></code> database</h2> <p> These are listed roughly in ascending order of complexity and fanciness. </p> @@ -242,7 +243,7 @@ calculates the current time difference between locations.</li> also contains data about time zone boundaries; it supports queries via place names and shows location maps.</li> </ul> -<h2>Network protocols for <code><abbr>tz</abbr></code> data</h2> +<h2 id="protocols">Network protocols for <code><abbr>tz</abbr></code> data</h2> <ul> <li>The <a href="https://www.ietf.org">Internet Engineering Task Force</a>'s <a href="https://datatracker.ietf.org/wg/tzdist/charter/">Time Zone Data @@ -267,7 +268,7 @@ title="Extensible Markup Language">XML</abbr></a> format, and a variant uses <a href="http://www.json.org"><abbr title="JavaScript Object Notation">JSON</abbr></a> format.</li> </ul> -<h2>Other <code><abbr>tz</abbr></code> compilers</h2> +<h2 id="compilers">Other <code><abbr>tz</abbr></code> compilers</h2> <ul> <li><a href="https://sourceforge.net/projects/vzic/">Vzic</a> is a <a href="https://en.wikipedia.org/wiki/C_%28programming_language%29">C</a> @@ -390,7 +391,7 @@ source into text files, along with a runtime that can read those files. Tcl is freely available under a <abbr>BSD</abbr>-style license.</li> </ul> -<h2>Other <code><abbr>tz</abbr></code> binary file readers</h2> +<h2 id="binary">Other <code><abbr>tz</abbr></code> binary file readers</h2> <ul> <li>The <a href="https://www.gnu.org/software/libc/"><abbr>GNU</abbr> C @@ -439,7 +440,7 @@ package contains <a href="https://www.haskell.org">Haskell</a> code that parses and uses <code><abbr>tz</abbr></code> binary data. It is freely available under a <abbr>BSD</abbr>-style license.</li> </ul> -<h2>Other <code><abbr>tz</abbr></code>-based time zone software</h2> +<h2 id="software">Other <code><abbr>tz</abbr></code>-based time zone software</h2> <ul> <li><a href="https://foxclocks.org">FoxClocks</a> is an extension for <a href="https://www.google.com/chrome/">Google @@ -496,7 +497,7 @@ an <abbr>OS X</abbr> program. Its developers <a href="http://veladg.com/tzoffer.html">offer free licenses</a> to <code><abbr>tz</abbr></code> contributors.</li> </ul> -<h2>Other time zone databases</h2> +<h2 id="other-dbs">Other time zone databases</h2> <ul> <li><a href="http://www.astro.com/atlas">Time-zone Atlas</a> is Astrodienst's Web version of Shanks and Pottenger's @@ -525,7 +526,7 @@ Schedules Information Manual</a> of the International Air Transport Association gives current time zone rules for airports served by commercial aviation.</li> </ul> -<h2>Maps</h2> +<h2 id="maps">Maps</h2> <ul> <li>The <a href="https://www.cia.gov/index.html">United States Central Intelligence Agency (<abbr @@ -552,7 +553,7 @@ much is time wrong around the world?</a> maps the difference between mean solar and standard time, highlighting areas such as western China where the two differ greatly. It's a bit out of date, unfortunately.</li> </ul> -<h2>Time zone boundaries</h2> +<h2 id="boundaries">Time zone boundaries</h2> <ul> <li><a href="http://efele.net/maps/tz/"><abbr>TZ</abbr> timezones maps</a> contains <a @@ -589,7 +590,7 @@ for land and territorial waters only). A captain can change ship's clocks any time after entering a new time zone; midnight changes are common.</li> </ul> -<h2>Civil time concepts and history</h2> +<h2 id="civil">Civil time concepts and history</h2> <ul> <li><a href="http://physics.nist.gov/time">A Walk through Time</a> @@ -609,7 +610,7 @@ time zone boundary.</li> <li><a href="http://statoids.com/tconcept.html">Basic Time Zone Concepts</a> discusses terminological issues behind time zones.</li> </ul> -<h2>National histories of legal time</h2> +<h2 id="national">National histories of legal time</h2> <dl> <dt>Australia</dt> <dd>The Parliamentary Library has commissioned a <a @@ -679,7 +680,7 @@ of Summer time dates</a>.</dd> href="https://www.transportation.gov/regulations/recent-time-zone-proceedings">Recent Time Zone Proceedings</a> lists changes to time zone boundaries.</dd> </dl> -<h2>Precision timekeeping</h2> +<h2 id="precision">Precision timekeeping</h2> <ul> <li><a href="http://literature.agilent.com/litweb/pdf/5965-7984E.pdf">The @@ -752,7 +753,7 @@ might be redefined without Leap Seconds</a> gives pointers on this contentious issue.</li> </ul> -<h2>Time notation</h2> +<h2 id="notation">Time notation</h2> <ul> <li>The <a href="http://cldr.unicode.org">Unicode Common Locale Data Repository (<abbr>CLDR</abbr>) Project</a> has localizations for time @@ -826,7 +827,7 @@ any future changes to the rules. One should never set local time is nine hours ahead of <abbr>UTC</abbr> and the time zone is called "<abbr>GMT</abbr>".</li> </ul> -<h2>See also</h2> +<h2 id="see-also">See also</h2> <ul> <li><a href="tz-art.htm">Time and the Arts</a></li> </ul> -- 2.7.4

1 0

Adapting localtime.c
by Carsten Larsen Oct. 10, 2016

Oct. 10, 2016

Hello list I am trying to adapt the tz code to a local system without any timezone database (AmigaOS). I got the code up and running and everything seems to work as intended. But one thing about the code puzzles me. I need to implement "time_t time(time_t *p)" which is the very last part of localtime.c. Should this code return time as local time or as GMT time ? Because I cannot get the time calculations to work properly. I use tzsetwall() to guess the timezone from the systems locale zone information (GMT+1, etc) and tzset() to load timezone from the TZ environment variable. Should "time_t time(time_t *p)" try to compensate if lclptr is set, or should it always just return the plain system time? I hope someone knows the answer and also thank you for any clarifications on this issue. Kind regards Carsten Larsen

8 13

TimeZone
by Ali Emre Gürsu Oct. 9, 2016

Oct. 9, 2016

Hello there, Is there any know tool or way to read and check your binary timezone files that you upload? Thanks for the work, great job. Best Regards, Ali Emre Gürsu

3 3

Re: [tz] New shapefile of world' s timezones based off of Open Street Map data
by Evan Siroky Oct. 8, 2016

Oct. 8, 2016

I got really worried for a second wondering if I had misspelled the Rankin_Inlet timezone name, but looks like I'm good! Whew. Thanks for your compliment and suggestion.

1 0

tzdata2016g.tar.gz\Makefile has a bug
by Help rtds.ru Oct. 7, 2016

Oct. 7, 2016

Hello. "Makefile" from tzdata2016g.tar.gz has the line: Version= unknown I think this is a bug. At least, it disrupts Oracle's tzupdater (ver.2.1.0). -- Best regards, *Nikotin Sergey* IT Dept *GK RTDService * Russia, 117393, Moscow, Obrucheva st., 52/69. phone: +7 (495) 718-66-77 e-mail: help(a)rtds.ru <mailto:help@rtds.ru> web: www.rtds.ru

2 1

zic: symlink generation issue
by Andreas Stieger Oct. 6, 2016

Oct. 6, 2016

Hello, on openSUSE we are seeing issues generating symlinks after replacing our distribution specific patches with the upstream code: $ rm /etc/localtime $ ln -s /usr/share/zoneinfo/Europe/London /etc/localtime $ ls -l /etc/localtime lrwxrwxrwx 1 root root 33 Oct 6 12:47 /etc/localtime -> /usr/share/zoneinfo/Europe/London $ zic -l Europe/Berlin $ ls -l /etc/localtime lrwxrwxrwx 1 root root 19 Oct 6 11:47 /etc/localtime -> ../../Europe/Berlin resulting in a broken symbolic link. The previous code supplied relname(), and in dolink() instead of calculating the dotdots using fromfield/tofield we used fromname/toname, respectively. I though I'd let you know while we are working on this, in case you have a quick fix. Otherwise we'll attempt to upstream what we come up with. Andreas -- Andreas Stieger <astieger(a)suse.com> Project Manager Security SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)

2 2

zic: symlink generation issue
by Andreas Stieger Oct. 6, 2016

Oct. 6, 2016

Hello, on openSUSE we are seeing issues generating symlinks after replacing our distribution specific patches with the upstream code: $ rm /etc/localtime $ ln -s /usr/share/zoneinfo/Europe/London /etc/localtime $ ls -l /etc/localtime lrwxrwxrwx 1 root root 33 Oct 6 12:47 /etc/localtime -> /usr/share/zoneinfo/Europe/London $ zic -l Europe/Berlin $ ls -l /etc/localtime lrwxrwxrwx 1 root root 19 Oct 6 11:47 /etc/localtime -> ../../Europe/Berlin resulting in a broken symbolic link. The previous code supplied relname(), and in dolink() instead of calculating the dotdots using fromfield/tofield we used fromname/toname, respectively. I though I'd let you know while we are working on this, in case you have a quick fix. Otherwise we'll attempt to upstream what we come up with. Andreas -- Andreas Stieger <astieger(a)suse.de> Project Manager Security SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)

1 0

[PROPOSED PATCH] Make targets more atomically
by Paul Eggert Oct. 4, 2016

Oct. 4, 2016

A 'make' that failed due to a write failure could leave behind a junk file that was up-to-date, confusing a later 'make'. * Makefile (version, version.h, leapseconds, zones, tzselect) ($(MANTXTS), tzcode$(VERSION).tar.gz, tzdata$(VERSION).tar.gz) (tzdb-$(VERSION).tar.lz): Use mv to create targets atomically. --- Makefile | 29 +++++++++++++++++++---------- 1 file changed, 19 insertions(+), 10 deletions(-) diff --git a/Makefile b/Makefile index 4781633..f7553a3 100644 --- a/Makefile +++ b/Makefile @@ -438,14 +438,16 @@ version: $(VERSION_DEPS) V=`git describe --match '[0-9][0-9][0-9][0-9][a-z]*' \ --abbrev=7 --dirty` || \ V=$(VERSION); } && \ - printf '%s\n' "$$V" >$@ + printf '%s\n' "$$V" >$@.out + mv $@.out $@ version.h: version VERSION=`cat version` && printf '%s\n' \ 'static char const PKGVERSION[]="($(PACKAGE)) ";' \ "static char const TZVERSION[]=\"$$VERSION\";" \ 'static char const REPORT_BUGS_TO[]="$(BUGEMAIL)";' \ - >$@ + >$@.out + mv $@.out $@ zdump: $(TZDOBJS) $(CC) -o $@ $(CFLAGS) $(LDFLAGS) $(TZDOBJS) $(LDLIBS) @@ -458,7 +460,8 @@ yearistype: yearistype.sh chmod +x yearistype leapseconds: $(LEAP_DEPS) - $(AWK) -f leapseconds.awk leap-seconds.list >$@ + $(AWK) -f leapseconds.awk leap-seconds.list >$@.out + mv $@.out $@ # Arguments to pass to submakes of install_data. # They can be overridden by later submake arguments. @@ -521,8 +524,9 @@ $(TZS_NEW): $(TDATA) zdump zic '/^Zone/{print wd "/tzs.dir/" $$2}' $(TDATA) \ | LC_ALL=C sort` && \ ./zdump -i -c $(TZS_YEAR) $$zones >>$@.out - sed 's,^TZ=".*tzs\.dir/,TZ=",' $@.out >$@ + sed 's,^TZ=".*tzs\.dir/,TZ=",' $@.out >$@.sed.out rm -fr tzs.dir $@.out + mv $@.sed.out $@ # If $(TZS) does not already exist (e.g., old-format tarballs), create it. # If it exists but 'make check_tzs' fails, a maintainer should inspect the @@ -548,8 +552,9 @@ tzselect: tzselect.ksh version -e 's|$REPORT_BUGS_TO$=.*|\1=$(BUGEMAIL)|' \ -e 's|TZDIR=[^}]*|TZDIR=$(TZDIR)|' \ -e 's|$TZVERSION$=.*|\1='"$$VERSION"'|' \ - <$@.ksh >$@ - chmod +x $@ + <$@.ksh >$@.out + chmod +x $@.out + mv $@.out $@ check: check_character_set check_white_space check_links check_sorted \ check_tables check_tzs check_web @@ -624,7 +629,8 @@ zdump.8.txt: zdump.8 zic.8.txt: zic.8 $(MANTXTS): workman.sh - LC_ALL=C sh workman.sh `expr $@ : '$.*$\.txt$$'` >$@ + LC_ALL=C sh workman.sh `expr $@ : '$.*$\.txt$$'` >$@.out + mv $@.out $@ # Set the time stamps to those of the git repository, if available, # and if the files have not changed since then. @@ -722,12 +728,14 @@ tzcode$(VERSION).tar.gz: set-timestamps.out LC_ALL=C && export LC_ALL && \ tar $(TARFLAGS) -cf - \ $(COMMON) $(DOCS) $(SOURCES) | \ - gzip $(GZIPFLAGS) > $@ + gzip $(GZIPFLAGS) >$@.out + mv $@.out $@ tzdata$(VERSION).tar.gz: set-timestamps.out LC_ALL=C && export LC_ALL && \ tar $(TARFLAGS) -cf - $(COMMON) $(DATA) $(MISC) | \ - gzip $(GZIPFLAGS) > $@ + gzip $(GZIPFLAGS) >$@.out + mv $@.out $@ tzdb-$(VERSION).tar.lz: set-timestamps.out rm -fr tzdb-$(VERSION) @@ -735,7 +743,8 @@ tzdb-$(VERSION).tar.lz: set-timestamps.out ln $(ENCHILADA) tzdb-$(VERSION) touch -cmr `ls -t tzdb-$(VERSION)/* | sed 1q` tzdb-$(VERSION) LC_ALL=C && export LC_ALL && \ - tar $(TARFLAGS) -cf - tzdb-$(VERSION) | lzip -9 > $@ + tar $(TARFLAGS) -cf - tzdb-$(VERSION) | lzip -9 >$@.out + mv $@.out $@ tzcode$(VERSION).tar.gz.asc: tzcode$(VERSION).tar.gz gpg --armor --detach-sign $? -- 2.7.4

1 0

[PROPOSED PATCH] Port better to Solaris 10
by Paul Eggert Oct. 4, 2016

Oct. 4, 2016

Solaris 10 /bin/sh does not handle exit status properly when called from 'make', and does not support the $(...) syntax. Also, simplify by removing comments about Solaris 9 and earlier, which are no longer maintained. * Makefile: Update comments for current operating system status. (version, set-timestamps.out): Don’t fail on Solaris 10 merely because git is not installed. (version, version.h, $(TZS_NEW), tzselect, check_white_space) (set-timestamps.out, check_time_t_alternatives, tarballs) (traditional_tarballs, signatures, traditional_signatures) (tzdb-$(VERSION).tar.lz): Use `foo`, not $(foo), for Solaris 10 /bin/sh. Check for command failure the old-fashioned way. * private.h, zdump.c (HAVE_STDINT_H): Default to 1 if limits.h defines INTMAX_MAX, for Solaris 10. * strftime.c (_fmt): Rework to avoid diagnostic about unreachable code from Sun C 5.9. Remove unwanted test for tm_isdst in the case where TM_GMTOFF is defined. --- Makefile | 47 +++++++++++++++++++++++++++-------------------- private.h | 12 ++++++------ strftime.c | 24 +++++++++++++----------- zdump.c | 2 +- 4 files changed, 47 insertions(+), 38 deletions(-) diff --git a/Makefile b/Makefile index abeacfa..4781633 100644 --- a/Makefile +++ b/Makefile @@ -101,7 +101,6 @@ PACKRATDATA= YEARISTYPE= ./yearistype # Non-default libraries needed to link. -# Add -lintl if you want to use 'gettext' on Solaris. LDLIBS= # Add the following to the end of the "CFLAGS=" line as needed. @@ -109,9 +108,10 @@ LDLIBS= # -DHAVE_DECL_ASCTIME_R=0 if <time.h> does not declare asctime_r # -DHAVE_DIRECT_H if mkdir needs <direct.h> (MS-Windows) # -DHAVE_DOS_FILE_NAMES if file names have drive specifiers etc. (MS-DOS) -# -DHAVE_GETTEXT=1 if 'gettext' works (GNU, Linux, Solaris); also see LDLIBS +# -DHAVE_GETTEXT=1 if 'gettext' works (e.g., GNU/Linux, FreeBSD, Solaris) # -DHAVE_INCOMPATIBLE_CTIME_R=1 if your system's time.h declares -# ctime_r and asctime_r incompatibly with the POSIX standard (Solaris 8). +# ctime_r and asctime_r incompatibly with the POSIX standard +# (Solaris when _POSIX_PTHREAD_SEMANTICS is not defined). # -DHAVE_INTTYPES_H=1 if you have a pre-C99 compiler with "inttypes.h" # -DHAVE_LINK=0 if your system lacks a link function # -DHAVE_LOCALTIME_R=0 if your system lacks a localtime_r function @@ -434,16 +434,18 @@ INSTALL: ALL install date.1 cp -f date.1 $(DESTDIR)$(MANDIR)/man1/. version: $(VERSION_DEPS) - { V=$$(git describe --match '[0-9][0-9][0-9][0-9][a-z]*' \ - --abbrev=7 --dirty) || \ + { (type git) >/dev/null 2>&1 && \ + V=`git describe --match '[0-9][0-9][0-9][0-9][a-z]*' \ + --abbrev=7 --dirty` || \ V=$(VERSION); } && \ printf '%s\n' "$$V" >$@ version.h: version - (echo 'static char const PKGVERSION[]="($(PACKAGE)) ";' && \ - printf 'static char const TZVERSION[]="%s";\n' \ - "$$(cat version)" && \ - echo 'static char const REPORT_BUGS_TO[]="$(BUGEMAIL)";') >$@ + VERSION=`cat version` && printf '%s\n' \ + 'static char const PKGVERSION[]="($(PACKAGE)) ";' \ + "static char const TZVERSION[]=\"$$VERSION\";" \ + 'static char const REPORT_BUGS_TO[]="$(BUGEMAIL)";' \ + >$@ zdump: $(TZDOBJS) $(CC) -o $@ $(CFLAGS) $(LDFLAGS) $(TZDOBJS) $(LDLIBS) @@ -514,9 +516,10 @@ $(TZS_NEW): $(TDATA) zdump zic $(zic) -d tzs.dir $(TDATA) $(AWK) '/^Link/{print $$1 "\t" $$2 "\t" $$3}' \ $(TDATA) | LC_ALL=C sort >$@.out - zones=$$($(AWK) -v wd="$$(pwd)" \ + wd=`pwd` && \ + zones=`$(AWK) -v wd="$$wd" \ '/^Zone/{print wd "/tzs.dir/" $$2}' $(TDATA) \ - | LC_ALL=C sort) && \ + | LC_ALL=C sort` && \ ./zdump -i -c $(TZS_YEAR) $$zones >>$@.out sed 's,^TZ=".*tzs\.dir/,TZ=",' $@.out >$@ rm -fr tzs.dir $@.out @@ -538,13 +541,13 @@ date: $(DATEOBJS) $(CC) -o $@ $(CFLAGS) $(LDFLAGS) $(DATEOBJS) $(LDLIBS) tzselect: tzselect.ksh version - sed \ + VERSION=`cat version` && sed \ -e 's|#!/bin/bash|#!$(KSHELL)|g' \ -e 's|AWK=[^}]*|AWK=$(AWK)|g' \ -e 's|$PKGVERSION$=.*|\1='\''($(PACKAGE)) '\''|' \ -e 's|$REPORT_BUGS_TO$=.*|\1=$(BUGEMAIL)|' \ -e 's|TZDIR=[^}]*|TZDIR=$(TZDIR)|' \ - -e 's|$TZVERSION$=.*|\1='"$$(cat version)"'|' \ + -e 's|$TZVERSION$=.*|\1='"$$VERSION"'|' \ <$@.ksh >$@ chmod +x $@ @@ -562,7 +565,8 @@ check_character_set: $(ENCHILADA) ! grep -Env $(OK_LINE) $(ENCHILADA) check_white_space: $(ENCHILADA) - ! grep -En ' '$(TAB_CHAR)"|$$(printf '[\f\r\v]')" $(ENCHILADA) + patfmt=' \t|[\f\r\v]' && pat=`printf "$$patfmt\\n"` && \ + ! grep -En "$$pat" $(ENCHILADA) ! grep -n '[[:space:]]$$' $(ENCHILADA) CHECK_CC_LIST = { n = split($$1,a,/,/); for (i=2; i<=n; i++) print a[1], a[i]; } @@ -631,7 +635,8 @@ $(MANTXTS): workman.sh # to be the maximum of the files it depends on. set-timestamps.out: $(ENCHILADA) rm -f $@ - if files=`git ls-files $(ENCHILADA)` && \ + if (type git) >/dev/null 2>&1 && \ + files=`git ls-files $(ENCHILADA)` && \ touch -md @1 test.out; then \ rm -f test.out && \ for file in $$files; do \ @@ -648,8 +653,8 @@ set-timestamps.out: $(ENCHILADA) touch -cmr `ls -t $$file workman.sh | sed 1q` $$file.txt || \ exit; \ done - touch -cmr $$(ls -t $(TZS_DEPS) | sed 1q) $(TZS) - touch -cmr $$(ls -t $(VERSION_DEPS) | sed 1q) version + touch -cmr `ls -t $(TZS_DEPS) | sed 1q` $(TZS) + touch -cmr `ls -t $(VERSION_DEPS) | sed 1q` version touch $@ # The zics below ensure that each data file can stand on its own. @@ -673,11 +678,12 @@ check_time_t_alternatives: else \ quiet_option=''; \ fi && \ + wd=`pwd` && \ zones=`$(AWK) '/^[^#]/ { print $$3 }' <zone1970.tab` && \ for type in $(TIME_T_ALTERNATIVES); do \ mkdir -p time_t.dir/$$type && \ $(MAKE) clean_misc && \ - $(MAKE) TOPDIR=$$(pwd)/time_t.dir/$$type \ + $(MAKE) TOPDIR="$$wd/time_t.dir/$$type" \ CFLAGS='$(CFLAGS) -Dtime_tz='"'$$type'" \ REDO='$(REDO)' \ install && \ @@ -702,7 +708,8 @@ check_time_t_alternatives: rm -fr time_t.dir tarballs traditional_tarballs signatures traditional_signatures: version - $(MAKE) VERSION="$$(cat version)" $@_version + VERSION=`cat version` && \ + $(MAKE) VERSION="$$VERSION" $@_version tarballs_version: traditional_tarballs_version tzdb-$(VERSION).tar.lz traditional_tarballs_version: \ @@ -726,7 +733,7 @@ tzdb-$(VERSION).tar.lz: set-timestamps.out rm -fr tzdb-$(VERSION) mkdir tzdb-$(VERSION) ln $(ENCHILADA) tzdb-$(VERSION) - touch -cmr $$(ls -t tzdb-$(VERSION)/* | sed 1q) tzdb-$(VERSION) + touch -cmr `ls -t tzdb-$(VERSION)/* | sed 1q` tzdb-$(VERSION) LC_ALL=C && export LC_ALL && \ tar $(TARFLAGS) -cf - tzdb-$(VERSION) | lzip -9 > $@ diff --git a/private.h b/private.h index daad297..d6a6c5d 100644 --- a/private.h +++ b/private.h @@ -78,9 +78,9 @@ /* Enable tm_gmtoff and tm_zone on GNUish systems. */ #define _GNU_SOURCE 1 -/* Fix asctime_r on Solaris 10. */ +/* Fix asctime_r on Solaris 11. */ #define _POSIX_PTHREAD_SEMANTICS 1 -/* Enable strtoimax on Solaris 10. */ +/* Enable strtoimax on pre-C99 Solaris 11. */ #define __EXTENSIONS__ 1 /* @@ -161,15 +161,15 @@ /* ** Define HAVE_STDINT_H's default value here, rather than at the -** start, since __GLIBC__'s value depends on previously-included -** files. -** (glibc 2.1 and later have stdint.h, even with pre-C99 compilers.) +** start, since __GLIBC__ and INTMAX_MAX's values depend on +** previously-included files. glibc 2.1 and Solaris 10 and later have +** stdint.h, even with pre-C99 compilers. */ #ifndef HAVE_STDINT_H #define HAVE_STDINT_H \ (199901 <= __STDC_VERSION__ \ || 2 < __GLIBC__ + (1 <= __GLIBC_MINOR__) \ - || __CYGWIN__) + || __CYGWIN__ || INTMAX_MAX) #endif /* !defined HAVE_STDINT_H */ #if HAVE_STDINT_H diff --git a/strftime.c b/strftime.c index 151b2e9..984ead5 100644 --- a/strftime.c +++ b/strftime.c @@ -496,15 +496,14 @@ label: */ continue; case 'z': +#if defined TM_GMTOFF || defined USG_COMPAT || defined ALTZONE { long diff; char const * sign; - if (t->tm_isdst < 0) - continue; -#ifdef TM_GMTOFF +# ifdef TM_GMTOFF diff = t->TM_GMTOFF; -#else /* !defined TM_GMTOFF */ +# else /* ** C99 says that the UT offset must ** be computed by looking only at @@ -524,19 +523,21 @@ label: ** determinable, so output nothing if the ** appropriate variables are not available. */ + if (t->tm_isdst < 0) + continue; if (t->tm_isdst == 0) -#ifdef USG_COMPAT +# ifdef USG_COMPAT diff = -timezone; -#else /* !defined USG_COMPAT */ +# else continue; -#endif /* !defined USG_COMPAT */ +# endif else -#ifdef ALTZONE +# ifdef ALTZONE diff = -altzone; -#else /* !defined ALTZONE */ +# else continue; -#endif /* !defined ALTZONE */ -#endif /* !defined TM_GMTOFF */ +# endif +# endif if (diff < 0) { sign = "-"; diff = -diff; @@ -547,6 +548,7 @@ label: (diff % MINSPERHOUR); pt = _conv(diff, "%04d", pt, ptlim); } +#endif continue; case '+': pt = _fmt(Locale->date_fmt, t, pt, ptlim, diff --git a/zdump.c b/zdump.c index f68ba3d..a901aff 100644 --- a/zdump.c +++ b/zdump.c @@ -45,7 +45,7 @@ # define HAVE_STDINT_H \ (199901 <= __STDC_VERSION__ \ || 2 < __GLIBC__ + (1 <= __GLIBC_MINOR__) \ - || __CYGWIN__) + || __CYGWIN__ || INTMAX_MAX) #endif #if HAVE_STDINT_H # include "stdint.h" -- 2.7.4

1 0

Jordan thinking of following Turkey's lead
by Paul Eggert Oct. 4, 2016

Oct. 4, 2016

Jordan is considering following Turkey's lead and switching to permanent +03, which would mean Asia/Amman's clocks would not be changed from 01:00 to 00:00 on October 28. Instead of switching back to +02 as currently planned, the government may delay working and school hours to better match year-round +03. (Amman's local mean time is roughly +0224.) There is no word on when the decision will be made. If they do decide to change the rules on such short notice, we'd need to generate a new tz version soon after. Given the usual delays in propagating such a change, there's a good chance Jordan's cell phones and computers won't be updated in time. Obeidat O. Gov’t mulls keeping summertime around the year. Jordan Times 2016-10-03. http://www.jordantimes.com/news/local/gov%E2%80%99t-mulls-keeping-summertim…

1 0

Fiji DST 2016/17
by Raymond Kumar Oct. 4, 2016

Oct. 4, 2016

Hi Paul, Some changes to the Fiji DST 2016/17 were communicated to us. See link order from Fiji Government Website. http://www.fiji.gov.fj/Media-Center/Press-Releases/DAYLIGHT-SAVING-STARTS-O… The attached order states: "Fiji's daylight savings will begin on Sunday, 6 November 2016, when clocks go forward an hour at 2am to 3am and end at 3.00am on Sunday 15th January 2017 Fiji rules in tzdata2016g.tar: Rule Fiji 2014 max - Nov Sun>=1 2:00 1:00 S Rule Fiji 2015 max - Jan Sun>=15 3:00 0 - The current rules will not work for 2016. Please can we have an updated file for Fiji. Regards, Raymond Kumar Head of Billing and Products Digicel Fiji Limited +6797015315 ________________________________ Notice of Confidentiality: The information contained in this communication is intended solely for the use of the individual or entity to whom it is addressed and others authorized to receive it. It may contain confidential or legally privileged information. If you are not the intended recipient you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this information is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by responding to this email and then delete it from your system.

2 1

Are tzdata2016g & tzdata-latest missing the VERSION file?
by Barry Allard Sept. 30, 2016

Sept. 30, 2016

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hello, Thanks to all the folks whom have maintained and contributed to this vital database over the for years. Has the format changed somehow? If this and future database files were to break backwards-compatibility arbitrarily, it would be an unwelcome, breaking change for potentially tens- to hundreds-of-thousands of deployed endpoints and would an expensive burden and require lots of system software providers to repackage and push new software to untold millions to billions of endpoints, some of which are for-all-practical-purposes immutable (such as embedded systems / SCADA). In short: it would make a lot of people mad because it would be very expensive and time-consuming to change. For example, here's just one error from a wide-deployed utility (TZUpdater 2.1) which worked using tzdata2016f, but not with tzdata-latest nor tzdata2016g: $ java -jar tzupdater.jar -l https://www.iana.org/time-zones/repository/tzdata-latest.tar.gz Using https://www.iana.org/time-zones/repository/tzdata-latest.tar.gz as source for tzdata bundle. Source directory does not contain file: VERSION $ $ java -jar tzupdater.jar -l https://www.iana.org/time-zones/repository/releases/tzdata2016f.tar.gz Using https://www.iana.org/time-zones/repository/releases/tzdata2016f.tar.gz as source for tzdata bundle. JRE has the same version as the tzupdater provided one (tzdata2016f). $ If I might humbly suggest continuing using what was a de-facto standard for stability and least-surprise, where at all possible. Thanks, Barry Allard PS: I saw a related past discussion but can't respond to it right now. -----BEGIN PGP SIGNATURE----- Version: Mailvelope v1.5.2 Comment: https://www.mailvelope.com wsFcBAEBCAAQBQJX7i2oCRAUysGWoSICbAAAR4QP/1MoTcbGQC7IfGNOZ1z3 nwl4FQIqJc7sECdA57AgGfjMQvweR2QZkayFEvQEgiCZ+0QinRfS03EQtY+r XJzmdRarJprfDq4b91Bp5LITT0bwKIAcHsqdvHs/BSlBUP2JgwLi7DHui/kP J9YMMI2nczoQx3ozXFGo3hWWV580dnHVdm4kyvtMGkJ1DCG+uhTmePzyH/Yz Zign0qsVKuse5PBwYsqqmgCCNO8smi2XwM0jGSr7jjoYd/We7ySzgq0vdMdt 0CQ3G2sR/DeyGBvsXDEVZ8LVCaTkevmVe8X8Ky9Z+U25CYV7ZoqTWNX6TBS4 cjGMfbxdBOCXRNRyOUkYLPEeeLmrsKl76bq1nGqY00NNrinjkPdxmxrDp8OP tiw1xKQM5j67Dkm6cbVhSPAyhIKcrGfGiahNMOILYnuEx/TJDQXFBQKBWIqc aamL404CRIWlpy4URDKGIFNOblaX6v1pTgIXe60GOjbNT4iIfSA7sFBMJrWw 7gvlnn4/X4pl7LegwRAMt87ikxom7nd8IBN6VZx0MyFRKPWKVvrFkmR5ZQ5Q R5zDGFLztRACyJruktM/LTfOa/RZYn1B4pqh3Ns7VE+zrMYEjTDix79RC2Au n8eCFIgsYVVpkTQ5RrTFp4BatUsV+LG9RROwq2om83VeXJIGYiVrCrviT+ia CyJF =XmoD -----END PGP SIGNATURE-----

8 21

Re: [tz] Geolocation extension to tzdist
by Karl Petrow Sept. 30, 2016

Sept. 30, 2016

Just signed up for this mail list so please forgive me if my etiquette is bad. There is a node module for this already I have used. https://www.npmjs.com/package/tz-lookup Karl Disclaimer The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful.

2 1

Re: [tz] tz-2016g.tar.gz and Oracle Java Timezone Updater Tool
by Susan Abraham Sept. 29, 2016

Sept. 29, 2016

Hi Pete, Oracle has not yet released the OJVM patch for 2016g. It is expected by 2nd week of Oracle. Regards, Susan On 9/27/2016 5:30 PM, tz-request(a)iana.org wrote: > Send tz mailing list submissions to > tz(a)iana.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://mm.icann.org/mailman/listinfo/tz > or, via email, send a message with subject or body 'help' to > tz-request(a)iana.org > > You can reach the person managing the list at > tz-owner(a)iana.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of tz digest..." > > > Today's Topics: > > 1. tz-2016g.tar.gz and Oracle Java Timezone Updater Tool > (Dempsey, Peter) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 27 Sep 2016 11:27:10 +0000 > From: "Dempsey, Peter" <Peter.Dempsey(a)verint.com> > To: "tz(a)iana.org" <tz(a)iana.org> > Subject: [tz] tz-2016g.tar.gz and Oracle Java Timezone Updater Tool > Message-ID: > <53037F6841B154468CE4ADF48141A7F7E9385CF6(a)TLVMBX1.verint.corp.verintsystems.com> > > Content-Type: text/plain; charset="iso-8859-1" > > Hi, > > I was wondering where I could a version of the 2016g.tar.gz file that works with the Oracle Java Timezone Updated Tool. I need to test this tool by using the file:// protocol. > > Best regards, > > Pete > > > -- Oracle <http://www.oracle.com> Susan Abraham | Principal Software Engineer, Advanced Resolution Engineer<tel:+9886756903> Oracle Global Customer Service Oracle India Bangalore Green Oracle <http://www.oracle.com/commitment> Oracle is committed to developing practices and products that help protect the environment

2 2

[PATCH] Phase out invented abbrs for ex-Soviet Union
by Paul Eggert Sept. 29, 2016

Sept. 29, 2016

* NEWS: Document this. * asia (Asia/Yerevan, Asia/Baku, Asia/Tbilisi, Asia/Bishkek) (Asia/Dushanbe, Asia/Ashgabat, Asia/Samarkand, Asia/Tashkent): * europe (Russia, Europe/Minsk, Europe/Kaliningrad) (Europe/Volgograd, Europe/Samara, Asia/Yekaterinburg, Asia/Omsk) (Asia/Krasnoyarsk, Asia/Irkutsk, Asia/Chita, Asia/Yakutsk) (Asia/Vladivostok, Asia/Khandyga, Asia/Sakhalin, Asia/Magadan) (Asia/Srednekolymsk, Asia/Ust-Nera, Asia/Kamchatka, Asia/Anadyr): Prefer numeric to invented time zone abbreviations. --- NEWS | 14 ++++ asia | 93 ++++++++++++-------------- europe | 232 ++++++++++++++++++++++++++++++++--------------------------------- 3 files changed, 171 insertions(+), 168 deletions(-) diff --git a/NEWS b/NEWS index 61213b0..e10083a 100644 --- a/NEWS +++ b/NEWS @@ -13,6 +13,20 @@ Unreleased, experimental changes corrected from 02:00 to 02:01 in 1948, and from 02:00 to 01:00 in 1950-1966. + Changes to past and future time zone abbreviations + + Several zones in the former Soviet Union now use numeric time zone + abbreviations instead of invented ones. The affected zones are + Asia/Anadyr, Asia/Ashgabat, Asia/Baku, Asia/Bishkek, Asia/Chita, + Asia/Dushanbe, Asia/Irkutsk, Asia/Kamchatka, Asia/Khandyga, + Asia/Krasnoyarsk, Asia/Magadan, Asia/Omsk, Asia/Sakhalin, + Asia/Samarkand, Asia/Srednekolymsk, Asia/Tashkent, Asia/Tbilisi, + Asia/Ust-Nera, Asia/Vladivostok, Asia/Yakutsk, Asia/Yekaterinburg, + Asia/Yerevan, Europe/Kaliningrad, Europe/Minsk, Europe/Samara, and + Europe/Volgograd. For Europe/Moscow the invented abbreviation MSM + was replaced by +05, whereas MSK and MSD were kept as they are not + our invention and are widely used. + Changes to code zic no longer generates binary files containing POSIX TZ-like diff --git a/asia b/asia index 533e218..ee2c436 100644 --- a/asia +++ b/asia @@ -116,13 +116,11 @@ Zone Asia/Kabul 4:36:48 - LMT 1890 # http://www.worldtimezone.com/dst_news/dst_news_armenia03.html # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Yerevan 2:58:00 - LMT 1924 May 2 - 3:00 - YERT 1957 Mar # Yerevan Time - 4:00 RussiaAsia YER%sT 1991 Mar 31 2:00s - 3:00 1:00 YERST 1991 Sep 23 # independence - 3:00 RussiaAsia AM%sT 1995 Sep 24 2:00s - 4:00 - AMT 1997 - 4:00 RussiaAsia AM%sT 2012 Feb 9 - 4:00 - AMT + 3:00 - +03 1957 Mar + 4:00 RussiaAsia +04/+05 1991 Mar 31 2:00s + 3:00 RussiaAsia +03/+04 1995 Sep 24 2:00s + 4:00 - +04 1997 + 4:00 RussiaAsia +04/+05 # Azerbaijan @@ -143,13 +141,12 @@ Rule Azer 1997 2015 - Mar lastSun 4:00 1:00 S Rule Azer 1997 2015 - Oct lastSun 5:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Baku 3:19:24 - LMT 1924 May 2 - 3:00 - BAKT 1957 Mar # Baku Time - 4:00 RussiaAsia BAK%sT 1991 Mar 31 2:00s - 3:00 1:00 BAKST 1991 Aug 30 # independence - 3:00 RussiaAsia AZ%sT 1992 Sep lastSun 2:00s - 4:00 - AZT 1996 # Azerbaijan Time - 4:00 EUAsia AZ%sT 1997 - 4:00 Azer AZ%sT + 3:00 - +03 1957 Mar + 4:00 RussiaAsia +04/+05 1991 Mar 31 2:00s + 3:00 RussiaAsia +03/+04 1992 Sep lastSun 2:00s + 4:00 - +04 1996 + 4:00 EUAsia +04/+05 1997 + 4:00 Azer +04/+05 # Bahrain # See Asia/Qatar. @@ -835,16 +832,15 @@ Link Asia/Nicosia Europe/Nicosia # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Tbilisi 2:59:11 - LMT 1880 2:59:11 - TBMT 1924 May 2 # Tbilisi Mean Time - 3:00 - TBIT 1957 Mar # Tbilisi Time - 4:00 RussiaAsia TBI%sT 1991 Mar 31 2:00s - 3:00 1:00 TBIST 1991 Apr 9 # independence - 3:00 RussiaAsia GE%sT 1992 # Georgia Time - 3:00 E-EurAsia GE%sT 1994 Sep lastSun - 4:00 E-EurAsia GE%sT 1996 Oct lastSun - 4:00 1:00 GEST 1997 Mar lastSun - 4:00 E-EurAsia GE%sT 2004 Jun 27 - 3:00 RussiaAsia GE%sT 2005 Mar lastSun 2:00 - 4:00 - GET + 3:00 - +03 1957 Mar + 4:00 RussiaAsia +04/+05 1991 Mar 31 2:00s + 3:00 RussiaAsia +03/+04 1992 + 3:00 E-EurAsia +03/+04 1994 Sep lastSun + 4:00 E-EurAsia +04/+05 1996 Oct lastSun + 4:00 1:00 +05 1997 Mar lastSun + 4:00 E-EurAsia +04/+05 2004 Jun 27 + 3:00 RussiaAsia +03/+04 2005 Mar lastSun 2:00 + 4:00 - +04 # East Timor @@ -1825,11 +1821,11 @@ Rule Kyrgyz 1997 2005 - Mar lastSun 2:30 1:00 S Rule Kyrgyz 1997 2004 - Oct lastSun 2:30 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Bishkek 4:58:24 - LMT 1924 May 2 - 5:00 - FRUT 1930 Jun 21 # Frunze Time - 6:00 RussiaAsia FRU%sT 1991 Mar 31 2:00s - 5:00 1:00 FRUST 1991 Aug 31 2:00 # independence - 5:00 Kyrgyz KG%sT 2005 Aug 12 # Kyrgyzstan Time - 6:00 - KGT + 5:00 - +05 1930 Jun 21 + 6:00 RussiaAsia +06/+07 1991 Mar 31 2:00s + 5:00 RussiaAsia +05/+06 1991 Aug 31 2:00 + 5:00 Kyrgyz +05/+06 2005 Aug 12 + 6:00 - +06 ############################################################################### @@ -2951,10 +2947,10 @@ Zone Asia/Damascus 2:25:12 - LMT 1920 # Dimashq # From Shanks & Pottenger. # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Dushanbe 4:35:12 - LMT 1924 May 2 - 5:00 - DUST 1930 Jun 21 # Dushanbe Time - 6:00 RussiaAsia DUS%sT 1991 Mar 31 2:00s - 5:00 1:00 DUSST 1991 Sep 9 2:00s - 5:00 - TJT # Tajikistan Time + 5:00 - +05 1930 Jun 21 + 6:00 RussiaAsia +06/+07 1991 Mar 31 2:00s + 5:00 1:00 +05/+06 1991 Sep 9 2:00s + 5:00 - +05 # Thailand # Zone NAME GMTOFF RULES FORMAT [UNTIL] @@ -2968,11 +2964,10 @@ Link Asia/Bangkok Asia/Vientiane # Laos # From Shanks & Pottenger. # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Ashgabat 3:53:32 - LMT 1924 May 2 # or Ashkhabad - 4:00 - ASHT 1930 Jun 21 # Ashkhabad Time - 5:00 RussiaAsia ASH%sT 1991 Mar 31 2:00 - 4:00 RussiaAsia ASH%sT 1991 Oct 27 # independence - 4:00 RussiaAsia TM%sT 1992 Jan 19 2:00 - 5:00 - TMT + 4:00 - +04 1930 Jun 21 + 5:00 RussiaAsia +05/+06 1991 Mar 31 2:00 + 4:00 RussiaAsia +04/+05 1992 Jan 19 2:00 + 5:00 - +05 # United Arab Emirates # Zone NAME GMTOFF RULES FORMAT [UNTIL] @@ -2984,20 +2979,18 @@ Link Asia/Dubai Asia/Muscat # Oman # Byalokoz 1919 says Uzbekistan was 4:27:53. # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Samarkand 4:27:53 - LMT 1924 May 2 - 4:00 - SAMT 1930 Jun 21 # Samarkand Time - 5:00 - SAMT 1981 Apr 1 - 5:00 1:00 SAMST 1981 Oct 1 - 6:00 - TAST 1982 Apr 1 # Tashkent Time - 5:00 RussiaAsia SAM%sT 1991 Sep 1 # independence - 5:00 RussiaAsia UZ%sT 1992 - 5:00 - UZT + 4:00 - +04 1930 Jun 21 + 5:00 - +05 1981 Apr 1 + 5:00 1:00 +06 1981 Oct 1 + 6:00 - +06 1982 Apr 1 + 5:00 RussiaAsia +05/+06 1992 + 5:00 - +05 # Milne says Tashkent was 4:37:10.8; round to nearest. Zone Asia/Tashkent 4:37:11 - LMT 1924 May 2 - 5:00 - TAST 1930 Jun 21 # Tashkent Time - 6:00 RussiaAsia TAS%sT 1991 Mar 31 2:00 - 5:00 RussiaAsia TAS%sT 1991 Sep 1 # independence - 5:00 RussiaAsia UZ%sT 1992 - 5:00 - UZT + 5:00 - +05 1930 Jun 21 + 6:00 RussiaAsia +06/+07 1991 Mar 31 2:00 + 5:00 RussiaAsia +05/+06 1992 + 5:00 - +05 # Vietnam diff --git a/europe b/europe index cd3a088..b02edbd 100644 --- a/europe +++ b/europe @@ -75,8 +75,7 @@ # 1:00 CET CEST CEMT Central Europe # 1:00:14 SET Swedish (1879-1899)* # 2:00 EET EEST Eastern Europe -# 3:00 FET Further-eastern Europe (2011-2014)* -# 3:00 MSK MSD MSM* Minsk, Moscow +# 3:00 MSK MSD Moscow # From Peter Ilieve (1994-12-04), # The original six [EU members]: Belgium, France, (West) Germany, Italy, @@ -592,7 +591,7 @@ Rule Russia 1919 only - May 31 23:00 2:00 MDST Rule Russia 1919 only - Jul 1 2:00 1:00 MSD Rule Russia 1919 only - Aug 16 0:00 0 MSK Rule Russia 1921 only - Feb 14 23:00 1:00 MSD -Rule Russia 1921 only - Mar 20 23:00 2:00 MSM # Midsummer +Rule Russia 1921 only - Mar 20 23:00 2:00 +05 Rule Russia 1921 only - Sep 1 0:00 1:00 MSD Rule Russia 1921 only - Oct 1 0:00 0 - # Act No. 925 of the Council of Ministers of the USSR (1980-10-24): @@ -787,8 +786,7 @@ Zone Europe/Minsk 1:50:16 - LMT 1880 3:00 Russia MSK/MSD 1990 3:00 - MSK 1991 Mar 31 2:00s 2:00 Russia EE%sT 2011 Mar 27 2:00s - 3:00 - FET 2014 Oct 26 1:00s - 3:00 - MSK + 3:00 - +03 # Belgium # @@ -2336,7 +2334,7 @@ Zone Europe/Kaliningrad 1:22:00 - LMT 1893 Apr 2:00 Poland CE%sT 1946 3:00 Russia MSK/MSD 1989 Mar 26 2:00s 2:00 Russia EE%sT 2011 Mar 27 2:00s - 3:00 - FET 2014 Oct 26 2:00s + 3:00 - +03 2014 Oct 26 2:00s 2:00 - EET @@ -2573,15 +2571,14 @@ Zone Europe/Astrakhan 3:12:12 - LMT 1924 May # The 1988 transition is from USSR act No. 5 (1988-01-04). Zone Europe/Volgograd 2:57:40 - LMT 1920 Jan 3 - 3:00 - TSAT 1925 Apr 6 # Tsaritsyn Time - 3:00 - STAT 1930 Jun 21 # Stalingrad Time - 4:00 - STAT 1961 Nov 11 - 4:00 Russia VOL%sT 1988 Mar 27 2:00s # Volgograd T - 3:00 Russia VOL%sT 1991 Mar 31 2:00s - 4:00 - VOLT 1992 Mar 29 2:00s - 3:00 Russia MSK/MSD 2011 Mar 27 2:00s - 4:00 - MSK 2014 Oct 26 2:00s - 3:00 - MSK + 3:00 - +03 1930 Jun 21 + 4:00 - +04 1961 Nov 11 + 4:00 Russia +04/+05 1988 Mar 27 2:00s + 3:00 Russia +03/+04 1991 Mar 31 2:00s + 4:00 - +04 1992 Mar 29 2:00s + 3:00 Russia +03/+04 2011 Mar 27 2:00s + 4:00 - +04 2014 Oct 26 2:00s + 3:00 - +03 # From Paul Eggert (2016-03-18): # Europe/Kirov covers: @@ -2607,15 +2604,15 @@ Zone Europe/Kirov 3:18:48 - LMT 1919 Jul 1 2:00 # The 1989 transition is from USSR act No. 227 (1989-03-14). Zone Europe/Samara 3:20:20 - LMT 1919 Jul 1 2:00 - 3:00 - SAMT 1930 Jun 21 # Samara Time - 4:00 - SAMT 1935 Jan 27 - 4:00 Russia KUY%sT 1989 Mar 26 2:00s # Kuybyshev - 3:00 Russia MSK/MSD 1991 Mar 31 2:00s - 2:00 Russia EE%sT 1991 Sep 29 2:00s - 3:00 - SAMT 1991 Oct 20 3:00 - 4:00 Russia SAM%sT 2010 Mar 28 2:00s - 3:00 Russia SAM%sT 2011 Mar 27 2:00s - 4:00 - SAMT + 3:00 - +03 1930 Jun 21 + 4:00 - +04 1935 Jan 27 + 4:00 Russia +04/+05 1989 Mar 26 2:00s + 3:00 Russia +03/+04 1991 Mar 31 2:00s + 2:00 Russia +02/+03 1991 Sep 29 2:00s + 3:00 - +03 1991 Oct 20 3:00 + 4:00 Russia +04/+05 2010 Mar 28 2:00s + 3:00 Russia +03/+04 2011 Mar 27 2:00s + 4:00 - +04 # From Paul Eggert (2016-03-18): # Europe/Ulyanovsk covers: @@ -2662,12 +2659,12 @@ Zone Europe/Ulyanovsk 3:13:36 - LMT 1919 Jul 1 2:00 Zone Asia/Yekaterinburg 4:02:33 - LMT 1916 Jul 3 3:45:05 - PMT 1919 Jul 15 4:00 - 4:00 - SVET 1930 Jun 21 # Sverdlovsk Time - 5:00 Russia SVE%sT 1991 Mar 31 2:00s - 4:00 Russia SVE%sT 1992 Jan 19 2:00s - 5:00 Russia YEK%sT 2011 Mar 27 2:00s - 6:00 - YEKT 2014 Oct 26 2:00s - 5:00 - YEKT + 4:00 - +04 1930 Jun 21 + 5:00 Russia +05/+06 1991 Mar 31 2:00s + 4:00 Russia +04/+05 1992 Jan 19 2:00s + 5:00 Russia +05/+06 2011 Mar 27 2:00s + 6:00 - +06 2014 Oct 26 2:00s + 5:00 - +05 # From Tim Parenti (2014-07-03), per Oscar van Vlijmen (2001-08-25): @@ -2677,12 +2674,12 @@ Zone Asia/Yekaterinburg 4:02:33 - LMT 1916 Jul 3 # Byalokoz 1919 says Omsk was 4:53:30. Zone Asia/Omsk 4:53:30 - LMT 1919 Nov 14 - 5:00 - OMST 1930 Jun 21 # Omsk Time - 6:00 Russia OMS%sT 1991 Mar 31 2:00s - 5:00 Russia OMS%sT 1992 Jan 19 2:00s - 6:00 Russia OMS%sT 2011 Mar 27 2:00s - 7:00 - OMST 2014 Oct 26 2:00s - 6:00 - OMST + 5:00 - +05 1930 Jun 21 + 6:00 Russia +06/+07 1991 Mar 31 2:00s + 5:00 Russia +05/+06 1992 Jan 19 2:00s + 6:00 Russia +06/+07 2011 Mar 27 2:00s + 7:00 - +07 2014 Oct 26 2:00s + 6:00 - +06 # From Paul Eggert (2016-02-22): # Asia/Barnaul covers: @@ -2845,12 +2842,12 @@ Zone Asia/Novokuznetsk 5:48:48 - LMT 1924 May 1 # Byalokoz 1919 says Krasnoyarsk was 6:11:26. Zone Asia/Krasnoyarsk 6:11:26 - LMT 1920 Jan 6 - 6:00 - KRAT 1930 Jun 21 # Krasnoyarsk Time - 7:00 Russia KRA%sT 1991 Mar 31 2:00s - 6:00 Russia KRA%sT 1992 Jan 19 2:00s - 7:00 Russia KRA%sT 2011 Mar 27 2:00s - 8:00 - KRAT 2014 Oct 26 2:00s - 7:00 - KRAT + 6:00 - +06 1930 Jun 21 + 7:00 Russia +07/+08 1991 Mar 31 2:00s + 6:00 Russia +06/+07 1992 Jan 19 2:00s + 7:00 Russia +07/+08 2011 Mar 27 2:00s + 8:00 - +08 2014 Oct 26 2:00s + 7:00 - +07 # From Tim Parenti (2014-07-03), per Oscar van Vlijmen (2001-08-25): @@ -2867,12 +2864,12 @@ Zone Asia/Krasnoyarsk 6:11:26 - LMT 1920 Jan 6 Zone Asia/Irkutsk 6:57:05 - LMT 1880 6:57:05 - IMT 1920 Jan 25 # Irkutsk Mean Time - 7:00 - IRKT 1930 Jun 21 # Irkutsk Time - 8:00 Russia IRK%sT 1991 Mar 31 2:00s - 7:00 Russia IRK%sT 1992 Jan 19 2:00s - 8:00 Russia IRK%sT 2011 Mar 27 2:00s - 9:00 - IRKT 2014 Oct 26 2:00s - 8:00 - IRKT + 7:00 - +07 1930 Jun 21 + 8:00 Russia +08/+09 1991 Mar 31 2:00s + 7:00 Russia +07/+08 1992 Jan 19 2:00s + 8:00 Russia +08/+09 2011 Mar 27 2:00s + 9:00 - +09 2014 Oct 26 2:00s + 8:00 - +08 # From Tim Parenti (2014-07-06): @@ -2889,13 +2886,13 @@ Zone Asia/Irkutsk 6:57:05 - LMT 1880 # http://publication.pravo.gov.ru/Document/View/0001201512300107 Zone Asia/Chita 7:33:52 - LMT 1919 Dec 15 - 8:00 - YAKT 1930 Jun 21 # Yakutsk Time - 9:00 Russia YAK%sT 1991 Mar 31 2:00s - 8:00 Russia YAK%sT 1992 Jan 19 2:00s - 9:00 Russia YAK%sT 2011 Mar 27 2:00s - 10:00 - YAKT 2014 Oct 26 2:00s - 8:00 - IRKT 2016 Mar 27 2:00 - 9:00 - YAKT + 8:00 - +08 1930 Jun 21 + 9:00 Russia +09/+10 1991 Mar 31 2:00s + 8:00 Russia +08/+09 1992 Jan 19 2:00s + 9:00 Russia +09/+10 2011 Mar 27 2:00s + 10:00 - +10 2014 Oct 26 2:00s + 8:00 - +08 2016 Mar 27 2:00 + 9:00 - +09 # From Tim Parenti (2014-07-03), per Oscar van Vlijmen (2009-11-29): @@ -2935,12 +2932,12 @@ Zone Asia/Chita 7:33:52 - LMT 1919 Dec 15 # Byalokoz 1919 says Yakutsk was 8:38:58. Zone Asia/Yakutsk 8:38:58 - LMT 1919 Dec 15 - 8:00 - YAKT 1930 Jun 21 # Yakutsk Time - 9:00 Russia YAK%sT 1991 Mar 31 2:00s - 8:00 Russia YAK%sT 1992 Jan 19 2:00s - 9:00 Russia YAK%sT 2011 Mar 27 2:00s - 10:00 - YAKT 2014 Oct 26 2:00s - 9:00 - YAKT + 8:00 - +08 1930 Jun 21 + 9:00 Russia +09/+10 1991 Mar 31 2:00s + 8:00 Russia +08/+09 1992 Jan 19 2:00s + 9:00 Russia +09/+10 2011 Mar 27 2:00s + 10:00 - +10 2014 Oct 26 2:00s + 9:00 - +09 # From Tim Parenti (2014-07-03), per Oscar van Vlijmen (2009-11-29): @@ -2958,12 +2955,12 @@ Zone Asia/Yakutsk 8:38:58 - LMT 1919 Dec 15 # Go with Byalokoz. Zone Asia/Vladivostok 8:47:31 - LMT 1922 Nov 15 - 9:00 - VLAT 1930 Jun 21 # Vladivostok Time - 10:00 Russia VLA%sT 1991 Mar 31 2:00s - 9:00 Russia VLA%sT 1992 Jan 19 2:00s - 10:00 Russia VLA%sT 2011 Mar 27 2:00s - 11:00 - VLAT 2014 Oct 26 2:00s - 10:00 - VLAT + 9:00 - +09 1930 Jun 21 + 10:00 Russia +10/+11 1991 Mar 31 2:00s + 9:00 Russia +09/+10 1992 Jan 19 2:00s + 10:00 Russia +10/+11 2011 Mar 27 2:00s + 11:00 - +11 2014 Oct 26 2:00s + 10:00 - +10 # From Tim Parenti (2014-07-03): @@ -2981,14 +2978,14 @@ Zone Asia/Vladivostok 8:47:31 - LMT 1922 Nov 15 # This transition is no doubt wrong, but we have no better info. Zone Asia/Khandyga 9:02:13 - LMT 1919 Dec 15 - 8:00 - YAKT 1930 Jun 21 # Yakutsk Time - 9:00 Russia YAK%sT 1991 Mar 31 2:00s - 8:00 Russia YAK%sT 1992 Jan 19 2:00s - 9:00 Russia YAK%sT 2004 - 10:00 Russia VLA%sT 2011 Mar 27 2:00s - 11:00 - VLAT 2011 Sep 13 0:00s # Decree 725? - 10:00 - YAKT 2014 Oct 26 2:00s - 9:00 - YAKT + 8:00 - +08 1930 Jun 21 + 9:00 Russia +09/+10 1991 Mar 31 2:00s + 8:00 Russia +08/+09 1992 Jan 19 2:00s + 9:00 Russia +09/+10 2004 + 10:00 Russia +10/+11 2011 Mar 27 2:00s + 11:00 - +11 2011 Sep 13 0:00s # Decree 725? + 10:00 - +10 2014 Oct 26 2:00s + 9:00 - +09 # From Tim Parenti (2014-07-03): @@ -3004,15 +3001,14 @@ Zone Asia/Khandyga 9:02:13 - LMT 1919 Dec 15 # The Zone name should be Asia/Yuzhno-Sakhalinsk, but that's too long. Zone Asia/Sakhalin 9:30:48 - LMT 1905 Aug 23 - 9:00 - JCST 1937 Oct 1 - 9:00 - JST 1945 Aug 25 - 11:00 Russia SAK%sT 1991 Mar 31 2:00s # Sakhalin T - 10:00 Russia SAK%sT 1992 Jan 19 2:00s - 11:00 Russia SAK%sT 1997 Mar lastSun 2:00s - 10:00 Russia SAK%sT 2011 Mar 27 2:00s - 11:00 - SAKT 2014 Oct 26 2:00s - 10:00 - SAKT 2016 Mar 27 2:00s - 11:00 - SAKT + 9:00 - +09 1945 Aug 25 + 11:00 Russia +11/+12 1991 Mar 31 2:00s # Sakhalin T + 10:00 Russia +10/+11 1992 Jan 19 2:00s + 11:00 Russia +11/+12 1997 Mar lastSun 2:00s + 10:00 Russia +10/+11 2011 Mar 27 2:00s + 11:00 - +11 2014 Oct 26 2:00s + 10:00 - +10 2016 Mar 27 2:00s + 11:00 - +11 # From Tim Parenti (2014-07-03), per Oscar van Vlijmen (2009-11-29): @@ -3035,13 +3031,13 @@ Zone Asia/Sakhalin 9:30:48 - LMT 1905 Aug 23 # http://publication.pravo.gov.ru/Document/View/0001201604050038 Zone Asia/Magadan 10:03:12 - LMT 1924 May 2 - 10:00 - MAGT 1930 Jun 21 # Magadan Time - 11:00 Russia MAG%sT 1991 Mar 31 2:00s - 10:00 Russia MAG%sT 1992 Jan 19 2:00s - 11:00 Russia MAG%sT 2011 Mar 27 2:00s - 12:00 - MAGT 2014 Oct 26 2:00s - 10:00 - MAGT 2016 Apr 24 2:00s - 11:00 - MAGT + 10:00 - +10 1930 Jun 21 # Magadan Time + 11:00 Russia +11/+12 1991 Mar 31 2:00s + 10:00 Russia +10/+11 1992 Jan 19 2:00s + 11:00 Russia +11/+12 2011 Mar 27 2:00s + 12:00 - +12 2014 Oct 26 2:00s + 10:00 - +10 2016 Apr 24 2:00s + 11:00 - +11 # From Tim Parenti (2014-07-06): @@ -3089,12 +3085,12 @@ Zone Asia/Magadan 10:03:12 - LMT 1924 May 2 # as the abbreviation. Use SRET instead. Zone Asia/Srednekolymsk 10:14:52 - LMT 1924 May 2 - 10:00 - MAGT 1930 Jun 21 # Magadan Time - 11:00 Russia MAG%sT 1991 Mar 31 2:00s - 10:00 Russia MAG%sT 1992 Jan 19 2:00s - 11:00 Russia MAG%sT 2011 Mar 27 2:00s - 12:00 - MAGT 2014 Oct 26 2:00s - 11:00 - SRET # Srednekolymsk Time + 10:00 - +10 1930 Jun 21 + 11:00 Russia +11/+12 1991 Mar 31 2:00s + 10:00 Russia +10/+11 1992 Jan 19 2:00s + 11:00 Russia +11/+12 2011 Mar 27 2:00s + 12:00 - +12 2014 Oct 26 2:00s + 11:00 - +11 # From Tim Parenti (2014-07-03): @@ -3112,14 +3108,14 @@ Zone Asia/Srednekolymsk 10:14:52 - LMT 1924 May 2 # UTC+12 since at least then, too. Zone Asia/Ust-Nera 9:32:54 - LMT 1919 Dec 15 - 8:00 - YAKT 1930 Jun 21 # Yakutsk Time - 9:00 Russia YAKT 1981 Apr 1 - 11:00 Russia MAG%sT 1991 Mar 31 2:00s - 10:00 Russia MAG%sT 1992 Jan 19 2:00s - 11:00 Russia MAG%sT 2011 Mar 27 2:00s - 12:00 - MAGT 2011 Sep 13 0:00s # Decree 725? - 11:00 - VLAT 2014 Oct 26 2:00s - 10:00 - VLAT + 8:00 - +08 1930 Jun 21 + 9:00 Russia +09/+10 1981 Apr 1 + 11:00 Russia +11/+12 1991 Mar 31 2:00s + 10:00 Russia +10/+11 1992 Jan 19 2:00s + 11:00 Russia +11/+12 2011 Mar 27 2:00s + 12:00 - +12 2011 Sep 13 0:00s # Decree 725? + 11:00 - +11 2014 Oct 26 2:00s + 10:00 - +10 # From Tim Parenti (2014-07-03), per Oscar van Vlijmen (2001-08-25): @@ -3132,12 +3128,12 @@ Zone Asia/Ust-Nera 9:32:54 - LMT 1919 Dec 15 # The Zone name should be Asia/Petropavlovsk-Kamchatski or perhaps # Asia/Petropavlovsk-Kamchatsky, but these are too long. Zone Asia/Kamchatka 10:34:36 - LMT 1922 Nov 10 - 11:00 - PETT 1930 Jun 21 # P-K Time - 12:00 Russia PET%sT 1991 Mar 31 2:00s - 11:00 Russia PET%sT 1992 Jan 19 2:00s - 12:00 Russia PET%sT 2010 Mar 28 2:00s - 11:00 Russia PET%sT 2011 Mar 27 2:00s - 12:00 - PETT + 11:00 - +11 1930 Jun 21 + 12:00 Russia +12/+13 1991 Mar 31 2:00s + 11:00 Russia +11/+12 1992 Jan 19 2:00s + 12:00 Russia +12/+13 2010 Mar 28 2:00s + 11:00 Russia +11/+12 2011 Mar 27 2:00s + 12:00 - +12 # From Tim Parenti (2014-07-03): @@ -3145,13 +3141,13 @@ Zone Asia/Kamchatka 10:34:36 - LMT 1922 Nov 10 # 87 RU-CHU Chukotka Autonomous Okrug Zone Asia/Anadyr 11:49:56 - LMT 1924 May 2 - 12:00 - ANAT 1930 Jun 21 # Anadyr Time - 13:00 Russia ANA%sT 1982 Apr 1 0:00s - 12:00 Russia ANA%sT 1991 Mar 31 2:00s - 11:00 Russia ANA%sT 1992 Jan 19 2:00s - 12:00 Russia ANA%sT 2010 Mar 28 2:00s - 11:00 Russia ANA%sT 2011 Mar 27 2:00s - 12:00 - ANAT + 12:00 - +12 1930 Jun 21 + 13:00 Russia +13/+14 1982 Apr 1 0:00s + 12:00 Russia +12/+13 1991 Mar 31 2:00s + 11:00 Russia +11/+12 1992 Jan 19 2:00s + 12:00 Russia +12/+13 2010 Mar 28 2:00s + 11:00 Russia +11/+12 2011 Mar 27 2:00s + 12:00 - +12 # San Marino -- 2.5.5

3 4

TZ data version 2016g
by Sami Nieminen Sept. 29, 2016

Sept. 29, 2016

With the latest TZ data release these have hanged: - The makefile now has "VERSION" set to "unknown". Earlier this contained the version string, e.g. "2016f". - Moving to FTP directories "/tz/code" and "/tz/data" now give "550: Failed to change directory" --------------------------------------- Sami Nieminen Puh: 040-7290290 Osoite: Ollinkatu 9 C 11, 33400 Tampere

2 2

Re: [tz] tzdata2016g missing version information
by Dempsey, Peter Sept. 29, 2016

Sept. 29, 2016

Hi, I am tried to update the time zone database on my PC using the Oracle TimeZone Updater but was unable to because of an error given about the VERSION. Below is the output from the command: 1. Using the timezone database from www.iana.org: C:\tzupdater>java -jar .\tzupdater.jar -v -l http://www.iana.org/time-zones/repository/tzdata-latest.tar.gz Using http://www.iana.org/time-zones/repository/tzdata-latest.tar.gz as source for tzdata bundle. java.home: C:\Program Files\Java\jre1.8.0_101 java.vendor: Oracle Corporation java.version: 1.8.0_101 tzupdater version 2.1.0-b04 JRE tzdata version: tzdata2016d Downloaded file to C:\Users\abc\AppData\Local\Temp\tz.tmp\tzdata.tar.gz Source directory does not contain file: VERSION 2. Using the local timezone database: C:\tzupdater>java -jar .\tzupdater.jar -v -l file:///c:/tzupdater/tzdata2016g.tar.gz Using file:///c:/tzupdater/tzdata2016g.tar.gz as source for tzdata bundle. java.home: C:\Program Files\Java\jre1.8.0_101 java.vendor: Oracle Corporation java.version: 1.8.0_101 tzupdater version 2.1.0-b04 JRE tzdata version: tzdata2016d Downloaded file to C:\Users\abc\AppData\Local\Temp\tz.tmp\tzdata.tar.gz Source directory does not contain file: VERSION I browsed to the folder C:\Users\abc\AppData\Local\Temp\tz.tmp\ and see that there is file called VERSION and its' content is: tzdataunknown What do I need to do to get this working? Best regards, Pete Pete Dempsey Application Engineer Verint Customer Engagement Solutions Phone +90.532.581.5995 Email peter.dempsey(a)verint.com<mailto:peter.dempsey@verint.com> Web www.verint.com<http://www.verint.com/> -- This electronic message may contain proprietary and confidential information of Verint Systems Inc., its affiliates and/or subsidiaries. The information is intended to be for the use of the individual(s) or entity(ies) named above. If you are not the intended recipient (or authorized to receive this e-mail for the intended recipient), you may not use, copy, disclose or distribute to anyone this message or any information contained in this message. If you have received this electronic message in error, please notify us by replying to this e-mail.

2 1

tz-2016g.tar.gz and Oracle Java Timezone Updater
by Dempsey, Peter Sept. 28, 2016

Sept. 28, 2016

Hi, @Brian Inglis: The file currently at http://www.iana.org/time-zones/repository/tzdata-latest.tar.gz is 2016f. I require the 2016g in the same format. I am unable to create the package myself in a Windows environment. @Susan Abraham: I will not be installing any JVM patches but will be updating the timezone database using the TimesoneUpdater. Best regards, Pete -- This electronic message may contain proprietary and confidential information of Verint Systems Inc., its affiliates and/or subsidiaries. The information is intended to be for the use of the individual(s) or entity(ies) named above. If you are not the intended recipient (or authorized to receive this e-mail for the intended recipient), you may not use, copy, disclose or distribute to anyone this message or any information contained in this message. If you have received this electronic message in error, please notify us by replying to this e-mail.

4 3

[tz-announce] 2016g release of tz code and data available
by Paul Eggert Sept. 28, 2016

Sept. 28, 2016

The 2016g release of the tz code and data is available. It reflects the following changes, which were either circulated on the tz mailing list or are relatively minor technical or administrative changes: Changes to future time stamps Turkey switched from EET/EEST (+02/+03) to permanent +03, effective 2016-09-07. (Thanks to Burak AYDIN.) Use "+03" rather than an invented abbreviation for the new time. New leap second 2016-12-31 23:59:60 UTC as per IERS Bulletin C 52. (Thanks to Tim Parenti.) Changes to past time stamps For America/Los_Angeles, spring-forward transition times have been corrected from 02:00 to 02:01 in 1948, and from 02:00 to 01:00 in 1950-1966. For zones using Soviet time on 1919-07-01, transitions to UT-based time were at 00:00 UT, not at 02:00 local time. The affected zones are Europe/Kirov, Europe/Moscow, Europe/Samara, and Europe/Ulyanovsk. (Thanks to Alexander Belopolsky.) Changes to past and future time zone abbreviations The Factory zone now uses the time zone abbreviation -00 instead of a long English-language string, as -00 is now the normal way to represent an undefined time zone. Several zones in Antarctica and the former Soviet Union, along with zones intended for ships at sea that cannot use POSIX TZ strings, now use numeric time zone abbreviations instead of invented or obsolete alphanumeric abbreviations. The affected zones are Antarctica/Casey, Antarctica/Davis, Antarctica/DumontDUrville, Antarctica/Mawson, Antarctica/Rothera, Antarctica/Syowa, Antarctica/Troll, Antarctica/Vostok, Asia/Anadyr, Asia/Ashgabat, Asia/Baku, Asia/Bishkek, Asia/Chita, Asia/Dushanbe, Asia/Irkutsk, Asia/Kamchatka, Asia/Khandyga, Asia/Krasnoyarsk, Asia/Magadan, Asia/Omsk, Asia/Sakhalin, Asia/Samarkand, Asia/Srednekolymsk, Asia/Tashkent, Asia/Tbilisi, Asia/Ust-Nera, Asia/Vladivostok, Asia/Yakutsk, Asia/Yekaterinburg, Asia/Yerevan, Etc/GMT-14, Etc/GMT-13, Etc/GMT-12, Etc/GMT-11, Etc/GMT-10, Etc/GMT-9, Etc/GMT-8, Etc/GMT-7, Etc/GMT-6, Etc/GMT-5, Etc/GMT-4, Etc/GMT-3, Etc/GMT-2, Etc/GMT-1, Etc/GMT+1, Etc/GMT+2, Etc/GMT+3, Etc/GMT+4, Etc/GMT+5, Etc/GMT+6, Etc/GMT+7, Etc/GMT+8, Etc/GMT+9, Etc/GMT+10, Etc/GMT+11, Etc/GMT+12, Europe/Kaliningrad, Europe/Minsk, Europe/Samara, Europe/Volgograd, and Indian/Kerguelen. For Europe/Moscow the invented abbreviation MSM was replaced by +05, whereas MSK and MSD were kept as they are not our invention and are widely used. Changes to zone names Rename Asia/Rangoon to Asia/Yangon, with a backward compatibility link. (Thanks to David Massoud.) Changes to code zic no longer generates binary files containing POSIX TZ-like strings that disagree with the local time type after the last explicit transition in the data. This fixes a bug with Africa/Casablanca and Africa/El_Aaiun in some year-2037 time stamps on the reference platform. (Thanks to Alexander Belopolsky for reporting the bug and suggesting a way forward.) If the installed localtime and/or posixrules files are symbolic links, zic now keeps them symbolic links when updating them, for compatibility with platforms like OpenSUSE where other programs configure these files as symlinks. zic now avoids hard linking to symbolic links, avoids some unnecessary mkdir and stat system calls, and uses shorter file names internally. zdump has a new -i option to generate transitions in a more-compact but still human-readable format. This option is experimental, and the output format may change in future versions. (Thanks to Jon Skeet for suggesting that an option was needed, and thanks to Tim Parenti and Chris Rovick for further comments.) Changes to build procedure An experimental distribution format is available, in addition to the traditional format which will continue to be distributed. The new format is a tarball tzdb-VERSION.tar.lz with signature file tzdb-VERSION.tar.lz.asc. It unpacks to a top-level directory tzdb-VERSION containing the code and data of the traditional two-tarball format, along with extra data that may be useful. (Thanks to Antonio Diaz Diaz, Oscar van Vlijmen, and many others for comments about the experimental format.) The release version number is now more accurate in the usual case where releases are built from a Git repository. For example, if 23 commits and some working-file changes have been made since release 2016g, the version number is now something like '2016g-23-g50556e3-dirty' instead of the misleading '2016g'. Official releases uses the same version number format as before, e.g., '2016g'. To support the more-accurate version number, its specification has moved from a line in the Makefile to a new source file 'version'. The experimental distribution contains a file to2050.tzs that contains what should be the output of 'zdump -i -c 2050' on primary zones. If this file is available, 'make check' now checks that zdump generates this output. 'make check_web' now works on Fedora-like distributions. Changes to documentation and commentary tzfile.5 now documents the new restriction on POSIX TZ-like strings that is now implemented by zic. Comments now cite URLs for some 1917-1921 Russian DST decrees. (Thanks to Alexander Belopolsky.) tz-link.htm mentions JuliaTime (thanks to Curtis Vogt) and Time4J (thanks to Meno Hochschild) and ThreeTen-Extra, and its description of Java 8 has been brought up to date (thanks to Stephen Colebourne). Its description of local time on Mars has been updated to match current practice, and URLs have been updated and some obsolete ones removed. Here are links to the release files: ftp://ftp.iana.org/tz/releases/tzcode2016g.tar.gz ftp://ftp.iana.org/tz/releases/tzdata2016g.tar.gz ftp://ftp.iana.org/tz/releases/tzdb-2016g.tar.lz The files are also available via HTTP as follows: http://www.iana.org/time-zones/repository/releases/tzcode2016g.tar.gz http://www.iana.org/time-zones/repository/releases/tzdata2016g.tar.gz http://www.iana.org/time-zones/repository/releases/tzdb-2016g.tar.lz As usual, links to the latest release files are here: http://www.iana.org/time-zones/repository/tzcode-latest.tar.gz http://www.iana.org/time-zones/repository/tzdata-latest.tar.gz http://www.iana.org/time-zones/repository/tzdb-latest.tar.lz ftp://ftp.iana.org/tz/tzcode-latest.tar.gz ftp://ftp.iana.org/tz/tzdata-latest.tar.gz ftp://ftp.iana.org/tz/tzdb-latest.tar.gz Each release file has a GPG signature, which can be retrieved by appending ".asc" to the above URLs. Copies of these signatures are appended to this message. This release corresponds to commit 04394af38a9d08fc6655466dfd8d4cf47025893d dated 2016-09-13 08:56:38 -0700 and tagged '2016g' in the experimental github repository at <https://github.com/eggert/tz>. Here are the SHA-512 checksums for the release files: 280f9bd9ee6eacc5cf82004dc5efd4e1d245e68a576c6d8172ebae0247d0777ac8987aed33609106eb1d596229979452023b593d1a4a58be9bc0932c376a3533 tzcode2016g.tar.gz 7b414c1af80faed335a59f40a18931265b71f8dacc3a5f3bd93e8ea0e3d6416a6839dfb88c64b04df3c728c4fb44105503ddb6e87f317dbff29e43c491c2fb3d tzdata2016g.tar.gz f3a26967d77a27c015f3259ab40ff77de16b9d517cbf8bbff30c110a239e3104289727e529cb5675c140cba199073575a63d84265e4b8068f70d730bb780fea8 tzdb-2016g.tar.lz Here are the GPG checksums for the release files: -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAABAgAGBQJX2CTkAAoJEO2X6Q5iqn40/dsQAKZVDkj6jZNmdcS3qfArD30Z U9K7AwLUlugG6WuwMzPYPp2zMNhdM3pVdfSrtgNPjGBJY4kISIiSnNx8CuvNUxlf u+gnsPkr2qfEMEhjEKS9K4yeBi12Bo3WX7lxFJDSqXfQM389EIQufLdcpggQVnoZ mbUCSGS3P+C+JCZBr3ltc6dZVo3OofduZR6rZauyKdHLsFo3UZgo3HZ1AgADU5KB b+8JUAUMssOFr9dp61mF1WBlhHrg7+SubCZe5a4QggON73prhCQWtNFH/de76Ep0 vpjn9y8dbzjSGEuMGxRRH7aBN1XYOiTyBEO3rXYA5J93I7C0IXRD3hALCpqJH/+F dw3lzEOHi7drX/WPS2eHYaHV6GtXs8BpU39lzPiyQ89ZwFDI+ed+IFx0F2nhGI4a YnncsPwHtodhK5AnTifDA9F95MuAZiILBlMLklaFicbtVuptM/pHgSRKKbkjptfR 3M8XmCgw/1zOAyMvc0D7X5YBspKacXDnMNX4jGDtdKoDiUAEjNf2w4RXV9fYg7Wa 5RgcqqhAcSW1SpyUcHo+po6oXTELaBh7+QGPKqsdG8ntbaywqYNT6oJqkLtYzyVj sraRd7+f0EXdgrYTi6rZim/v6VudEqGGBRVfenXzQPCwtaNY1/+UW+Ruo/Yqlo9k Cs4QYazop8GmeH74lAIx =+WWr -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAABAgAGBQJX2CTkAAoJEO2X6Q5iqn40i8IP/jtQ8PYjBG3NJV5uvRGzbV60 n1vdVJDMU9SkRpiT1G8p/cjr4mszUnm+qsZNZGg1wZknBuQdnglAMwA2lj8Llv5N gAlGj/JDEsNESfOC+9wD+NtZK+aUxJzHSXl4xzhzCMjBKaPOytcLKuGscMrpcGFH 2IDyjdjHOfDNG5PAxu0wjkMsKFUt95wmuWzPu1x48EqCF5c2zhanQI3mrugnmLwm MAnq69E+z1q/5WLOzZEfRGXm98BpS90PC89fWwiKdKciHvTVFO9XLz9pknaeRP4N uNcGoF0zEB+unAKoQmMI248sQZ1DzQGRC/niZ9SG70xHSdtBQF19B4oNoh27h3jz j2ZF262PZCL6J5SoEISqXRFkiZbRFR79uwUA5LQRyFWu4gg63wk85+gx8BjxwbPP bUVtV4IBRScFdVC7Li3Xw5PF8cwfQRf0JAxTdtwSgY9tC2pEjomCkb9mzSMDz78w CSFl6yNuL44atUmHK0XFCNIJnyoG0hNrIWwOx/zmlYnaX9Iqm6H9LmXaUcV3rg0N uKaTWuvZQzgxRwbrq0NxH8O/B1LWmdOls4ZGoMboVpTracg6APATXJIaQjm+RKjH EGtDiihPYP/WbrCg823uVPNHCbyoMcFrZB34ujjO89ObH8BsLJKmnUeQUCw74mok D92yWr5OAzGJYJFpgUNr =WYLD -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAABAgAGBQJX2CTkAAoJEO2X6Q5iqn40esIQALCF7VcFJCoopVUcjDigH2CU iG/tRiTiYUboTcLEyZjbXJ8JVuOpOdm5TxQ1U6jUnJidTcl4n7Zcm3BLwlRO4ijl 82sadHGAakvlmyIGulFMot9QfpU2VCAFTJjCs7fDRZOw6jszCGcn3JneuW1JfLV+ xSqkBhUBl4BoXkvRYyL8hOTOofST+Uo2ceAwJt+7IARSlpTqHAXmE8HhstwPuI6C CbgWi2arwJl3CnGz2hkSTo+OYb39SPNTFmDcNRxuw0MztsfA999bkeF67G1ZFhpN klXDGgIkv9NMAqozeblp79k9TSDl2vrsnaqXIp8vQkNFDJvwSp87PzR3Lxkd3DY3 lMK9XaUW55FBGOzuepUAAGfnLjBJ1386nyxhuSM5OGAGc1a1opUmQsTDQoZlYHrj soYsmVsv/mA5rkW7zO3Vckzhq42kM7ZUKWQHKUAoN6kaitjazEpGtjpuJ6GvR2Rz 0W5bf+YyRvu8hERZXood4Un+/UDEvls5uklIOWCZOhTb2bqnHFxTNmgu/9j3faFY E54e+bRnTJIBo51o91ufl9LbNL8R9Gf97y35a4cKCTzQudbz34TMFyfbeim+cNfx Icjevab3az7FacHfURlvuWfgrb69C2qBO1ixT1f8z7vI6KJXXPFSIb36YhLEXe+d Ns8/QhJSKCoDd0EVozzQ =/tZj -----END PGP SIGNATURE----- _______________________________________________ tz-announce mailing list tz-announce(a)iana.org https://mm.icann.org/mailman/listinfo/tz-announce

1 0

Re: [tz] tzdata 2016g
by Paul Eggert Sept. 28, 2016

Sept. 28, 2016

Susan Abraham wrote: > The DST Patches for Oracle Databases are released based on the tzdata. I got the > tzdata 2016g release from https://github.com/eggert/tz/releases. > > What are the changes included in 2016g? The changes are summarized in the NEWS file. https://github.com/eggert/tz/blob/2016g/NEWS

9 18

Link change for timezone and DST data for the Netherlands
by Gent, R.H. van (Rob) Sept. 27, 2016

Sept. 27, 2016

Hi, This has no urgency but at some point please replace the old link http://www.phys.uu.nl/~vgent/wettijd/wettijd.htm with http://www.staff.science.uu.nl/~gent0113/wettijd/wettijd.htm Thanks, Rob van Gent Utrecht University The Netherlands

2 1

tz-2016g.tar.gz and Oracle Java Timezone Updater Tool
by Dempsey, Peter Sept. 27, 2016

Sept. 27, 2016

Hi, I was wondering where I could a version of the 2016g.tar.gz file that works with the Oracle Java Timezone Updated Tool. I need to test this tool by using the file:// protocol. Best regards, Pete -- This electronic message may contain proprietary and confidential information of Verint Systems Inc., its affiliates and/or subsidiaries. The information is intended to be for the use of the individual(s) or entity(ies) named above. If you are not the intended recipient (or authorized to receive this e-mail for the intended recipient), you may not use, copy, disclose or distribute to anyone this message or any information contained in this message. If you have received this electronic message in error, please notify us by replying to this e-mail.

2 1

Istanbul fix for 1986-2006
by Kıvanç Yazan Sept. 25, 2016

Sept. 25, 2016

Hi! I've been looking at DST rules of Turkey, and I run into a few issues. 1) For 1986-2006, DST started at 01:00 local and ended at 02:00 local, with no exceptions. 2) 1994's lastSun was overridden with Mar 20, which was not reflected. Links in comments were inaccessible and some were not official. Here are official papers: http://www.resmigazete.gov.tr/arsiv/19032.pdf -- page 2 for 1986 http://www.resmigazete.gov.tr/arsiv/19400.pdf -- page 4 for 1987 http://www.resmigazete.gov.tr/arsiv/19752.pdf -- page 15 for 1988 http://www.resmigazete.gov.tr/arsiv/20102.pdf -- page 6 for 1989 http://www.resmigazete.gov.tr/arsiv/20464.pdf -- page 1 for 1990 - 1992 http://www.resmigazete.gov.tr/arsiv/21531.pdf -- page 15 for 1993 - 1995 http://www.resmigazete.gov.tr/arsiv/21879.pdf -- page 1 for overriding 1994 http://www.resmigazete.gov.tr/arsiv/22588.pdf -- page 1 for 1996, 1997 http://www.resmigazete.gov.tr/arsiv/23286.pdf -- page 10 for 1998 - 2000 http://www.resmigazete.gov.tr/eskiler/2001/03/20010324.htm#2 -- for 2001 http://www.resmigazete.gov.tr/eskiler/2002/03/20020316.htm#2 -- for 2002 - 2006 Sincerely, Kivanc Yazan

2 2

[PROPOSED PATCH] Change Turkey timezone abbreviation to TRT
by Orhan Biyiklioglu Sept. 23, 2016

Sept. 23, 2016

New time zone abbreviation TRT has been proposed to denote the Turkey Time. See: https://www.timeanddate.com/time/zones/trt Can we use it instead of the +03 abbreviation in the 2016g release? --- europe | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/europe b/europe index 6020059..f05d5fa 100644 --- a/europe +++ b/europe @@ -3496,6 +3496,11 @@ Zone Europe/Zurich 0:34:08 - LMT 1853 Jul 16 # See above comment. # From Paul Eggert (2016-09-07): # The change is permanent, so this is the new standard time in Turkey. # It takes effect today, which is not much notice. +# +# From Orhan Biyiklioglu (2016-09-23): +# New timezone abbreviation TRT is proposed for Turkey time +# https://www.timeanddate.com/time/zones/trt + # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S Rule Turkey 1916 only - May 1 0:00 1:00 S @@ -3569,7 +3574,7 @@ Zone Europe/Istanbul 1:55:52 - LMT 1880 2:00 EU EE%sT 2015 Oct 25 1:00u 2:00 1:00 EEST 2015 Nov 8 1:00u 2:00 EU EE%sT 2016 Sep 7 - 3:00 - +03 + 3:00 - TRT Link Europe/Istanbul Asia/Istanbul # Istanbul is in both continents. # Ukraine -- 1.8.3.1

2 1

Turkey Summer Time Regulation Update
by Ismail AKCAY Sept. 23, 2016

Sept. 23, 2016

Dear All, I am İsmail AKÇAY from Samsung Electronics Turkey company working as Mobile Phone Technical Product Manager. As you may know, Turkey regulation has been changed on 08 September 2016. With this new regulation, Summer Time setting will be used in Turkey for all the time. You can find official publication under below link. (Due to it is an official document, it is in Turkish language) http://www.resmigazete.gov.tr/main.aspx?home=http://www.resmigazete.gov.tr/e skiler/2016/09/20160908.htm <http://www.resmigazete.gov.tr/main.aspx?home=http://www.resmigazete.gov.tr/ eskiler/2016/09/20160908.htm&main=http://www.resmigazete.gov.tr/eskiler/2016 /09/20160908.htm> &main=http://www.resmigazete.gov.tr/eskiler/2016/09/20160908.htm (From above page, you should click to " <http://www.resmigazete.gov.tr/eskiler/2016/09/20160908-2.pdf> 2016/9154 Gün Işığından Daha Fazla Yararlanmak Amacıyla Bütün Yurtta Yaz Saati Uygulanması Hakkında Karar" link. In order to apply this change into our mobile phones, our R&D team is waiting IANA Organization's patch release. We are kindly asking your supports to get updated patch. Best Regards. cid:T9SZN3WZA6X7@namo.co.kr İsmail AKÇAY Mobile Phone Technical Product Manager / Manager Samsung Electronics Turkey Office +90 212 467 0573 Cell +90 533 310 1562 <mailto:ismail.akcay@samsung.com> ismail.akcay(a)samsung.com Bu e-posta (ve ekleri) sadece içeriğinde hitap edilen kişi veya kuruma yönlendirilmiştir; gizli ve/veya kişiye özel olduğu gibi, ticari sır içerebilir. E-posta içeriğinin ve/veya e-postada yer alan bilgilerin kullanılması, kopyalanması, tekrar iletilmesi, yayınlanması ve başka herhangi bir surette kullanımı kesinlikle yasaktır. Bu e-postayı yanlışlıkla aldıysanız, lütfen gönderici ile iletişime geçiniz ve e-posta ve içeriğini derhal siliniz. Aksi açıkça ifade edilmediği müddetçe, bu e-posta ve içeriği bağlayıcı bir teklif ve/veya sözleşme niteliğinde değildir. Bu e-postadaki görüşler yalnızca gönderen kişiye aittir ve Samsung'un görüşlerini yansıtmayabilir. This e-mail (and its attachments) are intended solely for the use of the individual or entity to whom they are addressed and confidential and/or privileged; it may contain trade secrets. Any use, duplication, retransmission, dissemination or other use of the scope of the e-mail and/or the information exist in the e-mail is strictly prohibited. If you have received this in error, please contact the sender and delete the e-mail & its contents. Unless it is specifically stated, this e-mail & its content do not constitute any binding offer or contract. The opinions expressed in this e-mail belong to sender alone and may not necessarily reflect the opinions of Samsung.

4 6

[PROPOSED PATCH] * northamerica: Credit W.F. Allen's work on US time zones.
by Paul Eggert Sept. 21, 2016

Sept. 21, 2016

2016-09-11 Paul Eggert <eggert(a)cs.ucla.edu> Revert Cyprus change for now See: http://mm.icann.org/pipermail/tz/2016-September/024106.html --- northamerica | 26 ++++++++++++++++++++++++-- 1 file changed, 24 insertions(+), 2 deletions(-) diff --git a/northamerica b/northamerica index 0bafb00..6b0d905 100644 --- a/northamerica +++ b/northamerica @@ -24,8 +24,30 @@ # was the result of his proposals at the Convention of Railroad Trunk Lines # in New York City (1869-10). His 1870 proposal was based on Washington, DC, # but in 1872-05 he moved the proposed origin to Greenwich. -# His proposal was adopted by the railroads on 1883-11-18 at 12:00, -# and the most of the country soon followed suit. + +# From Paul Eggert (2016-09-20): +# Dowd's proposal left many details unresolved, such as where to draw +# lines between time zones. The key individual who made time zones +# work in the US was William Frederick Allen - railway engineer, +# managing editor of the Travelers' Guide, and secretary of the +# General Time Convention, a railway standardization group. Allen +# spent months in dialogs with with scientific and railway leaders, +# developed a workable plan to institute time zones, and presented it +# to the General Time Convention on 1883-04-11, saying that his plan +# meant "local time would be practically abolished" - a plus for +# railway scheduling. By the next convention on 1883-10-11 nearly all +# railroads had agreed and it took effect on 1883-11-18 at 12:00. +# Allen witnessed the transition in New York City, writing: +# +# I heard the bells of St. Paul's strike on the old time. Four +# minutes later, obedient to the electrical signal from the Naval +# Observatory ... the time-ball made its rapid descent, the chimes +# of old Trinity rang twelve measured strokes, and local time was +# abandoned, probably forever. +# +# Most of the US soon followed suit. See: +# Bartky IR. The adoption of standard time. Technol Cult 1989 Jan;30(1)25-56. +# http://dx.doi.org/10.2307/3105430 # From Paul Eggert (2005-04-16): # That 1883 transition occurred at 12:00 new time, not at 12:00 old time. -- 2.7.4

2 2

2016g tagged but not released
by Andreas Stieger Sept. 21, 2016

Sept. 21, 2016

Hello, I see that 2016g was tagged on github three days ago, but it was not put up on the IANA archive. https://github.com/eggert/tz/releases/tag/2016g Was there a problem with a script? Andreas -- Andreas Stieger <andreas.stieger(a)suse.com> Project Manager Security SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)

8 11

Backward compatibility of tzfile?
by Deborah Goldsmith Sept. 21, 2016

Sept. 21, 2016

Hi, Is the intent that successive versions of the tzfile format will be compatible with older implementations of localtime.c, date.c, etc.? Obviously they wouldn’t be able to take advantage of any new information, but is the idea they’ll still be able to read it? I wasn’t able to find anything in the man pages about this. Thanks, Debbie

3 2

Time zone change in Turkey
by Burak AYDIN Sept. 20, 2016

Sept. 20, 2016

Dear Paul, It is announced that Turkey will stay in Daylight Saving Time even in winter. Here is the related announcement from Turkish Government: http://www.resmigazete.gov.tr/eskiler/2016/09/20160908-2.pdf It says that we will not set the time 1 hour back at 30 October 2016. Best Regards, Burak AYDIN --- G?ZL?L?K NOTU: Bu e-posta mesaj? ki?iye ?zel olup, gizli bilgiler i?eriyor olabilir. E?er bu e-posta mesaj? size yanl??l?kla ula?m??sa, i?eri?ini hi? bir ?ekilde kullanmay?n?z ve ekli dosyalar? a?may?n?z. Bu durumda l?tfen e-posta mesaj?n? kullan?c?ya hemen geri g?nderiniz ve t?m kopyalar?n? mesaj kutunuzdan siliniz. Bu e-posta mesaj?, hi? bir ?ekilde, herhangi bir ama? i?in ?o?alt?lamaz, yay?nlanamaz ve para kar??l??? sat?lamaz. Bu e-posta mesaj?ndaki g?r??ler yaln?zca g?nderen ki?iye aittir ve Kentkart ?irketler Grubunun g?r??lerini yans?tmayabilir. Bu e-posta mesaj? vir?slere kars? anti-vir?s sistemleri taraf?ndan taranm??t?r. Ancak Kentkart ?irketler Grubu, bu e-posta mesaj?n?n -vir?s koruma sistemleri ile kontrol ediliyor olsa bile- vir?s i?ermedi?ini garanti etmez ve meydana gelebilecek zararlardan do?acak hi? bir sorumlulu?u kabul etmez. CONFIDENTIALITY NOTICE: This message is intended solely for the use of the individual or entity to whom it is addressed , and may contain confidential information. If you are not the intended recipient of this message or you receive this mail by mistake, you should refrain from making any use of the contents and from opening any attachment. In that case, please notify the sender immediately and return the message to the sender, then, delete and destroy all copies. This e-mail message, cannot be copied, published or sold for any reason. Any opinions presented in this email are solely those of the sender and may not necessarily reflect those of Kentkart Group of Companies. This e-mail message has been scanned by anti-virus systems for the presence of computer viruses. In doing so, however, Kentkart Group of Companies does not warrant that virus or other forms of data corruption and do not take any responsibility in any occurrence. ---

13 22

[PROPOSED PATCH 2/2] Use lz format for new tarball
by Antonio Diaz Diaz Sept. 20, 2016

Sept. 20, 2016

Paul Eggert wrote: >> please use a compression format that can be handled easily by >> Windows users as well. For instance, choose a format from the list >> that 7Zip can handle: http://www.7-zip.org/ > > Thanks for mentioning the problem. xz format is on 7-Zip's list; it's > a tiny bit larger than lzip format for our data (0.3% larger for the > draft tzdb tarball) but I suppose portability trumps this minor > advantage. Please, do not use xz for a new distribution format. The xz format is defective. See for example http://www.nongnu.org/lzip/xz_inadequate.html or the note in the third xz test at the bottom of http://www.nongnu.org/lzip/lzip_benchmark.html If a format that 7-Zip can handle is desired, I recommend bzip2 which produces a tzdb tarball a 25% smaller than gzip and only a 9% larger than lzip. Best regards, Antonio.

18 47

URL to get lz file
by tz.kovacsbv＠spamgourmet.com Sept. 20, 2016

Sept. 20, 2016

Hi, I'm trying to get the .lz file and the link in git ( https://github.com/eggert/tz/tree/2016g) is ftp://ftp.iana.org/tz/tzdb-latest.tar.lz But I browsed in there (ftp://ftp.iana.org/tz <ftp://ftp.iana.org/tz/tzdb-latest.tar.lz>) and there seems to be no .lz file. Vic Kovacs On Tue, Sep 20, 2016 at 11:57 AM, tz-request(a)iana.org < tz.kovacsbv.30ca297cb3.tz-request#iana.org(a)ob.0sg.net> wrote: > Send tz mailing list submissions to > tz(a)iana.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://mm.icann.org/mailman/listinfo/tz > or, via email, send a message with subject or body 'help' to > tz-request(a)iana.org > > You can reach the person managing the list at > tz-owner(a)iana.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of tz digest..." > > > Today's Topics: > > 1. Re: [PROPOSED PATCH 2/2] Use lz format for new tarball > (Deborah Goldsmith) > 2. Re: [PROPOSED PATCH 2/2] Use lz format for new tarball > (Alexander Belopolsky) > 3. Re: [PROPOSED PATCH 2/2] Use lz format for new tarball > (Alexander Belopolsky) > 4. Re: [PROPOSED PATCH 2/2] Use lz format for new tarball > (Alexander Belopolsky) > 5. Re: [PROPOSED PATCH 2/2] Use lz format for new tarball (Random832) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 20 Sep 2016 08:24:51 -0700 > From: Deborah Goldsmith <goldsmit(a)apple.com> > To: Russ Allbery <eagle(a)eyrie.org> > Cc: Time zone mailing list <tz(a)iana.org> > Subject: Re: [tz] [PROPOSED PATCH 2/2] Use lz format for new tarball > Message-ID: <7DCA4197-C9B9-4F2E-9594-A31F33C5398C(a)apple.com> > Content-Type: text/plain; charset=us-ascii > > As far as I can tell, lzip is only used on Linux. There are no tools that > ship with macOS or Windows (out of the box) that can decode it. > > Adopting lzip as the primary format at this point seems like a statement > that only Linux matters. > > Debbie > > > On Sep 7, 2016, at 2:01 PM, Russ Allbery <eagle(a)eyrie.org> wrote: > > > > Deborah Goldsmith <goldsmit(a)apple.com> writes: > > > >> Maybe we should wait until lzip is widely available before adopting it? > > > >> Meanwhile, bzip2 is already widely adopted, and is smaller than gzip. > > > > My impression is that bzip2 is dying and offers no great advantages at > > this point. Those who are looking for the best compression are using > > either xz or lzip. Those who care primarily about backward compatibility > > are using gzip. bzip2 is falling between those two stools: it's much > > newer than gzip and not as widely-supported, and it's larger (and I think > > slower to decompress although I could be wrong) than either xz or lzip. > > > > I would not introduce bzip2 into anything that wasn't already using it at > > this point. > > > > I think the current plan is a good one: stick with gzip for the > supported, > > stable distribution, add an experimental distribution that can play > around > > with compression and contents, and worry later (possibly much later) > about > > when the stable distribution might be worth changing. At some point, > gzip > > will probably go the way of compress, but we're not there yet. (It will > > probably take longer than the replacement of compress with gzip took, > > since there aren't patent issues driving the matter the way that there > > were for compress.) > > > > -- > > Russ Allbery (eagle(a)eyrie.org) < > http://www.eyrie.org/~eagle/> > > > > ------------------------------ > > Message: 2 > Date: Tue, 20 Sep 2016 11:42:46 -0400 > From: Alexander Belopolsky <alexander.belopolsky(a)gmail.com> > To: Deborah Goldsmith <goldsmit(a)apple.com> > Cc: Time zone mailing list <tz(a)iana.org> > Subject: Re: [tz] [PROPOSED PATCH 2/2] Use lz format for new tarball > Message-ID: > <CAP7h-xYroWJ0JEb_2y4wuKceb9jnKPS7LHdN0sP07yjkbm > vd2A(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > On Tue, Sep 20, 2016 at 11:24 AM, Deborah Goldsmith <goldsmit(a)apple.com> > wrote: > > > There are no tools that ship with macOS or Windows (out of the box) that > > can decode it. > > > > Neither of those systems come with a compiler out of the box either. On > MacOS, it takes less than 1.5 seconds to install lzip: > > $ time brew install lzip > ==> Downloading > https://homebrew.bintray.com/bottles/lzip-1.18.el_capitan.bottle.tar.gz > Already downloaded: > /Users/a/Library/Caches/Homebrew/lzip-1.18.el_capitan.bottle.tar.gz > ==> Pouring lzip-1.18.el_capitan.bottle.tar.gz > ? /usr/local/Cellar/lzip/1.18: 9 files, 166.4K > > real 0m1.124s > user 0m0.646s > sys 0m0.537s > > If you have trouble unpacking .tar.lz files - just point your browser to > > https://github.com/eggert/tz/tree/2016g > > and get whatever individual files you need. >

1 0

Turkish Governtment Decides to Stay on Daylight Saving Time
by Ozaydin Dolek Sept. 19, 2016

Sept. 19, 2016

Hi There, As you may have already heard by now , Turkish Governtment Decided to Stay on Daylight Saving Time (always summer time) When could be this change updated on IANA ? This is really urgent . Thx & BR Ozaydin Dolek Refs: http://www.timeanddate.com/news/time/turkey-scraps-dst-2016.html Official government doc: http://www.resmigazete.gov.tr/eskiler/2016/09/20160908-2.pdf -- Özaydın Dölek | Senior Principal Technical Account Manager Oracle EMEA Systems Support Phone: +90(212)3296825 | Fax: +90(212)3296701 ORACLE Turkey | UniqIstanbul Maslak-Ayazaga Caddesi No:4/B Kat:234485 Sarıyer / Istanbul

1 0

Time-zone file requirement for DST change in Turkey
by Deepak Gupta C Sept. 19, 2016

Sept. 19, 2016

Hi Team, There is a requirement from Government of Turkey to disable the DST in Turkey for 2016 i.e. the current time-zone EEST (GMT+3) should not be changed to EET(GMT+2) after 30th Oct 2016. We need the updated Time-Zone file for the same. Kindly support us to share the updated Time-Zone file. Please let us know in case of any more information required for the same. Regards Deepak Gupta Specialist - Customer Support RMEA T1C Mob: +919582111838

1 0

Uruguay considering DST again
by Carlos M. Martinez Sept. 13, 2016

Sept. 13, 2016

Link in Spanish: [http://www.elobservador.com.uy/evaluan-si-adelantan-la-hora-partir-octubre-…] Last year the Uruguayan Government decided at quite the last minute to *cancel* DST, causing the expected general havoc mostly on mobile phones. tks! -Carlos

1 0

[PROPOSED PATCH] Simplify strftime to pacify GCC 6.2
by Paul Eggert Sept. 12, 2016

Sept. 12, 2016

* strftime.c (strftime): Remove unnecessary checks against NULL that provoke diagnostics from 'gcc -Wnonnull-compare'. --- strftime.c | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/strftime.c b/strftime.c index f75f9fd..151b2e9 100644 --- a/strftime.c +++ b/strftime.c @@ -137,14 +137,11 @@ strftime(char *s, size_t maxsize, const char *format, const struct tm *t) tzset(); warn = IN_NONE; - p = _fmt(((format == NULL) ? "%c" : format), t, s, s + maxsize, &warn); + p = _fmt(format, t, s, s + maxsize, &warn); #ifndef NO_RUN_TIME_WARNINGS_ABOUT_YEAR_2000_PROBLEMS_THANK_YOU if (warn != IN_NONE && getenv(YEAR_2000_NAME) != NULL) { fprintf(stderr, "\n"); - if (format == NULL) - fprintf(stderr, "NULL strftime format "); - else fprintf(stderr, "strftime format \"%s\" ", - format); + fprintf(stderr, "strftime format \"%s\" ", format); fprintf(stderr, "yields only two digits of years in "); if (warn == IN_SOME) fprintf(stderr, "some locales"); -- 2.7.4

1 0

[PROPOSED PATCH] Update HTML documentation
by Paul Eggert Sept. 9, 2016

Sept. 9, 2016

* NEWS: Mention this. * tz-art.htm: Reorder sections to make the order more logical. Use list style for TV episodes and books. * tz-link.htm: Update description of local time on Mars to match current practice. Remove obsolete URLs and update URLs that moved. --- NEWS | 4 +- tz-art.htm | 388 ++++++++++++++++++++++++++++-------------------------------- tz-link.htm | 92 +++++--------- 3 files changed, 212 insertions(+), 272 deletions(-) diff --git a/NEWS b/NEWS index 64233bf..7d994c5 100644 --- a/NEWS +++ b/NEWS @@ -114,7 +114,9 @@ Unreleased, experimental changes tz-link.htm mentions JuliaTime (thanks to Curtis Vogt) and Time4J (thanks to Meno Hochschild) and ThreeTen-Extra, and its description of Java 8 has been brought up to date (thanks to - Stephen Colebourne). + Stephen Colebourne). Its description of local time on Mars has + been updated to match current practice, and URLs have been updated + and some obsolete ones removed. Release 2016f - 2016-07-05 16:26:51 +0200 diff --git a/tz-art.htm b/tz-art.htm index 08ef562..0a2b427 100644 --- a/tz-art.htm +++ b/tz-art.htm @@ -24,6 +24,184 @@ into problems that programmers have with timekeeping.</li> Bell Science extravaganza, with Frank Baxter, Richard Deacon, and Les Tremayne. (<a href="http://www.imdb.com/title/tt0154110/">IMDb entry</a>.)</li> </ul> +<h2>Movies</h2> +<ul> +<li> +In the 1946 movie <em>A Matter of Life and Death</em> +(U.S. title <em>Stairway to Heaven</em>) +there is a reference to British Double Summer Time. +The time does not play a large part in the plot; +it's just a passing reference to the time when one of the +characters was supposed to have died (but didn't). +The IMDb page is at +<a href="http://us.imdb.com/title/tt0038733/"> +http://us.imdb.com/title/tt0038733/ +</a>. (Dave Cantor) +<li> +The 1953 railway comedy movie <em>The Titfield Thunderbolt</em> includes a +play on words on British Double Summer Time. Valentine's wife wants +him to leave the pub and asks him, "Do you know what time it is?" +And he, happy where he is, replies: "Yes, my love. Summer double time." +IMDb page: +<a href="http://us.imdb.com/title/tt0046436/"> +http://us.imdb.com/title/tt0046436/ +</a>. (Mark Brader, 2009-10-02) +</li> +<li> +The premise of the 1999 caper movie <em>Entrapment</em> involves computers +in an international banking network being shut down briefly at +midnight in each time zone to avoid any problems at the transition +from the year 1999 to 2000 in that zone. (Hmmmm.) If this shutdown +is extended by 10 seconds, it will create a one-time opportunity for +a gigantic computerized theft. To achieve this, at one location the +crooks interfere with the microwave system supplying time signals to +the computer, advancing the time by 0.1 second each minute over the +last hour of 1999. (So this movie teaches us that 0.1 × 60 = 10.) +IMDb page: +<a href="http://us.imdb.com/title/tt0137494/"> +http://us.imdb.com/title/tt0137494/ +</a>. (Mark Brader, 2009-10-02) +</li> +<li> +One mustn't forget the +<a href="https://www.youtube.com/watch?v=k4EUTMPuvHo">trailer</a> +(2014; 2:23) for the movie <em>Daylight Saving</em>. +</li> +</ul> +<h2>TV episodes</h2> +<ul> +<li> +An episode of <em>The Adventures of Superman</em> entitled "The Mysterious +Cube," first aired 1958-02-24, had Superman convincing the controllers +of the Arlington Time Signal to broadcast ahead of actual time; +doing so got a crook trying to be declared dead to +emerge a bit too early from the titular enclosure. +</li> +<li> +The 1960s ITC television series <em>The Prisoner</em> included an episode +entitled "The Chimes of Big Ben" in which our protagonist tumbled to +the fraudulent nature of a Poland-to-England escape upon hearing "Big +Ben" chiming on Polish local time. +</li> +<li> +The series <em>Seinfeld</em> included an episode entitled "The Susie," first +broadcast 1997-02-13, in which Kramer decides that daylight saving time +isn't coming fast enough, so he sets his watch ahead an hour. +</li> +<li> +The "20 Hours in America" episode of <em>The West Wing</em>, +first aired 2002-09-25, contained a <a +href="https://www.youtube.com/watch?v=-J1NHzQ1sgc">scene</a> that +saw White House staffers stranded in Indiana; they thought they had time to +catch Air Force One but were done in by intra-Indiana local time changes. +</li> +<li> +"In what time zone would you find New York City?" was a $200 question on +the 1999-11-13 United States airing of <em>Who Wants to Be a Millionaire?</em>, +and "In 1883, what industry led the movement to divide the U.S. into four time +zones?" was a $32,000 question on the 2001-05-23 United States airing of +the same show. At this rate, the million-dollar time-zone +question should have been asked 2002-06-04. +</li> +<li> +A private jet's mid-flight change of time zones distorts Alison Dubois' +premonition in the "We Had a Dream" episode of <em>Medium</em> +(originally aired 2007-02-28). +</li> +<li> +In the <em>30 Rock</em> episode "Anna Howard Shaw Day" +(first broadcast 2010-02-11), +Jack Donaghy's date realizes that a Geneva-to-New-York business phone call +received in the evening must be fake given the difference in local times. +</li> +<li> +In the "Run by the Monkeys" episode of <em>Da Vinci's Inquest</em> +(first broadcast 2002-11-17), +a witness in a five-year-old fire case realizes they may not have set +their clock back when daylight saving ended on the day of the fire, +introducing the possibility of an hour when arson might have occurred. +</li> +<li> +In "The Todd Couple" episode of <em>Outsourced</em> (first aired 2011-02-10), +Manmeet sets up Valentine's Day teledates for 6:00 and 9:00pm; +since one is with a New Yorker and the other with a San Franciscan, +hilarity ensues. +(Never mind that this should be 7:30am in Mumbai, yet for some reason the show +proceeds as though it's also mid-evening there.) +</li> +<li> +In the "14 Days to Go"/"T Minus..." episode of +<em>You, Me and the Apocalypse</em> +(first aired 2015-11-11 in the UK, 2016-03-10 in the US), +the success of a mission to deal with a comet +hinges on whether or not Russia observes daylight saving time. +(In the US, the episode first aired in the week before the switch to DST.) +</li> +<li> +"The Lost Hour", <em>Eerie, Indiana</em>, episode 10, NBC, 1991-12-01. +Despite Indiana's then-lack of DST, Marshall changes his clock with +unusual consequences. +</li> +<li> +"Time Tunnel", <em>The Adventures of Pete & Pete</em>, season 2, episode 5, +Nickelodeon, 1994-10-23. +The two Petes travel back in time an hour on the day that DST ends. +</li> +<li> +"King-Size Homer", <em>The Simpsons</em>, episode 135, Fox, 1995-11-05. +Homer, working from home, remarks "8:58, first +time I've ever been early for work. Except for all those daylight +savings days. Lousy farmers." +</li> +<li> +"Tracks", <em>The Good Wife</em>, season 7, episode 12, +CBS, 2016-01-17. +The applicability of a contract hinges on the +time zone associated with a video time stamp. +</li> +</ul> +<h2>Books, plays, and magazines</h2> +<ul> +<li> +Jules Verne, <em>Around the World in Eighty Days</em> +(<em>Le tour du monde en quatre-vingts jours</em>). +Wall-clock time plays a central role in the plot. +European readers of the 1870s clearly held the U.S. press in +deep contempt; the protagonists cross the U.S. without once +reading a paper. +Available versions include +<a href="http://www.literature.org/Works/Jules-Verne/eighty">an English +translation</a>, and +<a href="http://fourmilab.ch/etexts/www/tdm80j">the original French</a> +"with illustrations from the original 1873 French-language edition". +</li> +<li> +Nick Enright, <em>Daylight Saving</em>, 1989. +A fast-paced comedy about love and loneliness as the clocks turn back. +</li> +<li> +Umberto Eco, <em>The Island of the Day Before</em> +(<em>L'isola del giorno prima</em>), 1994. +"...the story of a 17th century Italian nobleman trapped near an island +on the International Date Line. Time and time zones play an integral +part in the novel." (Paul Eggert, 2006-04-22) +</li> +<li> +John Dunning, <a +href="http://books.simonandschuster.com/Two-OClock-Eastern-Wartime/John-Dunning/9…"><em>Two +O'Clock, Eastern Wartime</em></a>, 2001. +Mystery, history, daylight saving time, and old-time radio. +</li> +<li> +Surrealist artist Guy Billout's work "Date Line" appeared on page 103 +of the 1999-11 <em>Atlantic Monthly</em>. +</li> +<li> +"Gloom, Gloom, Go Away" by Walter Kirn appeared on page 106 of <em>Time</em> +magazine's 2002-11-11 issue; among other things, it proposed +year-round DST as a way of lessening wintertime despair. +</li> +</ul> <h2>Music</h2> <p> Data on recordings of "Save That Time," Russ Long, Serrob Publishing, BMI:</p> @@ -254,216 +432,6 @@ Supernaw.</td></tr> <tr><td>Notes</td><td>Includes the piece "What Time Is It" ("He knew what time it was everywhere...that counted").</td></tr> </table> - -<h2>TV episodes</h2> - -<ul> -<li> -An episode of <em>The Adventures of Superman</em> entitled "The Mysterious -Cube," first aired 1958-02-24, had Superman convincing the controllers -of the Arlington Time Signal to broadcast ahead of actual time; -doing so got a crook trying to be declared dead to -emerge a bit too early from the titular enclosure. -</li> -<li> -The 1960s ITC television series <em>The Prisoner</em> included an episode -entitled "The Chimes of Big Ben" in which our protagonist tumbled to -the fraudulent nature of a Poland-to-England escape upon hearing "Big -Ben" chiming on Polish local time. -</li> -<li> -The series <em>Seinfeld</em> included an episode entitled "The Susie," first -broadcast 1997-02-13, in which Kramer decides that daylight saving time -isn't coming fast enough, so he sets his watch ahead an hour. -</li> -<li> -The "20 Hours in America" episode of <em>The West Wing</em>, -first aired 2002-09-25, contained a <a -href="https://www.youtube.com/watch?v=-J1NHzQ1sgc">scene</a> that -saw White House staffers stranded in Indiana; they thought they had time to -catch Air Force One but were done in by intra-Indiana local time changes. -</li> -<li> -"In what time zone would you find New York City?" was a $200 question on -the 1999-11-13 United States airing of <em>Who Wants to Be a Millionaire?</em>, -and "In 1883, what industry led the movement to divide the U.S. into four time -zones?" was a $32,000 question on the 2001-05-23 United States airing of -the same show. At this rate, the million-dollar time-zone -question should have been asked 2002-06-04. -</li> -<li> -A private jet's mid-flight change of time zones distorts Alison Dubois' -premonition in the "We Had a Dream" episode of <em>Medium</em> -(originally aired 2007-02-28). -</li> -<li> -In the <em>30 Rock</em> episode "Anna Howard Shaw Day" -(first broadcast 2010-02-11), -Jack Donaghy's date realizes that a Geneva-to-New-York business phone call -received in the evening must be fake given the difference in local times. -</li> -<li> -In the "Run by the Monkeys" episode of <em>Da Vinci's Inquest</em> -(first broadcast 2002-11-17), -a witness in a five-year-old fire case realizes they may not have set -their clock back when daylight saving ended on the day of the fire, -introducing the possibility of an hour when arson might have occurred. -</li> -<li> -In "The Todd Couple" episode of <em>Outsourced</em> (first aired 2011-02-10), -Manmeet sets up Valentine's Day teledates for 6:00 and 9:00pm; -since one is with a New Yorker and the other with a San Franciscan, -hilarity ensues. -(Never mind that this should be 7:30am in Mumbai, yet for some reason the show -proceeds as though it's also mid-evening there.) -</li> -<li> -In the "14 Days to Go"/"T Minus..." episode of -<em>You, Me and the Apocalypse</em> -(first aired 2015-11-11 in the UK, 2016-03-10 in the US), -the success of a mission to deal with a comet -hinges on whether or not Russia observes daylight saving time. -(In the US, the episode first aired in the week before the switch to DST.) -</li> -</ul> - -<table> -<tr><td>TV episode title</td><td>The Lost Hour</td> -<tr><td>TV series</td><td><em>Eerie, Indiana</em></td> -<tr><td>TV episode number</td><td>10</td> -<tr><td>Network</td><td>NBC</td> -<tr><td>Air date</td><td>1991-12-01</td> -<tr><td>Notes</td><td>Despite Indiana's then-lack of DST, Marshall changes his clock with unusual consequences.</td></tr> -<tr><td> </td></tr> - -<tr><td>TV episode title</td><td>Time Tunnel</td> -<tr><td>TV series</td><td><em>The Adventures of Pete & Pete</em></td> -<tr><td>TV episode number</td><td>5, season 2</td> -<tr><td>Network</td><td>Nickelodeon</td> -<tr><td>Air date</td><td>1994-10-23</td> -<tr><td>Notes</td><td>The two Petes travel back in time an hour on the day that DST ends.</td></tr> -<tr><td> </td></tr> - -<tr><td>TV episode title</td><td>King-Size Homer</td> -<tr><td>TV series</td><td><em>The Simpsons</em></td> -<tr><td>TV episode number</td><td>135</td> -<tr><td>Network</td><td>Fox</td> -<tr><td>Air date</td><td>1995-11-05</td> -<tr><td>Notes</td><td>Homer, working from home, remarks "8:58, first -time I've ever been early for work. Except for all those daylight -savings days. Lousy farmers."</td></tr> -<tr><td> </td></tr> - -<tr><td>TV episode title</td><td>Tracks</td></tr> -<tr><td>TV series</td><td><em>The Good Wife</em></td></tr> -<tr><td>TV episode number</td><td>12, season 7</td></tr> -<tr><td>Network</td><td>CBS</td></tr> -<tr><td>Air date</td><td>2016-01-17</td></tr> -<tr><td>Notes</td><td>The applicability of a contract hinges on the -time zone associated with a video time stamp.</td></tr> -</table> - -<h2>Books, plays, and magazines</h2> - -<table> -<tr><td>Artist</td><td>Jules Verne</td></tr> -<tr><td>Book</td><td><em>Around the World in Eighty Days</em> -(<em>Le tour du monde en quatre-vingts jours</em>)</td></tr> -<tr><td>Notes</td><td>Wall-clock time plays a central role in the plot. -European readers of the 1870s clearly held the U.S. press in -deep contempt; the protagonists cross the U.S. without once -reading a paper. -An on-line French-language version of the book -"with illustrations from the original 1873 French-language edition" -is available at -<a href="http://fourmilab.ch/etexts/www/tdm80j">http://fourmilab.ch/etexts/www/tdm80j</a> -An on-line English-language translation of the book is available at -<a href="http://www.literature.org/Works/Jules-Verne/eighty">http://www.literature.org/Works/Jules-Verne/eighty</a></td></tr> - -<tr><td> </td></tr> -<tr><td>Artist</td><td>Nick Enright</td></tr> -<tr><td>Play</td><td><em>Daylight Saving</em></td></tr> -<tr><td>Copyright Date</td><td>1989</td></tr> -<tr><td>Notes</td><td> -A fast-paced comedy about love and loneliness as the clocks turn back. -</td></tr> - -<tr><td> </td></tr> -<tr><td>Artist</td><td>Umberto Eco</td></tr> -<tr><td>Book</td><td><em>The Island of the Day Before</em> -(<em>L'isola del giorno prima</em>)</td></tr> -<tr><td>Copyright Date</td><td>1994</td></tr> -<tr><td>Notes</td><td> -"...the story of a 17th century Italian nobleman trapped near an island -on the International Date Line. Time and time zones play an integral -part in the novel." (Paul Eggert, 2006-04-22) -</td></tr> -<tr><td> </td></tr> -<tr><td>Artist</td><td>John Dunning</td></tr> -<tr><td>Book</td><td><a -href="http://books.simonandschuster.com/Two-OClock-Eastern-Wartime/John-Dunning/9…"><em>Two -O'Clock, Eastern Wartime</em></a></td></tr> -<tr><td>Copyright Date</td><td>2001</td></tr> -<tr><td>Notes</td><td> -Mystery, history, daylight saving time, and old-time radio. -</td></tr> -</table> -<hr> -<ul> -<li> -Surrealist artist Guy Billout's work "Date Line" appeared on page 103 -of the 1999-11 <em>Atlantic Monthly</em>. -</li> -<li> -"Gloom, Gloom, Go Away" by Walter Kirn appeared on page 106 of <em>Time</em> -magazine's 2002-11-11 issue; among other things, it proposed -year-round DST as a way of lessening wintertime despair. -</li> -</ul> -<h2>Movies</h2> -<ul> -<li> -In the 1946 movie <em>A Matter of Life and Death</em> -(U.S. title <em>Stairway to Heaven</em>) -there is a reference to British Double Summer Time. -The time does not play a large part in the plot; -it's just a passing reference to the time when one of the -characters was supposed to have died (but didn't). -The IMDb page is at -<a href="http://us.imdb.com/title/tt0038733/"> -http://us.imdb.com/title/tt0038733/ -</a>. (Dave Cantor) -<li> -The 1953 railway comedy movie <em>The Titfield Thunderbolt</em> includes a -play on words on British Double Summer Time. Valentine's wife wants -him to leave the pub and asks him, "Do you know what time it is?" -And he, happy where he is, replies: "Yes, my love. Summer double time." -IMDb page: -<a href="http://us.imdb.com/title/tt0046436/"> -http://us.imdb.com/title/tt0046436/ -</a>. (Mark Brader, 2009-10-02) -</li> -<li> -The premise of the 1999 caper movie <em>Entrapment</em> involves computers -in an international banking network being shut down briefly at -midnight in each time zone to avoid any problems at the transition -from the year 1999 to 2000 in that zone. (Hmmmm.) If this shutdown -is extended by 10 seconds, it will create a one-time opportunity for -a gigantic computerized theft. To achieve this, at one location the -crooks interfere with the microwave system supplying time signals to -the computer, advancing the time by 0.1 second each minute over the -last hour of 1999. (So this movie teaches us that 0.1 × 60 = 10.) -IMDb page: -<a href="http://us.imdb.com/title/tt0137494/"> -http://us.imdb.com/title/tt0137494/ -</a>. (Mark Brader, 2009-10-02) -</li> -<li> -One mustn't forget the -<a href="https://www.youtube.com/watch?v=k4EUTMPuvHo">trailer</a> -(2014; 2:23) for the movie <em>Daylight Saving</em>. -</li> -</ul> <h2>Comics</h2> <ul> <li> diff --git a/tz-link.htm b/tz-link.htm index 52bb492..8964490 100644 --- a/tz-link.htm +++ b/tz-link.htm @@ -10,7 +10,7 @@ content="Sources for time zone and daylight saving time data"> <meta name="DC.Creator" content="Eggert, Paul"> <meta name="DC.Contributor" content="Olson, Arthur David"> -<meta name="DC.Date" content="2016-09-05"> +<meta name="DC.Date" content="2016-09-09"> <meta name="DC.Description" content="Sources of information about time zones and daylight saving time"> <meta name="DC.Identifier" @@ -65,13 +65,13 @@ title="Advanced Interactive eXecutive">AIX</abbr></a>, <a href="https://en.wikipedia.org/wiki/BlackBerry_10">BlackBerry 10</a>, <a href="http://www.apple.com/ios/"><abbr title="iPhone OS">iOS</abbr></a>, -<a href="http://windows.microsoft.com">Microsoft Windows</a>, +<a href="http://www.apple.com/macos/"><abbr +title="Mac Operating System">macOS</abbr></a>, +<a href="https://www.microsoft.com/en-us/windows">Microsoft Windows</a>, <a href="http://www.hp.com/go/openvms/">Open<abbr title="Virtual Memory System">VMS</abbr></a>, -<a href="https://www.oracle.com/database/index.html">Oracle Database</a>, -<a href="http://oracle.com/solaris">Oracle Solaris</a>, and -<a href="http://www.apple.com/osx/"><abbr title="Operating System Ten">OS -X</abbr></a>.</p> +<a href="https://www.oracle.com/database/index.html">Oracle Database</a>, and +<a href="https://www.oracle.com/solaris">Oracle Solaris</a>.</p> <p> Each location in the database represents a region where all clocks keeping local time have agreed since 1970. @@ -103,7 +103,7 @@ for time stamps after 1960 this is more precisely <a href="https://en.wikipedia.org/wiki/Coordinated_Universal_Time">Coordinated Universal Time</a> (<abbr>UTC</abbr>). The database also records when daylight saving time was in use, -along with alphabetic time zone abbreviations such as <abbr>EST</abbr> +along with some time zone abbreviations such as <abbr>EST</abbr> for Eastern Standard Time in the <abbr>US</abbr>.</p> <p> The following <a @@ -142,7 +142,7 @@ of the <a href="http://www.iana.org">Internet Assigned Numbers Authority (IANA)</a>. An <a href="https://github.com/eggert/tz">unofficial development repository</a> of the code and data is available -in <a href="http://git-scm.com">Git</a> form +in <a href="https://git-scm.com">Git</a> form from <a href="https://github.com">GitHub</a>; be careful, as this repository is less well tested and probably contains more errors. <p> @@ -208,7 +208,7 @@ the Timing of Time Zone Changes</a> gives examples of problems caused by inadequate notice by governments of time zone and daylight saving rule changes.</li> <li><a -href="http://blog.jonudell.net/2009/10/23/a-literary-appreciation-of-the-olsonzon…">A +href="https://blog.jonudell.net/2009/10/23/a-literary-appreciation-of-the-olsonzo…">A literary appreciation of the Olson/Zoneinfo/tz database</a> comments on the database's style.</li> </ul> @@ -244,15 +244,14 @@ names and shows location maps.</li> </ul> <h2>Network protocols for <code><abbr>tz</abbr></code> data</h2> <ul> -<li>The <a href="http://www.ietf.org">Internet Engineering Task Force</a>'s +<li>The <a href="https://www.ietf.org">Internet Engineering Task Force</a>'s <a href="https://datatracker.ietf.org/wg/tzdist/charter/">Time Zone Data Distribution Service (tzdist) working group</a> defined <a href="https://tools.ietf.org/html/rfc7808">TZDIST</a> (Internet <abbr>RFC</abbr> 7808), a time zone data distribution service, along with a <a href="https://tools.ietf.org/html/rfc7809">calendar access protocol for transferring time zone data by reference</a> -(Internet <abbr>RFC</abbr> 7809). This work was based -on the iCalendar and CalConnect efforts described below.</li> +(Internet <abbr>RFC</abbr> 7809).</li> <li>The <a href="https://tools.ietf.org/html/rfc5545"> Internet Calendaring and Scheduling Core Object Specification (iCalendar)</a> (Internet <abbr>RFC</abbr> 5445) @@ -261,35 +260,12 @@ data; see its VTIMEZONE calendar component. The iCalendar format requires specialized parsers and generators; a variant <a href="https://tools.ietf.org/html/rfc6321">xCal</a> (Internet <abbr>RFC</abbr> 6321) uses -<a href="http://www.w3.org/XML/"><abbr +<a href="https://www.w3.org/XML/"><abbr title="Extensible Markup Language">XML</abbr></a> format, and a variant <a href="https://tools.ietf.org/html/rfc7265">jCal</a> (Internet <abbr>RFC</abbr> 7265) uses <a href="http://www.json.org"><abbr -title="JavaScript Object Notation">JSON</abbr></a> format. -<a href="https://www.calconnect.org">CalConnect, The Calendaring and Scheduling -Consortium</a> is promoting further work in this area. <a -href="http://calconnect.org/publications/icalendartimezoneproblemsandrecommendati…">iCalendar -TIMEZONE Problems and Recommendations</a> offers guidelines and -recommendations for the use of VTIMEZONE and <code><abbr>tz</abbr></code>.</li> -<li>The <a -href="http://calconnect.org/publications/timezoneregistryandservicerecommendation…">Timezone -Registry and Service Recommendations</a> of CalConnect's -<a href="https://www.calconnect.org/about/technical-committees/tc-timezone">TIMEZONE -Technical Committee</a> discusses a -strategy for defining and deploying a time zone -registration process that would establish unique names for each -version of each <code><abbr>tz</abbr></code> zone, along with a polygonal -representation of the geographical area corresponding to the -zone.</li> -<li>The <a -href="http://lists.w3.org/Archives/Public/www-rdf-calendar/">www-rdf-calendar</a> -list discusses <a -href="http://www.w3.org/RDF/"><abbr -title="Resource Description Framework">RDF</abbr></a>-based calendar -and group scheduling systems, and has a <a -href="http://www.w3.org/2002/12/cal/#tzd">workspace on time zone -data</a> converted from <code><abbr>tz</abbr></code>.</li> +title="JavaScript Object Notation">JSON</abbr></a> format.</li> </ul> <h2>Other <code><abbr>tz</abbr></code> compilers</h2> <ul> @@ -423,7 +399,8 @@ has an independent, thread-safe implementation of a <code><abbr>tz</abbr></code> binary file reader. This library is freely available under the LGPL and is widely used in <abbr>GNU</abbr>/Linux systems.</li> -<li><a href="https://www.gnome.org">GNOME</a>'s Glib has +<li><a href="https://www.gnome.org">GNOME</a>'s +<a href="https://developer.gnome.org/glib/">GLib</a> has a <code><abbr>tz</abbr></code> binary file reader written in C that creates a <code>GTimeZone</code> object representing sets of <abbr>UT</abbr> offsets. @@ -542,7 +519,8 @@ is another time zone database.</li> <li><a href="http://tycho.usno.navy.mil/tzones.html">World Time Zones</a> contains data from the Time Service Department of the <abbr>US</abbr> Naval Observatory.</li> -<li>The <a href="http://www.iata.org/publications/Pages/ssim.aspx">Standard +<li>The <a +href="http://www.iata.org/publications/store/Pages/standard-schedules-information…">Standard Schedules Information Manual</a> of the International Air Transport Association gives current time zone rules for airports served by commercial aviation.</li> @@ -613,7 +591,7 @@ common.</li> </ul> <h2>Civil time concepts and history</h2> <ul> -<li><a href="http://www.nist.gov/pml/general/time/index.cfm">A +<li><a href="http://physics.nist.gov/time">A Walk through Time</a> surveys the evolution of timekeeping.</li> <li><a href="http://www.webexhibits.org/daylightsaving/">About Daylight @@ -622,8 +600,6 @@ is an overall history of <abbr>DST</abbr>.</li> <li><a href="https://www.w3.org/TR/timezone/">Working with Time Zones</a> contains guidelines and best practices for software applications that deal with civil time.</li> -<li><a href="http://energy.ca.gov/daylightsaving.html">Saving Time, -Saving Energy</a> discusses a primary justification for <abbr>DST</abbr>.</li> <li><a href="http://seizethedaylight.com/dst/">A Brief History of Daylight Saving Time</a> summarizes some of the contentious history of <abbr>DST</abbr>.</li> @@ -681,7 +657,7 @@ hreflang="nl">Legal time in the Netherlands (in Dutch)</a> covers the history of local time in the Netherlands from ancient times.</dd> <dt>New Zealand</dt> <dd>The Department of Internal Affairs maintains a brief <a -href="http://www.dia.govt.nz/Daylight-Saving-History">History of +href="https://www.dia.govt.nz/Daylight-Saving-History">History of Daylight Saving</a>. The privately-maintained <a href="http://astrologyschool.com/nztime.html">History of New Zealand time</a> has more details.</dd> @@ -714,7 +690,8 @@ title="Network Time Protocol">NTP</abbr>: The Network Time Protocol</a> discusses how to synchronize clocks of Internet hosts.</li> -<li>The <a href="http://www.nist.gov/el/isd/ieee/ieee1588.cfm">Precision +<li>The <a +href="https://www.nist.gov/intelligent-systems-division/ieee-1588">Precision Time Protocol</a> (<abbr title="Institute of Electrical and Electronics Engineers">IEEE</abbr> 1588) can achieve submicrosecond clock accuracy on a local area network.</li> @@ -726,11 +703,6 @@ specifies a <a href="https://en.wikipedia.org/wiki/Dynamic_Host_Configuration_Protocol"><abbr>DHCP</abbr></a> option for a server to configure a client's time zone and daylight saving settings automatically.</li> -<li><a href="http://gauss.gge.unb.ca/GMT.UT.and.the.RGO.html">A Few Facts -Concerning <abbr>GMT</abbr>, <abbr>UT</abbr>, and -the <abbr title="Royal Greenwich Observatory">RGO</abbr></a> -answers questions like "What is the -difference between <abbr>GMT</abbr> and <abbr>UTC</abbr>?"</li> <li><a href="http://www.cv.nrao.edu/~rfisher/Ephemerides/times.html">Astronomical Times</a> explains more abstruse astronomical time scales like @@ -739,7 +711,7 @@ Times</a> explains more abstruse astronomical time scales like <abbr title="Barycentric Dynamic Time">TDB</abbr>. <a href="http://www.ucolick.org/~sla/leapsecs/timescales.html">Time Scales</a> goes into more detail, particularly for historical variants.</li> -<li>The <a href="http://iau.org"><abbr +<li>The <a href="http://www.iau.org"><abbr title="International Astronomical Union">IAU</abbr></a>'s <a href="http://www.iausofa.org"><abbr title="Standards Of Fundamental Astronomy">SOFA</abbr></a> @@ -753,10 +725,8 @@ code for converting among time scales like Space Flight – Reference Systems – Time Conventions</a> briefly explains interplanetary space flight timekeeping.</li> <li><a -href="http://www.giss.nasa.gov/tools/mars24/help/notes.html">Technical -Notes on Mars Solar Time as Adopted by the Mars24 Sunclock</a> briefly -describes Mars Coordinated Time (<abbr -title="Mars Coordinated Time">MTC</abbr>) and the +href="http://www.giss.nasa.gov/tools/mars24/help/notes.html">Mars24 Sunclock +– Time on Mars</a> describes Airy Mean Time (<abbr>AMT</abbr>) and the diverse local time scales used by each landed mission on Mars.</li> <li><a href="http://leapsecond.com">LeapSecond.com</a> is @@ -772,7 +742,7 @@ when leap seconds occur.</li> <li>The <a href="https://pairlist6.pair.net/mailman/listinfo/leapsecs">Leap Second Discussion List</a> covers <a -href="http://gauss.gge.unb.ca/papers.pdf/gpsworld.november99.pdf">McCarthy +href="http://www2.unb.ca/gge/Resources/gpsworld.november99.pdf">McCarthy and Klepczynski's proposal to discontinue leap seconds</a>, discussed further in <a href="http://www.cl.cam.ac.uk/~mgk25/time/metrologia-leapsecond.pdf">The @@ -790,7 +760,7 @@ zone names, abbreviations, identifiers, and formats. For example, it contains French translations for "Eastern European Summer Time", "<abbr title="Eastern European Summer Time">EEST</abbr>", and "Bucharest". Its -<a href="http://unicode.org/cldr/charts/by_type/index.html">by-type +<a href="http://www.unicode.org/cldr/charts/latest/by_type/">by-type charts</a> show these values for many locales. Data values are available in both <abbr title="Locale Data Markup Language">LDML</abbr> (an <abbr>XML</abbr> format) and <abbr>JSON</abbr>. @@ -834,10 +804,10 @@ practice. For example, in English-speaking North America but in China it denotes 8 hours ahead of <abbr>UTC</abbr>, and French-speaking North Americans prefer "<abbr title="Heure Normale du Centre">HNC</abbr>" to -"<abbr>CST</abbr>". For <abbr>POSIX</abbr> the <code><abbr>tz</abbr></code> -database contains English abbreviations for all time stamps but in -many cases these are merely inventions of the database -maintainers.</li> +"<abbr>CST</abbr>". The <code><abbr>tz</abbr></code> +database contains English abbreviations for many time stamps; +unfortunately some of these abbreviations were merely the database maintainers' +inventions, and are gradually being removed.</li> <li>Numeric time zone abbreviations typically count hours east of <abbr>UTC</abbr>, e.g., +09 for Japan and −10 for Hawaii. However, the <abbr>POSIX</abbr> @@ -852,7 +822,7 @@ settings like <code><abbr>TZ</abbr>="Asia/Tokyo"</code> and confusion, handle old time stamps better, and insulate you better from any future changes to the rules. One should never set <abbr>POSIX</abbr> <code><abbr>TZ</abbr></code> to a value like -<code>"GMT-9"</code>, though, since this would falsely claim that +<code>"GMT-9"</code>, though, since this would incorrectly imply that local time is nine hours ahead of <abbr>UTC</abbr> and the time zone is called "<abbr>GMT</abbr>".</li> </ul> -- 2.7.4

1 0

About decision of Turkey to end DST ...
by askin senel Sept. 9, 2016

Sept. 9, 2016

Hello, When do you plan to update the tz database with recent Turkish decision to end DST. See https://www.timeanddate.com/news/time/turkey-scraps-dst-2016.html Kind Regards. Askin

2 1

tzdist and tz@iana
by Alexander Belopolsky Sept. 8, 2016

Sept. 8, 2016

On Wed, Sep 7, 2016 at 4:04 AM, Jon Skeet <skeet(a)pobox.com> wrote: > (Then there's tzdist of course, but that's a whole other matter...) I have been looking at RFC 7808 (aka tzdist) and I wonder what is the relationship between the proposed distribution standard and this project. While RFC 7808 mentions "Olson" as a possible "primary-source", it does not look like the proposed JSON format is capable of carrying all information provided by Olson raw files. The distribution format looks like a text variant of the binary zoneinfo files, but it is not clear whether or not the distributed data includes timezone abbreviations. Are there any plans to support the tzdist format in tzcode? Will IANA run its own "Time Zone Data Server"?

7 18

Rangoon to Yangon
by David Massoud Sept. 8, 2016

Sept. 8, 2016

Myanmar's former capital and most populous city is currently known as Yangon. In 1989 Burma was renamed Myanmar (which you have reflected in the Asia data file). At the same time, Rangoon was renamed Yangon, which is currently not reflected in the codebase. http://www.forbestravelguide.com/yangon-myanmar/whats-the-difference-betwee… . -- David Massoud http://lnked.in/DavidMassoud

2 1

Turkey to keep permanent DST
by Even Scharning Sept. 8, 2016

Sept. 8, 2016

Turkey will stay on DST, canceling October's transition back to UTC +2 standard time, according to Hürriyet, Turkey's "leading news source". http://www.hurriyet.com.tr/kis-saati-uygulamasi-yururlukten-kaldirildi-4021… Time in Turkey: http://time.is/Turkey Even Scharning Time.is - exact time for any time zone http://time.is/

3 4

Google search results displaying wrong time for Egypt
by Andrew Paprocki Sept. 7, 2016

Sept. 7, 2016

If you search for "current time in Egypt" (at least for me in NYC), it will display a UTC+3 time as if DST was applied (tzdata2016f not being used). In case there are any Googlers on the list want to raise awareness internally... -Andrew

7 11

[PROPOSED PATCH 1/5] zic now omits some mkdir and stat system calls
by Paul Eggert Sept. 6, 2016

Sept. 6, 2016

* NEWS: Document this. * zic.c (mkdirs): Do not mkdir a root directory. Avoid unnecessary stat call. --- NEWS | 2 ++ zic.c | 24 +++++++++++++----------- 2 files changed, 15 insertions(+), 11 deletions(-) diff --git a/NEWS b/NEWS index f5a0b13..192deb7 100644 --- a/NEWS +++ b/NEWS @@ -55,6 +55,8 @@ Unreleased, experimental changes stamps on the reference platform. (Thanks to Alexander Belopolsky for reporting the bug and suggesting a way forward.) + zic now avoids some unnecessary mkdir and stat system calls. + zdump has a new -i option to generate transitions in a more-compact but still human-readable format. This option is experimental, and the output format may change in future versions. diff --git a/zic.c b/zic.c index b8bd0a6..5ff78b4 100644 --- a/zic.c +++ b/zic.c @@ -3027,25 +3027,27 @@ mkdirs(char *argname) if (argname == NULL || *argname == '\0') return true; cp = name = ecpyalloc(argname); - while ((cp = strchr(cp + 1, '/')) != 0) { - *cp = '\0'; + + /* Do not mkdir a root directory, as it must exist. */ #ifdef HAVE_DOS_FILE_NAMES - /* - ** DOS drive specifier? - */ - if (is_alpha(name[0]) && name[1] == ':' && name[2] == '\0') { - *cp = '/'; - continue; - } + if (is_alpha(name[0]) && name[1] == ':') + cp += 2; #endif + while (*cp == '/') + cp++; + + for (; (cp = strchr(cp, '/')) != 0; cp++) { + *cp = '\0'; /* ** Try to create it. It's OK if creation fails because ** the directory already exists, perhaps because some - ** other process just created it. + ** other process just created it. For simplicity do + ** not check first whether it already exists, as that + ** is checked anyway if the mkdir fails. */ if (mkdir(name, MKDIR_UMASK) != 0) { int err = errno; - if (itsdir(name) <= 0) { + if (err != EEXIST && itsdir(name) <= 0) { char const *e = strerror(err); warning(_("%s: Can't create directory" " %s: %s"), -- 2.7.4

1 4

[PROPOSED PATCH 1/3] Call the new tarball experimental
by Paul Eggert Sept. 6, 2016

Sept. 6, 2016

* Makefile (tzdata$(VERSION).tar.gz): Omit $(TZS). * NEWS: Call the new format experimental, and say it has to2050.tzs. Do not imply a time limit for the old format. * README, tz-link.htm: Bring back traditional two-tarball recipe. * tz-how-to.html: Defer to tz-link.htm for tarball link. * tz-link.htm: Update some URLs. --- Makefile | 2 +- NEWS | 33 ++++++++++++++++----------------- README | 11 +++++++++++ tz-how-to.html | 3 +-- tz-link.htm | 52 ++++++++++++++++++++++++++++------------------------ 5 files changed, 57 insertions(+), 44 deletions(-) diff --git a/Makefile b/Makefile index 90363e9..31a2ec5 100644 --- a/Makefile +++ b/Makefile @@ -683,7 +683,7 @@ tzcode$(VERSION).tar.gz: set-timestamps.out tzdata$(VERSION).tar.gz: set-timestamps.out LC_ALL=C && export LC_ALL && \ - tar $(TARFLAGS) -cf - $(COMMON) $(DATA) $(MISC) $(TZS) | \ + tar $(TARFLAGS) -cf - $(COMMON) $(DATA) $(MISC) | \ gzip $(GZIPFLAGS) > $@ tzdb-$(VERSION).tar.lz: set-timestamps.out diff --git a/NEWS b/NEWS index e61a992..6cbdbd7 100644 --- a/NEWS +++ b/NEWS @@ -63,20 +63,18 @@ Unreleased, experimental changes Changes to build procedure - The tz distribution has a new file to2050.tzs that contains what - should be the output of 'zdump -i -c 2050' on primary zones. - 'make check' now checks that zdump generates this output. - - A new distribution format is available in the tarball - tzdb-VERSION.tar.lz and the signature tzdb-VERSION.tar.lz.asc. - The new tarball has the contents of tzcodeVERSION.tar.gz and - tzdataVERSION.tar.gz, in a single top-level directory 'tzdb' with - all other files under this directory, as is typical for software - distributions. The new format is intended to replace the old - tarball pair. The old format will continue to be distributed for - a while. The new format uses lzip compression, which is smaller - than gzip; see <http://www.nongnu.org/lzip/lzip.html>. - (Thanks to Antonio Diaz Diaz and Oscar van Vlijmen for comments.) + An experimental distribution format is available in the tarball + tzdb-VERSION.tar.lz with signature file tzdb-VERSION.tar.lz.asc. + It unpacks to a top-level directory containing the code and data + of the traditional two-tarball format, along with extra data that + may be useful. The traditional format will continue to be + distributed. (Thanks to Antonio Diaz Diaz, Oscar van Vlijmen, and + many others for comments about the experimental format.) + + The experimental distribution contains a file to2050.tzs that + contains what should be the output of 'zdump -i -c 2050' on + primary zones. If this file is available, 'make check' now checks + that zdump generates this output. 'make check_web' now works on Fedora-like distributions. @@ -3613,14 +3611,15 @@ This file contains copies of the part of each release announcement that talks about the changes in that release. The text has been adapted and reformatted for the purposes of this file. -Typically a release R consists of a pair of tarball files, +Traditionally a release R consists of a pair of tarball files, tzcodeR.tar.gz and tzdataR.tar.gz. However, some releases (e.g., code2010a, data2012c) consist of just one or the other tarball, and a few (e.g., code2012c-data2012d) have tarballs with mixed version -numbers. +numbers. Recent releases also come in an experimental format +consisting of a single tarball tzdb-R.tar.lz with extra data. Release time stamps are taken from the release's commit (for newer, -git releases), from the newest file in the tarball (for older +Git-based releases), from the newest file in the tarball (for older releases, where this info is available) or from the email announcing the release (if all else fails; these are marked with a time zone of -0000 and an "is missing!" comment). diff --git a/README b/README index ba0b790..8a09aa2 100644 --- a/README +++ b/README @@ -13,6 +13,17 @@ and daylight-saving rules. Here is a recipe for acquiring, building, installing, and testing the tz distribution on a GNU/Linux or similar host. +To acquire the distribution, run the following shell commands: + + mkdir tz + cd tz + wget --retr-symlinks 'ftp://ftp.iana.org/tz/tz*-latest.tar.gz' + gzip -dc tzcode-latest.tar.gz | tar -xf - + gzip -dc tzdata-latest.tar.gz | tar -xf - + +Alternatively, the following shell commands acquire the same +distribution, with extra data useful for regression testing: + wget --retr-symlinks 'ftp://ftp.iana.org/tz/tzdb-latest.tar.lz' lzip -dc tzdb-latest.tar.lz | tar -xf - diff --git a/tz-how-to.html b/tz-how-to.html index 7d9d521..a94759e 100644 --- a/tz-how-to.html +++ b/tz-how-to.html @@ -12,8 +12,7 @@ Database</a> Source Files</h2> times of day from the <a href="tz-link.htm">tz database</a> source files. It might be helpful, but not absolutely necessary, for the reader to have already downloaded the -<a href="http://www.iana.org/time-zones/repository/tzdb-latest.tar.lz">latest -release of the database</a> and become familiar with the basic layout +latest release of the database and become familiar with the basic layout of the data files. The format is explained in the “man page” for the zic compiler, <code>zic.8.txt</code>, in the <code>code</code> subdirectory.</p> diff --git a/tz-link.htm b/tz-link.htm index 8b05470..52bb492 100644 --- a/tz-link.htm +++ b/tz-link.htm @@ -10,7 +10,7 @@ content="Sources for time zone and daylight saving time data"> <meta name="DC.Creator" content="Eggert, Paul"> <meta name="DC.Contributor" content="Olson, Arthur David"> -<meta name="DC.Date" content="2016-08-30"> +<meta name="DC.Date" content="2016-09-05"> <meta name="DC.Description" content="Sources of information about time zones and daylight saving time"> <meta name="DC.Identifier" @@ -42,7 +42,7 @@ This database (often called <code>zoneinfo</code> or <code><abbr>tz</abbr></code>) is used by several implementations, including -<a href="http://www.gnu.org/software/libc/">the +<a href="https://www.gnu.org/software/libc/">the <abbr title="GNU's Not Unix">GNU</abbr> C Library</a> (used in <a href="https://en.wikipedia.org/wiki/Linux"><abbr>GNU</abbr>/Linux</a>), @@ -108,33 +108,35 @@ for Eastern Standard Time in the <abbr>US</abbr>.</p> <p> The following <a href="https://en.wikipedia.org/wiki/Unix_shell">shell</a> commands download -the latest release to a <abbr>GNU</abbr>/Linux or similar host; -see the downloaded -<code>README</code> file for what to do next.</p> -<pre style="margin-left: 2em"><code><a href="http://www.gnu.org/software/wget/">wget</a> --retr-symlinks 'ftp://ftp.iana.org/tz/tzdb-latest.tar.lz' -<a href="http://www.nongnu.org/lzip/">lzip</a> -dc tzdb-latest.tar.lz | <a href="http://www.gnu.org/software/tar/">tar</a> -xf - +the latest release's two +<a href="https://en.wikipedia.org/wiki/Tar_(computing)">tarballs</a> +to a <abbr>GNU</abbr>/Linux or similar host.</p> +<pre style="margin-left: 2em"><code>mkdir tzdb +cd tzdb +<a href="https://www.gnu.org/software/wget/">wget</a> --retr-symlinks 'ftp://ftp.iana.org/tz/tz*-latest.tar.gz' +<a href="https://www.gnu.org/software/gzip/">gzip</a> -dc tzcode-latest.tar.gz | <a href="https://www.gnu.org/software/tar/">tar</a> -xf - +gzip -dc tzdata-latest.tar.gz | tar -xf - </code></pre> -<p>This uses a convenience link to the -<a href="ftp://ftp.iana.org/tz/tzdb-latest.tar.lz">latest version</a> -archived in the +<p>Alternatively, the following shell commands download the same +release in a single-tarball format containing extra data +useful for regression testing:</p> +<pre style="margin-left: 2em"><code>wget --retr-symlinks 'ftp://ftp.iana.org/tz/tzdb-latest.tar.lz' +<a href="http://www.nongnu.org/lzip/">lzip</a> -dc tzdb-latest.tar.lz | tar -xf - +</code></pre> +<p>These commands use convenience links to the latest of the <a href="ftp://ftp.iana.org/tz/releases/"><abbr title="File Transfer Protocol">FTP</abbr> releases</a> of the <code><abbr>tz</abbr></code> database. -Archived versions are in files named <code>tzdb-<var>V</var>.tar.lz</code>, +Older releases are in files named +<code>tzcode<var>V</var>.tar.gz</code>, +<code>tzdata<var>V</var>.tar.gz</code>, and +<code>tzdb-<var>V</var>.tar.lz</code>, where <code><var>V</var></code> is the version. -For compatibility with releases before 2016g, a -<a href="https://www.gnu.org/software/gzip/">gzip</a>-compressed two-tarball -distribution is also available, where the code is in the -file <code>tzcode<var>C</var>.tar.gz</code>, -where <code><var>C</var></code> is the code's version; -similarly, the data entries are in <code>tzdata<var>D</var>.tar.gz</code>, -where <code><var>D</var></code> is the data's version. Since 1996, each version has been a four-digit year followed by lower-case letter (<samp>a</samp> through <samp>z</samp>, then <samp>za</samp> through <samp>zz</samp>, then <samp>zza</samp> -through <samp>zzz</samp>, and so on).</p> -<p> -The code and data files can also be obtained from the +through <samp>zzz</samp>, and so on). +The releases can also be obtained from the <a href="http://www.iana.org/time-zones">Time Zone Database website</a> of the <a href="http://www.iana.org">Internet Assigned Numbers Authority (IANA)</a>. @@ -144,6 +146,8 @@ in <a href="http://git-scm.com">Git</a> form from <a href="https://github.com">GitHub</a>; be careful, as this repository is less well tested and probably contains more errors. <p> +After extracting a distribution's files, see its +<code>README</code> file for what to do next. The code lets you compile the <code><abbr>tz</abbr></code> source files into machine-readable binary files, one for each location. It also lets you read a <code><abbr>tz</abbr></code> binary file and interpret time stamps for that @@ -295,7 +299,7 @@ program that compiles <code><abbr>tz</abbr></code> source into iCalendar-compatible VTIMEZONE files. Vzic is freely available under the <a -href="http://www.gnu.org/copyleft/gpl.html"><abbr>GNU</abbr> +href="https://www.gnu.org/copyleft/gpl.html"><abbr>GNU</abbr> General Public License (<abbr title="General Public License">GPL</abbr>)</a>.</li> <li><a href="https://sourceforge.net/projects/tzical/">tziCal – tz @@ -357,7 +361,7 @@ Advanced date, time and interval library for Java</a> contains a class <code>net.time4j.tool.TimezoneRepositoryCompiler</code> that compiles <code><abbr>tz</abbr></code> source into a binary format. Time4J is available under the <a -href="http://www.gnu.org/copyleft/lesser.html"><abbr>GNU</abbr> Lesser +href="https://www.gnu.org/copyleft/lesser.html"><abbr>GNU</abbr> Lesser General Public License (<abbr title="Lesser General Public License">LGPL</abbr>)</a>.</li> <li><abbr>ICU</abbr> (mentioned above) contains compilers and @@ -413,7 +417,7 @@ license.</li> <h2>Other <code><abbr>tz</abbr></code> binary file readers</h2> <ul> <li>The <a -href="http://www.gnu.org/software/libc/"><abbr>GNU</abbr> C +href="https://www.gnu.org/software/libc/"><abbr>GNU</abbr> C Library</a> has an independent, thread-safe implementation of a <code><abbr>tz</abbr></code> binary file reader. -- 2.7.4

1 2

tzdata for 2016 leap seconds
by Jimmy Wang (jcwang) Sept. 5, 2016

Sept. 5, 2016

Hi Paul et al, We heard that the tzdata for 2016 leap seconds would be published around Oct. Is there anyway that this can be published sooner? Many of our upstream vendors won't release their tzdata update until the official tzdata is published. Thanks, Jimmy

7 11

[PROPOSED PATCH] port 'environ' decl to Solaris 10
by Paul Eggert Sept. 5, 2016

Sept. 5, 2016

POSIX says apps must declare 'environ' themselves. Although this is not necessary on GNU/Linux with _GNU_SOURCE defined, it is needed with stricter environments like Solaris 10. * date.c, zdump.c (environ): Declare even if HAVE_POSIX_DECLS. --- date.c | 3 ++- zdump.c | 3 ++- 2 files changed, 4 insertions(+), 2 deletions(-) diff --git a/date.c b/date.c index 4c11f61..512d1ef 100644 --- a/date.c +++ b/date.c @@ -42,8 +42,9 @@ #define SECSPERMIN 60 #endif /* !defined SECSPERMIN */ -#if !HAVE_POSIX_DECLS extern char ** environ; + +#if !HAVE_POSIX_DECLS extern char * optarg; extern int optind; extern char * tzname[]; diff --git a/zdump.c b/zdump.c index 694b04f..f68ba3d 100644 --- a/zdump.c +++ b/zdump.c @@ -258,8 +258,9 @@ enum { SECSPER400YEARS_FITS = SECSPERLYEAR <= INTMAX_MAX / 400 }; # define timezone_t char ** #endif -#if !HAVE_POSIX_DECLS extern char ** environ; + +#if !HAVE_POSIX_DECLS extern int getopt(int argc, char * const argv[], const char * options); extern char * optarg; -- 2.7.4

2 2

[PROPOSED PATCH] * zic.c (dolink): Fix typo (missing newline) in diagnostic.
by Paul Eggert Sept. 4, 2016

Sept. 4, 2016

--- zic.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/zic.c b/zic.c index 9c696c6..b8bd0a6 100644 --- a/zic.c +++ b/zic.c @@ -772,7 +772,7 @@ dolink(char const *fromfield, char const *tofield) fromisdir = itsdir(fromname); if (fromisdir) { char const *e = strerror(fromisdir < 0 ? errno : EPERM); - fprintf(stderr, _("%s: link from %s failed: %s"), + fprintf(stderr, _("%s: link from %s failed: %s\n"), progname, fromname, e); exit(EXIT_FAILURE); } -- 2.7.4

1 0

[PROPOSED PATCH] zic fix storage-allocation bug with realloc
by Paul Eggert Sept. 4, 2016

Sept. 4, 2016

This bug was introduced in last month's Casablanca-in-2037 fix. Problem found by valgrind. * zic.c (outzone): Don't access freed storage. --- zic.c | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/zic.c b/zic.c index 1c91d5a..9c696c6 100644 --- a/zic.c +++ b/zic.c @@ -2290,7 +2290,7 @@ outzone(const struct zone *zpfirst, int zonecount) register int compat; register bool do_extend; register char version; - struct attype *lastatmax = NULL; + int lastatmax = -1; max_abbr_len = 2 + max_format_len + max_abbrvar_len; max_envvar_len = 2 * max_abbr_len + 5 * 9; @@ -2524,8 +2524,9 @@ outzone(const struct zone *zpfirst, int zonecount) type = addtype(offset, ab, rp->r_stdoff != 0, rp->r_todisstd, rp->r_todisgmt); if (rp->r_hiyear == ZIC_MAX - && ! (lastatmax && ktime < lastatmax->at)) - lastatmax = &attypes[timecnt]; + && ! (0 <= lastatmax + && ktime < attypes[lastatmax].at)) + lastatmax = timecnt; addtt(ktime, type); } } @@ -2557,8 +2558,8 @@ error(_("can't determine time zone abbreviation to use just after until time")); starttime = tadd(starttime, -gmtoff); } } - if (lastatmax) - lastatmax->dontmerge = true; + if (0 <= lastatmax) + attypes[lastatmax].dontmerge = true; if (do_extend) { /* ** If we're extending the explicitly listed observations -- 2.7.4

1 0

Bloomberg on possible Massachusetts time zone shift
by Arthur David Olson Aug. 30, 2016

Aug. 30, 2016

"Massachusetts Could Swap Time Zones for Later Winter Sunsets" (To Atlantic Time.) http://www.bloomberg.com/news/articles/2016-08-29/winter-s-hated-4-p-m-suns… --ado

2 1

[PROPOSED PATCH 1/4] Prefer +-NN notation for UT-offset time zones in comments.
by Paul Eggert Aug. 26, 2016

Aug. 26, 2016

This does not change any code or data; just comments. --- NEWS | 38 +++++++++++++++++++------------------- Theory | 2 +- africa | 2 +- asia | 51 +++++++++++++++++++++++++-------------------------- australasia | 26 +++++++++++++------------- backzone | 14 +++++++------- europe | 8 +------- localtime.c | 2 +- northamerica | 2 +- private.h | 1 + southamerica | 4 ++-- 11 files changed, 72 insertions(+), 78 deletions(-) diff --git a/NEWS b/NEWS index 4c18e55..b0da284 100644 --- a/NEWS +++ b/NEWS @@ -465,7 +465,7 @@ Release 2015d - 2015-04-24 08:09:46 -0700 Changes affecting past time stamps - America/Whitehorse switched from UTC-9 to UTC-8 on 1967-05-28, not + America/Whitehorse switched from -09 to -08 on 1967-05-28, not 1966-07-01. Also, Yukon's time zone history is documented better. (Thanks to Brian Inglis and Dennis Ferguson.) @@ -499,12 +499,12 @@ Release 2015c - 2015-04-11 08:55:55 -0700 The 1918 transition was September 10, not September 1. - The UTC-4 time observed from 1932 to 1942 is now considered to be + The -04 time observed from 1932 to 1942 is now considered to be standard time, not year-round DST. - Santiago observed DST (UTC-3) from 1946-07-15 through 1946-08-31, + Santiago observed DST (-03) from 1946-07-15 through 1946-08-31, then reverted to standard time, then switched its time zone to - UTC-5 on 1947-04-01. + -05 on 1947-04-01. Assume transitions before 1968 were at 00:00, since we have no data saying otherwise. @@ -633,7 +633,7 @@ Release 2014j - 2014-11-10 17:37:11 -0800 Changes affecting current and future time stamps - Turks & Caicos' switch from US eastern time to UTC-4 year-round + Turks & Caicos' switch from US eastern time to -04 year-round did not occur on 2014-11-02 at 02:00. It's currently scheduled for 2015-11-01 at 02:00. (Thanks to Chris Walton.) @@ -669,7 +669,7 @@ Release 2014i - 2014-10-21 22:04:57 -0700 years will use a similar pattern. A new Zone Pacific/Bougainville, for the part of Papua New Guinea - that plans to switch from UTC+10 to UTC+11 on 2014-12-28 at 02:00. + that plans to switch from +10 to +11 on 2014-12-28 at 02:00. (Thanks to Kiley Walbom for the heads-up.) Changes affecting time zone abbreviations @@ -679,8 +679,8 @@ Release 2014i - 2014-10-21 22:04:57 -0700 to its more-traditional value MSK on 2014-10-26 at 01:00. (Thanks to Alexander Bokovoy for the heads-up about Belarus.) - The new abbreviation IDT stands for the pre-1976 use of UT+8 in - Indochina, to distinguish it better from ICT (UT+7). + The new abbreviation IDT stands for the pre-1976 use of +08 in + Indochina, to distinguish it better from ICT (+07). Changes affecting past time stamps @@ -791,7 +791,7 @@ Release 2014g - 2014-08-28 12:31:23 -0700 Changes affecting future time stamps - Turks & Caicos is switching from US eastern time to UTC-4 year-round, + Turks & Caicos is switching from US eastern time to -04 year-round, modeled as a switch from EST/EDT to AST on 2014-11-02 at 02:00. [As noted in 2014j, this switch was later delayed.] @@ -975,7 +975,7 @@ Release 2014f - 2014-08-05 17:42:36 -0700 This change does not affect UTC offsets, only time zone abbreviations. (Thanks to Rich Tibbett and many others.) - Asia/Novokuznetsk shifts from NOVT to KRAT (remaining on UTC+7) + Asia/Novokuznetsk shifts from NOVT to KRAT (remaining on +07) effective 2014-10-26 at 02:00 local time. The time zone abbreviation for Xinjiang Time (observed in Ürümqi) @@ -1004,8 +1004,8 @@ Release 2014f - 2014-08-05 17:42:36 -0700 zones Asia/Harbin, Asia/Chongqing, and Asia/Kashgar have been removed; backwards-compatibility links still work, albeit with different behaviors for time stamps before May 1980. Asia/Urumqi's - 1980 transition to UTC+8 has been removed, so that it is now at - UTC+6 and not UTC+8. (Thanks to Luther Ma and to Alois Treindl; + 1980 transition to +08 has been removed, so that it is now at + +06 and not +08. (Thanks to Luther Ma and to Alois Treindl; Treindl sent helpful translations of two papers by Guo Qingsheng.) Some zones have been turned into links, when they differed from existing @@ -1035,7 +1035,7 @@ Release 2014f - 2014-08-05 17:42:36 -0700 Europe/Helsinki's 1942 fall-back transition was 10-04 at 01:00, not 10-03 at 00:00. (Thanks to Konstantin Hyppönen.) - Pacific/Pago_Pago has been changed from UTC-11:30 to UTC-11 for the period + Pacific/Pago_Pago has been changed from -11:30 to -11 for the period from 1911 to 1950. Pacific/Chatham has been changed to New Zealand standard time plus @@ -1363,15 +1363,15 @@ Release 2013h - 2013-10-25 15:32:32 -0700 Changes affecting current and future time stamps: - Libya has switched its time zone back to UTC+2 without DST, - instead of UTC+1 with DST. (Thanks to Even Scharning.) + Libya has switched its time zone back to +02 without DST, + instead of +01 with DST. (Thanks to Even Scharning.) Western Sahara (Africa/El_Aaiun) uses Morocco's DST rules. (Thanks to Gwillim Law.) Changes affecting future time stamps: - Acre and (we guess) western Amazonas will switch from UTC-4 to UTC-5 + Acre and (we guess) western Amazonas will switch from -04 to -05 on 2013-11-10. This affects America/Rio_Branco and America/Eirunepe. (Thanks to Steffen Thorsen.) @@ -1458,7 +1458,7 @@ Release 2013f - 2013-09-24 23:37:36 -0700 Tocantins will very likely not observe DST starting this spring. (Thanks to Steffen Thorsen.) - Jordan will likely stay at UTC+3 indefinitely, and will not fall + Jordan will likely stay at +03 indefinitely, and will not fall back this fall. Palestine will fall back at 00:00, not 01:00. (Thanks to Steffen Thorsen.) @@ -1515,7 +1515,7 @@ Release 2013e - 2013-09-19 23:50:04 -0700 Benny Lin.) This affects Asia/Dili, Asia/Jakarta, Asia/Jayapura, Asia/Makassar, and Asia/Pontianak. - Use ART (UTC-3, standard time), rather than WARST (also UTC-3, but + Use ART (-03, standard time), rather than WARST (also UTC-3, but daylight saving time) for San Luis, Argentina since 2009. Changes affecting Godthåb time stamps after 2037 if version mismatch @@ -1972,7 +1972,7 @@ Release 2012f - 2012-09-12 23:17:03 -0700 Release 2012e - 2012-08-02 20:44:55 -0700 - * australasia (Pacific/Fakaofo): Tokelau is UTC+13, not UTC+14. + * australasia (Pacific/Fakaofo): Tokelau is +13, not +14. (Thanks to Steffen Thorsen.) * Use a single version number for both code and data. diff --git a/Theory b/Theory index 60678fe..d8d3882 100644 --- a/Theory +++ b/Theory @@ -323,7 +323,7 @@ Errors in the tz database arise from many sources: * Sometimes historical timekeeping was specified more precisely than what the tz database can handle. For example, from 1909 to - 1937 Netherlands clocks were legally UT+00:19:32.13, but the tz + 1937 Netherlands clocks were legally +00:19:32.13, but the tz database cannot represent the fractional second. * Even when all the timestamp transitions recorded by the tz database diff --git a/africa b/africa index 50f29d5..43c8e23 100644 --- a/africa +++ b/africa @@ -464,7 +464,7 @@ Zone Africa/Monrovia -0:43:08 - LMT 1882 # http://www.libyaherald.com/2013/10/24/correction-no-time-change-tomorrow/ # # From Paul Eggert (2013-10-25): -# For now, assume they're reverting to the pre-2012 rules of permanent UTC+2. +# For now, assume they're reverting to the pre-2012 rules of permanent +02. # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S Rule Libya 1951 only - Oct 14 2:00 1:00 S diff --git a/asia b/asia index ee2c436..a935476 100644 --- a/asia +++ b/asia @@ -380,7 +380,7 @@ Rule PRC 1987 1991 - Apr Sun>=10 0:00 1:00 D # Lewiston (ME) Daily Sun (1939-05-29), p 17, said "Even the time is # different - the occupied districts going by Tokyo time, an hour # ahead of that prevailing in the rest of Shanghai." Guess that the -# Xujiahui Observatory was under French control and stuck with UT+8. +# Xujiahui Observatory was under French control and stuck with +08. # # In earlier versions of this file, China had many separate Zone entries, but # this was based on what were apparently incorrect data in Shanks & Pottenger. @@ -389,26 +389,26 @@ Rule PRC 1987 1991 - Apr Sun>=10 0:00 1:00 D # Proposed in 1918 and theoretically in effect until 1949 (although in practice # mainly observed in coastal areas), the five zones were: # -# Changbai Time ("Long-white Time", Long-white = Heilongjiang area) UT+8.5 +# Changbai Time ("Long-white Time", Long-white = Heilongjiang area) +08:30 # Asia/Harbin (currently a link to Asia/Shanghai) # Heilongjiang (except Mohe county), Jilin # -# Zhongyuan Time ("Central plain Time") UT+8 +# Zhongyuan Time ("Central plain Time") -08 # Asia/Shanghai # most of China # This currently represents most other zones as well, # as apparently these regions have been the same since 1970. # Milne gives 8:05:43.2 for Xujiahui Observatory time; round to nearest. -# Guo says Shanghai switched to UT+8 "from the end of the 19th century". +# Guo says Shanghai switched to +08 "from the end of the 19th century". # -# Long-shu Time (probably due to Long and Shu being two names of that area) UT+7 +# Long-shu Time (probably due to Long and Shu being two names of that area) +07 # Asia/Chongqing (currently a link to Asia/Shanghai) # Guangxi, Guizhou, Hainan, Ningxia, Sichuan, Shaanxi, and Yunnan; # most of Gansu; west Inner Mongolia; west Qinghai; and the Guangdong # counties Deqing, Enping, Kaiping, Luoding, Taishan, Xinxing, # Yangchun, Yangjiang, Yu'nan, and Yunfu. # -# Xin-zang Time ("Xinjiang-Tibet Time") UT+6 +# Xin-zang Time ("Xinjiang-Tibet Time") +06 # Asia/Urumqi # This currently represents Kunlun Time as well, # as apparently the two regions have been the same since 1970. @@ -421,7 +421,7 @@ Rule PRC 1987 1991 - Apr Sun>=10 0:00 1:00 D # Shihezi, Changji, Yanqi, Heshuo, Tuokexun, Tulufan, Shanshan, Hami, # Fukang, Kuitun, Kumukuli, Miquan, Qitai, and Turfan. # -# Kunlun Time UT+5.5 +# Kunlun Time +05:30 # Asia/Kashgar (currently a link to Asia/Urumqi) # West Tibet, including Pulan, Aheqi, Shufu, Shule; # West Xinjiang, including Aksu, Atushi, Yining, Hetian, Cele, Luopu, Nileke, @@ -493,7 +493,7 @@ Rule PRC 1987 1991 - Apr Sun>=10 0:00 1:00 D # having the same time as Beijing. # From Paul Eggert (2014-06-30): -# In the early days of the PRC, Tibet was given its own time zone (UT+6) but +# In the early days of the PRC, Tibet was given its own time zone (+06) but # this was withdrawn in 1959 and never reinstated; see Tubten Khétsun, # Memories of life in Lhasa under Chinese Rule, Columbia U Press, ISBN # 978-0231142861 (2008), translator's introduction by Matthew Akester, p x. @@ -508,12 +508,12 @@ Rule PRC 1987 1991 - Apr Sun>=10 0:00 1:00 D # Republics, the Soviet Union, the Kuomintang, and the People's Republic of # China, and tracking down all these organizations' timekeeping rules would be # quite a trick. Approximate this lost history by a transition from LMT to -# XJT at the start of 1928, the year of accession of the warlord Jin Shuren, +# +06 at the start of 1928, the year of accession of the warlord Jin Shuren, # which happens to be the date given by Shanks & Pottenger (no doubt as a -# guess) as the transition from LMT. Ignore the usage of UT+8 before -# 1986-02-01 under the theory that the transition date to UT+8 is unknown and +# guess) as the transition from LMT. Ignore the usage of +08 before +# 1986-02-01 under the theory that the transition date to +08 is unknown and # that the sort of users who prefer Asia/Urumqi now typically ignored the -# UT+8 mandate back then. +# +08 mandate back then. # Zone NAME GMTOFF RULES FORMAT [UNTIL] # Beijing time, used throughout China; represented by Shanghai. @@ -718,7 +718,7 @@ Zone Asia/Hong_Kong 7:36:42 - LMT 1904 Oct 30 # be found from historical government announcement database. # From Paul Eggert (2014-07-03): -# As per Yu-Cheng Chuang, say that Taiwan was at UT+9 from 1937-10-01 +# As per Yu-Cheng Chuang, say that Taiwan was at +09 from 1937-10-01 # until 1945-09-21 at 01:00, overriding Shanks & Pottenger. # Likewise, use Yu-Cheng Chuang's data for DST in Taiwan. @@ -917,7 +917,7 @@ Zone Asia/Kolkata 5:53:28 - LMT 1880 # Kolkata # These would be the earliest possible times for a change. # Régimes horaires pour le monde entier, by Henri Le Corre, (Éditions # Traditionnelles, 1987, Paris) says that Java and Madura switched -# from JST to UTC+07:30 on 1945-09-23, and gives 1944-09-01 for Jayapura +# from +09 to +07:30 on 1945-09-23, and gives 1944-09-01 for Jayapura # (Hollandia). For now, assume all Indonesian locations other than Jayapura # switched on 1945-09-23. # @@ -930,9 +930,9 @@ Zone Asia/Kolkata 5:53:28 - LMT 1880 # Kolkata # Indonesia, <http://time.kim.lipi.go.id/time-eng.php> (2006-09-29). # The abbreviations are: # -# WIB - UTC+7 - Waktu Indonesia Barat (Indonesia western time) -# WITA - UTC+8 - Waktu Indonesia Tengah (Indonesia central time) -# WIT - UTC+9 - Waktu Indonesia Timur (Indonesia eastern time) +# WIB - +07 - Waktu Indonesia Barat (Indonesia western time) +# WITA - +08 - Waktu Indonesia Tengah (Indonesia central time) +# WIT - +09 - Waktu Indonesia Timur (Indonesia eastern time) # # Zone NAME GMTOFF RULES FORMAT [UNTIL] # Java, Sumatra @@ -1864,25 +1864,24 @@ Rule ROK 1957 1960 - Sep Sun>=18 0:00 0 S Rule ROK 1987 1988 - May Sun>=8 2:00 1:00 D Rule ROK 1987 1988 - Oct Sun>=8 3:00 0 S -# From Paul Eggert (2014-10-30): +# From Paul Eggert (2016-08-23): # The Korean Wikipedia entry gives the following sources for UT offsets: # -# 1908: Official Journal Article No. 3994 (Edict No. 5) +# 1908: Official Journal Article No. 3994 (decree No. 5) # 1912: Governor-General of Korea Official Gazette Issue No. 367 # (Announcement No. 338) # 1954: Presidential Decree No. 876 (1954-03-17) # 1961: Law No. 676 (1961-08-07) -# 1987: Law No. 3919 (1986-12-31) # -# The Wikipedia entry also has confusing information about a change -# to UT+9 in April 1910, but then what would be the point of the later change -# to UT+9 on 1912-01-01? Omit the 1910 change for now. +# (Another source "1987: Law No. 3919 (1986-12-31)" was in the 2014-10-30 +# edition of the Korean Wikipedia entry.) # # I guessed that time zone abbreviations through 1945 followed the same # rules as discussed under Taiwan, with nominal switches from JST to KST # when the respective cities were taken over by the Allies after WWII. # -# For Pyongyang we have no information; guess no changes since World War II. +# For Pyongyang, guess no changes from World War II until 2015, as we +# have no information otherwise. # From Steffen Thorsen (2015-08-07): # According to many news sources, North Korea is going to change to @@ -2042,7 +2041,7 @@ Zone Indian/Maldives 4:54:00 - LMT 1880 # Male # Bill Bonnet (2005-05-19) reports that the US Embassy in Ulaanbaatar says # there is only one time zone and that DST is observed, citing Microsoft # Windows XP as the source. Risto Nykänen (2005-05-16) reports that -# travelmongolia.org says there are two time zones (UTC+7, UTC+8) with no DST. +# travelmongolia.org says there are two time zones (+07, +08) with no DST. # Oscar van Vlijmen (2005-05-20) reports that the Mongolian Embassy in # Washington, DC says there are two time zones, with DST observed. # He also found @@ -2678,7 +2677,7 @@ Link Asia/Qatar Asia/Bahrain # earlier date. # # Shanks & Pottenger also state that until 1968-05-01 Saudi Arabia had two -# time zones; the other zone, at UTC+4, was in the far eastern part of +# time zones; the other zone, at +04, was in the far eastern part of # the country. Ignore this, as it's before our 1970 cutoff. # # Zone NAME GMTOFF RULES FORMAT [UNTIL] diff --git a/australasia b/australasia index 0b33f67..fe77d07 100644 --- a/australasia +++ b/australasia @@ -545,7 +545,7 @@ Zone Pacific/Port_Moresby 9:48:40 - LMT 1880 # Base the Bougainville entry on the Arawa-Kieta region, which appears to have # the most people even though it was devastated in the Bougainville Civil War. # -# Although Shanks gives 1942-03-15 / 1943-11-01 for JST, these dates +# Although Shanks gives 1942-03-15 / 1943-11-01 for +09, these dates # are apparently rough guesswork from the starts of military campaigns. # The World War II entries below are instead based on Arawa-Kieta. # The Japanese occupied Kieta in July 1942, @@ -553,8 +553,8 @@ Zone Pacific/Port_Moresby 9:48:40 - LMT 1880 # http://pwencycl.kgbudge.com/B/o/Bougainville.htm # and seem to have controlled it until their 1945-08-21 surrender. # -# The Autonomous Region of Bougainville plans to switch from UTC+10 to UTC+11 -# on 2014-12-28 at 02:00. They call UTC+11 "Bougainville Standard Time"; +# The Autonomous Region of Bougainville switched from +10 to +11 +# on 2014-12-28 at 02:00. They call +11 "Bougainville Standard Time"; # abbreviate this as BST. See: # http://www.bougainville24.com/bougainville-issues/bougainville-gets-own-tim… # @@ -620,7 +620,7 @@ Link Pacific/Pago_Pago Pacific/Midway # in US minor outlying islands # From Paul Eggert (2014-06-27): # The International Date Line Act 2011 # http://www.parliament.gov.ws/images/ACTS/International_Date_Line_Act__2011_… -# changed Samoa from UTC-11 to UTC+13, effective "12 o'clock midnight, on +# changed Samoa from -11 to +13, effective "12 o'clock midnight, on # Thursday 29th December 2011". The International Date Line was adjusted # accordingly. @@ -715,7 +715,7 @@ Zone Pacific/Funafuti 11:56:52 - LMT 1901 # 1886-1891; Baker was similar but exact dates are not known. # Inhabited by civilians 1935-1942; U.S. military bases 1943-1944; # uninhabited thereafter. -# Howland observed Hawaii Standard Time (UT-10:30) in 1937; +# Howland observed Hawaii Standard Time (-10:30) in 1937; # see page 206 of Elgen M. Long and Marie K. Long, # Amelia Earhart: the Mystery Solved, Simon & Schuster (2000). # So most likely Howland and Baker observed Hawaii Time from 1935 @@ -1473,7 +1473,7 @@ Zone Pacific/Wallis 12:15:20 - LMT 1901 # Zealand time. I understand that is the time they keep locally, anyhow." # For now, assume this practice goes back to the introduction of standard time # in New Zealand, as this would make Chatham Islands time almost exactly match -# LMT back when New Zealand was at UTC+11:30; also, assume Chatham Islands did +# LMT back when New Zealand was at +11:30; also, assume Chatham Islands did # not observe New Zealand's prewar DST. ############################################################################### @@ -1529,7 +1529,7 @@ Zone Pacific/Wallis 12:15:20 - LMT 1901 # For now, we assume the Ladrones switched at the same time as the Philippines; # see Asia/Manila. -# US Public Law 106-564 (2000-12-23) made UTC+10 the official standard time, +# US Public Law 106-564 (2000-12-23) made +10 the official standard time, # under the name "Chamorro Standard Time". There is no official abbreviation, # but Congressman Robert A. Underwood, author of the bill that became law, # wrote in a press release (2000-12-27) that he will seek the use of "ChST". @@ -1541,15 +1541,15 @@ Zone Pacific/Wallis 12:15:20 - LMT 1901 # "I am certain, having lived there for the past decade, that 'Truk' # (now properly known as Chuuk) ... is in the time zone GMT+10." # -# Shanks & Pottenger write that Truk switched from UTC+10 to UTC+11 +# Shanks & Pottenger write that Truk switched from +10 to +11 # on 1978-10-01; ignore this for now. # From Paul Eggert (1999-10-29): # The Federated States of Micronesia Visitors Board writes in # The Federated States of Micronesia - Visitor Information (1999-01-26) # http://www.fsmgov.org/info/clocks.html -# that Truk and Yap are UTC+10, and Ponape and Kosrae are UTC+11. -# We don't know when Kosrae switched from UTC+12; assume January 1 for now. +# that Truk and Yap are +10, and Ponape and Kosrae are +11. +# We don't know when Kosrae switched from +12; assume January 1 for now. # Midway @@ -1615,11 +1615,11 @@ Zone Pacific/Wallis 12:15:20 - LMT 1901 # ordaining - by a masterpiece of diplomatic flattery - that # the Fourth of July should be celebrated twice in that year." -# Although Shanks & Pottenger says they both switched to UTC-11:30 -# in 1911, and to UTC-11 in 1950. many earlier sources give UTC-11 +# Although Shanks & Pottenger says they both switched to -11:30 +# in 1911, and to -11 in 1950. many earlier sources give -11 # for American Samoa, e.g., the US National Bureau of Standards # circular "Standard Time Throughout the World", 1932. -# Assume American Samoa switched to UTC-11 in 1911, not 1950, +# Assume American Samoa switched to -11 in 1911, not 1950, # and that after 1950 they agreed until (western) Samoa skipped a # day in 2011. Assume also that the Samoas follow the US and New # Zealand's "ST"/"DT" style of daylight-saving abbreviations. diff --git a/backzone b/backzone index 13dc8d4..27a5472 100644 --- a/backzone +++ b/backzone @@ -194,9 +194,9 @@ Zone Africa/Lusaka 1:53:08 - LMT 1903 Mar # Equatorial Guinea # -# Although Shanks says that Malabo switched from UTC to UTC+1 on 1963-12-15, +# Although Shanks says that Malabo switched from +00 to +01 on 1963-12-15, # a Google Books search says that London Calling, Issues 432-465 (1948), p 19, -# says that Spanish Guinea was at GMT+1 back then. The Shanks data entries +# says that Spanish Guinea was at +01 back then. The Shanks data entries # are most likely wrong, but we have nothing better; use them here for now. # Zone Africa/Malabo 0:35:08 - LMT 1912 @@ -479,14 +479,14 @@ Zone Asia/Muscat 3:54:24 - LMT 1920 # From Paul Eggert (2014-08-11), after a heads-up from Stephen Colebourne: # According to a Portuguese decree (1911-05-26) # http://dre.pt/pdf1sdip/1911/05/12500/23132313.pdf -# Portuguese India switched to GMT+5 on 1912-01-01. +# Portuguese India switched to +05 on 1912-01-01. #Zone Asia/Panaji [not enough info to complete] # Cambodia # From Paul Eggert (2014-10-11): # See Asia/Ho_Chi_Minh for the source for most of this data. Also, guess -# (1) Cambodia reverted to UT+7 on 1945-09-02, when Vietnam did, and -# (2) they also reverted to UT+7 on 1953-11-09, the date of independence. +# (1) Cambodia reverted to +07 on 1945-09-02, when Vietnam did, and +# (2) they also reverted to +07 on 1953-11-09, the date of independence. # These guesses are probably wrong but they're better than guessing no # transitions there. Zone Asia/Phnom_Penh 6:59:40 - LMT 1906 Jul 1 @@ -506,8 +506,8 @@ Zone Asia/Tel_Aviv 2:19:04 - LMT 1880 # Laos # From Paul Eggert (2014-10-11): # See Asia/Ho_Chi_Minh for the source for most of this data. -# Trần's book says that Laos reverted to UT+7 on 1955-04-15. -# Also, guess that Laos reverted to UT+7 on 1945-09-02, when Vietnam did; +# Trần's book says that Laos reverted to +07 on 1955-04-15. +# Also, guess that Laos reverted to +07 on 1945-09-02, when Vietnam did; # this is probably wrong but it's better than guessing no transition. Zone Asia/Vientiane 6:50:24 - LMT 1906 Jul 1 7:06:30 - PLMT 1911 May 1 diff --git a/europe b/europe index b02edbd..4219828 100644 --- a/europe +++ b/europe @@ -774,8 +774,6 @@ Zone Europe/Vienna 1:05:21 - LMT 1893 Apr # From Alexander Bokovoy (2014-10-09): # Belarussian government decided against changing to winter time.... # http://eng.belta.by/all_news/society/Belarus-decides-against-adjusting-time… -# From Paul Eggert (2014-10-08): -# Hence Belarus can share time zone abbreviations with Moscow again. # # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Minsk 1:50:16 - LMT 1880 @@ -1294,7 +1292,7 @@ Zone Europe/Paris 0:09:21 - LMT 1891 Mar 15 0:01 # http://www.parlament-berlin.de/pds-fraktion.nsf/727459127c8b66ee85256623004… # says that Bersarin issued an order to use Moscow time on May 20. # However, Moscow did not observe daylight saving in 1945, so -# this was equivalent to CEMT (GMT+3), not GMT+4. +# this was equivalent to +03, not +04. # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S @@ -2258,7 +2256,6 @@ Zone Europe/Bucharest 1:44:24 - LMT 1891 Oct # http://www.worldtimezone.com/dst_news/dst_news_russia-map-2014-07.html # From Paul Eggert (2006-03-22): -# Except for Moscow after 1919-07-01, I invented the time zone abbreviations. # Moscow time zone abbreviations after 1919-07-01, and Moscow rules after 1991, # are from Andrey A. Chernov. The rest is from Shanks & Pottenger, # except we follow Chernov's report that 1992 DST transitions were Sat @@ -3080,9 +3077,6 @@ Zone Asia/Magadan 10:03:12 - LMT 1924 May 2 # in Russian.) In addition, Srednekolymsk appears to be a much older # settlement and the population of Zyryanka seems to be declining. # Go with Srednekolymsk. -# -# Since Magadan Oblast moves to UTC+10 on 2014-10-26, we cannot keep using MAGT -# as the abbreviation. Use SRET instead. Zone Asia/Srednekolymsk 10:14:52 - LMT 1924 May 2 10:00 - +10 1930 Jun 21 diff --git a/localtime.c b/localtime.c index 276ce34..6c00c45 100644 --- a/localtime.c +++ b/localtime.c @@ -1510,7 +1510,7 @@ gmtsub(struct state const *sp, time_t const *timep, int_fast32_t offset, #ifdef TM_ZONE /* ** Could get fancy here and deliver something such as - ** "UT+xxxx" or "UT-xxxx" if offset is non-zero, + ** "+xx" or "-xx" if offset is non-zero, ** but this is no time for a treasure hunt. */ tmp->TM_ZONE = ((char *) diff --git a/northamerica b/northamerica index d66135e..0c069bb 100644 --- a/northamerica +++ b/northamerica @@ -3312,7 +3312,7 @@ Zone America/Miquelon -3:44:40 - LMT 1911 May 15 # St Pierre # indicating that the normal ET rules are followed. # # From Paul Eggert (2014-08-19): -# The 2014-08-13 Cabinet meeting decided to stay on UTC-4 year-round. See: +# The 2014-08-13 Cabinet meeting decided to stay on -04 year-round. See: # http://tcweeklynews.com/daylight-savings-time-to-be-maintained-p5353-127.htm # Model this as a switch from EST/EDT to AST ... # From Chris Walton (2014-11-04): diff --git a/private.h b/private.h index 941e91b..3583079 100644 --- a/private.h +++ b/private.h @@ -15,6 +15,7 @@ ** Thank you! */ +/* This string was in the tzdata Factory zone through version 2016f. */ #define GRANDPARENTED "Local time zone must be set--see zic manual page" /* diff --git a/southamerica b/southamerica index 1c38f63..5321451 100644 --- a/southamerica +++ b/southamerica @@ -410,9 +410,9 @@ Rule Arg 2008 only - Oct Sun>=15 0:00 1:00 S # stuck on Summer daylight savings time even though the summer is over. # From Paul Eggert (2013-09-05): -# Perhaps San Luis operates on the legal fiction that it is at UTC-4 +# Perhaps San Luis operates on the legal fiction that it is at -04 # with perpetual summer time, but ordinary usage typically seems to -# just say it's at UTC-3; see, for example, +# just say it's at -03; see, for example, # http://es.wikipedia.org/wiki/Hora_oficial_argentina # We've documented similar situations as being plain changes to # standard time, so let's do that here too. This does not change UTC -- 2.5.5

12 28

Timezone support in UTC format like in Windows 7
by kailash kumar Aug. 25, 2016

Aug. 25, 2016

Hi All, We wanted to implement timezone support from our web interface where user should be able to select timezone in the following UTC format similar to windows 7 OS. Is it possible to fetch records for timezone from tz database in following UTC format to construct timezone drop down? if yes then how can we set timezone in UTC format like *set timezone UTC+05:30 Chennai,Kolkata,Mumbai,New Delhi* Thanks, KAILASH KUMAR JAIN BE cs Post at: kailashkumarp(a)gmail.com Legal Warning: This message may contain privileged and confidential information. If you are not the intended recipient or for any reason think that this message may have been address to you or reached you as a mistake, its requested that you must not disseminate,copy or take any action in reliance on it and I ask you to delete all copies from your mail box and computer system and also notify me immediately by return e-mail.

5 4

16th century Nuremberg time
by Steve Allen Aug. 25, 2016

Aug. 25, 2016

At the Science of Time Symposium in Cambridge Massachussetts earlier this year Kevin Birth showed a situation that tz does not have to handle. http://gallica.bnf.fr/ark:/12148/btv1b8490533n gives a view of one surviving example of the 1589 Vergleichung nachvolgender siben Uhren This was a chart to translate between the 7 different ways of counting hours (some employing unequal hours) which visitors might know from their home cities (and their pocket sundials) and the hours which were in use by various different clock towers and agencies in Nuremberg. -- Steve Allen <sla(a)ucolick.org> WGS-84 (GPS) UCO/Lick Observatory--ISB 260 Natural Sciences II, Room 165 Lat +36.99855 1156 High Street Voice: +1 831 459 3046 Lng -122.06015 Santa Cruz, CA 95064 http://www.ucolick.org/~sla/ Hgt +250 m

1 0

[PROPOSED PATCH 1/2] Also distribute code and data in a single tarball
by Paul Eggert Aug. 24, 2016

Aug. 24, 2016

Suggested by Arthur David Olson in: https://mm.icann.org/pipermail/tz/2000-January/010789.html * Makefile (GNUTARFLAGS): Add --sort=name, so that the single tarball is more reproducible. (clean): Remove tzdb. (tzdb-$(VERSION).tar.gz): New target. (tarballs): Add it. (tzdb-$(VERSION).tar.gz.asc): New target. (signatures): Add it. * NEWS: Document this. --- Makefile | 21 +++++++++++++++++---- NEWS | 9 +++++++++ 2 files changed, 26 insertions(+), 4 deletions(-) diff --git a/Makefile b/Makefile index fc18819..da697b7 100644 --- a/Makefile +++ b/Makefile @@ -326,7 +326,7 @@ OK_LINE= '^'$(OK_CHAR)'*$$' # Flags to give 'tar' when making a distribution. # Try to use flags appropriate for GNU tar. -GNUTARFLAGS= --numeric-owner --owner=0 --group=0 --mode=go+u,go-w +GNUTARFLAGS= --numeric-owner --owner=0 --group=0 --mode=go+u,go-w --sort=name TARFLAGS= `if tar $(GNUTARFLAGS) --version >/dev/null 2>&1; \ then echo $(GNUTARFLAGS); \ else :; \ @@ -568,7 +568,7 @@ clean_misc: rm -f core *.o *.out \ date tzselect version.h zdump zic yearistype libtz.a clean: clean_misc - rm -fr *.dir $(TZS_NEW) + rm -fr *.dir tzdb $(TZS_NEW) maintainer-clean: clean @echo 'This command is intended for maintainers to use; it' @@ -672,7 +672,8 @@ check_time_t_alternatives: done rm -fr time_t.dir -tarballs: tzcode$(VERSION).tar.gz tzdata$(VERSION).tar.gz +tarballs: tzcode$(VERSION).tar.gz tzdata$(VERSION).tar.gz \ + tzdb-$(VERSION).tar.gz tzcode$(VERSION).tar.gz: set-timestamps.out LC_ALL=C && export LC_ALL && \ @@ -685,7 +686,16 @@ tzdata$(VERSION).tar.gz: set-timestamps.out tar $(TARFLAGS) -cf - $(COMMON) $(DATA) $(MISC) $(TZS) | \ gzip $(GZIPFLAGS) > $@ -signatures: tzcode$(VERSION).tar.gz.asc tzdata$(VERSION).tar.gz.asc +tzdb-$(VERSION).tar.gz: set-timestamps.out + rm -fr tzdb + mkdir tzdb + ln $(COMMON) $(DOCS) $(SOURCES) $(DATA) $(MISC) $(TZS) tzdb + touch -cmr $$(ls -t tzdb/* | sed 1q) tzdb + LC_ALL=C && export LC_ALL && \ + tar $(TARFLAGS) -cf - tzdb | gzip $(GZIPFLAGS) > $@ + +signatures: tzcode$(VERSION).tar.gz.asc tzdata$(VERSION).tar.gz.asc \ + tzdb-$(VERSION).tar.gz.asc tzcode$(VERSION).tar.gz.asc: tzcode$(VERSION).tar.gz gpg --armor --detach-sign $? @@ -693,6 +703,9 @@ tzcode$(VERSION).tar.gz.asc: tzcode$(VERSION).tar.gz tzdata$(VERSION).tar.gz.asc: tzdata$(VERSION).tar.gz gpg --armor --detach-sign $? +tzdb-$(VERSION).tar.gz.asc: tzdb-$(VERSION).tar.gz + gpg --armor --detach-sign $? + typecheck: $(MAKE) clean for i in "long long" unsigned; \ diff --git a/NEWS b/NEWS index 023883b..18b7c9d 100644 --- a/NEWS +++ b/NEWS @@ -32,6 +32,15 @@ Unreleased, experimental changes what should be the output of 'zdump -i -c 2050' on primary zones. 'make check' now checks that zdump generates this output. + A new distribution format is available in the tarball + tzdb-VERSION.tar.gz and the signature tzdb-VERSION.tar.gz.asc. + The new tarball has the contents of tzcodeVERSION.tar.gz and + tzdataVERSION.tar.gz, in a single top-level directory 'tzdb' with + all other files under this directory, as is typical for software + distributions. The new format is intended to replace the old + tarball pair. The old format will continue to be distributed for + a while. + Changes to documentation and commentary tzfile.5 now documents the new restriction on POSIX TZ-like -- 2.5.5

7 12

California keeps DST (to help its crops grow?!)
by Paul Eggert Aug. 24, 2016

Aug. 24, 2016

Today the California Senate rejected Assembly Bill 385, which would have placed a measure on the state ballot asking voters whether to cancel daylight saving time. This is the bill that prompted me to fix some historical inaccuracies in tzdata's Los Angeles entry a few days ago. Sen. Jim Nelson (R-Gerber) voted against the bill, arguing that farmers benefit from DST. He said, "Our crops have gotten accustomed to that. They've in fact been bred to deal with that longer harvest season." You just can't make this stuff up.... Koseff A. Effort to roll back daylight saving time defeated in California Senate. Sacramento Bee 2016-08-23 [misdated as 2016-08-22]. http://www.sacbee.com/news/politics-government/capitol-alert/article9748310…

2 2

[PROPOSED PATCH] Spelling fixes
by Paul Eggert Aug. 24, 2016

Aug. 24, 2016

--- NEWS | 2 +- europe | 4 ++-- factory | 4 ++-- tz-how-to.html | 2 +- 4 files changed, 6 insertions(+), 6 deletions(-) diff --git a/NEWS b/NEWS index 4c0f4e0..fd2bcbb 100644 --- a/NEWS +++ b/NEWS @@ -772,7 +772,7 @@ Release 2014h - 2014-09-25 18:59:03 -0700 zdump -c no longer mishandles transitions near year boundaries. (Thanks to Tim Parenti for reporting the problem.) - An access to uninitalized data has been fixed. + An access to uninitialized data has been fixed. (Thanks to Jörg Richter for reporting the problem.) When THREAD_SAFE is defined, the code ports to the C11 memory model. diff --git a/europe b/europe index 4219828..2ad164b 100644 --- a/europe +++ b/europe @@ -2425,7 +2425,7 @@ Zone Europe/Kaliningrad 1:22:00 - LMT 1893 Apr # attributes the 1982 changes to the Act of the Council of Ministers # of the USSR No. 126 from 18.02.1982. 1980-925.txt also adds # Udmurtia to the list of affected territories and lists Khatangsky -# district separately from Taymyr Autonomous Okurg. Probably erroneously. +# district separately from Taymyr Autonomous Okrug. Probably erroneously. # # The affected territories are currently listed under Europe/Moscow, # Asia/Yekaterinburg and Asia/Krasnoyarsk. @@ -2756,7 +2756,7 @@ Zone Asia/Novosibirsk 5:31:40 - LMT 1919 Dec 14 6:00 # Note that time belts (numbered from 2 (Moscow) to 12 according to their # GMT/UTC offset and having too many exceptions like regions formally # belonging to one belt but using time from another) were replaced -# with time zones in 2011 with different numberings (there was a +# with time zones in 2011 with different numbering (there was a # 2-hour gap between second and third zones in 2011-2014). # From Stepan Golosunov (2016-04-12): diff --git a/factory b/factory index 7c86430..75fa4a1 100644 --- a/factory +++ b/factory @@ -3,8 +3,8 @@ # For distributors who don't want to put time zone specification in # their installation procedures. Users that run 'date' will get the -# time zone abbrevation "-00", indicating that the actual time zone is -# unknown. +# time zone abbreviation "-00", indicating that the actual time zone +# is unknown. # Zone NAME GMTOFF RULES FORMAT Zone Factory 0 - -00 diff --git a/tz-how-to.html b/tz-how-to.html index a777a4e..feb47dd 100644 --- a/tz-how-to.html +++ b/tz-how-to.html @@ -251,7 +251,7 @@ local standard time (different from wall clock time when observing daylight saving time); or it can be suffixed with ‘g’, ‘u’, or ‘z’, all three of which mean the standard time at the -<a href="https://en.wikipedia.org/wiki/Prime_Meridian">prime meridan</a>. +<a href="https://en.wikipedia.org/wiki/Prime_Meridian">prime meridian</a>. ‘g’ stands for “<a href="https://en.wikipedia.org/wiki/Greenwich_Mean_Time">GMT</a>”; ‘u’ stands for “<a -- 2.7.4

1 0

[PROPOSED PATCH] Port 'make check_web' to Fedora
by Paul Eggert Aug. 23, 2016

Aug. 23, 2016

* Makefile (SGML_CATALOG_FILES), NEWS: Port to Fedora 23, where the catalog is in /usr/share/sgml/html/4.01/HTML4.cat. --- Makefile | 8 ++++---- NEWS | 4 ++++ 2 files changed, 8 insertions(+), 4 deletions(-) diff --git a/Makefile b/Makefile index b71211e..f6754af 100644 --- a/Makefile +++ b/Makefile @@ -272,16 +272,16 @@ AWK= awk KSHELL= /bin/bash # The path where SGML DTDs are kept and the catalog file(s) to use when -# validating. The default is appropriate for Ubuntu 13.10. +# validating. The default should work on both Debian and Red Hat. SGML_TOPDIR= /usr SGML_DTDDIR= $(SGML_TOPDIR)/share/xml/w3c-sgml-lib/schema/dtd SGML_SEARCH_PATH= $(SGML_DTDDIR)/REC-html401-19991224 SGML_CATALOG_FILES= \ - $(SGML_TOPDIR)/share/doc/w3-recs/html/www.w3.org/TR/1999/REC-html401-19991224/HTML4.cat + $(SGML_TOPDIR)/share/doc/w3-recs/html/www.w3.org/TR/1999/REC-html401-19991224/HTML4.cat:$(SGML_TOPDIR)/share/sgml/html/4.01/HTML4.cat # The name, arguments and environment of a program to validate your web pages. -# See <http://www.jclark.com/sp/> for a validator, and -# <http://validator.w3.org/source/> for a validation library. +# See <http://openjade.sourceforge.net/doc/> for a validator, and +# <https://validator.w3.org/source/> for a validation library. VALIDATE = nsgmls VALIDATE_FLAGS = -s -B -wall -wno-unused-param VALIDATE_ENV = \ diff --git a/NEWS b/NEWS index 548de8f..4c18e55 100644 --- a/NEWS +++ b/NEWS @@ -42,6 +42,8 @@ Unreleased, experimental changes (Thanks to Jon Skeet for suggesting that an option was needed, and thanks to Tim Parenti and Chris Rovick for further comments.) + Changes to build procedure + The tzdata distribution has a new file to2050.tzs that contains what should be the output of 'zdump -i -c 2050' on primary zones. 'make check' now checks that zdump generates this output. @@ -57,6 +59,8 @@ Unreleased, experimental changes significantly smaller than gzip. (Thanks to Oscar van Vlijmen for comments on the format.) + 'make check_web' now works on Fedora-like distributions. + Changes to documentation and commentary tzfile.5 now documents the new restriction on POSIX TZ-like -- 2.5.5

1 0

Re: [tz] [PROPOSED PATCH 2/2] Use lz format for new tarball
by vanadovv＠hetnet.nl Aug. 22, 2016

Aug. 22, 2016

There are also Windows users, not only *nix users! So, please use a compression format that can be handled easily by Windows users as well. For instance, choose a format from the list that 7Zip can handle: http://www.7-zip.org/ Yes, I know, one can allways install yet again another program for one purpose only (http://lzip.nongnu.org/lzip.html) but let's try to keep things simple. Cheers! Oscar van Vlijmen >----Origineel Bericht---- >Van : eggert(a)cs.ucla.edu >Datum : 22/08/2016 05:56 >Aan : tz(a)iana.org >Onderwerp : [tz] [PROPOSED PATCH 2/2] Use lz format for new tarball > [snip] >index 18b7c9d..61213b0 100644 >--- a/NEWS >+++ b/NEWS >@@ -33,13 +33,14 @@ Unreleased, experimental changes > 'make check' now checks that zdump generates this output. > > A new distribution format is available in the tarball >- tzdb-VERSION.tar.gz and the signature tzdb-VERSION.tar.gz.asc. >+ tzdb-VERSION.tar.lz and the signature tzdb-VERSION.tar.lz.asc. > The new tarball has the contents of tzcodeVERSION.tar.gz and > tzdataVERSION.tar.gz, in a single top-level directory 'tzdb' with > all other files under this directory, as is typical for software > distributions. The new format is intended to replace the old > tarball pair. The old format will continue to be distributed for >- a while. >+ a while. The new format uses lzip compression, which is >+ significantly smaller than gzip and is simpler than xz. > > Changes to documentation and commentary > >-- >2.5.5

2 1

The West Wing: 20 Hours in America
by Matt Johnson Aug. 22, 2016

Aug. 22, 2016

This is already mentioned in the arts file, but I just found a clip of it: https://www.youtube.com/watch?v=-J1NHzQ1sgc Cheers! -Matt

2 1

Julia tz compiler
by Curtis Vogt Aug. 22, 2016

Aug. 22, 2016

Hello, I'm one of the main contributors to TimeZones.jl <http://github.com/JuliaTime/TimeZones.jl>: a tz compiler written in the programming language Julia <http://julialang.org/>. I would appreciate if TimeZones.jl could be added to the "Other tz compilers" section on the https://www.iana.org/time-zones/repository/tz-link.html page. The blurb could be written as: [TimeZones.jl – Time zone database access for Julia]( > https://github.com/JuliaTime/TimeZones.jl) compiles tz source into > [Julia](http://julialang.org/). It is freely available under the MIT lic > ense. Thanks for your time, Curtis Vogt

2 1

[PROPOSED PATCH] Distribute .tzs file for regression testing
by Paul Eggert Aug. 22, 2016

Aug. 22, 2016

* NEWS: Document this. * Makefile (TZS_YEAR, TZS, TZS_NEW, TZS_DEPS): New macros. (ENCHILADA): Add TZS. ($(TZS_NEW), $(TZS), force_tzs, check_tzs): New targets. (check): Add check_tzs. (clean): Remove *.dir. (maintainer-clean): Remove $(TZS). (set-timestamps.out): Set $(TZS)'s time stamp. (check_public, check_time_t_alternatives): Use a temporary directory name ending in .dir, to make it easier to clean these directories out systematically. (tzdata$(VERSION).tar.gz): Add $(TZS). (.PHONY): Add force_tzs, check_tzs. --- Makefile | 71 ++++++++++++++++++++++++++++++++++++++++++++++------------------ NEWS | 12 +++++++---- 2 files changed, 59 insertions(+), 24 deletions(-) diff --git a/Makefile b/Makefile index bbe1ba8..fc18819 100644 --- a/Makefile +++ b/Makefile @@ -378,7 +378,12 @@ DATA= $(YDATA) $(NDATA) backzone $(TABDATA) \ leap-seconds.list yearistype.sh AWK_SCRIPTS= checklinks.awk checktab.awk leapseconds.awk MISC= $(AWK_SCRIPTS) zoneinfo2tdf.pl -ENCHILADA= $(COMMON) $(DOCS) $(SOURCES) $(DATA) $(MISC) +TZS_YEAR= 2050 +TZS= to$(TZS_YEAR).tzs +TZS_NEW= to$(TZS_YEAR)new.tzs +TZS_DEPS= $(PRIMARY_YDATA) asctime.c localtime.c \ + private.h tzfile.h zdump.c zic.c +ENCHILADA= $(COMMON) $(DOCS) $(SOURCES) $(DATA) $(MISC) $(TZS) # And for the benefit of csh users on systems that assume the user # shell should be used to handle commands in Makefiles. . . @@ -477,6 +482,27 @@ posix_packrat: zones: $(REDO) +$(TZS_NEW): $(TDATA) zdump zic + mkdir -p tzs.dir + $(zic) -d tzs.dir $(TDATA) + $(AWK) '/^Link/{print $$1 "\t" $$2 "\t" $$3}' \ + $(TDATA) | LC_ALL=C sort >$@.out + zones=$$($(AWK) -v wd="$$(pwd)" \ + '/^Zone/{print wd "/tzs.dir/" $$2}' $(TDATA) \ + | LC_ALL=C sort) && \ + ./zdump -i -c $(TZS_YEAR) $$zones >>$@.out + sed 's,^TZ=".*tzs\.dir/,TZ=",' $@.out >$@ + rm -fr tzs.dir $@.out + +# If $(TZS) does not already exist (e.g., old-format tarballs), create it. +# If it exists but 'make check_tzs' fails, a maintainer should inspect the +# failed output and fix the inconsistency, perhaps by running 'make force_tzs'. +$(TZS): + $(MAKE) force_tzs + +force_tzs: $(TZS_NEW) + cp $(TZS_NEW) $(TZS) + libtz.a: $(LIBOBJS) $(AR) ru $@ $(LIBOBJS) $(RANLIB) $@ @@ -496,7 +522,7 @@ tzselect: tzselect.ksh chmod +x $@ check: check_character_set check_white_space check_links check_sorted \ - check_tables check_web + check_tables check_tzs check_web check_character_set: $(ENCHILADA) LC_ALL=en_US.utf8 && export LC_ALL && \ @@ -532,6 +558,9 @@ check_tables: checktab.awk $(PRIMARY_YDATA) $(ZONETABLES) || exit; \ done +check_tzs: $(TZS) $(TZS_NEW) + diff -u $(TZS) $(TZS_NEW) + check_web: $(WEB_PAGES) $(VALIDATE_ENV) $(VALIDATE) $(VALIDATE_FLAGS) $(WEB_PAGES) @@ -539,12 +568,12 @@ clean_misc: rm -f core *.o *.out \ date tzselect version.h zdump zic yearistype libtz.a clean: clean_misc - rm -fr tzpublic + rm -fr *.dir $(TZS_NEW) maintainer-clean: clean @echo 'This command is intended for maintainers to use; it' @echo 'deletes files that may need special tools to rebuild.' - rm -f leapseconds $(MANTXTS) *.asc *.tar.gz + rm -f leapseconds $(MANTXTS) $(TZS) *.asc *.tar.gz names: @echo $(ENCHILADA) @@ -591,6 +620,7 @@ set-timestamps.out: $(ENCHILADA) touch -cmr `ls -t $$file workman.sh | sed 1q` $$file.txt || \ exit; \ done + touch -cmr $$(ls -t $(TZS_DEPS) | sed 1q) $(TZS) touch $@ # The zics below ensure that each data file can stand on its own. @@ -599,12 +629,12 @@ set-timestamps.out: $(ENCHILADA) check_public: $(MAKE) maintainer-clean $(MAKE) "CFLAGS=$(GCC_DEBUG_FLAGS)" ALL - mkdir tzpublic + mkdir -p public.dir for i in $(TDATA) ; do \ - $(zic) -v -d tzpublic $$i 2>&1 || exit; \ + $(zic) -v -d public.dir $$i 2>&1 || exit; \ done - $(zic) -v -d tzpublic $(TDATA) - rm -fr tzpublic + $(zic) -v -d public.dir $(TDATA) + rm -fr public.dir # Check that the code works under various alternative # implementations of time_t. @@ -616,15 +646,15 @@ check_time_t_alternatives: fi && \ zones=`$(AWK) '/^[^#]/ { print $$3 }' <zone1970.tab` && \ for type in $(TIME_T_ALTERNATIVES); do \ - mkdir -p tzpublic/$$type && \ + mkdir -p time_t.dir/$$type && \ $(MAKE) clean_misc && \ - $(MAKE) TOPDIR=`pwd`/tzpublic/$$type \ + $(MAKE) TOPDIR=$$(pwd)/time_t.dir/$$type \ CFLAGS='$(CFLAGS) -Dtime_tz='"'$$type'" \ REDO='$(REDO)' \ install && \ diff $$quiet_option -r \ - tzpublic/int64_t/etc/zoneinfo \ - tzpublic/$$type/etc/zoneinfo && \ + time_t.dir/int64_t/etc/zoneinfo \ + time_t.dir/$$type/etc/zoneinfo && \ case $$type in \ int32_t) range=-2147483648,2147483647;; \ uint32_t) range=0,4294967296;; \ @@ -633,14 +663,14 @@ check_time_t_alternatives: *) range=-10000000000,10000000000;; \ esac && \ echo checking $$type zones ... && \ - tzpublic/int64_t/etc/zdump -V -t $$range $$zones \ - >tzpublic/int64_t.out && \ - tzpublic/$$type/etc/zdump -V -t $$range $$zones \ - >tzpublic/$$type.out && \ - diff -u tzpublic/int64_t.out tzpublic/$$type.out \ + time_t.dir/int64_t/etc/zdump -V -t $$range $$zones \ + >time_t.dir/int64_t.out && \ + time_t.dir/$$type/etc/zdump -V -t $$range $$zones \ + >time_t.dir/$$type.out && \ + diff -u time_t.dir/int64_t.out time_t.dir/$$type.out \ || exit; \ done - rm -fr tzpublic + rm -fr time_t.dir tarballs: tzcode$(VERSION).tar.gz tzdata$(VERSION).tar.gz @@ -652,7 +682,7 @@ tzcode$(VERSION).tar.gz: set-timestamps.out tzdata$(VERSION).tar.gz: set-timestamps.out LC_ALL=C && export LC_ALL && \ - tar $(TARFLAGS) -cf - $(COMMON) $(DATA) $(MISC) | \ + tar $(TARFLAGS) -cf - $(COMMON) $(DATA) $(MISC) $(TZS) | \ gzip $(GZIPFLAGS) > $@ signatures: tzcode$(VERSION).tar.gz.asc tzdata$(VERSION).tar.gz.asc @@ -688,7 +718,8 @@ zic.o: private.h tzfile.h version.h .PHONY: ALL INSTALL all .PHONY: check check_character_set check_links .PHONY: check_public check_sorted check_tables -.PHONY: check_time_t_alternatives check_web check_white_space clean clean_misc +.PHONY: check_time_t_alternatives check_tzs check_web check_white_space +.PHONY: clean clean_misc force_tzs .PHONY: install install_data maintainer-clean names .PHONY: posix_only posix_packrat posix_right .PHONY: public right_only right_posix signatures tarballs typecheck diff --git a/NEWS b/NEWS index 3d01581..023883b 100644 --- a/NEWS +++ b/NEWS @@ -2,18 +2,18 @@ News for the tz database Unreleased, experimental changes - Changes affecting future time stamps + Changes to future time stamps New leap second 2016-12-31 23:59:60 UTC as per IERS Bulletin C 52. (Thanks to Tim Parenti.) - Changes affecting past time stamps + Changes to past time stamps For America/Los_Angeles, spring-forward transition times have been corrected from 02:00 to 02:01 in 1948, and from 02:00 to 01:00 in 1950-1966. - Changes affecting code + Changes to code zic no longer generates binary files containing POSIX TZ-like strings that disagree with the local time type after the last @@ -28,7 +28,11 @@ Unreleased, experimental changes (Thanks to Jon Skeet for suggesting that an option was needed, and thanks to Tim Parenti and Chris Rovick for further comments.) - Changes affecting documentation and commentary + The tzdata distribution has a new file to2050.tzs that contains + what should be the output of 'zdump -i -c 2050' on primary zones. + 'make check' now checks that zdump generates this output. + + Changes to documentation and commentary tzfile.5 now documents the new restriction on POSIX TZ-like strings that is now implemented by zic. -- 2.5.5

1 0

[PROPOSED PATCH] Fix 1948-1966 transitions for Los Angeles
by Paul Eggert Aug. 20, 2016

Aug. 20, 2016

These changes came from research I did to check the historical background behind Assembly Bill 385, which would abolish daylight saving time in California, and which has passed the CA Senate Appropriations Committee's suspense file. See: White JB. Bill letting California end Daylight Saving Time clears key committee. Sacramento Bee 2016-08-11. http://www.sacbee.com/news/politics-government/capitol-alert/article9511673… * NEWS, northamerica (CA): For America/Los_Angeles, correct spring-forward transition times from 02:00 to 02:01 in 1948, from 02:00 to 01:00 in 1950-1966. Correct the fall-back transition date for early 1949 from 1949-01-01 to 1949-01-16. --- NEWS | 7 +++++++ northamerica | 35 ++++++++++++++++++++++++++++++++--- 2 files changed, 39 insertions(+), 3 deletions(-) diff --git a/NEWS b/NEWS index ba26a49..a8479eb 100644 --- a/NEWS +++ b/NEWS @@ -7,6 +7,13 @@ Unreleased, experimental changes New leap second 2016-12-31 23:59:60 UTC as per IERS Bulletin C 52. (Thanks to Tim Parenti.) + Changes affecting past time stamps + + For America/Los_Angeles, spring-forward transition times have been + corrected from 02:00 to 02:01 in 1948, and from 02:00 to 01:00 in + 1950-1966. The fall-back transition date for early 1949 has been + corrected from 1949-01-01 to 1949-01-16. + Changes affecting code zic no longer generates binary files containing POSIX TZ-like diff --git a/northamerica b/northamerica index 6256f97..c9c2061 100644 --- a/northamerica +++ b/northamerica @@ -413,11 +413,40 @@ Zone America/Denver -6:59:56 - LMT 1883 Nov 18 12:00:04 # north of the Salmon River, and the towns of Burgdorf and Warren), # Nevada (except West Wendover), Oregon (except the northern 3/4 of # Malheur county), and Washington + +# From Paul Eggert (2016-08-19): +# In 1948 California had an electricity shortage. To save electricity, +# in early February PG&E changed power frequency from 60 to 59.5 Hz during +# daylight hours, causing electric clocks to lose six minutes per day. +# (This did not change legal time, and is not part of the data here.) +# See: Ross SA. An energy crisis from the past: Northern California in 1948. +# Working Paper No. 8, Institute of Governmental Studies, UC Berkeley, 1973-11. +# http://escholarship.org/uc/item/8x22k30c +# +# In another measure to save electricity, DST was instituted from 1948-03-14 +# at 02:01 to 1949-01-16 at 02:00, with the governor having the option to move +# the fallback transition earlier. See pages 3-4 of: +# http://clerk.assembly.ca.gov/sites/clerk.assembly.ca.gov/files/archive/Stat… +# Apparently the governor did not exercise the option. +# +# In response: +# +# Governor Warren received a torrent of objecting mail, and it is not too much +# to speculate that the objections to Daylight Saving Time were one important +# factor in the defeat of the Dewey-Warren Presidential ticket in California. +# -- Ross, p 25 +# +# Despite the controversy, in 1949 California voters approved Proposition 12, +# which established DST from April's last Sunday at 01:00 until September's +# last Sunday at 02:00. This was amended by 1962's Proposition 6, which changed +# the fall-back date to October's last Sunday. See: +# http://repository.uchastings.edu/cgi/viewcontent.cgi?article=1501&context=c… +# http://repository.uchastings.edu/cgi/viewcontent.cgi?article=1636&context=c… # # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER -Rule CA 1948 only - Mar 14 2:00 1:00 D -Rule CA 1949 only - Jan 1 2:00 0 S -Rule CA 1950 1966 - Apr lastSun 2:00 1:00 D +Rule CA 1948 only - Mar 14 2:01 1:00 D +Rule CA 1949 only - Jan 16 2:00 0 S +Rule CA 1950 1966 - Apr lastSun 1:00 1:00 D Rule CA 1950 1961 - Sep lastSun 2:00 0 S Rule CA 1962 1966 - Oct lastSun 2:00 0 S # Zone NAME GMTOFF RULES FORMAT [UNTIL] -- 2.7.4

3 4

Use of <> delimiters in TZ string is not documented
by Alexander Belopolsky Aug. 19, 2016

Aug. 19, 2016

The Asia/Almaty tzfile generated from recent Github tzdata snapshot contains the following TZ string at the end of the file $ git describe 2016f-7-ge0a7616 $ strings etc/zoneinfo/Asia/Almaty | tail -1 <+06>-6 This format is not documented in newtzset.3: When TZ is used directly as a specification of the time conversion information, it must have the following syntax (spaces inserted for clarity): stdoffset[dst[offset][,rule]] Where: std and dst Three or more bytes that are the designation for the standard (std) or summer (dst) time zone. Only std is required; if dst is missing, then summer time does not apply in this locale. Upper- and lowercase letters are explicitly allowed. Any characters except a leading colon (:), digits, comma (,), ASCII minus (-), ASCII plus (+), and NUL bytes are allowed.

3 3