- tz - lists.iana.org

Rename Ukrainian cities to their official transliterated names
by Volodymyr Kostyrko Oct. 5, 2018

Oct. 5, 2018

Hello. This is my first attempt on patching tz database. Hope I did everything right. Included patch renames Kiev to Kyiv, Uzhgorod to Uzhhorod and Zaporozhye to Zaporizhzhia according to official transliteration rules that came in effect 2014. According to Google search most sites are already using Uzhhorod and Zaporizhzhia to name cities, while with Kyiv it's a little bit complicated, as it's the capital so it's name was appearing on a huge list of sites throughout years... I'm just trying to bring a little bit of lawful sanity… Thanks in advance. -- Sphinx of black quartz judge my vow.

16 31

[PROPOSED] Improve leapseconds.awk commentary
by Paul Eggert Oct. 5, 2018

Oct. 5, 2018

(Inspired by a suggestion by Chris Woodbury.) * NEWS: Mention this. * leapseconds.awk: Improve commentary in output file. Output "#updated" and "#expires" comments that reproduce the updated and expiry timestamps in the input file. --- NEWS | 3 +++ leapseconds.awk | 36 +++++++++++++++++++++++++----------- 2 files changed, 28 insertions(+), 11 deletions(-) diff --git a/NEWS b/NEWS index 395d9a8..e9f5366 100644 --- a/NEWS +++ b/NEWS @@ -86,6 +86,9 @@ Unreleased, experimental changes transition (or for all time stamps if there are no transitions), just as DST strings specifying DST have always done. + leapseconds.awk now outputs "#updated" and "#expires" comments. + (Inspired by a suggestion from Chris Woodbury.) + Changes to documentation New restrictions: A Rule name must start with a character that diff --git a/leapseconds.awk b/leapseconds.awk index 66eb64d..6b069b3 100644 --- a/leapseconds.awk +++ b/leapseconds.awk @@ -8,21 +8,25 @@ BEGIN { print "# This file is in the public domain." print "" print "# This file is generated automatically from the data in the public-domain" - print "# leap-seconds.list file, which is copied from:" - print "# ftp://ftp.nist.gov/pub/time/leap-seconds.list" + print "# leap-seconds.list file, which can be copied from" + print "# <ftp://ftp.nist.gov/pub/time/leap-seconds.list>" + print "# or <ftp://ftp.boulder.nist.gov/pub/time/leap-seconds.list>" + print "# or <ftp://tycho.usno.navy.mil/pub/ntp/leap-seconds.list>." print "# For more about leap-seconds.list, please see" print "# The NTP Timescale and Leap Seconds" - print "# https://www.eecis.udel.edu/~mills/leap.html" + print "# <https://www.eecis.udel.edu/~mills/leap.html>." print "" print "# The International Earth Rotation and Reference Systems Service" 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 "# Levine J. Coordinated Universal Time and the leap second." + print "# (which measures the true angular orientation of the earth in space)" + print "# and publishes leap second data in a copyrighted file" + print "# <https://hpiers.obspm.fr/iers/bul/bulc/Leap_Second.dat>." + print "# See: Levine J. Coordinated Universal Time and the leap second." print "# URSI Radio Sci Bull. 2016;89(4):30-6. doi:10.23919/URSIRSB.2016.7909995" - print "# http://ieeexplore.ieee.org/document/7909995/" + print "# <https://ieeexplore.ieee.org/document/7909995>." 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." + print "# did not exist." print "" print "# The correction (+ or -) is made at the given time, so lines" print "# will typically look like:" @@ -30,18 +34,19 @@ BEGIN { print "# or" print "# Leap YEAR MON DAY 23:59:59 - R/S" print "" - print "# If the leapsecond is Rolling (R) the given time is local time." - print "# If the leapsecond is Stationary (S) the given time is UTC." + print "# If the leap second is Rolling (R) the given time is local time (unused here)." + print "# If the leap second is Stationary (S) the given time is UTC." print "" print "# Leap YEAR MONTH DAY HH:MM:SS CORR R/S" } -/^ *$/ { next } - /^#\tUpdated through/ || /^#\tFile expires on:/ { last_lines = last_lines $0 "\n" } +/^#[$][ \t]/ { updated = $2 } +/^#[@][ \t]/ { expires = $2 } + /^#/ { next } { @@ -71,5 +76,14 @@ BEGIN { } END { + # The difference between the NTP and POSIX epochs is 70 years + # (including 17 leap days), each 24 hours of 60 minutes of 60 + # seconds each. + epoch_minus_NTP = ((1970 - 1900) * 365 + 17) * 24 * 60 * 60 + + print "" + print "# POSIX timestamps for the data in this file:" + printf "#updated %s\n", updated - epoch_minus_NTP + printf "#expires %s\n", expires - epoch_minus_NTP printf "\n%s", last_lines } -- 2.17.1

1 0

Re: [tz] [PROPOSED] Allow some IPA symbols in commentary
by Paul Eggert Oct. 4, 2018

Oct. 4, 2018

On 10/4/18 9:23 AM, Paul.Koning(a)dell.com wrote: > I wonder if the Unicode standard says so, or if this is a Linux bug. I looked into it, and it's arguably a bug in the glibc regular expression matcher: it does not recognize u̯ as alphabetic because it's composed of U+0075 U+032F and the latter is not alphabetic. Let's add a comment to that effect and remove ɪ from the macro since it works OK. Proposed further patch attached.

1 0

[PROPOSED] Allow some IPA symbols in commentary
by Paul Eggert Oct. 4, 2018

Oct. 4, 2018

This for the [ˈkɪjiu̯] recently added to Kiev comments. * Makefile (UNUSUAL_OK_LATIN_1, UNUSUAL_OK_IPA): New macros. (UNUSUAL_OK_CHARSET): Use them. (check_character_set): Broaden list of exempt lines. --- Makefile | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-) diff --git a/Makefile b/Makefile index 3d06d93..39da17e 100644 --- a/Makefile +++ b/Makefile @@ -418,10 +418,14 @@ SAFE_CHARSET3= 'abcdefghijklmnopqrstuvwxyz{|}~' SAFE_CHARSET= $(SAFE_CHARSET1)$(SAFE_CHARSET2)$(SAFE_CHARSET3) SAFE_CHAR= '[]'$(SAFE_CHARSET)'-]' +# These characters are Latin-1, and so are likely to be displayable +# even in editors with limited character sets. +UNUSUAL_OK_LATIN_1 = «°±»½¾× +# IPA symbols are OK in commentary despite being non-alphabetic. +UNUSUAL_OK_IPA = ɪu̯ # Non-ASCII non-letters that OK_CHAR allows, as these characters are -# useful in commentary. These all came from Latin-1, and so are likely -# to be displayable even in editors with limited character sets. -UNUSUAL_OK_CHARSET= «°±»½¾× +# useful in commentary. +UNUSUAL_OK_CHARSET= $(UNUSUAL_OK_LATIN_1)$(UNUSUAL_OK_IPA) # OK_CHAR matches any character allowed in the distributed files. # This is the same as SAFE_CHAR, except that UNUSUAL_OK_CHARSET and @@ -735,7 +739,7 @@ check_character_set: $(ENCHILADA) $(MISC) $(SOURCES) $(WEB_PAGES) \ CONTRIBUTING LICENSE README \ version tzdata.zi && \ - ! grep -Env $(SAFE_LINE)'|^UNUSUAL_OK_CHARSET='$(OK_CHAR)'*$$' \ + ! grep -Env $(SAFE_LINE)'|^UNUSUAL_OK_'$(OK_CHAR)'*$$' \ Makefile && \ ! grep -Env $(SAFE_SHARP_LINE) $(TDATA_TO_CHECK) backzone \ leapseconds yearistype.sh zone.tab && \ -- 2.17.1

