- tz - lists.iana.org

Trivia: Sunrise in Santiago
by Hank W. June 30, 2015

June 30, 2015

Today, 30 June 2015, is the latest sunrise of winter in Santiago, Chile. I was curious about what that latest time is, not only because this is Chile's first winter on "permanent" Summer Time, but also because UTC-3 is so far from Santiago's LMT of UTC-4.713. Sunrise in Santiago today will be at 08:48 CLST! Hank Wisniewski of Austin, Texas, U.S.A. "'Tis better to be silent and thought the fool than to speak and dispel all doubt." -unknown

1 0

Best practices for upcoming leap second event
by Paul Eggert June 28, 2015

June 28, 2015

If you're responsible for proper timekeeping you probably have already thought about the upcoming leap second at the end of Tuesday 2015-06-30 UTC. This is the first leap second in eighteen years that has fallen on a non-holiday weekday. It might not hurt to run through your checklist again, and (if you haven't already done so) compare it to the checklist recommended by GPS.GOV, NAVCEN, NCCIC, NIST, and USNO. You can find that checklist here: http://www.gps.gov/news/2015/05/leap-second/2015-best-practices-for-leap-se… The new leap second has been in the tz database since release 2015a dated 2015-01-29 22:35:20 -0800, so if you're newer than that you should be good as far as tz is concerned. In the typical case where you're not using tz's leap-second support, you don't need to worry about tz at all.

1 0

Three more tweaks
by Howard Hinnant June 21, 2015

June 21, 2015

Hi, I’ve surveyed the entire database for transitions 24h or less apart with one of them being a faux transition. I found only 6. You just eliminated the first. Two more are in Europe/Istanbul and I see no way to eliminate the faux transition. Here are the remaining 3 with explanations and fixes: ——————————— Europe/Simferopol 1996 Mar 31: 1996-03-30 20:59:59u = 1996-03-30 23:59:59 MSK // 03:00:00 E-Eur MSK/MSD 1996-03-30 21:00:00u = 1996-03-31 01:00:00 MSD // 03:00:00 E-Eur MSK/MSD And then 3h later: 1996-03-30 23:59:59u = 1996-03-31 03:59:59 MSD // 03:00:00 E-Eur MSK/MSD 1996-03-31 00:00:00u = 1996-03-31 04:00:00 MSD // 03:00:00 01:00 MSD The second faux transition can be combined with the first actual transition with: diff --git a/europe b/europe index 630c234..1242927 100644 --- a/europe +++ b/europe @@ -2364,7 +2364,7 @@ Zone Europe/Simferopol 2:16:24 - LMT 1880 # 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 3:00s + 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. ——————————— Europe/Sofia 1982 Sep 26: 1982-09-25 22:59:59u = 1982-09-26 01:59:59 EEST // 02:00:00 Bulg EE%sT 1982-09-25 23:00:00u = 1982-09-26 02:00:00 EEST // 02:00:00 C-Eur EE%sT And then 1h later: 1982-09-25 23:59:59u = 1982-09-26 02:59:59 EEST // 02:00:00 C-Eur EE%sT 1982-09-26 00:00:00u = 1982-09-26 02:00:00 EET // 02:00:00 C-Eur EE%sT The first faux transition can be merged with the second actual transition with: diff --git a/europe b/europe index 630c234..f096de5 100644 --- a/europe +++ b/europe @@ -845,7 +845,7 @@ Zone Europe/Sofia 1:33:16 - LMT 1880 1:00 C-Eur CE%sT 1945 1:00 - CET 1945 Apr 2 3:00 2:00 - EET 1979 Mar 31 23:00 - 2:00 Bulg EE%sT 1982 Sep 26 2:00 + 2:00 Bulg EE%sT 1982 Sep 26 3:00 2:00 C-Eur EE%sT 1991 2:00 E-Eur EE%sT 1997 2:00 EU EE%sT ——————————— Europe/Tallinn 1999 Nov 1: 1999-10-31 00:59:59u = 1999-10-31 03:59:59 EEST // 02:00:00 EU EE%sT 1999-10-31 01:00:00u = 1999-10-31 03:00:00 EET // 02:00:00 EU EE%sT And then 21h later: 1999-10-31 21:59:59u = 1999-10-31 23:59:59 EET // 02:00:00 EU EE%sT 1999-10-31 22:00:00u = 1999-11-01 00:00:00 EET // 02:00:00 EET The second faux transition can be combined with the first actual transition with: diff --git a/europe b/europe index 630c234..c788416 100644 --- a/europe +++ b/europe @@ -1084,7 +1084,7 @@ Zone Europe/Tallinn 1:39:00 - LMT 1880 3:00 Russia MSK/MSD 1989 Mar 26 2:00s 2:00 1:00 EEST 1989 Sep 24 2:00s 2:00 C-Eur EE%sT 1998 Sep 22 - 2:00 EU EE%sT 1999 Nov 1 + 2:00 EU EE%sT 1999 Oct 31 4:00 2:00 - EET 2002 Feb 21 2:00 EU EE%sT Thanks, Howard

2 2

[tz-announce] 2015e release of tz code and data available
by Paul Eggert June 13, 2015

June 13, 2015

