- tz - lists.iana.org

"non-standard" timezones
by Shawn Steele Jan. 5, 2013

Jan. 5, 2013

Hoping someone can provide examples or something. Are there cases where people are using their own Timezone data? (I'm thinking like a company or research station or something that doesn't snap to some "normal" tz for some reason) Any examples? For non-standard timezones is there a recommendation for naming conventions? (Eg: etc/mine ?) In several systems it's possible to adjust the Timezone data, and, of course someone could edit and install their own versions of the tzdb data on systems that consume it, but I'm curious if it ever happens in practice? Thanks, Shawn

2 3

timezone db error
by Mayuresh Kathe Dec. 29, 2012

Dec. 29, 2012

Hello, there's an error while representing a timezone in your database. May I know who to communicate and interact with regarding getting it corrected? Thanks. ~Mayuresh -- Simplicity can be Marvelously Powerful.

5 8

Non-ASCII chars in southamerica file
by Andy Heninger Dec. 27, 2012

Dec. 27, 2012

In the southamerica data file we have several Latin-1 encoded non-ASCII characters. The other data files are 100% ASCII Here they are: $ grep -nP "[\\x80-\\xff]" * southamerica:384:# There's also a note in only one of the major national papers (La Naci�n) at southamerica:390:# (...) anunci� que el pr�ximo domingo a las 00:00 los puntanos deber�n southamerica:393:# A partir de entonces, San Luis establecer� el huso horario propio de southamerica:395:# 2009, el cambio horario quedar� comprendido entre las 00:00 del tercer southamerica:396:# domingo de marzo y las 24:00 del segundo s�bado de octubre. southamerica:815:# I just send a e-mail to Zulmira Brand�o at I think it's fine to allow non-ASCII in comments, but would strongly request that the files be UTF-8 encoded. Anything else leads to immense confusion over what charset is in use. -- Andy

4 3

zoneinfo : ist : error
by Mayuresh Kathe Dec. 21, 2012

Dec. 21, 2012

may i know the reason why asia/kolkata represents +0530 in india? logically, technically and politically speaking, it's incorrect. ~mayuresh

7 10

