July 2015 - tz - lists.iana.org

[PROPOSED PATCH] Don't warn about abbreviations like '-05'
by Paul Eggert July 15, 2015

July 15, 2015

* NEWS, zic.8: Document this. * zic.c (newabbr): Allow abbreviations that (when quoted) conform to POSIX.1-2001 or later. --- NEWS | 4 ++++ zic.8 | 2 ++ zic.c | 20 ++++---------------- 3 files changed, 10 insertions(+), 16 deletions(-) diff --git a/NEWS b/NEWS index 041983c..498e77b 100644 --- a/NEWS +++ b/NEWS @@ -19,6 +19,10 @@ Unreleased, experimental changes installed data files for Europe/Simferopol and Europe/Tallinn. It does not affect timestamps. (Thanks to Howard Hinnant.) + Changes affecting code + + zic no longer warns about valid time zone abbreviations like '-05'. + Release 2015e - 2015-06-13 10:56:02 -0700 diff --git a/zic.8 b/zic.8 index cf78ae3..968cc6f 100644 --- a/zic.8 +++ b/zic.8 @@ -376,6 +376,8 @@ of the time zone abbreviation goes. Alternately, a slash (/) separates standard and daylight abbreviations. +To conform to POSIX, a time zone abbreviation should contain only +alphanumeric ASCII characters, "+" and "\*-". .TP .B UNTILYEAR [MONTH [DAY [TIME]]] The time at which the UT offset or the rule(s) change for a location. diff --git a/zic.c b/zic.c index f51fc48..6fac4e3 100644 --- a/zic.c +++ b/zic.c @@ -2893,27 +2893,15 @@ newabbr(const char *const string) register const char * cp; const char * mp; - /* - ** Want one to ZIC_MAX_ABBR_LEN_WO_WARN alphabetics - ** optionally followed by a + or - and a number from 1 to 14. - */ cp = string; mp = NULL; - while (is_alpha(*cp)) + while (is_alpha(*cp) || ('0' <= *cp && *cp <= '9') + || *cp == '-' || *cp == '+') ++cp; - if (cp - string == 0) -mp = _("time zone abbreviation lacks alphabetic at start"); if (noise && cp - string < 3) -mp = _("time zone abbreviation has fewer than 3 alphabetics"); + mp = _("time zone abbreviation has fewer than 3 characters"); if (cp - string > ZIC_MAX_ABBR_LEN_WO_WARN) -mp = _("time zone abbreviation has too many alphabetics"); - if (mp == NULL && (*cp == '+' || *cp == '-')) { - ++cp; - if (is_digit(*cp)) - if (*cp++ == '1' && - *cp >= '0' && *cp <= '4') - ++cp; - } + mp = _("time zone abbreviation has too many characters"); if (*cp != '\0') mp = _("time zone abbreviation differs from POSIX standard"); if (mp != NULL) -- 2.1.0

1 0

Re: [tz] Uruguay out of DST
by Pablo Camargo July 13, 2015

July 13, 2015

Hello! Just to confirm: "Uruguay out of DST" is official. Next source in Spanish (presidential decree). >>> http://archivo.presidencia.gub.uy/sci/decretos/2015/06/cons_min_201.pdf Context: >>> http://presidencia.gub.uy/normativa/decretos/decretos-06-2015 Media coverage of the news (text) had better coverage, but the official communication was there (pdf). So we are looking forward for a future update of tz. Thanks! P.Camargo.

3 2

Unnecessary faux transition in Atlantic/Canary 1980 Sep/28
by Howard Hinnant July 13, 2015

July 13, 2015

Hi, I wouldn’t call this a bug, but a potential database inefficiency. I’m working on a TZ parser and using it to explore the timezone transitions as specified by the timezone database. I’m looking at the Atlantic/Canary transition on 1980 Sep 28 0:00s. At this time the timezone transitions from a permanent saving of 1:00 and abbreviation of WEST to a rule based savings specified by EU: 1980-09-27 23:59:59u = 1980-09-28 00:59:59 WEST // as specified by 0:00 1:00 WEST 1980-09-28 00:00:00u = 1980-09-28 01:00:00 WEST // as specified by 0:00 EU WE%sT I.e. there is no change in offset, savings, or abbreviation. And then an hour later EU specifies a savings and abbreviation change: 1980-09-28 00:59:59u = 1980-09-28 01:59:59 WEST 1980-09-28 01:00:00u = 1980-09-28 01:00:00 WET My observation is that this is a lot of transitions for one night. Would it not be better to delay the transition from "0:00 1:00 WEST” to "0:00 EU WE%sT” by one hour, and thus have only one transition instead of two? Here is a change that does so: diff --git a/europe b/europe index c64c41b..630c234 100644 --- a/europe +++ b/europe @@ -2922,7 +2922,7 @@ Zone Africa/Ceuta -0:21:16 - LMT 1901 Zone Atlantic/Canary -1:01:36 - LMT 1922 Mar # Las Palmas de Gran C. -1:00 - CANT 1946 Sep 30 1:00 # Canaries T 0:00 - WET 1980 Apr 6 0:00s - 0:00 1:00 WEST 1980 Sep 28 0:00s + 0:00 1:00 WEST 1980 Sep 28 1:00s 0:00 EU WE%sT # IATA SSIM (1996-09) says the Canaries switch at 2:00u, not 1:00u. # Ignore this for now, as the Canaries are part of the EU. Howard

