July 2014 - tz - lists.iana.org

Proposal - territorial coverage of an IANA zone - define, document, enforce
by Tobias Conradi July 10, 2014

July 10, 2014

Proposal 1) Define what territory an IANA zone covers 2) Include the definition in the documentation 3) Enforce the definition If there would be a definition that territories that use different abbreviations shall have different zones, then the merger On Thu, Jul 10, 2014 at 8:41 PM, Paul Eggert <eggert(a)cs.ucla.edu> wrote: > Alan Barrett wrote: >> To the best of my knowledge, most other African countries that share the >> same UTC offset do not use the abbreviation "SAST" > Thanks for catching this; this was indeed an error in the merge, would have violated 3). Is it really true, that starting 2014-07-10 IANA zones are created based on acronym observation? Also "coincidence" as in On Thu, Jul 10, 2014 at 8:39 PM, Paul Eggert <eggert(a)cs.ucla.edu> wrote: > This is a good point, and in some cases in hindsight I went too far in > merging zones that were coincidentally the same would need definition, if one really wants to base territorial extension of IANA zones on such a vaguely defined concept which can lead to decision that may look arbitrary. And arbitrary seems to be the other rule: > This is not a question about optimizing the implementation; it's a question > of having the tz data reflect our knowledge as accurately as the current > format allows. The current format allows to have at least one zone per post-1970 ISO 3166 country and having this would allow to more accurately "reflect our knowledge", namely for abbreviations and for laws. Laws are the main source for observation of a specific standard time in any country. So one could think the territory covered by an IANA zone would at least be a subset of the territory of exactly one jurisdiction named a country in ISO 3166. If acronym observation and "coincidence" are the basis of zoning, I propose to include that in the documentation. -- Tobias Conradi Rheinsberger Str. 18 10115 Berlin Germany http://tobiasconradi.com/

1 0

No leap second on 2014-12-31.
by Tim Parenti July 9, 2014

July 9, 2014

Per IERS Bulletin C48 (2014-07-07), no leap second will be observed on 2014-12-31. This patch updates leap-seconds.list from NIST. -- Tim Parenti

2 1

Daylight saving time in Egypt
by newsgroups＠engine2.net July 9, 2014

July 9, 2014

Hi everyone, I search through messages and couldn't find if this information was already sent or not. It seems that there will be a change in daylight saving time in Egypt according to NOTAM (notice to airmen) issued by NOAA (below) which was sent to us with this comment: FOR THE KIND ATTENTION OF OUR VALUABLE CUSTOMERS BELOW NOTAM ISSUED TO ANNOUNCE THAT STARTING 31July2014 AT 2200 GMT , CLOCK IN EGYPT WILL BE GMT PLUS 3 HOURS PLEASE RELAY MESSAGE TO THE CONCENED PARTIES NOTAM content: A0237/14 NOTAMN Q) HECC/QXXXX/IV/NBO/A/000/999/2721N03009E005 A) HECC B) 1407312200 C) 1409252100 E) SUMMER TIME (UTC+3 HOURS) WILL BE STARTED AS ITEM B. CREATED: 02 Jul 2014 13:28:00 SOURCE: HECAYNYX Source: https://www.notams.faa.gov/ Best regards, Michal Konvalinka engine2.net

2 1

Precise meaning of FROM and TO in a rule
by Jon Skeet July 9, 2014

July 9, 2014