Fwd: [IANA #636310] how to check a time
by Gemma Conn Nov. 30, 2012

Nov. 30, 2012

Hello, Can you point me in the direction of where I can double check that IANA has the correct time for New Zealand? I am worried that IANA has the wrong time for New Zealand, as Google Calendar which claims to use IANA Time Zone Database, displays the incorrect time for New Zealand. It displays GMT + 12 Auckland but it should be GMT + 13 Auckland, as we are observing Daylight Savings time. Sorry I could not find the right place to check this on your website - can you please check for me or tell me where I can check what time the IANA Time Zone Database has for New Zealand? I will let Google know if the mistake lies with them. Thanks Gemma Begin forwarded message: > From: Paul Eggert <eggert(a)cs.ucla.edu> > Date: 29 November 2012 2:17:18 PM NZDT > To: Gemma Conn <gemma(a)biozone.co.nz> > Subject: Re: Fwd: [IANA #636310] how to check a time > > On 11/28/2012 12:49 PM, Gemma Conn wrote: >> I couldn't find the place on the IANA website where I can check a time... > > I'm afraid there isn't a simple way to do that automatically. > I suggest you ask by sending email to tz(a)iana.org. This > mailing list is discussed in <http://www.iana.org/time-zones>.

7 6

patch for leapseconds to incorporate IERS bulletin C44
by Robert Elz Nov. 27, 2012

Nov. 27, 2012

In accordance with the tradition of keeping a copy of the most recent IERS bulletin C (currently C 44) in the leapseconds file (as comments at the end), here's a patch that updates it from C43 to C44. kre --- leapseconds 2012-01-06 18:37:49.000000000 +0700 +++ leapseconds.C44 2012-11-27 19:05:37.000000000 +0700 @@ -58,36 +58,28 @@ # SERVICE DE LA ROTATION TERRESTRE # OBSERVATOIRE DE PARIS # 61, Av. de l'Observatoire 75014 PARIS (France) -# Tel. : 33 (0) 1 40 51 22 26 +# Tel. : 33 (0) 1 40 51 22 29 # FAX : 33 (0) 1 40 51 22 91 # e-mail : (E-Mail Removed) # http://hpiers.obspm.fr/eop-pc # -# Paris, 5 January 2012 +# Paris, 7 August 2012 # # -# Bulletin C 43 +# Bulletin C 44 # # To authorities responsible # for the measurement and # distribution of time # # -# UTC TIME STEP -# on the 1st of July 2012 +# INFORMATION ON UTC - TAI # +# NO leap second will be introduced at the end of December 2012. +# The difference between Coordinated Universal Time UTC and the +# International Atomic Time TAI is : # -# A positive leap second will be introduced at the end of June 2012. -# The sequence of dates of the UTC second markers will be: -# -# 2012 June 30, 23h 59m 59s -# 2012 June 30, 23h 59m 60s -# 2012 July 1, 0h 0m 0s -# -# The difference between UTC and the International Atomic Time TAI is: -# -# from 2009 January 1, 0h UTC, to 2012 July 1 0h UTC : UTC-TAI = - 34s -# from 2012 July 1, 0h UTC, until further notice : UTC-TAI = - 35s +# from 2012 July 1, 0h UTC, until further notice : UTC-TAI = -35 s # # Leap seconds can be introduced in UTC at the end of the months of December # or June, depending on the evolution of UT1-TAI. Bulletin C is mailed every

1 0

Google moves beyond NTP
by Ted Cabeen Nov. 27, 2012

Nov. 27, 2012

Interesting article on how Google has moved beyond NTP, with a mention of last year's leap second: http://www.wired.com/wiredenterprise/2012/11/google-spanner-time/ --Ted

6 5

Rerun of changes for Russia
by Arthur David Olson Nov. 26, 2012

Nov. 26, 2012

A second rerun, this time for the "europe" and "zone.tab" files to reflect Russian time zone changes in 2011. Again, provided both as an attachment and with tabs mangled below. Again, these have been adjusted to be relative to tz2012j. --ado *** tz2012j/europe 2012-11-09 20:49:36.000000000 -0500 --- tznew/europe 2012-11-25 16:21:23.538043000 -0500 *************** *** 2043,2048 **** --- 2043,2112 ---- # Russia + # From Alexander Krivenyshev (2011-09-15): + # Based on last Russian Government Decree # 725 on August 31, 2011 + # (Government document + # <a href="http://www.government.ru/gov/results/16355/print/"> + # http://www.government.ru/gov/results/16355/print/ + # </a> + # in Russian) + # there are few corrections have to be made for some Russian time zones... + # All updated Russian Time Zones were placed in table and translated to English + # by WorldTimeZone.com at the link below: + # <a href="http://www.worldtimezone.com/dst_news/dst_news_russia36.htm"> + # http://www.worldtimezone.com/dst_news/dst_news_russia36.htm + # </a> + + # From Sanjeev Gupta (2011-09-27): + # Scans of [Decree #23 of January 8, 1992] are available at: + # <a href="http://government.consultant.ru/page.aspx?1223966"> + # http://government.consultant.ru/page.aspx?1223966 + # They are in Cyrillic letters (presumably Russian). + + # From Arthur David Olson (2012-05-09): + # Regarding the instant when clocks in time-zone-shifting parts of Russia + # changed in September 2011: + # + # One source is + # < a href="http://government.ru/gov/results/16355/> + # http://government.ru/gov/results/16355/ + # </a> + # which, according to translate.google.com, begins "Decree of August 31, + # 2011 No 725" and contains no other dates or "effective date" information. + # + # Another source is + # <a href="http://www.rg.ru/2011/09/06/chas-zona-dok.html"> + # http://www.rg.ru/2011/09/06/chas-zona-dok.html + # </a> + # which, according to translate.google.com, begins "Resolution of the + # Government of the Russian Federation on August 31, 2011 N 725" and also + # contains "Date first official publication: September 6, 2011 Posted on: + # in the 'RG' - Federal Issue number 5573 September 6, 2011" but which + # does not contain any "effective date" information. + # + # Another source is + # <a href=" http://en.wikipedia.org/wiki/Oymyakonsky_District#cite_note-RuTime-7"> + # http://en.wikipedia.org/wiki/Oymyakonsky_District#cite_note-RuTime-7 + # </a> + # which, in note 8, contains "Resolution #725 of August 31, 2011... + # Effective as of after 7 days following the day of the official publication" + # but which does not contain any reference to September 6, 2011. + # + # The Wikipedia article refers to + # <a href=" http://base.consultant.ru/cons/cgi/online.cgi?req=doc;base=LAW;n=118896"> + # http://base.consultant.ru/cons/cgi/online.cgi?req=doc;base=LAW;n=118896 + # </a> + # which seems to copy the text of the government.ru page. + # + # Tobias Conradi combines Wikipedia's + # "as of after 7 days following the day of the official publication" + # with www.rg.ru's "Date of first official publication: September 6, 2011" to get + # September 13, 2011 as the cutover date (unusually, a Tuesday, as Tobias Conradi notes). + # + # None of the sources indicates a time of day for changing clocks. + # + # Go with 2011-09-13 0:00s. + # From Paul Eggert (2006-03-22): # Except for Moscow after 1919-07-01, I invented the time zone abbreviations. # Moscow time zone abbreviations after 1919-07-01, and Moscow rules after 1991, *************** *** 2270,2283 **** # [parts of] Respublika Sakha (Yakutiya). # From Oscar van Vlijmen (2009-11-29): ! # The Sakha districts are: Bulunskij, Verkhoyanskij, Tomponskij, Ust'-Majskij, ! # Ust'-Yanskij. Zone Asia/Vladivostok 8:47:44 - LMT 1922 Nov 15 9:00 - VLAT 1930 Jun 21 # Vladivostok Time 10:00 Russia VLA%sT 1991 Mar 31 2:00s 9:00 Russia VLA%sST 1992 Jan 19 2:00s 10:00 Russia VLA%sT 2011 Mar 27 2:00s 11:00 - VLAT # # Sakhalinskaya oblast'. # The Zone name should be Yuzhno-Sakhalinsk, but that's too long. --- 2334,2359 ---- # [parts of] Respublika Sakha (Yakutiya). # From Oscar van Vlijmen (2009-11-29): ! # The Sakha districts are: Bulunskij, Verkhoyanskij, ... Ust'-Yanskij. Zone Asia/Vladivostok 8:47:44 - LMT 1922 Nov 15 9:00 - VLAT 1930 Jun 21 # Vladivostok Time 10:00 Russia VLA%sT 1991 Mar 31 2:00s 9:00 Russia VLA%sST 1992 Jan 19 2:00s 10:00 Russia VLA%sT 2011 Mar 27 2:00s 11:00 - VLAT + + # From Arthur David Olson (2012-05-09): + # Tomponskij and Ust'-Majskij switched from Vladivostok time to Yakutsk time + # in 2011. + + Zone Asia/Khandyga 9:02:13 - LMT 1922 Nov 15 + 9:00 - VLAT 1930 Jun 21 # Vladivostok Time + 10:00 Russia VLA%sT 1991 Mar 31 2:00s + 9:00 Russia VLA%sST 1992 Jan 19 2:00s + 10:00 Russia VLA%sT 2011 Mar 27 2:00s + 11:00 - VLAT 2011 Sep 13 0:00s # Decree 725? + 10:00 - YAKT + # # Sakhalinskaya oblast'. # The Zone name should be Yuzhno-Sakhalinsk, but that's too long. *************** *** 2296,2309 **** # From Oscar van Vlijmen (2009-11-29): # The Sakha districts are: Abyjskij, Allaikhovskij, Verkhhhnekolymskij, Momskij, ! # Nizhnekolymskij, Ojmyakonskij, Srednekolymskij. Zone Asia/Magadan 10:03:12 - LMT 1924 May 2 10:00 - MAGT 1930 Jun 21 # Magadan Time 11:00 Russia MAG%sT 1991 Mar 31 2:00s 10:00 Russia MAG%sT 1992 Jan 19 2:00s 11:00 Russia MAG%sT 2011 Mar 27 2:00s 12:00 - MAGT ! # # From Oscar van Vlijmen (2001-08-25): [This region consists of] # Kamchatskaya oblast', Koryakskij avtonomnyj okrug. # --- 2372,2396 ---- # From Oscar van Vlijmen (2009-11-29): # The Sakha districts are: Abyjskij, Allaikhovskij, Verkhhhnekolymskij, Momskij, ! # Nizhnekolymskij, ... Srednekolymskij. Zone Asia/Magadan 10:03:12 - LMT 1924 May 2 10:00 - MAGT 1930 Jun 21 # Magadan Time 11:00 Russia MAG%sT 1991 Mar 31 2:00s 10:00 Russia MAG%sT 1992 Jan 19 2:00s 11:00 Russia MAG%sT 2011 Mar 27 2:00s 12:00 - MAGT ! ! # From Arthur David Olson (2012-05-09): ! # Ojmyakonskij and the Kuril Islands switched from ! # Magadan time to Vladivostok time in 2011 ! Zone Asia/Ust-Nera 9:32:54 - LMT 1924 May 2 ! 10:00 - MAGT 1930 Jun 21 # Magadan Time ! 11:00 Russia MAG%sT 1991 Mar 31 2:00s ! 10:00 Russia MAG%sT 1992 Jan 19 2:00s ! 11:00 Russia MAG%sT 2011 Mar 27 2:00s ! 12:00 - MAGT 2011 Sep 13 0:00s # Decree 725? ! 11:00 - VLAT ! # From Oscar van Vlijmen (2001-08-25): [This region consists of] # Kamchatskaya oblast', Koryakskij avtonomnyj okrug. # *** tz2012j/zone.tab 2012-07-18 20:30:38.000000000 -0400 --- tznew/zone.tab 2012-11-25 16:24:25.920299600 -0500 *************** *** 341,348 **** --- 341,350 ---- RU +5601+09250 Asia/Krasnoyarsk Moscow+04 - Yenisei River RU +5216+10420 Asia/Irkutsk Moscow+05 - Lake Baikal RU +6200+12940 Asia/Yakutsk Moscow+06 - Lena River + RU +623923+1353314 Asia/Khandyga Moscow+06 - Tomponsky, Ust-Maysky RU +4310+13156 Asia/Vladivostok Moscow+07 - Amur River RU +4658+14242 Asia/Sakhalin Moscow+07 - Sakhalin Island + RU +643337+1431336 Asia/Ust-Nera Moscow+07 - Oymyakonsky RU +5934+15048 Asia/Magadan Moscow+08 - Magadan RU +5301+15839 Asia/Kamchatka Moscow+08 - Kamchatka RU +6445+17729 Asia/Anadyr Moscow+08 - Bering Sea

2 1

Not a rerun: tz-art.htm
by Arthur David Olson Nov. 25, 2012

Nov. 25, 2012

While it might not be a rerun, it's very important either: an addition to "tz-art.htm" to cover a "Da Vinci's Inquest" episode. As with the previous two, it's relative to tz2012j and appears both as an attachment and with tabs mangled below. --ado *** tz2012j/tz-art.htm 2012-07-18 22:23:31.000000000 -0400 --- tznew/tz-art.htm 2012-11-25 16:38:08.608479600 -0500 *************** *** 415,420 **** --- 415,427 ---- </a>. (Mark Brader, 2009-10-02) </li> <li> + In the "Run by the Monkeys" episode of "Da Vinci's Inquest" + (first broadcast 2002-11-17), + a witness in a five-year-old fire case realizes they may not have set + their clock back when daylight saving ended on the day of the fire, + introducing the possibility of an hour when arson might have occurred. + </li> + <li> In "The Todd Couple" episode of "Outsourced" (first aired 2011-02-10), Manmeet sets up teledates for 6:00 and 9:00; since one is with a New Yorker and the other with a San Franciscan,

1 0

Rerun of proposed localtime.c changes
by Arthur David Olson Nov. 25, 2012

Nov. 25, 2012

Now that silly season seems to be over, two reruns. First, changes to localtime.c (both attached and below, with tabs mangled). These are designed to address two issues noted earlier this year by Doug Bailey: ensuring that "tzname" values are set, and getting proper behavior when the software is being run on an unsigned-time_t system but is using data files generated on a signed-time_t system. These changes have been updated to be relative to tz2012j. --ado *** tz2012j/localtime.c 2012-10-26 20:37:42.000000000 -0400 --- tznew/localtime.c 2012-11-25 16:11:23.833188100 -0500 *************** *** 271,276 **** --- 271,281 ---- /* ** And to get the latest zone names into tzname. . . */ + for (i = 0; i < sp->typecnt; ++i) { + register const struct ttinfo * const ttisp = &sp->ttis[i]; + + tzname[ttisp->tt_isdst] = &sp->chars[ttisp->tt_abbrind]; + } for (i = 0; i < sp->timecnt; ++i) { register const struct ttinfo * const ttisp = &sp->ttis[ *************** *** 479,498 **** ** signed time_t system but using a data file with ** unsigned values (or vice versa). */ ! for (i = 0; i < sp->timecnt - 2; ++i) ! if (sp->ats[i] > sp->ats[i + 1]) { ! ++i; if (TYPE_SIGNED(time_t)) { /* ** Ignore the end (easy). */ ! sp->timecnt = i; } else { /* ** Ignore the beginning (harder). */ register int j; for (j = 0; j + i < sp->timecnt; ++j) { sp->ats[j] = sp->ats[j + i]; sp->types[j] = sp->types[j + i]; --- 484,514 ---- ** signed time_t system but using a data file with ** unsigned values (or vice versa). */ ! for (i = 0; i < sp->timecnt; ++i) ! if ((i < sp->timecnt - 1 && ! sp->ats[i] > sp->ats[i + 1]) || ! (i == sp->timecnt - 1 && !TYPE_SIGNED(time_t) && ! sp->ats[i] > ! ((stored == 4) ? INT32_MAX : INT64_MAX))) { if (TYPE_SIGNED(time_t)) { /* ** Ignore the end (easy). */ ! sp->timecnt = i + 1; } else { /* ** Ignore the beginning (harder). */ register int j; + /* + ** Keep the record right before the + ** epoch boundary, + ** but tweak it so that it starts + ** right with the epoch + ** (thanks to Doug Bailey). + */ + sp->ats[i] = 0; for (j = 0; j + i < sp->timecnt; ++j) { sp->ats[j] = sp->ats[j + i]; sp->types[j] = sp->types[j + i];

1 0