June 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

The West Wing: 20 Hours in America
by Matt Johnson Aug. 21, 2016

Aug. 21, 2016

This is already mentioned in the arts file, but I just found a clip of it: https://www.youtube.com/watch?v=-J1NHzQ1sgc Cheers! -Matt

2 1

Julia tz compiler
by Curtis Vogt Aug. 21, 2016

Aug. 21, 2016

Hello, I'm one of the main contributors to TimeZones.jl <http://github.com/JuliaTime/TimeZones.jl>: a tz compiler written in the programming language Julia <http://julialang.org/>. I would appreciate if TimeZones.jl could be added to the "Other tz compilers" section on the https://www.iana.org/time-zones/repository/tz-link.html page. The blurb could be written as: [TimeZones.jl – Time zone database access for Julia]( > https://github.com/JuliaTime/TimeZones.jl) compiles tz source into > [Julia](http://julialang.org/). It is freely available under the MIT lic > ense. Thanks for your time, Curtis Vogt

2 1

Morocco DST change happened on 4/June/2016 instead of 5/June/2016
by Gopal . Aug. 4, 2016

Aug. 4, 2016

Hi Team, TZupdater updated time zone 1 day before scheduled time, it was supposed to change time on 5 June 2016 for Morocco Casablanca and but application time changed on 4 June 2016. Could you please let us know as we are facing some problems in application due to this. Regards Gopal This e-mail and all material transmitted with it are for the use of the intended recipient(s) ONLY and contains confidential and/or privileged information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies and the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email or any action taken pursuant to the contents of the present e-mail is strictly prohibited and is unlawful. The recipient acknowledges that Comviva Technologies Limited or its management or directors, are unable to exercise control or ensure the integrity over /of the contents of the information contained in e-mail. Any views expressed herein are those of the individual sender only and no binding nature of the contents shall be implied or assumed unless the sender does so expressly with due authority of Comviva Technologies Limited. E-mail and any contents transmitted with it are prone to viruses and related defects despite all efforts to avoid such by Comviva Technologies Limited.

4 6

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

July 25, 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

Saratov and Novosibirsk proposed to change their time zones
by Stepan Golosunov July 4, 2016

July 4, 2016

Hi, Search for "об исчислении времени" on http://asozd2.duma.gov.ru/main.nsf/SearchUD?OpenForm revealed 3 new bills changing time zone borders in Russia: http://asozd2.duma.gov.ru/main.nsf/(Spravka)?OpenAgent&RN=1058438-6 and http://asozd2.duma.gov.ru/main.nsf/(Spravka)?OpenAgent&RN=1083558-6 move Saratov oblast from UTC+3 to UTC+4. http://asozd2.duma.gov.ru/main.nsf/(Spravka)?OpenAgent&RN=1085784-6 moves Novosibirsk oblast from UTC+6 to UTC+7. Given that the last two bills are proposed by regional parliaments, they are likely to be approved. When is less clear. The bills currently have effective dates in July, but that can be easily changed before the second readings. And they are just received while there are only 4 weeks before the summer break in the State Duma.

2 4

Europe/Minsk: September 1992 transition is incorrect?
by Ed Schouten July 2, 2016

July 2, 2016

Hi there, When taking a look at 'zdump -v Europe/Minsk' with tzcode2016e/tzdata2016e running on a FreeBSD 10 system, I observe the following: Europe/Minsk Sat Sep 26 23:59:59 1992 UTC = Sun Sep 27 02:59:59 1992 EEST isdst=1 gmtoff=10800 Europe/Minsk Sun Sep 27 00:00:00 1992 UTC = Sun Sep 27 02:00:00 1992 EET isdst=0 gmtoff=7200 Now taking a look at the Zone definition of Minsk: 2:00 1:00 EEST 1992 Sep 27 0:00s 2:00 Russia EE%sT 2011 Mar 27 2:00s My question is, shouldn't this transition have taken place two hours earlier? Can anyone else reproduce this? -- Ed Schouten <ed(a)nuxi.nl> Nuxi, 's-Hertogenbosch, the Netherlands KvK-nr.: 62051717

4 3

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

No DST in Egypt anymore
by Amgad Meckawy June 29, 2016

June 29, 2016

