- tz - lists.iana.org

Troll rule parsing issue
by David Braverman May 4, 2014

May 4, 2014

Hi, First, we don't use zic; we use our own .NET tzinfo parser. I would expect zic doesn't have the problem we've encountered. The most recent change of the Antarctica file (2014-03-21, commit 6285081) introduced three leading spaces before the three leading tab characters at line 267 (second line of the Antarctica/Troll zone definition). Because of the data before the first tab character, our system has an off-by-one error parsing the rest of the line, and doesn't recognize it as a zone definition line. What is the rule regarding continuation lines on zone definitions? We split lines into arrays by tab, which fails in this case where there are leading spaces before the first tab. Since this works in all other cases, is this an error in the data? Or should we follow a different semantic rule? Thanks. David Braverman Chicago

2 3

zic changes (1/2)
by Arthur David Olson May 1, 2014

May 1, 2014

A possibility mentioned last year at the time of the Macquarie fix: here's a more general fix for zic.c. For clarity, it comes in two pieces. This first piece simply rolls back the Macquarie-specific changes to zic.c; it's both attached and appears in mangled form below. These changes are relative to the git repository version. @dashdashado 1.1 2838 lines 1.2 2805 lines *** /tmp/,azic.c 2014-05-01 01:51:26.531315400 -0400 --- /tmp/,bzic.c 2014-05-01 01:51:26.640515600 -0400 *************** *** 1480,1490 **** fromi = 0; while (fromi < timecnt && attypes[fromi].at < min_time) ++fromi; ! /* ! ** Remember that type 0 is reserved. ! */ ! if (isdsts[1] == 0) ! while (fromi < timecnt && attypes[fromi].type == 1) ++fromi; /* handled by default rule */ for ( ; fromi < timecnt; ++fromi) { if (toi != 0 && ((attypes[fromi].at + --- 1480,1487 ---- fromi = 0; while (fromi < timecnt && attypes[fromi].at < min_time) ++fromi; ! if (isdsts[0] == 0) ! while (fromi < timecnt && attypes[fromi].type == 0) ++fromi; /* handled by default rule */ for ( ; fromi < timecnt; ++fromi) { if (toi != 0 && ((attypes[fromi].at + *************** *** 1589,1599 **** } thistimelim = thistimei + thistimecnt; thisleaplim = thisleapi + thisleapcnt; ! /* ! ** Remember that type 0 is reserved. ! */ ! writetype[0] = FALSE; ! for (i = 1; i < typecnt; ++i) writetype[i] = thistimecnt == timecnt; if (thistimecnt == 0) { /* --- 1586,1592 ---- } thistimelim = thistimei + thistimecnt; thisleaplim = thisleapi + thisleapcnt; ! for (i = 0; i < typecnt; ++i) writetype[i] = thistimecnt == timecnt; if (thistimecnt == 0) { /* *************** *** 1609,1619 **** /* ** For America/Godthab and Antarctica/Palmer */ - /* - ** Remember that type 0 is reserved. - */ if (thistimei == 0) ! writetype[1] = TRUE; } #ifndef LEAVE_SOME_PRE_2011_SYSTEMS_IN_THE_LURCH /* --- 1602,1609 ---- /* ** For America/Godthab and Antarctica/Palmer */ if (thistimei == 0) ! writetype[0] = TRUE; } #ifndef LEAVE_SOME_PRE_2011_SYSTEMS_IN_THE_LURCH /* *************** *** 1663,1688 **** } #endif /* !defined LEAVE_SOME_PRE_2011_SYSTEMS_IN_THE_LURCH */ thistypecnt = 0; - /* - ** Potentially, set type 0 to that of lowest-valued time. - */ - if (thistimei > 0) { - for (i = 1; i < typecnt; ++i) - if (writetype[i] && !isdsts[i]) - break; - if (i != types[thistimei - 1]) { - i = types[thistimei - 1]; - gmtoffs[0] = gmtoffs[i]; - isdsts[0] = isdsts[i]; - ttisstds[0] = ttisstds[i]; - ttisgmts[0] = ttisgmts[i]; - abbrinds[0] = abbrinds[i]; - writetype[0] = TRUE; - writetype[i] = FALSE; - } - } for (i = 0; i < typecnt; ++i) ! typemap[i] = writetype[i] ? thistypecnt++ : 0; for (i = 0; i < sizeof indmap / sizeof indmap[0]; ++i) indmap[i] = -1; thischarcnt = 0; --- 1653,1660 ---- } #endif /* !defined LEAVE_SOME_PRE_2011_SYSTEMS_IN_THE_LURCH */ thistypecnt = 0; for (i = 0; i < typecnt; ++i) ! typemap[i] = writetype[i] ? thistypecnt++ : -1; for (i = 0; i < sizeof indmap / sizeof indmap[0]; ++i) indmap[i] = -1; thischarcnt = 0; *************** *** 2105,2115 **** updateminmax(leapminyear); updateminmax(leapmaxyear + (leapmaxyear < ZIC_MAX)); } - /* - ** Reserve type 0. - */ - gmtoffs[0] = isdsts[0] = ttisstds[0] = ttisgmts[0] = abbrinds[0] = -1; - typecnt = 1; for (i = 0; i < zonecount; ++i) { zp = &zpfirst[i]; if (i < zonecount - 1) --- 2077,2082 ----

1 0

re : Time zones in Ukraine
by Nickolay Olshevsky April 19, 2014

April 19, 2014

Thank you guys for prompt answer, now I got it. Will at least go and read what was that Rutenia :) The another idea would be to keep somewhere list of active timezones along with tz database, but I understand that it would be almost impossible to add corresponding APIs everywhere. -- Best regards, Nickolay Olshevsky

8 15

Tennessee time (was Web sites using recent versions of the tz database)
by Arthur David Olson April 15, 2014

April 15, 2014

On Wed, Feb 19, 2014 at 7:49 PM, Zoidsoft <zoidsoft(a)gmail.com> wrote: > Tennessee has proposed permanent daylight time: > > > http://www.chattanoogan.com/2014/2/18/269932/Legislation-Making-Daylight-Sa… > If this moves forward at the state level, things could get interesting. The US Uniform Time Act lets states choose whether or not to make the DST switch, but may not allow for permanent DST (which would, in effect, be a time zone switch). "Full text - Daylight Saving Time - United States Law - 15 USC 6(IX)(260-7)" http://www.webexhibits.org/daylightsaving/usc.html A reminder: I am not a lawyer. @dashdashado

4 3

Time zones in Ukraine
by Nickolay Olshevsky April 15, 2014

April 15, 2014

Hi. I am aware about tz database for a while, and today, during FreeBSD installation found out that it still propose ancient and non-usable zones like Ruthenia, Zaporozhye or Crimea for time zone in Ukraine, while for last years only one time zone exists at the whole Ukraine area (except Crimea for now). So, it would be nice to remove all of them except Ukraine/Kyiv, or is this not possible due to historical reasons (to keep history of all those time zones)? Also, the other issue is that in Ukrainian language correct spelling is Kyiv, not Kiev (russian pronunciation). It would be quite logical to change default zone to Europe/Kyiv. Thanks. -- Best regards, Nickolay Olshevsky

3 2

US feds & Y2K
by Arthur David Olson April 11, 2014

April 11, 2014

In line with this morning's proposed 1998 change: "The Defense Department, General Services Administration and NASA are proposing that a 1997 [Y2K] acquisition rule--and all related clauses--be deleted from federal regulations." http://www.bizjournals.com/washington/blog/fedbiz_daily/2014/03/its-2014-is… @dashdashado

3 2

tiscal url not working
by Osko, Galatea April 4, 2014

April 4, 2014

Hi all, http://home.tiscali.nl/~t876506/TZworld.html#sam Can you please advise on the replacing link for time zones? Thank you! Galatea Osko Morgan Stanley | Enterprise Data & Services Lechner Odon fasor 8 | Floor 07 Budapest, 1095 Phone: +36 1 881-3530 Galatea.Osko(a)morganstanley.com<mailto:Galatea.Osko@morganstanley.com> Be carbon conscious. Please consider our environment before printing this email. ________________________________ NOTICE: Morgan Stanley is not acting as a municipal advisor and the opinions or views contained herein are not intended to be, and do not constitute, advice within the meaning of Section 975 of the Dodd-Frank Wall Street Reform and Consumer Protection Act. If you have received this communication in error, please destroy all electronic and paper copies and notify the sender immediately. Mistransmission is not intended to waive confidentiality or privilege. Morgan Stanley reserves the right, to the extent permitted under applicable law, to monitor electronic communications. This message is subject to terms available at the following link: http://www.morganstanley.com/disclaimers If you cannot access these links, please notify us by reply message and we will send the contents to you. By messaging with Morgan Stanley you consent to the foregoing.

2 1

GMT Abolished
by Matt Johnson April 1, 2014

April 1, 2014

http://www.timeanddate.com/news/time/paris-meridian-gmt-obsolete.html Happy April 1st. ;-)

1 0

zdump convenience options
by Arthur David Olson April 1, 2014

April 1, 2014

Attached are changes for two zdump convenience options; they also appear in mangled form below. @dashdashado diff -rc tz2014braw/zdump.8 tz2014bredone/zdump.8 *** tz2014braw/zdump.8 2014-03-26 16:33:56.432625200 -0400 --- tz2014bredone/zdump.8 2014-03-26 16:35:28.051586100 -0400 *************** *** 13,19 **** .B \-c [loyear,]hiyear ] [ .B \-t ! [lotime,]hitime ] [ zonename ... ] .SH DESCRIPTION .I Zdump prints the current time in each --- 13,23 ---- .B \-c [loyear,]hiyear ] [ .B \-t ! [lotime,]hitime ] [ ! .B \-\-pre ! ] [ ! .B \-\-ado ! ] [ zonename ... ] .SH DESCRIPTION .I Zdump prints the current time in each *************** *** 56,61 **** --- 60,71 ---- .BI "\-t " [lotime,]hitime Cut off verbose output at the start of the given time(s), given in decimal seconds since 1970-01-01 00:00:00 UTC. + .TP + .BI "\-\-pre" + Limit output to pre-A.D. only; equivalent to \-Vc\-1 + .TP + .BI "\-\-ado" + Limit output to A.D. only; equivalent to \-Vc1,2500 .SH LIMITATIONS Time discontinuities are found by sampling the results returned by localtime at twelve-hour intervals. diff -rc tz2014braw/zdump.c tz2014bredone/zdump.c *** tz2014braw/zdump.c 2014-03-26 16:33:56.432625200 -0400 --- tz2014bredone/zdump.c 2014-03-26 16:37:38.748615700 -0400 *************** *** 304,310 **** usage(FILE * const stream, const int status) { (void) fprintf(stream, ! _("%s: usage: %s [--version] [--help] [-{vV}] [-{ct} [lo,]hi] zonename ...\n" "\n" "Report bugs to %s.\n"), progname, progname, REPORT_BUGS_TO); --- 304,310 ---- usage(FILE * const stream, const int status) { (void) fprintf(stream, ! _("%s: usage: %s [--version] [--help] [--pre] [--ado] [-{vV}] [-{ct} [lo,]hi] zonename ...\n" "\n" "Report bugs to %s.\n"), progname, progname, REPORT_BUGS_TO); *************** *** 346,351 **** --- 346,355 ---- exit(EXIT_SUCCESS); } else if (strcmp(argv[i], "--help") == 0) { usage(stdout, EXIT_SUCCESS); + } else if (strcmp(argv[i], "--pre") == 0) { + argv[i] = "-Vc-1"; + } else if (strcmp(argv[i], "--ado") == 0) { + argv[i] = "-Vc1,2500", } vflag = Vflag = 0; cutarg = cuttimes = NULL;

4 4

Missing link to America/Montreal
by Paul_Koning＠Dell.com April 1, 2014

April 1, 2014

Apologies for not catching this sooner: In 2013, between 2013e and 2013i, America/Montreal was eliminated. But there is not, as is usually done, a link in the “backward” file. Some others I looked at, like Antarctica/South_Pole, did get an entry in backward. Is the an oversight or was it intentional? paul

2 4

DST on neolithic clocks
by Zefram April 1, 2014

April 1, 2014

http://www.ntsouthwest.co.uk/2014/04/putting-the-clock-forward-at-avebury-s… "Obviously Stone Age man didn't have daylight saving, so twice a year we have to move one of the stones." said Hilary Makins, National Trust Head Ranger. -zefram

1 0

Time zones in the news
by Arthur David Olson April 1, 2014

April 1, 2014

"The surprising political importance of Crimea's shift to Moscow time" http://www.washingtonpost.com/blogs/worldviews/wp/2014/03/31/the-surprising… @dashdashado

3 2

Re: [tz] Crimea switches to Moscow time at 22:00 local time March 29, 2014
by Paul Eggert March 31, 2014

March 31, 2014

Anatoly Zaytsev wrote: > It was only symbolic act, not official clock shift. Yes, thanks, that's the simplest interpretation. I've reverted the most recent change to the experimental repository, so the Crimean data has gone back to that of 2014b.

2 2

Crimea to switch to Moscow Time as of March 30, 2014
by Alexander Krivenyshev March 30, 2014

March 30, 2014

According to the news, Republic of Crimea (Simferopol, Sevastopol, Kerch, Yalta, Yevpatoriya) will change its clock 2 hours forward (to the Moscow time) on March 30, 2014. Crimea to switch to Moscow Time as of March 30 http://voiceofrussia.com/news/2014_03_17/Crimea-to-switch-to-Moscow-Time-as- of-March-30-8334/ or http://www.worldtimezone.com/dst_news/dst_news_crimea01.html Alexander Krivenyshev, http://www.worldtimezone.com

7 13

Asia rules change
by Oleksii Nochovnyi March 28, 2014

March 28, 2014

Hi there! I'm agree with this comment in asia rules file: # From Phil Pizzey (2009-04-02): # ...I think I may have spotted an error in the timezone data for # Jordan. # The current (2009d) asia file shows Jordan going to daylight # saving # time on the last Thursday in March. # # Rule Jordan 2000 max - Mar lastThu 0:00s 1:00 S # # However timeanddate.com, which I usually find reliable, shows Jordan # going to daylight saving time on the last Friday in March since 2002. # Please see # <a href="http://www.timeanddate.com/worldclock/timezone.html?n=11"> # http://www.timeanddate.com/worldclock/timezone.html?n=11 # </a> It's real that Jordan makes transition to DST on last Friday of march. For this reason I've changed 2 rules Rule Jordan 2000 2001 - Mar lastThu 0:00s 1:00 S Rule Jordan 2014 max - Mar lastThu 24:00 1:00 S To Rule Jordan 2000 2001 - Mar lastFri 0:00s 1:00 S Rule Jordan 2014 max - Mar lastFri 24:00 1:00 S I'va attached my copy of changed file. Best regards, Oleksii Nochovnyi Software Engineer [Description: Description: Description: Description: Description: Description: Description: Description: Description: http://c.softserveinc.com/mail/signature-logo.gif] 22 Karl Marks av., Dnipropetrovs'k 49000, Ukraine Tel: +380-56-270-2272 x 3776 Tel: +380-32-240-9090 x 3776 Fax: +380-32-240-9080 website<http://www.softserveinc.com/> | onoch(a)softserveinc.com<mailto:onoch@softserveinc.com> [Description: Description: Description: Description: Description: Description: Description: Description: Description: http://c.softserveinc.com/mail/linkedin.jpg]<http://www.linkedin.com/company/softserve> [Description: Description: Description: Description: Description: Description: Description: Description: Description: http://c.softserveinc.com/mail/facebook.jpg]<http://www.facebook.com/pages/SoftServe/336445732845> [Description: Description: Description: Description: Description: Description: Description: Description: Description: http://c.softserveinc.com/mail/twitter.jpg]<http://twitter.com/SoftServeInc>

2 1

Re: [tz] Ukraine 1990
by Bogdan Krusiński March 28, 2014

March 28, 2014

Hello, http://search.ligazakon.ua/l_doc2.nsf/link1/T217600.html excuse us for the earlier confusion, the text from 11 june 1990 we sent was reotroactively decreed in 1992 to remove the words "Moscow time minus 1 hour". The version we sent was version after retroactive edition of 1992 year after decree ordering to remove these words was issued. The original Original text from June of 1990 was: "1. Установити з 1 липня 1990 року на території Української РСР час другого часового поясу без додання однієї години, московський час мінус одна година." "1. Introduction from 1st of July 1990 on territory of Ukrainian SSR time zone of two hours without summer time, Moscow time minus 1 hour". with best regards Bogdan Krusinski -----Original Message----- From: Bogdan Krusiński Sent: Sunday, March 16, 2014 12:47 AM To: 'tz(a)iana.org' Subject: Ukraine 1990 Hello, the contenst of decree at http://search.ligazakon.ua/l_doc2.nsf/link1/T001500.html contain only one point: "1. Установити з 1 липня 1990 року на території Української РСР час другого часового поясу без додання однієї години." "1. Intorduction from 1st of July 1990 on territory of Ukrainian SSR time of two hours without addition of one hour". I'm a bit disturbed because I was directed by astro.com to these archives where it is translated as: "Set on 1 July 1990 in the Ukrainian SSR, the second time zone with the addition of one hour." "without" is not "with". Pozdrawiam serdecznie Bogdan Krusiński

2 1

Cygwin
by Arthur David Olson March 27, 2014

March 27, 2014

Changes to private.h and zdump.c, for the benefit of Cygwin setups which lack glibc but have stdint.h; both attached and tab-mangled (below) @dashdashado *** tz2014braw/private.h 2014-03-20 17:34:32.000000000 -0400 --- tz2014bcooked/private.h 2014-03-25 13:41:48.769742400 -0400 *************** *** 119,127 **** --- 119,131 ---- ** (glibc 2.1 and later have stdint.h, even with pre-C99 compilers.) */ #ifndef HAVE_STDINT_H + #ifdef __CYGWIN__ + #define HAVE_STDINT_H 1 + #else #define HAVE_STDINT_H \ (199901 <= __STDC_VERSION__ || \ 2 < (__GLIBC__ + (0 < __GLIBC_MINOR__))) + #endif #endif /* !defined HAVE_STDINT_H */ #if HAVE_STDINT_H *** tz2014braw/zdump.c 2013-10-20 19:20:23.000000000 -0400 --- tz2014bcooked/zdump.c 2014-03-25 13:46:25.124227800 -0400 *************** *** 35,43 **** --- 35,47 ---- */ #ifndef HAVE_STDINT_H + #ifdef __CYGWIN__ + #define HAVE_STDINT_H 1 + #else # define HAVE_STDINT_H \ (199901 <= __STDC_VERSION__ || 2 < (__GLIBC__ + (0 < __GLIBC_MINOR__))) #endif + #endif #if HAVE_STDINT_H # include "stdint.h" #endif

2 1

"make clean" leaves "libtz.a" behind
by Arthur David Olson March 26, 2014

March 26, 2014

Doing a "make clean" does not remove "libtz.a"--a fix is attached (and appears in mangled form below). @dashdashado *** tz2014braw/Makefile 2014-03-25 00:30:17.000000000 -0400 --- tz2014bcooked/Makefile 2014-03-26 18:53:56.650329500 -0400 *************** *** 443,449 **** clean_misc: rm -f core *.o *.out \ ! date tzselect version.h zdump zic yearistype clean: clean_misc rm -fr tzpublic --- 443,449 ---- clean_misc: rm -f core *.o *.out \ ! date tzselect version.h zdump zic yearistype libtz.a clean: clean_misc rm -fr tzpublic

1 0

tz changes linux debian caused sync diff
by John D. Hendrickson and Sara Darnell March 26, 2014

March 26, 2014

hello first background the Question is last i just spent an hour trying to edit America/New_York only to find US had been changed my two hosts disagreed by 1 hr and daylight savings time but not UTC prev US section used "max". apparently (i dont' have all tz revisions) someone change the last US rule this changes assumptions made in all rules of states using US in their Rules meaning one host assumes NY follows US from (19xx) forward, so does the other: but since US chaned they are an hour off -------------------------------------- Question: why was that a good idea ? and what if new Rules file becomes incompat with my libc and i cannot zic/compile and load "new localtime assumptions" ?? it seems rediculous however i'm guessing there is a good answer

3 2

Re: [tz] confirmation of historical DST changes in Ukraine
by David Cochrane March 26, 2014

March 26, 2014

Sorry, I did not post this to the correct thread. My apologies. David Cochrane ----- Original Message ----- From: "David Cochrane" <davidc(a)astrosoftware.com> To: <tz(a)iana.org> Sent: Wednesday, March 26, 2014 8:35 AM Subject: confirmation of historical DST changes in Ukraine > Gary How wrote: > >> The question for tz >> database is whether the switch to Urumqi Time in Xinjiang is on 1975 >> (when >> it was first announced) or 1986 (when it was more commonly implemented). > > Just a confirmation that Urumqi time was implemented in Urumqi on 1 Feb > 1986: > > http://content.time.com/time/magazine/article/0,9171,960684,00.html > > I did not subscribe or log in to the site but from the part of the article > on this page, it suggests that the article will confirm the Feb 1, 1986 > date > for the date when people began observing Urumqi time (even if a regulation > had already been passed in 1975). > > I am fairly new to this group. I also have some confirmation of the DST > changes in the Ukraine from newspaper articles in Russian that confirm > that the laws passed were put into practice. I can send these as well if > this is useful information. I can also gradually submit other historical > research information for countries that I have which I believe is not in > the TZ database files. > > David Cochrane > > > ----- Original Message ----- > From: "Gary How" <hytar(a)outlook.com> > To: <tz(a)iana.org> > Sent: Monday, March 24, 2014 8:26 AM > Subject: Re: [tz] China time zones 1949 - 1980: appeal to speakers > ofMandarin > > >> Alois Treindl <alois <at> astro.ch> writes: >> >>> >>> This seems to be a relevant source: >>> Guo, Qingsheng (2003) "Beijing Time at the Beginning of PRC", China >>> Historical Materials of Science and Technology 24(1) >>> >> >> Hi Alois and Paul, I purchased the journal article (finally after days of >> figuring out which service allows payment from outside China). From the >> points Alois raised in his recent email, I try to clarify by using that >> article, quoting/paraphrasing its English translation. >> >>> >>> Various sources claim that this unified country-wide timezone was >>> already introduced in 1949 or early 1950 >>> >> >> This particular source says the first meeting of the Chinese People's >> Political Consultative Conference passed the resolution of "making >> Beiping >> the capital, changing Beiping to Beijing." That was 27 September 1949. On >> the same day, Beiping Xinhua Radio was renamed with Beijing at the >> beginning. The next day, that station started using Beijing in its >> timekeeping call. The earliest written instance of "Beijing Time" found >> by >> the author was on 7 October 1949, through a newspaper posting from Xi'an >> People's Radio. That said, the author inferred that Beijing Time was >> established on 27 September 1949. >> >>> >>> It seems to me that the only source claiming the continuation of 5 time >>> zones for China is the International Atlas by Shanks and Pottenger. The >>> overall work of these authors is extremely valuable, but they do not >>> give a source for their China information. >>> >>> Paul Eckert says in tz/asia file: >>> # From Paul Eggert (2008-06-30): >>> # There seems to be a good chance China switched to a single time zone >>> in 1949 >>> # rather than in 1980 as Shanks & Pottenger have it, but we don't have a >>> # reliable documentary source saying so yet, so for now we still go with >>> # Shanks & Pottenger. >>> >> >> For time zones in the rest of China after that, Qing-sheng Guo has >> another >> journal article in 2001 that discussed these in detail, entitled "A Study >> on >> the Standard Time Changes for the Past 100 Years in China," from China >> Historical Materials of Science and Technology 22(3). >> >> Earlier I mentioned Xi'an radio station referencing Beijing Time. Another >> written source for this was from the Xi'an People's Government dated 2 >> November 1949, announcing to stop using Longshu Time (aka Kansu-Szechuan >> Time, GMT+7) and change to Beijing Time from 3 November 1949 onwards. >> >>> 10/16/2010 by Jonathan.Hassid <at> uts.edu.au who writes: >>> "The government in Chengdu (capital of Sichuan province) announced the >>> switch (from "Shulong" (Gansu/Sichuan) time) to Beijing time on 27 Dec. >>> 1949. >> >> As for Chengdu, the date 27 December 1949 is stated in the article as >> "being >> liberated" during the Communist Revolution. The switch to Beijing Time >> "was >> announced ten days or so after that." The author referenced a notice from >> the Chengdu Garrison Command dated 6 January 1950, to request citizens to >> adjust their watches through daily sirens at noon Beijing Time. For most >> other parts of China, they "have used standard time of 120° longitude >> around >> the year 1950 to 1953." He dubbed it the "chaotic period", since no >> government agency announced and enforced this rule of time, instead the >> cities synced to the unified time at their pace. >> >> In the 2003 article, Guo obtained two independent sources that verified >> the >> Beijing Time of 1949 was using apparent/true solar time (GMT+7:56) and >> not >> mean solar time (7:46) or standard time of 120° longitude (8:00). >> However, >> he had doubts about that, since he thought apparent solar time is a step >> back to time measurements in the early 20th century, and standard time >> signals can be obtained easily from overseas stations at the time. The >> 1954 >> Chinese Astronomical Almanac mentioned that "except Xinjiang and Tibet, >> the >> whole country uses standard time of 120° longitude." He has yet to find >> out >> exactly when did Beijing Time switch back to GMT+8 between 1949 and 1954 >> in >> the article. I will try to look for later articles that reference this >> work. >> >> For Tibet, the standard time of 90° longitude was used prior to March >> 1959, >> also known as Lhasa Time. After the Tibetan Uprising that month and the >> Panchen Lama took over, the author surmised that the transition from >> Lhasa >> Time to Beijing Time happened at the second half of 1959. He tried to >> look >> for "first-hand accounts" on this, but found none so far. On the other >> hand, >> Guo said time zone changes for Xinjiang is relatively well documented. >> >> The Revolutionary Committee of Xinjiang and Xinjiang military notified on >> 9 >> June 1969, that starting from 1 July 1969, Beijing Time would be put into >> effect for the entire Xinjiang province. On 7 April 1975, the same >> committee >> put out a notice to be enforced on 1 May, that except military, >> rail-road, >> civil aviation, postal and telecommunication services, the schedules for >> government, factories, mines, businesses and schools would use Urumqi >> Time. >> Due to poor implementation of this notice, they again informed on 10 June >> 1977 that "schedules for work, meeting etc. should only use Urumqi Time >> for >> the whole province." >> >> In the end, the Xinjiang People's Government decided that starting 1 >> February 1986, the entire province would use Urumqi Time. Whenever >> Beijing >> Time is used, they should be stated explicitly. According to Guo, this >> particular rule is more effectively put into practice. The question for >> tz >> database is whether the switch to Urumqi Time in Xinjiang is on 1975 >> (when >> it was first announced) or 1986 (when it was more commonly implemented). >> >> To conclude, all of China currently is in the UTC+8:00 time zone except >> for >> Xinjiang province, according to the articles. The central Chinese >> government >> still did not made a law to enforce the unified time zone, although it >> was >> widely accepted that China has one official time zone. Whether or not the >> locals all around China follow that standard time, we do not know for >> sure. >> >> The 2001 article by Guo also has details about Chinese time zones from >> the >> 1900s to 1949. We can start a new thread on this if necessary. > > > __________ Information from ESET NOD32 Antivirus, version of virus > signature database 9596 (20140326) __________ > > The message was checked by ESET NOD32 Antivirus. > > http://www.eset.com > > > > > __________ Information from ESET NOD32 Antivirus, version of virus > signature database 9597 (20140326) __________ > > The message was checked by ESET NOD32 Antivirus. > > http://www.eset.com > > > __________ Information from ESET NOD32 Antivirus, version of virus signature database 9597 (20140326) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com

1 0

morocco change in 12 days
by Sebastien WILLEMIJNS March 26, 2014

March 26, 2014

Hello, http://www.afriquinfos.com/articles/2014/3/18/maroc-heure-dete-avancez-tous… http://www.aujourdhui.ma/une/actualite/l-heure-d-ete-a-compter-de-dimanche-… maybe this info is already known...

5 4

Troll in the long term
by Arthur David Olson March 25, 2014

March 25, 2014

An interesting long-term exercise: extend (once again) the zic-produced POSIX-like time zone string format to cover Troll. (Have the in-place extensions been proposed to the POSIX governing body for its standard?) @dashdashado

4 3

Troll and zic warnings
by Arthur David Olson March 25, 2014

March 25, 2014

It may be useful to have zic warn when producing a binary with more than 1200 transition times; one possibility is attached (and appears below with tabs mangled). To make room for the new code, a warning about pre-1998 versions of zic has been removed.-) @dashdashado *** tz2014braw/zic.c 2014-03-20 23:21:43.000000000 -0400 --- tz2014bcooked/zic.c 2014-03-25 10:19:28.470390300 -0400 *************** *** 962,969 **** error(_("time overflow")); return 0; } - if (noise && hh == HOURSPERDAY && mm == 0 && ss == 0) - warning(_("24:00 not handled by pre-1998 versions of zic")); if (noise && (hh > HOURSPERDAY || (hh == HOURSPERDAY && (mm != 0 || ss != 0)))) warning(_("values over 24 hours not handled by pre-2007 versions of zic")); --- 962,967 ---- *************** *** 1503,1508 **** --- 1501,1508 ---- } timecnt = toi; } + if (noise && timecnt > 1200) + warning(_("pre-2014 clients may mishandle more than 1200 transition times")); /* ** Transfer. */

2 1

[tz-announce] 2014b release of tz code and data available
by Paul Eggert March 25, 2014

March 25, 2014

The 2014b 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 near-future time stamps Crimea switches to Moscow time on 2014-03-30 at 02:00 local time. (Thanks to Alexander Krivenyshev.) Move its zone.tab entry from UA to RU. New entry for Troll station, Antarctica. (Thanks to Paul-Inge Flakstad and Bengt-Inge Larsson.) This is currently an approximation; a better version will require the zic and localtime fixes mentioned below, and the plan is to wait for a while until at least the zic fixes propagate. Changes affecting code 'zic' and 'localtime' no longer reject locations needing four transitions per year for the forseeable future. (Thanks to Andrew Main (Zefram).) Also, 'zic' avoids some unlikely failures due to integer overflow. Changes affecting build procedure 'make check' now detects Rule lines defined but never used. The NZAQ rules, an instance of this problem, have been removed. Changes affecting commentary and documentation Fix Tuesday/Thursday typo in description of time in Israel. (Thanks to Bert Katz via Pavel Kharitonov and Mike Frysinger.) Microsoft Windows 8.1 doesn't support tz database names. (Thanks to Donald MacQueen.) Instead, the Microsoft Windows Store app library supports them. Add comments about Johnston Island time in the 1960s. (Thanks to Lyle McElhaney.) Morocco's 2014 DST start will be as predicted. (Thanks to Sebastien Willemijns.) Here are links to the release files: ftp://ftp.iana.org/tz/releases/tzcode2014b.tar.gz ftp://ftp.iana.org/tz/releases/tzdata2014b.tar.gz The files are also available via HTTP as follows: http://www.iana.org/time-zones/repository/releases/tzcode2014b.tar.gz http://www.iana.org/time-zones/repository/releases/tzdata2014b.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. 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 This release corresponds to commit ea08a2f6ef6b2cfe07ea2b3c570e59c9d8e9bd61 dated Mon Mar 24 21:28:50 2014 -0700 and tagged '2014b' in the unofficial github repository at <https://github.com/eggert/tz>. Here are the GPG checksums for the release files: -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.14 (GNU/Linux) iQIcBAABAgAGBQJTMQbFAAoJEO2X6Q5iqn40MmQP/jLFMoyIrHEHptt7gTxOiakP u+U2qhynw/tXQb44I+YgpYw54UPiZ7mGqQ9phGbmjcTsFT6vG9qO61LEMg9Y6nyr wu+qHYyKfqcLednTUFztR3x2aj4HWNVpMENXyoU+ZvVUw/Hd7J2uaNkw3n+zZYqY tZjMAkn7wPLVv2BGQPshkGQB7S5YEVdHcXyeey9mtS1TBCkPadldgSk6afsc7x89 lTiQ5v89dNJPfOqjRbyIBbS6I26XTxOlEQzuHdzWz5p1m1SUqznosEKw5Mnat5qe LNo3HnmwJyXXXrJDsgYja3yH3Ie4Bhs+y1kjJfwrArnQaex9UWmetHEKuJrz5VY1 HZadsNfVoBb4QYyZQiLxr/iqs/ZiTocX6xAdZpHdI5WSoUABfKLTgU67z1UFFVgd qEi335xK3/l6rFAOjwEzqEriugthSWU1SlqGCUAmP6c87gBgFFC+mMW/T1FnmZtn v/ST9L2xmeyS8a1693fnak1fATlTaF2j/JbrhqbhOFTim/k+u6LgXBpSZyuzs80/ gnLjGN5gAD7OhAMkjU1Ty5T3F1cGGev3kGgWX093JXugj4DszwUzzgG/NZniFkQc t+7B56jbxMTdFs+RB0YWfJ34QUbusAkWNprFyftPYMyF9PElKv6ngF+1XVFdq84Z jz7+k6FTz3hkU/Ru2s+4 =+BVZ -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.14 (GNU/Linux) iQIcBAABAgAGBQJTMQbFAAoJEO2X6Q5iqn40o1gQAKrv5uiwH6nkf+vAG6u3P1e+ RXdP+fC0IDOQoJFYf4i6gv1LPZ4A3uzwU9fZ8Fq4ETmCRr8UZmtRkrVTqNchfobV Kkkn3XlX5IlPqirBVL3/L3wVGybj7kfauhWozJuyvQuQCaF58TqNAqfV7joSZLZt 8CwBYf1cnkuHkybLJjiur+s3nZ3nAhKa/6p1MbMJBMpeAWtAqdOWW3C/LIgvrX5n 292hzn+0CILcsESxai6YOYpb3VwsVOilqdyBCos16Ra/qRwKUqhtUh+N+/0HdjUw E+wPh4n3mDVMSwiVi0yiZSMACU/mQmwI0W0lQAyGRtMjpK32R/VrwHUAZRAt/B8G 0vOeGl5xXjuaPl46agkhBVhpUHX2ATLKmuJAwZ9jPUYkspqmT3ttzArXcfekFpeb xd6jlpQiqENeo8aZRSllTxE2zYJg5k6UvZ+NTMElh1AmRuUhh+kJq3SQnuEv2fqZ qEXuUZmdkMfLt3xF6OMDX1Uel/i6GFRfs+Lr7w6PV1HFVTiqZiOB5a1X3hn0dk8M cJQpwyhEfidZASQsKJADhMpUlon6i2O1jBJwyAWrMaCx38a2L6EX9jLPWyPRHze8 v386Rk319AOWupf/G48pJt/LnYiFw1F1AtOct9cpUBDJFoopGuU8O9D3Z49Carsd CknX8ICVszv7uQpCvwO4 =vlee -----END PGP SIGNATURE----- _______________________________________________ tz-announce mailing list tz-announce(a)iana.org https://mm.icann.org/mailman/listinfo/tz-announce

1 0

Macao vs Macau in tzdata2014a/iso3166.tab
by Tomas Klacko March 23, 2014

March 23, 2014

Hi, the tzdata2014a/iso3166.tab lists "MO Macau". It used to be "MO Macao", for instance in tzdata2013d. Looking at: http://www.iso.org/iso/home/standards/country_codes/updates_on_iso_3166.htm it shows "MO Macao" (via the OBP link on page 14). I would like to check, is the "MO Macau" entry in tzdata2014a/iso3166.tab correct? Thank you, Tomas

3 3