January 2016 - 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

7 regions in Russia submitted draft bills to change their time zones
by Alexander Krivenyshev Feb. 18, 2016

Feb. 18, 2016

After researching several official government documents (duma.gov.ru), there are at least 7 regions in Russia (not 3) that have submitted draft bills proposing changes to their time zones. Those regions are: - Zabaykalsky Krai / Chita (draft bill date of entry July 16, 2015)- has recently received approval to change time zone from UTC+8 to UTC+9 - Astrakhan Oblast / Astrakhan (draft bill date of entry Aug. 15, 2015), UTC+3 to UTC+4 - Sakhalin Oblast / Yuzhno-Sakhalinsk (draft bill date of entry Sep. 28, 2015), UTC+10 to UTC+11 - Ulyanovsk Oblast / Ulyanovsk (draft bill date of entry Nov. 03, 2015), UTC+3 to UTC+4 - Altai republic / Gorno-Altaysk (draft bill date of entry Nov. 23, 2015), UTC+6 to UTC+7 - Altai Krai / Barnaul (draft bill date of entry Dec. 03, 2015), UTC+6 to UTC+7 - Magadan Oblast / Magadan (draft bill date of entry Dec. 08, 2015), UTC+10 to UTC+11 See as a reference Russia map with 7 regions to change their time zones (darker colors of blue, green, red): http://www.worldtimezone.com/russia-time-zones-map-2016-04.gif (vs current http://www.worldtimezone.com/time-russia12.php) Seems that draft bill in Russia must pass through the following phases before being signed into law: Phase 1- The State Duma Council draft bill review Phase 2- Pass three (3) readings/revisions by the State Duma Phase 3- Approval by the Federation Council Phase 4- Signed by the President. Currently there are 6 additional regions in Russia that have requested to change their time zones (make amendments to the current Federal Law "On the calculation of time"), those draft bills were introduced at different times and are in different phases of the approval (or rejection) process. To make it easier to understand, below are the approximate phases of the remaining regions requesting time zones changes: - Sakhalin Oblast / Yuzhno-Sakhalinsk - Phase 1 (introduced to the State Duma Council) - Astrakhan Oblast / Astrakhan - Phase 2 ( first reading by the State Duma) - Ulyanovsk Oblast / Ulyanovsk - Phase 1 (introduced to the State Duma Council) - Altai republic / Gorno-Altaysk - Phase 1 (introduced to the State Duma Council) - Altai Krai / Barnaul - Phase 1 (introduced to the State Duma Council) - Magadan Oblast / Magadan - Phase 1 ( introduced to the Chairman of the State Duma- part of the State Duma Council) It is hard to say, how many above regions will be able to get through all these phases and change their time zones by March 27, 2016. We will try to keep our eyes on it. Alexander Krivenyshev http://www.worldtimezone.com

15 38

[PATCH 1/5] tzselect.ksh: TZ validation bugs
by J William Piggott Feb. 14, 2016

Feb. 14, 2016

This commit fixes the following POSIX TZ validation bugs in tzselect.ksh. Did not allow: TZ name quoting (<, >): TZ="<EST+5>5" Allowed: TZ name == Non-alpha characters: TZ="E!T5" Time > 24 hours Julian date == J0 Julian date > J365 Julian date > 365 Month date > M12.x.x Month date > Mx.5.x Month date > Mx.x.6 Month date < M1.x.x Month date < Mx.1.x Signed-off-by: J William Piggott <elseifthen(a)gmx.com> --- tzselect.ksh | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/tzselect.ksh b/tzselect.ksh index df5621f..10570b6 100644 --- a/tzselect.ksh +++ b/tzselect.ksh @@ -346,11 +346,14 @@ while 'that is 10 hours ahead (east) of UTC.' read TZ $AWK -v TZ="$TZ" 'BEGIN { - tzname = "[^-+,0-9][^-+,0-9][^-+,0-9]+" - time = "[0-2]?[0-9](:[0-5][0-9](:[0-5][0-9])?)?" + tzname = "(<[[:alnum:]+-]{3,}>|[[:alpha:]]{3,})" + time = "(2[0-4]|[0-1]?[0-9])" \ + "(:[0-5][0-9](:[0-5][0-9])?)?" offset = "[-+]?" time - date = "(J?[0-9]+|M[0-9]+\\.[0-9]+\\.[0-9]+)" - datetime = "," date "(/" time ")?" + mdate = "M([1-9]|1[0-2])\\.[1-5]\\.[0-6]" + jdate = "((J[1-9]|[0-9]|J?[1-2]?[0-9][0-9])" \ + "|J?3[0-5][0-9]|J?36[0-5])" + datetime = ",(" mdate "|" jdate ")(/" time ")?" tzpattern = "^(:.*|" tzname offset "(" tzname \ "(" offset ")?(" datetime datetime ")?)?)$" if (TZ ~ tzpattern) exit 1

3 18

[PATCH 0/4] checktab.awk and zone tabs
by J William Piggott Feb. 13, 2016

Feb. 13, 2016

