- tz - lists.iana.org

[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", <em>Eerie, Indiana</em>, 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…"><em>Eerie, +Indiana</em> was a few dimensions ahead of its time</a>". </li> <li> "Time Tunnel", <em>The Adventures of Pete & Pete</em>, 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

I'm sure everyone has seen this... but...
by merlyn＠stonehenge.com Nov. 8, 2017

Nov. 8, 2017

https://www.youtube.com/watch?v=-5wpm-gesOY -- Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095 <merlyn(a)stonehenge.com> <URL:http://www.stonehenge.com/merlyn/> Perl/Unix/Dart consulting, Technical writing, Comedy, etc. etc. Still trying to think of something clever for the fourth line of this .sig

2 1

Apple watch crashes if daylight time ends
by Steve Allen Nov. 6, 2017

Nov. 6, 2017

https://www.reddit.com/r/AppleWatch/comments/7aqiw1/series_3_crashes_when_a… Reports that Apple watchOS 4.1 crashes if asked about today's weather (not tomorrow's, etc.) in a zone which is about to end daylight time. -- Steve Allen <sla(a)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

3 2

Massachusetts time zone report
by Steve Allen Nov. 4, 2017

Nov. 4, 2017

Massachusetts has approved a 47 page report on its time zone http://www.eileendonoghue.org/special-commission-approves-time-zone-report/ it cautiously recommends moving to permanent Atlantic standard time. -- Steve Allen <sla(a)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

3 3

Article proposes end of DST, adds interesting historic reference
by Steve Jones Nov. 4, 2017

Nov. 4, 2017

Interesting/amusing article on Fox News this morning (using the wayback machine link to reduce the oppressive spam: https://web.archive.org/web/20171104061246/http://www.foxnew s.com/opinion/2017/11/04/its-time-for-daylight-saving-time- to-fall-back-forever.html The best part was a link to an old gizmodo article containing a well-researched historical reference to Ben Franklin's original proposal for a DST-like policy: https://gizmodo.com/ben-franklins-daylight-saving-time-proposal-was-writte- 1456363759 Further clicking led me to the full letter from Ben: http://www.webexhibits.org/daylightsaving/franklin3.html which I think is tz-art worthy. Steve Jones [image: Emacs!]

2 1

Re: [tz] [IANA #985615] Sudan Time Zone change
by Mohammed Elsir Osman Alebeid Nov. 3, 2017

Nov. 3, 2017

Dear Eggert, This is Mohammed Elsir from Zain, the first mobile operator in Sudan. Actually our mobile network sends the correct time zone which is GMT+2 as seen in below trace. [cid:image015.png@01D353DB.A197A6D0] The thing is that some devices such as most of feature/legacy/old phones accept the sent time zone and change time correctly. But some Android device such as Samsung, Huawei, Lenovo and part of HTC reject the provided time zone and display the time zone based on lookup table inside the handset. Below is an example from Lenovo P2. [cid:image016.png@01D353DB.A197A6D0] Some Handset manufactures such as apple sent messages over the internet asking for handset restart to get the new time zone. Below is an examples. [cid:image003.png@01D353DD.1DA00320] I do appreciate your kind support to contact Android handset manufactures such as Samsung, Huawei and Lenovo asking them about 1. Why their handsets reject the network provided time zone. 2. How can they solve this issue? Should you need further discussion I am available on Skype @ mohammed_elsir_64 or WhatsApp @ +249912311500. Just let me know the appropriate time for you to discuss further. Thanks in advance for your kind support. Best Regards, Mohammed Elsir M.Sc., PMP,ITIL-SO From: Ahmed Ali Ahmed Ali Sent: Wednesday, November 01, 2017 8:18 PM To: Ahmed Ibrahim Ahmed Abdelkareem <Ahmed.AbdElkareem(a)sd.zain.com>; Mohammed Elsir Osman Alebeid <Mohammed.ElsirOsman(a)sd.zain.com>; Mugahed Bakri Mohammed Alhag <Mugahed.Bakri(a)sd.zain.com> Cc: Faisal El Muftah <Faisal.Nourelhuda(a)sd.zain.com>; Nizar Musa <Nizar.Musa(a)sd.zain.com>; Ali Boosh <Ali.Boosh(a)sd.zain.com>; Badr Eldin Abdalla Mohamed Nour <Badr.Nour(a)sd.zain.com> Subject: Fwd: [tz] [IANA #985615] Sudan Time Zone change Dears, Please check the below feedback from IANA Thanks, Sent from Samsung Mobile -------- Original message -------- From: ahmed.atyya(a)ntc.gov.sd<mailto:ahmed.atyya@ntc.gov.sd> Date:11/01/2017 20:19 (GMT+03:00) To: Faisal El Muftah , Ahmed Ali Ahmed Ali , Regulatory , Hiba Abbas Yousif Eltigani , Mohamed Gaafar Ibrahim Bashir Corporate Services - MTN - Sudan , Nafisa Mahmoud Karamalla Corporate Services - MTN - Sudan , Mohammed Abdelraheem Abdelmagid Elkhalifa , Munir Taha Elkabashi Hassan Elfaki Cc: abdelhafiz , Afaf Nijomi , yahia , mohamed elhaj Subject: Fwd: [tz] [IANA #985615] Sudan Time Zone change Dears Please find below email from IANA for your kind revision to find the way out; we will also discuss the proposal of Sudan Embassy regards Ahmed Atyya ----- Forwarded Message ----- From: "Paul Eggert" <eggert(a)cs.ucla.edu<mailto:eggert@cs.ucla.edu>> To: "ahmed atyya" <ahmed.atyya(a)ntc.gov.sd<mailto:ahmed.atyya@ntc.gov.sd>> Cc: "yahia" <yahia(a)ntc.gov.sd<mailto:yahia@ntc.gov.sd>>, "Matt Johnson" <mj1856(a)hotmail.com<mailto:mj1856@hotmail.com>>, "Time Zone Mailing List" <tz(a)iana.org<mailto:tz@iana.org>>, "itisalat" <itisalat(a)ntc.gov.sd<mailto:itisalat@ntc.gov.sd>>, "abdin" <abdin(a)ntc.gov.sd<mailto:abdin@ntc.gov.sd>>, "nadir" <nadir(a)ntc.gov.sd<mailto:nadir@ntc.gov.sd>>, "abdelhafiz" <abdelhafiz(a)ntc.gov.sd<mailto:abdelhafiz@ntc.gov.sd>> Sent: Wednesday, November 1, 2017 7:57:00 PM Subject: Re: [tz] [IANA #985615] Sudan Time Zone change On 11/01/2017 01:35 AM, ahmed.atyya(a)ntc.gov.sd<mailto:ahmed.atyya@ntc.gov.sd> wrote: > With respect to the topic, please be updated that the change was applied successfully, Apple > handsets did the update automatically but Android handsets didn’t. In what sense didn't they change? My Android phone's time zone menu has entries for Cairo, Harare, and Nairobi, but not for Khartoum. If it is a matter of the user's time zone settings, users need to change from (say) Nairobi time to Cairo time. On the other hand, if it is a matter of the time zone supplied from the cellular service company, then this is something for your local cell company to address. > We kindly request to communicate with Google in order to update Android OS with the changes > for the handsets take the time automatically. As I understand it, Google engineers monitor this mailing list and so already know about the time zone change. There is a gap between the time that Google releases software updates, and the time that phones actually change. For example, even though I have a Google Nexus 6P phone and live in the United States, my phone is well behind Google's release schedule: it upgraded over-the-air to Android 8.0 Oreo only last night, even though Oreo was released on August 21 *. Other manufacturers' Android phones are even slower to update. This underscores the importance of governments announcing time zone changes well in advance: we currently recommend one years' advance notice. When other countries have run into similar problems, they've had some luck by contacting the U.S. State Department and asking for its help in adjusting the priorities of commercial providers. I suggest that you contact the U.S. Deputy Chief of Mission in Sudan and ask for his advice for how to proceed. See: https://sd.usembassy.gov/our-relationship/dcm/ https://sd.usembassy.gov/embassy/khartoum/offices-departments/public-affair… From what you tell me, though, the problem is likely to involve the protocols used by your local cellular service providers (that is, the problem may not be in Android at all), so they'll need to be in contact with their suppliers too. [cid:image001.png@01D353B6.A6960840] Ahmed Ahmedali Market Power & Competition Advance Specialist Zain SD Al Mogran, Zain Building Al Ghaba Street P.O Box: 13588 Khartoum Sudan Mobile : +249912398071 Email : Ahmed.Ahmedali(a)sd.zain.com<mailto:Ahmed.Ahmedali@sd.zain.com> Web : www.zain.com<http://www.zain.com> [cid:image005.jpg@01D353DD.1DA00320]<https://twitter.com/ZainSudan> [cid:image007.jpg@01D353DD.1DA00320] <https://facebook.com/ZainSudan/?fref=ts> [cid:image009.jpg@01D353DD.1DA00320] <https://plus.google.com/110542740934974723351> [cid:image011.jpg@01D353DD.1DA00320] <https://instagram.com/zainsudan/> [cid:image013.jpg@01D353DD.1DA00320] <https://linkedin.com/company/3224878?trk=tyah&trkInfo=clickedVertical%3Acom…> [cid:image023.png@01D353DD.1DA00320] <https://youtube.com/user/ZainSudanTV> [cid:image014.png@01D353B6.A6960840] [cid:image2acf2f.BMP@a4b5ec2d.4c95cc79] Mohammed Elsir Osman CT Infrastructure Operation Team Leader Zain SD Al Mogran, Zain Building Al Ghaba Street P.O Box: 13588 Khartoum Sudan Mobile : ++249912311500 Office : +24990001-3256 Email : Mohammed.ElsirOsman(a)sd.zain.com Web : www.zain.com [cid:image1d8d7d.PNG@e9fa88a4.43aeded8]<https://twitter.com/ZainSudan> [cid:imaged5af34.PNG@146f7ddf.4e95af19] <https://facebook.com/ZainSudan/?fref=ts> [cid:image95f784.PNG@eb17dd26.4eb485d3] <https://plus.google.com/110542740934974723351> [cid:imageb1c854.JPG@2f1af4fa.4680f52e] <https://instagram.com/zainsudan/> [cid:imagead7fe1.PNG@0e87976d.42b9ff22] <https://linkedin.com/company/3224878?trk=tyah&trkInfo=clickedVertical%3Acom…> [cid:image108d42.PNG@d8c0b630.439783e1] <https://youtube.com/user/ZainSudanTV> [cid:image400fba.PNG@9f5f39e1.45ab1906]

4 3

Regarding changes of time format the Philippines
by Arati Nov. 3, 2017

Nov. 3, 2017

Hi , We are using tzdb for all our customers. With latest update of tzdb to 2017a, one of the customer came back with issue in time format display in logs. The timezone for this Customer is Asia/Manila i.e. Philippines. Before use on 2017a tzdb , the time displayed is as follows 2017-10-31 16:47:33.930 +0800 After using 2017a tzdb time displayed as 2017-10-31 08:48:38.056 +0000 We observed the same issue using perl DateTime module too. We could see that the time format for this zone is changed from PH%sT to +08/+09. This change is there only in asia file.(Note reverting back this change and recompiling tzdb resolves the issue) We are looking for a solution for this. We are not clear whether some dependent library needs to be upgraded , or it is a bug in tzdb. Kindly address the query and help to resolve the issue. Thanks & Regards, Arati =========================================================== Learn how to protect users, data, and applications with security engineered for the public cloud by Barracuda. http://barracuda.com DISCLAIMER: This e-mail and any attachments to it contain confidential and proprietary material of Barracuda, its affiliates or agents, and is solely for the use of the intended recipient. Any review, use, disclosure, distribution or copying of this transmittal is prohibited except by or on behalf of the intended recipient. If you have received this transmittal in error, please notify the sender and destroy this e-mail and any attachments and all copies, whether electronic or printed. ===========================================================

4 7

Re: [tz] [IANA #985615] Sudan Time Zone change
by Zhouyuxiang Nov. 3, 2017

Nov. 3, 2017

Dears, I'm not that sure. But I guess this is same problem as mine([time zone problem about 2017c] (Zefram)). This just happen in Android system now. Because the tzcode2017c.tar.gz has one error. external\icu\tools\update-tzdata.py Android use this script to update the tz data from IANA via internet. But africa file and backzone file have a duplicated data that made the update script error: # South Sudan Zone Africa/Juba 2:06:24 - LMT 1931 2:00 Sudan CA%sT 2000 Jan 15 12:00 3:00 - EAT So android device could not update the time zone data normally. I deleted one in backzone, then it worked in local. And Zefram told me "No one noticed in advance of release because few people use 'backzone'". So I infer that the old phone and ios system will not use backzone data, so they could update normally. I think you have two way to solve this problem. 1.Wait IANA modify the "backzone" data, so the internet updating could work. 2.Let Android device Manufacturers do this update themselves: a. Delete the duplicated data as I did. b. Modify the update-tzdata.py to update time zone data without internet. ---------------------------------------------------------------------- Message: 1 Date: Thu, 2 Nov 2017 11:19:09 +0000 From: Mohammed Elsir Osman Alebeid <Mohammed.ElsirOsman(a)sd.zain.com> To: "eggert(a)cs.ucla.edu" <eggert(a)cs.ucla.edu> Cc: Ali Boosh <Ali.Boosh(a)sd.zain.com>, "itisalat(a)ntc.gov.sd" <itisalat(a)ntc.gov.sd>, "abdin(a)ntc.gov.sd" <abdin(a)ntc.gov.sd>, "nadir(a)ntc.gov.sd" <nadir(a)ntc.gov.sd>, "tz(a)iana.org" <tz(a)iana.org>, Nizar Musa <Nizar.Musa(a)sd.zain.com>, "abdelhafiz(a)ntc.gov.sd" <abdelhafiz(a)ntc.gov.sd>, Ahmed Ali Ahmed Ali <Ahmed.Ahmedali(a)sd.zain.com>, "yahia(a)ntc.gov.sd" <yahia(a)ntc.gov.sd>, Mugahed Bakri Mohammed Alhag <Mugahed.Bakri(a)sd.zain.com>, Ahmed Ibrahim Ahmed Abdelkareem <Ahmed.AbdElkareem(a)sd.zain.com>, Badr Eldin Abdalla Mohamed Nour <Badr.Nour(a)sd.zain.com>, Faisal El Muftah <Faisal.Nourelhuda(a)sd.zain.com> Subject: Re: [tz] [IANA #985615] Sudan Time Zone change Message-ID: <BE1CCE5C566B134083665B1FF5684AE58BCDD6E4(a)sr-ark-mbxb.sd.zain.com> Content-Type: text/plain; charset="utf-8" Dear Eggert, This is Mohammed Elsir from Zain, the first mobile operator in Sudan. Actually our mobile network sends the correct time zone which is GMT+2 as seen in below trace. [cid:image015.png@01D353DB.A197A6D0] The thing is that some devices such as most of feature/legacy/old phones accept the sent time zone and change time correctly. But some Android device such as Samsung, Huawei, Lenovo and part of HTC reject the provided time zone and display the time zone based on lookup table inside the handset. Below is an example from Lenovo P2. [cid:image016.png@01D353DB.A197A6D0] Some Handset manufactures such as apple sent messages over the internet asking for handset restart to get the new time zone. Below is an examples. [cid:image003.png@01D353DD.1DA00320] I do appreciate your kind support to contact Android handset manufactures such as Samsung, Huawei and Lenovo asking them about 1. Why their handsets reject the network provided time zone. 2. How can they solve this issue? Should you need further discussion I am available on Skype @ mohammed_elsir_64 or WhatsApp @ +249912311500. Just let me know the appropriate time for you to discuss further. Thanks in advance for your kind support. Best Regards, Mohammed Elsir M.Sc., PMP,ITIL-SO From: Ahmed Ali Ahmed Ali Sent: Wednesday, November 01, 2017 8:18 PM To: Ahmed Ibrahim Ahmed Abdelkareem <Ahmed.AbdElkareem(a)sd.zain.com>; Mohammed Elsir Osman Alebeid <Mohammed.ElsirOsman(a)sd.zain.com>; Mugahed Bakri Mohammed Alhag <Mugahed.Bakri(a)sd.zain.com> Cc: Faisal El Muftah <Faisal.Nourelhuda(a)sd.zain.com>; Nizar Musa <Nizar.Musa(a)sd.zain.com>; Ali Boosh <Ali.Boosh(a)sd.zain.com>; Badr Eldin Abdalla Mohamed Nour <Badr.Nour(a)sd.zain.com> Subject: Fwd: [tz] [IANA #985615] Sudan Time Zone change Dears, Please check the below feedback from IANA Thanks, Sent from Samsung Mobile -------- Original message -------- From: ahmed.atyya(a)ntc.gov.sd<mailto:ahmed.atyya@ntc.gov.sd> Date:11/01/2017 20:19 (GMT+03:00) To: Faisal El Muftah , Ahmed Ali Ahmed Ali , Regulatory , Hiba Abbas Yousif Eltigani , Mohamed Gaafar Ibrahim Bashir Corporate Services - MTN - Sudan , Nafisa Mahmoud Karamalla Corporate Services - MTN - Sudan , Mohammed Abdelraheem Abdelmagid Elkhalifa , Munir Taha Elkabashi Hassan Elfaki Cc: abdelhafiz , Afaf Nijomi , yahia , mohamed elhaj Subject: Fwd: [tz] [IANA #985615] Sudan Time Zone change Dears Please find below email from IANA for your kind revision to find the way out; we will also discuss the proposal of Sudan Embassy regards Ahmed Atyya ----- Forwarded Message ----- From: "Paul Eggert" <eggert(a)cs.ucla.edu<mailto:eggert@cs.ucla.edu>> To: "ahmed atyya" <ahmed.atyya(a)ntc.gov.sd<mailto:ahmed.atyya@ntc.gov.sd>> Cc: "yahia" <yahia(a)ntc.gov.sd<mailto:yahia@ntc.gov.sd>>, "Matt Johnson" <mj1856(a)hotmail.com<mailto:mj1856@hotmail.com>>, "Time Zone Mailing List" <tz(a)iana.org<mailto:tz@iana.org>>, "itisalat" <itisalat(a)ntc.gov.sd<mailto:itisalat@ntc.gov.sd>>, "abdin" <abdin(a)ntc.gov.sd<mailto:abdin@ntc.gov.sd>>, "nadir" <nadir(a)ntc.gov.sd<mailto:nadir@ntc.gov.sd>>, "abdelhafiz" <abdelhafiz(a)ntc.gov.sd<mailto:abdelhafiz@ntc.gov.sd>> Sent: Wednesday, November 1, 2017 7:57:00 PM Subject: Re: [tz] [IANA #985615] Sudan Time Zone change On 11/01/2017 01:35 AM, ahmed.atyya(a)ntc.gov.sd<mailto:ahmed.atyya@ntc.gov.sd> wrote: > With respect to the topic, please be updated that the change was > applied successfully, Apple handsets did the update automatically but Android handsets didn?t. In what sense didn't they change? My Android phone's time zone menu has entries for Cairo, Harare, and Nairobi, but not for Khartoum. If it is a matter of the user's time zone settings, users need to change from (say) Nairobi time to Cairo time. On the other hand, if it is a matter of the time zone supplied from the cellular service company, then this is something for your local cell company to address. > We kindly request to communicate with Google in order to update > Android OS with the changes for the handsets take the time automatically. As I understand it, Google engineers monitor this mailing list and so already know about the time zone change. There is a gap between the time that Google releases software updates, and the time that phones actually change. For example, even though I have a Google Nexus 6P phone and live in the United States, my phone is well behind Google's release schedule: it upgraded over-the-air to Android 8.0 Oreo only last night, even though Oreo was released on August 21 *. Other manufacturers' Android phones are even slower to update. This underscores the importance of governments announcing time zone changes well in advance: we currently recommend one years' advance notice. When other countries have run into similar problems, they've had some luck by contacting the U.S. State Department and asking for its help in adjusting the priorities of commercial providers. I suggest that you contact the U.S. Deputy Chief of Mission in Sudan and ask for his advice for how to proceed. See: https://sd.usembassy.gov/our-relationship/dcm/ https://sd.usembassy.gov/embassy/khartoum/offices-departments/public-affair… From what you tell me, though, the problem is likely to involve the protocols used by your local cellular service providers (that is, the problem may not be in Android at all), so they'll need to be in contact with their suppliers too. [cid:image001.png@01D353B6.A6960840] Ahmed Ahmedali Market Power & Competition Advance Specialist Zain SD Al Mogran, Zain Building Al Ghaba Street P.O Box: 13588 Khartoum Sudan Mobile : +249912398071 Email : Ahmed.Ahmedali(a)sd.zain.com<mailto:Ahmed.Ahmedali@sd.zain.com> Web : www.zain.com<http://www.zain.com> [cid:image005.jpg@01D353DD.1DA00320]<https://twitter.com/ZainSudan> [cid:image007.jpg@01D353DD.1DA00320] <https://facebook.com/ZainSudan/?fref=ts> [cid:image009.jpg@01D353DD.1DA00320] <https://plus.google.com/110542740934974723351> [cid:image011.jpg@01D353DD.1DA00320] <https://instagram.com/zainsudan/> [cid:image013.jpg@01D353DD.1DA00320] <https://linkedin.com/company/3224878?trk=tyah&trkInfo=clickedVertical%3Acom…> [cid:image023.png@01D353DD.1DA00320] <https://youtube.com/user/ZainSudanTV> [cid:image014.png@01D353B6.A6960840] [cid:image2acf2f.BMP@a4b5ec2d.4c95cc79] Mohammed Elsir Osman CT Infrastructure Operation Team Leader Zain SD Al Mogran, Zain Building Al Ghaba Street P.O Box: 13588 Khartoum Sudan Mobile : ++249912311500 Office : +24990001-3256 Email : Mohammed.ElsirOsman(a)sd.zain.com Web : www.zain.com [cid:image1d8d7d.PNG@e9fa88a4.43aeded8]<https://twitter.com/ZainSudan> [cid:imaged5af34.PNG@146f7ddf.4e95af19] <https://facebook.com/ZainSudan/?fref=ts> [cid:image95f784.PNG@eb17dd26.4eb485d3] <https://plus.google.com/110542740934974723351> [cid:imageb1c854.JPG@2f1af4fa.4680f52e] <https://instagram.com/zainsudan/> [cid:imagead7fe1.PNG@0e87976d.42b9ff22] <https://linkedin.com/company/3224878?trk=tyah&trkInfo=clickedVertical%3Acom…> [cid:image108d42.PNG@d8c0b630.439783e1] <https://youtube.com/user/ZainSudanTV> [cid:image400fba.PNG@9f5f39e1.45ab1906]

1 0

Ulaanbaatar Time Zone Correction
by Brian M. Vibert Nov. 2, 2017

Nov. 2, 2017

Hello, Looking into the asia file, I see a listing comment for # From Ganbold Tsagaankhuu (2017-02-09): # Mongolian Government meeting has concluded today to cancel daylight # saving time adoption in Mongolia. Source: http://zasag.mn/news/view/16192 Which is correct, however, it appears that the change has not been propagated to the Zone as seen here # Ulaanbaatar, a.k.a. Ulan Bataar, Ulan Bator, Urga Zone Asia/Ulaanbaatar 7:07:32 - LMT 1905 Aug 7:00 - +07 1978 8:00 Mongol +08/+09 It should just be 8:00 across the board at all times. -- *Brian M. Vibert | L3 Technical Support Engineer* *e: **bvibert(a)instructure.com <bvibert(a)instructure.com>* *c: 801.913.4236| **instructure.com* <http://www.instructure.com/> <https://www.instructure.com/>

2 1

[time zone problem about 2017c]
by Zhouyuxiang Nov. 2, 2017

Nov. 2, 2017

Dear all: Hello. I'm a user of time zone data in IANA. Lately I found a problem when I used it in Android O system. external\icu\tools\update-tzdata.py I used the tool in the below path to deal with the data tzcode2017c.tar.gz<https://www.iana.org/time-zones/repository/releases/tzcode2017c.tar.gz>. Then the error occurred. Finally I found the way to solve it. It seemed that africa file and backzone file have a duplicated data: # South Sudan Zone Africa/Juba 2:06:24 - LMT 1931 2:00 Sudan CA%sT 2000 Jan 15 12:00 3:00 - EAT I deleted one in backzone, then it worked. Now I'm wondering if this is mistake. And what are the influences?

2 1

Data loss on FTP Server
by Nathan Winters Nov. 1, 2017

Nov. 1, 2017

Hello, I've been using the FTP server to access Timezone Info for a while now and it seems the directory I was using (/tz/data) has lost all of its files. Additionally, I'm unable to view the data for the most recent release ( tzdb-2017c/ <ftp://ftp.iana.org/tz/tzdb-2017c/>). Has anything changed recently? Thanks, Nate

13 24

[PROPOSED] Guess that Tonga has canceled DST
by Paul Eggert Nov. 1, 2017

Nov. 1, 2017

(Thanks to David Wade.) * NEWS, australasia (Tonga): Guess DST has been canceled. --- NEWS | 6 ++++++ australasia | 14 ++++++++++++-- 2 files changed, 18 insertions(+), 2 deletions(-) diff --git a/NEWS b/NEWS index 4e98ef7..28b46b8 100644 --- a/NEWS +++ b/NEWS @@ -7,6 +7,7 @@ Unreleased, experimental changes Fiji ends DST 2018-01-14, not 2018-01-21. Namibia switches from +01/+02 to +02 on 2018-04-01. Sudan switches from +03 to +02 on 2017-11-01. + Tonga likely switches from +13/+14 to +13 on 2017-11-05. Turks & Caicos switches from -04 to -05/-04 on 2018-11-04. A new file tzdata.zi now holds a small text copy of all data. The zic input format has been regularized slightly. @@ -28,6 +29,11 @@ Unreleased, experimental changes Atyya and Yahia Abdalla.) South Sudan is not switching, so Africa/Juba is no longer a link to Africa/Khartoum. + Tonga has likely ended its experiment with DST, and will not + adjust its clocks on 2017-11-05. Although Tonga has not announced + whether it will continue to observe DST, the IATA is assuming that + it will not. (Thanks to David Wade.) + Turks & Caicos will switch from -04 all year to -05 with US DST on 2018-03-11 at 03:00. This affects UT offsets starting 2018-11-04 at 02:00. (Thanks to Steffen Thorsen.) diff --git a/australasia b/australasia index ae2cd72..5f7c86d 100644 --- a/australasia +++ b/australasia @@ -704,8 +704,8 @@ Rule Tonga 1999 only - Oct 7 2:00s 1:00 S Rule Tonga 2000 only - Mar 19 2:00s 0 - Rule Tonga 2000 2001 - Nov Sun>=1 2:00 1:00 S Rule Tonga 2001 2002 - Jan lastSun 2:00 0 - -Rule Tonga 2016 max - Nov Sun>=1 2:00 1:00 S -Rule Tonga 2017 max - Jan Sun>=15 3:00 0 - +Rule Tonga 2016 only - Nov Sun>=1 2:00 1:00 S +Rule Tonga 2017 only - Jan Sun>=15 3:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Pacific/Tongatapu 12:19:20 - LMT 1901 12:20 - +1220 1941 @@ -1626,6 +1626,7 @@ Zone Pacific/Wallis 12:15:20 - LMT 1901 # day in 2011. Assume also that the Samoas follow the US and New # Zealand's "ST"/"DT" style of daylight-saving abbreviations. + # Tonga # From Paul Eggert (1996-01-22): @@ -1720,6 +1721,15 @@ Zone Pacific/Wallis 12:15:20 - LMT 1901 # Assume Tonga will observe DST from the first Sunday in November at 02:00 # through the third Sunday in January at 03:00, like Fiji, for now. +# From David Wade (2017-10-18): +# In August government was disolved by the King. The current prime minister +# continued in office in care taker mode. It is easy to see that few +# decisions will be made until elections 16th November. +# +# From Paul Eggert (2017-10-18): +# For now, guess that DST is discontinued. That's what the IATA is guessing. + + # Wake # From Vernice Anderson, Personal Secretary to Philip Jessup, -- 2.13.6

4 3

The misaligned borders of South Australia
by Gilmore Davidson Nov. 1, 2017

Nov. 1, 2017

An interesting piece of trivia/history popped up in the news today. The borders of South Australia (and hence the boundaries of some Australian time zones) look like straight lines on most maps, but have some kinks in them. Most notably for this mailing list, part of the eastern border is misaligned due to an incorrect timekeeping reference from GMT. http://www.abc.net.au/news/2017-11-01/why-south-australias-borders-are-anyt… <http://www.abc.net.au/news/2017-11-01/why-south-australias-borders-are-anyt…> > It was meant to run along the 141st meridian line of longitude. > But longitude is measured with time references to Greenwich Mean Time — and watches were not that great in the 1800s. > The result was a 3.6-kilometre gap where the borders were meant to have met. > > "Fundamentally the difference came down to a discrepancy that the nation had at the time," Mr Burdett said. > "The longitude that had been determined for Fort Macquarie [Australia's reference point] was out by two minutes. > "Hence ours was out by two minutes and the discrepancy ended up in that border." Cheers, Gil

1 0

Turks & Caicos to resume DST; details unclear
by Paul Eggert Oct. 31, 2017

Oct. 31, 2017

According to an article published in the Bahamas website Magnetic Media, the cabinet of Turks & Caicos decided on Thursday to resume the practice of daylight saving time starting in 2018. The article does not give enough details to update the database (it confuses summer with winter time, among other things). My guess is that Turks & Caicos will revert to its pre-2015 practice of staying in sync with New York, which means that tzdb's predictions for its UTC offsets will become wrong in November 2018, and the abbreviations and tm_isdst flag will become wrong some time between March and November 2018 (although the article implies April, this could well be an error). When the cabinet and/or the Turks & Caicos Weekly News get around to publishing the details of the decision, we should be able to update tzdb to reflect this change with some accuracy. Gordon Z. PDM to reinstate Daylight Savings Time. Magnetic Media 2017-07-20. http://magneticmediatv.com/2017/07/pdm-to-reinstate-daylight-savings-time/ ("PDM" is the People's Democratic Movement.)

4 4

A bill to move Polish time (Europe/Warsaw) permanently to UTC+2
by Sergiusz Wolicki Oct. 29, 2017

Oct. 29, 2017

An internal committee of the Polish parlament (Sejm) has unanimously voted in favor of a bill to stop DST changes and to introduce permanent Central European Summer Time (GMT+2). The law would come in force in autumn 2018. The bill still needs to be voted by Sejm, then Senat (upper house), and then must be signed by the President, so it is far from being the actual law. The bill is not considered conflicting with EU regulations, which only require DST changes to be synchronized across EU but do not actually mandate the use of DST. Reference in Polish: http://wiadomosci.gazeta.pl/wiadomosci/7,114883,22499682,nie-bedziemy-przes… The website <http://sejm.gov.pl/Sejm8.nsf/PrzebiegProc.xsp?nr=1852> of the Sejm has not yet been updated with the result of the voting. Thanks, Sergiusz

7 7

Bug in Latest Release of TZ Database ie 2017c
by Sahil Sethi Oct. 28, 2017

Oct. 28, 2017

Hi Team As decided by Sudan Government to change time zone from GMT+3 to GMT+2, we were testing TZ update from 2017b --> 2017c and we encountered the following error : Linux TZ version : 2017b --> 2017c ... Failed | "backzone", line 149: duplicate zone name Africa/Juba (file "africa", line 1107) | "backzone", line 150: input line of unknown type | "backzone", line 151: input line of unknown type On little debugging we found that in former version there was a link between Africa/Khartoum & Africa/Juba zones in africa file and Africa/Juba zone entry existed in "backzone" file but in later version same zone entry of Africa/Juba exists in both files ie "africa" & "backzone", causing trouble. Looking forward for an acknowledgement. Regards Sahil Sethi Sr Software Engineer GlogbalLogic, India

2 1

2017c zdump outputs "No such file or directory"
by 大山俊成 Oct. 27, 2017

Oct. 27, 2017

Hi, Previously, I tryed 2017b like the following. make TOPDIR=$HOME/tzdir install $HOME/tzdir/etc/zdump -v America/Los_Angeles It works good . Now I tryed 2017c as the same way. make TOPDIR=$HOME/tzdir install $HOME/tzdir/etc/zdump -v America/Los_Angeles But , zdump outputs "America/Los_Angeles: No such file or Directory" Something wrong with me?

3 7

why do Africa/Juba and backzone/Africa/Juba differ?
by Michael Deckers Oct. 24, 2017

Oct. 24, 2017

Puzzles me in 2017c: Africa/Juba and backzone/Africa/Juba differ in their astronomical longitudes: in zone1970.tab: SS +0451+03137 Africa/Juba in zone.tab: SS +0451+03136 Africa/Juba and (correspondingly) in the local mean time used before the switch to zone time in 1931: in africa: Zone Africa/Juba 2:06:28 - LMT 1931 in backzone: Zone Africa/Juba 2:06:24 - LMT 1931 Why? And do we need the backzone entry at all? Michael Deckers. --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

2 1

Anyone else having snprintf issues with 2017c?
by Jon Skeet Oct. 24, 2017

Oct. 24, 2017

The tzvalidate <https://github.com/nodatime/tzvalidate> travis build is failing, with both clang and gcc, with this error: zdump.c:803:1: error: static declaration of ‘snprintf’ follows non-static declaration snprintf(char *s, size_t size, char const *format, ...) ^ make: *** [zdump.o] Error 1 It's building fine for me locally, so I'm not quite sure what's wrong. We're currently building on trusty - I may try another distro... The snprintf changes were introduced on June 13th <https://github.com/eggert/tz/commit/399180580f65bcad63cf996997068366cadaf53…>. It's been too long since I've done a lot of C to easily work out what's going on. I'll investigate further myself tomorrow, but I thought I'd just see if anyone else had seen this before then. Jon

7 9

installargs loses part of backward
by Zefram Oct. 23, 2017

Oct. 23, 2017

New in the 2017c release, there's a bug in how INSTALLARGS in the Makefile passes the BACKWARD variable down to an inferior make process. Because the definition of INSTALLARGS doesn't put quotes around the value part of BACKWARD, and because BACKWARD is actually (by default) a space-separated list of two files, the inferior make only gets the first file in its BACKWARD value, treating the second file as something to ensure is up to date (which of course it already is). So the inferior make omits one of the BACKWARD files (pacificnew) from whatever it does. The practical effect of this is that when building the binary zone files by, for example, "make posix_only", without having previously done "make tzdata.zi", the US/Pacific-New link is omitted. It's missing from the directory of binary outputs, and missing from the tzdata.zi file that is created as a side effect of building them (thus affecting anything that later tries to use tzdata.zi). That's the only zone name affected, because it's the only zone name defined in the lost source file. If "make tzdata.zi" is done first then that will create a correct tzdata.zi, and subsequent building of the binary zone files will then include the link. This was spotted by my automation, which sanity checks the directory of generated binary zone files against a list of zone names that it extracts from the source files. I think this a sensible check, and that it ought to pass. The fix is that the definition of INSTALLARGS should quote $(BACKWARD), the same way it quotes $(PACKRATDATA). Or perhaps it should not set BACKWARD at all, just like it doesn't set YDATA et al. (But perhaps it should *also* set YDATA et al.) -zefram

3 4

[tz-announce] 2017c release of tz code and data available
by Paul Eggert Oct. 23, 2017

Oct. 23, 2017

The 2017c release of the tz code and data is available. It reflects the following changes, which were either circulated on the tz mailing list or are relatively minor technical or administrative changes: Briefly: Northern Cyprus switches from +03 to +02/+03 on 2017-10-29. Fiji ends DST 2018-01-14, not 2018-01-21. Namibia switches from +01/+02 to +02 on 2018-04-01. Sudan switches from +03 to +02 on 2017-11-01. Tonga likely switches from +13/+14 to +13 on 2017-11-05. Turks & Caicos switches from -04 to -05/-04 on 2018-11-04. A new file tzdata.zi now holds a small text copy of all data. The zic input format has been regularized slightly. Changes to future time stamps Northern Cyprus has decided to resume EU rules starting 2017-10-29, thus reinstituting winter time. Fiji ends DST 2018-01-14 instead of the 2018-01-21 previously predicted. (Thanks to Dominic Fok.) Adjust future predictions accordingly. Namibia will switch from +01 with DST to +02 all year on 2017-09-03 at 02:00. This affects UT offsets starting 2018-04-01 at 02:00. (Thanks to Steffen Thorsen.) Sudan will switch from +03 to +02 on 2017-11-01. (Thanks to Ahmed Atyya and Yahia Abdalla.) South Sudan is not switching, so Africa/Juba is no longer a link to Africa/Khartoum. Tonga has likely ended its experiment with DST, and will not adjust its clocks on 2017-11-05. Although Tonga has not announced whether it will continue to observe DST, the IATA is assuming that it will not. (Thanks to David Wade.) Turks & Caicos will switch from -04 all year to -05 with US DST on 2018-03-11 at 03:00. This affects UT offsets starting 2018-11-04 at 02:00. (Thanks to Steffen Thorsen.) Changes to past time stamps Namibia switched from +02 to +01 on 1994-03-21, not 1994-04-03. (Thanks to Arthur David Olson.) Detroit did not observe DST in 1967. Use railway time for Asia/Kolkata before 1941, by switching to Madras local time (UT +052110) in 1870, then to IST (UT +0530) in 1906. Also, treat 1941-2's +0630 as DST, like 1942-5. Europe/Dublin's 1946 and 1947 fallback transitions occurred at 02:00 standard time, not 02:00 DST. (Thanks to Michael Deckers.) Pacific/Apia and Pacific/Pago_Pago switched from Antipodean to American time in 1892, not 1879. (Thanks to Michael Deckers.) Adjust the 1867 transition in Alaska to better reflect the historical record, by changing it to occur on 1867-10-18 at 15:30 Sitka time rather than at the start of 1867-10-17 local time. Although strictly speaking this is accurate only for Sitka, the rest of Alaska's blanks need to be filled in somehow. Fix off-by-one errors in UT offsets for Adak and Nome before 1867. (Thanks to Michael Deckers.) Add 7 s to the UT offset in Asia/Yangon before 1920. Changes to zone names Remove Canada/East-Saskatchewan from the 'backward' file, as it exceeded the 14-character limit and was an unused misnomer anyway. Changes to build procedure To support applications that prefer to read time zone data in text form, two zic input files tzdata.zi and leapseconds are now installed by default. The commands 'zic tzdata.zi' and 'zic -L leapseconds tzdata.zi' can reproduce the tzdata binary files without and with leap seconds, respectively. To prevent these two new files from being installed, use 'make TZDATA_TEXT=', and to suppress leap seconds from the tzdata text installation, use 'make TZDATA_TEXT=tzdata.zi'. 'make BACKWARD=' now suppresses backward-compatibility names like 'US/Pacific' that are defined in the 'backward' and 'pacificnew' files. 'make check' now works on systems that lack a UTF-8 locale, or that lack the nsgmls program. Set UTF8_LOCALE to configure the name of a UTF-8 locale, if you have one. Y2K runtime checks are no longer enabled by default. Add -DDEPRECATE_TWO_DIGIT_YEARS to CFLAGS to enable them, instead of adding -DNO_RUN_TIME_WARNINGS_ABOUT_YEAR_2000_PROBLEMS_THANK_YOU to disable them. (New name suggested by Brian Inglis.) The build procedure for zdump now works on AIX 7.1. (Problem reported by Kees Dekker.) Changes to code zic and the reference runtime now reject multiple leap seconds within 28 days of each other, or leap seconds before the Epoch. As a result, support for double leap seconds, which was obsolescent and undocumented, has been removed. Double leap seconds were an error in the C89 standard; they have never existed in civil timekeeping. (Thanks to Robert Elz and Bradley White for noticing glitches in the code that uncovered this problem.) zic now warns about use of the obsolescent and undocumented -y option, and about use of the obsolescent TYPE field of Rule lines. zic now allows unambiguous abbreviations like "Sa" and "Su" for weekdays; formerly it rejected them due to a bug. Conversely, zic no longer considers non-prefixes to be abbreviations; for example, it no longer accepts "lF" as an abbreviation for "lastFriday". Also, zic warns about the undocumented usage with a "last-" prefix, e.g., "last-Fri". Similarly, zic now accepts the unambiguous abbreviation "L" for "Link" in ordinary context and for "Leap" in leap-second context. Conversely, zic no longer accepts non-prefixes such as "La" as abbreviations for words like "Leap". zic no longer accepts leap second lines in ordinary input, or ordinary lines in leap second input. Formerly, zic sometimes warned about this undocumented usage and handled it incorrectly. The new macro HAVE_TZNAME governs whether the tzname external variable is exported, instead of USG_COMPAT. USG_COMPAT now governs only the external variables "timezone" and "daylight". This change is needed because the three variables are not in the same category: although POSIX requires tzname, it specifies the other two variables as optional. Also, USG_COMPAT is now 1 or 0: if not defined, the code attempts to guess it from other macros. localtime.c and difftime.c no longer require stdio.h, and .c files other than zic.c no longer require sys/wait.h. zdump.c no longer assumes snprintf. (Reported by Jonathan Leffler.) Calculation of time_t extrema works around a bug in GCC 4.8.4 (Reported by Stan Shebs and Joseph Myers.) zic.c no longer mistranslates formats of line numbers in non-English locales. (Problem reported by Benno Schulenberg.) Several minor changes have been made to the code to make it a bit easier to port to MS-Windows and Solaris. (Thanks to Kees Dekker for reporting the problems.) Changes to documentation and commentary The two new files 'theory.html' and 'calendars' contain the contents of the removed file 'Theory'. The goal is to document tzdb theory more accessibly. The zic man page now documents abbreviation rules. tz-link.htm now covers how to apply tzdata changes to clients. (Thanks to Jorge Fábregas for the AIX link.) It also mentions MySQL. The leap-seconds.list URL has been updated to something that is more reliable for tzdb. (Thanks to Tim Parenti and Brian Inglis.) Here are links to the release files: https://www.iana.org/time-zones/repository/releases/tzcode2017c.tar.gz https://www.iana.org/time-zones/repository/releases/tzdata2017c.tar.gz https://www.iana.org/time-zones/repository/releases/tzdb-2017c.tar.lz As usual, links to the latest release files are here: https://www.iana.org/time-zones/repository/tzcode-latest.tar.gz https://www.iana.org/time-zones/repository/tzdata-latest.tar.gz https://www.iana.org/time-zones/repository/tzdb-latest.tar.lz Links are also available via plain HTTP, and via FTP from ftp://ftp.iana.org/tz/releases with the same basenames as above. Each release file has a GPG signature, which can be retrieved by appending ".asc" to the above URLs. Copies of these signatures are appended to this message. This release corresponds to commit 812e509d5a30657f8e99ec51cedac7d4229ed784 dated 2017-10-20 14:49:34 -0700 and tagged '2017c' in the development GitHub repository at <https://github.com/eggert/tz>. Here are the SHA-512 checksums for the release files: 0d8c3e07b0de9015a137602450468ceb6358312a50eeda2a860882367107b8ba9ef275880b292570a671b9910afc54e6209e1e642387d246bc9c08c4ff660ffb tzcode2017c.tar.gz feb5c544e617b30c73a397e5a1c51f9847d0fddf1dfa0f9ace2e6f686786f09b666937b2048e07075c84593fc584bd5a25d639fce70eca9735267df28621ab4c tzdata2017c.tar.gz f877cd48bde0e342b9f71490befd7890682c87e9f542480b2e412b3ae08bd284516a3015588222c1fad8e3ec40a0428986404c3b660d7c88da92c1a2b6af10b4 tzdb-2017c.tar.lz Here are the GPG checksums for the release files: -----BEGIN PGP SIGNATURE----- iQIcBAABAgAGBQJZ6nFEAAoJEO2X6Q5iqn40JnoP/i8JCoxp5Vb+oxD2F8hz85+S ikzzi0+l5vMifyI9+/kxU/V+W1YvLC3zbUMLN6moE65WryjRnXCJXfTzNyFUON0H Dg7a1al0mNcq5D4YIvR6C/O5SJdRNW6VNW0A0owXV8ZafAzUbe5ICoUKQ69DC3ps jKXjO9qsyxne7rqjaqCyJAGVRHdx82p7XRvr5JCtU5vEGoclCDglWN4cUP09019q azA1eYfqkqS+uf3KzPVc8e/0slAdXOqOib7NNFY/Y90wFUlKuhgHdOXVy9bIvdeP PQmNlXNi1TC/gYNtqdxoeCsWSnOCMW9f/v9vBZTB8Oh8Ycm6U+YSAKZxlaVP5zUa VEnyMxDjKOD6YcqGHqx035TFxaAfaDDvDRACcA98SdTcBr7TgY4Ubxv0kCQ007Vr BYesKUcVpE8/wsh6dDHbaZzK01bJkJYGr44UZBwOwAbbkyCG+HDv3J6eg4UphQq0 HITxJLsaiJcJnR/l8YVSrzSHXIftwRIhGbab3BFuPAN7nDEZFrhUkZdMwac4B6E8 gsVxLYK3SJyFz9Jx7D4oDBN+Nxt+54O3/GXYVtAF0k2hiytd6UFaIr1WsmdSVLzA kmBQNiyqJ9jOPJ75B/r4x15JRZfNFDKJZ7AMqo6QthKZrurK93uuR20OKZmklnLr Vwcz+6pYTUf9bRrRfyXg =drdL -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- iQIcBAABAgAGBQJZ6nFvAAoJEO2X6Q5iqn40dFwP/31AK4shXM+vRKf28szHxBwk gTHTka+WMvQdhRtkgQvRXDQo1q9QiI/t4l3x0TpxkkuZATA6Yf1AhV7ugFFfl8Ia 0bc+8uXnv8XnpZ3Qbk57B6J6LEsaMOeaXv1vIZ6x8E/oaDECAV4o2+dpDl5kdNTr O6hcUZwY1Rd8CcJCvOPSFfRV1kNcPXCaKQPh0Z5uohqC7DLmxhtagsiMeUmzInV/ Q1bPOJXF4sD9X7A6hKqk4oyFQvJrYjv/JeM5eoreHIXdSLqvvwhhqCSMx6A76NDA 1/rKFZxqBLojlLmG07SXsCMC9OmD2m709sHKPx0foixhlmB9QJjDm62EjPPwfXd9 AH/3jxolQQq8DCC4XyqLblzPORfFNwZ4vWC3QpTNsQOdqBdkKpfNYXIZTxGL/8Ti 6GtCwmp2E5+gXoV1uTHY51nLNjuI47XdUReh+eBWAWh95gJiKspStHebWLFsbUhg /YM9K9efhu5UaA3BxJn3SpXR43zeNDSUOmyIB+kyRQZDXSK/K0ukwgZPMzq8QuR8 aFB7K0YztC8P6SXIGOgMsWuVp06Cx4QQAdnvy9pcx0iDUUNoh/n+isvwfBCvvUvq ETDnuGYxsUTjlDvORG1VHg14sr4AdyTl3PH12cOscVP4fq5JV91cE4FBHwjD3jSx Lp4Yb/wfGxGLgqPmpY/I =C3sx -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- iQIcBAABAgAGBQJZ6nF3AAoJEO2X6Q5iqn40NeQP/iuhDY14PgMC6Y4NjghAv/hZ lv3TV1E9t9bWc1S4whVQMqU8cXKMd0FddIYajylefPyEb/OwxB4R7/9IDlr1qlKG NkwOWsIrmqp60yFAdSGO2sfwkAcYZlLrujU/Bh0rFy2LFbMSFL4fTfB9WnCjWmqk pX5ioFn8L+uRrVCVQf3ruoFZcAF0D+wRSGLyAb3TAxR6dr2Bq8B0eOQsRtcfPwaL 4nBy/Fa85G3BVqSMtJhJXNIK1Vat4qd8wDU8Wr9cVjImefvVGypgCom1DlOTFD/r 5+kAIXr4RPn0t7af1ue8pNVIo6NuLfEfql59JzDREgYyl2HzwfS93+Ga+/YLR9Xz rSL7nOSDhjoo66SD0TAGNEXuRhfm3IJb81NIqIyP3IV0BpnoPyZSN5ZgNNPZwIqy tfXp/jEO1JoPBNuF+S3/RucABYKkEVLrZT5RdRrmHXxVbORop+2g3ZRKYtUeuT9P ablFWRihBao7+5Enj5hMxkfivzRUgF1+Speai6uDWFfuO/wteqntYvKVIawCWN53 +IqkpBVit0LdkA7YYgBJ4SW7wfOwRRidHANWrjEMzyajP1rfFuc3Kh0N1erIdpeV 74yYcEcHZK7dU2vki331d0xr08chB215Cz/Z1Zbm2IQxxz09g0jfYrkYijFfpxuf vyMRiNaT/Hp+EpEroVP0 =0r0r -----END PGP SIGNATURE----- _______________________________________________ tz-announce mailing list tz-announce(a)iana.org https://mm.icann.org/mailman/listinfo/tz-announce

1 0

Fiji DST Change
by Raymond Kumar Oct. 20, 2017

Oct. 20, 2017

Hi, Can you please advise by when new version of tzdata will be out. As there were some changes to Fiji DST. Thanks, Raymond Kumar Head of Billing & Products +679-7015315 ________________________________ Notice of Confidentiality: The information contained in this communication is intended solely for the use of the individual or entity to whom it is addressed and others authorized to receive it. It may contain confidential or legally privileged information. If you are not the intended recipient you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this information is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by responding to this email and then delete it from your system.

2 1

[PATCH] * tz-link.htm: Update for moved and expired URLs.
by Paul Eggert Oct. 20, 2017

Oct. 20, 2017

--- tz-link.htm | 29 +++++++++-------------------- 1 file changed, 9 insertions(+), 20 deletions(-) diff --git a/tz-link.htm b/tz-link.htm index 03259d2..e7a7c8f 100644 --- a/tz-link.htm +++ b/tz-link.htm @@ -267,9 +267,10 @@ href="https://tools.ietf.org/html/rfc7808">TZDIST</a> (Internet <abbr>RFC</abbr> 7808), a time zone data distribution service, along with <a href="https://tools.ietf.org/html/rfc7809">CalDAV</a> (Internet <abbr>RFC</abbr> 7809), a calendar access protocol for -transferring time zone data by reference. The draft <a id="TZDIST-Geolocate" +transferring time zone data by reference. The (expired) draft <a +id="TZDIST-Geolocate" href="https://tools.ietf.org/html/draft-murchison-tzdist-geolocate-00">TZDIST -Geolocate Extension</a> lets a client determine its time zone region +Geolocate Extension</a> would have let a client determine its time zone region from its geographic location using a <a href="https://tools.ietf.org/html/rfc5870">'geo' URI</a>.</li> <li>The <a href="https://tools.ietf.org/html/rfc5545"> @@ -504,9 +505,6 @@ href="https://www.oracle.com/java/index.html">Oracle Java</a> contains a copy of a subset of a recent <code><abbr>tz</abbr></code> database in a Java-specific format.</li> -<li><a href="https://kimmo.suominen.com/sw/timezone/">Time Zone</a> is -a <a href="https://wordpress.org">WordPress</a> plugin. It is freely -available under a <abbr>BSD</abbr>-style license.</li> <li><a href="http://www.relativedata.com/time-zone-master">Time Zone Master</a> is a Microsoft Windows clock program that can automatically download, compile and use <code>tz</code> releases. The Basic version @@ -589,7 +587,8 @@ maps</a> contains <a href="https://en.wikipedia.org/wiki/Shapefile">shapefiles</a> of sets of <code><abbr>tz</abbr></code> regions. This includes <a href="http://efele.net/maps/tz/world/">tz_world</a>, a shapefile -for all the world's regions</li> +for all the world's regions. These maps are no longer maintained and +are superseded by the Timezone Boundary Builder.</li> <li><a href="https://github.com/straup/whereonearth-timezone">Whereonearth-timezone</a> is in <a href="https://tools.ietf.org/html/rfc7946">GeoJSON</a> format @@ -633,10 +632,7 @@ the <a href="https://timezonedb.com">Time Zone Database & API</a>. Commercial network API access is provided by <a href="https://askgeo.com">AskGeo</a> and <a href="https://www.geogarage.com/blog/news-1/post/geogarage-time-zone-api-31">GeoGarage</a>. -Also, an <a -href="https://mm.icann.org/pipermail/tz/2016-October/024309.html">experimental -server</a> is available for the TZDIST Geolocate Extension mentioned -<a href="#TZDIST-Geolocate">above</a>.</li> +</li> <li>"<a href="https://stackoverflow.com/questions/16086962/how-to-get-a-time-zone-from-a-…">How to get a time zone from a location using latitude and longitude @@ -648,13 +644,10 @@ political subdivision data related to time zones.</li> zone boundaries for multizone countries</a> summarizes legal boundaries between time zones within countries.</li> <li>Manifold.net's <a -href="http://manifold.net/info/freestuff.shtml">Free Stuff for +href="http://manifold.net/info/freestuff.shtml">Free Downloads for Manifold System Users</a> includes a Manifold-format map of world time zone boundaries distributed under the <abbr>GPL</abbr>.</li> -<li>The GeoCommunity lists several commercial sources for <a -href="http://spatialnews.geocomm.com/features/timezones/">International -Time Zones and Time Zone Data</a>.</li> <li>A ship within the <a href="https://en.wikipedia.org/wiki/Territorial_waters">territorial waters</a> of any nation uses that nation's time. In international @@ -723,7 +716,7 @@ href="ftp://ftp.cs.huji.ac.il/pub/tz/announcements" hreflang="he">announcements (in Hebrew)</a>.</dd> <dt>Italy</dt> <dd>The National Institute of Metrological Research maintains a -<a href="http://www.inrim.it/res/tf/ora_legale_i.shtml">table of civil time +<a href="http://www.nanospin.eu/res/tf/ora_legale_i.shtml">table of civil time (in Italian)</a>.</dd> <dt>Mexico</dt> <dd>The Investigation and Analysis Service of the Mexican Library of @@ -763,7 +756,7 @@ Time Zone Proceedings</a> lists changes to time zone boundaries.</dd> <h2 id="precision">Precision timekeeping</h2> <ul> <li><a -href="http://literature.agilent.com/litweb/pdf/5965-7984E.pdf">The +href="http://leapsecond.com/hpan/an1289.pdf">The Science of Timekeeping</a> is a thorough introduction to the theory and practice of precision timekeeping.</li> <li><a href="http://www.ntp.org"><abbr @@ -882,10 +875,6 @@ protocols.</li> <a href="https://www.hackcraft.net/web/datetime/">Date & Time Formats on the Web</a> surveys web- and Internet-oriented date and time formats.</li> -<li> -<a href="http://exit109.com/~ghealton/y2k/yrexamples.html">The -Best of Dates, the Worst of Dates</a> covers many problems encountered -by software developers when handling dates and time stamps.</li> <li>Alphabetic time zone abbreviations should not be used as unique identifiers for <abbr>UTC</abbr> offsets as they are ambiguous in practice. For example, in English-speaking North America -- 2.7.4

1 0