November 2015 - tz - lists.iana.org

proposed time zone package changes (Samoa, Factory, et al.)
by Arthur David Olson Aug. 28, 2019

Aug. 28, 2019

Below find proposed time zone package changes; the executive summary: * Makefile Change LOCALTIME default from "Factory" to "GMT"; do not compile "factory" file (but keep it in the distribution). * Theory Remove reference to "Factory" zone. * australasia Change end of DST in Samoa in 2011 from 2011-04-03 0:00 to 2011-04-03 1:00 (thanks to Raymond Hughes for a reference). * localtime.c Initialize ttinfo structures filled by tzparse (thanks to Ravindra for reporting a valgrind warning). * zic.c Fix generation of POSIX strings for zones with rules using "weekday<=n" forms of dates (thanks to Lei Liu for finding the problem). Also, limit output for non-POSIX-specificable zones defined to follow the same rules every year. (Note that no zones of either of the above types appear in the distribution; these changes cater to add-on zones). If no problems are found, 2010n will appear on 2010-10-25. --ado diff -r -c old/Makefile new/Makefile *** old/Makefile Mon Sep 27 09:24:25 2010 --- new/Makefile Tue Oct 12 12:36:50 2010 *************** *** 1,5 **** # <pre> ! # @(#)Makefile 8.8 # This file is in the public domain, so clarified as of # 2009-05-17 by Arthur David Olson. --- 1,5 ---- # <pre> ! # @(#)Makefile 8.9 # This file is in the public domain, so clarified as of # 2009-05-17 by Arthur David Olson. *************** *** 12,18 **** # make zonenames # to get a list of the values you can use for LOCALTIME. ! LOCALTIME= Factory # If you want something other than Eastern United States time as a template # for handling POSIX-style time zone environment variables, --- 12,18 ---- # make zonenames # to get a list of the values you can use for LOCALTIME. ! LOCALTIME= GMT # If you want something other than Eastern United States time as a template # for handling POSIX-style time zone environment variables, *************** *** 262,269 **** DOCS= README Theory $(MANS) date.1 Makefile PRIMARY_YDATA= africa antarctica asia australasia \ europe northamerica southamerica ! YDATA= $(PRIMARY_YDATA) pacificnew etcetera factory backward ! NDATA= systemv SDATA= solar87 solar88 solar89 TDATA= $(YDATA) $(NDATA) $(SDATA) TABDATA= iso3166.tab zone.tab --- 262,269 ---- DOCS= README Theory $(MANS) date.1 Makefile PRIMARY_YDATA= africa antarctica asia australasia \ europe northamerica southamerica ! YDATA= $(PRIMARY_YDATA) pacificnew etcetera backward ! NDATA= systemv factory SDATA= solar87 solar88 solar89 TDATA= $(YDATA) $(NDATA) $(SDATA) TABDATA= iso3166.tab zone.tab diff -r -c old/Theory new/Theory *** old/Theory Mon Sep 27 09:24:25 2010 --- new/Theory Tue Oct 12 12:36:50 2010 *************** *** 1,4 **** ! @(#)Theory 8.4 This file is in the public domain, so clarified as of 2009-05-17 by Arthur David Olson. --- 1,4 ---- ! @(#)Theory 8.5 This file is in the public domain, so clarified as of 2009-05-17 by Arthur David Olson. *************** *** 287,294 **** See the file `backward' for most of these older names (e.g. `US/Eastern' instead of `America/New_York'). The other old-fashioned names still supported are ! `WET', `CET', `MET', `EET' (see the file `europe'), ! and `Factory' (see the file `factory'). ----- Time zone abbreviations ----- --- 287,293 ---- See the file `backward' for most of these older names (e.g. `US/Eastern' instead of `America/New_York'). The other old-fashioned names still supported are ! `WET', `CET', `MET', and `EET' (see the file `europe'). ----- Time zone abbreviations ----- diff -r -c old/australasia new/australasia *** old/australasia Mon Sep 27 09:24:27 2010 --- new/australasia Tue Oct 12 13:14:56 2010 *************** *** 1,5 **** # <pre> ! # @(#)australasia 8.18 # This file is in the public domain, so clarified as of # 2009-05-17 by Arthur David Olson. --- 1,5 ---- # <pre> ! # @(#)australasia 8.19 # This file is in the public domain, so clarified as of # 2009-05-17 by Arthur David Olson. *************** *** 487,497 **** # http://www.parliament.gov.ws/documents/acts/Daylight%20Saving%20Act%20%2020… # </a> Zone Pacific/Apia 12:33:04 - LMT 1879 Jul 5 -11:26:56 - LMT 1911 -11:30 - SAMT 1950 # Samoa Time -11:00 - WST 2010 Sep 26 ! -11:00 1:00 WSDT 2011 Apr 3 -11:00 - WST # Solomon Is --- 487,507 ---- # http://www.parliament.gov.ws/documents/acts/Daylight%20Saving%20Act%20%2020… # </a> + # From Raymond Hughes (2010-10-07): + # Please see + # <a href="http://www.mcil.gov.ws"> + # http://www.mcil.gov.ws + # </a>, + # the Ministry of Commerce, Industry and Labour (sideframe) "Last Sunday + # September 2010 (26/09/10) - adjust clocks forward from 12:00 midnight + # to 01:00am and First Sunday April 2011 (03/04/11) - adjust clocks + # backwards from 1:00am to 12:00am" + Zone Pacific/Apia 12:33:04 - LMT 1879 Jul 5 -11:26:56 - LMT 1911 -11:30 - SAMT 1950 # Samoa Time -11:00 - WST 2010 Sep 26 ! -11:00 1:00 WSDT 2011 Apr 3 1:00 -11:00 - WST # Solomon Is diff -r -c old/localtime.c new/localtime.c *** old/localtime.c Mon Sep 27 09:24:26 2010 --- new/localtime.c Tue Oct 12 12:36:51 2010 *************** *** 5,11 **** #ifndef lint #ifndef NOID ! static char elsieid[] = "@(#)localtime.c 8.14"; #endif /* !defined NOID */ #endif /* !defined lint */ --- 5,11 ---- #ifndef lint #ifndef NOID ! static char elsieid[] = "@(#)localtime.c 8.15"; #endif /* !defined NOID */ #endif /* !defined lint */ *************** *** 914,919 **** --- 914,920 ---- register unsigned char * typep; register char * cp; register int load_result; + static struct ttinfo zttinfo; INITIALIZE(dstname); stdname = name; *************** *** 986,991 **** --- 987,993 ---- /* ** Two transitions per year, from EPOCH_YEAR forward. */ + sp->ttis[0] = sp->ttis[1] = zttinfo; sp->ttis[0].tt_gmtoff = -dstoffset; sp->ttis[0].tt_isdst = 1; sp->ttis[0].tt_abbrind = stdlen + 1; *************** *** 1099,1106 **** } /* ** Finally, fill in ttis. - ** ttisstd and ttisgmt need not be handled. */ sp->ttis[0].tt_gmtoff = -stdoffset; sp->ttis[0].tt_isdst = FALSE; sp->ttis[0].tt_abbrind = 0; --- 1101,1108 ---- } /* ** Finally, fill in ttis. */ + sp->ttis[0] = sp->ttis[1] = zttinfo; sp->ttis[0].tt_gmtoff = -stdoffset; sp->ttis[0].tt_isdst = FALSE; sp->ttis[0].tt_abbrind = 0; *************** *** 1113,1118 **** --- 1115,1121 ---- dstlen = 0; sp->typecnt = 1; /* only standard time */ sp->timecnt = 0; + sp->ttis[0] = zttinfo; sp->ttis[0].tt_gmtoff = -stdoffset; sp->ttis[0].tt_isdst = 0; sp->ttis[0].tt_abbrind = 0; diff -r -c old/zic.c new/zic.c *** old/zic.c Mon Sep 27 09:24:26 2010 --- new/zic.c Tue Oct 12 13:37:29 2010 *************** *** 3,9 **** ** 2006-07-17 by Arthur David Olson. */ ! static char elsieid[] = "@(#)zic.c 8.22"; #include "private.h" #include "locale.h" --- 3,9 ---- ** 2006-07-17 by Arthur David Olson. */ ! static char elsieid[] = "@(#)zic.c 8.24"; #include "private.h" #include "locale.h" *************** *** 1881,1896 **** register int week; if (rp->r_dycode == DC_DOWGEQ) { ! week = 1 + rp->r_dayofmonth / DAYSPERWEEK; ! if ((week - 1) * DAYSPERWEEK + 1 != rp->r_dayofmonth) return -1; } else if (rp->r_dycode == DC_DOWLEQ) { if (rp->r_dayofmonth == len_months[1][rp->r_month]) week = 5; else { ! week = 1 + rp->r_dayofmonth / DAYSPERWEEK; ! if (week * DAYSPERWEEK - 1 != rp->r_dayofmonth) return -1; } } else return -1; /* "cannot happen" */ (void) sprintf(result, "M%d.%d.%d", --- 1881,1896 ---- register int week; if (rp->r_dycode == DC_DOWGEQ) { ! if ((rp->r_dayofmonth % DAYSPERWEEK) != 1) return -1; + week = 1 + rp->r_dayofmonth / DAYSPERWEEK; } else if (rp->r_dycode == DC_DOWLEQ) { if (rp->r_dayofmonth == len_months[1][rp->r_month]) week = 5; else { ! if ((rp->r_dayofmonth % DAYSPERWEEK) != 0) return -1; + week = rp->r_dayofmonth / DAYSPERWEEK; } } else return -1; /* "cannot happen" */ (void) sprintf(result, "M%d.%d.%d", *************** *** 2018,2023 **** --- 2018,2024 ---- register char * envvar; register int max_abbr_len; register int max_envvar_len; + register int prodstic; /* all rules are min to max */ max_abbr_len = 2 + max_format_len + max_abbrvar_len; max_envvar_len = 2 * max_abbr_len + 5 * 9; *************** *** 2032,2037 **** --- 2033,2039 ---- timecnt = 0; typecnt = 0; charcnt = 0; + prodstic = zonecount == 1; /* ** Thanks to Earl Chew ** for noting the need to unconditionally initialize startttisstd. *************** *** 2053,2058 **** --- 2055,2062 ---- updateminmax(rp->r_loyear); if (rp->r_hiwasnum) updateminmax(rp->r_hiyear); + if (rp->r_lowasnum || rp->r_hiwasnum) + prodstic = FALSE; } } /* *************** *** 2075,2080 **** --- 2079,2094 ---- if (max_year <= INT_MAX - YEARSPERREPEAT) max_year += YEARSPERREPEAT; else max_year = INT_MAX; + /* + ** Regardless of any of the above, + ** for a "proDSTic" zone which specifies that its rules + ** always have and always will be in effect, + ** we only need one cycle to define the zone. + */ + if (prodstic) { + min_year = 1900; + max_year = min_year + YEARSPERREPEAT; + } } /* ** For the benefit of older systems,

