- tz - lists.iana.org

Deep Impact: worng time zone?
by Arthur David Olson Sept. 23, 2013

Sept. 23, 2013

"...analysis has uncovered a potential problem with computer time tagging..." "NASA's Deep Space Comet Hunter Mission Comes to an End" http://www.jpl.nasa.gov/news/news.php?release=2013-287 --ado

4 3

A New Rule? (was McMurdo/South Pole)
by Bill Seymour Sept. 22, 2013

Sept. 22, 2013

A partly-baked idea to solve the more general problem of when zones appear and disappear: would it make sense to have another kind of entry in the zone RULES column to indicate that we should now follow another zone's practice? How about the keyword, Zone, a space, and the name of the other zone, with the next column following whitespace, if present, being the [UNTIL] column?

2 4

Re: [tz] draft of change summary for next tz release
by David Patte ₯ Sept. 21, 2013

Sept. 21, 2013

And some of us prefer having at least one zone for each ISO 3166-1 country. Several of us understood the old theory file to require this. 1970 is an arbitrary computer geek cutoff point, with not much meaning to general time zone history.

13 41

Jordan permanently on UTC+3?
by Paul Eggert Sept. 20, 2013

Sept. 20, 2013

I looked for hints about what Jordan's going to do with its clocks next month, and found this article from February: Cancelling winter saved Jordan $7 million Petra News Agency 2013-02-20 11:34 UTC http://www.albawaba.com/business/jordan-winter-electricity--472005 Currently the tz database is guessing that Jordan will revert to UTC+2 next month, but if this article is any indication they'll stay at UTC+3 indefinitely, which means the obvious tz patch (already mentioned in the 2012-10-15 comments) would be appropriate.

1 0

Tocantins in Brazil probably not observing DST this season
by Steffen Thorsen Sept. 20, 2013

Sept. 20, 2013

According to this article, Tocantins in Brazil is very likely not to observe DST from October. The decree has not yet been issued, so the decision may still be revoked, but we assume it is very likely because it has been announced by the congressman and DST is so unpopular there. http://conexaoto.com.br/2013/09/18/ministerio-confirma-que-tocantins-esta-f… We will keep this article updated when this is confirmed: http://www.timeanddate.com/news/time/brazil-starts-dst-2013.html Best regards, Steffen Thorsen - timeanddate.com

2 1

Getting close to new release: testing, testing, ...
by Paul Eggert Sept. 20, 2013

Sept. 20, 2013

We need to release a new version soon, because of Fiji. I did further testing and it appears that the recent changes to add meta-information to the zic output won't fly, because they're incompatible with the GNU C library on Ubuntu 12.04. So we need to rethink that feature. There's no rush to introduce it, so let's omit it from the next release. Also, the -t option recently added to tzselect seems like it will be superseded by the tzwinnow approach, whenever we get that working and stable, so for now I think I'd rather omit this. There are a few other problems found by "make public", mostly links that were in the wrong files. I'll post proposed changes soon. If other people could do some testing that'd be nice. You can run "make public". The output should contain the following diagnostics: warning: "antarctica", line 318: Antarctica/Palmer: pre-2013 clients may mishandle distant timestamps warning: "asia", line 1412: 24:00 not handled by pre-1998 versions of zic warning: "asia", line 2332: 24:00 not handled by pre-1998 versions of zic warning: "asia", line 1026: Asia/Jerusalem: pre-2013 clients may mishandle distant timestamps (rule from "asia", line 1021) warning: "asia", line 1315: Asia/Amman: pre-1994 clients may mishandle distant timestamps warning: "asia", line 2016: Asia/Gaza: pre-2013 clients may mishandle distant timestamps warning: "asia", line 2347: Asia/Hebron: pre-2013 clients may mishandle distant timestamps warning: "australasia", line 269: Pacific/Fiji: pre-2013 clients may mishandle distant timestamps warning: "europe", line 998: America/Godthab: pre-2013 clients may mishandle distant timestamps warning: "southamerica", line 1141: America/Santiago: pre-2013 clients may mishandle distant timestamps warning: "southamerica", line 1313: Pacific/Easter: pre-2013 clients may mishandle distant timestamps along with a very long section that starts as follows, which shows that the tz code is still broken on platforms with unsigned 32-bit time_t (this is a longstanding problem). checking uint32_t zones ... --- tzpublic/int64_t.out 2013-09-11 02:43:50.871343089 -0700 +++ tzpublic/uint32_t.out 2013-09-11 02:43:55.907343185 -0700 @@ -210,278 +210,6 @@ Europe/Andorra Sun Mar 29 01:00:00 2037 UT = Sun Mar 29 03:00:00 2037 CEST isdst=1 Europe/Andorra Sun Oct 25 00:59:59 2037 UT = Sun Oct 25 02:59:59 2037 CEST isdst=1 Europe/Andorra Sun Oct 25 01:00:00 2037 UT = Sun Oct 25 02:00:00 2037 CET isdst=0 -Europe/Andorra Sun Mar 28 00:59:59 2038 UT = Sun Mar 28 01:59:59 2038 CET isdst=0 -Europe/Andorra Sun Mar 28 01:00:00 2038 UT = Sun Mar 28 03:00:00 2038 CEST isdst=1 -Europe/Andorra Sun Oct 31 00:59:59 2038 UT = Sun Oct 31 02:59:59 2038 CEST isdst=1

22 69

Historical data
by David Braverman Sept. 20, 2013

Sept. 20, 2013

I've followed the discussions about historical data with interest. I would like to keep historical data in the tzdb, and I understand why I'm in the minority. But I wonder if there couldn't be a compromise? We've implemented a .NET library that uses the tzdb by interpreting[1] the database rather than by compiling it. So for us, we only deploy the tzdb text files that the customer cares about. Some customers are strictly North American concerns, so we only put the northamerica file in their configuration; others need the whole database of 500-some zones. I think other posters have suggested separating pre-1970 data out into a separate file or file set. This would be perfect for our implementation. For the zic implementation, it seems like compilation is an all-or-nothing deal right now. But would it be difficult to create a build script that includes the historical data to the zic package if someone needs it, in addition to the post-1970 build script? Sorry if the question seems naïve. I just think there's room to compromise here. David Braverman Inner Drive Technology Chicago [1] The tzdb files actually get compiled down to an intermediate set of objects at application start, then live on in a singleton. The process takes about a second on an Azure Extra-Small instance. More info here: https://www.inner-drive.com/Demo/Timezones.aspx

