- tz - lists.iana.org

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

Jan. 27, 2016

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

3 4

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

Jan. 27, 2016

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

1 0

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

Jan. 22, 2016

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

8 11

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

Jan. 20, 2016

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

1 0

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

Jan. 18, 2016

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

2 2

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

Jan. 18, 2016

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

2 1

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

Jan. 16, 2016

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

2 4

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

Jan. 13, 2016

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

5 7

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

Jan. 12, 2016

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

1 0

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

Jan. 7, 2016

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

2 1

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

Jan. 2, 2016

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

3 3

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

Jan. 2, 2016

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

3 4

Taiwan (Asia/Taipei) Abbrevation
by Matt Johnson Dec. 26, 2015

Dec. 26, 2015

TZDB uses the abbreviations CST and CDT for Taiwan (Asia/Taipei), CDT last being observed in 1979. According to https://en.wikipedia.org/wiki/Time_in_Taiwan:...the government on Taiwan now favors the term National Standard Time (國家標準時間) as official use. Along with the governmental standard, popular alternatives include Taiwan Standard Time (臺灣標準時間), Taipei Time (臺北時間) and Formosan Time (寶島時間)... Should we update the current abbreviation to either NST or TST? CST doesn't seem right. I'm asking on behalf of a user of moment-timezone (a JS library that imports TZDB) who requested this here: https://github.com/moment/moment-timezone/issues/282 Thanks,Matt

3 2

FYI Time zone used in Fort Pierre SD USA
by RICK MCDERMID Dec. 25, 2015

Dec. 25, 2015

FYI, see below for some information regarding the City of Fort Pierre SD USA time zone. It looks like Fort Pierre and the surrounding Stanley County unofficially use Central Time.. Rick McDermid, Chilliwack BC Canada rickmcdermid(a)shaw.ca ----- Original Message ----- From: "Administration" <Admin1(a)fortpierre.com> To: "RICK MCDERMID" <rickmcdermid(a)shaw.ca> Sent: Monday, December 21, 2015 1:46:47 PM Subject: RE: Question about time in Fort Pierre Hi Rick Yes, Fort Pierre is technically located in the Mountain time zone as is the rest of Stanley County. Most of Stanley County and Fort Pierre uses the Central time zone due to doing most of their business in Pierre so it simplifies schedules. I have lived in Stanley County all my life and it has been that way since I can remember. (43 years!) I hope this helps you. If you have any further questions let me know. Thanks! Kelly City of Fort Pierre From: RICK MCDERMID [mailto:rickmcdermid@shaw.ca] Sent: Monday, December 21, 2015 3:22 PM To: admin1(a)fortpierre.com Subject: Question about time in Fort Pierre Hello. I'm updating some geographic data, and I have a question about your time zone. I understand that Fort Pierre is officially on Mountain time, while Pierre is on Central time. However, based on your location right across the river, it looks like you might actually use the same time as Pierre. Could you tell me which time zone you use? If you do follow Central time like Pierre, do you know if the rest of Stanley County does likewise? Do you know if there is any history to the issue? If you do go by the unofficial Central time I will pass the info along to www.iana.org , a non-profit which (among other things) publishes a global time zone database used widely for computer apps and the like. Thanks for your help. Rick McDermid, Chilliwack BC Canada rickmcdermid(a)shaw.ca

4 4

Admins should check expiration date of leap second file
by Martin Burnicki Dec. 22, 2015

Dec. 22, 2015

