- tz - lists.iana.org

[PROPOSED] * tz-link.htm: Improve citations to ISO standards.
by Paul Eggert Nov. 13, 2017

Nov. 13, 2017

--- tz-link.htm | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/tz-link.htm b/tz-link.htm index 93bcbae..0684ed1 100644 --- a/tz-link.htm +++ b/tz-link.htm @@ -318,8 +318,11 @@ Database Parser</a> is a <a href="https://en.wikipedia.org/wiki/C%2B%2B">C++</a> parser and runtime library that is <a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2017/p0355r4.html">moving -forward</a> for inclusion in the <a -href="https://isocpp.org/std/the-standard">ISO C++ standard</a>. +forward</a> for inclusion in the next iteration of <a +href="https://isocpp.org/std/the-standard"><abbr +title="International Organization for Standardization">ISO</abbr> +International Standard ISO/IEC 14882:2017(E) – Programming +Language C++</a>. It is freely available under the <abbr title="Massachusetts Institute of Technology">MIT</abbr> license.</li> <li><a id="ICU" href="http://site.icu-project.org">International Components for @@ -862,10 +865,9 @@ both <abbr title="Locale Data Markup Language">LDML</abbr> the international standard date and time notation</a> is a good summary of <a -href="https://www.iso.org/standard/40874.html"><abbr -title="International Organization for Standardization">ISO</abbr> +href="https://www.iso.org/standard/40874.html"><abbr>ISO</abbr> 8601:2004 – Data elements and interchange formats – Information -interchange – Representation of dates and times</a>.</li> +interchange – Representation of dates and times</a>.</li> <li> <a href="https://www.w3.org/TR/xmlschema-2/#dateTime"><abbr>XML</abbr> Schema: Datatypes – dateTime</a> specifies a format inspired by -- 2.7.4

1 0

Re: [tz] [PATCH] add attribute nonstring
by Paul Eggert Nov. 12, 2017

Nov. 12, 2017

Thanks for mentioning the problem with GCC 8. If the intent of __attribute__((__nonstring__)) is to consistently mark char arrays that are not necessarily null-terminated strings, then lots of data structures in the tzdb code would need to be marked with this attribute. For example, every member of tzfile.h's 'struct tzhead' would have the attribute, because they are all char arrays that might not be null-terminated. Looking at the proposed glibc patch, it seems its intent is more modest. All it's trying to do is to pacify GCC 8 so that GCC doesn't complain about calls to strncpy and strncat. In that case, a simpler and cleaner fix for tzdb is to stop using strncpy and strncat. (I suspect that the main reason tzdb uses strncpy is that its code is so old that it predates the widespread availability of memcpy.) So I installed the attached patch into tzdb's zic.c and it should be part of the next tzdb release. Perhaps you can this idea elsewhere in the rest of the glibc patch too. It would be a lot of work to consistently change glibc to use __attribute__((__nonstring__)) for its documented purpose. If glibc can avoid calling strncpy and strncat, it won't need __NONSTRING; if not, then I suggest changing this: /* Describes a char array that is not necessarily a NUL-terminated string. */ # define __NONSTRING __attribute__ ((__nonstring__)) to something more like this: /* Describes a char array whose address can safely be passed as the first argument to strncpy and strncat, as the char array is not necessarily a NUL-terminated string. */ # define __NONSTRING __attribute__ ((__nonstring__)) in sys/cdefs.h, so that the more-modest goal of the patch is clearer to the reader. I'll CC: this to tz(a)iana.org as a heads-up there.

2 1

Was Azerbaijan the first government to cite tzdb?
by Paul Eggert Nov. 11, 2017

Nov. 11, 2017

When Azerbaijan's Ministry of Transport, Communications and High Technologies said late last month that Azerbaijan would stay at +04, its announcement mentioned the TZ database. See: [Azerbaijan will not translate time] (in Russian). Sputnik. 2017-10-29. https://news.rambler.ru/caucasus/38277699-azerbaydzhan-ne-stanet-perevodit-… Initially I thought this was a first, but it turns out that the same ministry also mentioned tzdb (though not by name) in March 2016, here: Recommendations in connection with abolition of daylight saving time. http://www.mincom.gov.az/media-en/news-2/details/12011 (Azerbaijani and Russian translations are available.) Is the March 2016 announcement the first time a government has cited tzdb, or can readers come up with earlier examples?

7 9

Time zones, daylight saving, and cancer risk
by Paul Eggert Nov. 11, 2017

Nov. 11, 2017