3 4

Europe/Chisinau Timezone
by Roman Tudos July 11, 2015

July 11, 2015

Please be informed that according Moldavian Law dst start on last last Sunday of March end on last sunday of October at 02:00 to 03:00 and at 03:00 to 02:00 respectively 2015Sun, 29 Mar, 02:00EET <http://www.timeanddate.com/time/zones/eet> → EEST <http://www.timeanddate.com/time/zones/eest>+1 hour (DST start)UTC+3h Sun, 25 Oct, 03:00EEST <http://www.timeanddate.com/time/zones/eest> → EET <http://www.timeanddate.com/time/zones/eet>-1 hour (DST end)UTC+2h2016Sun, 27 Mar, 02:00EET <http://www.timeanddate.com/time/zones/eet> → EEST <http://www.timeanddate.com/time/zones/eest>+1 hour (DST start)UTC+3h Sun, 30 Oct, 03:00EEST <http://www.timeanddate.com/time/zones/eest> → EET <http://www.timeanddate.com/time/zones/eet>-1 hour (DST end)UTC+2h2017Sun, 26 Mar, 02:00EET <http://www.timeanddate.com/time/zones/eet> → EEST <http://www.timeanddate.com/time/zones/eest>+1 hour (DST start)UTC+3h Sun, 29 Oct, 03:00EEST <http://www.timeanddate.com/time/zones/eest> → EET <http://www.timeanddate.com/time/zones/eet>-1 hour (DST end)UTC+2h2018Sun, 25 Mar, 02:00EET <http://www.timeanddate.com/time/zones/eet> → EEST <http://www.timeanddate.com/time/zones/eest>+1 hour (DST start)UTC+3h Sun, 28 Oct, 03:00EEST <http://www.timeanddate.com/time/zones/eest> → EET <http://www.timeanddate.com/time/zones/eet>-1 hour (DST end)UTC+2h Please take consideration for changes in tzdata PS. Sorry for my english -- Vita sine libertate, nihil

3 2

Discrepancies in time zone data interpretation at standard offset changes
by Jon Skeet July 11, 2015

July 11, 2015

Heads up for Stephen Colebourne: this post highlights a discrepancy between Joda Time and tzdump, so you may want to read carefully :) This is in relation to my earlier message about the text format. My confusion here is the reason I'm anxious to see canonical data :) Currently, both Joda Time and Noda Time have some interesting code when working out the transitions for a time zone which checks whether the later transition occurs at the same *local* time as the earlier transition, and if so extends the earlier transition to consume the later one. I've worked out that this is basically to handle an oddity that sometimes occurs when standard offsets change. One example of a zone in which this happens is America/Juneau. Here are the zone lines from 2015e, and I've highlighted the ones we're immediately concerned with: Zone America/Juneau 15:02:19 - LMT 1867 Oct 18 -8:57:41 - LMT 1900 Aug 20 12:00 -8:00 - PST 1942 -8:00 US P%sT 1946 -8:00 - PST 1969 -8:00 US P%sT 1980 Apr 27 2:00 -9:00 US Y%sT 1980 Oct 26 2:00 * -8:00 US P%sT 1983 Oct 30 2:00* * -9:00 US Y%sT 1983 Nov 30* -9:00 US AK%sT The US rules in force at the time are: Rule US 1967 2006 - Oct lastSun 2:00 0 S Rule US 1976 1986 - Apr lastSun 2:00 1:00 D So, the first bolded zone line comes to an end at the instant of the transition into standard time, while standard time is -8 (so a wall offset of -7). I assume this transition should *not* be included in the eventual set of transitions (i.e. the bound given is exclusive). This would occur at 1983-10-30T09:00Z. Now, in the second bolded zone line, the standard offset is -9 instead, so the transition into daylight saving time would occur at 1983-10-30T10:00Z. So looking at the rules in a naive way, residents of Juneau would have to change their watches twice on October 30th 1983. At 2am they'd put their watches back an hour to account for the change in standard time (but still be in daylight saving time)... and then when it next hit 2am they'd put their watches back *another* hour to account for the transition into standard time. Now, I'm pretty sure that's not what's intended, and indeed zdump shows just a single transition setting local time back two hours at 1983-10-30T09:00Z: America/Juneau Sun Oct 30 08:59:59 1983 UTC = Sun Oct 30 01:59:59 1983 PDT isdst=1 America/Juneau Sun Oct 30 09:00:00 1983 UTC = Sun Oct 30 00:00:00 1983 YST isdst=0 ... whereas Noda Time (and, I've just checked, Joda Time) have a single transition at 1983-10-30T10:00Z instead. Is it documented somewhere what should happen in this case? (As a side question, is there a single canonical place documenting the time zone data format? I've found various sources over the years, but it would be nice to have somewhere canonical - ideally either within each release or on the IANA home page. The Theory file gives a lot of interesting more abstract information, but a single place saying "Here is what each file in the release means, with details of its format" would be very welcome. Apologies if it already exists and I've just missed it...) Jon

