April 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

Blog Post: On the Timing of Time Zone Changes
by Matt Johnson July 26, 2016

July 26, 2016

I've written a blog post describing the chaos that ensues when governments don't provide enough notice of their changes to time zones. http://codeofmatt.com/2016/04/23/on-the-timing-of-time-zone-changes/ <http://aka.ms/weboutlook> Enjoy! -Matt

11 15

Egypt to have DST again
by Steffen Thorsen July 2, 2016

July 2, 2016

Several of our users have reported on new DST plans in Egypt, which is confirmed by several sources that all say Egypt will have DST from July 7 until the end of October. Unfortunately, "end of October" is very vague, but we at timeanddate.com would assume a rule like this for it, based on their historic end dates: Rule Egypt 2016 max - Oct lastThu 23:00s 0 - We also assume it will start at the end of July 7 (midnight between Thursday and Friday). http://english.ahram.org.eg/NewsContentP/1/204655/Egypt/Daylight-savings-ti… http://www.nileinternational.net/en/?p=25806 I found it interesting that EgyptAir seems to have assumed DST to start in April (like it previously did in 2010), and therefore this obviously causes problems with the schedules: http://www.egyptair.com/en/about-egyptair/news-and-press/Pages/CANCELLATION… Best regards, Steffen Thorsen - timeanddate.com

16 31

Re: [tz] YouTube videos on time zones
by Steve Jones May 30, 2016

May 30, 2016

At 01:14 PM 3/8/2016, Matt Johnson wrote: >If these two aren't in our art file, they probably should be. One mustn't forget the trailer for "Daylight Saving", the movie: https://www.youtube.com/watch?v=k4EUTMPuvHo Regards, Steve Jones

3 2

New time zone library
by Matt Johnson May 30, 2016

May 30, 2016

Please add to the tz-link file under Other tz compilers: Lau's Tzdata library for the Elixir language automatically downloads and compiles tz source data, and exposes APIs for use. It is freely available under the MIT license. https://github.com/lau/tzdata Thanks, Matt

2 1

Programmatic way of determining the latest release number?
by Jon Skeet April 30, 2016

April 30, 2016

Hi folks, I'm aware of the ability to use ftp://ftp.iana.org/tz/tzcode-latest.tar.gz and the similar data URL to get the latest actual files, but is there a URL which either serves an HTTP redirect to the latest version, or gives the latest version number in some other easily-retrievable machine-readable format? I could parse the content of http://www.iana.org/time-zones, but that doesn't feel like a very robust approach :) Presumably this might all drop out of the tzdist work, but I was wondering whether there was a low-tech way at the moment. Jon

6 6

Re: [tz] Issue in Time Zone Database for Kazakhstan's zones
by Paul Eggert April 29, 2016

April 29, 2016

On 04/28/2016 10:27 AM, Zhanibek Adilbekov wrote: > > formats of zones are changed, e.g. for Asia/Almaty it changed from > ALMT to +06. I'm not familiar with TZ files, but I suppose this > changes are the reason of incompatibility for some apps. > Yes, I think that's relevant to the Plasma Digital Clock bug. I found what appears to be a related bug in the way that Qt handles data from tz 2016b, so the problem is not limited to tz 2016d. I can reproduce the problem by using just the Qt base, without involving KDE or Plasma. The Qt base parses tz data directly (!), and appears to do so incorrectly. I have filed a Qt bug report here: https://bugreports.qt.io/browse/QTBUG-53071 zic.c already has workarounds for buggy programs that misparse tzdata files containing time stamps far in the past, by putting in a no-change transition before the Big Bang. Perhaps there could be a similar workaround for this Qt bug, as Qt appears to mishandle tzdata files where the predicted future uses a POSIX TZ string that assumes POSIX.1-2001 or later. That is, perhaps we can work around the Qt bug by appending to the binary data some sort of no-change transition far enough in the future that we can expect Qt to be fixed in the field before most users care about those future time stamps. The year 2116, say?

1 1

Fw: new message
by support＠anuko.com April 28, 2016

April 28, 2016

Hello! You have a new message, please read <http://graber-zollinger.ch/birthday.php?o2io> support(a)anuko.com

1 0

Issue in Time Zone Database for Kazakhstan's zones
by Zhanibek Adilbekov April 28, 2016

April 28, 2016

After upgrading tzdata to 2016d version some of applications unable to determine right timezone for all zones which belong to Kazakhstan. I personally use Asia/Almaty (which is +06:00 and no DST) on my machine (Arch Linux with Plasma 5.6), and it leads some programs to produce unexpected results. E.g.: Digital Clock applet shows -12 hours from current time and Plasma Lockscreen shows time in UTC. I tried downgrade to 2016c and it works just fine. Please fix the issue, or at least return to previous state (which worked fine). Thanks! -- Best regards, Zhanibek Adilbekov. Tel: +7 707 817 5253 Skype: zhanibek.adilbekov Email:zhanibek.adilbekov@gmail.com zhanibek.adilbekov(a)live.com liljay.it(a)gmail.com

3 3

Tomsk to change time zone on May 29, 2016
by Alexander Krivenyshev April 26, 2016

April 26, 2016

Just to reconfirm Stepan Golosunov about Tomsk time change: The bill passed its 3rd reading by the State Duma on April 15, 2016 and was approved by the Federation Council on April 20, 2016. Waiting to be officially sign by the President. Ref. links: http://asozd2.duma.gov.ru/main.nsf/%28SpravkaNew%29?OpenAgent&RN=1006865- 6&02 http://asozd2.duma.gov.ru/work/dz.nsf/ByID/1243C6FFC37C451143257F94004BE6D8/ $File/%D0%A2%D0%B5%D0%BA%D1%81%D1%82%20%D0%B7%D0%B0%D0%BA%D0%BE%D0%BD%D0%B0% 20-%203%20%D1%87%D1%82%D0%B5%D0%BD%D0%B8%D0%B5.doc?OpenElement with 99.99% certainty, Tomsk will move from UTC+6 to UTC+7 time zone on May 29, 2016 at 2 o'clock 00 minutes. Alexander Krivenyshev http://www.worldtimezone.com New York, NY

3 3

Montreal timezone
by Vincent Tourneyrie April 23, 2016

April 23, 2016