1 0

[PATCH] Fix Asia/Shanghai 1940/9 DST transitions
by Paul Eggert Oct. 3, 2018

Oct. 3, 2018

* NEWS: Mention this. * asia (Shang): Switch to data from 2014 Li Yu paper. --- NEWS | 3 +++ asia | 34 +++++++++++++++++++++++++++------- 2 files changed, 30 insertions(+), 7 deletions(-) diff --git a/NEWS b/NEWS index a24d4b3..e217a50 100644 --- a/NEWS +++ b/NEWS @@ -42,6 +42,9 @@ Unreleased, experimental changes zic turns this into 01:00 on the day after September's second Saturday, which is the best that POSIX or C platforms can do. + Incorporate 1940-1949 Asia/Shanghai DST transitions from a 2014 + paper by Li Yu, replacing more-questionable data from Shanks. + Changes to time zone abbreviations Use "PST" and "PDT" for Philippine time. (Thanks to Paul Goyette.) diff --git a/asia b/asia index 365593a..a7b5c75 100644 --- a/asia +++ b/asia @@ -286,6 +286,29 @@ Zone Asia/Yangon 6:24:47 - LMT 1880 # or Rangoon # China +# From Paul Eggert (2018-10-02): +# The following comes from Table 1 of: +# Li Yu. Research on the daylight saving movement in 1940s Shanghai. +# Nanjing Journal of Social Sciences. 2014;(2):144-50. +# http://oversea.cnki.net/kns55/detail.aspx?dbname=CJFD2014&filename=NJSH2014… +# The table lists dates only; I am guessing 00:00 and 24:00 transition times. +# Also, the table lists the planned end of DST in 1949, but the corresponding +# zone line cuts this off on May 27, when the Communists took power. +# +# Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S +Rule Shang 1940 only - Jun 1 0:00 1:00 D +Rule Shang 1940 only - Oct 12 24:00 0 S +Rule Shang 1941 only - Mar 15 0:00 1:00 D +Rule Shang 1941 only - Nov 1 24:00 0 S +Rule Shang 1942 only - Jan 31 0:00 1:00 D +Rule Shang 1945 only - Sep 1 24:00 0 S +Rule Shang 1946 only - May 15 0:00 1:00 D +Rule Shang 1946 only - Sep 30 24:00 0 S +Rule Shang 1947 only - Apr 15 0:00 1:00 D +Rule Shang 1947 only - Oct 31 24:00 0 S +Rule Shang 1948 1949 - May 1 0:00 1:00 D +Rule Shang 1948 1949 - Sep 30 24:00 0 S + # From Guy Harris: # People's Republic of China. Yes, they really have only one time zone. @@ -336,12 +359,9 @@ Zone Asia/Yangon 6:24:47 - LMT 1880 # or Rangoon # http://data.people.com.cn/pic/101p/1988/04/1988041201.jpg # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S -Rule Shang 1940 only - Jun 3 0:00 1:00 D -Rule Shang 1940 1941 - Oct 1 0:00 0 S -Rule Shang 1941 only - Mar 16 0:00 1:00 D -Rule PRC 1986 only - May 4 2:00 1:00 D -Rule PRC 1986 1991 - Sep Sun>=11 2:00 0 S -Rule PRC 1987 1991 - Apr Sun>=11 2:00 1:00 D +Rule PRC 1986 only - May 4 2:00 1:00 D +Rule PRC 1986 1991 - Sep Sun>=11 2:00 0 S +Rule PRC 1987 1991 - Apr Sun>=11 2:00 1:00 D # From Anthony Fok (2001-12-20): # BTW, I did some research on-line and found some info regarding these five @@ -543,7 +563,7 @@ Rule PRC 1987 1991 - Apr Sun>=11 2:00 1:00 D # Zone NAME GMTOFF RULES FORMAT [UNTIL] # Beijing time, used throughout China; represented by Shanghai. Zone Asia/Shanghai 8:05:43 - LMT 1901 - 8:00 Shang C%sT 1949 + 8:00 Shang C%sT 1949 May 27 8:00 PRC C%sT # Xinjiang time, used by many in western China; represented by Ürümqi / Ürümchi # / Wulumuqi. (Please use Asia/Shanghai if you prefer Beijing time.) -- 2.17.1

