- tz - lists.iana.org

Time zone reference inconsistencies
by J-F Rivard Jan. 6, 2015

Jan. 6, 2015

To whom it may be of interest: The time zone rule files referred to following locations that are not found in "zone1970.tab": America/Montreal America/Antigua America/Cayman Asia/Bahrain Asia/Kuwait Asia/Muscat Asia/Aden Pacific/Saipan Pacific/Midway Note: some (if not all) of the above-listed locations are found in "zone.tab", but the documentation states that "zone1970.tab" should be used instead. Thank you for your excellent (and much appreciated!) work. Happy new year 2015! J-F Rivard *J-F Rivard | Consultant** | T:450.653.2912** | C:438.495.2912* *univoc(a)videotron.ca <univoc(a)videotron.ca>*

1 0

Time zones in the news
by Arthur David Olson Jan. 2, 2015

Jan. 2, 2015

"How to celebrate New Year’s in every time zone" http://www.washingtonpost.com/blogs/wonkblog/wp/2014/12/31/how-to-celebrate… (The article covers the traditional 24 time zones rather than those of TZDB.) @dashdashado

5 5

Re: [tz] [Tzdist] Getting to closure Re: [tzdist] #31 (service): Include leap seconds?
by Paul Eggert Dec. 19, 2014

Dec. 19, 2014

On 12/17/2014 06:55 AM, Martin Burnicki wrote: > > 2.) We have the leap second file from TZ DB. This file has a different > format than the NIST file, but as far as I can see is simply generated > from a file in NIST format by a script which is part of the TZ DB > package. Unfortunately the expiration date is *not* migrated into the > TZ DB's leap second file, so some important information is lost. > Thanks for reporting this. I have installed the attached fix in the experimental tz sources on github and it should appear in the next tz release. I am cc'ing the tz mailing list to give them a heads-up. > 3.) We have a leap second file from IERS, which is once more in a > different format than the ones mentioned above. > > In my opinion the IERS should be the authoritative source for a leap > second file (or table) since this is the institution deciding whether > a leap second is to be scheduled, I would prefer this also. However, the IERS file is copyrighted. That is why the tz database reproduces the NIST file (the NIST file is public domain). Other distributors of the IERS file might want to keep this in mind. Amusingly enough, the NIST file's expiration date disagrees with the IERS's. As a practical matter the NIST's date is more conservative and is a better choice for applications like tz and tzdist and this is another argument for using the NIST file. Perhaps someday the IERS will address these two concerns.

3 3

Info regarding TZ database
by Naveed Shakur Dec. 16, 2014

Dec. 16, 2014

Good day My name is Naveed and I have some query regarding the TZ database, is it possible to query the timezone database maintained by IANA or any other possible solution to have a local copy of the same at our own premises, we have to integrate with our in-house application with timezone information. Best Regards and Thank You Naveed Shakur.

4 4

US Sep 30, 1945
by Ken Murchison Dec. 12, 2014

Dec. 12, 2014

All, I'm wondering why the US rule for Sep 30, 1945 uses an explicit date rather than lastSun, where it would dovetail nicely into the existing rules for America/New_York, Chicago, Indiana/Indianapolis (and maybe others) which cover 1946-1954. The only reason that I care is because when converting the TZ data into iCalendar VTIMEZONEs with vzic, the dst->std transition for 1945 doesn't get coalesced into the recurrence rule for 1946-1954. I won't bother going into the reason for how/why vzic isn't able to coalesce these, but I'm pretty sure that it would take a non-trivial amount of work/logic/code to fix it. -- Kenneth Murchison Principal Systems Software Engineer Carnegie Mellon University

3 4

U.S. 1946-1966 dst
by John Madziarczyk Dec. 11, 2014

Dec. 11, 2014

Hi, I apologize is this question has been asked many times before, but is there any publication out there that lists all the observances and non-observances of Daylight Savings Time in the U.S. in the years between the end of World War II and the Uniform Time Act? John Madziarczyk

3 3

time zone 1948
by Susan Ferrara Dec. 8, 2014

Dec. 8, 2014

Hi, I was born in the Naval Hospital at Quantico Marine Base in August of 1948. I would like to know if the base was using DST or EST during that time period. Any advice you can give me as to how I can find this information would be greatly appreciated. Thanks, Susan Nichols

3 2

Mexico city 1950
by Alois Treindl Dec. 8, 2014

Dec. 8, 2014

Dear Paul I am looking at the timezone for Mexico City 1950. There is a special rules for DST 12 Feb - 31 July 1950, which seems to apply only to Mexico City. I need to find out the definition of the geographic area for which this is valid. You quote as a source http://www.cddhcu.gob.mx/bibliot/publica/inveyana/polisoc/horver/ but I cannot access that source. Do you happen to keep an offline copy of that source information? Best regards Alois

4 3

Adding Asia/Beijing timezone into the database
by Daoming Qiu Dec. 6, 2014

Dec. 6, 2014

"Beijing Time" is the standard time used for China region, so it is very strange that tzdatabase doesn't have timezone called Asia/Beijing. Strongly suggest to add "Asia/Beijing" zone into the database, and its information is very similar with "Asia/Shanghai".

14 17

Leap seconds
by Arthur David Olson Dec. 3, 2014

Dec. 3, 2014

Given history to date, the leap second information needed by knowledgeable, concerned clients is, in its entirety: 1972-06 1972-12 1973-12 1974-12 1975-12 1976-12 1977-12 1978-12 1979-12 1981-06 1982-06 1983-06 1985-06 1987-12 1989-12 1990-12 1992-06 1993-06 1994-06 1995-12 1997-06 1998-12 2005-12 2008-12 2012-06 These are the months at the ends of which leap seconds were inserted.* I'm confident that a way of getting the information to such clients can be developed. It may be prudent to wait and see if the status of the leap second changes in 2015; a change may obviate the need for leap second updates (though not the need for information on past leap seconds). @dashdashado *This ignores the possibility of skipped seconds, which have yet to occur in the wild. It also ignores niceties such as New York City, which at least once "observed" the leap second at midnight New York time rather than midnight UTC, making for a ball drop countdown of "Three...two...one...leap...Happy New Year!"

1 0