5 6

Syntax highlighting for Sublime Text
by Gilmore Davidson Aug. 16, 2017

Aug. 16, 2017

Hi, I’ve created some tzdata syntax highlighting rules for the Sublime Text editor: https://packagecontrol.io/packages/zoneinfo <https://packagecontrol.io/packages/zoneinfo> I have no idea if anyone other than me uses that particular text editor for looking at tzdata files. But I thought I’d mention it just in case it’s useful to someone. Cheers, Gil

3 3

Re: [tz] Version in zoneinfo files?
by Guy Harris Feb. 10, 2017

Feb. 10, 2017

On Oct 25, 2015, at 10:55 AM, Paul G <paul(a)ganssle.io> wrote: > I'm not suggesting that it be impossible to create a weird result when asking for the version, just that there's a standard place for the version to go, and preferably the standard default gives you something that you expected. I.e., something that works most of the time is sufficient? So what exactly is the intended use of this version field? > As it is now, you're virtually guaranteed to have a lot of incompatibility because there's nothing you can point to that says, "This is the canonical way to store version information about zoneinfo files", and no standard has emerged on how to do this as is. > > On 10/25/2015 01:51 PM, Guy Harris wrote: >> >> On Oct 25, 2015, at 10:37 AM, Paul G <paul(a)ganssle.io> wrote: >> >>> On 10/25/2015 01:35 PM, Guy Harris wrote: >>> >>>> So where would zic get the version information to put into the binary files? >>> >>> My understanding is that it's the VERSION= line of the Makefile in the tzdata tarballs. >> >> I.e., you're proposing that the value of the VERSION value in the Makefile be passed as an argument to zic, and zic would put the value of that argument into a field in the files? >> >> So, if the goal is to provide a "reliable way to get the version information in a cross-platform way", what would ensure that this field be set properly, for some value of "properly", everywhere that binary tzdata files are generated? >> >> I.e., what is to guarantee that >> >> 1) nobody downstream change VERSION if they aren't changing the zic files from what's distributed >> >> and >> >> 2) people change it "properly" if the files don't correspond to a particular version of files that were distributed (e.g., if some downstream supplier takes 2015q and adds some changes mentioned on the list to it before 2015r comes out with those changes plus other changes, they should call the resulting files something other than "2015q" or "2015r")? >> >