2 1

Data changes for v2013e
by Stephen Colebourne Sept. 20, 2013

Sept. 20, 2013

To better help everyone understand the data changes in 2013e, I've run a tool to analyse them and produce nice coloured git diffs. Changes from 2013d to 2013e https://github.com/jodastephen/tzdiff/commit/57aac13605f184a46f74d22f7dddc9… Lines in green are new added data, lines in red are deletions. >From a purely data perspective, the majority of 2013e changes are LMT based. The largest change is to McMurdo/South_Pole. Previous changes for reference: Changes from 2013c to 2013d https://github.com/jodastephen/tzdiff/commit/db93687fe0d5a6bb4a8ee9dd2d81e9… Changes from 2013b to 2013c https://github.com/jodastephen/tzdiff/commit/d145f2ae94c0587aba378920b44227… Changes from 2013a to 2013b https://github.com/jodastephen/tzdiff/commit/639b044db3e3c24d98b0cf5a6fba85… Stephen

1 0

While searching for Vaduz info...
by Andrew Paprocki Sept. 19, 2013

Sept. 19, 2013

I was hunting around for information when the Vaduz change was proposed and while I didn't find anything related to Vaduz specifically, I came across these very nice historical German documents that may be of use to others. The first from a watch-makers journal in 1916 with many pages discussing the adoption of "summer time" that year and reservations about it. There are mentions of those who proposed the legislation, etc. for anyone who can read German and feels like digging through the various pages talking about it. This is the most relevant page (but there are many others -- search for Sommerzeit): (Page 131) http://babel.hathitrust.org/cgi/pt?id=nyp.33433090896915;view=1up;seq=145 The second discusses WET / CET in terms of railroads and contains an interesting snippet regarding CET being authorized since 1 Feb 1920 as well as Netherlands being 20 minutes offset from GMT. I can't find mention of 1 Feb 1920 in the database, so I'm not sure what it is referring to or if this is new/known information. Also, the database says that railroads did not observe the GMT+0:20 in Netherlands, yet this is a railroad journal specifically mentioning it. (Page 84) http://babel.hathitrust.org/cgi/pt?id=njp.32101066879451;view=1up;seq=98 Just leaving these here since some may be interested. Make sure the links leave you on the page # indicated -- sometimes Hathi jumps to an incorrect page. -Andrew

2 1

Re: [tz] tz Digest, Vol 24, Issue 75
by Sterling Udell Sept. 17, 2013

Sept. 17, 2013

> > Can I suggest that we split this into two updates, the first containing > only the Fiji change, and the second with everything else? +1

1 0

Re: [tz] Pulling the data apart ...
by random832＠fastmail.us Sept. 17, 2013

Sept. 17, 2013

On Mon, Sep 16, 2013, at 14:32, Tobias Conradi wrote: > On Mon, Sep 16, 2013 at 7:40 PM, <random832(a)fastmail.us> wrote: > > People don't use the term "separated" for that. > > Except those that do, Huh? Surely you're not claiming that the format _actually_ separates them with no space between them. Go ahead and delete every space from your files, see if zic accepts them. > e.g. tz documentation writers that use "any > number" instead of "one or more". I assert that by "number" they meant "natural number" rather than "integer" (or complex number, or rational number, or real number). The fact that it is a number of characters implies it is an integer. The fact that it is a number of characters that separates something implies it is nonzero and positive. "number" by itself is defined by context. No-one would imagine that this includes non-integers or negative numbers or complex numbers. Not even in your wildest fantasies did you claim there may be sqrt(2)+pi*i spaces, even though that is a number.

5 6

tz mailing list guidelines
by Paul Eggert Sept. 17, 2013

Sept. 17, 2013

Now's as good a time as any to say what guidelines are used when discarding or blocking contributions to the tz mailing list. The tz mailing list discusses proposals for updates that would improve the time zone code and data. When contributions to the mailing list, on balance, harm the project more than help it, it is often advisable to discard them. Examples of abuse include (but are not limited to) spamming, commercial advertising, personal attacks, repetitive or out-of-scope topics, disinformation, sock puppetry, block evasion, copyright violations, and legal threats. An abusive mailing list correspondent should be blocked, with contributions discarded. The length of the block should depend on the severity of the offenses and the estimated future likelihood that future contributions would help more than harm. Correspondents whose contributions consist entirely of spam, for example, should be blocked permanently right away. Correspondents who make significant useful contributions should be treated more leniently: their first block should be for a period of a day to a week; the second, a month to six months; and later blocks, one year to permanent.

1 0

[PATCH 1/3] * backward: Move some links back to primary files.
by Paul Eggert Sept. 17, 2013

Sept. 17, 2013