Sorry to be pedantic again, but I'm trying to get my head round some fiddly code, and I've come across an interesting bit of ambiguity. FROM and TO are described <http://www.ietf.org/timezones/code/zic.8.txt> like this: FROM Gives the first year in which the rule applies. Any integer > year can be supplied; the Gregorian calendar is assumed. The > word minimum (or an abbreviation) means the minimum year > representable as an integer. The word maximum (or an > abbreviation) means the maximum year representable as an > integer. Rules can describe times that are not representable > as time values, with the unrepresentable times ignored; this > allows rules to be portable among hosts with differing time > value types. TO Gives the final year in which the rule applies. In addition to > minimum and maximum (as above), the word only (or an > abbreviation) may be used to repeat the value of the FROM > field. It's not clear whether that "year" is: 1. The year in UTC at the transition 2. The year in the local time before the transition 3. The year in the local time after the transition 4. The year in the same frame of reference as the "AT" part Option 1 seems unlikely. Options 2 and 3 seem likely to be equivalent in all realistic time zones - it would be odd for a time zone to add an hour of DST at 11.30pm on December 31st, for example... and even odder for it to *subtract* an hour of DST at 00.30am on January 1st. Option 4 is tricky. In some ways it feels natural - if you're going to use one frame of reference for a time, why not do it for the date as well? On the other hand, it means that a "TO" value of (say) 2001 where the transition is at 2am UTC on January 1st in a time zone with a standard time of UTC+8 would actually have its last transition in 2000 local time, assuming I've got my maths right. Can I assume that one of option 2 or option 3 is intended, and that no sensible time zone will ever make those two options behave differently? I've tried reading the C source code, but given the subtleties involved, I'd rather trust a natural language description. If we can come to a conclusion about this, I'd like to propose that we amend the text to be unambiguous, too. Jon

5 9

Re: [tz] LMT in Moscow before 1919, Kilometre Zero point
by Paul Eggert July 9, 2014

July 9, 2014

Thanks for those corrections; that area had been using unreliable data from Shanks & Pottenger. Your email prompted me to dust off my copy of Milne and fix similar problems in some other parts of Russia, and I installed the attached patch to the experimental version of the tz database on Github; it should reflect your comments.

1 1

Fixes for minor oversights re: Russia changes on 2014-10-26.
by Tim Parenti July 8, 2014

July 8, 2014

There were a few lingering oversights in the patch set distributed earlier; see attached. -- Tim Parenti

2 1

[PATCH1/1] Propose new zone for Crozet Islands
by Antoine Leca July 8, 2014

July 8, 2014

Crozet Islands have a year-round scientific base (Alfred-Faure) since 1964. Also corrected the geographic coordinates. Noticed by Tobias Conradi <http://mm.icann.org/pipermail/tz/2012-May/017804.html> --- antarctica | 8 +++++++- zone.tab | 3 ++- 2 files changed, 9 insertions(+), 2 deletions(-) diff --git a/antarctica b/antarctica index 9bf2494..7190413 100644 --- a/antarctica +++ b/antarctica @@ -169,7 +169,6 @@ Zone Antarctica/Mawson 0 - zzz 1954 Feb 13 # French Southern Territories with year-round inhabitants # # Martin-de-Vivies Base, Amsterdam Island, -374105+0773155, since 1950 -# Alfred-Faure Base, Crozet Islands, -462551+0515152, since 1964 # Port-aux-Francais, Kerguelen Islands, -492110+0701303, since 1951; # whaling & sealing station operated 1908/1914, 1920/1929, and 1951/1956 # @@ -179,6 +178,13 @@ Zone Antarctica/Mawson 0 - zzz 1954 Feb 13 # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Indian/Kerguelen 0 - zzz 1950 # Port-aux-Francais 5:00 - TFT # ISO code TF Time + +# Alfred-Faure Base, Crozet Islands, -462551+0515125, since 1964 +# sealing & whaling stations operated variously 1802/1911+ +# Zone NAME GMTOFF RULES FORMAT [UNTIL] +Zone Indian/Alfred-Faure 0 - zzz 1963 + 4:00 - AFT # Alfred-Faure Time + # # year-round base in the main continent # Dumont-d'Urville, Ile des Petrels, -6640+14001, since 1956-11 diff --git a/zone.tab b/zone.tab index 6b98520..0f34698 100644 --- a/zone.tab +++ b/zone.tab @@ -373,7 +373,8 @@ SY +3330+03618 Asia/Damascus SZ -2618+03106 Africa/Mbabane TC +2128-07108 America/Grand_Turk TD +1207+01503 Africa/Ndjamena -TF -492110+0701303 Indian/Kerguelen +TF -492110+0701303 Indian/Kerguelen most locations +TF -462551+0515125 Indian/Alfred-Faure Crozet Islands TG +0608+00113 Africa/Lome TH +1345+10031 Asia/Bangkok TJ +3835+06848 Asia/Dushanbe -- 1.8.0.msysgit.0