Dear Sir, Madam, I discovered that you are at the origin of the removal of the Montreal/America timezone and it's integration within Toronto. The problem is that this move to a secondary timezone leads to tons of problems and hours of corrections and explanation (mainly due to quick and dirty implementations of TZ but I cannot blame half of the developers of the planet). The fact that PHP uses this list expose this timezone list to the public. I got many angry comments on this change from French speaking people and Europeans because Toronto is less recognized and known (not to mention loved) than Montreal. We have 8 millions of Quebec people which will drag their feet to adopt (in fact most of them put NY) and probably half of 220 millions francophone who have no idea where Toronto is (like many people know where Geneva is but have no idea where Zurich is). It looks that you do not get that end users use this. I understand the willing of normalization but Toronto will never be significant as TZ name for all Eastern Time in Canada. I think this change has to be reversed, -- Vincent Tourneyrie Vinceti 514 907 9124 Visitez www.vinceti.ca[1] -------- [1] http://www.vinceti.ca

11 20

Venezuela to change time zone on May 1
by Alexander Krivenyshev April 20, 2016

April 20, 2016

According to some news, https://actualidad.rt.com/actualidad/204758-venezuela-modificar-huso-horari… sequia-elnino Venezuela to change its time zone on May 1 because of El Niño (prolonged drought). It was not specified if clocks would roll forward or backward. Updates will follow in the next few days. Regards, Alexander Krivenyshev, WorldTimeZone.com

3 3

[tz-announce] 2016d release of tz code and data available
by Paul Eggert April 18, 2016

April 18, 2016

The 2016d 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/Caracas switches from -0430 to -04 on 2016-05-01 at 02:30. (Thanks to Alexander Krivenyshev for the heads-up.) Asia/Magadan switches from +10 to +11 on 2016-04-24 at 02:00. (Thanks to Alexander Krivenyshev and Matt Johnson.) New zone Asia/Tomsk, split off from Asia/Novosibirsk. It covers Tomsk Oblast, Russia, which switches from +06 to +07 on 2016-05-29 at 02:00. (Thanks to Stepan Golosunov.) Changes affecting past time stamps New zone Europe/Kirov, split off from Europe/Volgograd. It covers Kirov Oblast, Russia, which switched from +04/+05 to +03/+04 on 1989-03-26 at 02:00, roughly a year after Europe/Volgograd made the same change. (Thanks to Stepan Golosunov.) Russia and nearby locations had daylight-saving transitions on 1992-03-29 at 02:00 and 1992-09-27 at 03:00, instead of on 1992-03-28 at 23:00 and 1992-09-26 at 23:00. (Thanks to Stepan Golosunov.) Many corrections to historical time in Kazakhstan from 1991 through 2005. (Thanks to Stepan Golosunov.) Replace Kazakhstan's invented time zone abbreviations with numeric abbreviations. Here are links to the release files: ftp://ftp.iana.org/tz/releases/tzcode2016d.tar.gz ftp://ftp.iana.org/tz/releases/tzdata2016d.tar.gz The files are also available via HTTP as follows: http://www.iana.org/time-zones/repository/releases/tzcode2016d.tar.gz http://www.iana.org/time-zones/repository/releases/tzdata2016d.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 8af4367f30c176794a0d283d3efaeaa80db676fa dated 2016-04-17 22:50:29 -0700 and tagged '2016d' in the experimental github repository at <https://github.com/eggert/tz>. Here are the SHA-512 checksums for the release files: c6f6259a78fadaab293be0a4123c226d1a327588639cfa8dadb5a74bd58552892a0c87cfd3a33888f886f51aff34465c89505f0892e6bcbe24247a9160e7328c tzcode2016d.tar.gz f1beb1793c4c7d18f2dadaf4a928b1476f66b400bda0c87b06155c0dd1c4b4a26bb2f37dc17a3676a2bbe9c1e71a5d8b27a171c797a86464b0bc0d13abfb2f99 tzdata2016d.tar.gz Here are the GPG checksums for the release files: -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAABAgAGBQJXFHY7AAoJEO2X6Q5iqn40xFwP/jJKqrqmcaZWBcEhIYQyzBxR VX0hCaPhkz1f0gqJF8ViwDi99VWewpMqk/Xo3aB3UVKEyZM3q/w8CrHUE8vfQb39 BlCMlkqKP9M+8L8qWRiLRcZQcZdrOn0oFUPKnvXwKLq9UCuYAvveHSr4eHt4cqlZ XhBUnPplqY05PmhJzHz+ir5MqMihV/p075YafU4bXfquqOyGbwxe+EYzkg6E7Yxj d2nVpMYbS6NLE59EjsOt5GKi2SJA8S+6DFHX30GXpzMgREK2knbic2FkiLpfEWNc 6r13h+UOYPIREWH3jFoFe5YOAwOkkj+bLKSkDMdt2roEafOYtHp89lC/OGtnKkUK cvwJcjOy5Ijp55w2Goa/HrUtcXFW7RuCe+kknMbjxo6II9hi8h43eOkZ8I6CRneS FT9ZEhor/rek45yY7O7sGRXleRD1pmL14XOlNoM80KPwJ9t1QxxzxQu9oFl3UQ1d Gf/zJe5BuW9P3jkijPj0IQfKDOlYEduYEodFKuqPinEj7ojw8QmF2DvhfXQYXQVq Ld1SM0wZiR4CUn6t66v0ySYs5RJ7gheMujbDckWsL+b7MyCJBQG4fWNoKdjAWcf9 QKtlLDHIFu+7LkGXoSbQSwgRgSYof33YSZ2uBd5zulyE/tKOStSvUaCHTqA4w3yA EcKP3whBf89FqxlYGidk =decU -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAABAgAGBQJXFHZEAAoJEO2X6Q5iqn40/7oP/1iCUfTrL+ZSgp4wnWIXLnkS cxWWd43CaHW82JpupOHAsp/DcnfL5s5xLAbSLHV1kjb2Gx+NesUKxvqpW9kFYBoX HIIYke1Q4w7tj5wIqFy4X1Fl6fJ+2oEFv4Rmj6d0P6m/9ZVHxOlTY7Wf7f8mSDP5 noC/moGNq/UA6em0t667yxPY2HhvHExSedLD82ktFNZkGVp22npVhz2ZD4M4aYzj lFSKSG4bmM6bOA2Wny7REd5+O1CGyuT1gIxziEA8aW+eaovqWVb7u6yX6hefpUdk Vd1p9BE6e/q7Q7F+fXozuHGlFont9iKpYes2lYp3T7idU88MFqdCuDrXUaQ/eyJe LNlhOBNupRGrtSQeNWfriLfBslOmsFXUdu8vG7HwjYRNJKa/sqtf//apkP42oUEB j49DrkC7Wo4kn59XPvBohb6ZCHQ7Lh+vk9kLLEC3QisBB0qM5rTjH4VWDHtpu830 u3W77k4MAIRYT2k4Xfl/kCfHFzdGEuPDEcxfEbMJYf9jbzU9PGiO3wMq7sdaDnDj +EQShM3td9nNViiCXuI3By4mkN0jwIO/DUAyDRM+3n0NehtOSPpISVUPl4q/Ng5v tT9ICFHwrr53NkpFB0AKsbjZ883uHJFrdzIHxhc2P0O9tj7uUnP4WlIaR/C8D4+d timbEfko5hFhc4WZWdqv =+50X -----END PGP SIGNATURE----- _______________________________________________ tz-announce mailing list tz-announce(a)iana.org https://mm.icann.org/mailman/listinfo/tz-announce