20 55

Proposal: validation text file with releases
by Jon Skeet Dec. 19, 2016

Dec. 19, 2016

Background: I'm the primary developer for Noda Time <http://nodatime.org> which consumes the tz data. I'm currently refactoring the code to do this... and I've come across some code (originally ported from Joda Time) which I now understand in terms of what it's doing, but not exactly why. For a little while now, the Noda Time source repo has included a text dump file <https://github.com/nodatime/nodatime/blob/master/src/NodaTime.Test/TestData…>, containing a text dump of every transition (up to 2100, at the moment) for every time zone. It looks like this, picking just one example: Zone: Africa/Maseru LMT: [StartOfTime, 1892-02-07T22:08:00Z) +01:52 (+00) SAST: [1892-02-07T22:08:00Z, 1903-02-28T22:30:00Z) +01:30 (+00) SAST: [1903-02-28T22:30:00Z, 1942-09-20T00:00:00Z) +02 (+00) SAST: [1942-09-20T00:00:00Z, 1943-03-20T23:00:00Z) +03 (+01) SAST: [1943-03-20T23:00:00Z, 1943-09-19T00:00:00Z) +02 (+00) SAST: [1943-09-19T00:00:00Z, 1944-03-18T23:00:00Z) +03 (+01) SAST: [1944-03-18T23:00:00Z, EndOfTime) +02 (+00) I use this file for confidence when refactoring my time zone handling code - if the new code comes up with the same set of transitions as the old code, it's probably okay. (This is just one line of defence, of course - there are unit tests, though not as many as I'd like.) It strikes me that having a similar file (I'm not wedded to the format, but it should have all the same information, one way or another) released alongside the main data files would be really handy for *all* implementors - it would be a good way of validating consistency across multiple platforms, with the release data being canonical. For any platforms which didn't want to actually consume the rules as rules, but just wanted a list of transitions, it could even effectively replace their use of the data. One other benefit: diffing the dump between two releases would make it clear what had changed in *effect*, rather than just in terms of rules. One sticking point is size. The current file for Noda Time is about 4MB, although it zips down to about 300K. Some thoughts around this: - We wouldn't need to distribute it in the same file as the data - just as we have data and code file, there could be a "textdump" file or whatever we'd want to call it. These could be retroactively generated for previous releases, too. - As you can see, there's redundancy in the format above, in that it's a list of "zone intervals" (as I call them in Noda Time) rather than a list of transitions - the end of each interval is always the start of the next interval. - For zones which settle into an infinite daylight saving pattern, I currently generate from the start of time to 2100 (and then a single zone interval for the end of time as Noda Time understands it; we'd need to work out what form that would take, if any). If we decided that "year of release + 30 years" was enough, that would cut down the size considerably. Any thoughts? If the feeling is broadly positive, the next step would be to nail down the text format, then find a willing victim/volunteer to write the C code. (You really don't want me writing C...) Jon