The 2015e 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 affecting future time stamps Morocco will suspend DST from 2015-06-14 03:00 through 2015-07-19 02:00, not 06-13 and 07-18 as we had guessed. (Thanks to Milamber.) Assume Cayman Islands will observe DST starting next year, using US rules. Although it isn't guaranteed, it is the most likely. Changes affecting data format The file 'iso3166.tab' now uses UTF-8, so that its entries can better spell the names of Åland Islands, Côte d'Ivoire, and Réunion. Changes affecting code When displaying data, tzselect converts it to the current locale's encoding if the iconv command works. (Problem reported by random832.) tzselect no longer mishandles Dominica, fixing a bug introduced in Release 2014f. (Problem reported by Owen Leibman.) zic -l no longer fails when compiled with -DTZDEFAULT=\"/etc/localtime\". This fixes a bug introduced in Release 2014f. (Problem reported by Leonardo Chiquitto.) Here are links to the release files: ftp://ftp.iana.org/tz/releases/tzcode2015e.tar.gz ftp://ftp.iana.org/tz/releases/tzdata2015e.tar.gz The files are also available via HTTP as follows: http://www.iana.org/time-zones/repository/releases/tzcode2015e.tar.gz http://www.iana.org/time-zones/repository/releases/tzdata2015e.tar.gz 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 ftp://ftp.iana.org/tz/tzcode-latest.tar.gz ftp://ftp.iana.org/tz/tzdata-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 503ee68905da57fc52df74c889aedf4e67e59a79 dated Sat Jun 13 10:56:02 2015 -0700 and tagged '2015e' in the experimental github repository at <https://github.com/eggert/tz>. Here are the SHA-512 checksums for the release files: fdc568a68f4876b967b39e21fa53f063dc5756e886e2a273cc046d5a014eb517e9c91eb6e03d18c94a89ce48578868aed710790415c500188fce4e4add0ce7ca tzcode2015e.tar.gz 86498190a20c5c67827aa75f7e9c6aa6c19d58a88a70425ce70d5ae7cea42dc7386eb2867fa455fcfcdedc6a105ad70fbbdc7c27c7a58a51bd21d76a135983ce tzdata2015e.tar.gz Here are the GPG checksums for the release files: -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAABAgAGBQJVfG8zAAoJEO2X6Q5iqn4014YP/jGiiK7VYqstDoQNm33/pOwx WlwTSkzByrhx0whaaAlTQ+j61q2MdZaDlpdDd4CEGN1vWaiI26MOEbZEKVpW5ogm xKGL9esGltoc3jelmWJTVf0e03l+k0+zDcnBq+58Pi5rkgM/WVFyZBDyCT5HGLq+ NPaHLHU4dlWtwpyd9Mr4eMb6DPEM4zbTK2NbHh/uf+ODG8F1VW8FP63N/hqq4Y/q 4H+ngf9jJxw73pBri/WBmidSxLWhhc+woezhKqbCThto4Jhoehlp3txIqBmAoN3G AwppaGiHV6PYheLqloCDmdxABMoS95tznuk8eL2FF69IP541kaOchHvKCnbEf6gu Sdr388Ayli/C98ZQknwzNWVlfKKW+d+nidS5iGyEHRpI/42RPemGh5kgYmZucZpH DRIbujsi9usxjrazWC8oGf7WH6D6ZmsUusl7pj071YnU0gpXyVSk9GUoMWIp3Wxc CSHJWxF6lkxOmHDqZFHhcVyyKlPHXFpWpDUPhu/QTi7oiSQeXRoP9BQAz07oN8WS 69JUSxCvkFANkFxnx6knsDBwduFUqiZ209WwV0R72DI/7Gi6OuubXUvgcQfJOHab wOyEInI32uHRKxEaQuDmu1PSzlur0iNGH3PtuQzgwLlMM0KXsRbLBhOO5zP2BgQ6 zVgFQ9FGlnExUxsBcnTf =BRRd -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAABAgAGBQJVfG8/AAoJEO2X6Q5iqn40ed0P/jn6lgG6tH+C2Xv2DYz5buRK CMDoGidznyzDuPSNgSPRaDetoKQ/6iVzEIgHYwBxBtmKmPXUgSY8rJPCabSLNKWK T3o7f8aREnIcfexmct/4DEeUOXePUIbSHnX6Noy3AmSvIsKT8ZahEpnELKgWFQD8 0EEOlck1rTTpEi9G2RATUwr430ii1OguIt0sKYycTvT1VFdihKWoFhgV9ydgaMh2 88he3Ornt4xd4/b278IJl3GI0WWVbVl2A+ziRPAkl3AH7iW7mTcv+/8i3u7txVW+ zB47UHOfV9jpiecLUQDw42KZJTlS+AkbgCitrpL++bZz1WQHWP9JkpgvAR8bdkBf WPNvcPXiG0I6Vtl2ZZrc2WXi9L22m0xIJA2so4vpBwBIMkTnaFa6VthLGy9UgHpA wteG6OogfdNm7fv+GhuRUNuHtd5TP5HdywhWMrMtGqgOvkEm/lF6tRMd12Wm57IW u72Gv3RrJILBuOvBvWPZJMNsjc8Uj1U+dhKa8Z51VHA85ZyiRM3mQr8g+1WETH/E sjnj8NgKkh7TL/N5vWJH1M3g1XZ3uofPL1Cbyqg04BGrMytxGAjigzIDbbg5pky+ yFUqR3qm12d9QPlm1xh35qxqYYDXcbiQkXENwGukLRzcc0jdU4BrFpDc1tVgukUg TmCC2ALEcxWWPEc1vtUG =gO91 -----END PGP SIGNATURE----- _______________________________________________ tz-announce mailing list tz-announce(a)iana.org https://mm.icann.org/mailman/listinfo/tz-announce

1 0