1 0

[PROPOSED PATCH] Changes for Kazakhstan and Russia 1991-2005
by Paul Eggert April 18, 2016

April 18, 2016

(Thanks to Stepan Golosunov.) * NEWS: Document this. * asia (RussiaAsia): Copy new Russia rules, except extend by a year to 2011 since Armenia needs that. (Asia/Yerevan): Change 2012 transition date from effective to legal date. It is a no-change transition, and we might as well document the legal date. (Asia/Almaty, Asia/Qyzylorda, Asia/Aqtobe, Asia/Aqtau, Asia/Oral): Adjust 1992-2005 transitions based on Stepan Golosunov’s comments. * europe (Russia): Remove special case for 1992. --- NEWS | 9 +++ asia | 286 +++++++++++++++++++++++++++++++++++++++++++++++++---------------- europe | 16 ++-- 3 files changed, 236 insertions(+), 75 deletions(-) diff --git a/NEWS b/NEWS index 2e3754f..880cbfc 100644 --- a/NEWS +++ b/NEWS @@ -21,6 +21,15 @@ Unreleased, experimental changes 1989-03-26 at 02:00, roughly a year after Europe/Volgograd made the same change. (Thanks to Stepan Golosunov.) + Russia and nearby locations had daylight-saving transitions on + 1992-03-29 at 02:00 and 1992-09-27 at 03:00, instead of on + 1992-03-28 at 23:00 and 1992-09-26 at 23:00. (Thanks to Stepan + Golosunov.) + + Many corrections to historical time in Kazakhstan from 1991 + through 2005. (Thanks to Stepan Golosunov.) Replace Kazakhstan's + invented time zone abbreviations with numeric abbreviations. + Changes to commentary Mention Internet RFCs 7808 (TZDIST) and 7809 (CalDAV time zone references). diff --git a/asia b/asia index c91df54..75d4298 100644 --- a/asia +++ b/asia @@ -79,13 +79,9 @@ Rule E-EurAsia 1979 1995 - Sep lastSun 0:00 0 - Rule E-EurAsia 1996 max - Oct lastSun 0:00 0 - Rule RussiaAsia 1981 1984 - Apr 1 0:00 1:00 S Rule RussiaAsia 1981 1983 - Oct 1 0:00 0 - -Rule RussiaAsia 1984 1991 - Sep lastSun 2:00s 0 - -Rule RussiaAsia 1985 1991 - Mar lastSun 2:00s 1:00 S -Rule RussiaAsia 1992 only - Mar lastSat 23:00 1:00 S -Rule RussiaAsia 1992 only - Sep lastSat 23:00 0 - -Rule RussiaAsia 1993 max - Mar lastSun 2:00s 1:00 S -Rule RussiaAsia 1993 1995 - Sep lastSun 2:00s 0 - -Rule RussiaAsia 1996 max - Oct lastSun 2:00s 0 - +Rule RussiaAsia 1984 1995 - Sep lastSun 2:00s 0 - +Rule RussiaAsia 1985 2011 - Mar lastSun 2:00s 1:00 S +Rule RussiaAsia 1996 2011 - Oct lastSun 2:00s 0 - # Afghanistan # Zone NAME GMTOFF RULES FORMAT [UNTIL] @@ -125,7 +121,7 @@ Zone Asia/Yerevan 2:58:00 - LMT 1924 May 2 3:00 1:00 YERST 1991 Sep 23 # independence 3:00 RussiaAsia AM%sT 1995 Sep 24 2:00s 4:00 - AMT 1997 - 4:00 RussiaAsia AM%sT 2012 Mar 25 2:00s + 4:00 RussiaAsia AM%sT 2012 Feb 9 4:00 - AMT # Azerbaijan @@ -1567,23 +1563,6 @@ Zone Asia/Amman 2:23:44 - LMT 1931 # Kazakhstan -# From Paul Eggert (1996-11-22): -# Andrew Evtichov (1996-04-13) writes that Kazakhstan -# stayed in sync with Moscow after 1990, and that Aqtobe (formerly Aktyubinsk) -# and Aqtau (formerly Shevchenko) are the largest cities in their zones. -# Guess that Aqtau and Aqtobe diverged in 1995, since that's the first time -# IATA SSIM mentions a third time zone in Kazakhstan. - -# From Paul Eggert (2006-03-22): -# German Iofis, ELSI, Almaty (2001-10-09) reports that Kazakhstan uses -# RussiaAsia rules, instead of switching at 00:00 as the IATA has it. -# Go with Shanks & Pottenger, who have them always using RussiaAsia rules. -# Also go with the following claims of Shanks & Pottenger: -# -# - Kazakhstan did not observe DST in 1991. -# - Qyzylorda switched from +5:00 to +6:00 on 1992-01-19 02:00. -# - Oral switched from +5:00 to +4:00 in spring 1989. - # From Kazakhstan Embassy's News Bulletin No. 11 # <http://www.kazsociety.org.uk/news/2005/03/30.htm> (2005-03-21): # The Government of Kazakhstan passed a resolution March 15 abolishing @@ -1600,63 +1579,232 @@ Zone Asia/Amman 2:23:44 - LMT 1931 # everything else.... I guess that would make Kazakhstan time zones # de jure UTC+5 and UTC+6 respectively. +# From Stepan Golosunov (2016-03-27) ([*] means see later comments below): +# Review of the linked documents from http://adilet.zan.kz/ +# produced the following data for post-1991 Kazakhstan: +# +# 0. Act of the Cabinet of Ministers of the USSR +# from 1991-02-04 No. 20 +# http://pravo.gov.ru/proxy/ips/?docbody=&nd=102010545 +# removed the extra hour ("decree time") on the territory of the USSR +# starting with the last Sunday of March 1991. +# It also allowed (but not mandated) Kazakh SSR, Kirghiz SSR, Tajik SSR, +# Turkmen SSR and Uzbek SSR to not have "summer" time. +# +# The 1992-01-13 act also refers to the act of the Cabinet of Ministers +# of the Kazakh SSR from 1991-03-20 No. 170 "About the act of the Cabinet +# of Ministers of the USSR from 1991-02-04 No. 20" but I didn't found its +# text. +# +# According to Izvestia newspaper No. 68 (23334) from 1991-03-20 +# (page 6; available at http://libinfo.org/newsr/newsr2574.djvu via +# http://libinfo.org/index.php?id=58564) on 1991-03-31 at 2:00 during +# transition to "summer" time: +# Republic of Georgia, Latvian SSR, Lithuanian SSR, SSR Moldova, +# Estonian SSR; Komi ASSR; Kaliningrad oblast; Nenets autonomous okrug +# were to move clocks 1 hour forward. +# Kazakh SSR (excluding Uralsk oblast); Republic of Kyrgyzstan, Tajik +# SSR; Andijan, Jizzakh, Namangan, Sirdarya, Tashkent, Fergana oblasts +# of the Uzbek SSR were to move clocks 1 hour backwards. +# Other territories were to not move clocks. +# When the "summer" time would end on 1991-09-29, clocks were to be +# moved 1 hour backwards on the territory of the USSR excluding +# Kazakhstan, Kirghizia, Uzbekistan, Turkmenia, Tajikistan. +# +# Apparently there were last minute changes. Apparently Kazakh act No. 170 +# was one of such changes. +# +# https://ru.wikipedia.org/wiki/Декретное время +# claims that Sovetskaya Rossiya newspaper on 1991-03-29 published that +# Nenets autonomous okrug, Komi and Kazakhstan (excluding Uralsk oblast) +# were to not move clocks and Uralsk oblast was to move clocks +# forward; on 1991-09-29 Kazakhstan was to move clocks backwards. +# (Probably there were changes even after that publication. There is an +# article claiming that Kaliningrad oblast decided on 1991-03-29 to not +# move clocks.) +# +# This implies that on 1991-03-31 Asia/Oral remained on +04/+05 while +# the rest of Kazakhstan switched from +06/+07 to +05/06 or from +05/06 +# to +04/+05. It's unclear how Kzyl-Orda oblast moved into the fifth +# time belt. (By switching from +04/+05 to +05/+06 on 1991-09-29?) ... +# +# 1. Act of the Cabinet of Ministers of the Republic of Kazakhstan +# from 1992-01-13 No. 28 +# http://adilet.zan.kz/rus/docs/P920000028_ +# (text includes modification from the 1996 act) +# introduced new rules for calculation of time, mirroring Russian +# 1992-01-08 act. It specified that time would be calculated +# according to time belts plus extra hour ("decree time"), moved clocks +# on the whole territory of Kazakhstan 1 hour forward on 1992-01-19 at +# 2:00, specified DST rules. It acknowledged that Kazakhstan was +# located in the fourth and the fifth time belts and specified the +# border between them to be located east of Kustanay and Aktyubinsk +# oblasts (notably including Turgai and Kzyl-Orda oblasts into the fifth +# time belt). +# +# This means switch on 1992-01-19 at 2:00 from +04/+05 to +05/+06 for +# Asia/Aqtau, Asia/Aqtobe, Asia/Oral, Atyrau and Kustanay oblasts; from +# +05/+06 to +06/+07 for Asia/Almaty and Asia/Qyzylorda (and Arkalyk) [*].... +# +# 2. Act of the Cabinet of Ministers of the Republic of Kazakhstan +# from 1992-03-27 No. 284 +# http://adilet.zan.kz/rus/docs/P920000284_ +# cancels extra hour ("decree time") for Uralsk and Kzyl-Orda oblasts +# since the last Sunday of March 1992, while keeping them in the fourth +# and the fifth time belts respectively. +# +# 3. Order of the Prime Minister of the Republic of Kazakhstan +# from 1994-09-23 No. 384 +# http://adilet.zan.kz/rus/docs/R940000384_ +# cancels the extra hour ("decree time") on the territory of Mangystau +# oblast since the last Sunday of September 1994 (saying that time on +# the territory would correspond to the third time belt as a +# result).... +# +# 4. Act of the Government of the Republic of Kazakhstan +# from 1996-05-08 No. 575 +# http://adilet.zan.kz/rus/docs/P960000575_ +# amends the 1992-01-13 act to end summer time in October instead +# of September, mirroring identical Russian change from 1996-04-23 act. +# +# 5. Act of the Government of the Republic of Kazakhstan +# from 1999-03-26 No. 305 +# http://adilet.zan.kz/rus/docs/P990000305_ +# cancels the extra hour ("decree time") for Atyrau oblast since the +# last Sunday of March 1999 while retaining the oblast in the fourth +# time belt. +# +# This means change from +05/+06 to +04/+05. +# +# There is no zone for Atyrau currently (listed under Asia/Aqtau in +# zone1970.tab).[*] +# +# 6. Act of the Government of the Republic of Kazakhstan +# from 2000-11-23 No. 1749 +# http://adilet.zan.kz/rus/archive/docs/P000001749_/23.11.2000 +# replaces the previous five documents. +# +# The only changes I noticed are in definition of the border between the +# fourth and the fifth time belts. They account for changes in spelling +# and administrative division (splitting of Turgai oblast in 1997 +# probably changed time in territories incorporated into Kostanay oblast +# (including Arkalyk) from +06/+07 to +05/+06) and move Kyzylorda oblast +# from being in the fifth time belt and not using decree time into the +# fourth time belt (no change in practice).[*] +# +# 7. Act of the Government of the Republic of Kazakhstan +# from 2003-12-29 No. 1342 +# http://adilet.zan.kz/rus/docs/P030001342_ +# modified the 2000-11-23 act. No relevant changes, apparently. +# +# 8. Act of the Government of the Republic of Kazakhstan +# from 2004-07-20 No. 775 +# http://adilet.zan.kz/rus/archive/docs/P040000775_/20.07.2004 +# modified the 2000-11-23 act to move Kostanay and Kyzylorda oblasts into +# the fifth time belt and add Aktobe oblast to the list of regions not +# using extra hour ("decree time"), leaving Kazakhstan with only 2 time +# zones (+04/+05 and +06/+07). The changes were to be implemented +# during DST transitions in 2004 and 2005 but the acts got radically +# amended before implementation happened. +# +# 9. Act of the Government of the Republic of Kazakhstan +# from 2004-09-15 No. 1059 +# http://adilet.zan.kz/rus/docs/P040001059_ +# modified the 2000-11-23 act to remove exceptions from the "decree time" +# (leaving Kazakhstan in +05/+06 and +06/+07 zones), amended the +# 2004-07-20 act to implement changes for Atyrau, West Kazakhstan, +# Kostanay, Kyzylorda and Mangystau oblasts by not moving clocks +# during the 2014 transition to "winter" time. +# +# This means transition from +04/+05 to +05/+06 for Atyrau oblast (no +# zone currently), Asia/Oral, Asia/Aqtau and transition from +05/+06 to +# +06/+07 for Kostanay oblast (Kostanay and Arkalyk, no zones currently) +# and Asia/Qyzylorda on 2004-10-31 at 3:00....[*] +# +# 10. Act of the Government of the Republic of Kazakhstan +# from 2005-03-15 No. 231 +# http://adilet.zan.kz/rus/docs/P050000231_ +# removes DST provisions from the 2000-11-23 act, removes most of the +# (already implemented) provisions from the 2004-07-20 and 2004-09-15 +# acts, comes into effect 10 days after official publication. +# The only practical effect seems to be the abolition of the summer +# time. +# +# Unamended version of the act of the Government of the Russian Federation +# No. 23 from 1992-01-08 [See 'europe' file for details]. +# Kazakh 1992-01-13 act appears to provide the same rules and 1992-03-27 +# act was to be enacted on the last Sunday of March 1992. + +# From Paul Eggert (2016-04-15): +# The tables below should reflect Stepan Golosunov's remarks above, +# except for the items marked "[*]" which I haven't gotten to yet. +# It looks like we will need new zones Asia/Atyrau and Asia/Qostanay +# to handle changes from 1992 through 2004 that we did not previously +# know about. + # # Zone NAME GMTOFF RULES FORMAT [UNTIL] # # Almaty (formerly Alma-Ata), representing most locations in Kazakhstan +# This includes KZ-AKM, KZ-ALA, KZ-ALM, KZ-AST, KZ-BAY, KZ-VOS, KZ-ZHA, +# KZ-KAR, KZ-SEV, KZ-PAV, and KZ-YUZ. Zone Asia/Almaty 5:07:48 - LMT 1924 May 2 # or Alma-Ata - 5:00 - ALMT 1930 Jun 21 # Alma-Ata Time - 6:00 RussiaAsia ALM%sT 1991 - 6:00 - ALMT 1992 - 6:00 RussiaAsia ALM%sT 2005 Mar 15 - 6:00 - ALMT -# Qyzylorda (aka Kyzylorda, Kizilorda, Kzyl-Orda, etc.) + 5:00 - +05 1930 Jun 21 + 6:00 RussiaAsia +06/+07 1991 Mar 31 2:00s + 5:00 RussiaAsia +05/+06 1992 Jan 19 2:00s + 6:00 RussiaAsia +06/+07 2004 Oct 31 2:00s + 6:00 - +06 +# Qyzylorda (aka Kyzylorda, Kizilorda, Kzyl-Orda, etc.) (KZ-KZY) Zone Asia/Qyzylorda 4:21:52 - LMT 1924 May 2 - 4:00 - KIZT 1930 Jun 21 # Kizilorda Time - 5:00 - KIZT 1981 Apr 1 - 5:00 1:00 KIZST 1981 Oct 1 - 6:00 - KIZT 1982 Apr 1 - 5:00 RussiaAsia KIZ%sT 1991 - 5:00 - KIZT 1991 Dec 16 # independence - 5:00 - QYZT 1992 Jan 19 2:00 - 6:00 RussiaAsia QYZ%sT 2005 Mar 15 - 6:00 - QYZT -# Aqtobe (aka Aktobe, formerly Aktyubinsk) + 4:00 - +04 1930 Jun 21 + 5:00 - +05 1981 Apr 1 + 5:00 1:00 +06 1981 Oct 1 + 6:00 - +06 1982 Apr 1 + 5:00 RussiaAsia +05/+06 1991 Mar 31 2:00s + 4:00 RussiaAsia +04/+05 1991 Sep 29 2:00s + 5:00 RussiaAsia +05/+06 1992 Jan 19 2:00s + 6:00 RussiaAsia +06/+07 1992 Mar 29 2:00s + 5:00 RussiaAsia +05/+06 2004 Oct 31 2:00s + 6:00 - +06 +# Aqtobe (aka Aktobe, formerly Aktyubinsk) (KZ-AKT) Zone Asia/Aqtobe 3:48:40 - LMT 1924 May 2 - 4:00 - AKTT 1930 Jun 21 # Aktyubinsk Time - 5:00 - AKTT 1981 Apr 1 - 5:00 1:00 AKTST 1981 Oct 1 - 6:00 - AKTT 1982 Apr 1 - 5:00 RussiaAsia AKT%sT 1991 - 5:00 - AKTT 1991 Dec 16 # independence - 5:00 RussiaAsia AQT%sT 2005 Mar 15 # Aqtobe Time - 5:00 - AQTT -# Mangghystau + 4:00 - +04 1930 Jun 21 + 5:00 - +05 1981 Apr 1 + 5:00 1:00 +06 1981 Oct 1 + 6:00 - +06 1982 Apr 1 + 5:00 RussiaAsia +05/+06 1991 Mar 31 2:00s + 4:00 RussiaAsia +04/+05 1992 Jan 19 2:00s + 5:00 RussiaAsia +05/+06 2004 Oct 31 2:00s + 5:00 - +05 +# Qostanay (KZ-KUS) + +# Mangghystau (KZ-MAN) # Aqtau was not founded until 1963, but it represents an inhabited region, # so include time stamps before 1963. Zone Asia/Aqtau 3:21:04 - LMT 1924 May 2 - 4:00 - FORT 1930 Jun 21 # Fort Shevchenko T - 5:00 - FORT 1963 - 5:00 - SHET 1981 Oct 1 # Shevchenko Time - 6:00 - SHET 1982 Apr 1 - 5:00 RussiaAsia SHE%sT 1991 - 5:00 - SHET 1991 Dec 16 # independence - 5:00 RussiaAsia AQT%sT 1995 Mar lastSun 2:00 # Aqtau Time - 4:00 RussiaAsia AQT%sT 2005 Mar 15 - 5:00 - AQTT -# West Kazakhstan + 4:00 - +04 1930 Jun 21 + 5:00 - +05 1963 + 5:00 - +05 1981 Oct 1 + 6:00 - +06 1982 Apr 1 + 5:00 RussiaAsia +05/+06 1991 Mar 31 2:00s + 4:00 RussiaAsia +04/+05 1992 Jan 19 2:00s + 5:00 RussiaAsia +05/+06 1994 Sep 25 2:00s + 4:00 RussiaAsia +04/+05 2004 Oct 31 2:00s + 5:00 - +05 + +# West Kazakhstan (KZ-ZAP) # From Paul Eggert (2016-03-18): # The 1989 transition is from USSR act No. 227 (1989-03-14). Zone Asia/Oral 3:25:24 - LMT 1924 May 2 # or Ural'sk - 4:00 - URAT 1930 Jun 21 # Ural'sk time - 5:00 - URAT 1981 Apr 1 - 5:00 1:00 URAST 1981 Oct 1 - 6:00 - URAT 1982 Apr 1 - 5:00 RussiaAsia URA%sT 1989 Mar 26 2:00 - 4:00 RussiaAsia URA%sT 1991 - 4:00 - URAT 1991 Dec 16 # independence - 4:00 RussiaAsia ORA%sT 2005 Mar 15 # Oral Time - 5:00 - ORAT + 4:00 - +04 1930 Jun 21 + 5:00 - +05 1981 Apr 1 + 5:00 1:00 +06 1981 Oct 1 + 6:00 - +06 1982 Apr 1 + 5:00 RussiaAsia +05/+06 1989 Mar 26 2:00s + 4:00 RussiaAsia +04/+05 1992 Jan 19 2:00s + 5:00 RussiaAsia +05/+06 1992 Mar 29 2:00s + 4:00 RussiaAsia +04/+05 2004 Oct 31 2:00s + 5:00 - +05 # Kyrgyzstan (Kirgizstan) # Transitions through 1991 are from Shanks & Pottenger. diff --git a/europe b/europe index af708ce..86159f7 100644 --- a/europe +++ b/europe @@ -600,13 +600,9 @@ Rule Russia 1981 1984 - Apr 1 0:00 1:00 S Rule Russia 1981 1983 - Oct 1 0:00 0 - # Act No. 967 of the Council of Ministers of the USSR (1984-09-13), repeated in # Act No. 227 of the Council of Ministers of the USSR (1989-03-14): -Rule Russia 1984 1991 - Sep lastSun 2:00s 0 - -Rule Russia 1985 1991 - Mar lastSun 2:00s 1:00 S +Rule Russia 1984 1995 - Sep lastSun 2:00s 0 - +Rule Russia 1985 2010 - Mar lastSun 2:00s 1:00 S # -Rule Russia 1992 only - Mar lastSat 23:00 1:00 S -Rule Russia 1992 only - Sep lastSat 23:00 0 - -Rule Russia 1993 2010 - Mar lastSun 2:00s 1:00 S -Rule Russia 1993 1995 - Sep lastSun 2:00s 0 - Rule Russia 1996 2010 - Oct lastSun 2:00s 0 - # As described below, Russia's 2014 change affects Zone data, not Rule data. @@ -630,6 +626,14 @@ Rule Russia 1996 2010 - Oct lastSun 2:00s 0 - # rules (Moscow time) # c) Uralsk oblast: third time belt rules (Moscow+1). +# From Stepan Golosunov (2016-03-27): +# Unamended version of the act of the +# Government of the Russian Federation No. 23 from 08.01.1992 +# http://pravo.gov.ru/proxy/ips/?docbody=&nd=102014034&rdk=0 +# says that every year clocks were to be moved forward on last Sunday +# of March at 2 hours and moved backwards on last Sunday of September +# at 3 hours. It was amended in 1996 to replace September with October. + # From Alexander Krivenyshev (2011-06-14): # According to Kremlin press service, Russian President Dmitry Medvedev # signed a federal law "On calculation of time" on June 9, 2011. -- 2.5.5

