- tz - lists.iana.org

Haiti not changing to DST tonight
by Steffen Thorsen March 12, 2016

March 12, 2016

Jean Antoine, editor of www.haiti-reference.com informed us that Haiti are not going on DST this year. Several other resources confirms this, auto-translation under: The Presidency Communication Office informs the general public and the press in particular that no by season time change is planned for this year. Thus, the national time will not be extended or retracted Sunday, March 13, 2016. The Presidential Communications Office invites the public to consider this provision to have no setbacks in his daily activities. http://www.radiotelevisioncaraibes.com/presse/heure_d_t_pas_de_changement_d… http://www.vantbefinfo.com/changement-dheure-pas-pour-haiti/ http://news.anmwe.com/haiti-lheure-nationale-ne-sera-ni-avancee-ni-reculee-… Best regards, Steffen Thorsen - timeanddate.com

2 1

Time zones in the arts
by Arthur David Olson March 11, 2016

March 11, 2016

(I'll forego any comment about the absence of an Oxford comma.) @dashdashado 1.1 531 lines 1.2 538 lines *** /tmp/,atz-art.htm 2016-03-11 09:52:55.639707700 -0500 --- /tmp/,btz-art.htm 2016-03-11 09:52:55.715712200 -0500 *************** *** 451,456 **** --- 451,463 ---- proceeds as though it's also mid-evening there.) </li> </ul> + <li> + In the "14 Days to Go"/"T Minus..." episode of "You, Me and the Apocalypse" + (first aired 2015-11-11 in the UK, 2016-03-10 in the US), + the success of a mission to deal with a comet + hinges on whether or not Russia observes Daylight Saving Time. + (In the US, the episode first aired in the week before the switch to DST.) + </li> <hr> <ul> <li>

2 1

[PATCH 0/5] Standardize zone table comments format
by J William Piggott March 10, 2016

March 10, 2016

