- tz - lists.iana.org

DPRK to revert to UTC+9 from UTC+8:30
by Kang Seonghoon April 30, 2018

April 30, 2018

On 2018-04-29 (+09:00), according to Yoon Young-chan, senior presidental secretary for public relations of South Korea, has announced that North Korea will revert its time zone from UTC+8:30 (PYT; Pyongyang Time) back to UTC+9 (KST; Korea Standard Time), in lieu of the recent Panmunjom Declaration. Yet another time to change tzdata? Source: South and North agreed to unify PYT to KST, Yonhap News http://m.yna.co.kr/kr/contents/?cid=AKR20180429018500001 (no English translation exists right now) -- -- Kang Seonghoon | https://mearie.org/ -- Opinions expressed in this email do not necessarily represent the views of my employer. --

4 4

North Korea timezone to become GMT+9 from May 5 2018
by Phake Nick April 30, 2018

April 30, 2018

The URL to the announcement cannot be directly copied, but you can access www.kcna.kp then select "English" on top right hand corner, and then there will be an article titled "SPA Presidium of DPRK Decides to Reset Pyongyang Time" which talk about the upcoming change in time in North Korea. Media outside North Korea have reported about it too. However, there are no info with respect to exactly which moment in May 5 are they switching their timezone

3 3

North Korea to match South Korea's time zone
by Arthur David Olson April 29, 2018

April 29, 2018

A tweet from Jef Poskanzer... https://twitter.com/jef_poskanzer/status/990430801903865856 ...alerted me to North Korea's plan to match South Korea's time zone. An AP item on the matter... https://apnews.com/301adfec088647c1b1cbc69eb4b0949a ...cites South Korean President Moon Jae-in's spokesperson Yoon Young-chan; referring to North Korean leader Kim Jong Un, " Yoon said Kim...revealed plans to re-adjust its current time zone to match the South’s." No word in the AP item on specifics of the plan. @dashdashado

2 1

[PROPOSED] Support zi parsers that mishandle negative DST offsets
by Paul Eggert April 23, 2018

April 23, 2018

This is intended to provide a way to support both clients that require data to have only positive DST offsets, and clients that do not have this restriction. * Makefile (XDST, SDST): New macros. (TZDATA_ZI_DEPS): Add zidst.awk. (DSTDATA_ZI_DEPS): New macro. (all): Depend on fulldata.zi and pdstdata.zi. (fulldata.zi pdstdata.zi): New rule. (tzdata.zi): Use $(XDST)data.zi instead of reading original source. (check_zishrink): Check zidst.awk, too. (clean): Remove all *.zi files, not just tzdata.zi. * NEWS, europe: Mention this. * zidst.awk: New file. --- Makefile | 63 ++++++++++++++++++++++++++++++++++++++++++++++++++++----------- NEWS | 30 ++++++++++++++++++++++++++++++ europe | 39 ++++++++++++++++++++++----------------- zidst.awk | 50 ++++++++++++++++++++++++++++++++++++++++++++++++++ 4 files changed, 154 insertions(+), 28 deletions(-) create mode 100644 zidst.awk diff --git a/Makefile b/Makefile index 8c84cd9..92ddb80 100644 --- a/Makefile +++ b/Makefile @@ -10,6 +10,26 @@ VERSION= unknown # Email address for bug reports. BUGEMAIL= tz(a)iana.org +# To install the full data, which can contain daylight saving time +# offsets that are negative (relative to standard time), use +# XDST= full +# To install data containing only positive daylight saving time +# offsets, but otherwise as close to the full data as practical, use +# XDST= pdst +XDST= pdst +# Parsers requiring DST offsets to be positive should use the file +# pdstdata.zi, which contains almost all the data of 'africa' etc., +# except with positive DST offsets. This works around a problem that +# was discovered in January 2018 with negative DST in tests for ICU +# and OpenJDK. See: +# https://mm.icann.org/pipermail/tz/2018-January/025825.html +# https://mm.icann.org/pipermail/tz/2018-January/025822.html +# Currently the 'africa' etc. files use pdst form if comments are +# ignored, to ease transition for parsers that do not support +# negative DST offsets. This is intended to change to full form at +# some point, so that full-featured zi parsers that use the 'africa' +# files will get the full data without changing anything. + # Change the line below for your time zone (after finding the zone you want in # the time zone files, or adding it to a time zone file). # Alternately, if you discover you've got the wrong time zone, you can just @@ -463,7 +483,8 @@ TDATA= $(YDATA) $(NDATA) $(BACKWARD) ZONETABLES= zone1970.tab zone.tab TABDATA= iso3166.tab $(TZDATA_TEXT) $(ZONETABLES) LEAP_DEPS= leapseconds.awk leap-seconds.list -TZDATA_ZI_DEPS= zishrink.awk version $(TDATA) $(PACKRATDATA) +TZDATA_ZI_DEPS= zidst.awk zishrink.awk version $(TDATA) $(PACKRATDATA) +DSTDATA_ZI_DEPS= zidst.awk $(TDATA) $(PACKRATDATA) DATA= $(TDATA_TO_CHECK) backzone iso3166.tab leap-seconds.list \ leapseconds yearistype.sh $(ZONETABLES) AWK_SCRIPTS= checklinks.awk checktab.awk leapseconds.awk zishrink.awk @@ -500,7 +521,8 @@ VERSION_DEPS= \ SHELL= /bin/sh -all: tzselect yearistype zic zdump libtz.a $(TABDATA) +all: tzselect yearistype zic zdump libtz.a $(TABDATA) \ + fulldata.zi pdstdata.zi ALL: all date $(ENCHILADA) @@ -535,11 +557,15 @@ 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) +# These files can be tailored by setting BACKWARD, PACKRATDATA, etc. +fulldata.zi pdstdata.zi: $(DSTDATA_ZI_DEPS) + $(AWK) -v outfile='$@' -f zidst.awk $(TDATA) $(PACKRATDATA) \ + >$@.out + mv $@.out $@ +tzdata.zi: $(XDST)data.zi version version=`sed 1q version` && \ LC_ALL=C $(AWK) -v version="$$version" -f zishrink.awk \ - $(TDATA) $(PACKRATDATA) >$@.out + $(XDST)data.zi >$@.out mv $@.out $@ version.h: version @@ -721,17 +747,32 @@ check_tzs: $(TZS) $(TZS_NEW) check_web: tz-how-to.html $(VALIDATE_ENV) $(VALIDATE) $(VALIDATE_FLAGS) tz-how-to.html -# Check that tzdata.zi generates the same binary data that its sources do. -check_zishrink: tzdata.zi zic leapseconds $(PACKRATDATA) $(TDATA) +# The format of the source files, either full or pdst. +# Currently they are in pdst format, but this is expected to change. +SDST = pdst + +# Check that zishrink.awk does not alter the data, and that zidst.awk +# preserves $(SDST) data. +check_zishrink: zic leapseconds $(PACKRATDATA) $(TDATA) \ + $(XDST)data.zi tzdata.zi for type in posix right; do \ - mkdir -p time_t.dir/$$type time_t.dir/$$type-shrunk && \ + mkdir -p time_t.dir/$$type time_t.dir/$$type-$(SDST) \ + time_t.dir/$$type-shrunk && \ case $$type in \ right) leap='-L leapseconds';; \ *) leap=;; \ esac && \ - $(ZIC) $$leap -d time_t.dir/$$type $(TDATA) && \ - $(AWK) '/^Rule/' $(TDATA) | \ + $(ZIC) $$leap -d time_t.dir/$$type $(XDST)data.zi && \ + $(AWK) '/^Rule/' $(XDST)data.zi | \ $(ZIC) $$leap -d time_t.dir/$$type - $(PACKRATDATA) && \ + case $(XDST) in \ + $(SDST)) \ + $(ZIC) $$leap -d time_t.dir/$$type-$(SDST) $(TDATA) && \ + $(AWK) '/^Rule/' $(TDATA) | \ + $(ZIC) $$leap -d time_t.dir/$$type-$(SDST) \ + $(XDST)data.zi && \ + diff -r time_t.dir/$$type time_t.dir/$$type-$(SDST);; \ + esac && \ $(ZIC) $$leap -d time_t.dir/$$type-shrunk tzdata.zi && \ diff -r time_t.dir/$$type time_t.dir/$$type-shrunk || exit; \ done @@ -741,7 +782,7 @@ clean_misc: rm -f core *.o *.out \ date tzselect version.h zdump zic yearistype libtz.a clean: clean_misc - rm -fr *.dir tzdata.zi tzdb-*/ $(TZS_NEW) + rm -fr *.dir *.zi tzdb-*/ $(TZS_NEW) maintainer-clean: clean @echo 'This command is intended for maintainers to use; it' diff --git a/NEWS b/NEWS index 4f763c0..c455f3c 100644 --- a/NEWS +++ b/NEWS @@ -2,6 +2,36 @@ News for the tz database Unreleased, experimental changes + Briefly: + Support zi parsers that mishandle negative DST offsets + + Changes to build procedure + + The new XDST macro in the Makefile lets the installer choose + XDST=full, which allows arbitrary DST offsets in the data, or + XDST=pdst, which allows only positive DST offsets. Choosing + XDST=full is arguably more correct for Ireland, which observes + Irish Standard Time (IST, UTC+01) in summer and GMT (UTC) in + winter. Choosing XDST=pdst is better for zoneinfo parsers that do + not work well with negative DST offsets, notably OpenJDK+CLDR. + On platforms using tzcode or similar APIs, XDST should not affect + any behavior other than that depending on the tm_isdst flag. + + For now this change does not affect client-visible behavior by + default, as the Makefile defaults to XDST=pdst and uncommented + parts of the data source files contain only pdst-format data. + After a bit of time for testing, XDST=full and full-format source + files are planned to become the default, so that parsers that + support negative DST offsets can get full data without changing + their build procedures. Parsers requiring positive DST offsets + should use the new file pdstdata.zi instead of tzdata.zi or the + source files 'africa' etc.: pdstdata.zi is pdst-compatible, it is + automatically built from the data source files, and it will + continue to be pdst-compatible regardless of XDST. To get + full-format data now, use the new file fulldata.zi, which will + continue to be full-format regardless of XDST. To get the format + selected by XDST, use tzdata.zi. + Changes to code The code is a bit more portable to MS-Windows. (Thanks to Manuela diff --git a/europe b/europe index 6c1ccbe..5aeda33 100644 --- a/europe +++ b/europe @@ -508,11 +508,27 @@ Link Europe/London Europe/Jersey Link Europe/London Europe/Guernsey Link Europe/London Europe/Isle_of_Man -# From Paul Eggert (2018-01-19): +# From Paul Eggert (2018-01-30): +# In January 2018 we discovered that the negative DST offsets in the +# Eire rules cause problems with tests for ICU: +# https://mm.icann.org/pipermail/tz/2018-January/025825.html +# and with tests for OpenJDK: +# https://mm.icann.org/pipermail/tz/2018-January/025822.html +# To work around this problem, zidst.awk translates the following data +# lines into two forms. First, fulldata.zi contains the full data, +# which includes negative DST offsets. Second, pdstdata.zi uses a +# traditional approximation for Irish time stamps after 1971-10-31 +# 02:00 UTC; although this approximation has tm_isdst flags that are +# the reverse of the full data, its UTC offsets are correct and this +# suffices for ICU and OpenJDK. Although this source file currently +# has pdstdata.zi lines active and fulldata.zi lines commented out, +# this is intended to change in the near future and downstream code +# should not rely on it. +# # The following is like GB-Eire and EU, except with standard time in # summer and negative daylight saving time in winter. -# Although currently commented out, this will need to become uncommented -# once the ICU/OpenJDK workaround is removed; see below. +# This rule set is active in fulldata.zi and is commented out in +# pdstdata.zi. # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S #Rule Eire 1971 only - Oct 31 2:00u -1:00 GMT #Rule Eire 1972 1980 - Mar Sun>=16 2:00u 0 IST @@ -533,24 +549,13 @@ Zone Europe/Dublin -0:25:00 - LMT 1880 Aug 2 0:00 1:00 IST 1947 Nov 2 2:00s 0:00 - GMT 1948 Apr 18 2:00s 0:00 GB-Eire GMT/IST 1968 Oct 27 -# From Paul Eggert (2018-01-18): -# The next line should look like this: +# The next line is active in fulldata.zi and commented out in pdstdata.zi. # 1:00 Eire IST/GMT -# However, in January 2018 we discovered that the Eire rules cause -# problems with tests for ICU: -# https://mm.icann.org/pipermail/tz/2018-January/025825.html -# and with tests for OpenJDK: -# https://mm.icann.org/pipermail/tz/2018-January/025822.html -# To work around this problem, use a traditional approximation for -# time stamps after 1971-10-31 02:00 UTC, to give ICU and OpenJDK -# developers breathing room to fix bugs. This approximation has -# correct UTC offsets, but results in tm_isdst flags are the reverse -# of what they should be. This workaround is temporary and should be -# removed reasonably soon. +# These three lines are active in pdstdata.zi and commented out in +# fulldata.zi. 1:00 - IST 1971 Oct 31 2:00u 0:00 GB-Eire GMT/IST 1996 0:00 EU GMT/IST -# End of workaround for ICU and OpenJDK bugs. ############################################################################### diff --git a/zidst.awk b/zidst.awk new file mode 100644 index 0000000..7885e9a --- /dev/null +++ b/zidst.awk @@ -0,0 +1,50 @@ +# Convert tzdata source into full or positive-DST form + +# Contributed by Paul Eggert. This file is in the public domain. + +# This is not a general-purpose converter; it is designed for current tzdata. +# +# When converting to full form, the output can use negative DST offsets. +# +# When converting to positive-DST form, the output uses only positive +# DST offsets. The idea is for the output data to simulate the +# behavior of the input data as best it can within the constraints of +# positive DST offsets. +# +# In the input, lines requiring the full format are commented #[full] +# and the positive DST near-equivalents are commented #[pdst]. + +BEGIN { + dst_type["full"] = 1 + dst_type["pdst"] = 1 + + # The command line should set OUTFILE to the name of the output file, + # which should start with either "full" or "pdst". + todst = substr(outfile, 1, 4) + if (!dst_type[todst]) exit 1 +} + +/^Zone/ { zone = $2 } + +{ + in_comment = /^#/ + + # Test whether this line should differ between the full and the pdst versions. + Rule_Eire = /^#?Rule[\t ]+Eire[\t ]/ + Zone_Dublin_post_1968 \ + = (zone == "Europe/Dublin" && /^#?[\t ]+[01]:00[\t ]/ \ + && (!$(in_comment + 4) || 1968 < $(in_comment + 4))) + + # If so, uncomment the desired version and comment out the undesired one. + if (Rule_Eire || Zone_Dublin_post_1968) { + if ((Rule_Eire \ + || (Zone_Dublin_post_1968 && $(in_comment + 3) == "IST/GMT")) \ + == (todst == "full")) { + sub(/^#/, "") + } else if (/^[^#]/) { + sub(/^/, "#") + } + } +} + +{ print } -- 2.14.3