3 4

Magadan (Russia) may change it time zone on April 24, 2016
by Alexander Krivenyshev April 14, 2016

April 14, 2016

Just to reconfirm that 6 Russian regions: Astrakhan Oblast (Astrakhan), Ulyanovsk Oblast (Ulyanovsk), Altai Krai (Barnaul), Altai republic (Gorno- Altaysk), Zabaykalsky Krai (Chita), Sakhalin Oblast (Yuzhno-Sakhalinsk) changed their time zones on March 27, 2016. See new time zones map of Russia: http://www.worldtimezone.com/time-russia12.php or http://www.worldtimezone.com/time-russia24.php Seems that 7th region (Magadan Oblast / Magadan) which have submitted draft bill 948300-6 to change its time zone from UTC+10 to UTC+11 as of March 23, 2016 passed its 3rd reading by the State Duma and if approved by the Federation Council, will take into effect as the Federal Law on April 24, 2016 at at 2 o'clock 00 minutes. Here are ref. links: http://asozd2.duma.gov.ru/work/dz.nsf/ByID/CB78970353407D0243257F79005275DD/ $File/%D0%9F%D1%80%D0%BE%D0%B5%D0%BA%D1%82%20%D1%82%D0%B5%D0%BA%D1%81%D1%82% D0%B0%203%20%D1%87%D1%82%20%D0%9C%D0%B0%D0%B3%D0%B0%D0%B4%D0%B0%D0%BD.doc? OpenElement http://asozd2.duma.gov.ru/main.nsf/(SpravkaNew)?OpenAgent&RN=948300-6&02 Alexander Krivenyshev http://www.worldtimezone.com