Folks, I've just checked some of the commonly known sources for the leap second file to be used with NTP and found that some sites on the internet only provide outdated versions of the leap second file. Some of the files will expire on 28 December 2015. So if you have an NTP daemon running and a leap second file specified in the ntp.conf file you should check if you have a current copy of the file installed, or otherwise update the leap second file. Unlike earlier version of ntpd (up to 4.2.6*), current versions (4.2.8*) of the NTP daemon really evaluate the expiration date of the file, and don't accept outdated an outdated leap second file. For many NTP installations this doesn't really matter, but - if an applications expects a current TAI offset set in the OS kernel then it won't get the correct information without a valid leap second file - if a valid leap second file is available then the leap second information takes precedence over leap second announcements from upstream servers, etc., so a valid leap second files provides some protection against wrong leap second announcements from faulty upstream servers. The original leap second file from NIST is available via this link: ftp://time.nist.gov/pub/leap-seconds.3629404800 (current) ftp://time.nist.gov/pub/leap-seconds.list (link to current) and the current version expires 28 June 2016. However, unfortunately the NIST server is often not reachable. The IERS which decides whether a leap second is to be scheduled or not, is now also providing an own leap second file: https://hpiers.obspm.fr/iers/bul/bulc/ntp/leap-seconds.3651350400 (current) https://hpiers.obspm.fr/iers/bul/bulc/ntp/leap-seconds.list (link to current) However, this file already expires on 28 January 2016, which is pretty early. I've already contacted the folks at IERS and asked them to set the expiration date to shortly before the next leap second event. I guess they will provide a new leap second file shortly after the next bulletin C has been published in January 2016. The USNO formerly also provided an own version of a leap second file via ftp://tycho.usno.navy.mil/pub/ntp/ However, on this web page there is only an outdated copy of the IERS file now, which expires on 28 December 2015. I've already tried to contact the folks at USNO and asked them to update their server, but haven't received a reply, yet. A copy of the current leap second file can also be found in the current Time Zone data package provided by the IANA. Since the IETF web site provides an unpacked copy of the tzdata archive the NIST file is also available here: http://www.ietf.org/timezones/data/ http://www.ietf.org/timezones/data/leap-seconds.list (shipped with tzdata, copy of a NIST file) Since this is a copy of the current NIST file this file is valid until 28 June 2016. Another copy of the current NIST leap second file is available via the Meinberg web site: http://www.meinberg.de/download/ntp/leap-seconds.list Hope this helps. Martin -- Martin Burnicki Senior Software Engineer MEINBERG Funkuhren GmbH & Co. KG Email: martin.burnicki(a)meinberg.de Phone: +49 (0)5281 9309-14 Fax: +49 (0)5281 9309-30 Lange Wand 9, 31812 Bad Pyrmont, Germany Amtsgericht Hannover 17HRA 100322 GeschÃ¤ftsfÃ¼hrer/Managing Directors: GÃ¼nter Meinberg, Werner Meinberg, Andre Hartmann, Heiko Gerstung Web: http://www.meinberg.de

1 0

[PROPOSED PATCH] Add Dublin Core profile attribute
by Paul Eggert Dec. 13, 2015

Dec. 13, 2015

* tz-link.htm: Add profile attribute to head element. See: http://dublincore.org/documents/2008/08/04/dc-html-notes/ --- tz-link.htm | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tz-link.htm b/tz-link.htm index ca2f2bc..e448184 100644 --- a/tz-link.htm +++ b/tz-link.htm @@ -2,7 +2,7 @@ PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"> <html> -<head> +<head profile="http://dublincore.org/documents/2008/08/04/dc-html/"> <title>Sources for Time Zone and Daylight Saving Time Data</title> <link rel="schema.DC" href="http://purl.org/DC/elements/1.1/"> <meta http-equiv="Content-type" content='text/html; charset="UTF-8"'> -- 2.1.0

2 4

[PATCH] Change Cayman abbreviations to CIST and CIDST
by Paul Eggert Dec. 11, 2015

Dec. 11, 2015

A bill to implement US-style daylight saving time has been published by the Cayman Islands Gazette, so it looks like our clock predictions are still on track. The bill gives Cayman-specific time zone abbreviations, though, so we need to change tzdata for that. * NEWS: Document this. * northamerica (Cayman): New rule. It is like the US since 2016, but with different LETTER/S. (America/Cayman): Use it. --- NEWS | 3 +++ northamerica | 17 +++++++++++------ 2 files changed, 14 insertions(+), 6 deletions(-) diff --git a/NEWS b/NEWS index 121e0e4..ac0369c 100644 --- a/NEWS +++ b/NEWS @@ -11,6 +11,9 @@ Unreleased, experimental changes America/Metlakatla switched from PST all year to AKST/AKDT on 2015-11-01 at 02:00. (Thanks to Steffen Thorsen.) + Time zone abbreviations for America/Cayman have been changed from + EST/EDT to CIST/CIDST, as per the 2015-11-25 daylight-saving bill. + Changes affecting future time stamps Asia/Tehran now has DST predictions for the year 2038 and later, diff --git a/northamerica b/northamerica index e916524..38a8beb 100644 --- a/northamerica +++ b/northamerica @@ -2688,16 +2688,21 @@ Zone Atlantic/Bermuda -4:19:18 - LMT 1930 Jan 1 2:00 # Hamilton # Cayman Is -# From Paul Eggert (2015-05-15): +# From Paul Eggert (2015-12-08): # The Cayman government has decided to introduce DST in 2016, the idea being -# to keep in sync with New York. The legislation hasn't passed but the change -# seems quite likely. See: Meade B. Cayman 27. -# http://www.cayman27.com.ky/2015/05/15/clock-ticks-toward-daylight-saving-ti… +# to keep in sync with New York. The enabling legislation has been published, +# and seems quite likely to be approved. See Cayman Islands +# Extraordinary Gazette No. 92 (2015-11-25), Supp. 2, which specifies the +# abbreviations CIST and CIDST. +# http://www.gov.ky/portal/pls/portal/docs/1/12274400.PDF + +# Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S +Rule Cayman 2016 max - Mar Sun>=8 2:00 1:00 D +Rule Cayman 2016 max - Nov Sun>=1 2:00 0 - Zone America/Cayman -5:25:32 - LMT 1890 # Georgetown -5:07:11 - KMT 1912 Feb # Kingston Mean Time - -5:00 - EST 2016 - -5:00 US E%sT + -5:00 Cayman CI%sST # Costa Rica -- 2.1.0

