- tz - lists.iana.org

Cayman Islands considering DST
by Paul Eggert Oct. 21, 2014

Oct. 21, 2014

The Cayman Islands are considering the use of daylight saving time for the first time. The government is inviting public comment through October 30. Arguments for DST include better synchronization with New York financial markets as well as stimulating tourism. See: Ministry of Financial Services, Commerce & Environment, Cayman Islands Government. Introduction of daylight savings time in the Cayman Islands. 2014-09-15. http://www.dci.gov.ky/pls/portal/url/item/0322D04AF1235B50E0506F0A6F1F5D58

1 1

Fiji DST Oct 26
by Ken Rylander Oct. 21, 2014

Oct. 21, 2014

Hi Paul, There might be an issue with the Fiji DST (Pacific/Fiji), predicted to happen on Oct 26, at 3am. It looks like the Fiji government haven't yet decided on whether to have DST this year, or not. And in that case, on what date it will start. There was recently elections here, and it seems like the Fiji government haven't prioritised any decisions around DST. Taking this into consideration, and also the fact that this future, predicted date was introduced by the TZDB, would it be possible to get a tzdata version, where the DST for 2014 is removed? *Ken Rylander**|*Solution Development and BI Manager - Digicel Pacific *|*** *Digicel (Fiji) Ltd****|*P.O.Box 13811, Suva, Fiji *|*Ground Floor, Kadavu House, Victoria Parade, Suva, Fiji *|* *Mobile*(679) 701 5353***| **Fax*(679) 331 0201 *| *_ken.rylander(a)digicelgroup.com <mailto:ken.rylander@digicelgroup.com>_*| **www.digicelpacific.com <http://www.digicelpacific.com/>*

13 31

Fiji DST, starts 2nd November
by "" Oct. 20, 2014

Oct. 20, 2014

DAYLIGHT-SAVING-STARTS-ON-SUNDAY,-NOVEMBER-2ND.aspx <http://www.fiji.gov.fj/Media-Center/Press-Releases/DAYLIGHT-SAVING-STARTS-O…>

1 0

more changes (and a bug fix)
by christos＠zoulas.com Oct. 19, 2014

Oct. 19, 2014