Morocco DST Interruption during Ramadan 2015
by Milamber June 12, 2015

June 12, 2015

Hello, (Google Translation) The current time of Morocco (GMT + 1) will be suspended from next Sunday until July 19, announced Monday the Ministry of Civil Service and Modernisation of Administration. The hour will thus be delayed 60 minutes Sunday, June 14 at 3:00, the ministry said in a statement, adding that the time will be advanced again 60 minutes Sunday, July 19, 2015 at 2:00. The move comes under 2.12.126 Decree of 26 Jumada I 1433 (18 April 2012) and the decision of the Head of Government of 16 N. 3-29-15 Chaaban 1435 (4 June 2015). Source (french): http://lnt.ma/le-maroc-reculera-dune-heure-le-dimanche-14-juin/ (currently the official notice isn't publish on official government website http://www.mmsp.gov.ma) I thinks that the new rule for all new ramadan period is the time change the Sunday (like the DST) or not the Saturday. Milamber Note: Current prediction in tzdata: Africa/Casablanca Sat Jun 13 01:59:59 2015 UT = Sat Jun 13 02:59:59 2015 WEST isdst=1 gmtoff=3600 Africa/Casablanca Sat Jun 13 02:00:00 2015 UT = Sat Jun 13 02:00:00 2015 WET isdst=0 gmtoff=0 Africa/Casablanca Sat Jul 18 01:59:59 2015 UT = Sat Jul 18 01:59:59 2015 WET isdst=0 gmtoff=0 Africa/Casablanca Sat Jul 18 02:00:00 2015 UT = Sat Jul 18 03:00:00 2015 WEST isdst=1 gmtoff=3600

3 6

Possible bug in the tz database
by Howard Hinnant June 8, 2015

June 8, 2015