2 1

[PATCH] * australasia (Pacific/Apia, WS): Move DST data from Zone to Rule lines.
by Paul Eggert July 8, 2014

July 8, 2014

This doesn't change the output, but is shorter and easier to follow. Trim and adjust commentary a bit. --- australasia | 31 +++++++++++-------------------- 1 file changed, 11 insertions(+), 20 deletions(-) diff --git a/australasia b/australasia index 1fd7cb1..605d8dd 100644 --- a/australasia +++ b/australasia @@ -533,7 +533,7 @@ Zone Pacific/Pago_Pago 12:37:12 - LMT 1879 Jul 5 -11:00 - BST 1983 Nov 30 # B=Bering -11:00 - SST # S=Samoa -# Samoa +# Samoa (formerly and also known as Western Samoa) # From Steffen Thorsen (2009-10-16): # We have been in contact with the government of Samoa again, and received @@ -592,35 +592,26 @@ Zone Pacific/Pago_Pago 12:37:12 - LMT 1879 Jul 5 # Thursday 29th December 2011 23:59:59 Hours # Saturday 31st December 2011 00:00:00 Hours # -# Clarification by Tim Parenti (2012-01-03): -# Although Samoa has used Daylight Saving Time in the 2010-2011 and 2011-2012 -# seasons, there is not yet any indication that this trend will continue on -# a regular basis. For now, we have explicitly listed the transitions below. -# -# From Nicky (2012-09-10): +# From Nicholas Pereira (2012-09-10): # Daylight Saving Time commences on Sunday 30th September 2012 and -# ends on Sunday 7th of April 2013. -# -# Please find link below for more information. +# ends on Sunday 7th of April 2013.... # http://www.mcil.gov.ws/mcil_publications.html # -# That publication also includes dates for Summer of 2013/4 as well -# which give the impression of a pattern in selecting dates for the -# future, so for now, we will guess this will continue. +# From Paul Eggert (2014-07-08): +# That web page currently lists transitions for 2012/3 and 2013/4. +# Assume the pattern instituted in 2012 will continue indefinitely. -# Western Samoa # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S -Rule WS 2012 max - Sep lastSun 3:00 1 D +Rule WS 2010 only - Sep lastSun 0:00 1 D +Rule WS 2011 only - Apr Sat>=1 4:00 0 - +Rule WS 2011 only - Sep lastSat 3:00 1 D Rule WS 2012 max - Apr Sun>=1 4:00 0 - +Rule WS 2012 max - Sep lastSun 3:00 1 D # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Pacific/Apia 12:33:04 - LMT 1879 Jul 5 -11:26:56 - LMT 1911 -11:30 - SAMT 1950 # Samoa Time - -11:00 - WST 2010 Sep 26 - -11:00 1:00 WSDT 2011 Apr 2 4:00 - -11:00 - WST 2011 Sep 24 3:00 - -11:00 1:00 WSDT 2011 Dec 29 24:00 - 13:00 1:00 WSDT 2012 Apr Sun>=1 4:00 + -11:00 WS WS%sT 2011 Dec 29 24:00 13:00 WS WS%sT # Solomon Is -- 1.9.1

1 0

Re: [tz] LMT in Moscow before 1919, Kilometre Zero point
by Vladimir Karpinsky July 8, 2014

July 8, 2014