7 14

[PATCH] Fix ziguard.awk Namibia invalid assumption
by Paul Eggert April 22, 2018

April 22, 2018

* ziguard.awk: Don’t assume input is in rearguard format. --- ziguard.awk | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/ziguard.awk b/ziguard.awk index 7cdceab..dbe64d6 100644 --- a/ziguard.awk +++ b/ziguard.awk @@ -63,7 +63,11 @@ outfile != "main.zi" { || (1994 <= $(in_comment + 4) && $(in_comment + 4) <= 2017) \ || in_comment + 3 == NF)) if (Rule_Namibia || Zone_using_Namibia_rule) { - if (in_comment == vanguard) { + if ((Rule_Namibia \ + ? ($(in_comment + 9) ~ /^-/ \ + || ($(in_comment + 9) == 0 && $(in_comment + 10) == "CAT")) \ + : $(in_comment + 1) == "2:00" && $(in_comment + 2) == "Namibia") \ + == vanguard) { uncomment = in_comment } else { comment_out = !in_comment -- 2.14.3

1 0

[PROPOSED] Update and/or clean up POSIX version info
by Paul Eggert April 15, 2018

April 15, 2018

--- asctime.c | 12 +++--------- localtime.c | 7 +++---- theory.html | 2 +- 3 files changed, 7 insertions(+), 14 deletions(-) diff --git a/asctime.c b/asctime.c index a55f785..56c54b3 100644 --- a/asctime.c +++ b/asctime.c @@ -1,3 +1,5 @@ +/* asctime and asctime_r a la POSIX and ISO C, except pad years before 1000. */ + /* ** This file is in the public domain, so clarified as of ** 1996-06-05 by Arthur David Olson. @@ -29,7 +31,7 @@ ** leading zeroes to get the newline in the traditional place. ** The -4 ensures that we get four characters of output even if ** we call a strftime variant that produces fewer characters for some years. -** The ISO C 1999 and POSIX 1003.1-2004 standards prohibit padding the year, +** The ISO C and POSIX standards prohibit padding the year, ** but many implementations pad anyway; most likely the standards are buggy. */ #ifdef __GNUC__ @@ -64,10 +66,6 @@ static char buf_asctime[MAX_ASCTIME_BUF_SIZE]; -/* -** A la ISO/IEC 9945-1, ANSI/IEEE Std 1003.1, 2004 Edition. -*/ - char * asctime_r(register const struct tm *timeptr, char *buf) { @@ -117,10 +115,6 @@ asctime_r(register const struct tm *timeptr, char *buf) } } -/* -** A la ISO/IEC 9945-1, ANSI/IEEE Std 1003.1, 2004 Edition. -*/ - char * asctime(register const struct tm *timeptr) { diff --git a/localtime.c b/localtime.c index b6b82bb..5b5a5b1 100644 --- a/localtime.c +++ b/localtime.c @@ -88,9 +88,8 @@ static const char gmt[] = "GMT"; /* ** The DST rules to use if TZ has no rules and we can't load TZDEFRULES. ** Default to US rules as of 2017-05-07. -** 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. +** POSIX does not specify the default DST rules; +** for historical reasons, US rules are a common default. */ #ifndef TZDEFRULESTRING #define TZDEFRULESTRING ",M3.2.0,M11.1.0" @@ -2211,7 +2210,7 @@ timeoff(struct tm *tmp, long offset) #ifdef STD_INSPIRED /* -** IEEE Std 1003.1-1988 (POSIX) legislates that 536457599 +** IEEE Std 1003.1 (POSIX) says that 536457599 ** shall correspond to "Wed Dec 31 23:59:59 UTC 1986", which ** is not the case if we are accounting for leap seconds. ** So, we provide the following conversion routines for use diff --git a/theory.html b/theory.html index b27b212..fc2102b 100644 --- a/theory.html +++ b/theory.html @@ -68,7 +68,7 @@ standard for <a href="https://en.wikipedia.org/wiki/Unix">UNIX</a>-like systems. As of this writing, the current edition of POSIX is: <a href="http://pubs.opengroup.org/onlinepubs/9699919799/"> The Open -Group Base Specifications Issue 7</a>, IEEE Std 1003.1-2008, 2016 +Group Base Specifications Issue 7</a>, IEEE Std 1003.1-2017, 2018 Edition. Because the database's scope encompasses real-world changes to civil timekeeping, its model for describing time is more complex than the -- 2.7.4

1 0

[PROPOSED] * europe: Adjust to kalendar.beda.cz correction.
by Paul Eggert April 15, 2018

April 15, 2018

--- europe | 9 ++------- 1 file changed, 2 insertions(+), 7 deletions(-) diff --git a/europe b/europe index 160be9f..6b97fd0 100644 --- a/europe +++ b/europe @@ -971,14 +971,9 @@ Zone Europe/Sofia 1:33:16 - LMT 1880 # Czech Republic / Czechia # -# From Paul Eggert (2018-04-14): -# The source for Czech data is: Kdy začíná a končí letní čas. +# From Paul Eggert (2018-04-15): +# The source for Czech data is: Kdy začíná a končí letní čas. 2018-04-15. # https://kalendar.beda.cz/kdy-zacina-a-konci-letni-cas -# with one correction, taken from: -# Sbírka zákonů a nařízení republiky Československé, částka 92/1946. -# http://ftp.aspi.cz/opispdf/1946/092-1946.pdf -# which says that the winter time (negative DST) starting 1946-12-01 -# was a switch from 03:00 to 02:00 (not from 02:00 to 01:00). # We know of no English-language name for historical Czech winter time; # abbreviate it as "GMT", as it happened to be GMT. # -- 2.14.3

1 0

start of 1946 winter time in "Kdy začíná a končí letní čas"
by Paul Eggert April 14, 2018

April 14, 2018

I recently proposed some tz database changes for Prague; see <https://en.wikipedia.org/wiki/Tz_database> and <https://mm.icann.org/pipermail/tz/2018-April/026415.html>. I used your web page <https://kalendar.beda.cz/kdy-zacina-a-konci-letni-cas> as the main source for these fixes; thank you! I noticed what appears to be a typographical error in your web page. It says: 1946-7 zimní čas 1. prosinec (2:00) 23. únor (2:00) However, the primary source <http://ftp.aspi.cz/opispdf/1946/092-1946.pdf> says: "§1. Počátek zimního času v roce 1946 se určuje na den 1. prosince 1946 o třetí hodiné ranní středoevropského času a provede se posunutím hodinových ručiček na druhou hodinu." Google Translate suggests this means the transition was December 1 at 03:00, not December 1 at 02:00. That is, the clock was 03:00 before the transition, and 02:00 afterwards. The attached patch contains a proposed fix to kalendar.beda.cz. I am CC:ing this to the time zone mailing list to give them a heads-up as to why I made this change in the tz database.

1 0

[PROPOSED 1/2] Czechs had negative DST in 1946/7
by Paul Eggert April 14, 2018

April 14, 2018

* NEWS: Document this. * europe (Czech): Adjust 1945 transition dates to match new source. (Europe/Prague): Likewise. Add negative DST in 1946/7. * tz-link.html: Link to kalendar.beda.cz. * ziguard.awk: Adjust to Czech changes. --- NEWS | 6 ++++++ europe | 24 +++++++++++++++++++++--- tz-link.html | 4 ++++ ziguard.awk | 10 ++++++++++ 4 files changed, 41 insertions(+), 3 deletions(-) diff --git a/NEWS b/NEWS index 17492b3..13652fc 100644 --- a/NEWS +++ b/NEWS @@ -29,6 +29,12 @@ Unreleased, experimental changes format; in rearguard and main format, the tm_isdst flag is still zero in winter and nonzero in summer. + In 1946/7 Czechoslovakia also observed negative DST in winter. + The full effect of this change is only in vanguard format; in + rearguard and main formats, it is modeled as plain GMT without + daylight saving. Also, the dates of some 1944/5 DST transitions + in Czechoslovakia have been changed. + Release 2018d - 2018-03-22 07:05:46 -0700 diff --git a/europe b/europe index 20eb4e8..5edb686 100644 --- a/europe +++ b/europe @@ -970,9 +970,21 @@ Zone Europe/Sofia 1:33:16 - LMT 1880 # Please see the 'asia' file for Asia/Nicosia. # Czech Republic / Czechia +# +# From Paul Eggert (2018-04-14): +# The source for Czech data is: Kdy začíná a končí letní čas. +# https://kalendar.beda.cz/kdy-zacina-a-konci-letni-cas +# with one correction, taken from: +# Sbírka zákonů a nařízení republiky Československé, částka 92/1946. +# http://ftp.aspi.cz/opispdf/1946/092-1946.pdf +# which says that the winter time (negative DST) starting 1946-12-01 +# was a switch from 03:00 to 02:00 (not from 02:00 to 01:00). +# We know of no English-language name for historical Czech winter time; +# abbreviate it as "GMT", as it happened to be GMT. +# # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S -Rule Czech 1945 only - Apr 8 2:00s 1:00 S -Rule Czech 1945 only - Nov 18 2:00s 0 - +Rule Czech 1945 only - Apr Mon>=1 2:00s 1:00 S +Rule Czech 1945 only - Oct 1 2:00s 0 - Rule Czech 1946 only - May 6 2:00s 1:00 S Rule Czech 1946 1949 - Oct Sun>=1 2:00s 0 - Rule Czech 1947 only - Apr 20 2:00s 1:00 S @@ -981,7 +993,13 @@ Rule Czech 1949 only - Apr 9 2:00s 1:00 S # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Prague 0:57:44 - LMT 1850 0:57:44 - PMT 1891 Oct # Prague Mean Time - 1:00 C-Eur CE%sT 1944 Sep 17 2:00s + 1:00 C-Eur CE%sT 1945 May 9 + 1:00 Czech CE%sT 1946 Dec 1 3:00 +# Vanguard section, for zic and other parsers that support negative DST. +# 1:00 -1:00 GMT 1947 Feb 23 2:00 +# Rearguard section, for parsers that do not support negative DST. + 0:00 - GMT 1947 Feb 23 2:00 +# End of rearguard section. 1:00 Czech CE%sT 1979 1:00 EU CE%sT # Use Europe/Prague also for Slovakia. diff --git a/tz-link.html b/tz-link.html index 6700c7f..13a824d 100644 --- a/tz-link.html +++ b/tz-link.html @@ -728,6 +728,10 @@ zones & daylight saving time</a>.</dd> <dd>The Hydrographic and Oceanographic Service of the Chilean Navy publishes a <a href="http://www.horaoficial.cl/historia_hora.html" hreflang="es">history of Chile's official time (in Spanish)</a>.</dd> +<dt>Czech Republic</dt> +<dd><a href="https://kalendar.beda.cz/kdy-zacina-a-konci-letni-cas" +hreflang="cs">When daylight saving time starts and ends (in Czech)</a> +summarizes and cites historical DST regulations.</dd> <dt>Germany</dt> <dd>The National Institute for Science and Technology maintains the <a href="https://www.ptb.de/cms/en/fachabteilungen/abt4/fb-44/ag-441/realisation-of-…">Realisation diff --git a/ziguard.awk b/ziguard.awk index 5bfaebb..7cdceab 100644 --- a/ziguard.awk +++ b/ziguard.awk @@ -28,6 +28,16 @@ outfile != "main.zi" { in_comment = /^#/ uncomment = comment_out = 0 + # If the line should differ due to Czechoslovakia using negative SAVE values, + # uncomment the desired version and comment out the undesired one. + if (zone == "Europe/Prague" && /1947 Feb 23/) { + if (($(in_comment + 2) != "-") == vanguard) { + uncomment = in_comment + } else { + comment_out = !in_comment + } + } + # If this line should differ due to Ireland using negative SAVE values, # uncomment the desired version and comment out the undesired one. Rule_Eire = /^#?Rule[\t ]+Eire[\t ]/ -- 2.7.4

1 1

[PROPOSED] * europe: Remove "exactly" from comment; it was not exactly right.
by Paul Eggert April 14, 2018

April 14, 2018

--- europe | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/europe b/europe index 3f092a4..20eb4e8 100644 --- a/europe +++ b/europe @@ -2016,7 +2016,7 @@ Rule Neth 1938 1939 - May 15 2:00s 1:00 S Rule Neth 1945 only - Apr 2 2:00s 1:00 S Rule Neth 1945 only - Sep 16 2:00s 0 - # -# Amsterdam Mean Time was +00:19:32.13 exactly, but the .13 is omitted +# Amsterdam Mean Time was +00:19:32.13, but the .13 is omitted # below because the current format requires GMTOFF to be an integer. # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Amsterdam 0:19:32 - LMT 1835 -- 2.14.3

1 0

[PROPOSED] Namibia was on DST until 2017-10-24
by Paul Eggert April 9, 2018

April 9, 2018

While we're at it, use negative DST offsets in vanguard format, since Namibia (like Ireland) used negative DST in winter. * NEWS, africa (Namibia, Africa/Windhoek), ziguard.awk: Implement this. --- NEWS | 10 ++++++++++ africa | 19 +++++++++++++++++-- ziguard.awk | 28 +++++++++++++++++++++++++--- 3 files changed, 52 insertions(+), 5 deletions(-) diff --git a/NEWS b/NEWS index 0297fd8..3bbb829 100644 --- a/NEWS +++ b/NEWS @@ -1,5 +1,15 @@ News for the tz database +Unreleased, experimental changes + + Changes to past time stamps + + For Namibia's transition from +01/+02 to plain +02, change the + transition date from 2017-09-03 at 03:00 to 2017-10-24 at 00:00. + This does not affect UTC offsets, only whether a DST regime was + in place. + + Release 2018d - 2018-03-22 07:05:46 -0700 Briefly: diff --git a/africa b/africa index 2f7217a..e564906 100644 --- a/africa +++ b/africa @@ -992,9 +992,20 @@ Link Africa/Maputo Africa/Lusaka # Zambia # the same time they would normally start DST, the first Sunday in September: # https://www.timeanddate.com/news/time/namibia-new-time-zone.html +# From Paul Eggert (2017-04-05): +# The official date of the time zone change was 2017-10-24. See: +# http://www.lac.org.na/laws/annoSTAT/Namibian%20Time%20Act%209%20of%202017.p… + # RULE NAME FROM TO TYPE IN ON AT SAVE LETTER/S +# The following has standard time in summer and negative daylight +# saving time in winter. It is for when negative SAVE values are used. +# For more about this, see the comments in 'europe' for Rule Eire. +#Rule Namibia 1994 only - Mar 21 0:00 -1:00 +01 +#Rule Namibia 1994 2017 - Sep Sun>=1 2:00 0 CAT +#Rule Namibia 1995 2017 - Apr Sun>=1 2:00 -1:00 +01 +# The following is for when SAVE values are always nonnegative. Rule Namibia 1994 only - Mar 21 0:00 0 - -Rule Namibia 1994 2016 - Sep Sun>=1 2:00 1:00 S +Rule Namibia 1994 2017 - Sep Sun>=1 2:00 1:00 S Rule Namibia 1995 2017 - Apr Sun>=1 2:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Africa/Windhoek 1:08:24 - LMT 1892 Feb 8 @@ -1003,7 +1014,11 @@ Zone Africa/Windhoek 1:08:24 - LMT 1892 Feb 8 2:00 1:00 SAST 1943 Mar 21 2:00 2:00 - SAST 1990 Mar 21 # independence 2:00 - CAT 1994 Mar 21 0:00 - 1:00 Namibia WA%sT 2017 Sep 3 2:00 +# The next line is for when negative SAVE values are used. +# 2:00 Namibia %s 2017 Oct 24 +# The next line is for when SAVE values are always nonnegative. + 1:00 Namibia WA%sT 2017 Oct 24 +# End of daylight saving. 2:00 - CAT # Niger diff --git a/ziguard.awk b/ziguard.awk index 6da3691..710b630 100644 --- a/ziguard.awk +++ b/ziguard.awk @@ -26,6 +26,7 @@ BEGIN { outfile != "main.zi" { in_comment = /^#/ + uncomment = comment_out = 0 # If this line should differ due to Ireland using negative SAVE values, # uncomment the desired version and comment out the undesired one. @@ -37,11 +38,32 @@ outfile != "main.zi" { if ((Rule_Eire \ || (Zone_Dublin_post_1968 && $(in_comment + 3) == "IST/GMT")) \ == vanguard) { - sub(/^#/, "") - } else if (/^[^#]/) { - sub(/^/, "#") + uncomment = in_comment + } else { + comment_out = !in_comment } } + + # If this line should differ due to Namibia using negative SAVE values, + # uncomment the desired version and comment out the undesired one. + Rule_Namibia = /^#?Rule[\t ]+Namibia[\t ]/ + Zone_using_Namibia_rule \ + = (zone == "Africa/Windhoek" && /^#?[\t ]+[12]:00[\t ]/ \ + && $(in_comment + 2) == "Namibia") + if (Rule_Namibia || Zone_using_Namibia_rule) { + if (in_comment == vanguard) { + uncomment = in_comment + } else { + comment_out = !in_comment + } + } + + if (uncomment) { + sub(/^#/, "") + } + if (comment_out) { + sub(/^/, "#") + } } # If a Link line is followed by a Zone line for the same data, comment -- 2.14.3

5 10

[PATCH] * Makefile, strftime.c, zic.8: alternate -> alternative
by Paul Eggert April 9, 2018

April 9, 2018

--- Makefile | 4 ++-- strftime.c | 2 +- zic.8 | 8 ++++---- 3 files changed, 7 insertions(+), 7 deletions(-) diff --git a/Makefile b/Makefile index 23599ce..2365d7c 100644 --- a/Makefile +++ b/Makefile @@ -21,7 +21,7 @@ DATAFORM= main # Change the line below for your time zone (after finding the zone you want in # the time zone files, or adding it to a time zone file). -# Alternately, if you discover you've got the wrong time zone, you can just +# Alternatively, if you discover you've got the wrong time zone, you can just # zic -l rightzone # to correct things. # Use the command @@ -38,7 +38,7 @@ LOCALTIME= GMT # template file are used to determine "spring forward" and "fall back" days and # times; the environment variable itself specifies UT offsets of standard and # daylight saving time. -# Alternately, if you discover you've got the wrong time zone, you can just +# Alternatively, if you discover you've got the wrong time zone, you can just # zic -p rightzone # to correct things. # Use the command diff --git a/strftime.c b/strftime.c index 6da3fb9..e855890 100644 --- a/strftime.c +++ b/strftime.c @@ -224,7 +224,7 @@ label: ** %Ec %EC %Ex %EX %Ey %EY ** %Od %oe %OH %OI %Om %OM ** %OS %Ou %OU %OV %Ow %OW %Oy - ** are supposed to provide alternate + ** are supposed to provide alternative ** representations. */ goto label; diff --git a/zic.8 b/zic.8 index 4251868..97644ac 100644 --- a/zic.8 +++ b/zic.8 @@ -372,7 +372,7 @@ begin the field with a minus sign if time must be subtracted from UT. .TP .B RULES The name of the rules that apply in the time zone or, -alternately, an amount of time to add to local standard time. +alternatively, an amount of time to add to local standard time. If this field is .B \*- then standard time always applies in the time zone. @@ -386,7 +386,7 @@ The pair of characters is used to show where the .q "variable part" of the time zone abbreviation goes. -Alternately, a format can use the pair of characters +Alternatively, a format can use the pair of characters .B %z to stand for the UT offset in the form .RI \(+- hh , @@ -399,7 +399,7 @@ using the shortest form that does not lose information, where and .I ss are the hours, minutes, and seconds east (+) or west (\(mi) of UT. -Alternately, +Alternatively, a slash (/) separates standard and daylight abbreviations. To conform to POSIX, a time zone abbreviation should contain only @@ -455,7 +455,7 @@ field should appear as the field in some zone line. The .B LINK-NAME -field is used as an alternate name for that zone; +field is used as an alternative name for that zone; it has the same syntax as a zone line's .B NAME field. -- 2.7.4

1 0

[PROPOSED 1/2] * .gitignore: Ignore .patch and .tzs files.
by Paul Eggert April 8, 2018

April 8, 2018

--- .gitignore | 2 ++ 1 file changed, 2 insertions(+) diff --git a/.gitignore b/.gitignore index bc6fc25..1e62d11 100644 --- a/.gitignore +++ b/.gitignore @@ -3,8 +3,10 @@ *.a *.asc *.o +*.patch *.tar.* *.txt +*.tzs *.zi *~ ChangeLog -- 2.14.3

1 1

[PROPOSED] Mention Zone names with two slashes
by Paul Eggert April 6, 2018

April 6, 2018

* theory.html: Mention that some zone names have two slashes, e.g., America/Indiana/Petersburg. Use past tense for Mars Pathfinder. Avoid contractions. Use full zone names in examples and omit no-longer-needed quotes. Add URLs and fix typos. --- theory.html | 105 +++++++++++++++++++++++++++++++++++------------------------- 1 file changed, 61 insertions(+), 44 deletions(-) diff --git a/theory.html b/theory.html index 596b32c..ba57653 100644 --- a/theory.html +++ b/theory.html @@ -53,7 +53,7 @@ However, the database is not designed for and does not suffice for applications requiring accurate handling of all past times everywhere, as it would take far too much effort and guesswork to record all details of pre-1970 civil timekeeping. -Athough some information outside the scope of the database is +Although some information outside the scope of the database is collected in a file <code>backzone</code> that is distributed along with the database proper, this file is less reliable and does not necessarily follow database guidelines. @@ -79,7 +79,7 @@ flip back and forth between two alternatives, and the rules themselves can change at times. Whether and when a <code><abbr>tz</abbr></code> region changes its clock, and even the region's notional base offset from UTC, are variable. -It doesn't even really make sense to talk about a region's +It does not always make sense to talk about a region's "base offset", since it is not necessarily a single number. </p> @@ -92,8 +92,8 @@ Each <code><abbr>tz</abbr></code> region has a unique name that corresponds to a set of time zone rules. Inexperienced users are not expected to select these names unaided. Distributors should provide documentation and/or a simple selection -interface that explains the names; for one example, see the 'tzselect' -program in the <code><abbr>tz</abbr></code> code. +interface that explains the names; for one example, see the +<code>tzselect</code> program in the <code><abbr>tz</abbr></code> code. The <a href="http://cldr.unicode.org/">Unicode Common Locale Data Repository</a> contains data that may be useful for other selection interfaces. @@ -137,6 +137,9 @@ region. North and South America share the same area, '<code>America</code>'. Typical names are '<code>Africa/Cairo</code>', '<code>America/New_York</code>', and '<code>Pacific/Honolulu</code>'. +Some names are further qualified to help avoid confusion; for example, +'<code>America/Indiana/Petersburg</code>' distinguishes Petersburg, +Indiana from other Petersburgs in America. </p> <p> @@ -159,7 +162,8 @@ in decreasing order of importance: <code>TZ</code> strings</a>. A file name component must not exceed 14 characters or start with '<code>-</code>'. - E.g., prefer '<code>Brunei</code>' to '<code>Bandar_Seri_Begawan</code>'. + E.g., prefer <code>Asia/Brunei</code> to + <code>Asia/Bandar_Seri_Begawan</code>. Exceptions: see the discussion of legacy names below. </li> <li> @@ -177,8 +181,8 @@ in decreasing order of importance: name <var>AB</var> (ignoring case), then <var>B</var> must not start with '<code>/</code>', as a regular file cannot have the same name as a directory in POSIX. - For example, '<code>America/New_York</code>' precludes - '<code>America/New_York/Bronx</code>'. + For example, <code>America/New_York</code> precludes + <code>America/New_York/Bronx</code>. </li> <li> Uninhabited regions like the North Pole and Bouvet Island @@ -193,50 +197,56 @@ in decreasing order of importance: </li> <li> If all the clocks in a region have agreed since 1970, - don't bother to include more than one location + do not bother to include more than one location even if subregions' clocks disagreed before 1970. Otherwise these tables would become annoyingly large. </li> <li> If a name is ambiguous, use a less ambiguous alternative; e.g., many cities are named San José and Georgetown, so - prefer '<code>Costa_Rica</code>' to '<code>San_Jose</code>' and - '<code>Guyana</code>' to '<code>Georgetown</code>'. + prefer <code>America/Costa_Rica</code> to + <code>America/San_Jose</code> and <code>America/Guyana</code> + to <code>America/Georgetown</code>. </li> <li> Keep locations compact. Use cities or small islands, not countries or regions, so that any future changes do not split individual locations into different <code><abbr>tz</abbr></code> regions. - E.g., prefer '<code>Paris</code>' to '<code>France</code>', since + E.g., prefer <code>Europe/Paris</code> to <code>Europe/France</code>, + since <a href="https://en.wikipedia.org/wiki/Time_in_France#History">France has had multiple time zones</a>. </li> <li> - Use mainstream English spelling, e.g., prefer '<code>Rome</code>' - to '<code>Roma</code>', and prefer '<code>Athens</code>' to the - Greek '<code>Αθήνα</code>' or the Romanized '<code>Athína</code>'. + Use mainstream English spelling, e.g., prefer + <code>Europe/Rome</code> to <code>Europe/Roma</code>, and + prefer <code>Europe/Athens</code> to the Greek + <code>Europe/Αθήνα</code> or the Romanized + <code>Europe/Athína</code>. The POSIX file name restrictions encourage this guideline. </li> <li> Use the most populous among locations in a region, - e.g., prefer '<code>Shanghai</code>' to - '<code>Beijing</code>'. + e.g., prefer <code>Asia/Shanghai</code> to + <code>Asia/Beijing</code>. Among locations with similar populations, pick the best-known - location, e.g., prefer '<code>Rome</code>' to - '<code>Milan</code>'. + location, e.g., prefer <code>Europe/Rome</code> to + <code>Europe/Milan</code>. </li> <li> - Use the singular form, e.g., prefer '<code>Canary</code>' to - '<code>Canaries</code>'. + Use the singular form, e.g., prefer <code>Atlantic/Canary</code> to + <code>Atlantic/Canaries</code>. </li> <li> Omit common suffixes like '<code>_Islands</code>' and '<code>_City</code>', unless that would lead to ambiguity. - E.g., prefer '<code>Cayman</code>' to - '<code>Cayman_Islands</code>' and '<code>Guatemala</code>' to - '<code>Guatemala_City</code>', but prefer - '<code>Mexico_City</code>' to '<code>Mexico</code>' + E.g., prefer <code>America/Cayman</code> to + <code>America/Cayman_Islands</code> and + <code>America/Guatemala</code> to + <code>America/Guatemala_City</code>, but prefer + <code>America/Mexico_City</code> to + <code>America/Mexico</code> because <a href="https://en.wikipedia.org/wiki/Time_in_Mexico">the country of Mexico has several time zones</a>. </li> @@ -245,13 +255,14 @@ in decreasing order of importance: </li> <li> Omit '<code>.</code>' from abbreviations in names. - E.g., prefer '<code>St_Helena</code>' to '<code>St._Helena</code>'. + E.g., prefer <code>Atlantic/St_Helena</code> to + <code>Atlantiic/St._Helena</code>. </li> <li> Do not change established names if they only marginally violate the above guidelines. - For example, don't change the existing name '<code>Rome</code>' to - '<code>Milan</code>' merely because Milan's population has grown + For example, do not change the existing name <code>Europe/Rome</code> to + <code>Europe/Milan</code> merely because Milan's population has grown to be somewhat greater than Rome's. </li> <li> @@ -318,8 +329,10 @@ in decreasing order of importance: Use three to six characters that are ASCII alphanumerics or '<code>+</code>' or '<code>-</code>'. Previous editions of this database also used characters like - '<code> </code>' and '<code>?</code>', but these characters have a - special meaning to the shell and cause commands like + space and '<code>?</code>', but these characters have a + special meaning to the + <a href="https://en.wikipedia.org/wiki/Unix_shell">UNIX shell</a> + and cause commands like '<code><a href="http://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#set">set</a> `<a href="http://pubs.opengroup.org/onlinepubs/9699919799/utilities/date.html">date</a>`</code>' to have unexpected effects. @@ -688,7 +701,7 @@ href="https://www.dissentmagazine.org/blog/booked-a-global-history-of-time-vanes subsecond accuracy is needed. </li> <li> - Civil time was not based on atomic time before 1972, and we don't + Civil time was not based on atomic time before 1972, and we do not know the history of <a href="https://en.wikipedia.org/wiki/Earth's_rotation">earth's rotation</a> accurately enough to map <a @@ -720,7 +733,7 @@ href="https://www.dissentmagazine.org/blog/booked-a-global-history-of-time-vanes Ideally it would contain information about when data entries are incomplete or dicey. Partial temporal knowledge is a field of active research, though, - and it's not clear how to apply it here. + and it is not clear how to apply it here. </li> </ul> @@ -764,7 +777,7 @@ an older <code>zic</code>. Unfortunately, the POSIX <code>TZ</code> string takes a form that is hard to describe and is error-prone in practice. - Also, POSIX <code>TZ</code> strings can't deal with daylight + Also, POSIX <code>TZ</code> strings cannot deal with daylight saving time rules not based on the Gregorian calendar (as in Iran), or with situations where more than two time zone abbreviations or <abbr>UT</abbr> offsets are used in an area. @@ -874,7 +887,7 @@ an older <code>zic</code>. need access to multiple time zone rulesets. </li> <li> - In POSIX, there's no tamper-proof way for a process to learn the + In POSIX, there is no tamper-proof way for a process to learn the system's best idea of local wall clock. (This is important for applications that an administrator wants used only at certain times – without regard to whether the @@ -973,14 +986,16 @@ an older <code>zic</code>. by subsequent calls to <code>localtime</code>. Source code for portable applications that "must" run on local wall clock time should call <code>tzsetwall</code>; - if such code is moved to "old" systems that don't - provide <code>tzsetwall</code>, you won't be able to generate an + if such code is moved to "old" systems that do not + provide <code>tzsetwall</code>, you will not be able to generate an executable program. (These functions also arrange for local wall clock time to be used if <code>tzset</code> is called – directly or - indirectly – and there's no <code>TZ</code> environment + indirectly – and there is no <code>TZ</code> environment variable; portable applications should not, however, rely on this - behavior since it's not the way SVR2 systems behave.) + behavior since it is not the way <a + href="https://en.wikipedia.org/wiki/UNIX_System_V#SVR2"><abbr>SVR2</abbr></a> + systems behave.) </li> <li> Negative <code>time_t</code> values are supported, on systems @@ -1040,7 +1055,7 @@ The vestigial <abbr>API</abbr>s are: <li> The <a href="https://en.wikipedia.org/wiki/Version_7_Unix">7th Edition UNIX</a> <code>timezone</code> function is not present in this - package; it's impossible to reliably map <code>timezone</code>'s + package; it is impossible to reliably map <code>timezone</code>'s arguments (a "minutes west of <abbr>GMT</abbr>" value and a "daylight saving time in effect" flag) to a time zone abbreviation, and we refuse to guess. @@ -1052,7 +1067,9 @@ The vestigial <abbr>API</abbr>s are: zone abbreviation to use. </li> <li> - The <abbr>4.2BSD</abbr> <code>gettimeofday</code> function is not + The <a + href="https://en.wikipedia.org/wiki/History_of_the_Berkeley_Software_Distribution…"><abbr>4.2BSD</abbr></a> + <code>gettimeofday</code> function is not used in this package. This formerly let users obtain the current <abbr>UTC</abbr> offset and <abbr>DST</abbr> flag, but this functionality was removed in @@ -1061,7 +1078,7 @@ The vestigial <abbr>API</abbr>s are: <li> In <abbr>SVR2</abbr>, time conversion fails for near-minimum or near-maximum <code>time_t</code> values when doing conversions - for places that don't use <abbr>UT</abbr>. + for places that do not use <abbr>UT</abbr>. This package takes care to do these conversions correctly. A comment in the source code tells how to get compatibly wrong results. @@ -1170,11 +1187,11 @@ They sometimes disagree. <p> Some people's work schedules use <a href="https://en.wikipedia.org/wiki/Timekeeping on Mars">Mars time</a>. -Jet Propulsion Laboratory (JPL) coordinators have kept Mars time on -and off at least since 1997 for the +Jet Propulsion Laboratory (JPL) coordinators kept Mars time on +and off during the <a href="https://en.wikipedia.org/wiki/Mars_Pathfinder#End_of_mission">Mars Pathfinder</a> mission. -Some of their family members have also adapted to Mars time. +Some of their family members also adapted to Mars time. Dozens of special Mars watches were built for JPL workers who kept Mars time during the Mars Exploration Rovers mission (2004). These timepieces look like normal Seikos and Citizens but use Mars @@ -1262,7 +1279,7 @@ Sources for time on other planets: Jia-Rui Chong, "<a href="http://articles.latimes.com/2004/jan/14/science/sci-marstime14">Workdays Fit for a Martian</a>", <cite>Los Angeles Times</cite> - (2004-01-14), pp A1, A20-A21. + (2004-01-14), pp A1, A20–A21. </li> <li> Tom Chmielewski, -- 2.14.3

2 2

Namibia Time Zone
by Mark Plaatje April 4, 2018

April 4, 2018

Good Day Kindly update your database to reflect that no Daylight Savings Time will be effected in 2018. https://www.timeanddate.com/time/change/namibia/windhoek?year=2018 https://www.namibian.com.na/65921/read/No-time-change-on-Sunday http://www.xinhuanet.com/english/2018-04/03/c_137086167.htm https://www.namibian.com.na/65942/read/Confusion-over-time-change Regards, Mark Plaatje Manager : Fraud Mobile Telecommunications Ltd Tel: +264818882842 Fax: E-mail: MPlaatje(a)mtc.com.na <mailto:MPlaatje@mtc.com.na>http://www.mtc.com.na [X]<http://www.mtc.com.na/> ________________________________ This e-mail message and any attachment are subject to the following terms and conditions http://www.mtc.com.na/legal/disclaimer

3 2

[PROPOSED] New edition of Calendrical Calculations
by Paul Eggert April 3, 2018

April 3, 2018

* theory.html (Calendrical issues): Update Reingold & Dershowitz citation to 4th edition. --- theory.html | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/theory.html b/theory.html index 4d8726d..596b32c 100644 --- a/theory.html +++ b/theory.html @@ -1155,10 +1155,10 @@ based on guesswork and these guesses may be corrected or improved. Calendrical issues are a bit out of scope for a time zone database, but they indicate the sort of problems that we would run into if we extended the time zone database further into the past. -An excellent resource in this area is Nachum Dershowitz and Edward M. -Reingold, <cite><a -href="https://www.cs.tau.ac.il/~nachum/calendar-book/third-edition/">Calendrical -Calculations: Third Edition</a></cite>, Cambridge University Press (2008). +An excellent resource in this area is Edward M. Reingold +and Nachum Dershowitz, <cite><a +href="https://www.cambridge.org/fr/academic/subjects/computer-science/computing-g…">Calendrical +Calculations: The Ultimate Edition</a></cite>, Cambridge University Press (2018). Other information and sources are given in the file '<code>calendars</code>' in the <code><abbr>tz</abbr></code> distribution. They sometimes disagree. -- 2.7.4

4 6

How to force zic output to TZIF?
by Johan Kohler April 3, 2018

April 3, 2018

Hi, I have a tz client that expects the tzdata in format TZIF (that's version \nul). It has become necessary to update the tzdata but it is not feasible to update the client. Is it possible with the current 2018d release to generate output in TZIF format (as opposed to TZIF2 or TZIF3)? If so, what needs to be modified? If not, what is the suggested approach? Thanks, Johan

2 2

Western Australia time zone January 1, 2019
by Paul Eggert April 2, 2018

April 2, 2018

Today the Guardian Express of Perth reported that the government of Western Australia has decided to advance the clocks permanently from +0800 to +0900 on January 1, 2019. Presumably the time will still be called Australian Western Standard Time (AWST), as it will still differ by 30 minutes from ACST (+0930). For now, I suppose we should guess that Australia/Eucla will simultaneously switch from +0845 to +0915 so as to stay halfway between AWST and ACST. Proposed patch attached. The article concludes that the government has made several concessions to residents opposed to the measure, and lists some of them. One is that "people over the age of 60 concerned about colour bleaching from drapes and blinds can apply in writing to have the extra hour of sunshine removed from their area." See: Daylight saving coming to WA in 2019. Guardian Express. 2018-04-01. https://www.communitynews.com.au/guardian-express/news/exclusive-daylight-s…

5 5

US marks centennial of daylight saving
by Paul Eggert March 30, 2018

March 30, 2018

Tonight marks 100 years since the introduction of daylight saving time as United States federal law. On March 30/31, 1918, New York City held a New-Year's-style celebration for the public in Madison Square Garden, along with a reception at the Aldine Club for the elite. The guest of honor was Marcus M. Marks, president of the Daylight Saving Association, and uncle of the now-more-famous Johnny Marks (who was later to write "Rudolph the Red-Nosed Reindeer"). Among other things, Marks got to push the button that advanced the 8-meter clocks atop what is now known as the Met Life Tower. See: Change in time begins tomorrow. Government's new daylight regulation goes into effect at 2 A. M. No confusion expected. New York Times. 1918-03-30. https://www.nytimes.com/packages/html/mobile/change-in-time.pdf

1 0

[PROPOSED] * tz-link.html: Add worldclock.com.
by Paul Eggert March 26, 2018

March 26, 2018

--- tz-link.html | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/tz-link.html b/tz-link.html index 7221777..6700c7f 100644 --- a/tz-link.html +++ b/tz-link.html @@ -239,8 +239,9 @@ These are listed roughly in ascending order of complexity and fanciness. <ul> <li><a href="https://time.is">Time.is</a> shows locations' time and zones.</li> -<li><a href="https://www.timejones.com">TimeJones.com</a> -and <a href="https://timezoneconverterapp.com">Time Zone Converter</a> +<li><a href="https://www.timejones.com">TimeJones.com</a>, +<a href="https://timezoneconverterapp.com">Time Zone Converter</a> and +<a href="http://worldclock.com">The World Clock</a> are time zone converters.</li> <li><a href="http://twiki.org/cgi-bin/xtra/tzdatepick.html">Date and Time Gateway</a> -- 2.7.4

1 0

Re: [tz] [PATCH1/1] Propose new zone for Crozet Islands
by REMI ACIEN March 25, 2018

March 25, 2018

Provenance : Courrier<https://go.microsoft.com/fwlink/?LinkId=550986> pour Windows 10 A new zone for Crozet Islands . Why not .

4 5

[PROPOSED] Spelling fixes
by Paul Eggert March 23, 2018

March 23, 2018

--- NEWS | 2 +- asia | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/NEWS b/NEWS index 8afe3a4..0297fd8 100644 --- a/NEWS +++ b/NEWS @@ -39,7 +39,7 @@ Release 2018d - 2018-03-22 07:05:46 -0700 Enderbury and Kiritimati skipped New Year's Eve 1994, not New Year's Day 1995. (Thanks to Kerry Shetline.) - Fix the 1912-01-01 transition for Portugual and its colonies. + Fix the 1912-01-01 transition for Portugal and its colonies. This transition was at 00:00 according to the new UT offset, not according to the old one. Also assume that Cape Verde switched on the same date as the rest, not in 1907. This affects diff --git a/asia b/asia index 998a7d4..7a6294a 100644 --- a/asia +++ b/asia @@ -2658,7 +2658,7 @@ Zone Asia/Karachi 4:28:12 - LMT 1907 # From Sharef Mustafa (2018-03-16): # Palestine summer time will start on Mar 24th 2018 by advancing the # clock by 60 minutes as per Palestinian cabinet decision published on -# the offical website, though the decree did not specify the exact +# the official website, though the decree did not specify the exact # time of the time shift. # http://www.palestinecabinet.gov.ps/Website/AR/NDecrees/ViewFile.ashx?ID=e7a… # -- 2.14.3

1 0

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

March 23, 2018

The 2018d 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: Palestine starts DST a week earlier in 2018. Add support for vanguard and rearguard data consumers. Add subsecond precision to source data format, though not to data. Changes to future time stamps In 2018, Palestine starts DST on March 24, not March 31. Adjust future predictions accordingly. (Thanks to Sharef Mustafa.) Changes to past and future time stamps Casey Station in Antarctica changed from +11 to +08 on 2018-03-11 at 04:00. (Thanks to Steffen Thorsen.) Changes to past time stamps Historical transitions for Uruguay, represented by America/Montevideo, have been updated per official legal documents, replacing previous data mainly originating from the inventions of Shanks & Pottenger. This has resulted in adjustments ranging from 30 to 90 minutes in either direction over at least two dozen distinct periods ranging from one day to several years in length. A mere handful of pre-1991 transitions are unaffected; data since then has come from more reliable contemporaneous reporting. These changes affect various timestamps in 1920-1923, 1936, 1939, 1942-1943, 1959, 1966-1970, 1972, 1974-1980, and 1988-1990. Additionally, Uruguay's pre-standard-time UT offset has been adjusted westward by 7 seconds, from UT-03:44:44 to UT-03:44:51, to match the location of the Observatory of the National Meteorological Institute in Montevideo. (Thanks to Jeremie Bonjour, Tim Parenti, and Michael Deckers.) Enderbury and Kiritimati skipped New Year's Eve 1994, not New Year's Day 1995. (Thanks to Kerry Shetline.) Fix the 1912-01-01 transition for Portugual and its colonies. This transition was at 00:00 according to the new UT offset, not according to the old one. Also assume that Cape Verde switched on the same date as the rest, not in 1907. This affects Africa/Bissau, Africa/Sao_Tome, Asia/Macau, Atlantic/Azores, Atlantic/Cape_Verde, Atlantic/Madeira, and Europe/Lisbon. (Thanks to Michael Deckers.) Fix an off-by-1 error for pre-1913 timestamps in Jamaica and in Turks & Caicos. Changes to past time zone abbreviations MMT took effect in Uruguay from 1908-06-10, not 1898-06-28. There is no clock change associated with the transition. Changes to build procedure The new DATAFORM macro in the Makefile lets the installer choose among three source data formats. The idea is to lessen downstream disruption when data formats are improved. * DATAFORM=vanguard installs from the latest, bleeding-edge format. DATAFORM=main (the default) installs from the format used in the 'africa' etc. files. DATAFORM=rearguard installs from a trailing-edge format. Eventually, elements of today's vanguard format should move to the main format, and similarly the main format's features should eventually move to the rearguard format. * In the current version, the main and rearguard formats are identical and match that of 2018c, so this change does not affect default behavior. The vanguard format currently contains one feature not in the main format: negative SAVE values. This improves support for Ireland, which uses Irish Standard Time (IST, UTC+01) in summer and GMT (UTC) in winter. tzcode has supported negative SAVE values for decades, and this feature should move to the main format soon. However, it will not move to the rearguard format for quite some time because some downstream parsers do not support it. * The build procedure constructs three files vanguard.zi, main.zi, and rearguard.zi, one for each format. The files represent the same data as closely as the formats allow. These three files are intended for downstream data consumers and are not installed. Zoneinfo parsers that do not support negative SAVE values should start using rearguard.zi, so that they will be unaffected when the negative-DST feature moves from vanguard to main. Bleeding-edge Zoneinfo parsers that support the new features already can use vanguard.zi; in this respect, current tzcode is bleeding-edge. The Makefile should now be safe for parallelized builds, and 'make -j to2050new.tzs' is now much faster on a multiprocessor host with GNU Make. When built with -DSUPPRESS_TZDIR, the tzcode library no longer prepends TZDIR/ to file names that do not begin with '/'. This is not recommended for general use, due to its security implications. (From a suggestion by Manuela Friedrich.) Changes to code zic now accepts subsecond precision in expressions like 00:19:32.13, which is approximately the legal time of the Netherlands from 1835 to 1937. However, because it is questionable whether the few recorded uses of non-integer offsets had subsecond precision in practice, there are no plans for tzdata to use this feature. (Thanks to Steve Allen for pointing out the limitations of historical data in this area.) The code is a bit more portable to MS-Windows. Installers can compile with -DRESERVE_STD_EXT_IDS on MS-Windows platforms that reserve identifiers like 'localtime'. (Thanks to Manuela Friedrich). Changes to documentation and commentary theory.html now outlines tzdb's extensions to POSIX's model for civil time, and has a section "POSIX features no longer needed" that lists POSIX API components that are now vestigial. (From suggestions by Steve Summit.) It also better distinguishes time zones from tz regions. (From a suggestion by Guy Harris.) Commentary is now more consistent about using the phrase "daylight saving time", to match the C name tm_isdst. Daylight saving time need not occur in summer, and need not have a positive offset from standard time. Commentary about historical transitions in Uruguay has been expanded with links to many relevant legal documents. (Thanks to Tim Parenti.) Commentary now uses some non-ASCII characters with Unicode value less than U+0100, as they can be useful and should work even with older editors such as XEmacs. Here are links to the release files: https://www.iana.org/time-zones/repository/releases/tzcode2018d.tar.gz https://www.iana.org/time-zones/repository/releases/tzdata2018d.tar.gz https://www.iana.org/time-zones/repository/releases/tzdb-2018d.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 bd850bce5d292caaa5eba2c2088f6d4ad8024647 dated 2018-03-22 07:05:46 -0700 and tagged '2018d' in the development GitHub repository at <https://github.com/eggert/tz>. Here are the SHA-512 checksums for the release files: e79a95e235cd384247e4112d5154f30eb7b40f28dab4872ed9153e45bf56569949d0845bc1b9ad24b7a5f9609bdadfc892959dbf0d540dbca79b18398dc4f930 tzcode2018d.tar.gz ee961aedc34e134172523a29fb8a9358f42649d06ffcd2d8a6ad86eeb174a80af5bfc4637e9e52ecdc51fa3d01afef9fff660a69ed72904ff747a59b5634830b tzdata2018d.tar.gz 12c839846c147b83ace915e399fe447f93e83b500327fb4549b6039615f548d7167594168b5c4779ee1f33d7a1b8c2e294aa13cd35823d778617065ad9ad8ea5 tzdb-2018d.tar.lz Here are the GPG checksums for the release files: -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAABAgAGBQJas7pNAAoJEO2X6Q5iqn40dn8P+gI1f6sWKcA8iuDkRWundwBk Y92iYPChJDbgUSiWw3o+qyFmVUz0P1PZkB3rCTFhtyY8u6zCiO4+6xADyS+le3II iwwIg2yCqPxBXDXYkcFvSrXDuOo1hG009L1k9nKmv6RvO7lvr/o0K/pRQTWKiV2w jS9gPZeZ/ggTdcyaD9tzFNwDe0nCg54rwFs3Gy+YK2+8fNhLmYJCp3WJydza9zgU pBMMP868h1ZY9uWEZcWX3mstyKD4egFRfyHMj4XPVrnGwpMT5u7groiq2TZv/MXV A/HDxa4jU+El6RW0TwAVnGEwUSJ3L3I7B6/Pbf3jf+VCTYkw67cX/WrtSNop1E03 ujPZVqYr5N8HLu/VO/R2R+OccvMZ1X/URehA4068w/+ESG8X8AbRVBYGavpFmnUv uHOeOFgzcJUQqFU1fqAEdhlrYqqbnsRFJN8QX1QWwQs5fUAzNSAkAB+kTEVCAvhK 1xaxlNaZqoWqT0bYvD2TL+VLkPNHvu8RMpa/rhmjE23AWfYuSJsAABNMBpB5t6ux SbBOBeJ+a5a1rZwya0hxeX6A3BCBPXKBjnt8MjBnV1s8Ns4Ng7jQ5ZqOXtlSo4ER fYHbVQITXnE+DbuM1zF6RY1dwmCLvkxpdM5lifgiYCdcDzttsifDdrq5WM+pJsz5 3yTFJFsk6et2ekpHRugZ =MMy8 -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAABAgAGBQJas7pNAAoJEO2X6Q5iqn40BqwP/A8PU9mzxssBdQirWsuGhN3E +3hk6i7UFLrCHixbpN03y7r8ujkhRvkjLSrA2tcrYEK9t8NLkhQIrnmlVjEOQEcz +qiZWJV55kd2dhk2EE+pc8xXuqRsnId4r/xCF+D2wxl6IZpMEFelRCRiCGgszhDS FSv3UjlnpBv3uB5UgKdOFJKYcTvfOZ5jmpt1O6Ma9YNxqlc2+s8hUBR3VEtzancU +AyCoL/sUrijfGOZPSznhGJJ3lC5LkjkWqC0BYB5EI3YeClVtGWoZlD64jShJhWT pe3CAimaEibz1ty1tGz4Agdd0vQErvyCPQY6wy1pRYPW5wb++JomMVub7Uh7w/6o pvrkVaVqeiWeENoI6NRnmC+ANSaz6/lF61HM36VZ1XaCgmeCDaLHn31WKHRPctse r26++PyCIJwllaTNfGynjkAKUeBJJwwR8a/sjPeqEfEgoDKV1EpQVCBbPna3hmTq 8nzt11WsTNG+aocYr3hevSYiyxEWOLp5O9UaiTtVDc91Mhk2U9E9Fa7Zva35ZhjJ oRPS+AU5GFfWzgiW8XOLURqvwRNqUUudNaXy2wVuzwROdmboyewzB//MBavkI+r+ raI+coG2ZJoPcQmuRCUcjs1+JnNBL3sZT68/jTy2w0LURfUP9V+dUuJgjtRbMCtb Myzq3RCYNI/x3EjU/xcb =ibli -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAABAgAGBQJas7pOAAoJEO2X6Q5iqn40ursP/02PBDqd4eb8qrKrjScYt+I4 wnXMcjy9AmsfhPq1k1x6ZUI5qIbidrMD9S9m4NwKBGyvGxxcneWWJ5Yoln+K95YJ tCtm40eHypeVUlsXJExv3JB0hJ7d7eY2olbY/DcK6CTYt7R4amGU/ClCQpEIVTz2 HcVeH8oOPRUG0STyzKh2lPF0Wua6LUGp9/nZWgsETsXrAQ8MaC/vlyrjiEJsvwP1 65bOoNiRKiGU7tp6JhFE8v85vLKgkzmHeysWJdMt0aczH1DMwlSWS9ViEauLugK7 K0ERNC22WwEzya0EKmTMcRFHYIT1B9/dg0Tbb2h2KKRqu7kzd2NVr6ap5Cu6ezYO hThz6i09OL6ADSwSk4c6JeUUjX7rGG6DNu0pCQYlNJ9xIhi+U/FAuTvzBfU3uJe3 8akO1UGwUWA/TwtnQTv08uGGia+Wt/GbQStkidZFVvdbXcjSH39GlhRXRWDKSOCv wDVNMkopDQOsxwoFgAE45dacQZh2Qv29eT4pG6Eo2J+eXJR2lb5edQkDZNLk2DcE 6frcVchrdBeaUUSA1+ssH3B+hVwwJ7IX/FCwhKDZgxyy67oqGVChkeUjes4GJ5vB 0t7/XZTORvsH6XwBNDKoXS0fswtZiwhPr3YV1nZHwKCa0OWIs9WsPt587K82Hlsf mROMmzivSut43pdALRCr =zKoc -----END PGP SIGNATURE----- _______________________________________________ tz-announce mailing list tz-announce(a)iana.org https://mm.icann.org/mailman/listinfo/tz-announce

1 0

[PROPOSED] * tz-link.html: Tweak URLs.
by Paul Eggert March 22, 2018

March 22, 2018

--- tz-link.html | 56 +++++++++++++++++++++++++++----------------------------- 1 file changed, 27 insertions(+), 29 deletions(-) diff --git a/tz-link.html b/tz-link.html index f3ac4ed..7221777 100644 --- a/tz-link.html +++ b/tz-link.html @@ -7,7 +7,9 @@ <body> <h1>Sources for time zone and daylight saving time data</h1> <p> -Time zone and daylight saving rules are controlled by individual +<a href="https://en.wikipedia.org/wiki/Time_zone">Time zone</a> and +<a href="https://en.wikipedia.org/wiki/Daylight_saving_time">daylight-saving</a> +rules are controlled by individual governments. They are sometimes changed with little notice, and their histories and planned futures are often recorded only fitfully. Here is a summary of attempts to organize and record relevant data in this @@ -20,12 +22,9 @@ time zone database contains code and data that represent the history of local time for many representative locations around the globe. It is updated periodically to reflect changes made by political bodies -to <a href="https://en.wikipedia.org/wiki/Time_zone">time zone</a> -boundaries and -<a href="https://en.wikipedia.org/wiki/Daylight_saving_time">daylight-saving</a> -rules. -This database (often called <code>zoneinfo</code> or -<code><abbr>tz</abbr></code>) +to time zone boundaries and daylight saving rules. +This database (known as <code><abbr>tz</abbr></code>, +<code><abbr>tzdb</abbr></code>, or <code>zoneinfo</code>) is used by several implementations, including <a href="https://www.gnu.org/software/libc/">the @@ -109,7 +108,7 @@ gzip -dc tzdata-latest.tar.gz | tar -xf - release in a single-tarball format containing extra data useful for regression testing:</p> <pre style="margin-left: 2em"><code>wget <a href="https://www.iana.org/time-zones/repository/tzdb-latest.tar.lz">https://www.iana.org/time-zones/repository/tzdb-latest.tar.lz</a> -<a href="http://www.nongnu.org/lzip/">lzip</a> -dc tzdb-latest.tar.lz | tar -xf - +<a href="https://www.nongnu.org/lzip/">lzip</a> -dc tzdb-latest.tar.lz | tar -xf - </code></pre> <p>These commands use convenience links to the latest release of the <code><abbr>tz</abbr></code> database hosted by the @@ -130,7 +129,7 @@ Since version 2016h, each release has contained a text file named The releases are also available in an <a href="ftp://ftp.iana.org/tz/releases/"><abbr title="File Transfer Protocol">FTP</abbr> directory</a> via a -less-secure protocol .</p> +less-secure protocol.</p> <p>Alternatively, a development repository of code and data can be retrieved from <a href="https://github.com">GitHub</a> via the shell command:</p> @@ -192,7 +191,7 @@ href="http://www.oracle.com/technetwork/java/javase/tzupdater-readme-136440.html Java, <a href="http://www.joda.org/joda-time/tz_update.html">Joda-Time</a>, <a href="https://dev.mysql.com/doc/refman/en/time-zone-support.html">MySQL</a>, and <a -href="http://nodatime.org/userguide/tzdb">Noda Time</a> (see below). +href="https://nodatime.org/userguide/tzdb">Noda Time</a> (see below). </p> <p>Sources for the <code><abbr>tz</abbr></code> database are <a href="https://en.wikipedia.org/wiki/UTF-8"><abbr @@ -203,7 +202,7 @@ title="linefeed">LF</abbr></a>, which can be modified by common text editors such as <a href="https://www.gnu.org/software/emacs/">GNU Emacs</a>, <a href="https://wiki.gnome.org/Apps/Gedit">gedit</a>, and -<a href="http://www.vim.org">vim</a>. +<a href="https://www.vim.org">vim</a>. Specialized source-file editing can be done via the <a href="https://packagecontrol.io/packages/zoneinfo">Sublime zoneinfo</a> package for <a @@ -258,7 +257,7 @@ timezone information for all countries</a> displays tables of DST rules. Worldwide</a> lets you sort zone names and convert times.</li> <li><a href="https://24timezones.com">24TimeZones</a> has a world time map and a time converter.</li> -<li><a href="http://www.zeitverschiebung.net/en/">Time Difference</a> +<li><a href="https://www.zeitverschiebung.net/en/">Time Difference</a> calculates the current time difference between locations.</li> <li><a href="http://www.wx-now.com">Weather Now</a> and <a href="http://www.thetimenow.com">The Time Now</a> list the weather too.</li> @@ -290,7 +289,7 @@ variant <a href="https://tools.ietf.org/html/rfc6321">xCal</a> 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 +uses <a href="https://www.json.org"><abbr title="JavaScript Object Notation">JSON</abbr></a> format.</li> </ul> <h2 id="compilers">Other <code><abbr>tz</abbr></code> compilers</h2> @@ -374,7 +373,7 @@ License">LGPL</abbr>)</a>.</li> <li><abbr>ICU</abbr> (mentioned <a href="#ICU">above</a>) contains compilers and Java-based libraries.</li> </ul> -<li><a href="http://nodatime.org">Noda Time – Date and +<li><a href="https://nodatime.org">Noda Time – Date and time <abbr>API</abbr> for .NET</a> and <a href="http://www.babiej.demon.nl/Tz4Net/main.htm">TZ4Net</a> are similar to Joda-Time and Time4J, but for the .NET framework instead of @@ -458,7 +457,7 @@ library that reads tz binary files and converts time stamps from one time zone or format to another. It is used by <a href="https://secure.php.net"><abbr title="PHP: Hypertext Preprocessor">PHP</abbr></a>, -<a href="http://hhvm.com"><abbr title="HipHop Virtual Machine">HHVM</abbr></a>, +<a href="https://hhvm.com"><abbr title="HipHop Virtual Machine">HHVM</abbr></a>, and <a href="https://www.mongodb.com">MongoDB</a>. It is freely available under the <abbr>MIT</abbr> license.</li> <li><a href="https://github.com/bigeasy/timezone">Timezone</a> is a @@ -518,7 +517,7 @@ the older, proprietary method of Microsoft Windows 2000 and later, which stores time zone data in the <a href="https://en.wikipedia.org/wiki/Windows_Registry">Windows Registry</a>. The <a -href="http://unicode.org/cldr/charts/latest/supplemental/zone_tzid.html">Zone → +href="https://unicode.org/cldr/charts/latest/supplemental/zone_tzid.html">Zone → Tzid table</a> or <a href="https://unicode.org/repos/cldr/trunk/common/supplemental/windowsZones.xml"><abbr>XML</abbr> file</a> of the <abbr>CLDR</abbr> data maps proprietary zone IDs @@ -528,7 +527,7 @@ href="https://www.oracle.com/java/index.html">Oracle Java</a> contains a copy of a subset of a recent <code><abbr>tz</abbr></code> database in a Java-specific format.</li> -<li><a href="http://www.relativedata.com/time-zone-master">Time Zone +<li><a href="https://www.relativedata.com/time-zone-master">Time Zone Master</a> is a Microsoft Windows clock program that can automatically download, compile and use <code>tz</code> releases. The Basic version is free.</li> @@ -543,8 +542,8 @@ licenses</a> to <code><abbr>tz</abbr></code> contributors.</li> <li><a href="https://www.astro.com/atlas">Time-zone Atlas</a> is Astrodienst's Web version of Shanks and Pottenger's time zone history atlases also published in <a -href="http://astrocom.com/astrology-products/software/acs-atlas-software">software</a> -form by <a href="http://astrocom.com">ACS-Starcrafts</a>. +href="https://astrocom.com/astrology-products/software/acs-atlas-software">software</a> +form by <a href="https://astrocom.com">ACS-Starcrafts</a>. These atlases are extensive but unreliable, as Shanks appears to have guessed many <abbr>UT</abbr> offsets and transitions. The atlases cite no sources and do not indicate which entries are guesswork.</li> @@ -552,7 +551,7 @@ sources and do not indicate which entries are guesswork.</li> its own <code>tztab</code>(4) format.</li> <li>Microsoft Windows has proprietary data mentioned <a href="#System.TimeZoneInfo">above</a>.</li> -<li><a href="http://www.worldtimeserver.com">World Time Server</a> +<li><a href="https://www.worldtimeserver.com">World Time Server</a> is another time zone database.</li> <li><a href="http://tycho.usno.navy.mil/tzones.html">World Time Zones</a> contains data from the Time Service Department of the @@ -578,14 +577,14 @@ recent editions. The pictorial quality is good, but the maps do not indicate daylight saving time, and parts of the data are a few years out of date.</li> -<li><a href="http://www.worldtimezone.com">Current time around the world +<li><a href="https://www.worldtimezone.com">Current time around the world and standard time zones map of the world</a> has several fancy time zone maps; it covers Russia particularly well. The maps' pictorial quality is not quite as good as the <abbr>CIA</abbr>'s but the maps are more up to date.</li> <li><a -href="http://blog.poormansmath.net/how-much-is-time-wrong-around-the-world/">How +href="https://blog.poormansmath.net/how-much-is-time-wrong-around-the-world/">How 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> @@ -666,9 +665,8 @@ political subdivision data related to time zones.</li> <li><a href="http://home.kpn.nl/vanadovv/time/Multizones.html">Time zone boundaries for multizone countries</a> summarizes legal boundaries between time zones within countries.</li> -<li>Manifold.net's <a -href="http://manifold.net/info/freestuff.shtml">Free Downloads for -Manifold System Users</a> includes a Manifold-format map of +<li><a href="http://manifold.net/info/freestuff.shtml">Manifold Software +– GIS and Database Tools</a> includes a Manifold-format map of world time zone boundaries distributed under the <abbr>GPL</abbr>.</li> <li>A ship within the <a @@ -808,12 +806,12 @@ href="https://en.wikipedia.org/wiki/Dynamic_Host_Configuration_Protocol"><abbr>D option for a server to configure a client's time zone and daylight saving settings automatically.</li> <li><a -href="http://www.cv.nrao.edu/~rfisher/Ephemerides/times.html">Astronomical +href="https://www.cv.nrao.edu/~rfisher/Ephemerides/times.html">Astronomical Times</a> explains more abstruse astronomical time scales like <abbr title="Terrestrial Dynamic Time">TDT</abbr>, <abbr title="Geocentric Coordinate Time">TCG</abbr>, and <abbr title="Barycentric Dynamic Time">TDB</abbr>. -<a href="http://www.ucolick.org/~sla/leapsecs/timescales.html">Time +<a href="https://www.ucolick.org/~sla/leapsecs/timescales.html">Time Scales</a> goes into more detail, particularly for historical variants.</li> <li>The <a href="https://www.iau.org"><abbr title="International Astronomical Union">IAU</abbr></a>'s <a @@ -859,7 +857,7 @@ and Klepczynski's 1999 proposal to discontinue leap seconds</a>, discussed further in <a href="https://www.cl.cam.ac.uk/~mgk25/time/metrologia-leapsecond.pdf">The leap second: its history and possible future</a>. -<a href="http://www.ucolick.org/~sla/leapsecs/"><abbr>UTC</abbr> +<a href="https://www.ucolick.org/~sla/leapsecs/"><abbr>UTC</abbr> might be redefined without Leap Seconds</a> gives pointers on this contentious issue, which was active until 2015 and could become active @@ -873,7 +871,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/latest/by_type/">by-type +<a href="https://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>. -- 2.7.4

1 0

Re: [tz] proposed tz data changes for Iran, Sri Lanka, Alberta, Thule, etc.
by REMI ACIEN March 21, 2018

March 21, 2018

Provenance : Courrier<https://go.microsoft.com/fwlink/?LinkId=550986> pour Windows 10 For Zone Asia/Seoul +8 :27 :52 . Why not .

3 2