Hi, Most of these changes make sure that errno is always set appropriately when the time functions fail. The bug fix below that when lclptr is allocated, is not zeroed and the result from zoneinit() was not checked. If zoneinit failed, then lclptr would contain garbage, and settzname() would coredump because it assumed that the lclptr contents were sane. christos --- localtime.c.orig 2014-10-07 16:20:32.000000000 -0400 +++ localtime.c 2014-10-16 14:10:03.000000000 -0400 @@ -690,17 +690,23 @@ register char c; register int num; - if (strp == NULL || !is_digit(c = *strp)) + if (strp == NULL || !is_digit(c = *strp)) { + errno = EINVAL; return NULL; + } num = 0; do { num = num * 10 + (c - '0'); - if (num > max) + if (num > max) { + errno = ERANGE; return NULL; /* illegal value */ + } c = *++strp; } while (is_digit(c)); - if (num < min) + if (num < min) { + errno = ERANGE; return NULL; /* illegal value */ + } *nump = num; return strp; } @@ -1202,14 +1208,20 @@ ? lcl_is_set < 0 : 0 < lcl_is_set && strcmp(lcl_TZname, name) == 0) return; - if (0 < lcl) - strcpy(lcl_TZname, name); #ifdef ALL_STATE if (! lclptr) lclptr = malloc(sizeof *lclptr); #endif /* defined ALL_STATE */ - zoneinit(lclptr, name); + if (!zoneinit(lclptr, name)) { +#ifdef ALL_STATE + free(lclptr); + lclptr = NULL; +#endif + return; + } settzname(); + if (0 < lcl) + strcpy(lcl_TZname, name); lcl_is_set = lcl; } @@ -1328,8 +1340,10 @@ newt += seconds; else newt -= seconds; if (newt < sp->ats[0] || - newt > sp->ats[sp->timecnt - 1]) - return NULL; /* "cannot happen" */ + newt > sp->ats[sp->timecnt - 1]) { + errno = EINVAL; + return NULL; /* "cannot happen" */ + } result = localsub(sp, &newt, offset, tmp); if (result) { register int_fast64_t newy; @@ -1338,8 +1352,10 @@ if (t < sp->ats[0]) newy -= years; else newy += years; - if (! (INT_MIN <= newy && newy <= INT_MAX)) + if (! (INT_MIN <= newy && newy <= INT_MAX)) { + errno = EOVERFLOW; return NULL; + } result->tm_year = newy; } return result; @@ -1528,13 +1544,13 @@ tdelta = tdays / DAYSPERLYEAR; if (! ((! TYPE_SIGNED(time_t) || INT_MIN <= tdelta) && tdelta <= INT_MAX)) - return NULL; + goto overflow; idelta = tdelta; if (idelta == 0) idelta = (tdays < 0) ? -1 : 1; newy = y; if (increment_overflow(&newy, idelta)) - return NULL; + goto overflow; leapdays = leaps_thru_end_of(newy - 1) - leaps_thru_end_of(y - 1); tdays -= ((time_t) newy - y) * DAYSPERNYEAR; @@ -1563,17 +1579,17 @@ } while (idays < 0) { if (increment_overflow(&y, -1)) - return NULL; + goto overflow; idays += year_lengths[isleap(y)]; } while (idays >= year_lengths[isleap(y)]) { idays -= year_lengths[isleap(y)]; if (increment_overflow(&y, 1)) - return NULL; + goto overflow; } tmp->tm_year = y; if (increment_overflow(&tmp->tm_year, -TM_YEAR_BASE)) - return NULL; + goto overflow; tmp->tm_yday = idays; /* ** The "extra" mods below avoid overflow problems. @@ -1604,6 +1620,8 @@ tmp->TM_GMTOFF = offset; #endif /* defined TM_GMTOFF */ return tmp; +overflow: + return NULL; } char * @@ -1753,20 +1771,21 @@ if (do_norm_secs) { if (normalize_overflow(&yourtm.tm_min, &yourtm.tm_sec, SECSPERMIN)) - return WRONG; + goto overflow; } if (normalize_overflow(&yourtm.tm_hour, &yourtm.tm_min, MINSPERHOUR)) - return WRONG; + goto overflow; if (normalize_overflow(&yourtm.tm_mday, &yourtm.tm_hour, HOURSPERDAY)) - return WRONG; + goto overflow; y = yourtm.tm_year; if (normalize_overflow32(&y, &yourtm.tm_mon, MONSPERYEAR)) - return WRONG; + goto overflow; /* ** Turn y into an actual year number for now. ** It is converted back to an offset from TM_YEAR_BASE later. */ if (increment_overflow32(&y, TM_YEAR_BASE)) + goto overflow; return WRONG; while (yourtm.tm_mday <= 0) { if (increment_overflow32(&y, -1)) @@ -1792,9 +1811,9 @@ } } if (increment_overflow32(&y, -TM_YEAR_BASE)) - return WRONG; + goto overflow; if (! (INT_MIN <= y && y <= INT_MAX)) - return WRONG; + goto overflow; yourtm.tm_year = y; if (yourtm.tm_sec >= 0 && yourtm.tm_sec < SECSPERMIN) saved_seconds = 0; @@ -1844,17 +1863,17 @@ if (dir != 0) { if (t == lo) { if (t == time_t_max) - return WRONG; + goto overflow; ++t; ++lo; } else if (t == hi) { if (t == time_t_min) - return WRONG; + goto overflow; --t; --hi; } if (lo > hi) - return WRONG; + goto invalid; if (dir > 0) hi = t; else lo = t; @@ -1898,7 +1917,7 @@ ** gets checked. */ if (sp == NULL) - return WRONG; + goto invalid; for (i = sp->typecnt - 1; i >= 0; --i) { if (sp->ttis[i].tt_isdst != yourtm.tm_isdst) continue; @@ -1920,16 +1939,22 @@ goto label; } } - return WRONG; + goto invalid; } label: newt = t + saved_seconds; if ((newt < t) != (saved_seconds < 0)) - return WRONG; + overflow; t = newt; if (funcp(sp, &t, offset, tmp)) *okayp = true; return t; +invalid: + errno = EINVAL; + return WRONG; +overflow: + errno = EOVERFLOW; + return WRONG; } static time_t @@ -1966,6 +1991,7 @@ char seen[TZ_MAX_TYPES]; unsigned char types[TZ_MAX_TYPES]; bool okay; + int save_errno; if (tmp == NULL) { errno = EINVAL; @@ -1973,9 +1999,12 @@ } if (tmp->tm_isdst > 1) tmp->tm_isdst = 1; + save_errno = errno; t = time2(tmp, funcp, sp, offset, &okay); - if (okay) + if (okay) { + errno = save_errno; return t; + } if (tmp->tm_isdst < 0) #ifdef PCTS /* @@ -2013,8 +2042,10 @@ sp->ttis[samei].tt_gmtoff; tmp->tm_isdst = !tmp->tm_isdst; t = time2(tmp, funcp, sp, offset, &okay); - if (okay) + if (okay) { + errno = save_errno; return t; + } tmp->tm_sec -= sp->ttis[otheri].tt_gmtoff - sp->ttis[samei].tt_gmtoff; tmp->tm_isdst = !tmp->tm_isdst;