> Zone Europe/Moscow 2:30:20 - LMT 1880 More correct LMT in Moscow (before Jul 3, 1916) is 2:30:17, that was defined by Moscow Observatory (coordinates: 55°45'29.70", 37°34'05.30") so 37°34'05.30" > 2h30m16.35s = 2:30:17, not 2:30:20. > 2:30 - MMT 1916 Jul 3 # Moscow Mean Time 2:30 is not correct. More correct LMT in Moscow since Jul 3, 1916 is 2:31:01 as a result of new standard. (The info is from the book by Byalokoz E.L. New Counting of Time in Russia since July 1, 1919, p. 18.) The time in St.Petersburg as capital of Russia was defined by Pulkov observatory, near St.Petersburg. In 1916 LMT Moscow was synchronized with LMT St.Petersburg (+30 minutes), (Pulkov observatory coordinates: 59°46'18.70", 30°19'40.70") so 30°19'40.70" > 2h01m18.7s = 2:01:19. LMT Moscow = LMT St.Petersburg + 30m 2:01:19 + 0:30 = 2:31:19, not 2:30. > 2:30:48 Russia %s 1919 Jul 1 2:00 2:30:48 is not correct! Probably a popular mistype. It does not correspond to any reference point in Moscow or St.Petersburg. More correct LMT in Moscow is 2:31:19 before July 1, 1919 or 2:30:17 before July 3, 1916. Since July 1, 1919 at 02:00 - Time Zone system established, Moscow time = GMT+2 (plus 2 hours DST) = GMT+4. > RU +5545+03735 Europe/Moscow Moscow+00 - west Russia 03735 is not correct for Moscow, because official center of Moscow is "Kilometre Zero" point: http://en.wikipedia.org/wiki/Kilometre_zero#Russia http://wikimapia.org/71156/Zero-point-or-Kilometre-Zero The coordinates of Kilometre Zero are 55°45'20.82", 37°37'03.47", so more correct would be 55°45', 037°37', not 037°35'. Sincerely, Vladimir Karpinsky Moscow, Russia ----- Original Message ----- From: <tz-request(a)iana.org> To: <tz(a)iana.org> Sent: Sunday, June 01, 2014 4:14 AM Subject: tz Digest, Vol 33, Issue 1 Sent: Tuesday, July 08, 2014 9:27 AM Subject: tz Digest, Vol 34, Issue 13 Sent: Tuesday, July 08, 2014 9:27 AM Subject: tz Digest, Vol 34, Issue 14

1 0

[PATCH] Pacify 'make check_character_set'.
by Paul Eggert July 8, 2014

July 8, 2014

--- asia | 2 +- europe | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/asia b/asia index 321deae..d396111 100644 --- a/asia +++ b/asia @@ -688,7 +688,7 @@ Zone Asia/Hong_Kong 7:36:42 - LMT 1904 Oct 30 # bulletin in Taiwan for that Ordinance No. 529. It also mentioned that 1am on # Sep 21, 1945 will be 12am on Sep 21. I think this bulletin is much more # official than the one I mentioned in my first mail, because it's from the -# top-level government in Taiwan. If you’re going to quote any resource, this +# top-level government in Taiwan. If you're going to quote any resource, this # would be a good one. # [1] Taiwan Governor-General Gazette, No. 1018, Sep 19, 1945: # http://db2.th.gov.tw/db2/view/viewImg.php?imgcode=0072031018a&num=19&bgn=01… diff --git a/europe b/europe index 8c493f3..9b6a502 100644 --- a/europe +++ b/europe @@ -2336,7 +2336,7 @@ Zone Europe/Samara 3:20:36 - LMT 1919 Jul 1 2:00 # 66 RU-SVE Sverdlovsk Oblast # 72 RU-TYU Tyumen Oblast # 74 RU-CHE Chelyabinsk Oblast -# 86 RU-KHM Khanty–Mansi Autonomous Okrug – Yugra +# 86 RU-KHM Khanty-Mansi Autonomous Okrug - Yugra # 89 RU-YAN Yamalo-Nenets Autonomous Okrug # # Note: Effective 2005-12-01, (59) Perm Oblast and (81) Komi-Permyak -- 1.9.1

1 0