- tz - lists.iana.org

[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

efele.net/tz maps updated
by Eric Muller Nov. 29, 2015

Nov. 29, 2015

I have updated the efele.net/tz maps (http://efele.net/maps/tz/) to be in sync with TZ 2015g. The new zones: Pacific/Bougainville Asia/Chita Asia/Srednekolymsk America/Fort_Nelson Antarctica/Troll Eric.

7 8

Machine-readable time zones diff/changelog?
by Максим Кочкин Nov. 27, 2015

Nov. 27, 2015

Hi. Recently I've run into an issue with time zones splitting, it's described in this my SO question — http://stackoverflow.com/questions/33943855/how-to-handle-new-time-zone/339… — and covered by a brilliant answer by Matt Johnson ( http://stackoverflow.com/a/33946308/487923) Matt also mentioned that there was a discussion about some machine-readable tz diff that can help developers to handle that changes like split automatically. Did you try to create a standardized diff/changelog? If not — why not? Or is it only me who needs it, and it can be handled in some other easier way?

2 1

TZ Updater
by Victor Uribe Nov. 26, 2015

Nov. 26, 2015

To whom it may concern, I am in need of acquiring the tz updater version JDK-8054458 found at http://bugs.java.com/view_bug.do?bug_id=8054458 since the Java time is no longer synchronized correctly. Where can I find this file to use on an XP machine running Java 6 update 30. Thank you. Regards, Victor Uribe Application Engineer Modular Mining Systems, Inc. 3289 E. Hemisphere Loop Tucson, Arizona 85706- 5028 USA +1 (520) 344-6376 (work) +1 (602) 762-0213 (cell) vuribe(a)mmsi.com<mailto:vuribe@mmsi.com> www.mmsi.com<http://www.mmsi.com> MODULAR - Mine Smarter™ _________________________________ The information contained in this email, including all attachments, is intended solely for the use of the individual or entity to whom it is addressed and may contain information that is privileged, proprietary and/or confidential. If the reader of this message is not the intended recipient or agent responsible for delivering the message to the intended recipient, you are hereby notified that any perusal, use, dissemination, or disclosure is strictly prohibited. Confidentiality, privilege, or copyright is not waived or lost because you have received this message in error. If you have received this message in error, please notify us immediately by reply email or email postmaster(a)mmsi.com and destroy the original message and any copies. Modular®, IntelliMine®, DISPATCH®, ProVision®, MineCare®, MasterLink®, PowerView ™, and ModularReady® are trademarks and/or registered trademarks and the sole and exclusive property of Modular Mining Systems, Inc.

2 1

More Russian Changes
by Matt Johnson Nov. 25, 2015

Nov. 25, 2015

FYI - Two draft bills are posted on the Russian government's web site: http://government.ru/activities/20702/ http://government.ru/activities/20703/ If approved, the effect would be to move the Astrakhan region from UTC+3 to UTC+4, and to move the Trans-Baikal region from UTC+8 to UTC+9. Neither bill mentions an effective date. It's not clear whether the Trans-Baikal region refers to the entire area of Zabaykalsky Krai or some subset. Zabaykalsk Krai is currently managed by the Asia/Chita time zone, which I assume would remain intact and just get a new row in its zone entry. Also, assuming by Astrakhan region they mean the Astrakhan Oblast, then I think this change would require a new time zone. I suggest Europe/Astrakan for the city of the same name in this region. This is split from the Europe/Volograd time zone. -Matt

1 2