- tz - lists.iana.org

Re: [tz] Anecdotal discrepancy for Navajo nation in Arizona
by Steve Jones May 25, 2016

May 25, 2016

At 10:53 PM 5/24/2016, Brian Inglis wrote: >Federal facilities and areas within AZ are subject to federal >legislation so they too observe DST. Federal legislation deals with time zone borders, not DST observance. DST observance is a state (and Indian) matter. Only AZ and HI have decided not to observe. Federal facilities located in those states therefore do not observe DST. Everything from national parks to post offices to federal polling places. Indian nations are deemed to have similar authority - and that it supersedes that of the state in which they are located. So on reservation lands the Navajo decision to observe DST trumps the AZ decision not to. Federal facilities inside the Navajo reservation observe time per the Navajo authority instead of the AZ authority. There are also exceptions to federal facilities deviating from official local time. The only one I knew of before today was Guadalupe Mountains National Park, which observes Mountain time despite being mostly located in the Central time zone. Today I learned of the Dangling Rope Marina exception. Regards, Steve Jones Emacs!

2 1

Re: [tz] Anecdotal discrepancy for Navajo nation in Arizona
by Sterling Udell May 25, 2016

May 25, 2016

> Federal facilities and areas within AZ are subject to federal > legislation so they too observe DST. That's not correct. I'm currently at Pipe Spring National Monument (a federal facility in AZ), and despite being just a few miles from the Utah border, it follows the bulk of AZ in *not* observing DST. I can tell you the same is true for Grand Canyon National Park, Petrified Forest NP, Organ Pipe Cactus NP, and other NPS locations here. On the other hand, Hubbell Trading Post National Historic Site - which is surrounded by the Navajo reservation - follows the Navajo in observing DST. In general, NPS sites in Arizona observe the time of their surrounding areas. I would strongly expect that the same is true for other federal facilities in Phoenix, Tucson, or wherever - it would just be too disruptive for the time zone to be different in a single building.

1 0

Re: [tz] Anecdotal discrepancy for Navajo nation in Arizona
by Steve Jones May 25, 2016

May 25, 2016

At 05:55 PM 5/24/2016, Arthur David Olson wrote: > > ...it might be worth checking if anyone has any sources inside > the Navajo nation. > >The source used back in 1987 (using--ahem--snail mail) was the Inter >Tribal Council of Arizona: <http://itcaonline.com/>http://itcaonline.com/. A very complex area: From http://ontimezone.com/exceptions.php: Even though Arizona does not observe Daylight Saving Time, the Navajo Indian Reservation (which takes up most of northeastern AZ) does observe DST. To add to the confusion, the Hopi Indian Reservation, which is wholly enclosed within the Navajo Reservation, does NOT observe DST. Confused? We're just getting started. * Consider also that the Navajos have an enclave containing the village of Jeddito, entirely within the Hopi reservation. And that the Hopi reservation has an exclave at Moenkopi, just south of Tuba City. Still not confused? * Some of the businesses in Tuba city (within the Navajo Reservation) reportedly do not observe Daylight Saving time, so as to avoid confusing the tourists. Good luck with that. At least that puts them in sync with their Hopi neighbors across highway 160 in Moenkopi. Got it? http://ontimezone.com/images/az_tribal.php Emacs! Steve Jones Emacs!

2 1

Re: [tz] tz Digest, Vol 56, Issue 13
by Uri Ramirez May 23, 2016

May 23, 2016