2 3

Re： Inquiry to NICT about Japanese Summer time in 1948-1952.
by aya sekido Oct. 2, 2018

Oct. 2, 2018

Dear Nick, Thank you for your interest. We will respond to your inquiry. It is said that corresponding summer time was performed by instruction of the GHQ: General Headquarters (office of the Supreme Commander of the Allied Powers). We do not have detailed data about summer time then. According to the law of those days, the last day of summer time was made into 25 hours. What came after 12:59 p.m. of the last day was 00:00 a.m. of the next day. If you have any further questions, please let us know. Sincerely, Japan Standard Time Group Space-Time standards Laboratory Applied Electromagnetic Research Institute National Institute of Information and Communications Technology From: Phake Nick <c933103(a)gmail.com> Sent: Sunday, September 09, 2018 12:53 AM To: horonet(a)ml.nict.go.jp Cc: tz(a)iana.org Subject: [horonet 13333] Inquiry to NICT about Japanese Summer time in 1948-1952. To receivers of this email: Recently, I have read an article, which mentioned the history of Japanese Summer Time Implementation in the past at www.bengo4.com/internet/n_8461/ <http://www.bengo4.com/internet/n_8461/> . In the article, it was mentioned that the summer time (DST) end at 25 hours at the last day of the implementation period. Does that mean the clock would go up to the 25th hours back then and reach 24:59 before it continues toward 00:00 on the next day in standard time? If not then how did the clock switched from Summer Time back to Standard Time back then? Please use the "reply to all" function when replying to the message so that other receivers of the message can also hear answer on the matter. Sincerely, P.N.