This should allay concerns that the links would go away any time soon. Suggested by Stephen Colebourne in <http://mm.icann.org/pipermail/tz/2013-September/019801.html>. Change "`" to "'"; these days, "`" and "'" are not symmetric. * antarctica (Antarctica/McMurdo): * europe (Europe/Jersey, Europe/Guernsey, Europe/Isle_of_Man) (Europe/Mariehamn, Europe/Busingen, Europe/Vatican, Europe/San_Marino) (Arctic/Longyearbyen, Europe/Ljubljana, Europe/Podgorica) (Europe/Sarajevo, Europe/Skopje, Europe/Zagreb, Europe/Bratislava): * northamerica (America/St_Barthelemy, America/Marigot): * southamerica (America/Lower_Princes, America/Kralendijk): Move here from 'backward'. This reverts a 2013-08-09 change. --- antarctica | 15 +++++++-------- backward | 19 ------------------- europe | 28 +++++++++++++++++++++------- northamerica | 44 +++++++++++++++++++++++--------------------- southamerica | 12 ++++++++---- 5 files changed, 59 insertions(+), 59 deletions(-) diff --git a/antarctica b/antarctica index 4cb7476..234e59c 100644 --- a/antarctica +++ b/antarctica @@ -16,9 +16,9 @@ # # Except for the French entries, # I made up all time zone abbreviations mentioned here; corrections welcome! -# FORMAT is `zzz' and GMTOFF is 0 for locations while uninhabited. +# FORMAT is 'zzz' and GMTOFF is 0 for locations while uninhabited. -# These rules are stolen from the `southamerica' file. +# These rules are stolen from the 'southamerica' file. # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S Rule ArgAQ 1964 1966 - Mar 1 0:00 0 - Rule ArgAQ 1964 1966 - Oct 15 0:00 1:00 S @@ -231,7 +231,7 @@ Zone Antarctica/Syowa 0 - zzz 1957 Jan 29 # Scott Base, Ross Island, since 1957-01. # See Pacific/Auckland. # -# These rules for New Zealand are stolen from the `australasia' file. +# These rules for New Zealand are stolen from the 'australasia' file. # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S Rule NZAQ 1974 only - Nov 3 2:00s 1:00 D Rule NZAQ 1975 1988 - Oct lastSun 2:00s 1:00 D @@ -269,11 +269,11 @@ Rule NZAQ 2008 max - Apr Sun>=1 2:00s 0 S # From Lee Hotz (2001-03-08): # I queried the folks at Columbia who spent the summer at Vostok and this is # what they had to say about time there: -# ``in the US Camp (East Camp) we have been on New Zealand (McMurdo) +# "in the US Camp (East Camp) we have been on New Zealand (McMurdo) # time, which is 12 hours ahead of GMT. The Russian Station Vostok was # 6 hours behind that (although only 2 miles away, i.e. 6 hours ahead # of GMT). This is a time zone I think two hours east of Moscow. The -# natural time zone is in between the two: 8 hours ahead of GMT.'' +# natural time zone is in between the two: 8 hours ahead of GMT." # # From Paul Eggert (2001-05-04): # This seems to be hopelessly confusing, so I asked Lee Hotz about it @@ -339,10 +339,7 @@ Zone Antarctica/Palmer 0 - zzz 1965 # # # McMurdo Station, Ross Island, since 1955-12 -# See Pacific/Auckland. -# # Amundsen-Scott South Pole Station, continuously occupied since 1956-11-20 -# See Pacific/Auckland. # # From Chris Carrier (1996-06-27): # Siple, the first commander of the South Pole station, @@ -363,3 +360,5 @@ Zone Antarctica/Palmer 0 - zzz 1965 # makes all of the clocks run fast. So every couple of days, # we have to go around and set them back 5 minutes or so. # Maybe if we let them run fast all of the time, we'd get to leave here sooner!! + +Link Pacific/Auckland Antarctica/McMurdo diff --git a/backward b/backward index 561e2ff..b8db6bb 100644 --- a/backward +++ b/backward @@ -18,19 +18,13 @@ Link America/Indiana/Indianapolis America/Fort_Wayne Link America/Indiana/Indianapolis America/Indianapolis Link America/Argentina/Jujuy America/Jujuy Link America/Indiana/Knox America/Knox_IN -Link America/Curacao America/Kralendijk Link America/Kentucky/Louisville America/Louisville -Link America/Curacao America/Lower_Princes -Link America/Guadeloupe America/Marigot Link America/Argentina/Mendoza America/Mendoza Link America/Rio_Branco America/Porto_Acre Link America/Argentina/Cordoba America/Rosario Link America/Denver America/Shiprock -Link America/Guadeloupe America/St_Barthelemy Link America/St_Thomas America/Virgin -Link Pacific/Auckland Antarctica/McMurdo Link Pacific/Auckland Antarctica/South_Pole -Link Europe/Oslo Arctic/Longyearbyen Link Asia/Ashgabat Asia/Ashkhabad Link Asia/Kolkata Asia/Calcutta Link Asia/Chongqing Asia/Chungking @@ -74,20 +68,7 @@ Link America/Havana Cuba Link Africa/Cairo Egypt Link Europe/Dublin Eire Link Europe/London Europe/Belfast -Link Europe/Prague Europe/Bratislava -Link Europe/Zurich Europe/Busingen -Link Europe/London Europe/Guernsey -Link Europe/London Europe/Isle_of_Man -Link Europe/London Europe/Jersey -Link Europe/Belgrade Europe/Ljubljana -Link Europe/Helsinki Europe/Mariehamn -Link Europe/Belgrade Europe/Podgorica -Link Europe/Rome Europe/San_Marino -Link Europe/Belgrade Europe/Sarajevo -Link Europe/Belgrade Europe/Skopje Link Europe/Chisinau Europe/Tiraspol -Link Europe/Rome Europe/Vatican -Link Europe/Belgrade Europe/Zagreb Link Europe/London GB Link Europe/London GB-Eire Link Etc/GMT GMT+0 diff --git a/europe b/europe index 52f15e1..4f972a5 100644 --- a/europe +++ b/europe @@ -440,6 +440,9 @@ Zone Europe/London -0:01:15 - LMT 1847 Dec 1 0:00s 1:00 - BST 1971 Oct 31 2:00u 0:00 GB-Eire %s 1996 0:00 EU GMT/BST +Link Europe/London Europe/Jersey +Link Europe/London Europe/Guernsey +Link Europe/London Europe/Isle_of_Man Zone Europe/Dublin -0:25:00 - LMT 1880 Aug 2 -0:25:21 - DMT 1916 May 21 2:00 -0:25:21 1:00 IST 1916 Oct 1 2:00s @@ -1105,7 +1108,9 @@ Zone Europe/Helsinki 1:39:52 - LMT 1878 May 31 1:39:52 - HMT 1921 May # Helsinki Mean Time 2:00 Finland EE%sT 1983 2:00 EU EE%sT -# Use Europe/Helsinki for the Aaland Islands. + +# Aaland Is +Link Europe/Helsinki Europe/Mariehamn # France @@ -1255,7 +1260,10 @@ Zone Europe/Berlin 0:53:28 - LMT 1893 Apr # Source for the time in Busingen 1980: # http://www.srf.ch/player/video?id=c012c029-03b7-4c2b-9164-aa5902cd58d3 -# Use Europe/Zurich for Busingen. +# From Arthur David Olson (2012-03-03): +# Busingen and Zurich have shared clocks since 1970. + +Link Europe/Zurich Europe/Busingen # Georgia # Please see the "asia" file for Asia/Tbilisi. @@ -1474,7 +1482,9 @@ Zone Europe/Rome 0:49:56 - LMT 1866 Sep 22 1:00 C-Eur CE%sT 1944 Jul 1:00 Italy CE%sT 1980 1:00 EU CE%sT -# Use Europe/Rome also for San Marino and Vatican City. + +Link Europe/Rome Europe/Vatican +Link Europe/Rome Europe/San_Marino # Latvia @@ -1853,7 +1863,7 @@ Zone Europe/Oslo 0:43:00 - LMT 1895 Jan 1 # before 1895, and therefore probably changed the local time somewhere # between 1895 and 1925 (inclusive). -# From Paul Eggert (2013-08-09): +# From Paul Eggert (2013-09-02): # # Actually, Jan Mayen was never occupied by Germany during World War II, # so it must have diverged from Oslo time during the war, as Oslo was @@ -1879,6 +1889,7 @@ Zone Europe/Oslo 0:43:00 - LMT 1895 Jan 1 # # All these events predate our cutoff date of 1970, so use Europe/Oslo # for these regions. +Link Europe/Oslo Arctic/Longyearbyen # Poland # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S @@ -2449,11 +2460,14 @@ Zone Europe/Belgrade 1:22:00 - LMT 1884 # Shanks & Pottenger don't give as much detail, so go with Kozelj. 1:00 - CET 1982 Nov 27 1:00 EU CE%sT -# Use Europe/Belgrade also for Bosnia and Herzegovina, Croatia, Macedonia, -# Montenegro, and Slovenia. +Link Europe/Belgrade Europe/Ljubljana # Slovenia +Link Europe/Belgrade Europe/Podgorica # Montenegro +Link Europe/Belgrade Europe/Sarajevo # Bosnia and Herzegovina +Link Europe/Belgrade Europe/Skopje # Macedonia +Link Europe/Belgrade Europe/Zagreb # Croatia # Slovakia -# See Europe/Prague. +Link Europe/Prague Europe/Bratislava # Slovenia # See Europe/Belgrade. diff --git a/northamerica b/northamerica index 418261f..d3b124e 100644 --- a/northamerica +++ b/northamerica @@ -20,7 +20,7 @@ # Howse writes (pp 121-125) that time zones were invented by # Professor Charles Ferdinand Dowd (1825-1904), # Principal of Temple Grove Ladies' Seminary (Saratoga Springs, NY). -# His pamphlet ``A System of National Time for Railroads'' (1870) +# His pamphlet "A System of National Time for Railroads" (1870) # was the result of his proposals at the Convention of Railroad Trunk Lines # in New York City (1869-10). His 1870 proposal was based on Washington, DC, # but in 1872-05 he moved the proposed origin to Greenwich. @@ -40,8 +40,8 @@ # From Paul Eggert (2001-03-06): # Daylight Saving Time was first suggested as a joke by Benjamin Franklin -# in his whimsical essay ``An Economical Project for Diminishing the Cost -# of Light'' published in the Journal de Paris (1784-04-26). +# in his whimsical essay "An Economical Project for Diminishing the Cost +# of Light" published in the Journal de Paris (1784-04-26). # Not everyone is happy with the results: # # I don't really care how time is reckoned so long as there is some @@ -167,8 +167,8 @@ Zone PST8PDT -8:00 US P%sT # of the Aleutian islands. No DST. # From Paul Eggert (1995-12-19): -# The tables below use `NST', not `NT', for Nome Standard Time. -# I invented `CAWT' for Central Alaska War Time. +# The tables below use 'NST', not 'NT', for Nome Standard Time. +# I invented 'CAWT' for Central Alaska War Time. # From U. S. Naval Observatory (1989-01-19): # USA EASTERN 5 H BEHIND UTC NEW YORK, WASHINGTON @@ -237,9 +237,9 @@ Zone PST8PDT -8:00 US P%sT # H.R. 6, Energy Policy Act of 2005, SEC. 110. DAYLIGHT SAVINGS. # (a) Amendment- Section 3(a) of the Uniform Time Act of 1966 (15 # U.S.C. 260a(a)) is amended-- -# (1) by striking `first Sunday of April' and inserting `second +# (1) by striking 'first Sunday of April' and inserting 'second # Sunday of March'; and -# (2) by striking `last Sunday of October' and inserting `first +# (2) by striking 'last Sunday of October' and inserting 'first # Sunday of November'. # (b) Effective Date- Subsection (a) shall take effect 1 year after the # date of enactment of this Act or March 1, 2007, whichever is later. @@ -678,13 +678,13 @@ Zone America/Boise -7:44:49 - LMT 1883 Nov 18 12:15:11 # and Switzerland counties have their own time zone histories as noted below. # # Shanks partitioned Indiana into 345 regions, each with its own time history, -# and wrote ``Even newspaper reports present contradictory information.'' +# and wrote "Even newspaper reports present contradictory information." # Those Hoosiers! Such a flighty and changeable people! # Fortunately, most of the complexity occurred before our cutoff date of 1970. # # Other than Indianapolis, the Indiana place names are so nondescript -# that they would be ambiguous if we left them at the `America' level. -# So we reluctantly put them all in a subdirectory `America/Indiana'. +# that they would be ambiguous if we left them at the 'America' level. +# So we reluctantly put them all in a subdirectory 'America/Indiana'. # From Paul Eggert (2005-08-16): # http://www.mccsc.edu/time.html says that Indiana will use DST starting 2006. @@ -948,8 +948,8 @@ Zone America/Kentucky/Monticello -5:39:24 - LMT 1883 Nov 18 12:20:36 # This story is too entertaining to be false, so go with Howse over Shanks. # # From Paul Eggert (2001-03-06): -# Garland (1927) writes ``Cleveland and Detroit advanced their clocks -# one hour in 1914.'' This change is not in Shanks. We have no more +# Garland (1927) writes "Cleveland and Detroit advanced their clocks +# one hour in 1914." This change is not in Shanks. We have no more # info, so omit this for now. # # Most of Michigan observed DST from 1973 on, but was a bit late in 1975. @@ -989,7 +989,7 @@ Zone America/Menominee -5:50:27 - LMT 1885 Sep 18 12:00 # occupied 1857/1900 by the Navassa Phosphate Co # US lighthouse 1917/1996-09 # currently uninhabited -# see Mark Fineman, ``An Isle Rich in Guano and Discord'', +# see Mark Fineman, "An Isle Rich in Guano and Discord", # _Los Angeles Times_ (1998-11-10), A1, A10; it cites # Jimmy Skaggs, _The Great Guano Rush_ (1994). @@ -1023,7 +1023,7 @@ Zone America/Menominee -5:50:27 - LMT 1885 Sep 18 12:00 # Milne J. Civil time. Geogr J. 1899 Feb;13(2):173-94 # <http://www.jstor.org/stable/1774359>. # -# See the `europe' file for Greenland. +# See the 'europe' file for Greenland. # Canada @@ -1224,7 +1224,7 @@ Zone America/St_Johns -3:30:52 - LMT 1884 # most of east Labrador -# The name `Happy Valley-Goose Bay' is too long; use `Goose Bay'. +# The name 'Happy Valley-Goose Bay' is too long; use 'Goose Bay'. # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Goose_Bay -4:01:40 - LMT 1884 # Happy Valley-Goose Bay -3:30:52 - NST 1918 @@ -1405,7 +1405,6 @@ Zone America/Montreal -4:54:16 - LMT 1884 -5:00 Mont E%sT 1974 -5:00 Canada E%sT - # Ontario # From Paul Eggert (2006-07-09): @@ -2211,7 +2210,7 @@ Zone America/Dawson -9:17:40 - LMT 1900 Aug 20 # From Paul Eggert (1996-06-12): # For an English translation of the decree, see # <a href="http://mexico-travel.com/extra/timezone_eng.html"> -# ``Diario Oficial: Time Zone Changeover'' (1996-01-04). +# "Diario Oficial: Time Zone Changeover" (1996-01-04). # </a> # From Rives McDow (1998-10-08): @@ -2640,7 +2639,7 @@ Rule CR 1991 1992 - Jan Sat>=15 0:00 1:00 D # go with Shanks & Pottenger. Rule CR 1991 only - Jul 1 0:00 0 S Rule CR 1992 only - Mar 15 0:00 0 S -# There are too many San Joses elsewhere, so we'll use `Costa Rica'. +# There are too many San Joses elsewhere, so we'll use 'Costa Rica'. # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Costa_Rica -5:36:13 - LMT 1890 # San Jose -5:36:13 - SJMT 1921 Jan 15 # San Jose Mean Time @@ -2931,7 +2930,10 @@ Zone America/Grenada -4:07:00 - LMT 1911 Jul # St George's # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Guadeloupe -4:06:08 - LMT 1911 Jun 8 # Pointe a Pitre -4:00 - AST -# Use America/Guadeloupe also for St Barthelemy and for St Martin (French part). +# St Barthelemy +Link America/Guadeloupe America/St_Barthelemy +# St Martin (French part) +Link America/Guadeloupe America/Marigot # Guatemala # @@ -3177,7 +3179,7 @@ Zone America/Panama -5:18:08 - LMT 1890 -5:00 - EST # Puerto Rico -# There are too many San Juans elsewhere, so we'll use `Puerto_Rico'. +# There are too many San Juans elsewhere, so we'll use 'Puerto_Rico'. # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Puerto_Rico -4:24:25 - LMT 1899 Mar 28 12:00 # San Juan -4:00 - AST 1942 May 3 @@ -3196,7 +3198,7 @@ Zone America/St_Lucia -4:04:00 - LMT 1890 # Castries -4:00 - AST # St Pierre and Miquelon -# There are too many St Pierres elsewhere, so we'll use `Miquelon'. +# There are too many St Pierres elsewhere, so we'll use 'Miquelon'. # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Miquelon -3:44:40 - LMT 1911 May 15 # St Pierre -4:00 - AST 1980 May diff --git a/southamerica b/southamerica index ff47cef..ea264a1 100644 --- a/southamerica +++ b/southamerica @@ -1349,9 +1349,13 @@ Zone America/Curacao -4:35:47 - LMT 1912 Feb 12 # Willemstad -4:30 - ANT 1965 # Netherlands Antilles Time -4:00 - AST -# Sint Maarten -# Caribbean Netherlands -# Use America/Curacao. +# From Arthur David Olson (2011-06-15): +# use links for places with new iso3166 codes. +# The name "Lower Prince's Quarter" is both longer than fourteen charaters +# and contains an apostrophe; use "Lower_Princes" below. + +Link America/Curacao America/Lower_Princes # Sint Maarten +Link America/Curacao America/Kralendijk # Caribbean Netherlands # Ecuador # @@ -1646,7 +1650,7 @@ Rule Uruguay 1937 1941 - Mar lastSun 0:00 0 - # Whitman gives 1937 Oct 3; go with Shanks & Pottenger. Rule Uruguay 1937 1940 - Oct lastSun 0:00 0:30 HS # Whitman gives 1941 Oct 24 - 1942 Mar 27, 1942 Dec 14 - 1943 Apr 13, -# and 1943 Apr 13 ``to present time''; go with Shanks & Pottenger. +# and 1943 Apr 13 "to present time"; go with Shanks & Pottenger. Rule Uruguay 1941 only - Aug 1 0:00 0:30 HS Rule Uruguay 1942 only - Jan 1 0:00 0 - Rule Uruguay 1942 only - Dec 14 0:00 1:00 S -- 1.8.1.2