Help On May 23, 2016 5:00 AM, <tz-request(a)iana.org> wrote: > Send tz mailing list submissions to > tz(a)iana.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://mm.icann.org/mailman/listinfo/tz > or, via email, send a message with subject or body 'help' to > tz-request(a)iana.org > > You can reach the person managing the list at > tz-owner(a)iana.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of tz digest..." > > > Today's Topics: > > 1. Re: Morocco confirms Ramadan DST dates (Milamber) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sun, 22 May 2016 17:18:17 +0200 > From: Milamber <milamberspace(a)gmail.com> > To: Matt Johnson <mj1856(a)hotmail.com>, Time Zone Mailing List > <tz(a)iana.org> > Subject: Re: [tz] Morocco confirms Ramadan DST dates > Message-ID: <5741CDB9.9040900(a)gmail.com> > Content-Type: text/plain; charset=UTF-8; format=flowed > > > Yes you are probably right, the arabic version seems have the good hour > (2:00 am) to the change. > Thanks. > > On 22/05/2016 04:54, Matt Johnson wrote: > > Thanks, but this appears to be a translation error. The Arabic version > on the same site says 2:00 instead of 3:00. See > http://mmsp.gov.ma/ar/actualites.aspx?id=1057 > > > > Given the history from previous years, I'm inclined to believe the > Arabic version. > > > > -Matt > > ________________________________________ > > From: Milamber <milamberspace(a)gmail.com> > > Sent: Saturday, May 21, 2016 3:24 PM > > To: Matt Johnson > > Subject: Re: [tz] Morocco confirms Ramadan DST dates > > > > Hello, > > > > The official link from the Ministry of Public service and Administration > > Modernization (in French): > > > > http://mmsp.gov.ma/fr/actualites.aspx?id=1056 > > > > Google Translation: > > "Back to the standard time of the Kingdom (GMT). > > The Ministry of Public Service and Modernization of Administration > > announces the return to standard time of the Kingdom (GMT). So time will > > be delayed for 60 minutes from 3:00 am Sunday, June 5, 2016. She will be > > advanced by 60 minutes (GMT + 1) from 3:00 am Sunday, July 10, 2016." > > > > > > One question: > > > > "She will be advanced by 60 minutes (GMT + 1) from 3:00 am Sunday, July > > 10, 2016." > > > > meaning this on zdump (current tzdata)? > > > > Africa/Casablanca Sun Jul 10 01:59:59 2016 UT = Sun Jul 10 01:59:59 > > 2016 WET isdst=0 gmtoff=0 > > Africa/Casablanca Sun Jul 10 02:00:00 2016 UT = Sun Jul 10 03:00:00 > > 2016 WEST isdst=1 gmtoff=3600 > > > > At 02am go to 03am or at 03am go to 04am? > > > > Milamber > > > > > > On 19/05/2016 06:30, Matt Johnson wrote: > >> > http://www.moroccoworldnews.com/2016/05/186863/morocco-goes-back-to-gmt-tim… > >> > >> Our guesses appear to be validated. > >> > > > > > > ------------------------------ > > _______________________________________________ > tz mailing list > tz(a)iana.org > https://mm.icann.org/mailman/listinfo/tz > > > End of tz Digest, Vol 56, Issue 13 > ********************************** >

1 0

Re: [tz] Morocco confirms Ramadan DST dates
by Milamber May 22, 2016

May 22, 2016

Yes you are probably right, the arabic version seems have the good hour (2:00 am) to the change. Thanks. On 22/05/2016 04:54, Matt Johnson wrote: > Thanks, but this appears to be a translation error. The Arabic version on the same site says 2:00 instead of 3:00. See http://mmsp.gov.ma/ar/actualites.aspx?id=1057 > > Given the history from previous years, I'm inclined to believe the Arabic version. > > -Matt > ________________________________________ > From: Milamber <milamberspace(a)gmail.com> > Sent: Saturday, May 21, 2016 3:24 PM > To: Matt Johnson > Subject: Re: [tz] Morocco confirms Ramadan DST dates > > Hello, > > The official link from the Ministry of Public service and Administration > Modernization (in French): > > http://mmsp.gov.ma/fr/actualites.aspx?id=1056 > > Google Translation: > "Back to the standard time of the Kingdom (GMT). > The Ministry of Public Service and Modernization of Administration > announces the return to standard time of the Kingdom (GMT). So time will > be delayed for 60 minutes from 3:00 am Sunday, June 5, 2016. She will be > advanced by 60 minutes (GMT + 1) from 3:00 am Sunday, July 10, 2016." > > > One question: > > "She will be advanced by 60 minutes (GMT + 1) from 3:00 am Sunday, July > 10, 2016." > > meaning this on zdump (current tzdata)? > > Africa/Casablanca Sun Jul 10 01:59:59 2016 UT = Sun Jul 10 01:59:59 > 2016 WET isdst=0 gmtoff=0 > Africa/Casablanca Sun Jul 10 02:00:00 2016 UT = Sun Jul 10 03:00:00 > 2016 WEST isdst=1 gmtoff=3600 > > At 02am go to 03am or at 03am go to 04am? > > Milamber > > > On 19/05/2016 06:30, Matt Johnson wrote: >> http://www.moroccoworldnews.com/2016/05/186863/morocco-goes-back-to-gmt-tim… >> >> Our guesses appear to be validated. >> >