This patch set applies on top of the two sets I posted on Jan 20 2016 with Subject: [PATCH 0/5] tzselect.ksh [PATCH 1/3] zone*.tab: make consistent 'most locations' Paul, I just noticed I used the wrong style commit messages on the first to sets. If you'd like me to fix them and resubmit V2, just let me know. J William Piggott (4): checktab.awk: fix comment (field 4) checks checktab.awk: don't repeat missing comment errors zone1970.tab: update column 4 definition Remove unneeded zone tab comments NEWS | 8 ++++++++ checktab.awk | 8 +++++++- zone.tab | 20 ++++++++++---------- zone1970.tab | 21 +++++++++++---------- 4 files changed, 36 insertions(+), 21 deletions(-) --- All of the patch sets are from the same branch of my github account here is the request-pull output: The following changes since commit 9e588f4c0bc2a1861c923aaa7760ebc7b024d885: Cite Ogle's 2015 book on history of civil time (2016-01-11 16:21:15 -0800) are available in the git repository at: git@github.com:jwpi/tz.git tzselect for you to fetch changes up to a7a2ef246e669c30533e5fd1cb01ef85fe921935: Remove unneeded zone tab comments (2016-01-23 18:57:43 -0500) ---------------------------------------------------------------- J William Piggott (12): zone*.tab: make consistent 'most locations' zone*.tab: fix capitalization zone*.tab: fix Salta comment tzselect.ksh: TZ validation bugs tzselect.ksh: regions list to inclusive tzselect.ksh: sort regions list tzselect.ksh: time scales assumed tzselect.ksh: add script mode option checktab.awk: fix comment (field 4) checks checktab.awk: don't repeat missing comment errors zone1970.tab: update column 4 definition Remove unneeded zone tab comments NEWS | 8 ++++++++ checktab.awk | 8 +++++++- tzselect.ksh | 47 ++++++++++++++++++++++++++++++----------------- zone.tab | 44 ++++++++++++++++++++++---------------------- zone1970.tab | 51 ++++++++++++++++++++++++++------------------------- 5 files changed, 93 insertions(+), 65 deletions(-)

2 5

[PATCH 1/3] zone*.tab: make consistent 'most locations'
by J William Piggott Feb. 13, 2016

Feb. 13, 2016