18 92

zic changes (2/2)
by Arthur David Olson March 9, 2016

March 9, 2016

And now, the update. These changes arrange things so that binary files include "transition" entries for minimum time values; these entries eliminate localtime guesswork in handling low-valued time stamps. The bad news: binary files grow slightly as a result of these changes. The good news: there are no changes in the output of "zdump -v" applied to before-and-after versions of all the binary files generated by a "make install." Changes are attached and appear in mangled form below; these are relative to the github version of zic.c after the rollback in the earlier message today. @dashdashado 1.2 2805 lines 1.4 2813 lines *** /tmp/,azic.c 2014-05-01 01:51:36.998933800 -0400 --- /tmp/,bzic.c 2014-05-01 01:51:37.092534000 -0400 *************** *** 1480,1493 **** fromi = 0; while (fromi < timecnt && attypes[fromi].at < min_time) ++fromi; - if (isdsts[0] == 0) - while (fromi < timecnt && attypes[fromi].type == 0) - ++fromi; /* handled by default rule */ for ( ; fromi < timecnt; ++fromi) { ! if (toi != 0 && ((attypes[fromi].at + gmtoffs[attypes[toi - 1].type]) <= ! (attypes[toi - 1].at + gmtoffs[toi == 1 ? 0 ! : attypes[toi - 2].type]))) { attypes[toi - 1].type = attypes[fromi].type; continue; --- 1480,1490 ---- fromi = 0; while (fromi < timecnt && attypes[fromi].at < min_time) ++fromi; for ( ; fromi < timecnt; ++fromi) { ! if (toi > 1 && ((attypes[fromi].at + gmtoffs[attypes[toi - 1].type]) <= ! (attypes[toi - 1].at + ! gmtoffs[attypes[toi - 2].type]))) { attypes[toi - 1].type = attypes[fromi].type; continue; *************** *** 1532,1537 **** --- 1529,1541 ---- --timecnt32; ++timei32; } + /* + ** Output an INT32_MIN "transition" if appropriate--see below. + */ + if (timei32 > 0 && ats[timei32] > INT32_MIN) { + --timei32; + ++timecnt32; + } while (leapcnt32 > 0 && !is32(trans[leapcnt32 - 1])) --leapcnt32; while (leapcnt32 > 0 && !is32(trans[leapi32])) { *************** *** 1698,1704 **** #undef DO for (i = thistimei; i < thistimelim; ++i) if (pass == 1) ! puttzcode(ats[i], fp); else puttzcode64(ats[i], fp); for (i = thistimei; i < thistimelim; ++i) { unsigned char uc; --- 1702,1713 ---- #undef DO for (i = thistimei; i < thistimelim; ++i) if (pass == 1) ! /* ! ** Output an INT32_MIN "transition" ! ** if appropriate--see above. ! */ ! puttzcode(((ats[i] < INT32_MIN) ? ! INT32_MIN : ats[i]), fp); else puttzcode64(ats[i], fp); for (i = thistimei; i < thistimelim; ++i) { unsigned char uc; *************** *** 2176,2183 **** if (usestart) { addtt(starttime, type); usestart = FALSE; ! } else if (stdoff != 0) ! addtt(min_time, type); } else for (year = min_year; year <= max_year; ++year) { if (useuntil && year > zp->z_untilrule.r_hiyear) break; --- 2185,2191 ---- if (usestart) { addtt(starttime, type); usestart = FALSE; ! } else addtt(min_time, type); } else for (year = min_year; year <= max_year; ++year) { if (useuntil && year > zp->z_untilrule.r_hiyear) break;

7 22

2015g: Is the 1:00 under Pacific/Norfolk "Rules" a typo?
by Marvel, Jim (CPCOE) March 1, 2016

March 1, 2016

Hello, Is the 1:00 under Pacific/Norfolk "Rules" a typo? # Norfolk # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Pacific/Norfolk 11:11:52 - LMT 1901 # Kingston 11:12 - NMT 1951 # Norfolk Mean Time 11:30 - NFT 1974 Oct 27 02:00 # Norfolk T. 11:30 1:00 NFST 1975 Mar 2 02:00 11:30 - NFT 2015 Oct 4 02:00 11:00 - NFT thanks Jim Marvel

5 5

[PATCH 0/1] Allow 'backzone' to be incorporated in 'right' data
by Ian Abbott Dec. 10, 2015

Dec. 10, 2015

The REDO macro in the Makefile currently allows you to build POSIX data, 'right' data, or both sets with either the default. It also allows information from the 'backzone' file to be incorporated into the POSIX data set but not if the 'right' data is being built to. There may be some unlucky bar steward out there who needs to incorporate the 'backzone' file data into the 'right' data set, or into both the POSIX and 'right' data sets, so I added a few extra targets to the Makefile for your consideration. See patch in following email.

2 11

Request to include www.timejones.com - tz database version 2014.8
by Web Master Dec. 9, 2015

Dec. 9, 2015

Hi, Greetings! First of all immense thanks for the introduction of tz database to the world. We are writing from www.timejones.com, an ultra simple time and weather services portal that helps people with time and weather information for 150000 places on Earth. We have developed this web site using tz database version 2014.8/ PHP 5.4.39 and hosted on a Apache/2.2.29. Could you please kindly include www.timejones.com under the section "Web sites using recent versions of the tz database" in http://cs.ucla.edu/~eggert/tz/tz-link.htm ? Thanks in advance! Best Regards, Webmaster(a)timejones.com

3 2

[PATCH 1/1] * LICENSE: New file.
by James Knight Dec. 8, 2015

Dec. 8, 2015

Adding a license-specific file to aid in package management and other possible use cases. Signed-off-by: James Knight <james.knight(a)rockwellcollins.com> diff -Naur tz_a/LICENSE tz_b/LICENSE --- tz_a/LICENSE 1969-12-31 19:00:00.000000000 -0500 +++ tz_b/LICENSE 2015-10-23 17:59:01.702710278 -0400 @@ -0,0 +1,21 @@ +Unless otherwise specified, all files in the tz code and data are in +the public domain, so clarified as of 2009-05-17 by Arthur David Olson. +The few exceptions are code derived from BSD, which uses the BSD license. + +date.c and strftime.c: +---------------------- +Copyright (c) 1985, 1987, 1988 The Regents of the University of California. +All rights reserved. + +Redistribution and use in source and binary forms are permitted +provided that the above copyright notice and this paragraph are +duplicated in all such forms and that any documentation, +advertising materials, and other materials related to such +distribution and use acknowledge that the software was developed +by the University of California, Berkeley. The name of the +University may not be used to endorse or promote products derived +from this software without specific prior written permission. +THIS SOFTWARE IS PROVIDED "AS IS" AND WITHOUT ANY EXPRESS OR +IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED +WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. +

2 1

CCTZ time zone library for C++ from Google
by Tim Parenti Dec. 8, 2015

Dec. 8, 2015

FYI, last month, Google released and open-sourced cctz <https://github.com/google/cctz>, a new time zone library for C++. My favorite quote from the announcement <http://google-opensource.blogspot.com/2015/09/introducing-cctz-simple-time-…> on their Open Source Blog: > *"Time zones are logical and easy to use." —no one ever* -- Tim Parenti

6 9

efele.net/tz maps updated
by Eric Muller Nov. 29, 2015

Nov. 29, 2015

I have updated the efele.net/tz maps (http://efele.net/maps/tz/) to be in sync with TZ 2015g. The new zones: Pacific/Bougainville Asia/Chita Asia/Srednekolymsk America/Fort_Nelson Antarctica/Troll Eric.

7 8

Machine-readable time zones diff/changelog?
by Максим Кочкин Nov. 27, 2015

Nov. 27, 2015

Hi. Recently I've run into an issue with time zones splitting, it's described in this my SO question — http://stackoverflow.com/questions/33943855/how-to-handle-new-time-zone/339… — and covered by a brilliant answer by Matt Johnson ( http://stackoverflow.com/a/33946308/487923) Matt also mentioned that there was a discussion about some machine-readable tz diff that can help developers to handle that changes like split automatically. Did you try to create a standardized diff/changelog? If not — why not? Or is it only me who needs it, and it can be handled in some other easier way?

2 1

TZ Updater
by Victor Uribe Nov. 26, 2015

Nov. 26, 2015

To whom it may concern, I am in need of acquiring the tz updater version JDK-8054458 found at http://bugs.java.com/view_bug.do?bug_id=8054458 since the Java time is no longer synchronized correctly. Where can I find this file to use on an XP machine running Java 6 update 30. Thank you. Regards, Victor Uribe Application Engineer Modular Mining Systems, Inc. 3289 E. Hemisphere Loop Tucson, Arizona 85706- 5028 USA +1 (520) 344-6376 (work) +1 (602) 762-0213 (cell) vuribe(a)mmsi.com<mailto:vuribe@mmsi.com> www.mmsi.com<http://www.mmsi.com> MODULAR - Mine Smarter™ _________________________________ The information contained in this email, including all attachments, is intended solely for the use of the individual or entity to whom it is addressed and may contain information that is privileged, proprietary and/or confidential. If the reader of this message is not the intended recipient or agent responsible for delivering the message to the intended recipient, you are hereby notified that any perusal, use, dissemination, or disclosure is strictly prohibited. Confidentiality, privilege, or copyright is not waived or lost because you have received this message in error. If you have received this message in error, please notify us immediately by reply email or email postmaster(a)mmsi.com and destroy the original message and any copies. Modular®, IntelliMine®, DISPATCH®, ProVision®, MineCare®, MasterLink®, PowerView ™, and ModularReady® are trademarks and/or registered trademarks and the sole and exclusive property of Modular Mining Systems, Inc.

2 1

More Russian Changes
by Matt Johnson Nov. 25, 2015

Nov. 25, 2015

FYI - Two draft bills are posted on the Russian government's web site: http://government.ru/activities/20702/ http://government.ru/activities/20703/ If approved, the effect would be to move the Astrakhan region from UTC+3 to UTC+4, and to move the Trans-Baikal region from UTC+8 to UTC+9. Neither bill mentions an effective date. It's not clear whether the Trans-Baikal region refers to the entire area of Zabaykalsky Krai or some subset. Zabaykalsk Krai is currently managed by the Asia/Chita time zone, which I assume would remain intact and just get a new row in its zone entry. Also, assuming by Astrakhan region they mean the Astrakhan Oblast, then I think this change would require a new time zone. I suggest Europe/Astrakan for the city of the same name in this region. This is split from the Europe/Volograd time zone. -Matt

1 2

Coordinated Universal Time (UTC) to retain “leap second”
by Brian Inglis Nov. 20, 2015

Nov. 20, 2015

http://www.itu.int/net/pressoffice/press_releases/2015/53.aspx -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

10 15

Coordinated Universal Time (UTC) to retain “leap second”
by Brian Inglis Nov. 19, 2015

Nov. 19, 2015

http://www.itu.int/net/pressoffice/press_releases/2015/53.aspx -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

1 0

zoneinfo vs zoneinfo-leaps
by Ken Murchison Nov. 17, 2015

Nov. 17, 2015

Maybe this is a FAQ but I haven't found the answer. Having studied up the tzfile(5) format and written some code to produce these files, I'm wondering why the files in zoneinfo-leaps include the leap records AND adjust the transition times by the appropriate number of leap seconds. This seems redundant to me. If the file includes the leap second records, why not let the consumer adjust the transitions? -- Kenneth Murchison Principal Systems Software Engineer Carnegie Mellon University

7 11

Note of thanks - Australian Tz Acronyms [SEC=UNCLASSIFIED]
by Peter Stagg Nov. 17, 2015

Nov. 17, 2015

This week we (The Australian Bureau of Meteorology) updated the TZ database on our web systems to the latest version and we are finally able to display Australian time zone acronyms properly via scripts using the TZ database - AEST, AEDT etc. Thanks for the inclusion of these in the TZ database. Regards, Peter Stagg | Web Systems Technology Officer [bureau_logo] Web Systems, Platform Services, Information Technology Services, Information Systems & Services Division, Bureau of Meteorology GPO Box 1289 Melbourne VIC 3001 Level 6, 700 Collins Street, Docklands VIC 3008 Tel: +61 3 9669 4232 | p.stagg(a)bom.gov.au www.bom.gov.au<http://www.bom.gov.au/>

1 0

[PROPOSED PATCH] Improve guesses for post-2037 Iran
by Paul Eggert Nov. 14, 2015

Nov. 14, 2015

* NEWS: Document this. * asia (Iran): Predict 2038 and later DST to be March 21 thru Sept. 21. This is not correct, but it's better than predicting no DST. --- NEWS | 6 ++++++ asia | 11 +++++++++-- 2 files changed, 15 insertions(+), 2 deletions(-) diff --git a/NEWS b/NEWS index b4e1483..121e0e4 100644 --- a/NEWS +++ b/NEWS @@ -11,6 +11,12 @@ Unreleased, experimental changes America/Metlakatla switched from PST all year to AKST/AKDT on 2015-11-01 at 02:00. (Thanks to Steffen Thorsen.) + Changes affecting future time stamps + + Asia/Tehran now has DST predictions for the year 2038 and later, + to be March 21 00:00 to September 21 00:00. This is likely better + than predicting no DST, albeit off by a day every now and then. + Changes affecting documentation tz-link.htm mentions the BDE library (thanks to Andrew Paprocki). diff --git a/asia b/asia index 5467024..f170244 100644 --- a/asia +++ b/asia @@ -1084,8 +1084,15 @@ Rule Iran 2032 2033 - Mar 21 0:00 1:00 D Rule Iran 2032 2033 - Sep 21 0:00 0 S Rule Iran 2034 2035 - Mar 22 0:00 1:00 D Rule Iran 2034 2035 - Sep 22 0:00 0 S -Rule Iran 2036 2037 - Mar 21 0:00 1:00 D -Rule Iran 2036 2037 - Sep 21 0:00 0 S +# +# The following rules are approximations starting in the year 2038. +# These are the best post-2037 approximations available, given the +# restrictions of a single rule using a Gregorian-based data format. +# At some point this table will need to be extended, though quite +# possibly Iran will change the rules first. +Rule Iran 2036 max - Mar 21 0:00 1:00 D +Rule Iran 2036 max - Sep 21 0:00 0 S + # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Tehran 3:25:44 - LMT 1916 3:25:44 - TMT 1946 # Tehran Mean Time -- 2.5.0

1 0

America/Metlakatla now follows Alaska
by Steffen Thorsen Nov. 13, 2015

Nov. 13, 2015

It seems Metlakatla did go off PST on Sunday, November 1, changing their time to AKST and are going to follow Alaska's DST, switching between AKST and AKDT from now on. Based on: http://www.krbd.org/2015/10/30/annette-island-times-they-are-a-changing/ Best regards, Steffen Thorsen - timeanddate.com

12 18

A discussion on POSIX on new timezone related C APIs
by Random832 Nov. 13, 2015

Nov. 13, 2015

http://austingroupbugs.net/view.php?id=1005 The proposals seem to be: 1. Something involving integrating timezone information into locale_t 2. Something along the lines of NetBSD's _z/_rz functions The fact that no-one seems to have a reference C implementation of localizing time zone names/abbreviations also came up. I don't know how open they are to outsiders sticking their noses into the process though, just thought some people here might be interested. Also proposed is the addition of "tm_nsec" to struct tm, and the new APIs in one of the proposals use a struct timespec rather than time_t.

4 4

Re: [tz] efele.net/tz maps updated
by Steve Jones Nov. 11, 2015

Nov. 11, 2015

At 08:13 PM 11/10/2015, Chris Walton wrote: >There is one (and only one) community in the >western half of the PRRD;Â it is the isolated >community of Fort Ware (also known as >Kwadacha).Â It has a population of about 270. There is another - Tsay Keh Deme, about 86km to the south (56.892014, -124.963373). Population 245. I imagine it also observes Vancouver time. I have tried to reach out to the RCMP detachment office there via the "contact us" thingy on the RCMP website, but have not received any response. I didn't feel like making an international call. Their detachment webpage is: www.rcmp-grc.gc.ca/detach/en/d/212. If it's a free call for you, it may be worth giving them a ring. There area of coverage is basically the whole western part of the PRRD. I imagine they could speak with some authority about whatever time zone observances may be practiced throughout the area. But it has to be Pacific time - nothing else makes sense regardless of the opinion of the GIS folks at the PRRD. Their primary economic ties will be outside the PRRD to their south and west. Regards, Steve Jones Emacs! 14h pg

2 1

Re: [tz] efele.net/tz maps updated
by Steve Jones Nov. 11, 2015

Nov. 11, 2015

Sorry, typo, it's Dene, not Deme. Tsay Keh Dene. >There is another - Tsay Keh Deme, about 86km to the south \ Regards, Steve Jones Emacs!

1 0

Re: [tz] America/Santa_Isabel
by Steve Jones Nov. 10, 2015

Nov. 10, 2015

At 01:19 PM 11/9/2015, Matt Johnson (PNP) wrote: >Our research concluded that there is no known location in the state >of Baja California that observes Mexican DST rules. All are on US >DST rules. The 20km boundary mentioned in the law applies in the >other Mexican states, but not in Baja California due to the >exclusions mentioned in the same law. One more data point in support of your conclusion: I reached out to a contact on Cedros Island, which nearly touches the southern border of Baja. He indicates that clocks on the island adjusted on November 1. Regards, Steve Jones Emacs!

1 0

Re: [tz] America/Santa_Isabel
by Matt Johnson (PNP) Nov. 9, 2015

Nov. 9, 2015

WRT my previous comment: "I've got a parallel discussion going within Microsoft about this zone, and will share the findings of our research. " Our research concluded that there is no known location in the state of Baja California that observes Mexican DST rules. All are on US DST rules. The 20km boundary mentioned in the law applies in the other Mexican states, but not in Baja California due to the exclusions mentioned in the same law. This agrees with ADO’s observations about San Quintin. Also, the Wikipedia information about San Quintin becoming its own municipality is outdated. The decision was overturned by the Mexican supreme court due to jurisdictional issues. See: http://www2.scjn.gob.mx/juridica/engroses/cerrados/Publico/13000980.009-268… Thanks, Matt Johnson Microsoft ________________________________ Date: Sun, 1 Nov 2015 20:32:17 -0500 From: arthurdavidolson(a)gmail.com<mailto:arthurdavidolson@gmail.com> To: tz(a)iana.org<mailto:tz@iana.org> Subject: Re: [tz] America/Santa_Isabel And in today's final listen, XEQIN announced "cinco de la tarde con veinticuatro minutos" (literally "5 of the afternoon with 24 minutes") at about 8:24 PM USEST--the same as 5:24 PM USPST. At least this year, San Quintín seems to have followed has followed US rules. So much for that bookmark. @dashdashado On Sat, Oct 31, 2015 at 10:12 PM, Arthur David Olson <arthurdavidolson(a)gmail.com<mailto:arthurdavidolson@gmail.com>> wrote: This evening's next-to-last listen to XEQIN included advice to listeners to "atrarse una hora de su reloj" ("delay your clock by an hour") tonight before going to bed. The end-of-broadcast-day national anthem, due at 7:00 p. m. local time, came shortly after 10:00 p.m. USEDT, consistent with San Quintín still being on daylight saving time. The last listen should be tomorrow or Monday evening. @dashdashado On Tue, Oct 27, 2015 at 3:44 PM, Matt Johnson <mj1856(a)hotmail.com<mailto:mj1856@hotmail.com>> wrote: Acknowledged. Thanks for the clarification. -Matt ________________________________ From: Paul Eggert<mailto:eggert@cs.ucla.edu> Sent: ‎10/‎27/‎2015 10:31 AM To: Matt Johnson<mailto:mj1856@hotmail.com> Cc: Time Zone Mailing List<mailto:tz@iana.org> Subject: Re: [tz] America/Santa_Isabel Matt Johnson wrote: > there is a corresponding entry in Windows, "Pacific Standard Time (Mexico) |(UTC-08:00) Baja California" I'm afraid this will have to be adjusted on the Microsoft end. There needs to be a procedure for removing time zones that turn out to be mistakes. America/Santa_Isabel is a mistake, and I suppose we can view this as an opportunity for ironing out any procedural glitches while removing it. We do have a backward compatibility link on the tzdata side; perhaps that will help for the Microsoft side. > Also, there's a chance that San Quintin could indeed start using Mexican DST rules in 2017, We can create a zone America/San_Quintin if that happens.

1 0