In 2011 Mikhail Borisenkov of the Komi Science Center in Syktyvkar, Russia reported that latitude and longitude can affect cancer rates. In particular he found that in Russia, position within a time zone explained 15% of the variability in female breast cancer mortality. Similar results have now been reported in the US. Neil Caporaso and colleagues at the National Cancer Institute in Bethesda, Maryland recently found a significant association between time zone position and cancer incidence. They estimated that the risk of breast cancer is 12% higher at the western extreme of a US time zone compared to the eastern extreme. Other cancers show similar (but smaller) effects. A plausible explanation is that ill-timed light increases cancer risk by disrupting circadian rhythm. This effect has been known for some time in other respects: for example, blind women have a significantly lower risk for breast cancer, possibly because melatonin offers a protective effect and nocturnal exposure to visible light suppresses melatonin secretion. This is currently an active area of research: the 2017 Nobel Prizes in Physiology or Medicine went to circadian-rhythm researchers. Perhaps we should not take Ben Franklin's "early to bed and early to rise" advice to an extreme, as daylight saving time (or more generally, moving time zones eastward) can significantly increase cancer risk. ---- Stevens RG. Breast cancer risk higher in western parts of time zones; is electric light to blame? The Conversation. 2017-10-19. https://theconversation.com/breast-cancer-risk-higher-in-western-parts-of-t… Gu F, Xu S, Devesa SS et al. Longitude position in a time zone and cancer risk in the United States. Cancer Epidem Biomarkers Prev. 2017-08-01;26(8):1306-11 http://dx.doi.org/10.1158/1055-9965.EPI-16-1029 Borisenkov MF. Latitude of residence and position in time zone are predictors of cancer incidence, cancer mortality, and life expectancy at birth. Chronobiology Int. 2011-01-13;28(2):155-62. http://dx.doi.org/10.3109/07420528.2010.541312

1 0

Fwd: Howard Hinnant's tz Library (was Beginner's help request)
by Bill Seymour Nov. 9, 2017

Nov. 9, 2017