2 4

Canadian time zones official site link
by Matt Johnson Oct. 18, 2014

Oct. 18, 2014

The TZ source comments for Canada references the INMS, but the link there is dead. Archive.org's last copy was taken in June 2006: https://web.archive.org/web/20060710032930/http://inms-ienm.nrc-cnrc.gc.ca/… It appears that the INMS is/was a division of the NRC, and I've found the current time zone page for the NRC here: http://www.nrc-cnrc.gc.ca/eng/services/time/time_zones.html The pages appear very similar. Please update the comments in the TZ source accordingly. Thanks.

3 3

Re: [tz] Carving shapes
by Marvel, Jim (CPCOE) Oct. 17, 2014

Oct. 17, 2014

Also, how to determine borders for Zabaykalsky Krai From: Marvel, Jim (CPCOE) Sent: Thursday, October 16, 2014 11:22 AM To: 'tz(a)iana.org' Subject: Carving shapes How to determine borders for these new zones? Two zones are added: Asia/Chita (split from Asia/Yakutsk, and also with two hours subtracted) and Asia/Srednekolymsk (split from Asia/Magadan, but with only one hour subtracted). thanks Jim Marvel

4 6

Incorrect timezone offset with current Russian rules - tzdata or glibc bug or normal?
by Andrei Borzenkov Oct. 17, 2014

Oct. 17, 2014

I hit strange problem which looks like a bug and actually caused serious problem due to different interpretation of current timezone offset. Current tzdata correctly - as far as I can tell - defines time today as UTC-4 with summer time inactive: /etc/localtime Sat Mar 26 23:00:00 2011 UT = Sun Mar 27 03:00:00 2011 MSK isdst=0 gmtoff=14400 /etc/localtime Sat Oct 25 21:59:59 2014 UT = Sun Oct 26 01:59:59 2014 MSK isdst=0 gmtoff=14400 /etc/localtime Sat Oct 25 22:00:00 2014 UT = Sun Oct 26 01:00:00 2014 MSK isdst=0 gmtoff=10800 /etc/localtime 9223372036854689407 = NULL /etc/localtime 9223372036854775807 = NULL But the valule of variable "timezone" (man timezone(3)) is set to UTC-3 ... bor@opensuse:~/tmp/sapttzz> ./sapttz Name of local time zone: no info (=TZ) Technical description of local time zone: UTC time +10800 sec Daylight Saving Time at the current/given date is: inaktiv where offset is computed as simply printf(" UTC time %+ld sec\n",- (long int)timezone); if(tm->tm_isdst == 1) printf(" aktiv\n"); else if(tm->tm_isdst == 0) printf(" inaktiv\n"); else printf(" unknown\n"); So basically any application which tries to compute current offset from UTC as based offset (timezone) + dst offset (if isdst) will fail. Or better, two programs running on the same system may have different idea of current time. What puzzles me - if I take previous timezone before last change (before 2014f) the same program displays correct time. But visually nothing has changed ... /etc/localtime Sat Mar 26 22:59:59 2011 UT = Sun Mar 27 01:59:59 2011 MSK isdst=0 gmtoff=10800 /etc/localtime Sat Mar 26 23:00:00 2011 UT = Sun Mar 27 03:00:00 2011 MSK isdst=0 gmtoff=14400 /etc/localtime 9223372036854689407 = NULL /etc/localtime 9223372036854775807 = NULL bor@opensuse:~/tmp/sapttzz> ./sapttz Name of local time zone: no info (=TZ) Technical description of local time zone: UTC time +14400 sec Daylight Saving Time at the current/given date is: inaktiv openSUSE 13.1 with glibc-2.18-4.21.1.x86_64 Any ideas? TIA -andrei

2 1

Utah may drop DST
by Paul Eggert Oct. 17, 2014

Oct. 17, 2014