Not having a standard format for zone table comments is creating ambiguity. For example: 1 Thule / Pituffik 2 Pohnpei (Ponape) 3 Nova Scotia (peninsula) 4 peninsular Malaysia 5 Eastern Time - Pangnirtung, Nunavut 6 Central Time - Campeche, Yucatán 1 and 2 are different formats for alternate names/spellings. 3 shows a sub-region, but uses the same format as the previous alternate name. 4 places the sub-region before the region, where 3 has it after and uses a different format. 5 and 6 use the same format, but 5 defines a single sub-region while 6 defines two regions. These ambiguities make it impossible to interpret the comments without having prior knowledge of the area. This patch set is an effort to standardize the column 4 comments format as follows: A dash (-) is consistently used to delimit a zone_id prefix, so that was retained. A comma (,) is consistently used to delimit regions, so that was retained. Using a slash (/) to delimit alternate names/spellings is accepted English grammar, so that was chosen. Placing sub-regions after regions facilitates having list items begin in uppercase (which is both aesthetically pleasing and grammatically correct) and improves the usability of a sorted list; so that was chosen. Delimiting sub-regions with with curved braces () is in current practice, so that was chosen. Finally two letter codes for regions/sub-regions are included at the end of the sub-region(s) within the curved braces. Multiple regions grouped with the same sub-region(s) are delimited with a comma between the final region of the group and the sub-region(s). Region sub-region groups are delimited from other regions with a semicolon. At least one zone_id or region must be given. When adding a foreign country code to a zone_id on border locations, add it after the zone_id to accommodate implementations that sort the list. This will group zone_id's together, for example: Mountain Time - Chihuahua (away from US border) Mountain Time US - Chihuahua (near US border) Use full words in favor of abbreviations. This format can be represent as: [zone_id] [-] [region[(sub_region, ... [2_letter_code, ... ])][,|;] ... ] There currently are no zone table comments that model the full specification, so here is an imaginary example of the full spec: Central Scooter Time - Yamaha (YZ); Harley, Davidson, Sprint, (west coast XL, XR, FL, ST); Honda (most locations CB, CR), Suzuki, Kawasaki, Vespa The following changes since commit 99b658c3a129dfd0cb777337575e200656b8ff9d: * NEWS, Theory: Clear up descriptions of tzdata abbreviations. (2016-02-14 12:36:54 -0800) are available in the git repository at: git@github.com:jwpi/tz.git zonetab0215 for you to fetch changes up to cf921321194419bc88104da5d7a3a7cfac0ca47e: Standardize zone table comment format (2016-02-20 11:30:20 -0500) ---------------------------------------------------------------- J William Piggott (5): Holiday Islands does not exist. North of Scoresbysund is named National Park Durango is not a border state Use proper names for Baja California States Standardize zone table comment format australasia | 8 +++ europe | 8 +++ northamerica | 6 +- zone.tab | 240 +++++++++++++++++++++++++++++++-------------------------------- zone1970.tab | 250 +++++++++++++++++++++++++++++++++--------------------------------- 5 files changed, 264 insertions(+), 248 deletions(-) --- 8< Example zone1970.tab comments using the standardized format: Adelaide Island (Rothera Station) Anvers Island (Palmer Station) Holme Bay (Mawson Station) Vestfold Hills (Davis Station) Bailey Peninsula (Casey Station) Lake Vostok (Vostok Station) Adélie Land (Dumont-d'Urville Station) East Ongul Island (Syowa Station) Queen Maud Land (Troll Station) Buenos Aires (BA, CF) Argentina (most locations CB, CC, CN, ER, FM, MN, SE, SF) Salta (SA, LP, NQ, RN) Jujuy (JY) Tucumán (TM) Catamarca (CT), Chubut (CH) La Rioja (LR) San Juan (SJ) Mendoza (MZ) San Luis (SL) Santa Cruz (SC) Tierra del Fuego (TF) Samoa, Midway Lord Howe Island Macquarie Island Tasmania (most locations) Tasmania (King Island) Victoria New South Wales (most locations) New South Wales (Yancowinna) Queensland (most locations) Queensland (Whitsunday Islands) South Australia Northern Territory Western Australia (most locations) Western Australia (Eucla) Atlantic islands Pará (east), Amapá Northeast Brazil (MA, PI, CE, RN, PB) Pernambuco Tocantins Alagoas, Sergipe Bahia South Brazil, Southeast Brazil, (GO, DF, MG, ES, RJ, SP, PR, SC, RS) Mato Grosso do Sul Mato Grosso Pará (west) Rondônia Roraima Amazonas (east) Amazonas (west) Acre Newfoundland, Labrador (southeast) Atlantic Time - Nova Scotia (peninsula), Prince Edward Island Atlantic Time - Nova Scotia (Cape Breton) Atlantic Time - New Brunswick Atlantic Time - Labrador (most locations) Atlantic Standard Time - Quebec (Lower North Shore) Eastern Time - Ontario, Quebec, (most locations) Eastern Time - Ontario, Quebec, (places that did not observe DST 1967-1973) Eastern Time - Ontario (Thunder Bay) Eastern Time - Nunavut (most eastern locations) Eastern Time - Nunavut (Pangnirtung) Central Time - Nunavut (Resolute) Eastern Standard Time - Ontario (Atikokan), Nunavut (Southampton Island) Central Time - Nunavut (central) Central Time - Ontario (west), Manitoba Central Time - Ontario (Rainy River, Fort Frances) Central Standard Time - Saskatchewan (most locations) Central Standard Time - Saskatchewan (midwest) Mountain Time - Alberta, British Columbia (east), Saskatchewan (west) Mountain Time - Nunavut (west) Mountain Time - Northwest Territories (central) Mountain Time - Northwest Territories (west) Mountain Standard Time - British Columbia (Creston) Mountain Standard Time - British Columbia (Dawson Creek, Fort Saint John) Mountain Standard Time - British Columbia (Fort Nelson) Pacific Time - British Columbia (west) Pacific Time - Yukon (south) Pacific Time - Yukon (north) Swiss Time Chile (most locations) Easter Island Beijing Time Xinjiang Time Germany (most locations) Ecuador (mainland) Galápagos Islands Spain (mainland) Ceuta, Melilla Canary Islands Chuuk/Truk, Yap Pohnpei/Ponape Kosrae Greenland (most locations) National Park (east coast) Scoresbysund/Ittoqqortoormiit Thule/Pituffik Java, Sumatra Borneo (west, central) Borneo (east, south), Sulawesi (Celebes), Bali, Nusa Tengarra, Timor (west) New Guinea (West Papua / Irian Jaya), Maluku/Moluccas Gilbert Islands Phoenix Islands Line Islands Kazakhstan (most locations) Qyzylorda/Kyzylorda/Kzyl-Orda Aqtobe/Aktobe Atyrau/Atirau/Gur'yev, Mangghystau/Mankistau West Kazakhstan Marshall Islands (most locations) Kwajalein Mongolia (most locations) Bayan-Ölgii, Govi-Altai, Hovd, Uvs, Zavkhan Dornod, Sükhbaatar Central Time Eastern Standard Time - Quintana Roo Central Time - Campeche, Yucatán Central Time - Durango; Coahuila, Nuevo León, Tamaulipas, (away from US border) Central Time US - Coahuila, Nuevo León, Tamaulipas, (near US border) Mountain Time - Baja California Sur, Nayarit, Sinaloa Mountain Time - Chihuahua (away from US border) Mountain Time US - Chihuahua (near US border) Mountain Standard Time - Sonora Pacific Time US - Baja California Central Time - Bahía de Banderas Malaysia (peninsula) Sabah, Sarawak UTC+2 - Central Africa Time UTC+1 - West Africa Time New Zealand Time Chatham Islands Society Islands Marquesas Islands Gambier Islands Papua New Guinea (most locations) Bougainville Gaza Strip West Bank Portugal (mainland) Madeira Islands Azores Réunion Island, Crozet Islands, Scattered Islands Moscow-01 - Kaliningrad Moscow+00 - Russia (west) Moscow+00 - Crimea Moscow+00 - Caspian Sea Moscow+01 - Samara, Udmurtia Moscow+02 - Urals Moscow+03 - Siberia (west) Moscow+03 - Novosibirsk Moscow+04 - Kemerovo Moscow+04 - Yenisei River Moscow+05 - Lake Baikal Moscow+05 - Zabaykalsky Moscow+06 - Lena River Moscow+06 - Tomponsky, Ust-Maysky Moscow+07 - Amur River Moscow+07 - Sakhalin Island Moscow+07 - Oymyakonsky Moscow+07 - Magadan Moscow+08 - Sakha (east), North Kuril Islands Moscow+09 - Kamchatka Moscow+09 - Bering Sea Kerguelen, St Paul Island, Amsterdam Island Indochina (most locations) Ukraine (most locations) Ruthenia Zaporozh'ye/Zaporizhia, Lugansk/Luhansk (east) Wake Island Eastern Time Eastern Time - Michigan (most locations) Eastern Time - Kentucky (Louisville area) Eastern Time - Kentucky (Wayne) Eastern Time - Indiana (most locations) Eastern Time - Indiana (Daviess, Dubois, Knox, Martin) Eastern Time - Indiana (Pulaski) Eastern Time - Indiana (Crawford) Eastern Time - Indiana (Pike) Eastern Time - Indiana (Switzerland) Central Time Central Time - Indiana (Perry) Central Time - Indiana (Starke) Central Time - Michigan (Dickinson, Gogebic, Iron, Menominee) Central Time - North Dakota (Oliver) Central Time - North Dakota (Morton except Mandan area) Central Time - North Dakota (Mercer) Mountain Time Mountain Time - Idaho (south), Oregon (east) Mountain Standard Time - Arizona (except Navajo) Pacific Time Alaska Time Alaska Time - Alaska Panhandle Alaska Time - Alaska Panhandle (southeast) Alaska Time - Annette Island Alaska Time - Alaska Panhandle (neck) Alaska Time - Alaska (west) Aleutian Islands Hawaii Time Uzbekistan (west) Uzbekistan (east) Vietnam (south)