2 1

UY Timezone DST changed since June 2015
by Nicolas Antoniello July 9, 2015

July 9, 2015

Hi folks, Just to request a Timezone DB update as Past June 2015, Uruguay (UY) eliminated the DST Timezone change (now it's UTC-3 all year). So for Montevideo (capital city) and all rest of Uruguayan cities now is all year UTC-3. Thanks in advance, Nicolas

1 0

Greetings from Mongolia
by amgalan tsogtgerel July 4, 2015

July 4, 2015

Dear Paul Eggert, Greetings from Mongolia. I am writing this letter on behalf of the Communications Regulatory Commission of Mongolia. The Mongolian Government has approved the Resolution ? 82, dated 09 March 2015, to use Daylight Saving Time (DST) every year from last week of March until last week of September from 2015. According to the Resolution, the clocks in Mongolia has set forward one hour at 2 : 00 (2 am) local time. Unfortunately, some of system, service and software which are widely using in Mongolia have not updated their time zone. Regarding this issue, the CRC has sent you official letter dated 15th June 2015 to you for your support on above mentioned issue and we have not received any response from you yet. Here I attached the copy of letter. Thank you for your understanding. I look forward hearing from you soon. BR, Amgalan Ts. (Ms) Foreign Relation Officer, Legal, Information and Administration Dept, CRC of Mongolia. mobile: 976 91112268 phone: 976 11 304258,304257 fax:976 11 327720 e-mail: amgalants(a)crc.gov.mn<mailto:amgalants@crc.gov.mn>

7 8

[PROPOSED_PATCH] Moldova DST transitions were off by an hour
by Paul Eggert July 2, 2015

July 2, 2015

* NEWS: Moldova starts and ends DST at 00:00 UTC, not at 01:00 UTC. (Thanks to Roman Tudos.) * europe (Moldova): New rule. (Europe/Chisinau): Use it. --- NEWS | 5 +++++ europe | 14 +++++++++++++- 2 files changed, 18 insertions(+), 1 deletion(-) diff --git a/NEWS b/NEWS index 156da23..f0fedbd 100644 --- a/NEWS +++ b/NEWS @@ -6,6 +6,11 @@ Unreleased, experimental changes Uruguay will stop observing DST. (Thanks to Steffen Thorsen.) + Changes affecting past and future time stamps + + Moldova starts and ends DST at 00:00 UTC, not at 01:00 UTC. + (Thanks to Roman Tudos.) + Changes affecting installed data files Data entries have been simplified for Atlantic/Canary, Europe/Simferopol, diff --git a/europe b/europe index a5e95bb..7cbf1f8 100644 --- a/europe +++ b/europe @@ -1763,6 +1763,18 @@ Zone Europe/Malta 0:58:04 - LMT 1893 Nov 2 0:00s # Valletta # News from Moldova (in russian): # http://ru.publika.md/link_317061.html +# From Roman Tudos (2015-07-02): +# http://lex.justice.md/index.php?action=view&view=doc&lang=1&id=355077 +# From Paul Eggert (2015-07-01): +# The abovementioned official link to IGO1445-868/2014 states that +# 2014-10-26's fallback transition occurred at 03:00 local time. Also, +# http://www.trm.md/en/social/la-30-martie-vom-trece-la-ora-de-vara +# says the 2014-03-30 spring-forward transition was at 02:00 local time. +# Guess that since 1997 Moldova has switched one hour before the EU. + +# Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S +Rule Moldova 1997 max - Mar lastSun 2:00 1:00 S +Rule Moldova 1997 max - Oct lastSun 3:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Chisinau 1:55:20 - LMT 1880 @@ -1777,7 +1789,7 @@ Zone Europe/Chisinau 1:55:20 - LMT 1880 2:00 Russia EE%sT 1992 2:00 E-Eur EE%sT 1997 # See Romania commentary for the guessed 1997 transition to EU rules. - 2:00 EU EE%sT + 2:00 Moldova EE%sT # Monaco # Shanks & Pottenger give 0:09:20 for Paris Mean Time; go with Howse's -- 2.1.0

1 0