1 0

Morocco confirms Ramadan DST dates
by Matt Johnson May 19, 2016

May 19, 2016

http://www.moroccoworldnews.com/2016/05/186863/morocco-goes-back-to-gmt-tim… Our guesses appear to be validated.

1 0

Getting offset for each time zones
by kailash kumar May 19, 2016

May 19, 2016

Hi All, I wanted to get UTC offset for each time zone which is present under zoneinfo folder. basically I wanted to create a drop down for all timezones with UTC offset, where user can select timezone. Please let me know if it is possible to get UTC offset for all time zones in tz database. Thanks, KAILASH KUMAR JAIN Legal Warning: This message may contain privileged and confidential information. If you are not the intended recipient or for any reason think that this message may have been address to you or reached you as a mistake, its requested that you must not disseminate,copy or take any action in reliance on it and I ask you to delete all copies from your mail box and computer system and also notify me immediately by return e-mail.

4 4

South Australia not changing time zones, again
by Gilmore Davidson May 18, 2016

May 18, 2016

Last year saw a proposal by the South Australian government to move clocks forward 30 minutes to align with Australia's eastern states, which was discussed on this mailing list. Ultimately that proposal was rejected by the opposition after a lack of support among the general public. Now a minor party's upper house representative, Robert Brokenshire, has introduced a bill to move the clocks 30 minutes in the other direction, towards a "true" central time. This bill was resoundingly defeated by both the government and major opposition party, so the clocks will remain at UTC+09:30 for a while yet. I get the feeling this won't be the end of the discussion though. http://www.abc.net.au/news/2016-05-19/attempt-to-shift-south-australian-tim… Mr Brokenshire said he remained passionate about the idea. "I learnt a bit about arithmetic and I'm not going to actually beat the two major parties but we will be back," he said. "At an appropriate time I will bring this debate back to Parliament."

1 0

Time Zone Database Update
by sherif.atef＠hsbc.com May 18, 2016

May 18, 2016

3 4

some info for you
by support＠anuko.com May 17, 2016

May 17, 2016

Hello, Isn't it the information you were looking for? Read about it here <http://fospathopy.kissmecait.com/yield.php?7u> Sincerely yours, support(a)anuko.com

1 0

DST changes for year 2016 not getting reflected for Asia Region
by AJAY SETHUMADHAVAN May 13, 2016

May 13, 2016

Hello Below is the time zone version used in my Linux machine. ======================================================== Name : tzdata Relocations: (not relocatable) Version : 2016d Vendor: CentOS Release : 1.el5 Build Date: Fri 22 Apr 2016 10:07:55 AM PDT Install Date: Thu 12 May 2016 09:14:18 AM PDT Build Host: builder17.centos.org Group : System Environment/Base Source RPM: tzdata-2016d-1.el5.src.rpm Size : 1803555 License: Public Domain Signature : DSA/SHA1, Fri 22 Apr 2016 10:36:20 AM PDT, Key ID a8a447dce8562897 URL : https://www.iana.org/time-zones Summary : Timezone data Description : This package contains data files with rules for various time zones around the world ======================================================== Asia/Tijuana has DST started on 13 Mar 2016 and will End on 6 Nov 2016. On 13 Mar 2016 if i keep time as 02:00:00 it should ideally jump to 03:00:00 Similarly On 6 Nov 2016 if i keep time as 02:00:00 it should jump to 01:00:00 The same is not happening on my machine. ========================================================= . Please Help me out for resolving this Thanks and Regards Ajay

2 1

Chile time changed early?
by Matt Johnson May 13, 2016

May 13, 2016