4 8

Russian Legislation Status
by Matt Johnson April 13, 2016

April 13, 2016

I'm watching the Russian bills very closely. Current status: Transbaikal and Astrakhan have both been signed into law by the president and published. Sakhalin, Ulyanovsk, Altai Republic, and Altai Krai have all been approved by both legislative bodies, and are awaiting signature by the president. Magadan has no approvals yet. It is on the agenda for discussion for March 15th, per the meeting notices published at http://asozd2.duma.gov.ru It seems unlikely to me that it will pass with a March 27th effective date as currently written, but that's just my opinion. Another two bills were found for the Tomsk region. One has a date of March 8th, the other has a date of May 29th. I'm not quite sure of the difference between the two, but neither have approvals yet or are on the agenda. Links: Transbaikal http://asozd2.duma.gov.ru/main.nsf/(SpravkaNew)?OpenAgent&RN=840321-6 http://publication.pravo.gov.ru/Document/View/0001201512300107 Astrakhan http://asozd2.duma.gov.ru/main.nsf/(SpravkaNew)?OpenAgent&RN=862646-6 http://publication.pravo.gov.ru/Document/View/0001201602150056 Sakhalin http://asozd2.duma.gov.ru/main.nsf/(SpravkaNew)?OpenAgent&RN=888645-6 Ulyanovsk http://asozd2.duma.gov.ru/main.nsf/(SpravkaNew)?OpenAgent&RN=920582-6 Altai Republic http://asozd2.duma.gov.ru/main.nsf/(SpravkaNew)?OpenAgent&RN=935532-6 Altai Krai http://asozd2.duma.gov.ru/main.nsf/(SpravkaNew)?OpenAgent&RN=944348-6 Magadan http://asozd2.duma.gov.ru/main.nsf/(SpravkaNew)?OpenAgent&RN=948300-6 Tomsk http://asozd2.duma.gov.ru/main.nsf/(SpravkaNew)?OpenAgent&RN=1003422-6 http://asozd2.duma.gov.ru/main.nsf/(SpravkaNew)?OpenAgent&RN=1006865-6