Egyptian parliament have just agreed to Cancel the DST so clock won't change 1 hour ahead on next 7th of July. time-fixed would still the same allover the year this decision have been announced just on 28-june-2016 sources --------- http://s.youm7.com/2780068 https://rassd.com/189329.htm http://www.parlmany.com/News/7/98619/%D8%A5%D9%84%D8%BA%D8%A7%D8%A1- %D8%A7%D9%84%D8%AA%D9%88%D9%82%D9%8A%D8%AA- %D8%A7%D9%84%D8%B5%D9%8A%D9%81%D9%89-%D8%A8%D8%A3%D9%85%D8%B1- %D8%A7%D9%84%D8%A8%D8%B1%D9%84%D9%85%D8%A7%D9%86 http://www.masrawy.com/News/News_Egypt/details/2016/6/28/876429/%D8%B1%D8% B3%D9%85%D9%8A%D8%A7-%D9%85%D8%AC%D9%84%D8%B3- %D8%A7%D9%84%D9%86%D9%88%D8%A7%D8%A8-%D9%8A%D9%88%D8%A7%D9%81%D9%82- %D8%B9%D9%84%D9%89-%D8%A5%D9%84%D8%BA%D8%A7%D8%A1- %D8%A7%D9%84%D8%AA%D9%88%D9%82%D9%8A%D8%AA- %D8%A7%D9%84%D8%B5%D9%8A%D9%81%D9%8A#NEWS-MOSTREAD-details

1 0

America/Indiana/Vincennes
by Matt Johnson June 23, 2016

June 23, 2016

In zone.tab, the America/Indiana/Vincennes comments were changed to "Eastern - IN (Da, Du, K, Mn)". IMHO, those abbreviations aren't distinct enough to identify specific counties in Indiana. We used to say "Daviess, Dubois, Knox & Martin". Da and Du I might be able to figure out, but K could just as well be Kosciusko County, and Mn could be Madison or Marion. Can we just return them to their names please?

3 4

Asia/Kashgar offset
by stefan.kruzlik.ext＠geodis.com June 23, 2016

June 23, 2016

Hello, Could you please confirm the current usage of offset of +6hours for Asia/Kashgar in your TZ database is correct? Checking any available source on the internet Google (search for 'Kashgar time') Bing (search for 'Kashgar time') http://www.timeanddate.com/worldclock/china/kashgar https://www.localtimenow.com/china/kashgar/ All show offset of +8hours. Thanks, Stefan Kruzlik SCO IT Geobus Solution Architect Geodis IT Supply Chain Optimisation GEODIS 7-9, allées de l'Europe 92615 - CLICHY / FRANCE Tel. : + 33 (0)1 71 15 65 62 stefan.kruzlik.ext(a)geodis.com | geodis.com

2 1

Asia/Novosibirsk switch from +06 to +07 on 2016-07-24.
by Александр June 21, 2016

June 21, 2016

> The bill for Novosibirsk is here: > http://asozd2.duma.gov.ru/main.nsf/(Spravka)?OpenAgent&RN=1085784-6 > > It has passed the first reading in the State Duma. It needs to pass a second reading, then pass the Federation Council, then be signed into law by the President. Even if this all passes, it's possible the effective date will change along the way. > http://asozd2.duma.gov.ru/main.nsf/(SpravkaNew)?OpenAgent&RN=1085784-6&02 This bill was approved in the second reading today. It moves Novosibirsk oblast from UTC+6 to UTC+7 and is supposed to come into effect on 2016-07-24 at 2:00. The bill needs to be approved in the third readings by the State Duma, approved by the Federation Council, signed by the President and published to become a law. Minor changes in the text are to be expected before the second reading (references need to be updated to account for the recent changes). --- Best regards, Alexander Golikov.

1 0

Asia/Novosibirsk switch from +06 to +07 on 2016-07-03.
by Andrey Kitsul June 16, 2016

June 16, 2016

Hello, Asia/Novosibirsk switch from +06 to +07 on 2016-07-03. https://rg.ru/2016/06/14/reg-sibfo/deputaty-pereveli-chasy-v-novosibirskoj-… -- Kind regards, Andrey Kitsul.

2 1

zdump broken with latest Cairo changes?
by Dave Rolsky June 16, 2016

June 16, 2016