13 70

Re: [tz] Pulling the data apart ...
by Lester Caine Sept. 16, 2013

Sept. 16, 2013

Tobias Conradi wrote: > On Mon, Sep 16, 2013 at 4:31 PM, <random832(a)fastmail.us> wrote: >> On Sun, Sep 15, 2013, at 12:23, Michael Deckers wrote: >>> >>> On 2013-09-13 18:32, Alan Barrett wrote: >>> >>>> The input format is documented in the zic(8) man page. Here's the >>>> relevant part: >>>> Input lines are made up of fields. Fields are separated from >>>> one another by any number of white space characters. >>> >>> Actually, "one or more" seems to be meant rather than "any number" >>> (which would include zero). >> >> .... The fact that they're _separated_ implies there is at least one >> character, because if not then there is no separation. > It does not. There could also be separation by less than one white > space character. > > Only, one could not find it by looking for white space characters. There is no reason that a format could not be fixed length fields simply padded with spaces as required. If an entry uses all the space then no separation. Pulling in data originally formated on 80 column punched often did that simply to get the most data on the card. That is where my 'header code' comes from, the first 2 characters identify the record type, and the next character is the first field of data so no white space :) -- Lester Caine - G8HFL ----------------------------- Contact - http://lsces.co.uk/wiki/?page=contact L.S.Caine Electronic Services - http://lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk Rainbow Digital Media - http://rainbowdigitalmedia.co.uk