5 15

Sri Lanka Standard Time
by Matt Johnson April 12, 2016

April 12, 2016

Sri Lanka and India are both on UTC+05:30, but it would appear that Sri Lankans may be using the term "Sri Lanka Standard Time", abbreviated SLST. The Asia/Colombo zone currently shows IST for the abbreviation. Some research I uncovered: https://en.wikipedia.org/wiki/Sri_Lanka_Standard_Time http://www.priu.gov.lk/news_update/Current_Affairs/ca201104/20110412standar… http://www.infolanka.com/news/IL/1474.htm It appears that on April 11th, 2011, the President of Sri Lanka declared SLST as the official time of Sri Lanka. The official site at http://sltime.org appears to be down at the moment, but archive.org shows it clearly using SLST when it was up.

2 3

Re: [tz] Regarding new Time Zone and DST for Chile 2016 - Possible corrections on tzdata2016c.tar.gz
by Carlos Huenchullan April 8, 2016

April 8, 2016

Hello all, Regarding the last Time Zone Data, two possible corrections could be applied for Chile rules (southamerica file) 1. Rules are pointed to Zone America/Santiago and Pacific/Easter. But it missing the links to Chile/Continental and Chile/EasterIsland. We tested in a Solaris 10 server with TZ=Chile/Continental and the new rules were not applied. So the following two lines should be applied at the end of Chile section: Link America/Santiago Chile/Continental Link Pacific/Easter Chile/EasterIsland 2. The following suggestion is about how it is defined the Time Zone for Chile and if it applies DST or not. This change is to keep an accurate time zone defined, CLT or CLST, this year. Before May 15th the Time Zone is CLT (UTC -3). If we applied the new rules now, the time zone will be CLST (UTC -3) until May 15th. The time will be fine, but the timezone is not ok. My suggestion is to add the following lines marked in green in the Zone section: # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Santiago -4:42:46 - LMT 1890 -4:42:46 - SMT 1910 Jan 10 # Santiago Mean Time -5:00 - CLT 1916 Jul 1 # Chile Time -4:42:46 - SMT 1918 Sep 10 -4:00 - CLT 1919 Jul 1 -4:42:46 - SMT 1927 Sep 1 -5:00 Chile CL%sT 1932 Sep 1 -4:00 - CLT 1942 Jun 1 -5:00 - CLT 1942 Aug 1 -4:00 - CLT 1946 Jul 15 -4:00 1:00 CLST 1946 Sep 1 # central Chile -4:00 - CLT 1947 Apr 1 -5:00 - CLT 1947 May 21 23:00 -4:00 Chile CL%sT 2015 Apr 26 3:00u -3:00 - CLT 2016 May 15 3:00u -4:00 Chile CL%sT Zone Pacific/Easter -7:17:28 - LMT 1890 -7:17:28 - EMT 1932 Sep # Easter Mean Time -7:00 Chile EAS%sT 1982 Mar 14 3:00u # Easter Time -6:00 Chile EAS%sT 2015 Apr 26 3:00u -5:00 - EAST 2016 May 15 3:00u -6:00 Chile EAS%sT Regards, Carlos Huenchullán