Here's a snippet of "zdump -v Africa/Cairo" with the latest changes: Africa/Cairo Thu Apr 29 21:59:59 2038 UT = Thu Apr 29 23:59:59 2038 EET isdst=0 gmtoff=7200 Africa/Cairo Thu Apr 29 22:00:00 2038 UT = Fri Apr 30 01:00:00 2038 EEST isdst=1 gmtoff=10800 Africa/Cairo Thu Sep 23 20:59:59 2038 UT = Thu Sep 23 23:59:59 2038 EEST isdst=1 gmtoff=10800 Africa/Cairo Thu Sep 23 21:00:00 2038 UT = Thu Sep 23 23:00:00 2038 EET isdst=0 gmtoff=7200 Africa/Cairo Thu Apr 28 21:59:59 2039 UT = Thu Apr 28 23:59:59 2039 EET isdst=0 gmtoff=7200 Africa/Cairo Thu Apr 28 22:00:00 2039 UT = Fri Apr 29 01:00:00 2039 EEST isdst=1 gmtoff=10800 Africa/Cairo Thu Sep 15 20:59:59 2039 UT = Thu Sep 15 23:59:59 2039 EEST isdst=1 gmtoff=10800 Africa/Cairo Thu Sep 15 21:00:00 2039 UT = Thu Sep 15 23:00:00 2039 EET isdst=0 gmtoff=7200 Africa/Cairo Thu Oct 20 21:59:59 2039 UT = Thu Oct 20 23:59:59 2039 EET isdst=0 gmtoff=7200 Africa/Cairo Thu Oct 20 22:00:00 2039 UT = Fri Oct 21 01:00:00 2039 EEST isdst=1 gmtoff=10800 Africa/Cairo Thu Oct 27 20:59:59 2039 UT = Thu Oct 27 23:59:59 2039 EEST isdst=1 gmtoff=10800 Africa/Cairo Thu Oct 27 21:00:00 2039 UT = Thu Oct 27 23:00:00 2039 EET isdst=0 gmtoff=7200 Africa/Cairo Thu Apr 26 21:59:59 2040 UT = Thu Apr 26 23:59:59 2040 EET isdst=0 gmtoff=7200 Africa/Cairo Thu Apr 26 22:00:00 2040 UT = Fri Apr 27 01:00:00 2040 EEST isdst=1 gmtoff=10800 Africa/Cairo Thu Sep 6 20:59:59 2040 UT = Thu Sep 6 23:59:59 2040 EEST isdst=1 gmtoff=10800 Africa/Cairo Thu Sep 6 21:00:00 2040 UT = Thu Sep 6 23:00:00 2040 EET isdst=0 gmtoff=7200 Africa/Cairo Thu Oct 11 21:59:59 2040 UT = Thu Oct 11 23:59:59 2040 EET isdst=0 gmtoff=7200 Africa/Cairo Thu Oct 11 22:00:00 2040 UT = Fri Oct 12 01:00:00 2040 EEST isdst=1 gmtoff=10800 Africa/Cairo Thu Oct 25 20:59:59 2040 UT = Thu Oct 25 23:59:59 2040 EEST isdst=1 gmtoff=10800 Africa/Cairo Thu Oct 25 21:00:00 2040 UT = Thu Oct 25 23:00:00 2040 EET isdst=0 gmtoff=7200 Note that things seem to be fine up to 2038, but then after that it reports 6+ transitions a year for the region. This looks like a bug to me, and my Perl tools that parse the files still come up with just 2 transitions per year. Cheers, -dave /*============================================================ http://VegGuide.org http://blog.urth.org Your guide to all that's veg House Absolute(ly Pointless) ============================================================*/

3 4

Cairo/Egypt
by Frank Bean June 16, 2016

June 16, 2016

I just saw this update and need to add some detail I think. Africa/Cairo observes DST in 2016 from July 7 to the end of October. Guess October 27 and 24:00 transitions. (Thanks to Steffen Thorsen.) For future years, guess April's last Thursday to October's last Thursday except for Ramadan. Now, this may change next year but the current story from Egypt's government is that they will not be implementing DST until the end of Ramadan going forward.

3 3

the final second before standard time daylight savings time transitions
by Inman, Mark H CIV USARMY HQDA (US) June 15, 2016

June 15, 2016

Hello, Is there any official documentation on the time zone for March 13 2016 in New York City, when the clock says 1:59:59.99991000 ? My guess would be that it is EST or -04:00 offset, but I cannot find anything that discussed the fractions of the last second. We store fractions of seconds, and we need to be able to convert to a particular offset. Thanks for your work and your consideration. P.S. I have enjoyed the notes in the time zone rules. Most Respectfully, Mark Inman Army Analytics Group Email: mark.h.inman2.civ(a)mail.mil Personal Work Phone: 707-863-7150 Personal Cell Phone: 925-324-9864 Personal Cell Text: 9253249864(a)vtext.com

3 2

[tz-announce] 2016e release of tz code and data available
by Paul Eggert June 14, 2016

June 14, 2016