The Utah Governor's Office of Economic Development, pursuant to a bill passed last year by the state legislature, polled citizens and held public meetings about daylight saving time. They got more than 27,000 responses, including 13,000 written comments totaling 574,000 words. The results: 67% preferred Mountain Standard Time (UTC-7) all year (like Arizona) 18% preferred daylight time (UTC-6) all year, essentially Central Standard Time 15% liked the current spring-forward/fall-back system The main argument of the majority was convenience. The tourism and recreation industries prefer daylight saving, though, and will lobby against switching to MST all year if (as seems likely) an MST bill is introduced in the legislature. My source: Davidson L. Something new under the sun: Utah may dump daylight saving time. Salt Lake Tribune 2014-10-15 http://www.sltrib.com/sltrib/politics/58526154-90/daylight-saving-malley-ut…

10 15

zone.tab deprecation
by Matt Johnson Oct. 16, 2014

Oct. 16, 2014

I understand the differences between zone.tab and zone1970.tab, but why does zone.tab have to be deprecated? Can't we just maintain both files indefinitely? Then developers can choose whichever file makes sense for their scenario. Is there a specific reason for the deprecation? If it is to be dropped at some point - how far out is that, and does it get maintained until then?

2 1

Carving shapes
by Marvel, Jim (CPCOE) Oct. 16, 2014

Oct. 16, 2014

How to determine borders for these new zones? Two zones are added: Asia/Chita (split from Asia/Yakutsk, and also with two hours subtracted) and Asia/Srednekolymsk (split from Asia/Magadan, but with only one hour subtracted). thanks Jim Marvel

1 0

zdump bug in Asia/Singapore
by Tim Parenti Oct. 15, 2014

Oct. 15, 2014

While sorting out some issues for tzdist, I noticed a bug in zdump, which is still present in 2014g. Running zdump on Asia/Singapore for both 1981 and 1982 together produces the expected transition from UTC+7:30 to UTC+8 at the boundary between those years: $ ./zdump.exe -vc 1981,1983 Asia/Singapore Asia/Singapore -9223372036854775808 = NULL Asia/Singapore -9223372036854689408 = NULL Asia/Singapore Thu Dec 31 16:29:59 1981 UT = Thu Dec 31 23:59:59 1981 SGT isdst=0 Asia/Singapore Thu Dec 31 16:30:00 1981 UT = Fri Jan 1 00:30:00 1982 SGT isdst=0 Asia/Singapore 9223372036854689407 = NULL Asia/Singapore 9223372036854775807 = NULL However, running it on 1981 and 1982 individually does not: $ ./zdump.exe -vc 1981,1982 Asia/Singapore Asia/Singapore -9223372036854775808 = NULL Asia/Singapore -9223372036854689408 = NULL Asia/Singapore 9223372036854689407 = NULL Asia/Singapore 9223372036854775807 = NULL $ ./zdump.exe -vc 1982,1983 Asia/Singapore Asia/Singapore -9223372036854775808 = NULL Asia/Singapore -9223372036854689408 = NULL Asia/Singapore 9223372036854689407 = NULL Asia/Singapore 9223372036854775807 = NULL Initially, I thought this might have to do with the fact that the transition is specified as a Zone continuation line rather than as a Rule, since zdump properly handled my extended edge-case examples to Jon Skeet a while back: http://mm.icann.org/pipermail/tz/2014-July/021162.html <http://mm.icann.org/pipermail/tz/2014-July/021162.html> zdump also properly handles Asia/Dhaka's DST transition at the end of 2009, but fails in some other similar cases. So it looks like it's more to do with the transition taking place too close to the year boundary. Part of the problem may be the transition happening in different years, UTC and local, but that doesn't seem to be all that's going on. Attached are some test cases to run against various versions of Singapore with 1981,1982 and 1982,1983; and various versions of Dhaka with 2009,2010 and 2010,2011. All of these should work, but most currently don't. (The ones that do are marked.) -- Tim Parenti

4 21

localtime.c patch
by christos＠zoulas.com Oct. 14, 2014

Oct. 14, 2014