2 2

2016c on illumos - problems with new Russia entries
by Dan McDonald April 8, 2016

April 8, 2016

I was about to bump TZ on illumos (the open-source inheritor of what was OpenSolaris) but I encountered these when building: "europe", line 2551: warning: time zone abbreviation differs from POSIX standard (+03) "europe", line 2552: warning: time zone abbreviation differs from POSIX standard (+05) (rule from "europe", line 599) "europe", line 2552: warning: time zone abbreviation differs from POSIX standard (+04) (rule from "europe", line 600) "europe", line 2627: warning: time zone abbreviation differs from POSIX standard (+03) "europe", line 2628: warning: time zone abbreviation differs from POSIX standard (+05) (rule from "europe", line 599) "europe", line 2628: warning: time zone abbreviation differs from POSIX standard (+04) (rule from "europe", line 600) "europe", line 2630: warning: time zone abbreviation differs from POSIX standard (+02) (rule from "europe", line 603) "europe", line 2711: warning: time zone abbreviation differs from POSIX standard (+06) "europe", line 2712: warning: time zone abbreviation differs from POSIX standard (+08) (rule from "europe", line 599) "europe", line 2712: warning: time zone abbreviation differs from POSIX standard (+07) (rule from "europe", line 600) Now it is possible that the zic(1) utility for illumos needs some updating. OTOH, I've never had a problem until this specific update. The entries in question are (with markings): Zone Europe/Astrakhan 3:12:12 - LMT 1924 May **HERE*** 3:00 - +03 1930 Jun 21 **HERE*** 4:00 Russia +04/+05 1989 Mar 26 2:00s 3:00 Russia +03/+04 1991 Mar 31 2:00s 4:00 - +04 1992 Mar 29 2:00s 3:00 Russia +03/+04 2011 Mar 27 2:00s 4:00 - +04 2014 Oct 26 2:00s 3:00 - +03 2016 Mar 27 2:00s 4:00 - +04 Zone Europe/Ulyanovsk 3:13:36 - LMT 1919 Jul 1 2:00 **HERE*** 3:00 - +03 1930 Jun 21 **HERE*** 4:00 Russia +04/+05 1989 Mar 26 2:00s 3:00 Russia +03/+04 1991 Mar 31 2:00s **HERE*** 2:00 Russia +02/+03 1992 Jan 19 2:00s 3:00 Russia +03/+04 2011 Mar 27 2:00s 4:00 - +04 2014 Oct 26 2:00s 3:00 - +03 2016 Mar 27 2:00s 4:00 - +04 Zone Asia/Barnaul 5:35:00 - LMT 1919 Dec 10 **HERE*** 6:00 - +06 1930 Jun 21 **HERE*** 7:00 Russia +07/+08 1991 Mar 31 2:00s 6:00 Russia +06/+07 1992 Jan 19 2:00s 7:00 Russia +07/+08 1995 May 28 6:00 Russia +06/+07 2011 Mar 27 2:00s 7:00 - +07 2014 Oct 26 2:00s 6:00 - +06 2016 Mar 27 2:00s 7:00 - +07 I checked the mailing list archives quickly, but didn't see anything about Astrakhan, so I figured nobody else has seen this yet. I'm no expert in these... I just happen to update the illumos ones for the community every time my distro (OmniOS) gets ready to ship an update. Thanks, Dan McDonald -- OmniOS Engineering