3 3

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

Dec. 10, 2015

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

2 11

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

Dec. 9, 2015

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

3 2

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

Dec. 8, 2015

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

2 1

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

Dec. 8, 2015

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

6 9

Re: [tz] Question about historical TZData for North Carolina
by Paul Eggert Dec. 7, 2015

Dec. 7, 2015

On 12/07/2015 04:25 AM, Clifford Ribaudo wrote: > http://ncpedia.org/time-zones > > The relevant section of the article states that: > > On 28 Sept. 1947 North Carolina adopted Eastern Standard Time statewide. > > During World War I, North Carolina adopted Daylight Time for the periods 31 Mar.-27 Oct. 1918 and 30 Mar.-26 Oct. 1919. Between 1 Aug. 1941 and 9 Feb. 1942, state offices operated on Daylight Time; from 9 Feb. 1942 to 30 Sept. 1945, North Carolina implemented what President Franklin D. Roosevelt called "War Time." From 1946 to 1965 North Carolina did not observe Daylight Time, but since 1966 the state has followed the national schedule. > > So in summary that means we have: > > 1) Sep 28 1947 statewide adoption of ET > 2) Mar 31 - Oct 27 1918 Adopted Daylight Time > 3) Mar 30 - Oct 26 1919 Adopted Daylight Time > 4) Feb 9 1942 - Sep 30 1945 Adopted War Time > 5) 1946 - 1965 Daylight time NOT observed > 6) 1966 - Entire state adopts national schedule for Daylight time. > > So I would propose that this data be added to an America/North_Carolina entry in backzone That's useful info. Let me try to summarize what work would need to be done to get this in (and this may help to explain why it hasn't been done yet....). First, that source is better than nothing, but it has real problems. First, it cites secondary sources (Doane is an old astrology book if I'm not mistaken, and the DOT source is also secondary), and these secondary sources are often in error. Second, it summarizes the secondary sources without giving full details, e.g., it doesn't say which part of North Carolina formerly observed Central Time, and it doesn't give the times that switchovers occurred. Someone should read the secondary sources directly, or better yet, read the primary sources that they are based on, to get as many details as we can. Second, whatever data we come up with needs to be put in tzdata form, with commentary citing the sources. You can look at the existing 'northamerica' and 'backzone' files for examples, and read the tzfile man page (and the file 'Theory', which explains naming and in particular why we shouldn't use the name 'America/North_Carolina') for details. The result should be a patch to the file 'backone' in Git form. If that's all done and the patch goes in, you should be able to run 'make posix_packrat', and use the result in your programs.

1 0

Possible DST Discrepancies for Manitoba, Canada
by Rena B Dec. 7, 2015

Dec. 7, 2015

Across the board, I've come across a possible discrepancy that I can't seem to let go off. The years 1957 - 1963 in the data base for Manitoba. Winnipeg and Selkirk both switch for those years appropriately, but none of the other Manitoba towns I've tried have. My birth date is June 1957 in one of the town and I cannot find out if DST was province wide for that year. I believe there were 2 years in this time frame that Winnipeg did not subscribe to DST (1960-61). Would very much appreciate if you have the resources to look into this? If the rest of the towns in Manitoba followed Winnipeg/Selkirk, then there is a large error margin happening. Regards, Rena Bergman

3 2

Question about historical TZData for North Carolina
by Clifford Ribaudo Dec. 7, 2015

Dec. 7, 2015

Hi, I’m working on some astronomical/astrological software and looking for open source Historical Time Zone data. Obviously I’m looking at tzdata but find that while some local peculiarities are covered such as Indiana, but places like North Carolina are not? Specifically, there does not appear to be a way to do a tzdump for America/North_Carolina to get the adoption of DST in 1966? Am I missing something here? North Carolina appears to be grouped under America/New_York, however New York DST adoption was very different from some of the other more “stubborn” states in the Eastern Zone. I would like to propose that Zone Names be added for each state and which at a minimum simply model the adoption of DST in 1966. This is helpful to applications like mine that look up a zone name by lat/lng and then try to get a Time Zone for a date. Thanks, Cliff Ribaudo cr(a)iphemeris.com

3 3

south korea will use DST in 2016
by Sebastien WILLEMIJNS Dec. 6, 2015

Dec. 6, 2015

hello, dunno if it was displayed here http://french.yonhapnews.co.kr/news/2015/12/06/0200000000AFR201512060003008…

4 3