http://www.wsj.com/articles/what-time-is-it-in-chile-theres-no-telling-1463… Since the change isn't scheduled until Sunday, the only way I can think that this happened is that the cell towers were updated prematurely. Can anyone confirm or comment? -Matt

3 4

America/ Santiago possible Correction
by Gretchen Gottsacker May 12, 2016

May 12, 2016

Greetings, I noticed there may be a discrepancy for the time zone America/ Santiago. As mentioned in the document NEWS "Also, call the period from 2014-09-07 through 2016-05-14 daylight saving time instead of standard time, as that seems more appropriate now." I believe is an incorrect statement as the link provided on the southamerica document provides these two links http://www.diariooficial.interior.gob.cl/versiones-anteriores/do/20160318/ and http://www.leychile.cl/Navegar?idNorma=1088502 which states that "as amended by Presidential Decree Nº106, 2015, both the Ministry of the Interior and Public Security, will be extended, as regards the year 2016, until 24 pm the second Saturday of May. Also, starting from the 24 hours of the second Saturday in August 2016 and until 24 pm the second Saturday in May 2017, the official time will advance in 60 minutes" Meaning daylight savings is not active until August 2016. Thank you, http://www.oracle.com/ Gretchen Gottsacker | BDE Support - BDE Engineer - Special Forces Oracle +1.800.806.6592 Oracle Service Cloud Support - USA - 45.6778° N, 111.0472° W http://www.oracle.com/commitment Oracle is committed to developing practices and products that help protect the environment.

3 2

TZ Changing in Chile on May, 14th.
by Luis Martinez Villa May 3, 2016

May 3, 2016

Dear IANA TZ, Since the last time change Chile has been in GMT-3 (i.e. Chile is right now in GMT-3). Chile is going to GMT-4 in May,14th midnight and returning to GMT-3 in August, 13th midnight. That means clocks will go back 1 hour at 00:00 May 15th (jumping back to May 14th); and will go forward by 1 hour on 00:00, August 14th. In tzdata2016c I can see this new rules for Chile: # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S Rule Chile 2016 max - May Sun>=9 3:00u 0 - Rule Chile 2016 max - Aug Sun>=9 4:00u 1:00 S And I can see this Chile zone definition: # 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 But with these two information I'm not sure that in the midnight of May, 14th this tzdata2016c will change the TZ of Chile from GMT-3 to GMT-4. Can you please explain me how these structures in tzdata2016c work to accomplish the necessary TZ change in Chile. Thank you very much, best regards. Luis

3 2

[PROPOSED PATCH 1/2] Mostly work around Qt bug 53071 by inserting dummy
by Paul Eggert May 1, 2016

May 1, 2016