Minor nits. christos --- localtime.c.orig 2014-10-07 16:20:32.000000000 -0400 +++ localtime.c 2014-10-07 16:22:47.000000000 -0400 @@ -306,3 +306,3 @@ register int stored; - register int nread; + register ssize_t nread; typedef union { @@ -934,3 +934,2 @@ register bool load_ok; - static struct ttinfo zttinfo; @@ -1006,3 +1005,3 @@ */ - sp->ttis[0] = sp->ttis[1] = zttinfo; + memset(sp->ttis, 0, sizeof(sp->ttis)); sp->ttis[0].tt_gmtoff = -dstoffset; @@ -1131,3 +1130,3 @@ */ - sp->ttis[0] = sp->ttis[1] = zttinfo; + memset(sp->ttis, 0, sizeof(sp->ttis)); sp->ttis[0].tt_gmtoff = -stdoffset; @@ -1145,3 +1144,3 @@ sp->timecnt = 0; - sp->ttis[0] = zttinfo; + memset(sp->ttis, 0, sizeof(sp->ttis)); sp->ttis[0].tt_gmtoff = -stdoffset; @@ -2108,3 +2107,2 @@ - sp = lclptr; i = sp->leapcnt;

5 12

[PROPOSED PATCH] new Zone Pacific/Bougainville
by Paul Eggert Oct. 14, 2014

Oct. 14, 2014

This is for the part of Papua New Guinea that plans to switch from UTC+10 to UTC+11 on 2014-12-28 at 02:00. (Thanks to Kiley Walbom for the heads-up.) * australasia (Pacific/Bougainville): New zone. * zone.tab, zone1970.tab: Add entries for it. * NEWS: Document this. --- NEWS | 6 ++++++ australasia | 25 +++++++++++++++++++++++++ zone.tab | 3 ++- zone1970.tab | 3 ++- 4 files changed, 35 insertions(+), 2 deletions(-) diff --git a/NEWS b/NEWS index 69dc2ca..26dcbf6 100644 --- a/NEWS +++ b/NEWS @@ -2,6 +2,12 @@ News for the tz database Unreleased, experimental changes + Changes affecting future time stamps + + A new Zone Pacific/Bougainville, for the part of Papua New Guinea + that plans to switch from UTC+10 to UTC+11 on 2014-12-28 at 02:00. + (Thanks to Kiley Walbom for the heads-up.) + Changes affecting past time stamps Many time stamps have been corrected for Asia/Ho_Chi_Minh before 1976 diff --git a/australasia b/australasia index 5ea1f18..c06e62c 100644 --- a/australasia +++ b/australasia @@ -519,6 +519,30 @@ Zone Pacific/Palau 8:57:56 - LMT 1901 # Koror Zone Pacific/Port_Moresby 9:48:40 - LMT 1880 9:48:32 - PMMT 1895 # Port Moresby Mean Time 10:00 - PGT # Papua New Guinea Time +# +# From Paul Eggert (2014-10-13): +# Base the Bougainville entry on the Arawa-Kieta region, which appears to have +# the most people even though it was devastated in the Bougainville Civil War. +# +# Although Shanks gives 1942-03-15 / 1943-11-01 for JST, these dates +# are apparently rough guesswork from the starts of military campaigns. +# The World War II entries below are instead based on Arawa-Kieta. +# The Japanese occupied Kieta in July 1942, +# according to the Pacific War Online Encyclopedia +# http://pwencycl.kgbudge.com/B/o/Bougainville.htm +# and seem to have controlled it until their 1945-08-21 surrender. +# +# The Autonomous Region of Bougainville plans to switch from UTC+10 to UTC+11 +# on 2014-12-28 at 02:00. They call UTC+11 "Bougainville Standard Time"; +# abbreviate this as BST. See: +# http://www.bougainville24.com/bougainville-issues/bougainville-gets-own-tim… +# +Zone Pacific/Bougainville 10:22:16 - LMT 1880 + 9:48:32 - PMMT 1895 + 10:00 - PGT 1942 Jul + 9:00 - JST 1945 Aug 21 + 10:00 - PGT 2014 Dec 28 2:00 + 11:00 - BST # Pitcairn # Zone NAME GMTOFF RULES FORMAT [UNTIL] @@ -803,6 +827,7 @@ Zone Pacific/Wallis 12:15:20 - LMT 1901 # 10:00 AEST AEDT Eastern Australia # 10:00 ChST Chamorro # 10:30 LHST LHDT Lord Howe* +# 11:00 BST Bougainville* # 11:30 NZMT NZST New Zealand through 1945 # 12:00 NZST NZDT New Zealand 1946-present # 12:15 CHAST Chatham through 1945* diff --git a/zone.tab b/zone.tab index 084bb2f..a7373f1 100644 --- a/zone.tab +++ b/zone.tab @@ -307,7 +307,8 @@ PE -1203-07703 America/Lima PF -1732-14934 Pacific/Tahiti Society Islands PF -0900-13930 Pacific/Marquesas Marquesas Islands PF -2308-13457 Pacific/Gambier Gambier Islands -PG -0930+14710 Pacific/Port_Moresby +PG -0930+14710 Pacific/Port_Moresby most locations +PG -0613+15534 Pacific/Bougainville Bougainville PH +1435+12100 Asia/Manila PK +2452+06703 Asia/Karachi PL +5215+02100 Europe/Warsaw diff --git a/zone1970.tab b/zone1970.tab index 57c11f1..e971bc7 100644 --- a/zone1970.tab +++ b/zone1970.tab @@ -264,7 +264,8 @@ PE -1203-07703 America/Lima PF -1732-14934 Pacific/Tahiti Society Islands PF -0900-13930 Pacific/Marquesas Marquesas Islands PF -2308-13457 Pacific/Gambier Gambier Islands -PG -0930+14710 Pacific/Port_Moresby +PG -0930+14710 Pacific/Port_Moresby most locations +PG -0613+15534 Pacific/Bougainville Bougainville PH +1435+12100 Asia/Manila PK +2452+06703 Asia/Karachi PL +5215+02100 Europe/Warsaw -- 1.9.3

1 0

[PATCH] tzdata: Asia/Ha_Noi: Add new timezone
by Trần Ngọc Quân Oct. 13, 2014

Oct. 13, 2014

Signed-off-by: Trần Ngọc Quân <vnwildman(a)gmail.com> --- asia | 20 ++++++++++++++++++++ zone.tab | 1 + 2 files changed, 21 insertions(+) diff --git a/asia b/asia index 0be896b..eb7787b 100644 --- a/asia +++ b/asia @@ -2769,6 +2769,26 @@ Zone Asia/Tashkent 4:37:11 - LMT 1924 May 2 # Vietnam +# From Trần Ngọc Quân (Fri, 03 Oct 2014): +# Hanoi is the capital of Vietnam. +# Currently, official timezone of Vietname is Ha_Noi, not Ho_Chi_Minh. +# References (most of them are in Vietnamese language): +# * http://en.wikipedia.org/wiki/Time_in_Vietnam +# * http://vi.wikipedia.org/wiki/M%C3%BAi_gi%E1%BB%9D +# * http://www.thoigian.com.vn/?mPage=P80D01 +# * [1] http://moj.gov.vn/vbpq/Lists/Vn%20bn%20php%20lut/View_Detail.aspx?ItemID=22… +# Zone NAME GMTOFF RULES FORMAT [UNTIL] +Zone Asia/Ha_Noi 7:06:40 - LMT 1906 Jun 9 + 7:06:20 - SMT 1911 Mar 11 0:01 # Saigon MT? + 7:00 - ICT 1942 Dec 31 23:00 + 8:00 - ICT 1945 Mar 14 23:00 + 9:00 - JST 1945 Sep 02 # Tokyo Standard Time + 7:00 - ICT 1947 Mar 31 23:00 + 8:00 - ICT 1954 Oct 09 23:00 + 7:00 - ICT 1967 Dec 31 23:00 + 7:00 - ICT 2002 Oct 14 # See [1] + 7:00 - ICT + # From Paul Eggert (2013-02-21): # Milne gives 7:16:56 for the meridian of Saigon in 1899, as being # used in Lower Laos, Cambodia, and Annam. But this is quite a ways diff --git a/zone.tab b/zone.tab index 084bb2f..cf87c19 100644 --- a/zone.tab +++ b/zone.tab @@ -428,6 +428,7 @@ VC +1309-06114 America/St_Vincent VE +1030-06656 America/Caracas VG +1827-06437 America/Tortola VI +1821-06456 America/St_Thomas +VN +1054+10600 Asia/Ha_Noi VN +1045+10640 Asia/Ho_Chi_Minh VU -1740+16825 Pacific/Efate WF -1318-17610 Pacific/Wallis -- 2.0.1.427.gc47372d

8 30

Republic of Belarus is considering time zone change due to Russia's change
by Alexander Bokovoy Oct. 10, 2014

Oct. 10, 2014

Hi, a local news site got a comment from PR service of Belarussian National Standardization Committee that government is currently deciding on the time zone change to follow Russia. The decision is not yet made and I was unable to find any other source or reference at any governmental site, which is, unfortunately, typical. http://news.tut.by/society/416667.html (in Russian) -- / Alexander Bokovoy

3 8

Re: [tz] Recent conversions of zones to aliases
by random832＠fastmail.us Oct. 6, 2014

Oct. 6, 2014

On Sat, Oct 4, 2014, at 06:15, Stephen Colebourne wrote: > The key point to remember is that Joda-Time has been running for many > years and has striven very hard to retain backwards compatibility. > Converting aliases to their underlying zone has worked well over many > years, and is far from an unreasonable approach, as it reduces the > effect of older zones such as US-Pacific. The effect of those zones is limited to when the user has actually selected them. For that matter, if aliases were not normalized, you would have _maintained_ backwards compatibility when (in principle - in reality, that was before Joda-Time was even a thing.) the zone name was changed _from_ those older names in the first place. The point of aliases is to limit the impact of changes on users who selected the old name when it was current, by keeping the behavior of their systems the same. "Normalizing" them goes against that principle.

1 0

St Andrews meridian in the 17th century
by Peter Ilieve Oct. 6, 2014

Oct. 6, 2014

Now that we don’t have to think about a possible future Europe/Glasgow zone (postings back in August) for several years at least, here’s a bit of Scottish history to consider instead. St Andrews, on the Fife coast in the east of Scotland, had a meridian line set up some 200 years before Greenwich. Here’s a quote from a press release from the University of St Andrews, who have just created a memorial to mark this line: "The 17th Century Scottish astronomer and scientific pioneer James Gregory laid down a meridian line across the floor of his lab at St Andrews University in 1673, almost 200 years before the Greenwich Meridian was established and arbitrarily adopted as the world’s official prime meridian. "Now St Andrews has recognised Gregory’s remarkable body of work with a permanent public memorial – a solid brass line which follows exactly the line of his meridian and bisects the pavement in South Street, St Andrews.” This story was picked up by The Times and the BBC (and probably others I haven’t seen). As well as the line on the lab floor there was a sighting mark outside a window and a stone marker on a hill 2.4km away. This still exists and is marked on Ordnance Survey maps. Some URLs: The University of St Andrews press release: <http://www.st-andrews.ac.uk/news/archive/2014/title,250213,en.php> BBC piece: <http://www.bbc.co.uk/news/uk-scotland-29474850> The Times piece (which is behind their paywall): <http://www.thetimes.co.uk/tto/news/uk/scotland/article4224136.ece> Map showing St Andrews and Gregory’s Pillar (marked with arrow): <http://www.streetmap.co.uk/idld.srf?X=350994&Y=715496&A=Y&Z=115&lm=1&ax=350…> Peter Ilieve

5 6

[PROPOSED PATCH] * zdump.c (adjusted_yday): Define only if TM_GMTOFF is not defined.
by Paul Eggert Oct. 5, 2014

Oct. 5, 2014

--- zdump.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/zdump.c b/zdump.c index 37a0926..13bbb0e 100644 --- a/zdump.c +++ b/zdump.c @@ -851,8 +851,9 @@ delta(struct tm * newp, struct tm *oldp) return result; } +#ifndef TM_GMTOFF /* Return A->tm_yday, adjusted to compare it fairly to B->tm_yday. - Assume A and B differ by at most one year. */ + Assume A and B differ by at most one year. */ static int adjusted_yday(struct tm const *a, struct tm const *b) { @@ -861,6 +862,7 @@ adjusted_yday(struct tm const *a, struct tm const *b) yday += 365 + isleap_sum(b->tm_year, TM_YEAR_BASE); return yday; } +#endif /* If A is the broken-down local time and B the broken-down UTC for the same instant, return A's UTC offset in seconds, where positive -- 1.9.1