8 49

zic changes (2/2)
by Arthur David Olson March 9, 2016

March 9, 2016

And now, the update. These changes arrange things so that binary files include "transition" entries for minimum time values; these entries eliminate localtime guesswork in handling low-valued time stamps. The bad news: binary files grow slightly as a result of these changes. The good news: there are no changes in the output of "zdump -v" applied to before-and-after versions of all the binary files generated by a "make install." Changes are attached and appear in mangled form below; these are relative to the github version of zic.c after the rollback in the earlier message today. @dashdashado 1.2 2805 lines 1.4 2813 lines *** /tmp/,azic.c 2014-05-01 01:51:36.998933800 -0400 --- /tmp/,bzic.c 2014-05-01 01:51:37.092534000 -0400 *************** *** 1480,1493 **** 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 + gmtoffs[attypes[toi - 1].type]) <= ! (attypes[toi - 1].at + gmtoffs[toi == 1 ? 0 ! : attypes[toi - 2].type]))) { attypes[toi - 1].type = attypes[fromi].type; continue; --- 1480,1490 ---- fromi = 0; while (fromi < timecnt && attypes[fromi].at < min_time) ++fromi; for ( ; fromi < timecnt; ++fromi) { ! if (toi > 1 && ((attypes[fromi].at + gmtoffs[attypes[toi - 1].type]) <= ! (attypes[toi - 1].at + ! gmtoffs[attypes[toi - 2].type]))) { attypes[toi - 1].type = attypes[fromi].type; continue; *************** *** 1532,1537 **** --- 1529,1541 ---- --timecnt32; ++timei32; } + /* + ** Output an INT32_MIN "transition" if appropriate--see below. + */ + if (timei32 > 0 && ats[timei32] > INT32_MIN) { + --timei32; + ++timecnt32; + } while (leapcnt32 > 0 && !is32(trans[leapcnt32 - 1])) --leapcnt32; while (leapcnt32 > 0 && !is32(trans[leapi32])) { *************** *** 1698,1704 **** #undef DO for (i = thistimei; i < thistimelim; ++i) if (pass == 1) ! puttzcode(ats[i], fp); else puttzcode64(ats[i], fp); for (i = thistimei; i < thistimelim; ++i) { unsigned char uc; --- 1702,1713 ---- #undef DO for (i = thistimei; i < thistimelim; ++i) if (pass == 1) ! /* ! ** Output an INT32_MIN "transition" ! ** if appropriate--see above. ! */ ! puttzcode(((ats[i] < INT32_MIN) ? ! INT32_MIN : ats[i]), fp); else puttzcode64(ats[i], fp); for (i = thistimei; i < thistimelim; ++i) { unsigned char uc; *************** *** 2176,2183 **** if (usestart) { addtt(starttime, type); usestart = FALSE; ! } else if (stdoff != 0) ! addtt(min_time, type); } else for (year = min_year; year <= max_year; ++year) { if (useuntil && year > zp->z_untilrule.r_hiyear) break; --- 2185,2191 ---- if (usestart) { addtt(starttime, type); usestart = FALSE; ! } else addtt(min_time, type); } else for (year = min_year; year <= max_year; ++year) { if (useuntil && year > zp->z_untilrule.r_hiyear) break;

7 22

YouTube videos on time zones
by Matt Johnson March 8, 2016

March 8, 2016

If these two aren't in our art file, they probably should be. "Daylight Saving Time Explained" - CGP Grey https://youtu.be/84aWtseb2-4 Among other things, explains Arizona's enclaves and exclaves quite well. "The Problem with Time & Timezones" - Computerphile / Tom Scott https://youtu.be/-5wpm-gesOY Though Tom gets Nepal's time zone offset wrong - can you blame him?

2 1

field separators in tzdata2016a.tar.gz
by Joris Wu March 8, 2016

March 8, 2016

Dear reader, While writing a Perl script to parse the original TZ data files, I discovered that most fields are separated by tab characters ( ASCII 09 ), yet some by spaces. Given the frequency, I expect tabs were the intended separator. It makes parsing less ambiguous anyhow. I converted a set of space separators in attached patches. Not all, as I do not know yet what is the intent here. Regards, Joris Software developer Brisbane

2 1

[PATCH 1/1] Document tzselect std out redirection
by J William Piggott March 7, 2016

March 7, 2016

* tzselect.8: Implement this. Signed-off-by: J William Piggott <elseifthen(a)gmx.com> --- Question: What does the following sentence from this man-page mean? NOTES Applications should not assume that tzselect's output matches the user's political preferences. How can a TZ string define ones political preference? tzselect.8 | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/tzselect.8 b/tzselect.8 index fb39e1f..19f63bb 100644 --- a/tzselect.8 +++ b/tzselect.8 @@ -19,10 +19,16 @@ tzselect \- select a time zone .SH DESCRIPTION The .B tzselect -program asks the user for information about the current location, -and outputs the resulting time zone description to standard output. +program asks the user for information about a target location, +and outputs the corresponding time zone description to standard output. The output is suitable as a value for the TZ environment variable. .PP +If standard output is redirected to anything other than a terminal, +then the instructions following the confirmation prompt are not printed. +This is to facilitate calling +.B tzselect +from another program. +.PP All interaction with the user is done via standard input and standard error. .SH OPTIONS .TP

2 2

tzcode: please rename the "new" argument in icatalloc()
by Markus Scherer March 7, 2016

March 7, 2016

tzcode/private.h has this declaration: char * icatalloc(char * old, const char * new); The "new" identifier prevents it from being compiled with a C++ compiler. Would you mind renaming the second argument? Thanks! markus

3 2

[PATCH] POSIX TZ string validation bug
by J William Piggott March 7, 2016

March 7, 2016

Invalid Julian date of J00 passes. POSIX indicates that there should be no zero padding on 'Julian' dates: Jn The Julian day n (1 <= n <= 365). n The zero-based Julian day (0 <= n <= 365). * tzselect.ksh: Implement this. Signed-off-by: J William Piggott <elseifthen(a)gmx.com> --- tzselect.ksh | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/tzselect.ksh b/tzselect.ksh index ba763e7..d2c3a6d 100644 --- a/tzselect.ksh +++ b/tzselect.ksh @@ -351,8 +351,8 @@ while "(:[0-5][0-9](:[0-5][0-9])?)?" offset = "[-+]?" time mdate = "M([1-9]|1[0-2])\\.[1-5]\\.[0-6]" - jdate = "((J[1-9]|[0-9]|J?[1-2]?[0-9][0-9])" \ - "|J?3[0-5][0-9]|J?36[0-5])" + jdate = "((J[1-9]|[0-9]|J?[1-9][0-9]" \ + "|J?[1-2][0-9][0-9])|J?3[0-5][0-9]|J?36[0-5])" datetime = ",(" mdate "|" jdate ")(/" time ")?" tzpattern = "^(:.*|" tzname offset "(" tzname \ "(" offset ")?(" datetime datetime ")?)?)$"

2 2

[PROPOSED PATCH] Add xkcd
by Paul Eggert March 6, 2016

March 6, 2016

* tz-art.htm: Add xkcd. Add URLs for specific comic strips or panels. --- tz-art.htm | 13 ++++++++++--- 1 file changed, 10 insertions(+), 3 deletions(-) diff --git a/tz-art.htm b/tz-art.htm index 57d9092..127ab69 100644 --- a/tz-art.htm +++ b/tz-art.htm @@ -353,10 +353,17 @@ broadcast 1997-02-13, in which Kramer decides that daylight saving time isn't coming fast enough, so he sets his watch ahead an hour. </li> <li> -The syndicated comic strip Dilbert featured an all-too-rare example of -time zone humor on 1998-03-14. +The syndicated comic strip Dilbert featured an +<a href='http://dilbert.com/strip/1998-03-14'>all-too-rare example of +time zone humor</a> on 1998-03-14. </li> <li> +The webcomic xkcd has the strip +"<a href='https://xkcd.com/673/'>The Sun</a>" (2009-12-09) and the panels +"<a href='https://xkcd.com/1017/'>Backward in Time</a>" (2012-02-14), +"<a href='https://xkcd.com/1061/'>EST</a>" (2012-05-28), and +"<a href='https://xkcd.com/1335/'>Now</a>" (2014-02-26). +<li> Surrealist artist Guy Billout's work "Date Line" appeared on page 103 of the 1999-11 Atlantic Monthly. </li> @@ -515,7 +522,7 @@ Peppermint Patty: "What if the world comes to an end tonight, Marcie?" Marcie: "I promise there'll be a tomorrow, sir ... in fact, it's already tomorrow in Australia!" -(Charles M. Schulz, Peanuts, 1980-06-13) +(Charles M. Schulz, <a href='http://www.gocomics.com/peanuts/1980/06/13'>Peanuts, 1980-06-13</a>) </li> </ul> </body> -- 2.5.0

3 3

Time Lord Judah Levine
by Brian Inglis March 4, 2016

March 4, 2016

Wondered if you might want to give a mention in one of the HTML docs to the person responsible for providing our leap-seconds.list from NIST (courtesy of Tom Van Baak on Time-Nuts): https://www.febo.com/pipermail/time-nuts/2016-March/096401.html a couple of the articles quoted are more textual rather than Youtube link introductions: https://jila.colorado.edu/faculty/judah-levine http://cuindependent.com/2011/08/23/the-nations-time-lord/ -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

1 0

[PATCH] Broken link: Website has disappeared
by Sanjeev March 1, 2016

March 1, 2016

* tz-link.htm --- tz-link.htm | 3 --- 1 file changed, 3 deletions(-) diff --git a/tz-link.htm b/tz-link.htm index bd92f64..c519669 100644 --- a/tz-link.htm +++ b/tz-link.htm @@ -200,9 +200,6 @@ time zone converter.</li> <li><a href="http://twiki.org/cgi-bin/xtra/tzdatepick.html">Date and Time Gateway</a> lets you see the <code><abbr>TZ</abbr></code> values directly.</li> -<li><a -href="http://convertit.com/Go/ConvertIt/World_Time/Current_Time.ASP">Current -Time in 1000 Places</a> uses descriptions of the values.</li> <li><a href="http://www.timezoneconverter.com/cgi-bin/tzc.tzc">Time Zone Converter</a> uses a pulldown menu.</li> -- 2.7.0

3 2

2015g: Is the 1:00 under Pacific/Norfolk "Rules" a typo?
by Marvel, Jim (CPCOE) March 1, 2016

March 1, 2016

Hello, Is the 1:00 under Pacific/Norfolk "Rules" a typo? # Norfolk # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Pacific/Norfolk 11:11:52 - LMT 1901 # Kingston 11:12 - NMT 1951 # Norfolk Mean Time 11:30 - NFT 1974 Oct 27 02:00 # Norfolk T. 11:30 1:00 NFST 1975 Mar 2 02:00 11:30 - NFT 2015 Oct 4 02:00 11:00 - NFT thanks Jim Marvel

5 5

[PROPOSED PATCH] * NEWS: × → x, to pacify ‘make check_character_set’.
by Paul Eggert Feb. 28, 2016

Feb. 28, 2016

--- NEWS | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/NEWS b/NEWS index f3499d7..e4dc2b5 100644 --- a/NEWS +++ b/NEWS @@ -31,7 +31,7 @@ Unreleased, experimental changes Comments in zone tables have been improved. (Thanks to J William Piggott.) tzselect again limits its menu comments so that menus fit on a - 24×80 alphanumeric display. + 24x80 alphanumeric display. In the Theory file, the description of possible time zone abbreviations in tzdata has been cleaned up, as the old description was unclear and -- 2.5.0

1 0

[PATCH] Allow use of <direct.h> from Microsoft Windows to fix mkdir() parameters
by Ian Abbott Feb. 28, 2016

Feb. 28, 2016

This is an alternative to a patch by Esben Haabendal, titled "Fix MinGW builds by adding MKDIR_TAKES_ONE_ARG", posted on Feb 23. Esben's patch made "private.h" optionally include <sys/stat.h> to get at Microsoft's mkdir function, but I think that only works in MinGW, and relies on MinGW's <io.h> header (included by <sys/stat.h>) optionally declaring the mkdir function. The mkdir function is also deprecated by Microsoft. New code should call _mkdir instead. Both functions only take a single parameter. This patch makes "private.h" optionally include <direct.h> (and also <io.h>, due to MinGW's behavior), controlled by the HAVE_DIRECT_H macro, and defines mkdir(path, mode) as macro calling _mkdir(path). With this patch, tz builds successfully in a MSYS2 MingW-w64 Win32 or Win64 environment using the following command line: make CFLAGS="-DHAVE_SYS_WAIT_H=0 -DHAVE_DIRECT_H=1 -DHAVE_LINK=0 -DHAVE_SYMLINK=0 -DHAVE_LOCALTIME_R=0" There are some warnings about 'tzname' being redeclared without dllimport attribute, when compiling zdump.c and localtime.c, but the resulting zdump executable seems to work. -- -=( Ian Abbott @ MEV Ltd. E-mail: <abbotti(a)mev.co.uk> )=- -=( Web: http://www.mev.co.uk/ )=-

2 7

[PATCH] zic: don't warn about link creation failure if not supported
by Ian Abbott Feb. 25, 2016

Feb. 25, 2016

Hi, The attached patch suppresses some warnings output by zic when compiled without support for hard links and/or symbolic links. When linking zone files in dolink(from, to), zic first tries to create hard links, falling back to creating symbolic links, falling back to creating copies. If HAVE_LINK is 0, link(from, to) is defined as a macro that always fails, so in that case, don't issue the warning "hard link failed, symbolic link used" when symbolic links are successfully created in place of hard links. If HAVE_SYMLINK is 0, symlink(from, to) is defined as a macro that always fails, so in that case, don't issue the warning "link failed, copy used" when copies are successfully created in place of symbolic links. -- -=( Ian Abbott @ MEV Ltd. E-mail: <abbotti(a)mev.co.uk> )=- -=( Web: http://www.mev.co.uk/ )=-

1 0

NIST leap-second file not yet updated
by Martin Burnicki Feb. 23, 2016

Feb. 23, 2016

Hi all, please note the NIST leap-second file at ftp://time.nist.gov/pub/ has not yet been updated according to IERS bulletin C 51. It's still the version which has been published in July 2015, and will expire in June 2016. I saw that also tzdata2016a.tar.gz which has been published 2016-01-26 still contains the old leap second file even though bulletin C 51 has already been published 2016-01-11. I've dropped Judah Levine a similar note, but eventually you can include the IERS version of the file into the TZ DB distribution. The IERS file has already been updated and expires 2016-12-28. Regards, Martin -- Martin Burnicki Senior Software Engineer MEINBERG Funkuhren GmbH & Co. KG Email: martin.burnicki(a)meinberg.de Phone: +49 (0)5281 9309-14 Fax: +49 (0)5281 9309-30 Lange Wand 9, 31812 Bad Pyrmont, Germany Amtsgericht Hannover 17HRA 100322 Geschäftsführer/Managing Directors: Günter Meinberg, Werner Meinberg, Andre Hartmann, Heiko Gerstung Web: http://www.meinberg.de

17 57

[PATCH] Fix MinGW builds by adding MKDIR_TAKES_ONE_ARG
by esben.haabendal＠gmail.com Feb. 23, 2016

Feb. 23, 2016

From: Esben Haabendal <esben(a)haabendal.dk> On MinGW, we have non-standard mkdir() which only takes one argument. Signed-off-by: Esben Haabendal <esben(a)haabendal.dk> --- Makefile | 1 + private.h | 5 +++++ 2 files changed, 6 insertions(+) diff --git a/Makefile b/Makefile index 568f7f6..a789fee 100644 --- a/Makefile +++ b/Makefile @@ -125,6 +125,7 @@ LDLIBS= # -DHAVE_SYS_WAIT_H=0 if your compiler lacks a "sys/wait.h" # -DHAVE_TZSET=0 if your system lacks a tzset function # -DHAVE_UNISTD_H=0 if your compiler lacks a "unistd.h" (Microsoft C++ 7?) +# -DMKDIR_TAKES_ONE_ARG if your mkdir takes one arg (MinGW) # -DNO_RUN_TIME_WARNINGS_ABOUT_YEAR_2000_PROBLEMS_THANK_YOU=1 # if you do not want run time warnings about formats that may cause # year 2000 grief diff --git a/private.h b/private.h index 1c176e6..b2e7ecb 100644 --- a/private.h +++ b/private.h @@ -58,6 +58,11 @@ #define HAVE_UTMPX_H 1 #endif /* !defined HAVE_UTMPX_H */ +#ifdef MKDIR_TAKES_ONE_ARG +#include <sys/stat.h> +#define mkdir(path,mode) mkdir(path) +#endif + #ifndef NETBSD_INSPIRED # define NETBSD_INSPIRED 1 #endif -- 2.7.1

1 0

Ulyanovsk, Altai Krai and Altai republic on their way to change time zones
by Alexander Krivenyshev Feb. 23, 2016

Feb. 23, 2016

Ulyanovsk, Altai Krai and Altai republic on their way to change time zones by March 27, 2016 at 2am. Today (Feb. 17, 2016) Russian State Duma passed the bill in the first reading for 3 more regions to change their time zones (http://asozd2.duma.gov.ru/) - Ulyanovsk Oblast / Ulyanovsk from MSK to MSK+1 (UTC+3 to UTC+4) same as Astrakhan Oblast - Altai republic / Gorno-Altaysk MSK+3 to MSK+4 (UTC+6 to UTC+7) to Krasnoyarsk time zone - Altai Krai / Barnaul MSK+3 to MSK+4 (UTC+6 to UTC+7) to Krasnoyarsk time zone 920582-6 On Amendments to Article 5 of the Federal Law "On the Calculation of Time" (on reference of the Ulyanovsk Oblast / Ulyanovsk to the 3rd time zone, MSK+1, UTC+4) 02/17/2016- The State Duma passed the bill in the first reading; 935532-6 On Amendments to Article 5 of the Federal Law "On the Calculation of Time" (on reference of the Altai republic / Gorno-Altaysk to the 6th time zone, MSK+4, UTC+7) 02/17/2016- The State Duma passed the bill in the first reading; 944348-6 On Amendments to Article 5 of the Federal Law "On the Calculation of Time" (on reference of the Altai Krai / Barnaul to the 6th time zone, MSK+4, UTC+7) 02/17/2016- The State Duma passed the bill in the first reading; With 95% certainty these 3 more regions will change their time zones by March 27, 2016 at 2am. Alexander Krivenyshev http://www.worldtimezone.com

4 9

Re: [tz] Astrakhan region got approval to change its time zone
by Paul Eggert Feb. 20, 2016

Feb. 20, 2016

Alain Mouette wrote: > May a suggest that you publish somewhere in the Docs the RegEx to correctly test > the Region String? Thanks, good suggestion. Proposed patch attached.

2 2

7 regions in Russia submitted draft bills to change their time zones
by Alexander Krivenyshev Feb. 18, 2016

Feb. 18, 2016

After researching several official government documents (duma.gov.ru), there are at least 7 regions in Russia (not 3) that have submitted draft bills proposing changes to their time zones. Those regions are: - Zabaykalsky Krai / Chita (draft bill date of entry July 16, 2015)- has recently received approval to change time zone from UTC+8 to UTC+9 - Astrakhan Oblast / Astrakhan (draft bill date of entry Aug. 15, 2015), UTC+3 to UTC+4 - Sakhalin Oblast / Yuzhno-Sakhalinsk (draft bill date of entry Sep. 28, 2015), UTC+10 to UTC+11 - Ulyanovsk Oblast / Ulyanovsk (draft bill date of entry Nov. 03, 2015), UTC+3 to UTC+4 - Altai republic / Gorno-Altaysk (draft bill date of entry Nov. 23, 2015), UTC+6 to UTC+7 - Altai Krai / Barnaul (draft bill date of entry Dec. 03, 2015), UTC+6 to UTC+7 - Magadan Oblast / Magadan (draft bill date of entry Dec. 08, 2015), UTC+10 to UTC+11 See as a reference Russia map with 7 regions to change their time zones (darker colors of blue, green, red): http://www.worldtimezone.com/russia-time-zones-map-2016-04.gif (vs current http://www.worldtimezone.com/time-russia12.php) Seems that draft bill in Russia must pass through the following phases before being signed into law: Phase 1- The State Duma Council draft bill review Phase 2- Pass three (3) readings/revisions by the State Duma Phase 3- Approval by the Federation Council Phase 4- Signed by the President. Currently there are 6 additional regions in Russia that have requested to change their time zones (make amendments to the current Federal Law "On the calculation of time"), those draft bills were introduced at different times and are in different phases of the approval (or rejection) process. To make it easier to understand, below are the approximate phases of the remaining regions requesting time zones changes: - Sakhalin Oblast / Yuzhno-Sakhalinsk - Phase 1 (introduced to the State Duma Council) - Astrakhan Oblast / Astrakhan - Phase 2 ( first reading by the State Duma) - Ulyanovsk Oblast / Ulyanovsk - Phase 1 (introduced to the State Duma Council) - Altai republic / Gorno-Altaysk - Phase 1 (introduced to the State Duma Council) - Altai Krai / Barnaul - Phase 1 (introduced to the State Duma Council) - Magadan Oblast / Magadan - Phase 1 ( introduced to the Chairman of the State Duma- part of the State Duma Council) It is hard to say, how many above regions will be able to get through all these phases and change their time zones by March 27, 2016. We will try to keep our eyes on it. Alexander Krivenyshev http://www.worldtimezone.com

15 38

Hanke-Henry want to destroy tz
by Steve Allen Feb. 17, 2016

Feb. 17, 2016

Steve Hanke and Dick Henry want to decharter this tz project https://www.washingtonpost.com/news/worldviews/wp/2016/02/12/the-radical-pl… -- Steve Allen <sla(a)ucolick.org> WGS-84 (GPS) UCO/Lick Observatory--ISB Natural Sciences II, Room 165 Lat +36.99855 1156 High Street Voice: +1 831 459 3046 Lng -122.06015 Santa Cruz, CA 95064 http://www.ucolick.org/~sla/ Hgt +250 m

5 4

URUGUAY Timezone Update
by Nicolas Antoniello Feb. 15, 2016

Feb. 15, 2016

Hi Folks, Finally, there is a resolution by Uruguayan government on June the 29th, 2015, that the timezone for Uruguay will be GMT-3 (UTC-3) from now on (not just for this summer as initially announced). Just to make it permanently in the TZ data archive (in case was done only for this summer). ... hope not to change ever again! Regards, Nicolas

2 2

POSIX epoch in the news?
by Arthur David Olson Feb. 15, 2016

Feb. 15, 2016

"Don’t Set Your iPhone Back to 1970, No Matter What" http://www.wired.com/2016/02/dont-set-your-iphone-back-to-1970-no-matter-wh… @dashdashado

5 7

Re: [tz] Astrakhan region got approval to change its time zone
by Matt Johnson Feb. 14, 2016

Feb. 14, 2016

I'm more concerned with end-user confusion on whether +04 means GMT+04 or MSK+04. ________________________________ From: Paul Eggert<mailto:eggert@cs.ucla.edu> Sent: ‎2/‎13/‎2016 6:03 PM To: Brian.Inglis(a)systematicsw.ab.ca<mailto:Brian.Inglis@systematicsw.ab.ca>; tz(a)iana.org<mailto:tz@iana.org> Subject: Re: [tz] Astrakhan region got approval to change its time zone Brian Inglis wrote: > I just know a bunch of people out there are cluelessly checking this string is > upper case alpha. We crossed that bridge many years ago, so we shouldn't be giving any such people much more grief than we're already giving them. There have been non-upper-case-alpha abbreviations in the tz database since nearly day one. For example, in our repository the very first version of the 'europe' file (dated 1986) had spaces in some abbreviations, and spaces are much harder to parse than digits or plus signs are. In the current release, Pacific/Guam uses abbreviations that are not upper case alpha. Also, POSIX has blessed digits and plus signs in the abbreviations for quite some time; see <https://mm.icann.org/pipermail/tz/2001-January/011305.html>.

4 7