modified: zone.tab modified: zone1970.tab The comments (field 4) inconsistently use leading area names. This causes tzselect's output to be mixed: Please select one of the following time zone regions. 1) Buenos Aires (BA, CF) 2) most locations (CB, CC, CN, ER, FM, MN, SE, SF) Please select one of the following time zone regions. 1) Lord Howe Island 2) Macquarie Island 3) Tasmania - most locations The leading name is absent from entries when it would match the chosen country, but sometimes the chosen country is no longer visible. Including the country name doesn't hurt anything and it improves readability. Signed-off-by: J William Piggott <elseifthen(a)gmx.com> --- zone.tab | 22 +++++++++++----------- zone1970.tab | 22 +++++++++++----------- 2 files changed, 22 insertions(+), 22 deletions(-) diff --git a/zone.tab b/zone.tab index d267f5b..2fd7953 100644 --- a/zone.tab +++ b/zone.tab @@ -41,7 +41,7 @@ AQ -6640+14001 Antarctica/DumontDUrville Dumont-d'Urville Station, Adelie Land AQ -690022+0393524 Antarctica/Syowa Syowa Station, E Ongul I AQ -720041+0023206 Antarctica/Troll Troll Station, Queen Maud Land AR -3436-05827 America/Argentina/Buenos_Aires Buenos Aires (BA, CF) -AR -3124-06411 America/Argentina/Cordoba most locations (CB, CC, CN, ER, FM, MN, SE, SF) +AR -3124-06411 America/Argentina/Cordoba Argentina - most locations (CB, CC, CN, ER, FM, MN, SE, SF) AR -2447-06525 America/Argentina/Salta (SA, LP, NQ, RN) AR -2411-06518 America/Argentina/Jujuy Jujuy (JY) AR -2649-06513 America/Argentina/Tucuman Tucuman (TM) @@ -141,7 +141,7 @@ CG -0416+01517 Africa/Brazzaville CH +4723+00832 Europe/Zurich CI +0519-00402 Africa/Abidjan CK -2114-15946 Pacific/Rarotonga -CL -3327-07040 America/Santiago most locations +CL -3327-07040 America/Santiago Chile - most locations CL -2709-10926 Pacific/Easter Easter Island CM +0403+00942 Africa/Douala CN +3114+12128 Asia/Shanghai Beijing Time @@ -154,7 +154,7 @@ CW +1211-06900 America/Curacao CX -1025+10543 Indian/Christmas CY +3510+03322 Asia/Nicosia CZ +5005+01426 Europe/Prague -DE +5230+01322 Europe/Berlin most locations +DE +5230+01322 Europe/Berlin Germany - most locations DE +4742+00841 Europe/Busingen Busingen DJ +1136+04309 Africa/Djibouti DK +5540+01235 Europe/Copenhagen @@ -187,7 +187,7 @@ GF +0456-05220 America/Cayenne GG +4927-00232 Europe/Guernsey GH +0533-00013 Africa/Accra GI +3608-00521 Europe/Gibraltar -GL +6411-05144 America/Godthab most locations +GL +6411-05144 America/Godthab Greenland - most locations GL +7646-01840 America/Danmarkshavn east coast, north of Scoresbysund GL +7029-02158 America/Scoresbysund Scoresbysund / Ittoqqortoormiit GL +7634-06847 America/Thule Thule / Pituffik @@ -235,7 +235,7 @@ KP +3901+12545 Asia/Pyongyang KR +3733+12658 Asia/Seoul KW +2920+04759 Asia/Kuwait KY +1918-08123 America/Cayman -KZ +4315+07657 Asia/Almaty most locations +KZ +4315+07657 Asia/Almaty Kazakhstan - most locations KZ +4448+06528 Asia/Qyzylorda Qyzylorda (Kyzylorda, Kzyl-Orda) KZ +5017+05710 Asia/Aqtobe Aqtobe (Aktobe) KZ +4431+05016 Asia/Aqtau Atyrau (Atirau, Gur'yev), Mangghystau (Mankistau) @@ -257,12 +257,12 @@ MD +4700+02850 Europe/Chisinau ME +4226+01916 Europe/Podgorica MF +1804-06305 America/Marigot MG -1855+04731 Indian/Antananarivo -MH +0709+17112 Pacific/Majuro most locations +MH +0709+17112 Pacific/Majuro Marshall Islands - most locations MH +0905+16720 Pacific/Kwajalein Kwajalein MK +4159+02126 Europe/Skopje ML +1239-00800 Africa/Bamako MM +1647+09610 Asia/Rangoon -MN +4755+10653 Asia/Ulaanbaatar most locations +MN +4755+10653 Asia/Ulaanbaatar Mongolia - most locations MN +4801+09139 Asia/Hovd Bayan-Olgiy, Govi-Altai, Hovd, Uvs, Zavkhan MN +4804+11430 Asia/Choibalsan Dornod, Sukhbaatar MO +2214+11335 Asia/Macau @@ -274,7 +274,7 @@ MT +3554+01431 Europe/Malta MU -2010+05730 Indian/Mauritius MV +0410+07330 Indian/Maldives MW -1547+03500 Africa/Blantyre -MX +1924-09909 America/Mexico_City Central Time - most locations +MX +1924-09909 America/Mexico_City Mexican Central Time - most locations MX +2105-08646 America/Cancun Eastern Standard Time - Quintana Roo MX +2058-08937 America/Merida Central Time - Campeche, Yucatan MX +2540-10019 America/Monterrey Mexican Central Time - Coahuila, Durango, Nuevo Leon, Tamaulipas away from US border @@ -299,7 +299,7 @@ NO +5955+01045 Europe/Oslo NP +2743+08519 Asia/Kathmandu NR -0031+16655 Pacific/Nauru NU -1901-16955 Pacific/Niue -NZ -3652+17446 Pacific/Auckland most locations +NZ -3652+17446 Pacific/Auckland New Zealand - most locations NZ -4357-17633 Pacific/Chatham Chatham Islands OM +2336+05835 Asia/Muscat PA +0858-07932 America/Panama @@ -307,7 +307,7 @@ PE -1203-07703 America/Lima PF -1732-14934 Pacific/Tahiti Society Islands PF -0900-13930 Pacific/Marquesas Marquesas Islands PF -2308-13457 Pacific/Gambier Gambier Islands -PG -0930+14710 Pacific/Port_Moresby most locations +PG -0930+14710 Pacific/Port_Moresby Papua New Guinea - most locations PG -0613+15534 Pacific/Bougainville Bougainville PH +1435+12100 Asia/Manila PK +2452+06703 Asia/Karachi @@ -385,7 +385,7 @@ TT +1039-06131 America/Port_of_Spain TV -0831+17913 Pacific/Funafuti TW +2503+12130 Asia/Taipei TZ -0648+03917 Africa/Dar_es_Salaam -UA +5026+03031 Europe/Kiev most locations +UA +5026+03031 Europe/Kiev Ukraine - most locations UA +4837+02218 Europe/Uzhgorod Ruthenia UA +4750+03510 Europe/Zaporozhye Zaporozh'ye, E Lugansk / Zaporizhia, E Luhansk UG +0019+03225 Africa/Kampala diff --git a/zone1970.tab b/zone1970.tab index e77d6cf..c050269 100644 --- a/zone1970.tab +++ b/zone1970.tab @@ -48,7 +48,7 @@ AQ -6640+14001 Antarctica/DumontDUrville Dumont-d'Urville Station, AdÃ©lie Land AQ -690022+0393524 Antarctica/Syowa Syowa Station, E Ongul I AQ -720041+0023206 Antarctica/Troll Troll Station, Queen Maud Land AR -3436-05827 America/Argentina/Buenos_Aires Buenos Aires (BA, CF) -AR -3124-06411 America/Argentina/Cordoba most locations (CB, CC, CN, ER, FM, MN, SE, SF) +AR -3124-06411 America/Argentina/Cordoba Argentina - most locations (CB, CC, CN, ER, FM, MN, SE, SF) AR -2447-06525 America/Argentina/Salta (SA, LP, NQ, RN) AR -2411-06518 America/Argentina/Jujuy Jujuy (JY) AR -2649-06513 America/Argentina/Tucuman TucumÃ¡n (TM) @@ -134,7 +134,7 @@ CC -1210+09655 Indian/Cocos CH,DE,LI +4723+00832 Europe/Zurich Swiss time CI,BF,GM,GN,ML,MR,SH,SL,SN,ST,TG +0519-00402 Africa/Abidjan CK -2114-15946 Pacific/Rarotonga -CL -3327-07040 America/Santiago most locations +CL -3327-07040 America/Santiago Chile - most locations CL -2709-10926 Pacific/Easter Easter Island CN +3114+12128 Asia/Shanghai Beijing Time CN +4348+08735 Asia/Urumqi Xinjiang Time @@ -146,7 +146,7 @@ CW,AW,BQ,SX +1211-06900 America/Curacao CX -1025+10543 Indian/Christmas CY +3510+03322 Asia/Nicosia CZ,SK +5005+01426 Europe/Prague -DE +5230+01322 Europe/Berlin Berlin time +DE +5230+01322 Europe/Berlin Germany - most locations DK +5540+01235 Europe/Copenhagen DO +1828-06954 America/Santo_Domingo DZ +3647+00303 Africa/Algiers @@ -171,7 +171,7 @@ GE +4143+04449 Asia/Tbilisi GF +0456-05220 America/Cayenne GH +0533-00013 Africa/Accra GI +3608-00521 Europe/Gibraltar -GL +6411-05144 America/Godthab most locations +GL +6411-05144 America/Godthab Greenland - most locations GL +7646-01840 America/Danmarkshavn east coast, north of Scoresbysund GL +7029-02158 America/Scoresbysund Scoresbysund / Ittoqqortoormiit GL +7634-06847 America/Thule Thule / Pituffik @@ -208,7 +208,7 @@ KI +0152-15720 Pacific/Kiritimati Line Islands KP +3901+12545 Asia/Pyongyang KR +3733+12658 Asia/Seoul KY +1918-08123 America/Cayman -KZ +4315+07657 Asia/Almaty most locations +KZ +4315+07657 Asia/Almaty Kazakhstan - most locations KZ +4448+06528 Asia/Qyzylorda Qyzylorda (Kyzylorda, Kzyl-Orda) KZ +5017+05710 Asia/Aqtobe Aqtobe (Aktobe) KZ +4431+05016 Asia/Aqtau Atyrau (Atirau, Gur'yev), Mangghystau (Mankistau) @@ -223,10 +223,10 @@ LY +3254+01311 Africa/Tripoli MA +3339-00735 Africa/Casablanca MC +4342+00723 Europe/Monaco MD +4700+02850 Europe/Chisinau -MH +0709+17112 Pacific/Majuro most locations +MH +0709+17112 Pacific/Majuro Marshall Islands - most locations MH +0905+16720 Pacific/Kwajalein Kwajalein MM +1647+09610 Asia/Rangoon -MN +4755+10653 Asia/Ulaanbaatar most locations +MN +4755+10653 Asia/Ulaanbaatar Mongolia - most locations MN +4801+09139 Asia/Hovd Bayan-Ãlgii, Govi-Altai, Hovd, Uvs, Zavkhan MN +4804+11430 Asia/Choibalsan Dornod, SÃ¼khbaatar MO +2214+11335 Asia/Macau @@ -234,7 +234,7 @@ MQ +1436-06105 America/Martinique MT +3554+01431 Europe/Malta MU -2010+05730 Indian/Mauritius MV +0410+07330 Indian/Maldives -MX +1924-09909 America/Mexico_City Central Time - most locations +MX +1924-09909 America/Mexico_City Mexican Central Time - most locations MX +2105-08646 America/Cancun Eastern Standard Time - Quintana Roo MX +2058-08937 America/Merida Central Time - Campeche, YucatÃ¡n MX +2540-10019 America/Monterrey Mexican Central Time - Coahuila, Durango, Nuevo LeÃ³n, Tamaulipas away from US border @@ -265,7 +265,7 @@ PE -1203-07703 America/Lima PF -1732-14934 Pacific/Tahiti Society Islands PF -0900-13930 Pacific/Marquesas Marquesas Islands PF -2308-13457 Pacific/Gambier Gambier Islands -PG -0930+14710 Pacific/Port_Moresby most locations +PG -0930+14710 Pacific/Port_Moresby Papua New Guinea - most locations PG -0613+15534 Pacific/Bougainville Bougainville PH +1435+12100 Asia/Manila PK +2452+06703 Asia/Karachi @@ -317,7 +317,7 @@ SY +3330+03618 Asia/Damascus TC +2128-07108 America/Grand_Turk TD +1207+01503 Africa/Ndjamena TF -492110+0701303 Indian/Kerguelen Kerguelen, St Paul I, Amsterdam I -TH,KH,LA,VN +1345+10031 Asia/Bangkok most of Indochina +TH,KH,LA,VN +1345+10031 Asia/Bangkok Indochina - most locations TJ +3835+06848 Asia/Dushanbe TK -0922-17114 Pacific/Fakaofo TL -0833+12535 Asia/Dili @@ -328,7 +328,7 @@ TR +4101+02858 Europe/Istanbul TT,AG,AI,BL,DM,GD,GP,KN,LC,MF,MS,VC,VG,VI +1039-06131 America/Port_of_Spain TV -0831+17913 Pacific/Funafuti TW +2503+12130 Asia/Taipei -UA +5026+03031 Europe/Kiev most locations +UA +5026+03031 Europe/Kiev Ukraine - most locations UA +4837+02218 Europe/Uzhgorod Ruthenia UA +4750+03510 Europe/Zaporozhye Zaporozh'ye, E Lugansk / Zaporizhia, E Luhansk UM +1917+16637 Pacific/Wake Wake Island

2 5

[tz-announce] 2016a release of tz code and data available
by Paul Eggert Jan. 28, 2016

Jan. 28, 2016

The 2016a 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: Changes affecting future time stamps America/Cayman will not observe daylight saving this year after all. Revert our guess that it would. (Thanks to Matt Johnson.) Asia/Chita switches from +0800 to +0900 on 2016-03-27 at 02:00. (Thanks to Alexander Krivenyshev.) 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 past and future time stamps America/Metlakatla switched from PST all year to AKST/AKDT on 2015-11-01 at 02:00. (Thanks to Steffen Thorsen.) America/Santa_Isabel has been removed, and replaced with a backward compatibility link to America/Tijuana. Its contents were apparently based on a misreading of Mexican legislation. Changes affecting past time stamps Asia/Karachi's two transition times in 2002 were off by a minute. (Thanks to Matt Johnson.) Changes affecting build procedure An installer can now combine leap seconds with use of the backzone file, e.g., with 'make PACKRATDATA=backzone REDO=posix_right zones'. The old 'make posix_packrat' rule is now marked as obsolescent. (Thanks to Ian Abbott for an initial implementation.) Changes affecting documentation and commentary A new file LICENSE makes it easier to see that the code and data are mostly public-domain. (Thanks to James Knight.) The three non-public-domain files now use the current (3-clause) BSD license instead of older versions of that license. tz-link.htm mentions the BDE library (thanks to Andrew Paprocki), CCTZ (thanks to Tim Parenti), TimeJones.com, and has a new section on editing tz source files (with a mention of Sublime zoneinfo, thanks to Gilmore Davidson). The Theory and asia files now mention the 2015 book "The Global Transformation of Time, 1870-1950", and cite a couple of reviews. The America/Chicago entry now documents the informal use of US central time in Fort Pierre, South Dakota. (Thanks to Rick McDermid, Matt Johnson, and Steve Jones.) Here are links to the release files: ftp://ftp.iana.org/tz/releases/tzcode2016a.tar.gz ftp://ftp.iana.org/tz/releases/tzdata2016a.tar.gz The files are also available via HTTP as follows: http://www.iana.org/time-zones/repository/releases/tzcode2016a.tar.gz http://www.iana.org/time-zones/repository/releases/tzdata2016a.tar.gz As usual, links to the latest release files are here: http://www.iana.org/time-zones/repository/tzcode-latest.tar.gz http://www.iana.org/time-zones/repository/tzdata-latest.tar.gz ftp://ftp.iana.org/tz/tzcode-latest.tar.gz ftp://ftp.iana.org/tz/tzdata-latest.tar.gz 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 0f03a534155f590681e45ad8a3202a4412a8ba80 dated Tue Jan 26 23:28:02 2016 -0800 and tagged '2016a' in the experimental github repository at <https://github.com/eggert/tz>. Here are the SHA-512 checksums for the release files: 33a1078ba16aef19048aa97ce1816fc5368061bfe40eddc0e7e246ca57c4a535eaf2f03847128e971a6d959f34ea77224bf33fd53dc6a0c006450dde35222223 tzcode2016a.tar.gz 9aa5f61a73afa5070dfb1d1982945d268ea8215663d0cd594216500aff14797ea5591ccfd488dc2280902fa1820bf782623624912b669873728431258fe10ec1 tzdata2016a.tar.gz Here are the GPG checksums for the release files: -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAABAgAGBQJWqHJCAAoJEO2X6Q5iqn40vggP/iUDh0UDG3g9lQfV41yXx+Dg 4Ln+RVSEkfKE82ffPSJzvyRQzp1l/U2alopcI+Ernou7hmcrYYcJC827QZ+boiLv uK5/LIDqI/uBb6j3bxt2aiymsbL1+q4C3RDypujKa4lh0kuinO6MUTpnIEGmNdAl l0q6pWyJfH4UYxT8UCjCvJrNQwMxCD+31oz4blUMUr3h/TdAfd/uRs0xm06Fi6ss HSzJ1P2gej4uTdGzuWczbZrCdkpLvZXhYt/kIQ3tOl+9bAJOJa0/3zVuIxUO6DNL w4RRaHbdtvtDUw7vqGcIe2nZHZ4GdRfHINi2sflHfH6auq53x6mWiOGbDqAMQkk4 2HFnHr8sawB+6TA8vSgayOKg+Ja2eX/4IXBqrGBzt96a0AfJDgWlulgA5oc6lQvy BAYtgXYfUTg05EEZOIvL1kDR3CZJB2v6U72DVT8y6Bs52w1ue1/7HfhY9N5hHor5 nCeaeqoQLopMdfpMn3pATqRXvTFsxmlDaN8Y2S6IZyvQgPqpPGBdaH0i+Ran5bXf vKCRpxS6rsSvOdliNCnr2hytk5UrRdxuLJ6yWiUjhVBszGISUR15w2iwK26NifIR ZbMV4e2bcZl7kGcq+dIeTtjAoXeP+Bh3Y3NfIq37O1NK8gsx31GfGMVifJYxE4ti qtlircuZtjdkQR0GmACZ =cUhj -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAABAgAGBQJWqHJHAAoJEO2X6Q5iqn40O/QP/0dWxkvnViAXibpFmZeQF9qC 18S3oL35D9CwWdIo60zmQ1K4lzq7k3K4fCs+VAZnlp8DeqxbnX/utfFsxRGBZu9F fHYeIyxPB+Gm45SE3USefZgD38LDDmEIkeQ+SE3geDSVKMO/gHGk55jl/8vylm1d bIdU/1PNSr5EZt2LlXuRRO1lnQ6cW1G5vDtGj4nyB++/FDIi4qsBMQy21qqRs2K3 vcw3yRQbqz7rEUxG/k0d9KU/dRUY980f4pHx2kkYpRKL2nhLeYqH3jfRUhOgwupS Yp4fVFF1gZWbxjcf8Xb97jpCW0q4TL4wPYFQNOsLJJGtNeRP1Pgz7FsjH1qwSUy2 blX1UWhtFAjUnHF+XO7Z5DUexoq1+14OFWSGwxuGpwUNxgtMmRr4KZVuKg9ag7jC hKoegozcf90lZ+PmuAXNbz1S9DcILRFG7qnV+E3oKPjyOQBnU1z7Mx0rtleT14iQ Pdi0ygv4/9cs07dOsF3oqRfwqldYogYF0/O3559eQzGfKdxOIu0eLZV9PLaCnAoM 2zpnPOBqBIwUHRynd6EBJyeu1WCRoC/oIvEs8A8QINf6EN/Fu/Xxgmf8HwwRIOE+ xgJeNE4Z4xjWiCmu7dvBZJIZZi7dmWaHwste+WxUMZ0boDsYOmnkGCclpSb+MzpX 49a9DUdrNMurifgNd4vy =WafQ -----END PGP SIGNATURE----- _______________________________________________ tz-announce mailing list tz-announce(a)iana.org https://mm.icann.org/mailman/listinfo/tz-announce

1 0

Opposition to Cayman DST
by Paul Eggert Jan. 27, 2016

Jan. 27, 2016

Currently tzdata is guessing that Cayman will introduce daylight saving time this year. This is not official, though. There is opposition in the Legislative Assembly, and if the LA rejects it we will need to update tzdata. Ragoonath R. Gov’t Daylight Savings Time plans to get resistance in LA. Cayman Reporter 2016-01-08. http://www.caymanreporter.com/2016/01/08/govt-daylight-savings-time-plans-g…

3 4

Re: [tz] Opposition to Cayman DST
by Steve Jones Jan. 27, 2016

Jan. 27, 2016

A complex area, timewise: http://OnTimeZone.com/images/caribbean.jpg (includes recent changes in Quinta Roo and the Turks and Caicos.) (magenta lines = time zone borders) (blue lines = dst observance borders) I wonder if the recent thaw in US/Cuban relations will have any tangential change in the economic relationship between the Caymans and Cuba. If so it might increase pressure to adopt DST. Steve Jones

1 0

If you lie about the time zone, your iPhone will have its revenge
by Paul Eggert Jan. 22, 2016

Jan. 22, 2016

iPhone 6s and iPhone 6s Plus users are reporting that their phones are sometimes showing plenty of charge left even though their batteries are actually depleted, leaving some users stranded out of power. Apparently users who change their time (e.g., to gain unfair advantage in games like Candy Crush Saga) can confuse iOS 9.2 into not updating the battery percentage indicator. A similar problem can occur to users who set the time zone manually. One workaround is to reboot and revert to getting date and time from the network. Reference: Smith J. iPhone 6s battery bug leaves users longing for iOS 9.3. GottaBeMobile.com 2016-01-17. http://www.gottabemobile.com/2016/01/17/iphone-6s-battery-bug-leaves-users-…

8 11

[PATCH 0/5] tzselect.ksh
by J William Piggott Jan. 20, 2016

Jan. 20, 2016

Hello, In the process of writing a tzselect style application which uses a dialog UI, I discovered some bugs and other issues with tzselect and the support files it uses (zone*.tab). I split the patches into two sets to address the issues. The second set is for the zone*.tab files and have a subject line like: [PATCH 1/3] zone*.tab: ... J William Piggott (5): tzselect.ksh: TZ validation bugs tzselect.ksh: regions list to inclusive tzselect.ksh: sort regions list tzselect.ksh: time scales assumed tzselect.ksh: add script mode option tzselect.ksh | 47 ++++++++++++++++++++++++++++++----------------- 1 file changed, 30 insertions(+), 17 deletions(-) ______________________________________ They are also available from my github account. Both patch sets are from the same branch. Here is the request-pull output: The following changes since commit 9e588f4c0bc2a1861c923aaa7760ebc7b024d885: Cite Ogle's 2015 book on history of civil time (2016-01-11 16:21:15 -0800) are available in the git repository at: git@github.com:jwpi/tz.git tzselect for you to fetch changes up to 2b16c464c2cb1c7a16297b861d9c060c151272bb: tzselect.ksh: add script mode option (2016-01-19 15:42:12 -0500) ---------------------------------------------------------------- J William Piggott (8): zone*.tab: make consistent 'most locations' zone*.tab: fix capitalization zone*.tab: fix Salta comment tzselect.ksh: TZ validation bugs tzselect.ksh: regions list to inclusive tzselect.ksh: sort regions list tzselect.ksh: time scales assumed tzselect.ksh: add script mode option tzselect.ksh | 47 ++++++++++++++++++++++++++++++----------------- zone.tab | 26 +++++++++++++------------- zone1970.tab | 32 ++++++++++++++++---------------- 3 files changed, 59 insertions(+), 46 deletions(-)

1 0

Re: [tz] tzcode test suite
by Paul Eggert Jan. 18, 2016

Jan. 18, 2016

On 01/14/2016 10:18 AM, Steve Summit wrote: >> >* Would you mind if we changed "if(" to "if (" ... > Not at all. (Not my style, but I truly don't care.) OK, thanks, attached are a few followup patches. The first adjusts white space, the second fixes a glitch I introduced earlier. The test cases still fail, though. I wonder why they fail for me and not for you? Some more things I noticed. testsuite.c assumes time_t is equivalent to long, by using the %ld printf format to print it. That's not portable. time_t might have a different width from long, and time_t might be unsigned. zdump.c's tformat function gets it right. Adding 1900 to tm_year can overflow, if tm_year is close to INT_MAX. quick_timegm is full of gotchas like that. As it's not needed and is likely to have bugs in testing, how about if we remove it? This is in the 3rd attached patch. The remaining uses of isleap have a similar problem. It would be better to use isleap_sum; see tzfile.h.

2 2

tz-art.htm: The Good Wife
by Arthur David Olson Jan. 18, 2016

Jan. 18, 2016

@dashdashado *** /tmp/,atz-art.htm 2016-01-17 22:55:53.832841200 -0500 --- /tmp/,btz-art.htm 2016-01-17 22:55:53.951096000 -0500 *************** *** 274,279 **** --- 274,288 ---- savings days. Lousy farmers."</td></tr> <tr><td> </td></tr> + <tr><td>TV episode title</td><td>Tracks</td></tr> + <tr><td>TV series</td><td>The Good Wife</td></tr> + <tr><td>TV episode number</td><td>12, season 7</td></tr> + <tr><td>Network</td><td>CBS</td></tr> + <tr><td>Air date</td><td>2016-01-17</td></tr> + <tr><td>Notes</td><td>The applicability of a contract hinges on the + time zone associated with a video time stamp.</td></tr> + <tr><td> </td></tr> + <tr><td>Artist</td><td>Jules Verne</td></tr> <tr><td>Book</td><td>Around the World in Eighty Days (Le tour du monde en quatre-vingts jours)</td></tr>

2 1

tzcode test suite
by scs＠eskimo.com Jan. 16, 2016

Jan. 16, 2016

I've been doing some surgery on localtime.c (perhaps more on that later), and to check my work I felt the need for a decent gmtime/localtime/mktime test suite. I'm sure such a thing has been written numbers of times before, and there may be some reason not to have one in the tzcode distribution, but if not, I'd like to donate this one for inclusion. It runs in two modes, one driven by a script containing (in effect) a list of known-good (time_t, struct tm) pairs, and another which exhaustively runs a potentially very large set of synthesized tests over a specified range. The script contains lines such as gmtime 1234567890 2009-02-13 23:31:30 and tz America/New_York localtime 483811200 1985-05-01 12:00:00 z=EDT o=-14400 dst=1 which are used to drive reciprocal pairs of tests on gmtime/timegm or localtime/mktime, in a reasonably obvious way. A line like the first one tests both that gmtime(1234567890) gives 2009-02-13, and also that timegm on 2009-02-13 23:31:30 gives 1234567890. There are keywords for setting the expected output values for zone, offset, and DST flag (as shown). There are also additional keywords to set the expected values of tm_wday and tm_yday. (See the attached test script for more examples.) I'm also enclosing a patch to the tzcode Makefile to add a "make tests" target, building and appropriately invoking this tool. At the moment this tool tests only localtime, gmtime, mktime, and timegm. It would make sense to have coverage of ctime and strftime, too, which would be straightforward enough to add. Note that the zone names in the attached 'testcases' script match those built by the stock tzdata distribution, but not necessarily those installed on the machine where you may be trying to run this. See the long comment at the top of testsuite.c for additional information. Enjoy! Steve Summit scs(a)eskimo.com

2 4

Bulletin C 51: No leap second in June 2016, but new leap second file
by Martin Burnicki Jan. 13, 2016

Jan. 13, 2016

The International Earth rotation Service (IERS) has just published bulletin C 51, announcing that *no* leap second will be introduced at the end of June 2016: ftp://hpiers.obspm.fr/iers/bul/bulc/bulletinc.dat The IERS now also makes a leap second file available for use with NTP: https://hpiers.obspm.fr/iers/bul/bulc/ntp/leap-seconds.list This new file has the expiration date set to 28 December 2016, so users who have configured ntpd to use the leap second file should upgrade their local copy of the file. The leap second file does not only announce leap seconds, it also provides ntpd and thus the OS kernel with the current TAI/UTC offset, which is helpful for applications working with TAI. Martin -- Martin Burnicki Senior Software Engineer MEINBERG Funkuhren GmbH & Co. KG Email: martin.burnicki(a)meinberg.de Phone: +49 (0)5281 9309-14 Fax: +49 (0)5281 9309-30 Lange Wand 9, 31812 Bad Pyrmont, Germany Amtsgericht Hannover 17HRA 100322 Geschäftsführer/Managing Directors: Günter Meinberg, Werner Meinberg, Andre Hartmann, Heiko Gerstung Web: http://www.meinberg.de

5 7

[PROPOSED PATCH] Cite Ogle's 2015 book on history of civil time
by Paul Eggert Jan. 12, 2016

Jan. 12, 2016

* NEWS, Theory, asia: Mention Ogle's book, or reviews of it. --- NEWS | 3 +++ Theory | 10 +++++++++- asia | 9 +++++++++ 3 files changed, 21 insertions(+), 1 deletion(-) diff --git a/NEWS b/NEWS index f9de054..14a87ac 100644 --- a/NEWS +++ b/NEWS @@ -47,6 +47,9 @@ Unreleased, experimental changes on editing tz source files (with a mention of Sublime zoneinfo, thanks to Gilmore Davidson). + The Theory and asia files now mention the 2015 book "The Global + Transformation of Time, 1870-1950", and cite a couple of reviews. + The America/Chicago entry now documents the informal use of US central time in Fort Pierre, South Dakota. (Thanks to Rick McDermid, Matt Johnson, and Steve Jones.) diff --git a/Theory b/Theory index 96cba51..4f9c226 100644 --- a/Theory +++ b/Theory @@ -263,7 +263,15 @@ Errors in the tz database arise from many sources: be needed if the tz database's scope were extended to cover even just the known or guessed history of standard time; for example, the current single entry for France would need to split into dozens - of entries, perhaps hundreds. + of entries, perhaps hundreds. And in most of the world even this + approach would be misleading due to widespread disagreement or + indifference about what times should be observed. In her 2015 book + "The Global Transformation of Time, 1870-1950", Vanessa Ogle writes + "Outside of Europe and North America there was no system of time + zones at all, often not even a stable landscape of mean times, + prior to the middle decades of the twentieth century". See: + Timothy Shenk, Booked: A Global History of Time. Dissent 2015-12-17 + https://www.dissentmagazine.org/blog/booked-a-global-history-of-time-vaness… * Most of the pre-1970 data entries come from unreliable sources, often astrology books that lack citations and whose compilers evidently diff --git a/asia b/asia index 7756444..a59d653 100644 --- a/asia +++ b/asia @@ -874,6 +874,15 @@ Zone Asia/Dili 8:22:20 - LMT 1912 Jan 1 9:00 - TLT # India + +# From Ian P. Beacock, in "A brief history of (modern) time", The Atlantic +# http://www.theatlantic.com/technology/archive/2015/12/the-creation-of-moder… +# (2015-12-22): +# In January 1906, several thousand cotton-mill workers rioted on the +# outskirts of Bombay.... They were protesting the proposed abolition of +# local time in favor of Indian Standard Time.... Journalists called this +# dispute the "Battle of the Clocks." It lasted nearly half a century. + # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Kolkata 5:53:28 - LMT 1880 # Kolkata 5:53:20 - HMT 1941 Oct # Howrah Mean Time? -- 2.5.0

1 0

About Time Zone
by Chenshiwei (Yona) Jan. 7, 2016

Jan. 7, 2016

Hi, Dear IANA I met some problem in time zone data. >From the timeanddate.com, we know the time zone have some changes. [cid:image001.png@01D1488F.C9B0DEB0] But it seemed that iana.org did not update the time zone data about two months. [cid:image002.png@01D1488F.C9B0DEB0] So, I'd like to know if iana.org stop maintaining the time zone data. Could you give some suggestion about this.

2 1

Pakistan DST in 2002
by Matt Johnson Jan. 2, 2016

Jan. 2, 2016

The Pakistan rules for 2002 have the transition at 0:01 instead of 0:00. This disagrees with the commentary: # From Rives McDow (2002-03-13): # I have been advised that Pakistan has decided to adopt dst on a # TRIAL basis for one year, starting 00:01 local time on April 7, 2002 # and ending at 00:01 local time October 6, 2002. This is what I was # told, but I believe that the actual time of change may be 00:00; the # 00:01 was to make it clear which day it was on. The remaining rules in the file are at 0:00. Also, our friends at timeanddate.com have it at midnight as well. http://www.timeanddate.com/time/change/pakistan/karachi?year=2002 Of course, the problem with any fall-back transition after 0:00 and before 1:00 is that it implies the calendar date goes forward, then back, then forward again. In this case going from Oct 6, back to Oct 5, then forward to Oct 6 again. While there are indeed areas where this certainly occurred, we should be careful not to introduce that artificially. If there is uncertainty between 0:00 and 0:01, we should assume 0:00 (IMHO). Thanks, Matt

3 3

Zabaykalsky Krai (Chita) time zone changes to UTC+9 on March 27, 2016
by Alexander Krivenyshev Jan. 2, 2016

Jan. 2, 2016

On December 30, 2015 Russian President Vladimir Putin signed the federal law changing the time zone in the Trans-Baikal Territory (Zabaykalsky Krai) - Asia/Chita from UTC+8 to UTC+9. Effective date will be March 27, 2016 at 2:00am. Official publication on: http://publication.pravo.gov.ru/Document/View/0001201512300107? index=0&rangeSize=1 Alexander Krivenyshev (worldtimezone.com)

3 4