1 0

coding style for tzcode?
by christos＠zoulas.com Oct. 4, 2014

Oct. 4, 2014

Hello, The code used to be 8-tab BSD formatted, and now it seems that 2 space indentantion is being used, or 4 space, or whatever random spacing (sometimes contination lines follow the opening parenthesis of the function above, other times they don't) in both new code and diffs from the old code. If people don't like the current coding style, let's decide on a style, reformat all the code to the new style and keep it consistent. What we have now is making the code unreadable. Thank you! christos

2 4

Timezone for Moscow is -10800 after installing tzdata-2014g
by Alexander Koblov Oct. 4, 2014

Oct. 4, 2014

Hi All! My timezone is Europe/Moscow. After installing tzdata-2014g, tzset sets value for timezone not -14400 as before, but -10800, although time shift will be only in October 26th. Is this the expected behavior, or maybe I don't understand something? Please see below program I use for the test and output from console. Notice, how depends on what version of tzdata is installed value of timezone is different, although current time is the same. My question is: Why tzdata-2014g returns timezone for the Europe/Moscow -10800 (3 hours)? As far as I understand timezone for Moscow should be changed on the night of 25/26 October. Thank you, Alexander. ========== #include <iostream> #include <ctime> #include <cstdlib> using namespace std; int main() { tzset(); //set all 4 DST globals using TZ cout<< "the difference between UTC and the local standard time is: "<<timezone<<endl; cout<<boolalpha; //switch to verbal representation of bools cout<<"DST in effect: "<<(bool) daylight<<endl; cout<<"local standard time code: "<<tzname[0]<<endl; cout<<"local standard time code: "<<tzname[1]<<endl; } ========== ============== // With tzdata-2014g-installed [root@Linux jgm]# ./jtz the difference between UTC and the local standard time is: -10800 DST in effect: true local standard time code: MSK local standard time code: MSD [root@Linux jgm]# date Птн Окт 3 14:43:37 MSK 2014 //Let's downgrade to tzdata-2014b [root@Linux jgm]# yum downgrade tzdata-2014b-1.el6.noarch // skip lines Removed: tzdata.noarch 0:2014g-1.el6 Installed: tzdata.noarch 0:2014b-1.el6 Complete! [root@Linux jgm]# ./jtz the difference between UTC and the local standard time is: -14400 DST in effect: false local standard time code: MSK local standard time code: MSD [root@Linux jgm]# date Птн Окт 3 14:44:05 MSK 2014 //Let's return back to tzdata-2014g [root@Linux jgm]# yum update tzdata //skip lines Updated: tzdata.noarch 0:2014g-1.el6 Complete! [root@Linux jgm]# ./jtz the difference between UTC and the local standard time is: -10800 DST in effect: true local standard time code: MSK local standard time code: MSD [root@Linux jgm]# date Птн Окт 3 14:44:36 MSK 2014 [root@Linux jgm]# ==============

5 5

Handling of uninitialized tm_gmtoff and tm_zone
by random832＠fastmail.us Oct. 2, 2014

Oct. 2, 2014

It is possible that mktime, strftime, etc?, may be called with a struct tm that has not had non-standard members initialized. How does tzcode deal with these cases? (It _looks_ like strftime handles it badly; I can't figure out what, if anything, the mktime implementation does with these members).

2 1

Issue with Jordan timezone
by obulesh kumar Oct. 1, 2014

Oct. 1, 2014

Hi all, I am getting wrong time zone for Jordan in my android device. I am calculating time zone from NITZ information provided by network in Amman country. I am using offset and DST value from NITZ to calculate timezone. Below are the values provided by network on date:15/Jul/2014 OFFSET:10800000 DST:false I am getting from proper timezone for Jordan country in 2013g database version as Asia/Amman. But i am not getting any timezone for Amman country in 2013i database on wards. below is timezone data differences from 2013g to 2013i please find snapshot. [image: Inline image 1] Please help us in resolving this issue. Thanks and Regards, Obulesh

2 4

Aix question
by Donald MacQueen Oct. 1, 2014

Oct. 1, 2014

Hi all, Sorry for the off topic, but does anyone know the procedure for updating tz info on Aix? Google is not my friend today. Thanks in advance. Great work, Paul. -- Donald [|] Joel Cairo: "You always have a very smooth explanation." Sam Spade: "What do you want me to do? Learn to stutter?" - The Maltese Falconn

3 2

Time, Clock, and Calendar Programming In C, by Eric S. Raymond
by random832＠fastmail.us Sept. 30, 2014

Sept. 30, 2014

Eric S. Raymond has written an article about the history of the time.h functions at http://www.catb.org/esr/time-programming/ >From his blog post announcing it (http://esr.ibiblio.org/?p=6311) > The C/UNIX library support for time and calendar programming is a nasty mess of historical contingency. I have grown tired of having to re-learn its quirks every time I’ve had to deal with it, so I’m doing something about that. > > Announcing Time, Clock, and Calendar Programming In C, a document which attempts to chart the historical clutter (so you can ignore it once you know why it’s there) and explain the mysteries. > > What I’ve released is an 0.9 beta version. My hope is that it will rapidly attract some thoroughgoing reviews so I can release a 1.0 in a week or so. More than that, I would welcome a subject matter expert as a collaborator. When I saw it I thought it might be generally interesting to people who subscribe to this list.

1 0

Mehdi Ashrafi
by Mehdi Ashrafi Sept. 29, 2014

Sept. 29, 2014

+989376266654

1 0