Problem reported by Zhanibek Adilbekov in: http://mm.icann.org/pipermail/tz/2016-April/023605.html Also see the Qt bug report in: https://bugreports.qt.io/browse/QTBUG-53071 * NEWS: Document this. * zic.c (WORK_AROUND_QTBUG_53071): New constant. (growalloc): Don't grow past INT_MAX - 1 if the bug is present, since we add 1 at the end. (writezone) [WORK_AROUND_QTBUG_53071]: Work around most of QTBUG-53071, by inserting a dummy transition at time 2**31 - 1. --- NEWS | 7 +++++++ zic.c | 30 +++++++++++++++++++++++++++--- 2 files changed, 34 insertions(+), 3 deletions(-) diff --git a/NEWS b/NEWS index e16f489..b5fb182 100644 --- a/NEWS +++ b/NEWS @@ -14,6 +14,13 @@ Unreleased, experimental changes Asia/Baku's 1992-09-27 transition from +04 (DST) to +04 (non-DST) was at 03:00, not 23:00 the previous day. (Thanks to Michael Deckers.) + Changes to code + + zic now outputs a dummy transition at time 2**31 - 1 in zones + whose POSIX-style TZ strings contain a '<'. This mostly works + around Qt bug 53071 <https://bugreports.qt.io/browse/QTBUG-53071>. + (Thanks to Zhanibek Adilbekov for reporting the Qt bug.) + Changes affecting documentation and commentary tz-link.htm says why governments should give plenty of notice for diff --git a/zic.c b/zic.c index 0ec3359..3b32f9b 100644 --- a/zic.c +++ b/zic.c @@ -143,6 +143,13 @@ static bool yearistype(int year, const char * type); /* Bound on length of what %z can expand to. */ enum { PERCENT_Z_LEN_BOUND = sizeof "+995959" - 1 }; +/* If true, work around a bug in Qt 5.6 and earlier, which mishandles + tzdata binary files whose POSIX-TZ-style strings contain '<'; see + QTBUG-53071 <https://bugreports.qt.io/browse/QTBUG-53071>. This + workaround will no longer be needed when Qt 5.6 is obsolete, say in + the year 2021. */ +enum { WORK_AROUND_QTBUG_53071 = true }; + static int charcnt; static bool errors; static bool warnings; @@ -420,7 +427,8 @@ growalloc(void *ptr, size_t itemsize, int nitems, int *nitems_alloc) if (nitems < *nitems_alloc) return ptr; else { - int amax = INT_MAX < SIZE_MAX ? INT_MAX : SIZE_MAX; + int nitems_max = INT_MAX - WORK_AROUND_QTBUG_53071; + int amax = nitems_max < SIZE_MAX ? nitems_max : SIZE_MAX; if ((amax - 1) / 3 * 2 < *nitems_alloc) memory_exhausted(_("int overflow")); *nitems_alloc = *nitems_alloc + (*nitems_alloc >> 1) + 1; @@ -1616,8 +1624,11 @@ writezone(const char *const name, const char *const string, char version) char * fullname; static const struct tzhead tzh0; static struct tzhead tzh; - zic_t *ats = emalloc(size_product(timecnt, sizeof *ats + 1)); - void *typesptr = ats + timecnt; + zic_t one = 1; + zic_t y2038_boundary = one << 31; + int nats = timecnt + WORK_AROUND_QTBUG_53071; + zic_t *ats = emalloc(size_product(nats, sizeof *ats + 1)); + void *typesptr = ats + nats; unsigned char *types = typesptr; /* @@ -1661,6 +1672,19 @@ writezone(const char *const name, const char *const string, char version) ats[i] = attypes[i].at; types[i] = attypes[i].type; } + + /* Work around QTBUG-53071 for time stamps less than y2038_boundary - 1, + by inserting a no-op transition at time y2038_boundary - 1. + This works only for timestamps before the boundary, which + should be good enough in practice as QTBUG-53071 should be + long-dead by 2038. */ + if (WORK_AROUND_QTBUG_53071 && timecnt != 0 + && ats[timecnt - 1] < y2038_boundary - 1 && strchr(string, '<')) { + ats[timecnt] = y2038_boundary - 1; + types[timecnt] = types[timecnt - 1]; + timecnt++; + } + /* ** Correct for leap seconds. */ -- 2.7.4

1 1

[PROPOSED PATCH] Fix minor glitches in Morocco rule formatting
by Paul Eggert May 1, 2016

May 1, 2016

These changes do not affect the data per se, only how it is formatted in the source. (Thanks to Corey Danielson.) * africa (Morocco): Use "0:00" for time, not "0". Sort 2012 transitions by date. --- africa | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/africa b/africa index 442b326..547e215 100644 --- a/africa +++ b/africa @@ -944,11 +944,11 @@ Rule Morocco 2009 only - Aug 21 0:00 0 - Rule Morocco 2010 only - May 2 0:00 1:00 S Rule Morocco 2010 only - Aug 8 0:00 0 - Rule Morocco 2011 only - Apr 3 0:00 1:00 S -Rule Morocco 2011 only - Jul 31 0 0 - +Rule Morocco 2011 only - Jul 31 0:00 0 - Rule Morocco 2012 2013 - Apr lastSun 2:00 1:00 S -Rule Morocco 2012 only - Sep 30 3:00 0 - Rule Morocco 2012 only - Jul 20 3:00 0 - Rule Morocco 2012 only - Aug 20 2:00 1:00 S +Rule Morocco 2012 only - Sep 30 3:00 0 - Rule Morocco 2013 only - Jul 7 3:00 0 - Rule Morocco 2013 only - Aug 10 2:00 1:00 S Rule Morocco 2013 max - Oct lastSun 3:00 0 - -- 2.7.4

1 0

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