I’m new to this list, so please forgive me for my inexperience and lack of history. I am concerned about the timezone America/North_Dakota/Beula: Early of the local morning of 2010-11-07 the local timezone GMTOFF changed from -7:00 to -6:00, and the timezone abbreviation changed from MDT to CST. I am not questioning this historical fact. Rather I am concerned about exactly when it happened and does the tz database accurately reflect this event. Here are the relevant entries today: Zone America/North_Dakota/Beulah -6:47:07 - LMT 1883 Nov 18 12:12:53 -7:00 US M%sT 2010 Nov 7 2:00 -6:00 US C%sT Which says at 2:00am local time on 2010/Nov/07 the change from MDT to CST occurs. Local time is defined by GMTOFF == -7:00 + US timezone rules for 2010. Or in other words 2:00am + 7:00 + any daylight savings time adjustment. I’m sure I’m preaching to the choir with this audience. I think there is no dispute that: 2010-11-07 01:59:59 MDT == 2010-11-07 07:59:59 UTC At this point in time the GMTOFF == -7:00 and in the US rule SAVE == 1:00 for a total offset of -6:00. However according to US rules for this date, the local clock ticks from 01:59:59 MDT to 01:00:00 MST. To reach 2:00am local time we need to wait another hour: 2010-11-07 02:00:00 MST == 2010-11-07 09:00:00 UTC According to US time zone rules (speaking about the recognized practice in the US, not about tz database rules), there was no 2010-11-07 02:00:00 MDT. It simply did not exist. So 2010-11-07 02:00:00 local time in US rules is unambiguously a standard time, not a daylight savings time. Whereas the times [01:00:00, 01:59:59] *are* ambiguous (or more accurately described with a half-open range: [01:00:00, 02:00:00). Since 2010-11-07 02:00:00 is unambiguously a standard time, the database could read like this with no change in behavior: Zone America/North_Dakota/Beulah -6:47:07 - LMT 1883 Nov 18 12:12:53 -7:00 US M%sT 2010 Nov 7 2:00s -6:00 US C%sT But this data indicates that local time behaves as follows that morning: 2010-11-07 01:59:59 MDT = 2010-11-07 07:59:59 UTC 2010-11-07 01:00:00 MST = 2010-11-07 08:00:00 UTC 2010-11-07 01:00:01 MST = 2010-11-07 08:00:01 UTC … 2010-11-07 01:59:59 MST = 2010-11-07 08:59:59 UTC 2010-11-07 03:00:00 CST = 2010-11-07 09:00:00 UTC 2010-11-07 03:00:01 CST = 2010-11-07 09:00:01 UTC However I believe the intended behavior is: 2010-11-07 01:59:59 MDT = 2010-11-07 07:59:59 UTC 2010-11-07 02:00:00 CST = 2010-11-07 08:00:00 UTC 2010-11-07 02:00:01 CST = 2010-11-07 08:00:01 UTC I believe the tz database can be changed to give the desired behavior with: diff --git a/northamerica b/northamerica index 88423e6..aeaf12c 100644 --- a/northamerica +++ b/northamerica @@ -371,7 +371,7 @@ Zone America/North_Dakota/New_Salem -6:45:39 - LMT 1883 Nov 18 12:14:21 # of 6h47'07". Zone America/North_Dakota/Beulah -6:47:07 - LMT 1883 Nov 18 12:12:53 - -7:00 US M%sT 2010 Nov 7 2:00 + -7:00 US M%sT 2010 Nov 7 1:00s -6:00 US C%sT # US mountain time, represented by Denver If I have misinterpreted the meanings of the fields to the tz database in some way, I would appreciate an education. I’ve reread all of the man pages and other documentation I can find, and haven’t been able to rectify this contradiction on my own. If this is indeed a bug that can be corrected, I am volunteering to detect and correct similar issues elsewhere in the database and generate a pull request for https://github.com/eggert/tz. Howard

5 5

NTSB investigation derailed by time zone labyrinth
by Paul Eggert June 6, 2015

June 6, 2015

When the chair of the U.S. National Transportation Safety Board appeared before the House Transportation and Infrastructure Committee this week, he was asked "Could you just tell us again in plain English why we don't know if this operator was on the phone three weeks after the accident?" He had trouble answering, because although the NTSB has detailed timestamped data for the engineer's cell phone records, and they have physical access to the phone and the phone's passwords, they can't figure out the data's time zones. The cell phone companies don't know either. My sources: Jaffe E. We still basically have no idea what happened with the Amtrak 188 derailment. CityLab 2015-06-04. http://www.citylab.com/commute/2015/06/we-still-basically-have-no-idea-what… Nixon R. Phone data labyrinth hinders investigation of Amtrak derailment. New York Times 2015-06-05. http://www.nytimes.com/2015/06/06/us/inquiry-into-amtrak-derailment-is-slow…

1 0

DST in the US 1945-1966
by Matt Johnson June 4, 2015

June 4, 2015

Wikipedia's page at:http://en.wikipedia.org/wiki/Daylight_saving_time_in_the_United_States#H… states the following: >From 1945 to 1966 there was no federal law on daylight saving time, so localities could choose when it began and ended or drop it entirely. In 1954 only California and Nevada had statewide DST west of the Mississippi, and only a few cities between Nevada and St Louis. In the 1964 Official Railway Guide, 21 of the 48 states had no DST anywhere. I'm wondering if we have any additional details about the localities that adopted DST during this period and those that did not? Also, do we already incorporated data from the source mentioned? (the 1964 Official Railway Guide) Specifically, I was discussing this topic with another developer who was curious about Nashville, Tennessee. One could probably assume that it was on Central time - due to the Standard Time Act, but whether or not it used DST (specifically in 1949) or not is the question. The tz database entry for Chicago would say yes - but my guess is that it might not be certain that both Chicago and Nashville used DST that year. Thanks.

2 1

[PROPOSED PATCH] tzselect: port to POSIX sh and fix a typo
by Paul Eggert May 27, 2015

May 27, 2015

* tzselect.ksh: Use portable names for trap signals. Also, fix a typo: signal 2 (INT) was meant, not signal 12. --- tzselect.ksh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tzselect.ksh b/tzselect.ksh index 2a622f5..2c3b2f4 100644 --- a/tzselect.ksh +++ b/tzselect.ksh @@ -191,7 +191,7 @@ done tmp=${TMPDIR-/tmp}/tzselect.$$ && (umask 77 && mkdir -- "$tmp") };} && - trap 'status=$?; rm -fr -- "$tmp"; exit $status' 0 1 12 13 15 && + trap 'status=$?; rm -fr -- "$tmp"; exit $status' 0 HUP INT PIPE TERM && (iconv -f UTF-8 -t //TRANSLIT <"$TZ_COUNTRY_TABLE" >$tmp/iso3166.tab) \ 2>/dev/null && TZ_COUNTRY_TABLE=$tmp/iso3166.tab && -- 2.1.4

1 0

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

May 25, 2015

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

5 5

"zic -l" complains about "empty component" in /etc/localtime
by Leonardo Chiquitto May 20, 2015

May 20, 2015

Hello, With 2015d I can no longer use "zic -l" to recreate /etc/localtime. I'm getting the following error: # ./zic -l America/Sao_Paulo ./zic: file name '/etc/localtime' contains empty component If I comment out the check introduced by commit 0ddac5ef7e in componentcheck(), then it works fine again: # ./zic -l America/Sao_Paulo # ls -lai /etc/localtime 1183669 -rw-r--r-- 5 root root 2015 May 17 20:20 /etc/localtime # ls -lai /usr/share/zoneinfo/America/Sao_Paulo 1183669 -rw-r--r-- 5 root root 2015 May 17 20:20 /usr/share/zoneinfo/America/Sao_Paulo A quick analysis: when "/etc/localtime" is passed to namecheck(), in the first loop iteration componentcheck() will be called with all three arguments set to "/etc/localtime". A possible fix is to skip this call to componentcheck() in the first iteration (patch attached). Leonardo

2 2

Leap seconds in the news
by Arthur David Olson May 20, 2015

May 20, 2015

>From the Wall Street Journal: "Markets Are Jumpy Over Coming Leap Second" http://www.wsj.com/articles/markets-are-jumpy-over-coming-leap-second-14319… @dashdashado

5 5

[PROPOSED PATCH] Guess Cayman Is will observe DST starting 2016
by Paul Eggert May 15, 2015

May 15, 2015

* NEWS: Document this. * backzone (America/Cayman): Move from here ... * northamerica: ... back to here, and assume US-style DST starting 2016. * zone1970.tab (KY): Now a separate row, since KY and PA disagree starting 2016. --- NEWS | 5 +++++ backzone | 5 ----- northamerica | 13 +++++++++++-- zone1970.tab | 3 ++- 4 files changed, 18 insertions(+), 8 deletions(-) diff --git a/NEWS b/NEWS index 392f09b..d69a98c 100644 --- a/NEWS +++ b/NEWS @@ -2,6 +2,11 @@ News for the tz database Unreleased, experimental changes + Changes affecting future time stamps + + Assume Cayman Islands will observe DST starting next year, using US rules. + Although it isn't guaranteed, it is the most likely. + Changes affecting data format The file 'iso3166.tab' now uses UTF-8, so that its entries can better diff --git a/backzone b/backzone index 6b392bd..0316708 100644 --- a/backzone +++ b/backzone @@ -279,11 +279,6 @@ Zone America/Aruba -4:40:24 - LMT 1912 Feb 12 # Oranjestad -4:30 - ANT 1965 # Netherlands Antilles Time -4:00 - AST -# Cayman Is -Zone America/Cayman -5:25:32 - LMT 1890 # Georgetown - -5:07:11 - KMT 1912 Feb # Kingston Mean Time - -5:00 - EST - # Canada Zone America/Coral_Harbour -5:32:40 - LMT 1884 -5:00 NT_YK E%sT 1946 diff --git a/northamerica b/northamerica index c3af9eb..88423e6 100644 --- a/northamerica +++ b/northamerica @@ -2661,7 +2661,17 @@ Zone Atlantic/Bermuda -4:19:18 - LMT 1930 Jan 1 2:00 # Hamilton -4:00 US A%sT # Cayman Is -# See America/Panama. + +# From Paul Eggert (2015-05-15): +# The Cayman government has decided to introduce DST in 2016, the idea being +# to keep in sync with New York. The legislation hasn't passed but the change +# seems quite likely. See: Meade B. Cayman 27. +# http://www.cayman27.com.ky/2015/05/15/clock-ticks-toward-daylight-saving-ti… + +Zone America/Cayman -5:25:32 - LMT 1890 # Georgetown + -5:07:11 - KMT 1912 Feb # Kingston Mean Time + -5:00 - EST 2016 + -5:00 US E%sT # Costa Rica @@ -3184,7 +3194,6 @@ Zone America/Managua -5:45:08 - LMT 1890 Zone America/Panama -5:18:08 - LMT 1890 -5:19:36 - CMT 1908 Apr 22 # Colón Mean Time -5:00 - EST -Link America/Panama America/Cayman # Puerto Rico # There are too many San Juans elsewhere, so we'll use 'Puerto_Rico'. diff --git a/zone1970.tab b/zone1970.tab index 5da0200..2689c00 100644 --- a/zone1970.tab +++ b/zone1970.tab @@ -206,6 +206,7 @@ KI -0308-17105 Pacific/Enderbury Phoenix Islands KI +0152-15720 Pacific/Kiritimati Line Islands KP +3901+12545 Asia/Pyongyang KR +3733+12658 Asia/Seoul +KY +1918-08123 America/Cayman KZ +4315+07657 Asia/Almaty most locations KZ +4448+06528 Asia/Qyzylorda Qyzylorda (Kyzylorda, Kzyl-Orda) KZ +5017+05710 Asia/Aqtobe Aqtobe (Aktobe) @@ -259,7 +260,7 @@ NR -0031+16655 Pacific/Nauru NU -1901-16955 Pacific/Niue NZ,AQ -3652+17446 Pacific/Auckland New Zealand time NZ -4357-17633 Pacific/Chatham Chatham Islands -PA,KY +0858-07932 America/Panama +PA +0858-07932 America/Panama PE -1203-07703 America/Lima PF -1732-14934 Pacific/Tahiti Society Islands PF -0900-13930 Pacific/Marquesas Marquesas Islands -- 2.1.0

1 0

Time Zone Database from Portugal
by Suzana Ferreira May 15, 2015

May 15, 2015

Hi, Where can I see information about Time Zone Database related to Portugal in your site?http://www.iana.org/time-zones http://tools.ietf.org/html/rfc6557 Thank you, -- Suzana Ferreira, Astrónoma ********************************************* Observatório Astronómico de Lisboa (OAL) -------------- desde 1861 -------------- Edifício Leste, Tapada da Ajuda, PT-1349-018 LISBOA, PORTUGAL tel: (351) 213616734 / fax: (351) 213616750 www.oal.ul.pt *********************************************

2 1

Time Zones - Canary Islands - Offshore Spain - Error
by moxhull May 15, 2015

May 15, 2015

Dear Paul Eggert, I use software which sources your data in github for time zones. The Canary Islands, located off the coast of Morocco, belong to Spain but have a different time zone. It's causing me problems because it seems your files do not take account of this. Would you kindly amend your files accordingly, please, so that my software programmer can use an updated file, so in turn I can use his software? Please see below for references. Many thanks indeed, so grateful. Yours sincerely, Sylvie ---------- Forwarded message ---------- From: Anatoly Zaytsev <astrozet(a)gmail.com> Date: Thu, May 14, 2015 at 5:41 PM Subject: Re: Zet 8 Geo, time zones To: moxhull <moxhull(a)gmail.com> Hello Sylvie, 1) This is not so important. 2) I use more (seems) relevant source: https://github.com/eggert/tz Paul Eggert tz-bounces(a)iana.org also https://github.com/eggert/tz/blob/master/europe line 2922 Please talk with him. ----------------- Anatoly Zaytsev www.astrozet.com ----- Original Message ----- From: "moxhull" <moxhull(a)gmail.com> To: <astrozet(a)gmail.com> Sent: Thursday, May 14, 2015 7:02 PM Subject: Zet 8 Geo, time zones Dear Anatoly, I hope you are well. I write for two items: - I have retired from my job in Geneva (Switzerland), sold my house in France, and I have moved to the Canary Islands, a part of Spain that is off the coast of Morocco. So my addresses, email and telephone number need to be changed in your records - see below. - The Canary Islands do not use the same time as mainland Spain, so I'm having trouble with the time changes. I tried to make a few modifications in my Zet but I do not know enough and did not succeed. Please would make the corrections in the time zone files and make them available? For reference see: http://en.wikipedia.org/wiki/Time_in_Spain#The_Canary_Islands_exception Thank you very much for correcting this. Kind regards, Sylvie Weber Calle Aceviño 49 Ed. Tarahal, Apto 201 38400 Puerto de la Cruz, Tenerife Spain Tel. +34 674 80 18 34 email: moxhull(a)gmail.com [image: Inline image 1]

2 1

Question about IANA time zone names
by Avila, Edgar May 15, 2015

May 15, 2015

Hi, I'm a software engineer working on the data modeling group. We are trying to figure out how the IANA time zone names can be described on our message model. At the modem it seems that the time zone names such as America/Costa_Rica or Japan are just a string without restrictions. We wonder whether there is a restriction such as maximum length of characters, pattern of characters to allow, etc. One more question, is it really America/Costa_Rica or Japan a name or an ID? The following is the description we have today in one of our schemas: <xs:simpleType name="IANATimeZoneId_Type"> <xs:annotation> <xs:documentation> Timezone Id represented by IANA. </xs:documentation> </xs:annotation> <xs:restriction base="xs:string"/> </xs:simpleType> Thanks in advance ________________________________ [https://www.aciworldwide.com/photolibrary/ACI_logotag_footer.gif]<http://www.aciworldwide.com> This email message and any attachments may contain confidential, proprietary or non-public information. The information is intended solely for the designated recipient(s). If an addressing or transmission error has misdirected this email, please notify the sender immediately and destroy this email. Any review, dissemination, use or reliance upon this information by unintended recipients is prohibited. Any opinions expressed in this email are those of the author personally.

2 1

Re: [tz] [C/C++ PATCH] Implement -Wshift-negative-value (PR c/65179)
by Paul Eggert May 12, 2015

May 12, 2015

On 05/08/2015 09:59 AM, Joseph Myers wrote: > Paul, although glibc's copy of parts of tzcode is a bit out of date, it > looks like the currenthttps://github.com/eggert/tz.git still has the > problematic code in private.h, relying on left-shifting -1 which has > undefined behavior in C99/C11 (implementation-defined in C90, as per > DR#081). Thanks for reporting that. I installed the attached patch into the experimental tz version on github <https://github.com/eggert/tz>, with the intent that this fix propagate into the next tz release and thus into glibc etc.

3 2

Problem with tzselect and Dominica
by Owen Leibman May 12, 2015

May 12, 2015

Using a freshly downloaded version of tzelect, and choosing 2 (Americas) followed by 18 (Dominica), the following results: ./tzselect: line 469: /usr/share/zoneinfo/ America/Port_of_Spain: No such file or directory ./tzselect: time zone files are not set up correctly I believe that is because Dominica's abbreviation (DM) is actually found in some comments near the head of the file. To avoid this problem, I believe he awk statement at line 463: $1 ~ cc && $4 == region { print $3 } needs to be changed thus to exclude comment lines: $0 !~ /^#/ && $1 ~ cc && $4 == region { print $3 }

2 1

[PROPOSED PATCH 1/2] Prefer '$(MAKE)' to 'make'
by Paul Eggert May 8, 2015

May 8, 2015

* Makefile (check_public, check_time_t_alternatives) (typecheck): Use '$(MAKE)' instead of 'make'. This has better behavior with GNU 'make' and -j. --- Makefile | 16 +++++++++------- 1 file changed, 9 insertions(+), 7 deletions(-) diff --git a/Makefile b/Makefile index 6f70979..8d624bc 100644 --- a/Makefile +++ b/Makefile @@ -324,6 +324,8 @@ GZIPFLAGS= -9n ############################################################################### +#MAKE= make + cc= cc CC= $(cc) -DTZDIR=\"$(TZDIR)\" @@ -572,8 +574,8 @@ set-timestamps.out: $(ENCHILADA) # We also do an all-files run to catch links to links. check_public: $(ENCHILADA) - make maintainer-clean - make "CFLAGS=$(GCC_DEBUG_FLAGS)" $(ENCHILADA) all + $(MAKE) maintainer-clean + $(MAKE) "CFLAGS=$(GCC_DEBUG_FLAGS)" $(ENCHILADA) all mkdir tzpublic for i in $(TDATA) ; do \ $(zic) -v -d tzpublic $$i 2>&1 || exit; \ @@ -592,8 +594,8 @@ check_time_t_alternatives: zones=`$(AWK) '/^[^#]/ { print $$3 }' <zone1970.tab` && \ for type in $(TIME_T_ALTERNATIVES); do \ mkdir -p tzpublic/$$type && \ - make clean_misc && \ - make TOPDIR=`pwd`/tzpublic/$$type \ + $(MAKE) clean_misc && \ + $(MAKE) TOPDIR=`pwd`/tzpublic/$$type \ CFLAGS='$(CFLAGS) -Dtime_tz='"'$$type'" \ REDO='$(REDO)' \ install && \ @@ -639,12 +641,12 @@ tzdata$(VERSION).tar.gz.asc: tzdata$(VERSION).tar.gz gpg --armor --detach-sign $? typecheck: - make clean + $(MAKE) clean for i in "long long" unsigned; \ do \ - make CFLAGS="-DTYPECHECK -D__time_t_defined -D_TIME_T \"-Dtime_t=$$i\"" ; \ + $(MAKE) CFLAGS="-DTYPECHECK -D__time_t_defined -D_TIME_T \"-Dtime_t=$$i\"" ; \ ./zdump -v Europe/Rome ; \ - make clean ; \ + $(MAKE) clean ; \ done zonenames: $(TDATA) -- 2.1.0

1 1

[PROPOSED PATCH 1/3] Remove hair from southamerica comment
by Paul Eggert May 4, 2015

May 4, 2015

While using the tz source to test some other program I found an unwanted hair space (U+200A) in the commentary. Fix this, and adjust Makefile to catch this sort of thing in the future. * Makefile (SAFE_CHARSET): Exclude ] and -, as they're now the invoker's responsibility. Invoker changed. (NONSYM_CHAR): Remove, replacing with ... (OK_CHAR): ... this new macro. All uses changed. (NONSYM_LINE, VALID_LINE): Remove, replacing with ... (OK_LINE): ... this new macro. All uses changed. (check_character_set): Simplify test, and report all non-ASCII non-letters. Remove the exception for Makefile, as it no longer needs to contain non-OK characters. * southamerica: Replace an inadvertent hair space with a space. --- Makefile | 30 ++++++++++++++---------------- southamerica | 2 +- 2 files changed, 15 insertions(+), 17 deletions(-) diff --git a/Makefile b/Makefile index b398727..c3b23c8 100644 --- a/Makefile +++ b/Makefile @@ -292,23 +292,24 @@ TAB_CHAR= ' ' SAFE_CHARSET1= $(TAB_CHAR)' !\"'$$sharp'$$%&'\''()*+,./0123456789:;<=>?@' SAFE_CHARSET2= 'ABCDEFGHIJKLMNOPQRSTUVWXYZ[\\^_`' SAFE_CHARSET3= 'abcdefghijklmnopqrstuvwxyz{|}~' -SAFE_CHARSET= ]$(SAFE_CHARSET1)$(SAFE_CHARSET2)$(SAFE_CHARSET3)- -SAFE_CHAR= '['$(SAFE_CHARSET)']' -# NONSYM_CHAR is a regular expression that matches any character -# except for a small number of symbols, where we prefer to stick with +SAFE_CHARSET= $(SAFE_CHARSET1)$(SAFE_CHARSET2)$(SAFE_CHARSET3) +SAFE_CHAR= '[]'$(SAFE_CHARSET)'-]' + +# OK_CHAR matches any character allowed in the distributed files. +# This is the same as SAFE_CHAR, except that multibyte letters are +# also allowed so that commentary can contain people's names and quote +# non-English sources. For non-letters the sources are limited to # ASCII renderings for the convenience of maintainers whose text editors # mishandle UTF-8 by default (e.g., XEmacs 21.4.22). -NONSYM_CHAR= '[^–—°′″≈≠≤≥±−×÷∞←→↔·•§¶«»‘’‚‛“”„‟‹›「」『』〝〞〟]' +OK_CHAR= '[][:alpha:]'$(SAFE_CHARSET)'-]' # SAFE_LINE matches a line of safe characters. -# SAFE_SHARP_LINE is similar, except any character can follow '#'; +# SAFE_SHARP_LINE is similar, except any OK character can follow '#'; # this is so that comments can contain non-ASCII characters. -# NONSYM_LINE matches a line of non-symbols. -# VALID_LINE matches a line of any validly-encoded characters. +# OK_LINE matches a line of OK characters. SAFE_LINE= '^'$(SAFE_CHAR)'*$$' -SAFE_SHARP_LINE='^'$(SAFE_CHAR)'*('$$sharp$(NONSYM_CHAR)'*)?$$' -NONSYM_LINE= '^'$(NONSYM_CHAR)'*$$' -VALID_LINE= '^.*$$' +SAFE_SHARP_LINE='^'$(SAFE_CHAR)'*('$$sharp$(OK_CHAR)'*)?$$' +OK_LINE= '^'$(OK_CHAR)'*$$' # Flags to give 'tar' when making a distribution. # Try to use flags appropriate for GNU tar. @@ -475,14 +476,11 @@ check: check_character_set check_white_space check_links check_sorted \ check_character_set: $(ENCHILADA) LC_ALL=en_US.utf8 && export LC_ALL && \ sharp='#' && \ - ! grep -Env $(SAFE_LINE) $(MANS) date.1 $(MANTXTS) \ + ! grep -Env $(SAFE_LINE) Makefile $(MANS) date.1 $(MANTXTS) \ $(MISC) $(SOURCES) $(WEB_PAGES) && \ ! grep -Env $(SAFE_SHARP_LINE) $(TDATA) backzone \ iso3166.tab leapseconds yearistype.sh zone.tab && \ - test $$(grep -Ecv $(SAFE_SHARP_LINE) Makefile) -eq 1 && \ - ! grep -Env $(NONSYM_LINE) CONTRIBUTING NEWS README Theory \ - $(MANS) date.1 zone1970.tab && \ - ! grep -Env $(VALID_LINE) $(ENCHILADA) + ! grep -Env $(OK_LINE) $(ENCHILADA) check_white_space: $(ENCHILADA) ! grep -En ' '$(TAB_CHAR)"|$$(printf '[\f\r\v]')" $(ENCHILADA) diff --git a/southamerica b/southamerica index be63a88..6bbc2c8 100644 --- a/southamerica +++ b/southamerica @@ -30,7 +30,7 @@ # 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 +# -- 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 -- 2.1.4

2 4

Re: [tz] Kyiv time zone
by sam.ua April 29, 2015

April 29, 2015

Dear Florian. perhaps you are not aware of the history between Ukraine and Russia. Let me remind you that Moscow has pursued the destruction of Ukraine, Ukrainians and the Ukrainian language and culture for many centuries. This ethnic cleansing continues today with the Russification of Ukraine. Once you destroy a nation's identity --their language, culture and history, it's quite easy to convert them into mindless robots, who are easy prey for the imperialist. Even in 1991, as we achieved our long overdue independence , Ukrane was over 80-90% pro-Russian. after two plus decades those same people, who were once slaves to the empire, have been schooled on the true history of Ukraine and understand just how devious Moscow was in it's ethnic cleansing of the Ukrainian people. Little over a year ago we got rid of the last remaining remnant of that Soviet-Russian past - the Putin puppet Yanykovych. Our cities are nearly rid of Lenin and Stalin - two monsters that murdered tens of millions of Ukrainians, but as the links you provided show, that past is still a part of the present. We are gradually getting rid of it. The issue of Kyiv vs Kiev is precisely the past vs the present. Kyiv is today, it's also what it was in the old Ruthenian-Ukrainian chronicles that date back to the 9th century. It became Kiev under Russian rule and now it's once again Kyiv. The war in Eastern Ukraine - the invasion by Russia, is a last attempt too keep Ukraine under Russia's orbit. we don't want that. My generation doesn't want that. Once again Kyiv vs Kiev is a part of that ugly past. I can promise you that all of our sites will one day be Kyiv and that the term will be the one used wide-spread and worldwide. But we need to do this one step at a time and wikipedia is a big part of this. This has to be corrected and the general population will then become familiar and accept the new word, it's very easy to spell and pronounce. I kindly ask that you respect our history, our past and what is currently happening in eastern Ukraine. it's no accident that where the Russian population - 15% of Ukraine's population. lives and breathes, there is a war. the same way Stalin killed my forefathers and replaced them with Russians from Russia, we are battling for the existence of our own unique identity. Kyiv is and will always be the proper transliterated version of our capital. there is no argument today that can supercede that. Thank you kindly, Simon Kostenko ---- On сб, 28 бер 2015 11:27:35 +0200 Florian Weimer<fw(a)deneb.enyo.de> wrote ---- * Simon: >> Many government web sites in the Ukraine still use the “Kiev” >> transliteration > For example? “While the Obama administration has publicly acknowledged it is considering supplying Kiev with arms, backed by hardline EU countries like Poland and Lithuania, German Chancellor Angela Merkel has vehemently opposed the move.” <http://www.kmu.gov.ua/control/en/publish/article?art_id=248025420>

11 10

Database and Code compatibility
by Thomas v. Karlsson April 28, 2015

April 28, 2015

Hi, I would like to know the compatibility constraints between the code and the datebase. Is the code forward and backward compatible with the database binaries? I.e can code read older and newer version of database binaries? Or do the code and the database need to be version sync with each other? Thanks Thomas Karlsson

2 1

ASEAN time shelved for now
by Paul Eggert April 27, 2015

April 27, 2015

ASEAN foreign ministers decided yesterday to put the proposal for a common (UTC+8) time zone "in abeyance", i.e., they'll keep looking at it but it's not going to happen any time soon if ever. Agence France-Presse. Too early for common SE Asia time zone. The Sun (Malaysia) 2015-04-26. http://www.thesundaily.my/news/1396105

1 0

Re: [tz] Belarus is listed in MSK timezone
by Matt Johnson April 25, 2015

April 25, 2015

Yes , but when you say "identifier", I think "Europe/Minsk", not "MSK". Do you consider both to be identifying a rule set? ________________________________ From: Lester Caine<mailto:lester@lsces.co.uk> Sent: ‎4/‎3/‎2015 1:15 AM To: tz(a)iana.org<mailto:tz@iana.org> Subject: Re: [tz] Belarus is listed in MSK timezone On 03/04/15 08:22, Matt Johnson wrote: > How can we even hope to achieve time zone abbreviations that follow what > people use on the ground if some places don't use abbreviations at all? While on one hand the bulk of the current rules are well established, some edge cases simply need a unique identifier for the internal rule set being referred to. I'll repeat what I keep saying ... the local 'conversion' of the descriptions is not something that the TZ database has any control over, and in some cases the internal identifiers are simply that ... internal ... only requiring that they uniquely identify a particular rule set. -- Lester Caine - G8HFL ----------------------------- Contact - http://lsces.co.uk/wiki/?page=contact L.S.Caine Electronic Services - http://lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk Rainbow Digital Media - http://rainbowdigitalmedia.co.uk

11 33

Micronations?
by Matt Johnson April 24, 2015

April 24, 2015

I read an article today about a newly formed country:http://www.businessinsider.com/liberland-this-newly-declared-microc… Which got me thinking - What is the rule/guideline for tzdb treatment of micronations? According to it's wikipedia article (http://en.wikipedia.org/wiki/Liberland) it's currently following CET/CEST. It's on the Croatia/Serbia border, so if modeled in the TZDB it would probably be something simple like: Link Europe/Belgrade Europe/Liberpolis # Liberland Now, I'm not suggesting we add this now - but just wondering at what point we would recognize a micronation? If they were granted an ISO3166 country code, would they show up in zone.tab/zone1970.tab? If they changed their time zone or DST rules, should they get their own zone entry? What if they were never recongnized broadly, but still changed their time conventions? Do we have a policy on this? For that matter - is there a list of general policies documented anywhere?

2 2