2 1

Re: [tz] Proposal to restrict field separator to tab
by Lester Caine Sept. 16, 2013

Sept. 16, 2013

Tobias Conradi wrote: > This is a proposal to restrict field separator to tab > > Current seems to be: > "any number of white space characters" > > Reason: > More than one person in 2013 alone reported problems parsing the data. > > http://mm.icann.org/pipermail/tz/2013-May/019160.html > http://mm.icann.org/pipermail/tz/2013-September/020189.html > > One person in 2013 assumes the current statement means something > different from its English language meaning > > / Actually, "one or more" seems to be meant rather than "any number" / > http://mm.icann.org/pipermail/tz/2013-May/019160.html As someone who would benefit from that change, I'm still a little look warm. Use of 'tab' in the ZONE line would make pulling apart easy, but then the follow on lines need different handling. It is nice that these documents 'reads' nicely looking down the page, but removing a tab from the follow on lines to keep the fields in order will then make things messy as a text document. That said, I am using the tab on these lines to indicate how that line is handled, so a space there would cause a problem anyway, and I drop the 'extra' field to line things up again ... -- Lester Caine - G8HFL ----------------------------- Contact - http://lsces.co.uk/wiki/?page=contact L.S.Caine Electronic Services - http://lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk Rainbow Digital Media - http://rainbowdigitalmedia.co.uk