The 2016e 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 Africa/Cairo observes DST in 2016 from July 7 to the end of October. Guess October 27 and 24:00 transitions. (Thanks to Steffen Thorsen.) For future years, guess April's last Thursday to October's last Thursday except for Ramadan. Changes affecting past time stamps Locations while uninhabited now use '-00', not 'zzz', as a placeholder time zone abbreviation. This is inspired by Internet RFC 3339 and is more consistent with numeric time zone abbreviations already used elsewhere. The change affects several arctic and antarctic locations, e.g., America/Cambridge_Bay before 1920 and Antarctica/Troll before 2005. 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 time zone or DST changes, and refers to Matt Johnson's blog post. tz-link.htm mentions Tzdata for Elixir. (Thanks to Matt Johnson.) Here are links to the release files: ftp://ftp.iana.org/tz/releases/tzcode2016e.tar.gz ftp://ftp.iana.org/tz/releases/tzdata2016e.tar.gz The files are also available via HTTP as follows: http://www.iana.org/time-zones/repository/releases/tzcode2016e.tar.gz http://www.iana.org/time-zones/repository/releases/tzdata2016e.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 ddb14859b156e72bb2daff70ff2fe59d6d82d545 dated 2016-06-14 08:46:16 -0700 and tagged '2016e' in the experimental github repository at <https://github.com/eggert/tz>. Here are the SHA-512 checksums for the release files: dcaf615ada96920e60ffb336253f53541861153decc156d41661f43e0bfb128c6c231b0b776bbe3f2176549346275fc5a879074f4977d5141228e58cb33a41c6 tzcode2016e.tar.gz dace0f6fc87a73879ca3a1b143d7dcf9c50803e23e6b8c91f83711704e28129af776676c547c42f14dee7f1e8e285ce25296e53a52d11f4c8f155b5f80f4beb3 tzdata2016e.tar.gz Here are the GPG checksums for the release files: -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAABAgAGBQJXYCdTAAoJEO2X6Q5iqn40EK8P/iKELbSZ0ZbgcqAkWRuh8OeG v/T8qkbK3pHeHi9+eELqR24ZODPe/KIORFZxXaxsn+JBUo8QdAlgyZc/5/MkISV1 AvJlk3SAe5TgyKRIQfmVeLpjPHx8w1fcHU3yc7ssMqcv8vhPXXZHGWhmoDoiJOwW ocnToizAWdjNQlqK29Ra33qCEYZuTjLg/a+gvJGqMV9d3zEtA4qOZNSyl9h8pKZo lUYIk+Vj56QSqw3iwZ83MrwhXw7/R8NpfjqAgXw3Au04CRYscvVLlKutdp3+B515 bjnX0ghtgvzolVQLRIPXLjDKXx5FduvW83yTfqFk8gPRgcCplE4mC1zZKfv8CXs9 tR4F+in7iLr23+7o4wjD3yolI9hgY0D8/XTuXs7XWzAaHjCcKAwT460AVmY3MkaL 130TQonnLuWPdfg6EWJHRxHr4du3s6Sg8aMO6tZiSf9eL2oOGPq7A0Yl3XkR01pb 9UEuVEsA0w1MxDl6jAIBZq9vZkbj5vehPD5yzmrXQbgMEeongY5eun0UYIJH8M/X P05+DnpnG9u88/U+yzZmOWLYL97JA2SQal/nfL8lIFkRnmVQnSlHzvi2MGkuYPcz jnhNQOkOGxTiZ5TTNqDPOe1wJ7nVfNJoaIoklnQXLES0necZDQJJ354+EjzzC+jK GuWBNHojTrArRXSkITEK =1NuU -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAABAgAGBQJXYCdYAAoJEO2X6Q5iqn40yasP/18erUr4JDpff6WZWh/YN5uo 6D6aoDIvjgeC1L+OeUX4jEO2Iinc04rP4atMHqHueXYdSYhz9fJpRF+MawUP2Crf ccZEqN+zd4/x9M8JC7QjDFlYJQa7Z4O5YcAN69vGE6PBKLyc3C2oX5mh/OG5bQTR VfocXsCcCW5EJz8jVfQt+uEd8ZZPyVIDyNJG0eTXNupwTqYpErpj5LrpsHycEMRj iIDaSQMmHI30HJI/O5MGOWVZXUt9zkaXNVTy/O1T0Bg0/k2+1/zGynNyxTP88vlv qvHihVHr2E7cFTSka3pVnwF2lmQVuOmf3/Z2aj2c9ldgQCkmVYdnmiIk6ysvv1Lv qTh0680vdY++lVg8zhd59589lHMf4DZF0rve5hQjUU/E6Vh6cUPBHiQ3a/2yO0Y0 McHebPpGmho2p33Cx4xNE7jhcwcFNTbD2HV6P/gVCkteF3yvpjQHIdD+pZZj50mt FjH2+JMegXpaTNN/B0uk1krgguUf3LSyV3IpReg25ISE2giRNgciOePm/72/333r BKTKZPzEiHo/Ey6levNHkrhAKg0oaaaohw88AqGBO2OkCqfWrzdJL4kWi6I68UBE E/5y9fxdjInGKK7hbYGha+pQluLVF3AFY1dqn3JoGgYp0zKh8+kUy5vcEheCmJpu FUU381uQENicZ9FsYL+e =T1kv -----END PGP SIGNATURE----- _______________________________________________ tz-announce mailing list tz-announce(a)iana.org https://mm.icann.org/mailman/listinfo/tz-announce

1 0

Egypt DST
by Mina Samuel June 14, 2016

June 14, 2016