6 13

Turkey decided to stay in +3
by Kıvanç Yazan Oct. 2, 2018

Oct. 2, 2018

Hi, Recently there was some confusion on whether Turkey was going back to +2. A decision is published today. It says all-year-long summer time (ie. UTC+3) is here to stay. No end date is specified. http://www.resmigazete.gov.tr/eskiler/2018/10/20181002-7.pdf Thanks, Kivanc Yazan

1 0

stale leap seconds file at IETF
by Hal Murray Sept. 29, 2018

Sept. 29, 2018

From: https://www.ietf.org/timezones/data/leap-seconds.list # Updated through IERS Bulletin C55 # File expires on: 28 December 2018 >From ftp://ftp.nist.gov/pub/time/leap-seconds.list # Updated through IERS Bulletin C56 # File expires on: 28 June 2019 What's the procedure for getting the IETF copy updated? Is the TZ community maintaining that file or is somebody at the IETF responsible for tracking NIST? -- These are my opinions. I hate spam.

2 1

When will physics make 32-bit signed leap-second counts obsolete?
by Paul Eggert Sept. 27, 2018

Sept. 27, 2018

A while ago I vaguely remember a prediction on this list of when the TZif file format will become obsolete because we have accumulated 2**31 total leap seconds if we continue to just add leap seconds as needed to keep UTC roughly in sync with TAI. To some extent this is just a playful prediction, as the format will undoubtedly become obsolete for other reasons long before then, but it's still fun to predict. Unfortunately I don't remember the details, and a quick Google search didn't find it. Does anyone else remember this? If not, I'll have to recalculate. The topic has just come up again on the tzdist-bis mailing list, which is why I'm thinking about it again. See <https://mailarchive.ietf.org/arch/msg/tzdist-bis/Q7OVmd60wydqcJahS3QRNHwtXHM>.

3 2

another solar-based time proposal (not)
by scs＠eskimo.com Sept. 27, 2018

Sept. 27, 2018

Many have probably seen this, but I'm surprised no one has mentioned Monday's xkcd: https://xkcd.com/2050/

3 2