2 2

Pulling the data apart ...
by Lester Caine Sept. 16, 2013

Sept. 16, 2013

Paul ... I've started on phase two which is extracting the data, but I'm falling at the first hurdle. Should there be a tab character between 'Zone' and the name? I've found many entries in the africa file which don't and it is messing up my 'csv' splitter. Just need a special rule when 'Zone' is found, but looks a little inconsistent with respect to the following lines? -- Lester Caine - G8HFL ----------------------------- Contact - http://lsces.co.uk/wiki/?page=contact L.S.Caine Electronic Services - http://lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk Rainbow Digital Media - http://rainbowdigitalmedia.co.uk

6 6

[PATCH 1/3] * tzfile.5 (SEE ALSO): Mention zdump(8), zic(8).
by Paul Eggert Sept. 16, 2013

Sept. 16, 2013

--- tzfile.5 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tzfile.5 b/tzfile.5 index 4089910..69b9e8b 100644 --- a/tzfile.5 +++ b/tzfile.5 @@ -151,6 +151,6 @@ between daylight saving and standard time. .PP Future changes to the format may append more data. .SH SEE ALSO -newctime(3), newtzset(3) +newctime(3), newtzset(3), zdump(8), zic(8) .\" This file is in the public domain, so clarified as of .\" 1996-06-05 by Arthur David Olson. -- 1.8.3.1

1 2

Deputies of the Russian Duma introduced a bill to switch to "winter time" in Russia
by Alexander Krivenyshev Sept. 15, 2013

Sept. 15, 2013