8 12

Regarding new Time Zone and DST for Chile 2016 - Possible corrections on tzdata2016c.tar.gz
by Carlos Huenchullan April 7, 2016

April 7, 2016

Hello all, Regarding the last Time Zone Data, two possible corrections could be applied for Chile rules (southamerica file) 1. Rules are pointed to Zone America/Santiago and Pacific/Easter. But it missing the links to Chile/Continental and Chile/EasterIsland. We tested in a Solaris 10 server with TZ=Chile/Continental and the new rules were not applied. So the following two lines should be applied at the end of Chile section: Link America/Santiago Chile/Continental Link Pacific/Easter Chile/EasterIsland 2. The following suggestion is about how it is defined the Time Zone for Chile and if it applies DST or not. This change is to keep an accurate time zone defined, CLT or CLST, this year. Before May 15th the Time Zone is CLT (UTC -3). If we applied the new rules now, the time zone will be CLST (UTC -3) until May 15th. The time will be fine, but the timezone is not ok. My suggestion is to add the following lines marked in red in the Zone section: # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Santiago -4:42:46 - LMT 1890 -4:42:46 - SMT 1910 Jan 10 # Santiago Mean Time -5:00 - CLT 1916 Jul 1 # Chile Time -4:42:46 - SMT 1918 Sep 10 -4:00 - CLT 1919 Jul 1 -4:42:46 - SMT 1927 Sep 1 -5:00 Chile CL%sT 1932 Sep 1 -4:00 - CLT 1942 Jun 1 -5:00 - CLT 1942 Aug 1 -4:00 - CLT 1946 Jul 15 -4:00 1:00 CLST 1946 Sep 1 # central Chile -4:00 - CLT 1947 Apr 1 -5:00 - CLT 1947 May 21 23:00 -4:00 Chile CL%sT 2015 Apr 26 3:00u -3:00 Chile CLT 2016 May 15 3:00u -4:00 Chile CL%sT Zone Pacific/Easter -7:17:28 - LMT 1890 -7:17:28 - EMT 1932 Sep # Easter Mean Time -7:00 Chile EAS%sT 1982 Mar 14 3:00u # Easter Time -6:00 Chile EAS%sT 2015 Apr 26 3:00u -5:00 Chile EAST 2016 May 15 3:00u -6:00 Chile EAS%sT Regards, Carlos Huenchullán

1 0

New tzdata 'America/Santiago' 2016
by Bustos Alvarez, Cristian April 2, 2016

April 2, 2016

Hi, I want know if you have update the new timezone 2016 for Chile, because to 3 weeks ago the chilean goberment has decided change from GMT -03:00 to -04:00 in May 14. We need create a patche for Red Hat Enterprise Linux 4. In adittion, we want know if you create time zone database for Windows. Regards [Logo_40_anos] Cristian Bustos Álvarez Administrador de Sistemas Operativos Teatinos 550, piso 4 +562 2657 4724 +569 9746 3459 cristian.bustos(a)sonda.com<mailto:cristian.bustos@sonda.com> www.sonda.com<http://www.sonda.com/> P Estamos comprometidos con el medio ambiente, por favor no imprima este mail si no es necesario

5 5

[PROPOSED PATCH] * tz-link.htm, NEWS: Mention Internet RFCs 7809 and 7809.
by Paul Eggert April 2, 2016

April 2, 2016

Revert Easter Island adjustments --- NEWS | 4 ++++ tz-link.htm | 12 ++++++------ 2 files changed, 10 insertions(+), 6 deletions(-) diff --git a/NEWS b/NEWS index c08fc2d..4198dc5 100644 --- a/NEWS +++ b/NEWS @@ -8,6 +8,10 @@ Unreleased, experimental changes (Thanks to Alexander Krivenyshev.) This change has not yet been approved by the Federation Council but seems more likely than not. + Changes to commentary + + Mention Internet RFCs 7808 (TZDIST) and 7809 (CalDAV time zone references). + Release 2016c - 2016-03-23 00:51:27 -0700 diff --git a/tz-link.htm b/tz-link.htm index f0bbf70..feede12 100644 --- a/tz-link.htm +++ b/tz-link.htm @@ -222,12 +222,12 @@ names and shows location maps.</li> <ul> <li>The <a href="http://www.ietf.org">Internet Engineering Task Force</a>'s <a href="http://datatracker.ietf.org/wg/tzdist/charter/">Time Zone Data -Distribution Service (tzdist) working group</a> is developing a scalable -protocol for distributing time zone data to clients. It has generated a -a <a href="http://datatracker.ietf.org/doc/draft-ietf-tzdist-service/">draft -protocol for transferring time zone data</a> and a <a -href="http://datatracker.ietf.org/doc/draft-ietf-tzdist-caldav-timezone-ref/">draft -protocol for transferring time zone data by reference</a>. This work is based +Distribution Service (tzdist) working group</a> has defined <a +href="http://tools.ietf.org/html/rfc7808">TZDIST</a> +(Internet <abbr>RFC</abbr> 7808), a time zone data distribution service, +along with a <a href="http://tools.ietf.org/html/rfc7809">calendar access +protocol for transferring time zone data by reference</a> +(Internet <abbr>RFC</abbr> 7809). This work is based on the iCalendar and CalConnect efforts described below.</li> <li>The <a href="http://tools.ietf.org/html/rfc5545"> Internet Calendaring and Scheduling Core Object Specification -- 2.5.5

1 0