Here below the confirmation link from official government website regarding Egypt DST 2016: http://www.cabinet.gov.eg/Media/NewsDetails.aspx?id=30512 ========= 3. On the basis of work to take coordinated world time on the GMT basis for determining the legal time in the Arab Republic of Egypt, the cabinet approved the draft decision of the PM which provides for the timing of Egypt by adding two hours to the coordinated world time (GMT 2). As provided for in the draft resolution that the cabinet may amend the legal time stipulated in article 1 of this law during the period or specific periods of the year in accordance with the considerations of the true connoisseur. The draft resolution would be in addition to the timing of a specific legal special decision on timing and legal status, the starting from the beginning on Friday, 8 July 2016 until the end of the day on Thursday, 27 October of the same year. ========

2 1

[PATCH] Update tz-link.htm URLs
by Paul Eggert June 14, 2016

June 14, 2016

* tz-link.htm: Update URLs. Also, add Chromium OS, and the tzdist WG is now concluded. --- tz-link.htm | 79 +++++++++++++++++++++++++++++++------------------------------ 1 file changed, 40 insertions(+), 39 deletions(-) diff --git a/tz-link.htm b/tz-link.htm index b925c95..adb4fac 100644 --- a/tz-link.htm +++ b/tz-link.htm @@ -10,7 +10,7 @@ content="Sources for time zone and daylight saving time data"> <meta name="DC.Creator" content="Eggert, Paul"> <meta name="DC.Contributor" content="Olson, Arthur David"> -<meta name="DC.Date" content="2016-05-29"> +<meta name="DC.Date" content="2016-06-14"> <meta name="DC.Description" content="Sources of information about time zones and daylight saving time"> <meta name="DC.Identifier" @@ -46,13 +46,14 @@ including <abbr title="GNU's Not Unix">GNU</abbr> C Library</a> (used in <a href="https://en.wikipedia.org/wiki/Linux"><abbr>GNU</abbr>/Linux</a>), -<a href="http://www.android.com">Android</a>, -<a href="https://developer.mozilla.org/en-US/Firefox_OS">Firefox +<a href="https://www.android.com">Android</a>, +<a href="https://developer.mozilla.org/en-US/docs/Mozilla/B2G_OS">B2G <abbr title="Operating System">OS</abbr></a>, <a href="https://www.freebsd.org">Free<abbr title="Berkeley Software Distribution">BSD</abbr></a>, <a href="http://netbsd.org">Net<abbr>BSD</abbr></a>, <a href="http://www.openbsd.org">Open<abbr>BSD</abbr></a>, +<a href="http://www.chromium.org/chromium-os">Chromium OS</a>, <a href="https://cygwin.com">Cygwin</a>, <a href="http://www.delorie.com/djgpp/"><abbr title="DJ's GNU Programming Platform">DJGPP</abbr></a>, @@ -65,7 +66,7 @@ title="Advanced Interactive eXecutive">AIX</abbr></a>, <a href="http://www.apple.com/ios/"><abbr title="iPhone OS">iOS</abbr></a>, <a href="http://windows.microsoft.com">Microsoft Windows</a>, -<a href="http://www8.hp.com/us/en/products/servers/openvms/overview.html">Open<abbr +<a href="http://www.hp.com/go/openvms/">Open<abbr title="Virtual Memory System">VMS</abbr></a>, <a href="https://www.oracle.com/database/index.html">Oracle Database</a>, <a href="http://oracle.com/solaris">Oracle Solaris</a>, and @@ -176,17 +177,17 @@ title="linefeed">LF</abbr></a>, which can be modified by common text editors such as <a href="https://www.gnu.org/software/emacs/">GNU Emacs</a>, <a href="https://wiki.gnome.org/Apps/Gedit">gedit</a>, and -<a href="http://www.vim.org/">vim</a>. One +<a href="http://www.vim.org">vim</a>. One editor has a package to simplify editing further:</p> <ul> <li><a href="https://packagecontrol.io/packages/zoneinfo">Sublime -zoneinfo</a> is a <a href="http://www.sublimetext.com/">Sublime +zoneinfo</a> is a <a href="http://www.sublimetext.com">Sublime Text</a> package for syntax highlighting <code><abbr>tz</abbr></code> source files.</li> </ul> <p> For further information about updates, please see -<a href="http://tools.ietf.org/html/rfc6557">Procedures for +<a href="https://tools.ietf.org/html/rfc6557">Procedures for Maintaining the Time Zone Database</a> (Internet <abbr title="Request For Comments">RFC</abbr> 6557).</p> <h2>Commentary on the <code><abbr>tz</abbr></code> database</h2> @@ -214,7 +215,7 @@ These are listed roughly in ascending order of complexity and fanciness. <ul> <li><a href="http://time.is">Time.is</a> shows locations' time and zones in a simple format.</li> -<li><a href="https://www.timejones.com/">TimeJones.com</a> is a simple +<li><a href="https://www.timejones.com">TimeJones.com</a> is a simple time zone converter.</li> <li><a href="http://twiki.org/cgi-bin/xtra/tzdatepick.html">Date and Time Gateway</a> @@ -233,36 +234,36 @@ Worldwide</a> lets you sort zone names and convert times.</li> calculates the current time difference between locations.</li> <li><a href="http://www.wx-now.com">Weather Now</a> lists the weather too.</li> <li><a href="http://www.thetimenow.com">The Time Now</a> also lists weather.</li> -<li><a href="http://worldtime.io">worldtime.io</a> +<li><a href="https://worldtime.io">worldtime.io</a> also contains data about time zone boundaries; it supports queries via place names and shows location maps.</li> </ul> <h2>Network protocols for <code><abbr>tz</abbr></code> data</h2> <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> has defined <a -href="http://tools.ietf.org/html/rfc7808">TZDIST</a> +<a href="https://datatracker.ietf.org/wg/tzdist/charter/">Time Zone Data +Distribution Service (tzdist) working group</a> defined <a +href="https://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 +along with a <a href="https://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 +(Internet <abbr>RFC</abbr> 7809). This work was based on the iCalendar and CalConnect efforts described below.</li> -<li>The <a href="http://tools.ietf.org/html/rfc5545"> +<li>The <a href="https://tools.ietf.org/html/rfc5545"> Internet Calendaring and Scheduling Core Object Specification (iCalendar)</a> (Internet <abbr>RFC</abbr> 5445) covers time zone data; see its VTIMEZONE calendar component. The iCalendar format requires specialized parsers and generators; a -variant <a href="http://tools.ietf.org/html/rfc6321">xCal</a> +variant <a href="https://tools.ietf.org/html/rfc6321">xCal</a> (Internet <abbr>RFC</abbr> 6321) uses <a href="http://www.w3.org/XML/"><abbr title="Extensible Markup Language">XML</abbr></a> format, and a variant -<a href="http://tools.ietf.org/html/rfc7265">jCal</a> +<a href="https://tools.ietf.org/html/rfc7265">jCal</a> (Internet <abbr>RFC</abbr> 7265) uses <a href="http://www.json.org"><abbr title="JavaScript Object Notation">JSON</abbr></a> format. -<a href="http://calconnect.org">CalConnect, The Calendaring and Scheduling +<a href="https://www.calconnect.org">CalConnect, The Calendaring and Scheduling Consortium</a> is promoting further work in this area. <a href="http://calconnect.org/publications/icalendartimezoneproblemsandrecommendati…">iCalendar TIMEZONE Problems and Recommendations</a> offers guidelines and @@ -270,7 +271,7 @@ recommendations for the use of VTIMEZONE and <code><abbr>tz</abbr></code>.</li> <li>The <a href="http://calconnect.org/publications/timezoneregistryandservicerecommendation…">Timezone Registry and Service Recommendations</a> of CalConnect's -<a href="http://calconnect.org/tc-timezone.shtml">TIMEZONE +<a href="https://www.calconnect.org/about/technical-committees/tc-timezone">TIMEZONE Technical Committee</a> discusses a strategy for defining and deploying a time zone registration process that would establish unique names for each @@ -288,7 +289,7 @@ data</a> converted from <code><abbr>tz</abbr></code>.</li> </ul> <h2>Other <code><abbr>tz</abbr></code> compilers</h2> <ul> -<li><a href="http://sourceforge.net/projects/vzic/">Vzic</a> is a <a +<li><a href="https://sourceforge.net/projects/vzic/">Vzic</a> is a <a href="https://en.wikipedia.org/wiki/C_%28programming_language%29">C</a> program that compiles <code><abbr>tz</abbr></code> source into iCalendar-compatible VTIMEZONE files. @@ -297,21 +298,21 @@ available under the <a href="http://www.gnu.org/copyleft/gpl.html"><abbr>GNU</abbr> General Public License (<abbr title="General Public License">GPL</abbr>)</a>.</li> -<li><a href="http://sourceforge.net/projects/tzical/">tziCal – tz +<li><a href="https://sourceforge.net/projects/tzical/">tziCal – tz database conversion utility</a> is like Vzic, except for the <a -href="https://msdn.microsoft.com/netframework">.NET framework</a> +href="https://www.microsoft.com/net">.NET framework</a> and with a <abbr>BSD</abbr>-style license.</li> <li><a href="http://search.cpan.org/dist/DateTime-TimeZone/">DateTime::TimeZone</a> contains a script <code>parse_olson</code> that compiles -<code><abbr>tz</abbr></code> source into <a href="http://www.perl.org">Perl</a> +<code><abbr>tz</abbr></code> source into <a href="https://www.perl.org">Perl</a> modules. It is part of the Perl <a href="http://datetime.perl.org">DateTime Project</a>, which is freely available under both the <abbr>GPL</abbr> and the Perl Artistic License. DateTime::TimeZone also contains a script <code>tests_from_zdump</code> that generates test cases for each clock transition in the <code><abbr>tz</abbr></code> database.</li> -<li>The <a href="http://howardhinnant.github.io/tz.html">Time Zone +<li>The <a href="https://howardhinnant.github.io/date/tz.html">Time Zone Database Parser</a> is a <a href="https://en.wikipedia.org/wiki/C%2B%2B">C++</a> parser and runtime library. It is freely available under the @@ -328,7 +329,7 @@ into an <abbr>ICU</abbr>-specific format. <abbr>ICU</abbr> is freely available under a <abbr>BSD</abbr>-style license.</li> <li>The <a href="https://github.com/lau/tzdata">Tzdata</a> package for -the <a href="http://elixir-lang.org/">Elixir</a> language downloads +the <a href="http://elixir-lang.org">Elixir</a> language downloads and compiles tz source and exposes <abbr title="Application Program Interface">API</abbr>s for use. It is freely available under the <abbr @@ -432,23 +433,23 @@ in its JavaScript library for time zone conversion. Dates before 1970 are not supported.</li> <li>The <a href="http://hackage.haskell.org/package/timezone-olson">timezone-olson</a> -package contains <a href="http://haskell.org">Haskell</a> code that +package contains <a href="https://www.haskell.org">Haskell</a> code that parses and uses <code><abbr>tz</abbr></code> binary data. It is freely available under a <abbr>BSD</abbr>-style license.</li> </ul> <h2>Other <code><abbr>tz</abbr></code>-based time zone software</h2> <ul> <li><a href="https://foxclocks.org">FoxClocks</a> -is an extension for <a href="http://www.google.com/chrome/">Google +is an extension for <a href="https://www.google.com/chrome/">Google Chrome</a> and for <a href="https://developer.mozilla.org/en-US/docs/Mozilla/Tech/Toolkit_API">Mozilla Toolkit</a> applications like <a href="https://www.mozilla.org/en-US/firefox/new/">Firefox</a> and <a href="https://www.mozilla.org/en-US/thunderbird/">Thunderbird</a>. It displays multiple clocks in the application window, and has a mapping -interface to <a href="http://www.google.com/earth/">Google Earth</a>. +interface to <a href="https://www.google.com/earth/">Google Earth</a>. It is freely available under the <abbr>GPL</abbr>.</li> -<li><a href="http://golang.org">Go programming language</a> +<li><a href="https://golang.org">Go programming language</a> implementations contain a copy of a 32-bit subset of a recent <code><abbr>tz</abbr></code> database in a Go-specific format.</li> @@ -464,7 +465,7 @@ data (mentioned below) used by classes such as <a href="https://msdn.microsoft.com/en-us/library/windows/apps/windows.globalization…"><code>DateTimeFormatter</code></a>. <a -href="http://blogs.msdn.com/b/bclteam/archive/2007/06/07/exploring-windows-time-z…">Exploring +href="https://blogs.msdn.microsoft.com/bclteam/2007/06/07/exploring-windows-time-…">Exploring Windows Time Zones with <code>System.TimeZoneInfo</code></a> describes the older, proprietary method of Microsoft Windows 2000 and later, which stores time zone data in the @@ -495,7 +496,7 @@ licenses</a> to <code><abbr>tz</abbr></code> contributors.</li> </ul> <h2>Other time zone databases</h2> <ul> -<li><a href="http://www.astro.com/cgi/aq.cgi">Atlas Query</a> +<li><a href="http://www.astro.com/atlas">Time-zone Atlas</a> is Astrodienst's Web version of Shanks and Pottenger's time zone history atlases published in both <a href="http://astrocom.com/astrology-products/software/acs-atlas-software">computer</a> @@ -557,8 +558,8 @@ sets of <code><abbr>tz</abbr></code> regions.</li> <li>The <a href="https://github.com/bradfitz/latlong">latlong package</a> maps geographical coordinates to a <code><abbr>tz</abbr></code> region. It is written in Go and is freely available under the Apache License.</li> -<li><a href="http://derickrethans.nl/what-time-is-it.html">What Time -is It Here?</a> applies <a href="http://www.mongodb.org">MongoDB</a> +<li><a href="https://derickrethans.nl/what-time-is-it.html">What Time +is It Here?</a> applies <a href="https://www.mongodb.com">MongoDB</a> geospatial query operators to shapefiles' data.</li> <li><a href="http://statoids.com/statoids.html">Administrative Divisions of Countries ("Statoids")</a> contains lists of @@ -593,7 +594,7 @@ surveys the evolution of timekeeping.</li> <li><a href="http://www.webexhibits.org/daylightsaving/">About Daylight Saving Time – History, rationale, laws & dates</a> is an overall history of <abbr>DST</abbr>.</li> -<li><a href="http://www.w3.org/TR/timezone/">Working with Time Zones</a> +<li><a href="https://www.w3.org/TR/timezone/">Working with Time Zones</a> contains guidelines and best practices for software applications that deal with civil time.</li> <li><a href="http://energy.ca.gov/daylightsaving.html">Saving Time, @@ -693,7 +694,7 @@ Time Protocol</a> (<abbr title="Institute of Electrical and Electronics Engineers">IEEE</abbr> 1588) can achieve submicrosecond clock accuracy on a local area network.</li> <li><a -href="http://tools.ietf.org/html/rfc4833">Timezone +href="https://tools.ietf.org/html/rfc4833">Timezone Options for <abbr title="Dynamic Host Configuration Protocol">DHCP</abbr></a> (Internet <abbr>RFC</abbr> 4833) specifies a <a @@ -738,7 +739,7 @@ dedicated not only to leap seconds but to precise time and frequency in general. It covers the state of the art in amateur timekeeping, and how the art has progressed over the past few decades.</li> <li><a -href="http://www.iers.org/IERS/EN/Publications/Bulletins/bulletins.html"><abbr +href="https://www.iers.org/IERS/EN/Publications/Bulletins/bulletins.html"><abbr title="International Earth Rotation and Reference Systems Service">IERS</abbr> Bulletins</a> contains official publications of the International Earth Rotation and Reference Systems Service, which decides @@ -778,17 +779,17 @@ title="International Organization for Standardization">ISO</abbr> 8601:2004 – Data elements and interchange formats – Information interchange – Representation of dates and times</a>.</li> <li> -<a href="http://www.w3.org/TR/xmlschema-2/#dateTime"><abbr>XML</abbr> +<a href="https://www.w3.org/TR/xmlschema-2/#dateTime"><abbr>XML</abbr> Schema: Datatypes – dateTime</a> specifies a format inspired by <abbr>ISO</abbr> 8601 that is in common use in <abbr>XML</abbr> data.</li> <li> -<a href="http://tools.ietf.org/html/rfc5322">Internet +<a href="https://tools.ietf.org/html/rfc5322">Internet Message Format</a> (Internet <abbr>RFC</abbr> 5322) §3.3 specifies the time notation used in email and <a href="https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol"><abbr>HTTP</abbr></a> headers.</li> <li> -<a href="http://tools.ietf.org/html/rfc3339">Date and Time +<a href="https://tools.ietf.org/html/rfc3339">Date and Time on the Internet: Timestamps</a> (Internet <abbr>RFC</abbr> 3339) specifies an <abbr>ISO</abbr> 8601 profile for use in new Internet -- 2.7.4