Oops...meant this for the list, not just Daniel. --bs ---------- Forwarded message ---------- From: Bill Seymour <stdbill.h(a)pobox.com> Date: Wed, Nov 8, 2017 at 2:16 PM Subject: Howard Hinnant's tz Library (was Beginner's help request) To: Daniel Ford <dfnojunk(a)gmail.com> Yes, Howard's (exquisite in my opinion) library is specifically for C++, and is moving forward for inclusion in the ISO standard. (Indeed, a subgroup gave it unanimous consent just this morning.) >From http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2017/p0355r4.html: "The implementation has been ported to Windows, Linux, Android, macOS and iOS." I've BCCd Howard in case he has anything more to say about it (although I wouldn't be surprised if he already follows this list anyway). --Bill Seymour On Wed, Nov 8, 2017 at 12:38 AM, Daniel Ford <dfnojunk(a)gmail.com> wrote: > Oops, looks like I was mistaken. Howard's library appears to be not (specifically) for Arduino, but a C++ library for Windows (and maybe other) platforms. Maybe it will compile in the Arduino IDE, though I suspect it will be problematic, if possible at all. > > And I've so far found only one TZdb mirror that keeps a current copy of the data - very disappointing. It's a shame the whole TZdb scheme is so user-unfriendly. Quite discouraging. > > Regards, > Daniel > > > > -----Original Message----- > From: Daniel Ford [mailto:dfnojunk@gmail.com] > Sent: Saturday, November 04, 2017 7:03 PM > To: 'Time zone mailing list' > Subject: RE: [tz] Beginner's help request > > Woohoo! I've discovered (and downloaded) an Arduino library, written by Howard E. Hinnant: > > "This timezone library is a complete parser of the IANA timezone database. It provides for an easy way to access all of the data in this database, using the types from "date.h" and <chrono>. The IANA database also includes data on leap seconds, and this library provides utilities to compute with that information as well." > > All I need to find now are established TZdb mirrors that keep their copy up-to-date, so I don't overload the master TZdb with queries. Can anyone point me to any, please? > > Regards, > Daniel > --------------- > Daniel Ford (Gerroa, Australia)

2 1

Regarding Wikipedia entry
by Jens Tröger Nov. 8, 2017

Nov. 8, 2017

Hi, This is regarding the following table: https://en.wikipedia.org/wiki/List_of_tz_database_time_zones#List I believe that the links in the first column CC are incorrect: they link to [[ISO_3166-1:CI|CI]] (link to the country) instead of [[ISO_3166-2:CI|CI]] (link to the timezone page) That applies to _all_ entries in the first column. Cheers, Jens -- Jens Tröger http://savage.light-speed.de/

9 12

Turkey reintroduces DST next year
by Kıvanç Yazan Nov. 8, 2017

Nov. 8, 2017

Turkey will roll hours back on 10/28/2018 04:00AM. This means going back to EU rule after two years of staying in UTC+3. Here's a link to news article: https://www.cnnturk.com/turkiye/son-dakika-yaz-saati-uygulamasi-sona-erecek Here's a link to official paper: http://www.resmigazete.gov.tr/eskiler/2017/10/20171028-5.pdf A proposed patch is attached, thanks! Sincerely, Kivanc Yazan

4 6

[PROPOSED] Cite "Eerie, Indiana was a few dimensions ahead of its time"
by Paul Eggert Nov. 8, 2017

Nov. 8, 2017

* tz-art.htm: Add URL. --- tz-art.htm | 3 +++ 1 file changed, 3 insertions(+) diff --git a/tz-art.htm b/tz-art.htm index 920d6e7..429dd63 100644 --- a/tz-art.htm +++ b/tz-art.htm @@ -144,6 +144,9 @@ hinges on whether or not Russia observes daylight saving time. "The Lost Hour", Eerie, Indiana, episode 10, NBC, 1991-12-01. Despite Indiana's then-lack of DST, Marshall changes his clock with unusual consequences. +See "<a +href="https://www.avclub.com/eerie-indiana-was-a-few-dimensions-ahead-of-its-time…">Eerie, +Indiana was a few dimensions ahead of its time</a>". </li> <li> "Time Tunnel", The Adventures of Pete & Pete, season 2, episode 5, -- 2.7.4

4 7

vlog on personal timezones
by Zefram Nov. 8, 2017

Nov. 8, 2017

Here's a vlog that may be of interest to people on this list. It's CGP Grey, whose "Daylight Saving Time Explained" video has previously been mentioned here, taking a three-day trip to Las Vegas (America/Los_Angeles) from Britain (Europe/London). Rather than live with the jet lag, he decides to keep his circadian rhythm on London time throughout the trip. As he comments, the 24-hour culture of Las Vegas is particularly amenable to maintaining a non-local timezone. https://www.youtube.com/watch?v=f-mHLBD64HM -zefram

2 1

[PROPOSED] Be more consistent about UT vs UTC
by Paul Eggert Nov. 8, 2017

Nov. 8, 2017

* NEWS, africa, asia, australasia, europe, localtime.c: * newctime.3, newtzset.3, northamerica, southamerica, theory.html: * tz-link.htm, tzselect.ksh, zdump.c, zic.8, zic.c: Be more consistent about using "UT" instead of "UTC" when talking about timestamps that might predate the introduction of UTC. * tzselect.ksh: Use AEST instead of the (obsolescent) abbreviation GST when talking about UT offsets. --- NEWS | 29 +++++++++++++++++------------ africa | 2 +- asia | 14 +++++++------- australasia | 4 ++-- europe | 6 +++--- localtime.c | 2 +- newctime.3 | 2 +- newtzset.3 | 20 ++++++++++---------- northamerica | 2 +- southamerica | 4 ++-- theory.html | 6 +++--- tz-link.htm | 14 +++++++------- tzselect.ksh | 5 +++-- zdump.c | 14 +++++++------- zic.8 | 4 ++-- zic.c | 2 +- 16 files changed, 68 insertions(+), 62 deletions(-) diff --git a/NEWS b/NEWS index de81afc..2254650 100644 --- a/NEWS +++ b/NEWS @@ -33,6 +33,11 @@ Unreleased, experimental changes that have snprintf and use pre-C99 compilers. (Problem reported by Jon Skeet.) + Changes to code + + Diagnostis and commentary are now more careful about + distinguishing UT from UTC. + Release 2017c - 2017-10-20 14:49:34 -0700 @@ -929,8 +934,8 @@ Release 2015f - 2015-08-10 18:06:56 -0700 (Thanks to Jon Skeet and Arthur David Olson.) Constraints on simultaneity are now documented. - The two characters '%z' in a zone format now stand for the UTC - offset, e.g., '-07' for seven hours behind UTC and '+0530' for + The two characters '%z' in a zone format now stand for the UT + offset, e.g., '-07' for seven hours behind UT and '+0530' for five hours and thirty minutes ahead. This better supports time zone abbreviations conforming to POSIX.1-2001 and later. @@ -1053,13 +1058,13 @@ Release 2015c - 2015-04-11 08:55:55 -0700 The spring 1988 transition was 1988-10-09, not 1988-10-02. The fall 1990 transition was 1990-03-11, not 1990-03-18. - Assume no UTC offset change for Pacific/Easter on 1890-01-01, + Assume no UT offset change for Pacific/Easter on 1890-01-01, and omit all transitions on Pacific/Easter from 1942 through 1946 since we have no data suggesting that they existed. One more zone has been turned into a link, as it differed from an existing zone only for older time stamps. As usual, - this change affects UTC offsets in pre-1970 time stamps only. + this change affects UT offsets in pre-1970 time stamps only. The zone's old contents have been moved to the 'backzone' file. The affected zone is America/Montreal. @@ -1089,7 +1094,7 @@ Release 2015b - 2015-03-19 23:28:11 -0700 Some more zones have been turned into links, when they differed from existing zones only for older time stamps. As usual, - these changes affect UTC offsets in pre-1970 time stamps only. + these changes affect UT offsets in pre-1970 time stamps only. Their old contents have been moved to the 'backzone' file. The affected zones are: America/Antigua, America/Cayman, Pacific/Midway, and Pacific/Saipan. @@ -1141,7 +1146,7 @@ Release 2015a - 2015-01-29 22:35:20 -0800 Some more zones have been turned into links, when they differed from existing zones only for older time stamps. As usual, - these changes affect UTC offsets in pre-1970 time stamps only. + these changes affect UT offsets in pre-1970 time stamps only. Their old contents have been moved to the 'backzone' file. The affected zones are: Asia/Aden, Asia/Bahrain, Asia/Kuwait, and Asia/Muscat. @@ -1188,7 +1193,7 @@ Release 2014j - 2014-11-10 17:37:11 -0800 Some more zones have been turned into links, when they differed from existing zones only for older time stamps. As usual, - these changes affect UTC offsets in pre-1970 time stamps only. + these changes affect UT offsets in pre-1970 time stamps only. Their old contents have been moved to the 'backzone' file. The affected zones are: Africa/Addis_Ababa, Africa/Asmara, Africa/Dar_es_Salaam, Africa/Djibouti, Africa/Kampala, @@ -1278,7 +1283,7 @@ Release 2014h - 2014-09-25 18:59:03 -0700 Some more zones have been turned into links, when they differed from existing zones only for older timestamps. As usual, - these changes affect UTC offsets in pre-1970 timestamps only. + these changes affect UT offsets in pre-1970 timestamps only. Their old contents have been moved to the 'backzone' file. The affected zones are: Africa/Blantyre, Africa/Bujumbura, Africa/Gaborone, Africa/Harare, Africa/Kigali, Africa/Lubumbashi, @@ -1363,7 +1368,7 @@ Release 2014g - 2014-08-28 12:31:23 -0700 Some more zones have been turned into links, when they differed from existing zones only for older timestamps. As usual, - these changes affect UTC offsets in pre-1970 timestamps only. + these changes affect UT offsets in pre-1970 timestamps only. Their old contents have been moved to the 'backzone' file. The affected zones are: Africa/Bangui, Africa/Brazzaville, Africa/Douala, Africa/Kinshasa, Africa/Libreville, Africa/Luanda, @@ -1513,7 +1518,7 @@ Release 2014f - 2014-08-05 17:42:36 -0700 standard and daylight saving time the abbreviations are AEST and AEDT instead of the former EST for both; similarly, ACST/ACDT, ACWST/ACWDT, and AWST/AWDT are now used instead of the former CST, CWST, and WST. - This change does not affect UTC offsets, only time zone abbreviations. + This change does not affect UT offsets, only time zone abbreviations. (Thanks to Rich Tibbett and many others.) Asia/Novokuznetsk shifts from NOVT to KRAT (remaining on UT +07) @@ -1550,8 +1555,8 @@ Release 2014f - 2014-08-05 17:42:36 -0700 Treindl sent helpful translations of two papers by Guo Qingsheng.) Some zones have been turned into links, when they differed from existing - zones only for older UTC offsets where data entries were likely invented. - These changes affect UTC offsets in pre-1970 timestamps only. This is + zones only for older UT offsets where data entries were likely invented. + These changes affect UT offsets in pre-1970 timestamps only. This is similar to the change in release 2013e, except this time for western Africa. The affected zones are: Africa/Bamako, Africa/Banjul, Africa/Conakry, Africa/Dakar, Africa/Freetown, Africa/Lome, diff --git a/africa b/africa index 3a60bc2..be44580 100644 --- a/africa +++ b/africa @@ -425,7 +425,7 @@ Link Africa/Nairobi Indian/Mayotte # # The Nautical Almanac for the Year 1970, p 264, is the source for -0:44:30. # -# In 1972 Liberia was the last country to switch from a UTC offset +# In 1972 Liberia was the last country to switch from a UT offset # that was not a multiple of 15 or 20 minutes. The 1972 change was on # 1972-01-07, according to an entry dated 1972-01-04 on p 330 of: # Presidential Papers: First year of the administration of diff --git a/asia b/asia index ac39af3..91076fd 100644 --- a/asia +++ b/asia @@ -50,7 +50,7 @@ # 9:00 KST KDT Korea when at +09 # 9:30 ACST Australian Central Standard Time # Otherwise, these tables typically use numeric abbreviations like +03 -# and +0330 for integer hour and minute UTC offsets. Although earlier +# and +0330 for integer hour and minute UT offsets. Although earlier # editions invented alphabetic time zone abbreviations for every # offset, this did not reflect common practice. # @@ -647,17 +647,17 @@ Zone Asia/Hong_Kong 7:36:42 - LMT 1904 Oct 30 # time", in which abolished the adoption of Western Standard Time in # western islands (listed above), which means the whole Japan # territory, including later occupations, adopt Japan Central Time -# (UTC+9). The adoption began on Oct 1, 1937. The original text can +# (UT+9). The adoption began on Oct 1, 1937. The original text can # be found on Wikisource: # https://ja.wikisource.org/wiki/明治二十八年勅令第百六十七號標準時ニ關スル件中改正ノ件 # -# That is, the time zone of Taipei switched to UTC+9 on Oct 1, 1937. +# That is, the time zone of Taipei switched to UT+9 on Oct 1, 1937. # From Yu-Cheng Chuang (2014-07-02): -# I've found more evidence about when the time zone was switched from UTC+9 -# back to UTC+8 after WW2. I believe it was on Sep 21, 1945. In a document +# I've found more evidence about when the time zone was switched from UT+9 +# back to UT+8 after WW2. I believe it was on Sep 21, 1945. In a document # during Japanese era [1] in which the officer told the staff to change time -# zone back to Western Standard Time (UTC+8) on Sep 21. And in another +# zone back to Western Standard Time (UT+8) on Sep 21. And in another # history page of National Cheng Kung University [2], on Sep 21 there is a # note "from today, switch back to Western Standard Time". From these two # materials, I believe that the time zone change happened on Sep 21. And @@ -1505,7 +1505,7 @@ Rule Japan 1950 1951 - May Sun>=1 2:00 1:00 D # # ...the Showa Emperor announced Ordinance No. 529 of Showa Year 12 ... which # means the whole Japan territory, including later occupations, adopt Japan -# Central Time (UTC+9). The adoption began on Oct 1, 1937. +# Central Time (UT+9). The adoption began on Oct 1, 1937. # https://ja.wikisource.org/wiki/明治二十八年勅令第百六十七號標準時ニ關スル件中改正ノ件 # Zone NAME GMTOFF RULES FORMAT [UNTIL] diff --git a/australasia b/australasia index 5f7c86d..9a968e4 100644 --- a/australasia +++ b/australasia @@ -683,8 +683,8 @@ Zone Pacific/Guadalcanal 10:39:48 - LMT 1912 Oct # Honiara # From Steffen Thorsen (2012-07-25) # ... we double checked by calling hotels and offices based in Tokelau asking # about the time there, and they all told a time that agrees with UTC+13.... -# Shanks says UTC-10 from 1901 [but] ... there is a good chance the change -# actually was to UTC-11 back then. +# Shanks says UT-10 from 1901 [but] ... there is a good chance the change +# actually was to UT-11 back then. # # From Paul Eggert (2012-07-25) # A Google Books snippet of Appendix to the Journals of the House of diff --git a/europe b/europe index cf6d7e4..7bca59b 100644 --- a/europe +++ b/europe @@ -2772,9 +2772,9 @@ Zone Asia/Omsk 4:53:30 - LMT 1919 Nov 14 # # https://regnum.ru/news/society/1957270.html # has some historical data for Altai Krai: -# before 1957: west part on UTC+6, east on UTC+7 -# after 1957: UTC+7 -# since 1995: UTC+6 +# before 1957: west part on UT+6, east on UT+7 +# after 1957: UT+7 +# since 1995: UT+6 # http://barnaul.rusplt.ru/index/pochemu_altajskij_kraj_okazalsja_v_neprivych… # confirms that and provides more details including 1995-05-28 transition date. diff --git a/localtime.c b/localtime.c index 2e1d621..9b8266a 100644 --- a/localtime.c +++ b/localtime.c @@ -1982,7 +1982,7 @@ time2sub(struct tm *const tmp, && ((BIGGEST (INT_FAST32_MIN, LONG_MIN) + yourtm.TM_GMTOFF) <= mytm.TM_GMTOFF)))) { - /* MYTM matches YOURTM except with the wrong UTC offset. + /* MYTM matches YOURTM except with the wrong UT offset. YOURTM.TM_GMTOFF is plausible, so try it instead. It's OK if YOURTM.TM_GMTOFF contains uninitialized data, since the guess gets checked. */ diff --git a/newctime.3 b/newctime.3 index 8b89935..b376ae1 100644 --- a/newctime.3 +++ b/newctime.3 @@ -191,7 +191,7 @@ extra initial argument specifying the time zone to be used for conversion. If .B zone -is null, UTC is used; otherwise, +is null, UT is used; otherwise, .B zone should be have been allocated by .I tzalloc diff --git a/newtzset.3 b/newtzset.3 index c3e22dc..beee20a 100644 --- a/newtzset.3 +++ b/newtzset.3 @@ -61,7 +61,7 @@ If the implied call to .B tzalloc fails, .I tzset -falls back on UTC. +falls back on Universal Time (UT). .PP If .B TZ @@ -74,7 +74,7 @@ in the system time conversion information directory, is used. If .B TZ is the empty string, -Universal Time (UT) is used, with the abbreviation "UTC" +UT is used, with the abbreviation "UTC" and without leap second correction; please see .IR newctime (3) for more about UT, UTC, and leap seconds. If @@ -256,22 +256,22 @@ extensions to POSIX. .TP .B EST5 stands for US Eastern Standard -Time (EST), 5 hours behind UTC, without daylight saving. +Time (EST), 5 hours behind UT, without daylight saving. .TP .B FJT\*-12FJST,M11.1.0,M1.3.4/75 stands for Fiji Time (FJT) and Fiji Summer Time (FJST), 12 hours ahead -of UTC, springing forward on November's first Sunday at 02:00, and +of UT, springing forward on November's first Sunday at 02:00, and falling back on January's third Thursday at 75:00 (i.e., 03:00 on the first Sunday on or after January 18). .TP .B IST\*-2IDT,M3.4.4/26,M10.5.0 stands for Israel Standard Time (IST) and Israel Daylight Time (IDT), -2 hours ahead of UTC, springing forward on March's fourth +2 hours ahead of UT, springing forward on March's fourth Thursday at 26:00 (i.e., 02:00 on the first Friday on or after March 23), and falling back on October's last Sunday at 02:00. .TP .B WART4WARST,J1/0,J365/25 -stands for Western Argentina Summer Time (WARST), 3 hours behind UTC. +stands for Western Argentina Summer Time (WARST), 3 hours behind UT. There is a dummy fall-back transition on December 31 at 25:00 daylight saving time (i.e., 24:00 standard time, equivalent to January 1 at 00:00 standard time), and a simultaneous spring-forward transition on @@ -282,9 +282,9 @@ is a placeholder. .TP .B WGT3WGST,M3.5.0/\*-2,M10.5.0/\*-1 stands for Western Greenland Time (WGT) and Western Greenland Summer -Time (WGST), 3 hours behind UTC, where clocks follow the EU rules of -springing forward on March's last Sunday at 01:00 UTC (\-02:00 local -time) and falling back on October's last Sunday at 01:00 UTC +Time (WGST), 3 hours behind UT, where clocks follow the EU rules of +springing forward on March's last Sunday at 01:00 UT (\-02:00 local +time) and falling back on October's last Sunday at 01:00 UT (\-01:00 local time). .PP If no @@ -297,7 +297,7 @@ by the file .B posixrules in the system time conversion information directory are used, with the -standard and summer time offsets from UTC replaced by those specified by +standard and summer time offsets from UT replaced by those specified by the .I offset values in diff --git a/northamerica b/northamerica index e5d3eca..505300a 100644 --- a/northamerica +++ b/northamerica @@ -1896,7 +1896,7 @@ Zone America/Edmonton -7:33:52 - LMT 1906 Sep # manager of the Creston & District Museum. The article was written in May 2009. # http://www.ilovecreston.com/?p=articles&t=spec&ar=260 # According to the article, Creston has not changed its clocks since June 1918. -# i.e. Creston has been stuck on UTC-7 for 93 years. +# i.e. Creston has been stuck on UT-7 for 93 years. # Dawson Creek, on the other hand, changed its clocks as recently as April 1972. # Unfortunately the exact date for the time change in June 1918 remains diff --git a/southamerica b/southamerica index bbae226..e0b3265 100644 --- a/southamerica +++ b/southamerica @@ -25,7 +25,7 @@ # https://www.jstor.org/stable/1774359 # # These tables use numeric abbreviations like -03 and -0330 for -# integer hour and minute UTC offsets. Although earlier editions used +# integer hour and minute UT offsets. Although earlier editions used # alphabetic time zone abbreviations, these abbreviations were # invented and did not reflect common practice. @@ -1068,7 +1068,7 @@ Zone America/Rio_Branco -4:31:12 - LMT 1914 # From Paul Eggert (2015-04-03): # Shanks & Pottenger says America/Santiago introduced standard time in -# 1890 and rounds its UTC offset to 70W40; guess that in practice this +# 1890 and rounds its UT offset to 70W40; guess that in practice this # was the same offset as in 1916-1919. It also says Pacific/Easter # standardized on 109W22 in 1890; assume this didn't change the clocks. # diff --git a/theory.html b/theory.html index 965135d..3e686a0 100644 --- a/theory.html +++ b/theory.html @@ -598,7 +598,7 @@ POSIX has the following properties and limitations. and daylight saving time (DST) zone names. Starting with POSIX.1-2001, <var>std</var> and <var>dst</var> may also be - in a quoted form like '<code><UTC+10></code>'; this allows + in a quoted form like '<code><+09></code>'; this allows "<code>+</code>" and "<code>-</code>" in the names. </dd> <dt><var>offset</var></dt><dd> @@ -646,7 +646,7 @@ POSIX has the following properties and limitations. </dd> </dl> Here is an example POSIX TZ string for New Zealand after 2007. - It says that standard time (NZST) is 12 hours ahead of UTC, + It says that standard time (NZST) is 12 hours ahead of UT, and that daylight saving time (NZDT) is observed from September's last Sunday at 02:00 until April's first Sunday at 03:00: @@ -678,7 +678,7 @@ POSIX has the following properties and limitations. applications that an administrator wants used only at certain times – without regard to whether the user has fiddled the TZ environment - variable. While an administrator can "do everything in UTC" to get + variable. While an administrator can "do everything in UT" to get around the problem, doing so is inconvenient and precludes handling daylight saving time shifts - as might be required to limit phone calls to off-peak hours.) diff --git a/tz-link.htm b/tz-link.htm index 835df40..2a8a486 100644 --- a/tz-link.htm +++ b/tz-link.htm @@ -432,7 +432,7 @@ It is freely available under the <abbr>LGPL</abbr>.</li> implementation of a binary file reader. It is freely available under the Apache License.</li> <li><a href="https://github.com/google/cctz">CCTZ</a> is a simple C++ -library that translates between <abbr>UTC</abbr> and civil time and +library that translates between <abbr>UT</abbr> and civil time and can read binary files. It is freely available under the Apache License.</li> <li><a href="http://bmsi.com/java/#TZ">ZoneInfo.java</a> @@ -660,7 +660,7 @@ world time zone boundaries distributed under the href="https://en.wikipedia.org/wiki/Territorial_waters">territorial waters</a> of any nation uses that nation's time. In international waters, time zone boundaries are meridians 15° apart, except that -<abbr>UTC</abbr>−12 and <abbr>UTC</abbr>+12 are each 7.5° +<abbr>UT</abbr>−12 and <abbr>UT</abbr>+12 are each 7.5° wide and are separated by the 180° meridian (not by the International Date Line, which is for land and territorial waters only). A captain can change ship's @@ -884,10 +884,10 @@ protocols.</li> Formats on the Web</a> surveys web- and Internet-oriented date and time formats.</li> <li>Alphabetic time zone abbreviations should not be used as unique -identifiers for <abbr>UTC</abbr> offsets as they are ambiguous in +identifiers for <abbr>UT</abbr> offsets as they are ambiguous in practice. For example, in English-speaking North America -"<abbr>CST</abbr>" denotes 6 hours behind <abbr>UTC</abbr>, -but in China it denotes 8 hours ahead of <abbr>UTC</abbr>, +"<abbr>CST</abbr>" denotes 6 hours behind <abbr>UT</abbr>, +but in China it denotes 8 hours ahead of <abbr>UT</abbr>, and French-speaking North Americans prefer "<abbr title="Heure Normale du Centre">HNC</abbr>" to "<abbr>CST</abbr>". The <code><abbr>tz</abbr></code> @@ -895,7 +895,7 @@ database contains English abbreviations for many time stamps; unfortunately some of these abbreviations were merely the database maintainers' inventions, and are gradually being removed.</li> <li>Numeric time zone abbreviations typically count hours east of -<abbr>UTC</abbr>, e.g., +09 for Japan and +<abbr>UT</abbr>, e.g., +09 for Japan and −10 for Hawaii. However, the <abbr>POSIX</abbr> <code><abbr>TZ</abbr></code> environment variable uses the opposite convention. For example, one might use <code><abbr>TZ</abbr>="<abbr @@ -909,7 +909,7 @@ confusion, handle old time stamps better, and insulate you better from any future changes to the rules. One should never set <abbr>POSIX</abbr> <code><abbr>TZ</abbr></code> to a value like <code>"GMT-9"</code>, though, since this would incorrectly imply that -local time is nine hours ahead of <abbr>UTC</abbr> and the time zone +local time is nine hours ahead of <abbr>UT</abbr> and the time zone is called "<abbr>GMT</abbr>".</li> </ul> <h2 id="see-also">See also</h2> diff --git a/tzselect.ksh b/tzselect.ksh index 759ba5f..d71a95e 100644 --- a/tzselect.ksh +++ b/tzselect.ksh @@ -342,8 +342,9 @@ while while echo >&2 'Please enter the desired value' \ 'of the TZ environment variable.' - echo >&2 'For example, GST-10 is a zone named GST' \ - 'that is 10 hours ahead (east) of UTC.' + echo >&2 'For example, AEST-10 is a zone named AEST' \ + 'that is 10 hours ahead (east) of UT' + echo >&2 'and does not observe daylight saving time.' read TZ $AWK -v TZ="$TZ" 'BEGIN { tzname = "(<[[:alnum:]+-]{3,}>|[[:alpha:]]{3,})" diff --git a/zdump.c b/zdump.c index d4e6084..3cd4f42 100644 --- a/zdump.c +++ b/zdump.c @@ -265,7 +265,7 @@ tzfree(timezone_t env) } #endif /* ! USE_LOCALTIME_RZ */ -/* A UTC time zone, and its initializer. */ +/* A UT time zone, and its initializer. */ static timezone_t gmtz; static void gmtzinit(void) @@ -280,7 +280,7 @@ gmtzinit(void) } } -/* Convert *TP to UTC, storing the broken-down time into *TMP. +/* Convert *TP to UT, storing the broken-down time into *TMP. Return TMP if successful, NULL otherwise. This is like gmtime_r(TP, TMP), except typically faster if USE_LOCALTIME_RZ. */ static struct tm * @@ -730,8 +730,8 @@ adjusted_yday(struct tm const *a, struct tm const *b) } #endif -/* If A is the broken-down local time and B the broken-down UTC for - the same instant, return A's UTC offset in seconds, where positive +/* If A is the broken-down local time and B the broken-down UT for + the same instant, return A's UT offset in seconds, where positive offsets are east of Greenwich. On failure, return LONG_MIN. If T is nonnull, *T is the timestamp that corresponds to A; call @@ -847,10 +847,10 @@ format_local_time(char *buf, size_t size, struct tm const *tm) : my_snprintf(buf, size, "%02d", hh)); } -/* Store into BUF, of size SIZE, a formatted UTC offset for the +/* Store into BUF, of size SIZE, a formatted UT offset for the localtime *TM corresponding to time T. Use ISO 8601 format +HHMMSS, or -HHMMSS for timestamps west of Greenwich; use the - format -00 for unknown UTC offsets. If the hour needs more than + format -00 for unknown UT offsets. If the hour needs more than two digits to represent, extend the length of HH as needed. Otherwise, omit SS if SS is zero, and omit MM too if MM is also zero. @@ -925,7 +925,7 @@ format_quoted_string(char *buf, size_t size, char const *p) %f zone name %L local time as per format_local_time - %Q like "U\t%Z\tD" where U is the UTC offset as for format_utc_offset + %Q like "U\t%Z\tD" where U is the UT offset as for format_utc_offset and D is the isdst flag; except omit D if it is zero, omit %Z if it equals U, quote and escape %Z if it contains nonalphabetics, and omit any trailing tabs. */ diff --git a/zic.8 b/zic.8 index ab95b08..43ef2ce 100644 --- a/zic.8 +++ b/zic.8 @@ -366,7 +366,7 @@ is used to show where the of the time zone abbreviation goes. Alternately, a format can use the pair of characters .B %z -to stand for the UTC offset in the form +to stand for the UT offset in the form .RI \(+- hh , .RI \(+- hhmm , or @@ -376,7 +376,7 @@ using the shortest form that does not lose information, where .IR mm , and .I ss -are the hours, minutes, and seconds east (+) or west (\(mi) of UTC. +are the hours, minutes, and seconds east (+) or west (\(mi) of UT. Alternately, a slash (/) separates standard and daylight abbreviations. diff --git a/zic.c b/zic.c index a3d7383..82e653d 100644 --- a/zic.c +++ b/zic.c @@ -2055,7 +2055,7 @@ abbroffset(char *buf, zic_t offset) minutes = offset % MINSPERHOUR; offset /= MINSPERHOUR; if (100 <= offset) { - error(_("%%z UTC offset magnitude exceeds 99:59:59")); + error(_("%%z UT offset magnitude exceeds 99:59:59")); return "%z"; } else { char *p = buf; -- 2.7.4

7 11