Once again, Deputies of the Russian State Duma (Ivan Melnikov and Oleg Smolin) have attempted to introduce a bill concerning the switch to "winter time" in Russia. The bill proposes that Russia return to winter time on Oct. 27, 2013 and reinstate the original 11 time zones. original document (in Russian) (http://asozd2c.duma.gov.ru/addwork/scans.nsf/ID/53CA0EEFC86797C443257BDE004 C0BE9/$FILE/339386-6.PDF?OpenElement) http://www.worldtimezone.com/dst_news/dst_news_russia56.html Alexander Krivenyshev, http://www.WorldTimeZone.com

1 0

TAI as a time zone?
by DataPacRat Sept. 15, 2013

Sept. 15, 2013

Would it be feasible to include International Atomic Time (TAI) and/or GPS time (which differs from TAI by a fixed number of seconds) in the tz database as a time zone separate from UTC? I ask because I'm getting ready to submit at least one calendar to BCP 47 which is based on the leap-second-free TAI, and from the feedback I've gotten so far, it seems that the most widely-acceptable way to deal with the differences between TAI and UTC is to employ the tz database, if it's possible to do so. -- Thank you for your time, -- DataPacRat

4 7

Question about leap seconds
by random832＠fastmail.us Sept. 12, 2013

Sept. 12, 2013

Two things: Can a transition time ever reasonably fall _on_ a leap second, and can the zic input format represent this case? I am sketching out a design for a new time zone file format, and it occurs to me that it might be a good idea to specify transitions with POSIX timestamps so the data regarding one time zone is independent of whether leap seconds are enabled or not.

9 17

Re: [tz] Using MediaWiki / Wikidata
by Lester Caine Sept. 12, 2013

Sept. 12, 2013

Tobias Conradi wrote: > was: Re: [tz] [PATCH 3/3] * europe (Europe/Vaduz): Now a link to Europe/Zurich. > > On Tue, Sep 10, 2013 at 7:29 PM, Paul Eggert <eggert(a)cs.ucla.edu> wrote: >> It may well make sense to organize what is currently tz commentary >> into something that is, well, a bit more organized. The format >> I'm most familiar with is MediaWiki, for what it's worth. > And here is some infrastructure using MediaWiki: > https://en.wikipedia.org/wiki/Category:Tz_database > > E.g. > https://en.wikipedia.org/wiki/Africa/Luanda > https://en.wikipedia.org/wiki/America/Indiana/Indianapolis > https://en.wikipedia.org/wiki/Asia/Novosibirsk > > But there are vandalizing admins around, e.g. Anthony Bradbury: > https://en.wikipedia.org/w/index.php?title=Special:Log&page=Time+in+Africa > > Another option could be to use wikidata, e.g. > Asia/Novosibirsk > https://www.wikidata.org/wiki/Q4806295 > and put evidences and for time offsets there. Personally I have no time for wikipedia since we had a lot of well written material removed in the past because some other editors decided they did not like it. So I have no confidence that any material posted would remain clean or even available. I think that a 'private' wiki is much more appropriate given that what we are going to archive is evidential material? With publicly accessible sandboxes for providing new material. Which is then managed based on it's suitability for inclusion? I could live with mediawiki format, but I much prefer clean html documents using ckeditor. And adding interactive packages is something I don't find particularly easy with those type of systems anyway. Is there somewhere appropriate to host a service Paul? I'm happy to run something on my servers, but I suspect the load may be quite high ;) -- Lester Caine - G8HFL ----------------------------- Contact - http://lsces.co.uk/wiki/?page=contact L.S.Caine Electronic Services - http://lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk Rainbow Digital Media - http://rainbowdigitalmedia.co.uk

4 6

[PATCH 1/3] Fix off-by-one bug with Kingston Mean Time.
by Paul Eggert Sept. 12, 2013

Sept. 12, 2013

* northamerica (America/Cayman, America/Jamaica, America/Grand_Turk): Change KMT from -5:07:12 to -5:07:11 (should be -5:07:10.41). * zone.tab: Fine-tune geographical coordinates to match -5:07:10.41. I chose the latitude to match the General Post Office, Kingston, in the city center according to Google Maps. --- northamerica | 19 +++++++------------ zone.tab | 2 +- 2 files changed, 8 insertions(+), 13 deletions(-) diff --git a/northamerica b/northamerica index 3a572ba..55755dd 100644 --- a/northamerica +++ b/northamerica @@ -2622,7 +2622,7 @@ Zone Atlantic/Bermuda -4:19:18 - LMT 1930 Jan 1 2:00 # Hamilton # Cayman Is # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Cayman -5:25:32 - LMT 1890 # Georgetown - -5:07:12 - KMT 1912 Feb # Kingston Mean Time + -5:07:11 - KMT 1912 Feb # Kingston Mean Time -5:00 - EST # Costa Rica @@ -3067,17 +3067,12 @@ Zone America/Tegucigalpa -5:48:52 - LMT 1921 Apr # Great Swan I ceded by US to Honduras in 1972 # Jamaica - -# From Bob Devine (1988-01-28): -# Follows US rules. - -# From U. S. Naval Observatory (1989-01-19): -# JAMAICA 5 H BEHIND UTC - -# From Shanks & Pottenger: +# Shanks & Pottenger give -5:07:12, but Milne records -5:07:10.41 from an +# unspecified official document, and says "This time is used throughout the +# island". Go with Milne. Round to the nearest second as required by zic. # Zone NAME GMTOFF RULES FORMAT [UNTIL] -Zone America/Jamaica -5:07:12 - LMT 1890 # Kingston - -5:07:12 - KMT 1912 Feb # Kingston Mean Time +Zone America/Jamaica -5:07:11 - LMT 1890 # Kingston + -5:07:11 - KMT 1912 Feb # Kingston Mean Time -5:00 - EST 1974 Apr 28 2:00 -5:00 US E%sT 1984 -5:00 - EST @@ -3217,7 +3212,7 @@ Rule TC 2007 max - Mar Sun>=8 2:00 1:00 D Rule TC 2007 max - Nov Sun>=1 2:00 0 S # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Grand_Turk -4:44:32 - LMT 1890 - -5:07:12 - KMT 1912 Feb # Kingston Mean Time + -5:07:11 - KMT 1912 Feb # Kingston Mean Time -5:00 TC E%sT # British Virgin Is diff --git a/zone.tab b/zone.tab index 769432b..7d4c575 100644 --- a/zone.tab +++ b/zone.tab @@ -233,7 +233,7 @@ IR +3540+05126 Asia/Tehran IS +6409-02151 Atlantic/Reykjavik IT +4154+01229 Europe/Rome JE +4912-00207 Europe/Jersey -JM +1800-07648 America/Jamaica +JM +175805-0764736 America/Jamaica JO +3157+03556 Asia/Amman JP +353916+1394441 Asia/Tokyo KE -0117+03649 Africa/Nairobi -- 1.8.3.1

13 34

Re: [tz] uniform time in Switzerland in second half of 19th century
by Paul Eggert Sept. 12, 2013

Sept. 12, 2013

Pierre-Yves Berger found some documentary evidence of the 1894 transition in Switzerland, and I got my hands on a copy of Messerli's book, which gives more details about the circa-1855 transition. Here's a patch, which I'll push to the experimental repository. As far as data goes, this merely moves the 1855 transition to 1853-07-16. >From 9805c5c4a38750ff0c2345fdcc2a273357153259 Mon Sep 17 00:00:00 2001 From: Paul Eggert <eggert(a)cs.ucla.edu> Date: Wed, 11 Sep 2013 18:28:36 -0700 Subject: [PATCH] * europe, zic.8 (Europe/Zurich): Change transition to 1853-07-16. Explain how I derived this guess from Messerli's book. Also, give better evidence about the 1894 transition, from Pierre-Yves Berger. --- europe | 39 ++++++++++++++++++++++++++++----------- zic.8 | 6 +++--- 2 files changed, 31 insertions(+), 14 deletions(-) diff --git a/europe b/europe index 8d26b4e..e70cfb4 100644 --- a/europe +++ b/europe @@ -2662,23 +2662,40 @@ Zone Europe/Stockholm 1:12:12 - LMT 1879 Jan 1 # ... the meridian for Bern mean time ... is 7 degrees 26'22.50". # Expressed in time, it is 0h29m45.5s. +# From Pierre-Yves Berger (2013-09-11): +# the "Circulaire du conseil federal" (December 11 1893) +# <http://www.amtsdruckschriften.bar.admin.ch/viewOrigDoc.do?id=10071353> ... +# clearly states that the [1894-06-01] change should be done at midnight +# but if no one is present after 11 at night, could be postponed until one +# hour before the beginning of service. + # From Paul Eggert (2013-09-11): -# Round to the nearest even second, 0:29:46. -# -# We can find no reliable source for Shanks's claim that all of Switzerland -# except Geneva switched to Bern Mean Time at 00:00 on 1848-09-12. On the -# contrary, a more-reliable source talks about "the gradual introduction of a -# national time (from the 1850s)" (Google translation) with a switch to CET in -# 1894; see Speich's review of Messerli's thesis, Traverse 1997/3, 131-3 -# <http://www.tg.ethz.ch/dokumente/pdf_files/rez_messerli.pdf>. For now, model -# this messy process as a transition in 1855. Shanks's 1894 transition is more -# plausible for Zurich but has not been checked. +# Round BMT to the nearest even second, 0:29:46. +# +# We can find no reliable source for Shanks's assertion that all of Switzerland +# except Geneva switched to Bern Mean Time at 00:00 on 1848-09-12. This book: +# +# Jakob Messerli. Gleichmassig, punktlich, schnell: Zeiteinteilung und +# Zeitgebrauch in der Schweiz im 19. Jahrhundert. Chronos, Zurich 1995, +# ISBN 3-905311-68-2, OCLC 717570797. +# +# suggests that the transition was more gradual, and that the Swiss did not +# agree about civil time during the transition. The timekeeping it gives the +# most detail for is postal and telegraph time: here, federal legislation (the +# "Bundesgesetz uber die Erstellung von elektrischen Telegraphen") passed on +# 1851-11-23, and an official implementation notice was published 1853-07-16 +# (Bundesblatt 1853, Bd. II, S. 859). On p 72 Messerli writes that in +# practice since July 1853 Bernese time was used in "all postal and telegraph +# offices in Switzerland from Geneva to St. Gallen and Basel to Chiasso" +# (Google translation). For now, model this transition as occuring on +# 1853-07-16, though it probably occurred at some other date in Zurich, and +# legal civil time probably changed at still some other transition date. # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S Rule Swiss 1941 1942 - May Mon>=1 1:00 1:00 S Rule Swiss 1941 1942 - Oct Mon>=1 2:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] -Zone Europe/Zurich 0:34:08 - LMT 1855 # See above comment. +Zone Europe/Zurich 0:34:08 - LMT 1853 Jul 16 # See above comment. 0:29:46 - BMT 1894 Jun # Bern Mean Time 1:00 Swiss CE%sT 1981 1:00 EU CE%sT diff --git a/zic.8 b/zic.8 index a2374a1..7ea94c5 100644 --- a/zic.8 +++ b/zic.8 @@ -468,7 +468,7 @@ Rule EU 1996 max - Oct lastSun 1:00u 0 - .sp .ta \w'# Zone\0\0'u +\w'Europe/Zurich\0\0'u +\w'GMTOFF\0\0'u +\w'RULES/SAVE\0\0'u +\w'FORMAT\0\0'u # Zone NAME GMTOFF RULES/SAVE FORMAT UNTIL -Zone Europe/Zurich 0:34:08 - LMT 1855 +Zone Europe/Zurich 0:34:08 - LMT 1853 Jul 16 0:29:46 - BMT 1894 Jun 1:00 Swiss CE%sT 1981 1:00 EU CE%sT @@ -480,9 +480,9 @@ Link Europe/Zurich Switzerland In this example, the zone is named Europe/Zurich but it has an alias as Switzerland. This example says that Zurich was 34 minutes and 8 -seconds west of UT until 1855-01-01 at 00:00, when the legal offset +seconds west of UT until 1853-07-16 at 00:00, when the legal offset was changed to 7\(de\|26\(fm\|22.50\(sd; although this works out to -0:29.45.50, the input format cannot represent fractional seconds so it +0:29:45.50, the input format cannot represent fractional seconds so it is rounded here. After 1894-06-01 at 00:00 Swiss daylight saving rules (defined with lines beginning with "Rule Swiss") apply, and the UT offset became one hour. From 1981 to the present, EU daylight saving rules have -- 1.8.1.2

1 0

Re: [tz] Getting close to new release: testing, testing, ... [SEC=UNOFFICIAL]
by Timothy Arceri Sept. 12, 2013

Sept. 12, 2013

Will you be including the updates to the Australian Daylight Saving's abbreviations in this release? http://mm.icann.org/pipermail/tz/2013-April/019099.html -----Original Message----- From: tz-bounces(a)iana.org [mailto:tz-bounces@iana.org] On Behalf Of Paul Eggert Sent: Wednesday, 11 September 2013 7:55 PM To: Time zone mailing list Subject: [tz] Getting close to new release: testing, testing, ... We need to release a new version soon, because of Fiji. I did further testing and it appears that the recent changes to add meta-information to the zic output won't fly, because they're incompatible with the GNU C library on Ubuntu 12.04. So we need to rethink that feature. There's no rush to introduce it, so let's omit it from the next release. Also, the -t option recently added to tzselect seems like it will be superseded by the tzwinnow approach, whenever we get that working and stable, so for now I think I'd rather omit this. There are a few other problems found by "make public", mostly links that were in the wrong files. I'll post proposed changes soon. If other people could do some testing that'd be nice. You can run "make public". The output should contain the following diagnostics: warning: "antarctica", line 318: Antarctica/Palmer: pre-2013 clients may mishandle distant timestamps warning: "asia", line 1412: 24:00 not handled by pre-1998 versions of zic warning: "asia", line 2332: 24:00 not handled by pre-1998 versions of zic warning: "asia", line 1026: Asia/Jerusalem: pre-2013 clients may mishandle distant timestamps (rule from "asia", line 1021) warning: "asia", line 1315: Asia/Amman: pre-1994 clients may mishandle distant timestamps warning: "asia", line 2016: Asia/Gaza: pre-2013 clients may mishandle distant timestamps warning: "asia", line 2347: Asia/Hebron: pre-2013 clients may mishandle distant timestamps warning: "australasia", line 269: Pacific/Fiji: pre-2013 clients may mishandle distant timestamps warning: "europe", line 998: America/Godthab: pre-2013 clients may mishandle distant timestamps warning: "southamerica", line 1141: America/Santiago: pre-2013 clients may mishandle distant timestamps warning: "southamerica", line 1313: Pacific/Easter: pre-2013 clients may mishandle distant timestamps along with a very long section that starts as follows, which shows that the tz code is still broken on platforms with unsigned 32-bit time_t (this is a longstanding problem). checking uint32_t zones ... --- tzpublic/int64_t.out 2013-09-11 02:43:50.871343089 -0700 +++ tzpublic/uint32_t.out 2013-09-11 02:43:55.907343185 -0700 @@ -210,278 +210,6 @@ Europe/Andorra Sun Mar 29 01:00:00 2037 UT = Sun Mar 29 03:00:00 2037 CEST isdst=1 Europe/Andorra Sun Oct 25 00:59:59 2037 UT = Sun Oct 25 02:59:59 2037 CEST isdst=1 Europe/Andorra Sun Oct 25 01:00:00 2037 UT = Sun Oct 25 02:00:00 2037 CET isdst=0 -Europe/Andorra Sun Mar 28 00:59:59 2038 UT = Sun Mar 28 01:59:59 2038 CET isdst=0 -Europe/Andorra Sun Mar 28 01:00:00 2038 UT = Sun Mar 28 03:00:00 2038 CEST isdst=1 -Europe/Andorra Sun Oct 31 00:59:59 2038 UT = Sun Oct 31 02:59:59 2038 CEST isdst=1

3 3

POSIX extension check
by Arthur David Olson Sept. 10, 2013

Sept. 10, 2013

It's probably worthwhile to check whether extended POSIX in zic-produced binaries will cause grief when those binaries are used with old versions of localtime.c. If so, one or more of documentation, a zic warning, or a version number bump may be in order. --ado

8 19