1 0

Egypt TZ Update
by ahmed mekawy June 14, 2016

June 14, 2016

Good day,Egypt announced recently that it will return to DST in Julymay you please advise when you are planning to release a new TZ data reflecting this.

4 6

daylight saving and hospital admissions due to trampolines
by Paul Eggert June 10, 2016

June 10, 2016

A research paper published today concludes that in New Zealand, the October spring-forward transition is associated with increased incidence of hospital admissions for trampoline-related injuries for children aged 0-15. The most common injuries are fracture of the radius and/or ulna, and humeral fracture. Children aged 5-9 were responsible for almost half the studied injuries, followed by children aged 0-4. Sources: Yule MS, Krishna S, Rahiri J-S, Hill AG. Trampoline-associated injuries are more common in children in spring. NZ Med J 129:1436 (2016-06-10), 6916. https://www.nzma.org.nz/journal/read-the-journal/all-issues/2010-2019/2016/… Thomas R. Trampoline-associated injuries are more common in children in spring. stuff.co.nz (2016-06-10). http://www.stuff.co.nz/national/80886934/Trampoline-injuries-spike-in-sprin…

1 0

Asia/Tomsk
by Victor Sudakov June 7, 2016

June 7, 2016

Dear Colleagues, As a citizen of Tomsk, I would like to raise some questions concerning the recent addition of the Asia/Tomsk timezone. As you know, this time zone's abbreviation is all numeric: Zone Asia/Tomsk 5:39:51 - LMT 1919 Dec 22 6:00 - +06 1930 Jun 21 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 2002 May 1 3:00 6:00 Russia +06/+07 2011 Mar 27 2:00s 7:00 - +07 2014 Oct 26 2:00s 6:00 - +06 2016 May 29 2:00s 7:00 - +07 In my opinion, it is bad for two reasons: 1. zic warns that 'warning: time zone abbreviation differs from POSIX standard (+06)' 2. Such an abbreviation is not user friendly and even borders on offensive. A locality deserves a name! Could we do something about Asia/Tomsk and other zones with share the same fate: Europe/Astrakhan, Europe/Kirov, Europe/Ulyanovsk, Asia/Barnaul? Thank you for your attention. -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN sip:sudakov@sibptus.tomsk.ru

14 57