[PROPOSED PATCH 1/4] Prefer +-NN notation for UT-offset time zones in comments.
This does not change any code or data; just comments. --- NEWS | 38 +++++++++++++++++++------------------- Theory | 2 +- africa | 2 +- asia | 51 +++++++++++++++++++++++++-------------------------- australasia | 26 +++++++++++++------------- backzone | 14 +++++++------- europe | 8 +------- localtime.c | 2 +- northamerica | 2 +- private.h | 1 + southamerica | 4 ++-- 11 files changed, 72 insertions(+), 78 deletions(-) diff --git a/NEWS b/NEWS index 4c18e55..b0da284 100644 --- a/NEWS +++ b/NEWS @@ -465,7 +465,7 @@ Release 2015d - 2015-04-24 08:09:46 -0700 Changes affecting past time stamps - America/Whitehorse switched from UTC-9 to UTC-8 on 1967-05-28, not + America/Whitehorse switched from -09 to -08 on 1967-05-28, not 1966-07-01. Also, Yukon's time zone history is documented better. (Thanks to Brian Inglis and Dennis Ferguson.) @@ -499,12 +499,12 @@ Release 2015c - 2015-04-11 08:55:55 -0700 The 1918 transition was September 10, not September 1. - The UTC-4 time observed from 1932 to 1942 is now considered to be + The -04 time observed from 1932 to 1942 is now considered to be standard time, not year-round DST. - Santiago observed DST (UTC-3) from 1946-07-15 through 1946-08-31, + Santiago observed DST (-03) from 1946-07-15 through 1946-08-31, then reverted to standard time, then switched its time zone to - UTC-5 on 1947-04-01. + -05 on 1947-04-01. Assume transitions before 1968 were at 00:00, since we have no data saying otherwise. @@ -633,7 +633,7 @@ Release 2014j - 2014-11-10 17:37:11 -0800 Changes affecting current and future time stamps - Turks & Caicos' switch from US eastern time to UTC-4 year-round + Turks & Caicos' switch from US eastern time to -04 year-round did not occur on 2014-11-02 at 02:00. It's currently scheduled for 2015-11-01 at 02:00. (Thanks to Chris Walton.) @@ -669,7 +669,7 @@ Release 2014i - 2014-10-21 22:04:57 -0700 years will use a similar pattern. A new Zone Pacific/Bougainville, for the part of Papua New Guinea - that plans to switch from UTC+10 to UTC+11 on 2014-12-28 at 02:00. + that plans to switch from +10 to +11 on 2014-12-28 at 02:00. (Thanks to Kiley Walbom for the heads-up.) Changes affecting time zone abbreviations @@ -679,8 +679,8 @@ Release 2014i - 2014-10-21 22:04:57 -0700 to its more-traditional value MSK on 2014-10-26 at 01:00. (Thanks to Alexander Bokovoy for the heads-up about Belarus.) - The new abbreviation IDT stands for the pre-1976 use of UT+8 in - Indochina, to distinguish it better from ICT (UT+7). + The new abbreviation IDT stands for the pre-1976 use of +08 in + Indochina, to distinguish it better from ICT (+07). Changes affecting past time stamps @@ -791,7 +791,7 @@ Release 2014g - 2014-08-28 12:31:23 -0700 Changes affecting future time stamps - Turks & Caicos is switching from US eastern time to UTC-4 year-round, + Turks & Caicos is switching from US eastern time to -04 year-round, modeled as a switch from EST/EDT to AST on 2014-11-02 at 02:00. [As noted in 2014j, this switch was later delayed.] @@ -975,7 +975,7 @@ Release 2014f - 2014-08-05 17:42:36 -0700 This change does not affect UTC offsets, only time zone abbreviations. (Thanks to Rich Tibbett and many others.) - Asia/Novokuznetsk shifts from NOVT to KRAT (remaining on UTC+7) + Asia/Novokuznetsk shifts from NOVT to KRAT (remaining on +07) effective 2014-10-26 at 02:00 local time. The time zone abbreviation for Xinjiang Time (observed in Ürümqi) @@ -1004,8 +1004,8 @@ Release 2014f - 2014-08-05 17:42:36 -0700 zones Asia/Harbin, Asia/Chongqing, and Asia/Kashgar have been removed; backwards-compatibility links still work, albeit with different behaviors for time stamps before May 1980. Asia/Urumqi's - 1980 transition to UTC+8 has been removed, so that it is now at - UTC+6 and not UTC+8. (Thanks to Luther Ma and to Alois Treindl; + 1980 transition to +08 has been removed, so that it is now at + +06 and not +08. (Thanks to Luther Ma and to Alois Treindl; Treindl sent helpful translations of two papers by Guo Qingsheng.) Some zones have been turned into links, when they differed from existing @@ -1035,7 +1035,7 @@ Release 2014f - 2014-08-05 17:42:36 -0700 Europe/Helsinki's 1942 fall-back transition was 10-04 at 01:00, not 10-03 at 00:00. (Thanks to Konstantin Hyppönen.) - Pacific/Pago_Pago has been changed from UTC-11:30 to UTC-11 for the period + Pacific/Pago_Pago has been changed from -11:30 to -11 for the period from 1911 to 1950. Pacific/Chatham has been changed to New Zealand standard time plus @@ -1363,15 +1363,15 @@ Release 2013h - 2013-10-25 15:32:32 -0700 Changes affecting current and future time stamps: - Libya has switched its time zone back to UTC+2 without DST, - instead of UTC+1 with DST. (Thanks to Even Scharning.) + Libya has switched its time zone back to +02 without DST, + instead of +01 with DST. (Thanks to Even Scharning.) Western Sahara (Africa/El_Aaiun) uses Morocco's DST rules. (Thanks to Gwillim Law.) Changes affecting future time stamps: - Acre and (we guess) western Amazonas will switch from UTC-4 to UTC-5 + Acre and (we guess) western Amazonas will switch from -04 to -05 on 2013-11-10. This affects America/Rio_Branco and America/Eirunepe. (Thanks to Steffen Thorsen.) @@ -1458,7 +1458,7 @@ Release 2013f - 2013-09-24 23:37:36 -0700 Tocantins will very likely not observe DST starting this spring. (Thanks to Steffen Thorsen.) - Jordan will likely stay at UTC+3 indefinitely, and will not fall + Jordan will likely stay at +03 indefinitely, and will not fall back this fall. Palestine will fall back at 00:00, not 01:00. (Thanks to Steffen Thorsen.) @@ -1515,7 +1515,7 @@ Release 2013e - 2013-09-19 23:50:04 -0700 Benny Lin.) This affects Asia/Dili, Asia/Jakarta, Asia/Jayapura, Asia/Makassar, and Asia/Pontianak. - Use ART (UTC-3, standard time), rather than WARST (also UTC-3, but + Use ART (-03, standard time), rather than WARST (also UTC-3, but daylight saving time) for San Luis, Argentina since 2009. Changes affecting Godthåb time stamps after 2037 if version mismatch @@ -1972,7 +1972,7 @@ Release 2012f - 2012-09-12 23:17:03 -0700 Release 2012e - 2012-08-02 20:44:55 -0700 - * australasia (Pacific/Fakaofo): Tokelau is UTC+13, not UTC+14. + * australasia (Pacific/Fakaofo): Tokelau is +13, not +14. (Thanks to Steffen Thorsen.) * Use a single version number for both code and data. diff --git a/Theory b/Theory index 60678fe..d8d3882 100644 --- a/Theory +++ b/Theory @@ -323,7 +323,7 @@ Errors in the tz database arise from many sources: * Sometimes historical timekeeping was specified more precisely than what the tz database can handle. For example, from 1909 to - 1937 Netherlands clocks were legally UT+00:19:32.13, but the tz + 1937 Netherlands clocks were legally +00:19:32.13, but the tz database cannot represent the fractional second. * Even when all the timestamp transitions recorded by the tz database diff --git a/africa b/africa index 50f29d5..43c8e23 100644 --- a/africa +++ b/africa @@ -464,7 +464,7 @@ Zone Africa/Monrovia -0:43:08 - LMT 1882 # http://www.libyaherald.com/2013/10/24/correction-no-time-change-tomorrow/ # # From Paul Eggert (2013-10-25): -# For now, assume they're reverting to the pre-2012 rules of permanent UTC+2. +# For now, assume they're reverting to the pre-2012 rules of permanent +02. # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S Rule Libya 1951 only - Oct 14 2:00 1:00 S diff --git a/asia b/asia index ee2c436..a935476 100644 --- a/asia +++ b/asia @@ -380,7 +380,7 @@ Rule PRC 1987 1991 - Apr Sun>=10 0:00 1:00 D # Lewiston (ME) Daily Sun (1939-05-29), p 17, said "Even the time is # different - the occupied districts going by Tokyo time, an hour # ahead of that prevailing in the rest of Shanghai." Guess that the -# Xujiahui Observatory was under French control and stuck with UT+8. +# Xujiahui Observatory was under French control and stuck with +08. # # In earlier versions of this file, China had many separate Zone entries, but # this was based on what were apparently incorrect data in Shanks & Pottenger. @@ -389,26 +389,26 @@ Rule PRC 1987 1991 - Apr Sun>=10 0:00 1:00 D # Proposed in 1918 and theoretically in effect until 1949 (although in practice # mainly observed in coastal areas), the five zones were: # -# Changbai Time ("Long-white Time", Long-white = Heilongjiang area) UT+8.5 +# Changbai Time ("Long-white Time", Long-white = Heilongjiang area) +08:30 # Asia/Harbin (currently a link to Asia/Shanghai) # Heilongjiang (except Mohe county), Jilin # -# Zhongyuan Time ("Central plain Time") UT+8 +# Zhongyuan Time ("Central plain Time") -08 # Asia/Shanghai # most of China # This currently represents most other zones as well, # as apparently these regions have been the same since 1970. # Milne gives 8:05:43.2 for Xujiahui Observatory time; round to nearest. -# Guo says Shanghai switched to UT+8 "from the end of the 19th century". +# Guo says Shanghai switched to +08 "from the end of the 19th century". # -# Long-shu Time (probably due to Long and Shu being two names of that area) UT+7 +# Long-shu Time (probably due to Long and Shu being two names of that area) +07 # Asia/Chongqing (currently a link to Asia/Shanghai) # Guangxi, Guizhou, Hainan, Ningxia, Sichuan, Shaanxi, and Yunnan; # most of Gansu; west Inner Mongolia; west Qinghai; and the Guangdong # counties Deqing, Enping, Kaiping, Luoding, Taishan, Xinxing, # Yangchun, Yangjiang, Yu'nan, and Yunfu. # -# Xin-zang Time ("Xinjiang-Tibet Time") UT+6 +# Xin-zang Time ("Xinjiang-Tibet Time") +06 # Asia/Urumqi # This currently represents Kunlun Time as well, # as apparently the two regions have been the same since 1970. @@ -421,7 +421,7 @@ Rule PRC 1987 1991 - Apr Sun>=10 0:00 1:00 D # Shihezi, Changji, Yanqi, Heshuo, Tuokexun, Tulufan, Shanshan, Hami, # Fukang, Kuitun, Kumukuli, Miquan, Qitai, and Turfan. # -# Kunlun Time UT+5.5 +# Kunlun Time +05:30 # Asia/Kashgar (currently a link to Asia/Urumqi) # West Tibet, including Pulan, Aheqi, Shufu, Shule; # West Xinjiang, including Aksu, Atushi, Yining, Hetian, Cele, Luopu, Nileke, @@ -493,7 +493,7 @@ Rule PRC 1987 1991 - Apr Sun>=10 0:00 1:00 D # having the same time as Beijing. # From Paul Eggert (2014-06-30): -# In the early days of the PRC, Tibet was given its own time zone (UT+6) but +# In the early days of the PRC, Tibet was given its own time zone (+06) but # this was withdrawn in 1959 and never reinstated; see Tubten Khétsun, # Memories of life in Lhasa under Chinese Rule, Columbia U Press, ISBN # 978-0231142861 (2008), translator's introduction by Matthew Akester, p x. @@ -508,12 +508,12 @@ Rule PRC 1987 1991 - Apr Sun>=10 0:00 1:00 D # Republics, the Soviet Union, the Kuomintang, and the People's Republic of # China, and tracking down all these organizations' timekeeping rules would be # quite a trick. Approximate this lost history by a transition from LMT to -# XJT at the start of 1928, the year of accession of the warlord Jin Shuren, +# +06 at the start of 1928, the year of accession of the warlord Jin Shuren, # which happens to be the date given by Shanks & Pottenger (no doubt as a -# guess) as the transition from LMT. Ignore the usage of UT+8 before -# 1986-02-01 under the theory that the transition date to UT+8 is unknown and +# guess) as the transition from LMT. Ignore the usage of +08 before +# 1986-02-01 under the theory that the transition date to +08 is unknown and # that the sort of users who prefer Asia/Urumqi now typically ignored the -# UT+8 mandate back then. +# +08 mandate back then. # Zone NAME GMTOFF RULES FORMAT [UNTIL] # Beijing time, used throughout China; represented by Shanghai. @@ -718,7 +718,7 @@ Zone Asia/Hong_Kong 7:36:42 - LMT 1904 Oct 30 # be found from historical government announcement database. # From Paul Eggert (2014-07-03): -# As per Yu-Cheng Chuang, say that Taiwan was at UT+9 from 1937-10-01 +# As per Yu-Cheng Chuang, say that Taiwan was at +09 from 1937-10-01 # until 1945-09-21 at 01:00, overriding Shanks & Pottenger. # Likewise, use Yu-Cheng Chuang's data for DST in Taiwan. @@ -917,7 +917,7 @@ Zone Asia/Kolkata 5:53:28 - LMT 1880 # Kolkata # These would be the earliest possible times for a change. # Régimes horaires pour le monde entier, by Henri Le Corre, (Éditions # Traditionnelles, 1987, Paris) says that Java and Madura switched -# from JST to UTC+07:30 on 1945-09-23, and gives 1944-09-01 for Jayapura +# from +09 to +07:30 on 1945-09-23, and gives 1944-09-01 for Jayapura # (Hollandia). For now, assume all Indonesian locations other than Jayapura # switched on 1945-09-23. # @@ -930,9 +930,9 @@ Zone Asia/Kolkata 5:53:28 - LMT 1880 # Kolkata # Indonesia, <http://time.kim.lipi.go.id/time-eng.php> (2006-09-29). # The abbreviations are: # -# WIB - UTC+7 - Waktu Indonesia Barat (Indonesia western time) -# WITA - UTC+8 - Waktu Indonesia Tengah (Indonesia central time) -# WIT - UTC+9 - Waktu Indonesia Timur (Indonesia eastern time) +# WIB - +07 - Waktu Indonesia Barat (Indonesia western time) +# WITA - +08 - Waktu Indonesia Tengah (Indonesia central time) +# WIT - +09 - Waktu Indonesia Timur (Indonesia eastern time) # # Zone NAME GMTOFF RULES FORMAT [UNTIL] # Java, Sumatra @@ -1864,25 +1864,24 @@ Rule ROK 1957 1960 - Sep Sun>=18 0:00 0 S Rule ROK 1987 1988 - May Sun>=8 2:00 1:00 D Rule ROK 1987 1988 - Oct Sun>=8 3:00 0 S -# From Paul Eggert (2014-10-30): +# From Paul Eggert (2016-08-23): # The Korean Wikipedia entry gives the following sources for UT offsets: # -# 1908: Official Journal Article No. 3994 (Edict No. 5) +# 1908: Official Journal Article No. 3994 (decree No. 5) # 1912: Governor-General of Korea Official Gazette Issue No. 367 # (Announcement No. 338) # 1954: Presidential Decree No. 876 (1954-03-17) # 1961: Law No. 676 (1961-08-07) -# 1987: Law No. 3919 (1986-12-31) # -# The Wikipedia entry also has confusing information about a change -# to UT+9 in April 1910, but then what would be the point of the later change -# to UT+9 on 1912-01-01? Omit the 1910 change for now. +# (Another source "1987: Law No. 3919 (1986-12-31)" was in the 2014-10-30 +# edition of the Korean Wikipedia entry.) # # I guessed that time zone abbreviations through 1945 followed the same # rules as discussed under Taiwan, with nominal switches from JST to KST # when the respective cities were taken over by the Allies after WWII. # -# For Pyongyang we have no information; guess no changes since World War II. +# For Pyongyang, guess no changes from World War II until 2015, as we +# have no information otherwise. # From Steffen Thorsen (2015-08-07): # According to many news sources, North Korea is going to change to @@ -2042,7 +2041,7 @@ Zone Indian/Maldives 4:54:00 - LMT 1880 # Male # Bill Bonnet (2005-05-19) reports that the US Embassy in Ulaanbaatar says # there is only one time zone and that DST is observed, citing Microsoft # Windows XP as the source. Risto Nykänen (2005-05-16) reports that -# travelmongolia.org says there are two time zones (UTC+7, UTC+8) with no DST. +# travelmongolia.org says there are two time zones (+07, +08) with no DST. # Oscar van Vlijmen (2005-05-20) reports that the Mongolian Embassy in # Washington, DC says there are two time zones, with DST observed. # He also found @@ -2678,7 +2677,7 @@ Link Asia/Qatar Asia/Bahrain # earlier date. # # Shanks & Pottenger also state that until 1968-05-01 Saudi Arabia had two -# time zones; the other zone, at UTC+4, was in the far eastern part of +# time zones; the other zone, at +04, was in the far eastern part of # the country. Ignore this, as it's before our 1970 cutoff. # # Zone NAME GMTOFF RULES FORMAT [UNTIL] diff --git a/australasia b/australasia index 0b33f67..fe77d07 100644 --- a/australasia +++ b/australasia @@ -545,7 +545,7 @@ Zone Pacific/Port_Moresby 9:48:40 - LMT 1880 # Base the Bougainville entry on the Arawa-Kieta region, which appears to have # the most people even though it was devastated in the Bougainville Civil War. # -# Although Shanks gives 1942-03-15 / 1943-11-01 for JST, these dates +# Although Shanks gives 1942-03-15 / 1943-11-01 for +09, these dates # are apparently rough guesswork from the starts of military campaigns. # The World War II entries below are instead based on Arawa-Kieta. # The Japanese occupied Kieta in July 1942, @@ -553,8 +553,8 @@ Zone Pacific/Port_Moresby 9:48:40 - LMT 1880 # http://pwencycl.kgbudge.com/B/o/Bougainville.htm # and seem to have controlled it until their 1945-08-21 surrender. # -# The Autonomous Region of Bougainville plans to switch from UTC+10 to UTC+11 -# on 2014-12-28 at 02:00. They call UTC+11 "Bougainville Standard Time"; +# The Autonomous Region of Bougainville switched from +10 to +11 +# on 2014-12-28 at 02:00. They call +11 "Bougainville Standard Time"; # abbreviate this as BST. See: # http://www.bougainville24.com/bougainville-issues/bougainville-gets-own-time... # @@ -620,7 +620,7 @@ Link Pacific/Pago_Pago Pacific/Midway # in US minor outlying islands # From Paul Eggert (2014-06-27): # The International Date Line Act 2011 # http://www.parliament.gov.ws/images/ACTS/International_Date_Line_Act__2011_-... -# changed Samoa from UTC-11 to UTC+13, effective "12 o'clock midnight, on +# changed Samoa from -11 to +13, effective "12 o'clock midnight, on # Thursday 29th December 2011". The International Date Line was adjusted # accordingly. @@ -715,7 +715,7 @@ Zone Pacific/Funafuti 11:56:52 - LMT 1901 # 1886-1891; Baker was similar but exact dates are not known. # Inhabited by civilians 1935-1942; U.S. military bases 1943-1944; # uninhabited thereafter. -# Howland observed Hawaii Standard Time (UT-10:30) in 1937; +# Howland observed Hawaii Standard Time (-10:30) in 1937; # see page 206 of Elgen M. Long and Marie K. Long, # Amelia Earhart: the Mystery Solved, Simon & Schuster (2000). # So most likely Howland and Baker observed Hawaii Time from 1935 @@ -1473,7 +1473,7 @@ Zone Pacific/Wallis 12:15:20 - LMT 1901 # Zealand time. I understand that is the time they keep locally, anyhow." # For now, assume this practice goes back to the introduction of standard time # in New Zealand, as this would make Chatham Islands time almost exactly match -# LMT back when New Zealand was at UTC+11:30; also, assume Chatham Islands did +# LMT back when New Zealand was at +11:30; also, assume Chatham Islands did # not observe New Zealand's prewar DST. ############################################################################### @@ -1529,7 +1529,7 @@ Zone Pacific/Wallis 12:15:20 - LMT 1901 # For now, we assume the Ladrones switched at the same time as the Philippines; # see Asia/Manila. -# US Public Law 106-564 (2000-12-23) made UTC+10 the official standard time, +# US Public Law 106-564 (2000-12-23) made +10 the official standard time, # under the name "Chamorro Standard Time". There is no official abbreviation, # but Congressman Robert A. Underwood, author of the bill that became law, # wrote in a press release (2000-12-27) that he will seek the use of "ChST". @@ -1541,15 +1541,15 @@ Zone Pacific/Wallis 12:15:20 - LMT 1901 # "I am certain, having lived there for the past decade, that 'Truk' # (now properly known as Chuuk) ... is in the time zone GMT+10." # -# Shanks & Pottenger write that Truk switched from UTC+10 to UTC+11 +# Shanks & Pottenger write that Truk switched from +10 to +11 # on 1978-10-01; ignore this for now. # From Paul Eggert (1999-10-29): # The Federated States of Micronesia Visitors Board writes in # The Federated States of Micronesia - Visitor Information (1999-01-26) # http://www.fsmgov.org/info/clocks.html -# that Truk and Yap are UTC+10, and Ponape and Kosrae are UTC+11. -# We don't know when Kosrae switched from UTC+12; assume January 1 for now. +# that Truk and Yap are +10, and Ponape and Kosrae are +11. +# We don't know when Kosrae switched from +12; assume January 1 for now. # Midway @@ -1615,11 +1615,11 @@ Zone Pacific/Wallis 12:15:20 - LMT 1901 # ordaining - by a masterpiece of diplomatic flattery - that # the Fourth of July should be celebrated twice in that year." -# Although Shanks & Pottenger says they both switched to UTC-11:30 -# in 1911, and to UTC-11 in 1950. many earlier sources give UTC-11 +# Although Shanks & Pottenger says they both switched to -11:30 +# in 1911, and to -11 in 1950. many earlier sources give -11 # for American Samoa, e.g., the US National Bureau of Standards # circular "Standard Time Throughout the World", 1932. -# Assume American Samoa switched to UTC-11 in 1911, not 1950, +# Assume American Samoa switched to -11 in 1911, not 1950, # and that after 1950 they agreed until (western) Samoa skipped a # day in 2011. Assume also that the Samoas follow the US and New # Zealand's "ST"/"DT" style of daylight-saving abbreviations. diff --git a/backzone b/backzone index 13dc8d4..27a5472 100644 --- a/backzone +++ b/backzone @@ -194,9 +194,9 @@ Zone Africa/Lusaka 1:53:08 - LMT 1903 Mar # Equatorial Guinea # -# Although Shanks says that Malabo switched from UTC to UTC+1 on 1963-12-15, +# Although Shanks says that Malabo switched from +00 to +01 on 1963-12-15, # a Google Books search says that London Calling, Issues 432-465 (1948), p 19, -# says that Spanish Guinea was at GMT+1 back then. The Shanks data entries +# says that Spanish Guinea was at +01 back then. The Shanks data entries # are most likely wrong, but we have nothing better; use them here for now. # Zone Africa/Malabo 0:35:08 - LMT 1912 @@ -479,14 +479,14 @@ Zone Asia/Muscat 3:54:24 - LMT 1920 # From Paul Eggert (2014-08-11), after a heads-up from Stephen Colebourne: # According to a Portuguese decree (1911-05-26) # http://dre.pt/pdf1sdip/1911/05/12500/23132313.pdf -# Portuguese India switched to GMT+5 on 1912-01-01. +# Portuguese India switched to +05 on 1912-01-01. #Zone Asia/Panaji [not enough info to complete] # Cambodia # From Paul Eggert (2014-10-11): # See Asia/Ho_Chi_Minh for the source for most of this data. Also, guess -# (1) Cambodia reverted to UT+7 on 1945-09-02, when Vietnam did, and -# (2) they also reverted to UT+7 on 1953-11-09, the date of independence. +# (1) Cambodia reverted to +07 on 1945-09-02, when Vietnam did, and +# (2) they also reverted to +07 on 1953-11-09, the date of independence. # These guesses are probably wrong but they're better than guessing no # transitions there. Zone Asia/Phnom_Penh 6:59:40 - LMT 1906 Jul 1 @@ -506,8 +506,8 @@ Zone Asia/Tel_Aviv 2:19:04 - LMT 1880 # Laos # From Paul Eggert (2014-10-11): # See Asia/Ho_Chi_Minh for the source for most of this data. -# Trần's book says that Laos reverted to UT+7 on 1955-04-15. -# Also, guess that Laos reverted to UT+7 on 1945-09-02, when Vietnam did; +# Trần's book says that Laos reverted to +07 on 1955-04-15. +# Also, guess that Laos reverted to +07 on 1945-09-02, when Vietnam did; # this is probably wrong but it's better than guessing no transition. Zone Asia/Vientiane 6:50:24 - LMT 1906 Jul 1 7:06:30 - PLMT 1911 May 1 diff --git a/europe b/europe index b02edbd..4219828 100644 --- a/europe +++ b/europe @@ -774,8 +774,6 @@ Zone Europe/Vienna 1:05:21 - LMT 1893 Apr # From Alexander Bokovoy (2014-10-09): # Belarussian government decided against changing to winter time.... # http://eng.belta.by/all_news/society/Belarus-decides-against-adjusting-time-... -# From Paul Eggert (2014-10-08): -# Hence Belarus can share time zone abbreviations with Moscow again. # # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Minsk 1:50:16 - LMT 1880 @@ -1294,7 +1292,7 @@ Zone Europe/Paris 0:09:21 - LMT 1891 Mar 15 0:01 # http://www.parlament-berlin.de/pds-fraktion.nsf/727459127c8b66ee852566230045... # says that Bersarin issued an order to use Moscow time on May 20. # However, Moscow did not observe daylight saving in 1945, so -# this was equivalent to CEMT (GMT+3), not GMT+4. +# this was equivalent to +03, not +04. # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S @@ -2258,7 +2256,6 @@ Zone Europe/Bucharest 1:44:24 - LMT 1891 Oct # http://www.worldtimezone.com/dst_news/dst_news_russia-map-2014-07.html # From Paul Eggert (2006-03-22): -# Except for Moscow after 1919-07-01, I invented the time zone abbreviations. # Moscow time zone abbreviations after 1919-07-01, and Moscow rules after 1991, # are from Andrey A. Chernov. The rest is from Shanks & Pottenger, # except we follow Chernov's report that 1992 DST transitions were Sat @@ -3080,9 +3077,6 @@ Zone Asia/Magadan 10:03:12 - LMT 1924 May 2 # in Russian.) In addition, Srednekolymsk appears to be a much older # settlement and the population of Zyryanka seems to be declining. # Go with Srednekolymsk. -# -# Since Magadan Oblast moves to UTC+10 on 2014-10-26, we cannot keep using MAGT -# as the abbreviation. Use SRET instead. Zone Asia/Srednekolymsk 10:14:52 - LMT 1924 May 2 10:00 - +10 1930 Jun 21 diff --git a/localtime.c b/localtime.c index 276ce34..6c00c45 100644 --- a/localtime.c +++ b/localtime.c @@ -1510,7 +1510,7 @@ gmtsub(struct state const *sp, time_t const *timep, int_fast32_t offset, #ifdef TM_ZONE /* ** Could get fancy here and deliver something such as - ** "UT+xxxx" or "UT-xxxx" if offset is non-zero, + ** "+xx" or "-xx" if offset is non-zero, ** but this is no time for a treasure hunt. */ tmp->TM_ZONE = ((char *) diff --git a/northamerica b/northamerica index d66135e..0c069bb 100644 --- a/northamerica +++ b/northamerica @@ -3312,7 +3312,7 @@ Zone America/Miquelon -3:44:40 - LMT 1911 May 15 # St Pierre # indicating that the normal ET rules are followed. # # From Paul Eggert (2014-08-19): -# The 2014-08-13 Cabinet meeting decided to stay on UTC-4 year-round. See: +# The 2014-08-13 Cabinet meeting decided to stay on -04 year-round. See: # http://tcweeklynews.com/daylight-savings-time-to-be-maintained-p5353-127.htm # Model this as a switch from EST/EDT to AST ... # From Chris Walton (2014-11-04): diff --git a/private.h b/private.h index 941e91b..3583079 100644 --- a/private.h +++ b/private.h @@ -15,6 +15,7 @@ ** Thank you! */ +/* This string was in the tzdata Factory zone through version 2016f. */ #define GRANDPARENTED "Local time zone must be set--see zic manual page" /* diff --git a/southamerica b/southamerica index 1c38f63..5321451 100644 --- a/southamerica +++ b/southamerica @@ -410,9 +410,9 @@ Rule Arg 2008 only - Oct Sun>=15 0:00 1:00 S # stuck on Summer daylight savings time even though the summer is over. # From Paul Eggert (2013-09-05): -# Perhaps San Luis operates on the legal fiction that it is at UTC-4 +# Perhaps San Luis operates on the legal fiction that it is at -04 # with perpetual summer time, but ordinary usage typically seems to -# just say it's at UTC-3; see, for example, +# just say it's at -03; see, for example, # http://es.wikipedia.org/wiki/Hora_oficial_argentina # We've documented similar situations as being plain changes to # standard time, so let's do that here too. This does not change UTC -- 2.5.5
* NEWS: Document this. * antarctica (Antarctica/Casey, Antarctica/Davis, Antarctica/Mawson): (Indian/Kerguelen, Antarctica/DumontDUrville, Antarctica/Syowa) (Troll, Antarctica/Vostok, Antarctica/Rothera): Prefer numeric to invented time zone abbreviations. --- NEWS | 15 +++++++++------ antarctica | 55 ++++++++++++++++++++++++++----------------------------- 2 files changed, 35 insertions(+), 35 deletions(-) diff --git a/NEWS b/NEWS index b0da284..d88d2bb 100644 --- a/NEWS +++ b/NEWS @@ -15,17 +15,20 @@ Unreleased, experimental changes Changes to past and future time zone abbreviations - Several zones in the former Soviet Union now use numeric time zone - abbreviations instead of invented ones. The affected zones are + Several zones in Antarctica and the former Soviet Union now use + numeric time zone abbreviations instead of invented ones. The + affected zones are Antarctica/Casey, Antarctica/Davis, + Antarctica/DumontDUrville, Antarctica/Mawson, Antarctica/Rothera, + Antarctica/Syowa, Antarctica/Troll, Antarctica/Vostok, Asia/Anadyr, Asia/Ashgabat, Asia/Baku, Asia/Bishkek, Asia/Chita, Asia/Dushanbe, Asia/Irkutsk, Asia/Kamchatka, Asia/Khandyga, Asia/Krasnoyarsk, Asia/Magadan, Asia/Omsk, Asia/Sakhalin, Asia/Samarkand, Asia/Srednekolymsk, Asia/Tashkent, Asia/Tbilisi, Asia/Ust-Nera, Asia/Vladivostok, Asia/Yakutsk, Asia/Yekaterinburg, - Asia/Yerevan, Europe/Kaliningrad, Europe/Minsk, Europe/Samara, and - Europe/Volgograd. For Europe/Moscow the invented abbreviation MSM - was replaced by +05, whereas MSK and MSD were kept as they are not - our invention and are widely used. + Asia/Yerevan, Europe/Kaliningrad, Europe/Minsk, Europe/Samara, + Europe/Volgograd, and Indian/Kerguelen. For Europe/Moscow the + invented abbreviation MSM was replaced by +05, whereas MSK and MSD + were kept as they are not our invention and are widely used. Changes to code diff --git a/antarctica b/antarctica index a537832..f8b4bfb 100644 --- a/antarctica +++ b/antarctica @@ -10,9 +10,7 @@ # http://www.spri.cam.ac.uk/bob/periant.htm # for information. # Unless otherwise specified, we have no time zone information. -# -# Except for the French entries, -# I made up all time zone abbreviations mentioned here; corrections welcome! + # FORMAT is '-00' and GMTOFF is 0 for locations while uninhabited. # Argentina - year-round bases @@ -68,23 +66,22 @@ # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Antarctica/Casey 0 - -00 1969 - 8:00 - AWST 2009 Oct 18 2:00 - # Australian Western Std Time - 11:00 - CAST 2010 Mar 5 2:00 # Casey Time - 8:00 - AWST 2011 Oct 28 2:00 - 11:00 - CAST 2012 Feb 21 17:00u - 8:00 - AWST + 8:00 - +08 2009 Oct 18 2:00 + 11:00 - +11 2010 Mar 5 2:00 + 8:00 - +08 2011 Oct 28 2:00 + 11:00 - +11 2012 Feb 21 17:00u + 8:00 - +08 Zone Antarctica/Davis 0 - -00 1957 Jan 13 - 7:00 - DAVT 1964 Nov # Davis Time + 7:00 - +07 1964 Nov 0 - -00 1969 Feb - 7:00 - DAVT 2009 Oct 18 2:00 - 5:00 - DAVT 2010 Mar 10 20:00u - 7:00 - DAVT 2011 Oct 28 2:00 - 5:00 - DAVT 2012 Feb 21 20:00u - 7:00 - DAVT + 7:00 - +07 2009 Oct 18 2:00 + 5:00 - +05 2010 Mar 10 20:00u + 7:00 - +07 2011 Oct 28 2:00 + 5:00 - +05 2012 Feb 21 20:00u + 7:00 - +07 Zone Antarctica/Mawson 0 - -00 1954 Feb 13 - 6:00 - MAWT 2009 Oct 18 2:00 # Mawson Time - 5:00 - MAWT + 6:00 - +06 2009 Oct 18 2:00 + 5:00 - +05 # References: # Casey Weather (1998-02-26) # http://www.antdiv.gov.au/aad/exop/sfo/casey/casey_aws.html @@ -138,7 +135,7 @@ Zone Antarctica/Mawson 0 - -00 1954 Feb 13 # # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Indian/Kerguelen 0 - -00 1950 # Port-aux-Français - 5:00 - TFT # ISO code TF Time + 5:00 - +05 # # year-round base in the main continent # Dumont d'Urville, Île des Pétrels, -6640+14001, since 1956-11 @@ -149,9 +146,9 @@ Zone Indian/Kerguelen 0 - -00 1950 # Port-aux-Français # # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Antarctica/DumontDUrville 0 - -00 1947 - 10:00 - PMT 1952 Jan 14 # Port-Martin Time + 10:00 - +10 1952 Jan 14 0 - -00 1956 Nov - 10:00 - DDUT # Dumont-d'Urville Time + 10:00 - +10 # France & Italy - year-round base # Concordia, -750600+1232000, since 2005 @@ -177,7 +174,7 @@ Zone Antarctica/DumontDUrville 0 - -00 1947 # station of Japan, it's appropriate for the principal location. # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Antarctica/Syowa 0 - -00 1957 Jan 29 - 3:00 - SYOT # Syowa Time + 3:00 - +03 # See: # NIPR Antarctic Research Activities (1999-08-17) # http://www.nipr.ac.jp/english/ara01.html @@ -219,12 +216,12 @@ Zone Antarctica/Syowa 0 - -00 1957 Jan 29 # with only UTC and CEST. Uncomment them when 2014b is more prevalent. # # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S -#Rule Troll 2005 max - Mar 1 1:00u 1:00 CET -Rule Troll 2005 max - Mar lastSun 1:00u 2:00 CEST -#Rule Troll 2005 max - Oct lastSun 1:00u 1:00 CET -#Rule Troll 2004 max - Nov 7 1:00u 0:00 UTC +#Rule Troll 2005 max - Mar 1 1:00u 1:00 +01 +Rule Troll 2005 max - Mar lastSun 1:00u 2:00 +02 +#Rule Troll 2005 max - Oct lastSun 1:00u 1:00 +01 +#Rule Troll 2004 max - Nov 7 1:00u 0:00 +00 # Remove the following line when uncommenting the above '#Rule' lines. -Rule Troll 2004 max - Oct lastSun 1:00u 0:00 UTC +Rule Troll 2004 max - Oct lastSun 1:00u 0:00 +00 # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Antarctica/Troll 0 - -00 2005 Feb 12 0:00 Troll %s @@ -265,10 +262,10 @@ Zone Antarctica/Troll 0 - -00 2005 Feb 12 # changes during the year and does not necessarily correspond to mean # solar noon. So the Vostok time might have been whatever the clocks # happened to be during their visit. So we still don't really know what time -# it is at Vostok. But we'll guess UTC+6. +# it is at Vostok. But we'll guess +06. # Zone Antarctica/Vostok 0 - -00 1957 Dec 16 - 6:00 - VOST # Vostok time + 6:00 - +06 # S Africa - year-round bases # Marion Island, -4653+03752 @@ -301,7 +298,7 @@ Zone Antarctica/Vostok 0 - -00 1957 Dec 16 # # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Antarctica/Rothera 0 - -00 1976 Dec 1 - -3:00 - ROTT # Rothera time + -3:00 - -03 # Uruguay - year round base # Artigas, King George Island, -621104-0585107 -- 2.5.5
On Tue, Aug 23, 2016 at 7:55 PM, Paul Eggert <eggert@cs.ucla.edu> wrote:
+ ... For Europe/Moscow the + invented abbreviation MSM was replaced by +05, whereas MSK and MSD + were kept as they are not our invention and are widely used.
What's the difference between MSM (Midsummer) and MDST (Moscow Double Summer Time)? Both seem to be +05 = MSK + 2, but got different abbreviations. BTW, the earlier Soviet decrees have been collected on the istmat.info web site. For example, (transition date: url): Dec 28, 1917: http://istmat.info/node/28137 May 31, 1918: http://istmat.info/node/30001 May 31, 1919: http://istmat.info/node/37949 Feb 14, 1921: http://istmat.info/node/45840 May 20, 1921: http://istmat.info/node/45949 You may want to reference these documents in the source files.
Alexander Belopolsky wrote:
On Tue, Aug 23, 2016 at 7:55 PM, Paul Eggert <eggert@cs.ucla.edu> wrote:
+ ... For Europe/Moscow the + invented abbreviation MSM was replaced by +05, whereas MSK and MSD + were kept as they are not our invention and are widely used.
What's the difference between MSM (Midsummer) and MDST (Moscow Double Summer Time)? Both seem to be +05 = MSK + 2, but got different abbreviations.
The former differs from UT by an integer number of hours, the latter does not. In the current go-round I am looking at integer-hour offsets, as they are the most important for contemporaneous time stamps. Addressing the non-integer offsets will be a bit more tricky and I plan to take it up later.
BTW, the earlier Soviet decrees have been collected on the istmat.info web site. For example, (transition date: url):
Dec 28, 1917: http://istmat.info/node/28137 May 31, 1918: http://istmat.info/node/30001 May 31, 1919: http://istmat.info/node/37949 Feb 14, 1921: http://istmat.info/node/45840 May 20, 1921: http://istmat.info/node/45949
You may want to reference these documents in the source files.
Thanks for the pointers. These indicate that our old abbreviations are dubious too. The first decree talks about "Петроградского гражданского времени" (Petrograd civil time), for example, and doesn't give DST a particular name. For now, I added them to the commentary by installing the attached experimental patch.
On Tue, Aug 23, 2016 at 9:25 PM, Paul Eggert <eggert@cs.ucla.edu> wrote:
What's the difference between MSM (Midsummer) and MDST (Moscow Double Summer Time)? Both seem to be +05 = MSK + 2, but got different abbreviations.
The former differs from UT by an integer number of hours, the latter does not.
Interesting. It looks like the transition to integer offset from UTC is recorded as happening on Mon Jun 30 21:28:41 1919 UT (from zdump -v output.) However, according to this February 18, 1919 decree № 59 < http://istmat.info/node/35567>, the GMT-based system of 11 zones (belts) went into effect on GMT midnight, April 1, 1919. The decree does not mention Moscow time, but the UTC+2 belt boundaries are defined by the state boundaries on the West and rivers Volga and Don on the east which places Moscow in UTC+2. The decree does not establish DST rules, but allows regional DST shifts by integer number of hours only.
It looks like the decree № 59 was not implemented and replaced by decree № 147 <http://istmat.info/node/35854> which postponed the implementation until July 1, 1919. This is close to the date in tzdata, but it would still make more sense to have transition on a round UTC hour rather than at 21:28:41. On Tue, Aug 23, 2016 at 11:57 PM, Alexander Belopolsky < alexander.belopolsky@gmail.com> wrote:
On Tue, Aug 23, 2016 at 9:25 PM, Paul Eggert <eggert@cs.ucla.edu> wrote:
What's the difference between MSM (Midsummer) and MDST (Moscow Double Summer Time)? Both seem to be +05 = MSK + 2, but got different abbreviations.
The former differs from UT by an integer number of hours, the latter does not.
Interesting. It looks like the transition to integer offset from UTC is recorded as happening on Mon Jun 30 21:28:41 1919 UT (from zdump -v output.) However, according to this February 18, 1919 decree № 59 < http://istmat.info/node/35567>, the GMT-based system of 11 zones (belts) went into effect on GMT midnight, April 1, 1919. The decree does not mention Moscow time, but the UTC+2 belt boundaries are defined by the state boundaries on the West and rivers Volga and Don on the east which places Moscow in UTC+2. The decree does not establish DST rules, but allows regional DST shifts by integer number of hours only.
Alexander Belopolsky wrote:
It looks like the decree № 59 was not implemented and replaced by decree № 147 <http://istmat.info/node/35854> which postponed the implementation until July 1, 1919. This is close to the date in tzdata, but it would still make more sense to have transition on a round UTC hour rather than at 21:28:41.
Thanks, that's interesting. Decree No. 59 says this: Первого апреля 1919 года в среднюю Гринвичскую полночь часы в каждом из поясов России поставить так, чтобы они показывали целое число часов, равное номеру пояса. Время в течение суток считать от 0 до 24 часов, принимая за начало суток полночь. which Google Translate renders as: On April, 1919, in Greenwich Mean midnight hours in each of the Russian zone to put so that they showed a whole number of hours equal to the zone number. Time during the day to count from 0 to 24 hours, taking the start of the day at midnight. I interpret this to mean that all Russian zones were supposed to switch to the new system at 00:00 GMT on the specified date (April 1 in that decree, but delayed to July 1 in Decree No. 147). Of course this would affect only the territories actually controlled by the Bolsheviks at the time. (Also, of course the actual switches were not implemented precisely; there was a war going on, after all.) Proposed patch attached, and installed into the experimental repository on Github.
On Aug 23, 2016, at 9:25 PM, Paul Eggert <eggert@cs.ucla.edu> wrote:
These indicate that our old abbreviations are dubious too. The first decree talks about "Петроградского гражданского времени" (Petrograd civil time),
I don't think abbreviations for old zones in non English speaking countries can be justified by historical usage. Before the switch to the GMT based system, the timekeeping in Russia was based on Pulkov time - the time measured at the Pulkov observatory near St. Petersburg. That observatory has an easy to remember location: it is almost exactly at 30 degrees east longitude and 60 degrees north latitude. This means UTC+2 LMT and 1/2 hour behind Moscow LMT. I don't think Moscow solar time was ever used for precise time keeping. Pulkov time was important for navigation- Russian navy used Pulkov meridian as 0 longitude before Greenwich became the international standard.
On 24/08/16 06:22, Alexander Belopolsky wrote:
These indicate that our old abbreviations are dubious too. The first decree talks about "Петроградского гражданского времени" (Petrograd civil time), I don't think abbreviations for old zones in non English speaking countries can be justified by historical usage. Before the switch to the GMT based system, the timekeeping in Russia was based on Pulkov time - the time measured at the Pulkov observatory near St. Petersburg. That observatory has an easy to remember location: it is almost exactly at 30 degrees east longitude and 60 degrees north latitude. This means UTC+2 LMT and 1/2 hour behind Moscow LMT. I don't think Moscow solar time was ever used for precise time keeping. Pulkov time was important for navigation- Russian navy used Pulkov meridian as 0 longitude before Greenwich became the international standard.
Prior to Pulkov time being established, then solar time is all that can be assumed. Totally OT for tz discussions, but historic references prior to any formal timing methods such as sunrise, midday, and sunset in Moscow need a solar base and are as precise as the people at the time could be ;) So when Russia started standardising on Pulkov time is an historic point, and one would assume that prior to that some local standards would have existed much as the 'town' times in the UK? Documentary evidence of which may start to appear? We have had the discussion that much historic material in tz WAS fabricated to give a consistent base, and some gaps will never be authenticated, but the additional material that has been uncovered needs a reliable home! -- 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
* NEWS: Document this. * etcetera (Etc/GMT-14, Etc/GMT-13, Etc/GMT-12, Etc/GMT-11) (Etc/GMT-10, Etc/GMT-9, Etc/GMT-8, Etc/GMT-7, Etc/GMT-6) (Etc/GMT-5, Etc/GMT-4, Etc/GMT-3, Etc/GMT-2, Etc/GMT-1, Etc/GMT+1) (Etc/GMT+2, Etc/GMT+3, Etc/GMT+4, Etc/GMT+5, Etc/GMT+6, Etc/GMT+7) (Etc/GMT+8, Etc/GMT+9, Etc/GMT+10, Etc/GMT+11, Etc/GMT+12): Use numeric time zone abbreviations, for consistency with the rest of the database. The old abbreviations like "GMT-9" were both confusing and obsolete. --- NEWS | 21 ++++++++++++------ etcetera | 74 +++++++++++++++++++++++++++++++--------------------------------- 2 files changed, 50 insertions(+), 45 deletions(-) diff --git a/NEWS b/NEWS index d88d2bb..71916a9 100644 --- a/NEWS +++ b/NEWS @@ -15,9 +15,11 @@ Unreleased, experimental changes Changes to past and future time zone abbreviations - Several zones in Antarctica and the former Soviet Union now use - numeric time zone abbreviations instead of invented ones. The - affected zones are Antarctica/Casey, Antarctica/Davis, + Several zones in Antarctica and the former Soviet Union, along + with zones intended for ships at sea that cannot use POSIX TZ + strings, now use numeric time zone abbreviations instead of + invented or obsolete alphanumeric abbreviations. The affected + zones are Antarctica/Casey, Antarctica/Davis, Antarctica/DumontDUrville, Antarctica/Mawson, Antarctica/Rothera, Antarctica/Syowa, Antarctica/Troll, Antarctica/Vostok, Asia/Anadyr, Asia/Ashgabat, Asia/Baku, Asia/Bishkek, Asia/Chita, @@ -25,10 +27,15 @@ Unreleased, experimental changes Asia/Krasnoyarsk, Asia/Magadan, Asia/Omsk, Asia/Sakhalin, Asia/Samarkand, Asia/Srednekolymsk, Asia/Tashkent, Asia/Tbilisi, Asia/Ust-Nera, Asia/Vladivostok, Asia/Yakutsk, Asia/Yekaterinburg, - Asia/Yerevan, Europe/Kaliningrad, Europe/Minsk, Europe/Samara, - Europe/Volgograd, and Indian/Kerguelen. For Europe/Moscow the - invented abbreviation MSM was replaced by +05, whereas MSK and MSD - were kept as they are not our invention and are widely used. + Asia/Yerevan, Etc/GMT-14, Etc/GMT-13, Etc/GMT-12, Etc/GMT-11, + Etc/GMT-10, Etc/GMT-9, Etc/GMT-8, Etc/GMT-7, Etc/GMT-6, Etc/GMT-5, + Etc/GMT-4, Etc/GMT-3, Etc/GMT-2, Etc/GMT-1, Etc/GMT+1, Etc/GMT+2, + Etc/GMT+3, Etc/GMT+4, Etc/GMT+5, Etc/GMT+6, Etc/GMT+7, Etc/GMT+8, + Etc/GMT+9, Etc/GMT+10, Etc/GMT+11, Etc/GMT+12, Europe/Kaliningrad, + Europe/Minsk, Europe/Samara, Europe/Volgograd, and + Indian/Kerguelen. For Europe/Moscow the invented abbreviation MSM + was replaced by +05, whereas MSK and MSD were kept as they are not + our invention and are widely used. Changes to code diff --git a/etcetera b/etcetera index c2e2532..f5fa4c9 100644 --- a/etcetera +++ b/etcetera @@ -8,6 +8,13 @@ # need now for the entries that are not on UTC are for ships at sea # that cannot use POSIX TZ settings. +# Starting with POSIX 1003.1-2001, the entries below are all +# unnecessary as settings for the TZ environment variable. E.g., +# instead of TZ='Etc/GMT+4' one can use the POSIX setting TZ='<-04>+4'. +# +# Do not use a POSIX TZ setting like TZ='GMT+4', which is four hours +# behind GMT but uses the completely misleading abbreviation "GMT". + Zone Etc/GMT 0 - GMT Zone Etc/UTC 0 - UTC Zone Etc/UCT 0 - UCT @@ -26,23 +33,13 @@ Link Etc/GMT Etc/GMT-0 Link Etc/GMT Etc/GMT+0 Link Etc/GMT Etc/GMT0 -# We use POSIX-style signs in the Zone names and the output abbreviations, +# Be consistent with POSIX TZ settings in the Zone names, # even though this is the opposite of what many people expect. # POSIX has positive signs west of Greenwich, but many people expect # positive signs east of Greenwich. For example, TZ='Etc/GMT+4' uses -# the abbreviation "GMT+4" and corresponds to 4 hours behind UT +# the abbreviation "-04" and corresponds to 4 hours behind UT # (i.e. west of Greenwich) even though many people would expect it to # mean 4 hours ahead of UT (i.e. east of Greenwich). -# -# In the draft 5 of POSIX 1003.1-200x, the angle bracket notation allows for -# TZ='<GMT-4>+4'; if you want time zone abbreviations conforming to -# ISO 8601 you can use TZ='<-0400>+4'. Thus the commonly-expected -# offset is kept within the angle bracket (and is used for display) -# while the POSIX sign is kept outside the angle bracket (and is used -# for calculation). -# -# Do not use a TZ setting like TZ='GMT+4', which is four hours behind -# GMT but uses the completely misleading abbreviation "GMT". # Earlier incarnations of this package were not POSIX-compliant, # and had lines such as @@ -51,30 +48,31 @@ Link Etc/GMT Etc/GMT0 # way does a # zic -l GMT-12 # so we moved the names into the Etc subdirectory. +# Also, the time zone abbreviations are now compatible with %z. -Zone Etc/GMT-14 14 - GMT-14 # 14 hours ahead of GMT -Zone Etc/GMT-13 13 - GMT-13 -Zone Etc/GMT-12 12 - GMT-12 -Zone Etc/GMT-11 11 - GMT-11 -Zone Etc/GMT-10 10 - GMT-10 -Zone Etc/GMT-9 9 - GMT-9 -Zone Etc/GMT-8 8 - GMT-8 -Zone Etc/GMT-7 7 - GMT-7 -Zone Etc/GMT-6 6 - GMT-6 -Zone Etc/GMT-5 5 - GMT-5 -Zone Etc/GMT-4 4 - GMT-4 -Zone Etc/GMT-3 3 - GMT-3 -Zone Etc/GMT-2 2 - GMT-2 -Zone Etc/GMT-1 1 - GMT-1 -Zone Etc/GMT+1 -1 - GMT+1 -Zone Etc/GMT+2 -2 - GMT+2 -Zone Etc/GMT+3 -3 - GMT+3 -Zone Etc/GMT+4 -4 - GMT+4 -Zone Etc/GMT+5 -5 - GMT+5 -Zone Etc/GMT+6 -6 - GMT+6 -Zone Etc/GMT+7 -7 - GMT+7 -Zone Etc/GMT+8 -8 - GMT+8 -Zone Etc/GMT+9 -9 - GMT+9 -Zone Etc/GMT+10 -10 - GMT+10 -Zone Etc/GMT+11 -11 - GMT+11 -Zone Etc/GMT+12 -12 - GMT+12 +Zone Etc/GMT-14 14 - +14 +Zone Etc/GMT-13 13 - +13 +Zone Etc/GMT-12 12 - +12 +Zone Etc/GMT-11 11 - +11 +Zone Etc/GMT-10 10 - +10 +Zone Etc/GMT-9 9 - +09 +Zone Etc/GMT-8 8 - +08 +Zone Etc/GMT-7 7 - +07 +Zone Etc/GMT-6 6 - +06 +Zone Etc/GMT-5 5 - +05 +Zone Etc/GMT-4 4 - +04 +Zone Etc/GMT-3 3 - +03 +Zone Etc/GMT-2 2 - +02 +Zone Etc/GMT-1 1 - +01 +Zone Etc/GMT+1 -1 - -01 +Zone Etc/GMT+2 -2 - -02 +Zone Etc/GMT+3 -3 - -03 +Zone Etc/GMT+4 -4 - -04 +Zone Etc/GMT+5 -5 - -05 +Zone Etc/GMT+6 -6 - -06 +Zone Etc/GMT+7 -7 - -07 +Zone Etc/GMT+8 -8 - -08 +Zone Etc/GMT+9 -9 - -09 +Zone Etc/GMT+10 -10 - -10 +Zone Etc/GMT+11 -11 - -11 +Zone Etc/GMT+12 -12 - -12 -- 2.5.5
* NEWS, factory (Factory): Use the more-standard time zone abbreviation "-00" to denote a non-setting. --- NEWS | 4 ++++ factory | 9 +++++---- 2 files changed, 9 insertions(+), 4 deletions(-) diff --git a/NEWS b/NEWS index 71916a9..4c0f4e0 100644 --- a/NEWS +++ b/NEWS @@ -15,6 +15,10 @@ Unreleased, experimental changes Changes to past and future time zone abbreviations + The Factory zone now uses the time zone abbreviation -00 instead + of a long English-language string, as -00 is now the normal way to + represent an undefined time zone. + Several zones in Antarctica and the former Soviet Union, along with zones intended for ships at sea that cannot use POSIX TZ strings, now use numeric time zone abbreviations instead of diff --git a/factory b/factory index 4304f7c..7c86430 100644 --- a/factory +++ b/factory @@ -1,9 +1,10 @@ # This file is in the public domain, so clarified as of # 2009-05-17 by Arthur David Olson. -# For companies who don't want to put time zone specification in -# their installation procedures. When users run date, they'll get the message. -# Also useful for the "comp.sources" version. +# For distributors who don't want to put time zone specification in +# their installation procedures. Users that run 'date' will get the +# time zone abbrevation "-00", indicating that the actual time zone is +# unknown. # Zone NAME GMTOFF RULES FORMAT -Zone Factory 0 - "Local time zone must be set--see zic manual page" +Zone Factory 0 - -00 -- 2.5.5
Date: Tue, 23 Aug 2016 16:55:42 -0700 From: Paul Eggert <eggert@cs.ucla.edu> Message-ID: <1471996545-960-1-git-send-email-eggert@cs.ucla.edu> I am not a fan of this change in general, I think UTC-1 is both more common, and less ambiguous than -01 (from the latter it isn't even obvious that the expression has anything to do with time offsets) but this change in particular ... | -# Zhongyuan Time ("Central plain Time") UT+8 | +# Zhongyuan Time ("Central plain Time") -08 cannot be right. kre
On Wed, 24 Aug 2016, Robert Elz wrote:
Date: Tue, 23 Aug 2016 16:55:42 -0700 From: Paul Eggert <eggert@cs.ucla.edu> Message-ID: <1471996545-960-1-git-send-email-eggert@cs.ucla.edu>
I am not a fan of this change in general, I think UTC-1 is both more common, and less ambiguous than -01
I agree. I don't think this change should be made. It looks like an change for the sake of a change to me. cheers, Derick
On Aug 24, 2016, at 7:38 AM, Robert Elz <kre@munnari.OZ.AU> wrote:
Date: Tue, 23 Aug 2016 16:55:42 -0700 From: Paul Eggert <eggert@cs.ucla.edu> Message-ID: <1471996545-960-1-git-send-email-eggert@cs.ucla.edu>
I am not a fan of this change in general, I think UTC-1 is both more common, and less ambiguous than -01 (from the latter it isn't even obvious that the expression has anything to do with time offsets) but this change in particular ...
So are you suggesting that all the entries that have already been changed to the +/-NN syntax should be changed to UTC+/-N? paul
On 24/08/16 14:39, Paul_Koning@dell.com wrote:
I am not a fan of this change in general, I think UTC-1 is both more
common, and less ambiguous than -01 (from the latter it isn't even obvious that the expression has anything to do with time offsets) but this change in particular ... So are you suggesting that all the entries that have already been changed to the ±NN syntax should be changed to UTC+/-N?
Looking at the posted patch I must say that in most cases the replacement is a lot more difficult to read than the original. Using UTC as a flag that the offset is based on that makes documentation unambiguous. But then I'm still fighting the fact that these ARE only offsets and have nothing to do with flagging DST time zones! -- 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
I understand the partial motivation behind getting rid of the need to specify UTC±N, UT±N, and GMT±N, which do have differences, but I agree with the general sentiment expressed here that this negatively affects the readability of our commentary. -- Tim Parenti On 24 August 2016 at 09:51, Lester Caine <lester@lsces.co.uk> wrote:
On 24/08/16 14:39, Paul_Koning@dell.com wrote:
I am not a fan of this change in general, I think UTC-1 is both more
common, and less ambiguous than -01 (from the latter it isn't even obvious that the expression has anything to do with time offsets) but this change in particular ... So are you suggesting that all the entries that have already been changed to the ±NN syntax should be changed to UTC+/-N?
Looking at the posted patch I must say that in most cases the replacement is a lot more difficult to read than the original. Using UTC as a flag that the offset is based on that makes documentation unambiguous. But then I'm still fighting the fact that these ARE only offsets and have nothing to do with flagging DST time zones!
-- 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
On Wed 2016-08-24T09:56:09 -0400, Tim Parenti hath writ:
I understand the partial motivation behind getting rid of the need to specify UTC±N, UT±N, and GMT±N, which do have differences, but I agree with the general sentiment expressed here that this negatively affects the readability of our commentary.
I agree about the readability, but I'm not sure what is best. Furthermore, in some countries some of those different notations are legally correct and others are not. Some multi-lingual countries use different terms in the versions of their law written in the different languages. Preprint 662 at the 2011 Future of UTC colloquium http://www.cacr.caltech.edu/futureofutc/2011/preprints/index.html and preprint 505 at the 2013 Future of UTC colloquium http://www.cacr.caltech.edu/futureofutc/preprints/index.html have a survey of the legal language in many countries and analysis of the legislative processes which have resulted in the different use of UT, UTC, GMT. -- Steve Allen <sla@ucolick.org> WGS-84 (GPS) UCO/Lick Observatory--ISB 260 Natural Sciences II, Room 165 Lat +36.99855 1156 High Street Voice: +1 831 459 3046 Lng -122.06015 Santa Cruz, CA 95064 http://www.ucolick.org/~sla/ Hgt +250 m
On Wed, Aug 24, 2016, at 12:23, Steve Allen wrote:
On Wed 2016-08-24T09:56:09 -0400, Tim Parenti hath writ:
I understand the partial motivation behind getting rid of the need to specify UTC±N, UT±N, and GMT±N, which do have differences, but I agree with the general sentiment expressed here that this negatively affects the readability of our commentary.
I agree about the readability, but I'm not sure what is best. Furthermore, in some countries some of those different notations are legally correct and others are not. Some multi-lingual countries use different terms in the versions of their law written in the different languages.
I'm not sure how important it is for the comments to be "legally correct", other than when directly quoting the laws. And ±N doesn't seem to me to be *more* "legally correct", it's just less readable to no clear purpose.
Preprint 662 at the 2011 Future of UTC colloquium http://www.cacr.caltech.edu/futureofutc/2011/preprints/index.html and preprint 505 at the 2013 Future of UTC colloquium http://www.cacr.caltech.edu/futureofutc/preprints/index.html have a survey of the legal language in many countries and analysis of the legislative processes which have resulted in the different use of UT, UTC, GMT.
Are there any countries whose law still prescribes the time zone as a meridian (that may be a multiple of 15, but arguably still can't be "legally correctly" described as GMT±N since it gives the difference in degrees rather than hours), e.g. "the mean solar time of the sixtieth degree of longitude west from Greenwich"? The US law doesn't currently, but I can't find when it changed.
Random832 wrote:
Are there any countries whose law still prescribes the time zone as a meridian
Legal time in the UK is still officially offset from GMT, not from UTC. See <https://www.polyomino.org.uk/british-time/>. This is a bit dicey, since GMT is no longer maintained. I expect other countries specify something similar, though I don't know of any offhand. India, perhaps? In practice people don't follow this part of UK law exactly as written, and use UTC even when a strict reading of the law might require GMT. For example, as part of the EU, the UK requires electronic signatures' time stamps to be linked to UTC, not GMT (see regulation 910/2014/EU). I doubt whether this would change even if Brexit becomes real.
On Wed, Aug 24, 2016 at 3:05 PM, Paul Eggert <eggert@cs.ucla.edu> wrote:
I expect other countries specify something similar, though I don't know of any offhand.
In Russia, the official time scale is UTC (SU) maintained by the National Research Institute for Physical-Technical and Radio Engineering Measurements (http://www.vniiftri.ru/index.php/en). For all practical purposes UTC (SU) is the same as UTC because the difference between the two scales does not currently exceed 10 ns and expected to become smaller as time measuring equipment improves.
On 24/08/16 20:05, Paul Eggert wrote:
Are there any countries whose law still prescribes the time zone as a meridian
Legal time in the UK is still officially offset from GMT, not from UTC. See <https://www.polyomino.org.uk/british-time/>. This is a bit dicey, since GMT is no longer maintained. I expect other countries specify something similar, though I don't know of any offhand. India, perhaps?
In practice people don't follow this part of UK law exactly as written, and use UTC even when a strict reading of the law might require GMT. For example, as part of the EU, the UK requires electronic signatures' time stamps to be linked to UTC, not GMT (see regulation 910/2014/EU). I doubt whether this would change even if Brexit becomes real.
http://wwp.greenwichmeantime.com/info/timezone/ Just use Military designation and have done with it ;) But essentially Zulu marries GMT, UT and UTC which is perhaps why the international space station runs on GMT but essentially it's interchangeable with UTC today. http://www.dxing.com/utcgmt.htm -- 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
On Wed 2016-08-24T12:56:46 -0400, Random832 hath writ:
Are there any countries whose law still prescribes the time zone as a meridian (that may be a multiple of 15, but arguably still can't be "legally correctly" described as GMT±N since it gives the difference in degrees rather than hours), e.g. "the mean solar time of the sixtieth degree of longitude west from Greenwich"?
Argentina, for one http://servicios.infoleg.gob.ar/infolegInternet/anexos/135000-139999/136191/... but as with many other places, the observatory tasked with providing Argentine legal time has the leeway to interpret that as offset in SI seconds from UTC rather than fractions of one earth rotation from GMT.
The US law doesn't currently, but I can't find when it changed.
America Competes Act of of 2007 https://www.govtrack.us/congress/bills/110/hr2272 https://www.govtrack.us/congress/bills/110/hr2272/text -- Steve Allen <sla@ucolick.org> WGS-84 (GPS) UCO/Lick Observatory--ISB 260 Natural Sciences II, Room 165 Lat +36.99855 1156 High Street Voice: +1 831 459 3046 Lng -122.06015 Santa Cruz, CA 95064 http://www.ucolick.org/~sla/ Hgt +250 m
To me, UTC-1 looks too much like a traditional Unix TZ value with negated offset, leading to possible confusion about the direction of the offset. My personal preference would be to use the ±HHMM format (with non-negated offsets), as that is more recognizable as an offset. On 24 August 2016 12:40:16 p.m. Robert Elz <kre@munnari.OZ.AU> wrote:
Date: Tue, 23 Aug 2016 16:55:42 -0700 From: Paul Eggert <eggert@cs.ucla.edu> Message-ID: <1471996545-960-1-git-send-email-eggert@cs.ucla.edu>
I am not a fan of this change in general, I think UTC-1 is both more common, and less ambiguous than -01 (from the latter it isn't even obvious that the expression has anything to do with time offsets) but this change in particular ...
| -# Zhongyuan Time ("Central plain Time") UT+8 | +# Zhongyuan Time ("Central plain Time") -08
cannot be right.
kre
On 2016-08-24 08:56, Ian Abbott wrote:
On 24 August 2016 12:40:16 p.m. Robert Elz <kre@munnari.OZ.AU> wrote:
Date: Tue, 23 Aug 2016 16:55:42 -0700 From: Paul Eggert <eggert@cs.ucla.edu> Message-ID: <1471996545-960-1-git-send-email-eggert@cs.ucla.edu> I am not a fan of this change in general, I think UTC-1 is both more common, and less ambiguous than -01 (from the latter it isn't even obvious that the expression has anything to do with time offsets) but this change in particular ... | -# Zhongyuan Time ("Central plain Time") UT+8 | +# Zhongyuan Time ("Central plain Time") -08 cannot be right. To me, UTC-1 looks too much like a traditional Unix TZ value with negated offset, leading to possible confusion about the direction of the offset. My personal preference would be to use the ±HHMM format (with non-negated offsets), as that is more recognizable as an offset.
I am concerned about: * the downstream effect of these changes on client code * changes like that resulting in a previous banning from the list * duplication of the numeric offset in a useless text string already available as a different format string, and the subsequent need to change that string every time an offset changes * the lack of any legislative or widespread community push towards making unnecessary changes to the data * the lack of any coordination with downstream distributors and consumers e.g. travel industry, airlines, to assess the impact * political impact from outrage by American, Canadian, European, etc. output consumers, managers, IT managers, programmers when their favourite TLA gets replaced by some number based on the UK * increasing possibility of a competing fork as authoritative for large numbers of downstream distributors, hosted by a commercial or political organization with an interest in standards. -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
Brian Inglis wrote:
I am concerned about: * the downstream effect of these changes on client code
We have had numeric time zone abbreviations in tzdata since release 2016b, and client code seems to be doing OK.
* duplication of the numeric offset in a useless text string already available as a different format string, and the subsequent need to change that string every time an offset changes
Yes, which is why I'd eventually like to change tzdata source to use %z instead. I've deferred this because I want the relevant zic.c changes to make their way out to downstream platforms. Once this happens, the duplication can be removed.
* the lack of any legislative or widespread community push towards making unnecessary changes to the data
Look at the bright side: thank goodness the U.N. isn't harassing us about this! We'd never get anything done. (:-) Seriously - whether the changes are necessary depends on how seriously one considers invented data to be. I view the matter seriously enough to want to fix the problem when reasonably feasible, as is the case here. Admittedly this is a judgment call.
* the lack of any coordination with downstream distributors and consumers e.g. travel industry, airlines, to assess the impact
Coordination can be done via this mailing list. Anybody in the travel industry, etc. is welcome to report problems they run into because (say) in South Kazakhstan the GNU/Linux 'date' command now outputs "+06" rather than "ALMT". Although the absence of such email does not mean no problems exist, any such problems are likely to be minor given that tzdata 2016d and later have been in widespread use for months without serious squawks from users.
* political impact from outrage by American, Canadian, European, etc. output consumers, managers, IT managers, programmers when their favourite TLA gets replaced by some number based on the UK
This shouldn't be a problem, as there are no plans to replace common English-language abbreviations like "PST" and "CEST". The goal is only to remove invented abbreviations like "ALMT".
On Aug 24, 2016, at 11:21 AM, Brian Inglis <Brian.Inglis@systematicsw.ab.ca> wrote:
I am concerned about: * the downstream effect of these changes on client code * changes like that resulting in a previous banning from the list * duplication of the numeric offset in a useless text string already available as a different format string, and the subsequent need to change that string every time an offset changes * the lack of any legislative or widespread community push towards making unnecessary changes to the data * the lack of any coordination with downstream distributors and consumers e.g. travel industry, airlines, to assess the impact * political impact from outrage by American, Canadian, European, etc. output consumers, managers, IT managers, programmers when their favourite TLA gets replaced by some number based on the UK * increasing possibility of a competing fork as authoritative for large numbers of downstream distributors, hosted by a commercial or political organization with an interest in standards.
Presumably you're commenting on another patch, as *this* patch only changes comments.
Robert Elz wrote:
I think UTC-1 is both more common, and less ambiguous than -01
You make a good point that "UTC-1" is less ambiguous in general English text. Unfortunately in tzdata commentary "UTC-1" is often not technically correct, as UTC is not defined for older time stamps. With this in mind, how about if we change that commentary to use "UT -01" instead, as in the attached proposed patch. This should be clear enough within the tzdata context. The space after the "UT" encourages shorthands like "switch from UT -09 to -08" without having to repeat the "UT" all the time.
| -# Zhongyuan Time ("Central plain Time") UT+8 | +# Zhongyuan Time ("Central plain Time") -08
cannot be right.
Thanks, good catch. Also fixed in the attached.
On Wed 2016-08-24T21:42:19 -0700, Paul Eggert hath writ:
With this in mind, how about if we change that commentary to use "UT -01" instead, as in the attached proposed patch. This should be clear enough within the tzdata context.
The use of the word "Universal" comes from the 1884 International Meridian Conference, is consistent with North American railroad time zones of 1883, and from the 14th century onward can be differenced to within the relevant precision with the civil time of any localities which used equinoctial hours. I think that matches the tzdata context. -- Steve Allen <sla@ucolick.org> WGS-84 (GPS) UCO/Lick Observatory--ISB 260 Natural Sciences II, Room 165 Lat +36.99855 1156 High Street Voice: +1 831 459 3046 Lng -122.06015 Santa Cruz, CA 95064 http://www.ucolick.org/~sla/ Hgt +250 m
On 25/08/16 05:42, Paul Eggert wrote:
I think UTC-1 is both more common, and less ambiguous than -01
You make a good point that "UTC-1" is less ambiguous in general English text. Unfortunately in tzdata commentary "UTC-1" is often not technically correct, as UTC is not defined for older time stamps.
With this in mind, how about if we change that commentary to use "UT -01" instead, as in the attached proposed patch. This should be clear enough within the tzdata context. The space after the "UT" encourages shorthands like "switch from UT -09 to -08" without having to repeat the "UT" all the time.
I think this does read better - "within the tzdata context" - which simply needs a novice reader to be aware when one can mentally think UTC or even GMT in a different context. Displaying local times where one has sufficient information to show the correct TIMEZONE is somewhat different to trying to guess that from a simple offset on a single date string. -- 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
participants (12)
-
Alexander Belopolsky -
Brian Inglis -
Derick Rethans -
Guy Harris -
Ian Abbott -
Lester Caine -
Paul Eggert -
Paul_Koning@dell.com -
Random832 -
Robert Elz -
Steve Allen -
Tim Parenti