- tz - lists.iana.org

ICANN News Alert - ICANN to Manage Time Zone Database
by dr.hingston Oct. 15, 2011

Oct. 15, 2011

I don't think this has been notified to the list? On 30 September Astrolabe Inc filed action for alleged copyright infringement against the voluntary maintainers of the TZ database. Details at: www.scribd.com/doc/67760407/ASTROLABE-INC-Vs-ARTHUR-DAVID-OLSON-and-PAUL-EGG ERT-Complaint ICANN has just released the following statement at: www.icann.org/en/news/releases/release-14oct11-en.pdf ICANN to Manage Time Zone Database The Internet Corporation for Assigned Names and Numbers (ICANN) today took over operation of an Internet Time Zone Database that is used by a number of major computer systems. ICANN agreed to manage the database after receiving a request from the Internet Engineering Task Force (IETF). The database contains time zone code and data that computer programs and operating systems such as Unix, Linux, Java, and Oracle rely on to determine the correct time for a given location. Modifications to the database occur frequently throughout the year. "The time zone database is used by a large number of commercial operating systems and the software applications," said Russ Housely, chairman of the IETF. "Incorrect time zone information will impact many everyday activities, including meeting and conference call coordination, airplane and train schedules, physical package delivery notices, and astronomical observatories." For nearly three decades, the TZ Database had been maintained by a group of dedicated volunteers, in particular, Arthur David Olson at the US National Institutes of Health. Olson coordinated the group, managed the data, and created a platform for their release. Olson's announced retirement prompted the IETF to turn to ICANN to ensure continued operation of the database. "The Time Zone Database provides an essential service on the Internet and keeping it operational falls within ICANN's mission of maintaining a stable and dependable Internet," said Akram Atallah, ICANN's Chief Operating Officer. <end>

2 1

Re: [tz] LST
by Robert Elz Oct. 15, 2011

Oct. 15, 2011

Date: Fri, 14 Oct 2011 10:10:31 -0400 From: Tim Parenti <tim(a)timtimeonline.com> Message-ID: <CAFpi07yBJVqZxgFSzqOoKTLPb2m67NiH_LPCBifGT3J8hMrzsw(a)mail.gmail.com> | "LST" seems too like the other "meaningful" identifiers that people may try | to continue to infer meaning from it. And ... Jaakko Hyvätti <jaakko.hyvatti(a)foreca.com> said: | LOC or LOCAL would be least confusing I think. A couple of other suggestions I have been sent off list: LCT (Local Clock Time) which has the advantages of LST (most of the advantages I like in that one, but without the name clash - which personally I see as a deficit of LCT!) NIL or nil as an alternative for NONE or none while remaining 3 characters long (which is a minor advantage, but we already have zones with longer abbreviations, so ...) These are thrown into the pot for consideration. There is no current urgency to come to a conclusion on this that I'm aware of, so we can treat it as a back-burner topic. But please everyone, keep in mind that debating names is easy, everyone can have an opinion, as there's usually no right answer (sometimes some wrong answers, but not often one obviously right answer). kre

1 0

Re: [tz] LST
by Tim Parenti Oct. 14, 2011

Oct. 14, 2011

On Thu, Oct 13, 2011 at 23:29, Robert Elz <kre(a)munnari.oz.au> wrote: > | Forgive me if I'm wrong, but I believe most robust implementations of > the TZ > | database already have some way of expressing an offset in this way. > > That isn't the issue. What is of interest for this topic, is what the > tz database (and code) should put in the tzname[] array &/or tm_zone field > of the struct tm. > ... > > So, using -04:00 just isn't an option, sorry. > That was precisely my point. While a numeric offset would be meaningful, it's place is simply *not* in the abbreviation designation, for programmatic and practical reasons. On Fri, Oct 14, 2011 at 06:29, Zefram <zefram(a)fysh.org> wrote: > FWIW, the POSIX standard for $TZ allows ASCII letters (of either case), > digits, "+", and "-" in the abbreviation, and requires the abbreviation > to be at least three characters long. > "LST" seems too like the other "meaningful" identifiers that people may try to continue to infer meaning from it. Could we perhaps just use the string "local" for these "non-meaningful" cases, and avoid abbreviations altogether? This all-lowercase string conforms to the POSIX standard as described and would also serve to *clearly* disambiguate from other identifiers like "UTC", while not having to deal with contrived abbreviations. -- Tim Parenti

4 4

mktime() during the the DST gap
by christos＠zoulas.com Oct. 14, 2011

Oct. 14, 2011

I am sure that this has been discussed before, but I think that if we decide to keep the current behavior, we should document it in the manual page explicitly. As you probably know calling mktime() in during the DST gap with tm_isdst == -1, returns -1 in this tzcode() implementation. The glibc one at least, adds the difference between the non-DST and the DST time. Both behaviors are justifyable. - We are returning -1 because this time cannot be represented. - We are returning the time you meant, since you cannot easily fix it by yourself by deducing the dst offset. I am suggesting that we explicitly document the chosen behavior in the manual page and if we choose to return -1, we set errno which is currently not set. I have appended a patch that changes the behavior to return the closest time as glibc does (if we choose to do that) as well as a test program that demonstrates that mktime() fails and does not set errno now. christos ------------- #include <stdio.h> #include <unistd.h> #include <err.h> #include <time.h> int main(int argc, char *argv[]) { struct tm tm; time_t t; setenv("TZ", "America/New_York"); memset(&tm, 0, sizeof(tm)); tm.tm_hour = 2; tm.tm_min = 30; tm.tm_mday = 14; tm.tm_mon = 2; tm.tm_year = 110; tm.tm_isdst = -1; t = mktime(&tm); if (t == -1) err(1, "mktime"); printf("%s", ctime(&t)); return 0; } ------------------- diff -u -r1.8 localtime.c --- localtime.c 14 Dec 2010 19:08:54 -0000 1.8 +++ localtime.c 14 Oct 2011 15:17:58 -0000 @@ -1787,6 +1787,25 @@ return WRONG; --hi; } + if (lo - 1 == hi && yourtm.tm_isdst < 0) { + time_t off = 0; + for (i = sp->typecnt - 1; i >= 0; --i) { + for (j = sp->typecnt - 1; j >= 0; --j) { + if (sp->ttis[j].tt_isdst == + sp->ttis[i].tt_isdst) + continue; + off = sp->ttis[j].tt_gmtoff - + sp->ttis[i].tt_gmtoff; + break; + } + if (j >= 0) + break; + } + if (off) { + t = hi + off; + break; + } + } if (lo > hi) return WRONG; if (dir > 0)

1 0

A history maintaining repository for tzdata
by Kevin Lyda Oct. 14, 2011

Oct. 14, 2011

I note that some others have created some repositories for tzdata, but I'd really like to see the history of what Paul and Arthur have done be maintained. Commits that have useful commit messages and "correct" dates. To that end I've created the following repository (I stuck it on two hosters as I saw there were concerns about github on the list): https://github.com/lyda/tzdata https://gitorious.org/tzdata The README file explains how the import was done and what might need to be fixed: https://github.com/lyda/tzdata/blob/master/README https://gitorious.org/tzdata/tzdata/blobs/master/README If people want me to recreate it differently I'm happy to do so. It takes about a minute to build from scratch. The git repo is only 1.5M BTW so if someone wants to setup private hosting it really won't take up much room or bandwidth. If people like this I'm happy to do the same for tzcode. Kevin PS It would amuse me if the tz project had one of the oldest git commits on github/gitorious/wherever: https://github.com/lyda/tzdata/commit/dcf9a59f640d3e24745b36a9b5593add336a0… -- Kevin Lyda Dublin, Ireland US Citizen overseas? We can vote. Register now: http://www.votefromabroad.org/

12 20

archive completeness
by Zefram Oct. 14, 2011

Oct. 14, 2011

For the benefit of those looking to complete the oldtz archive, I've checked the entire mailing list archive for release announcements. I used <http://mm.icann.org/pipermail/tz/> for 1986 to 2010, and <http://news.gmane.org/gmane.comp.time.tz> for 2011. In this combination I believe they're a complete archive of the mailing lists, <tz(a)elsie.nci.nih.gov> and <tz(a)iana.org>, from inception on 1986-11-25 up to the present 2011-10-11. I extracted all the information from the archives today, 2011-10-11. I have some confidence that this is a complete list of the announcements on the mailing lists, because I grepped specifically for ones that seemed to be missing. (Did find a few that I'd missed on the first pass.) There are, however, some releases that were not announced, ranging from tz92b up to tzdata2011f. There are various other irregularities. This listing incorporates corrections that were made on the list, and obvious typo fixes. The dates given are the UT date of the announcement message (the original one, if later corrected) as reported by the archive. All announcements up to 2011k were by Arthur David Olson. I'd like to see someone expand this into a systematic list of all releases actually made. The mailing list contains a few mentions of releases that were not announced at the time, but I have no confidence that this would catch all unannounced releases. 1992-04-25 tz92.tar.Z only 1992-11-21 tz92c.tar.Z only 1993-01-08 tzcode93.tar.Z tzdata93.tar.Z 1993-02-02 tzdata93b.tar.Z only 1993-06-06 tzcode93c.tar.Z tzdata93c.tar.Z 1993-07-18 tzcode93d.tar.Z tzdata93d.tar.Z 1993-09-06 tzcode93e.tar.Z tzdata93e.tar.Z 1993-10-15 tzcode93f.tar.Z tzdata93f.tar.Z 1993-11-29 tzcode93g.tar.gz tzdata93g.tar.gz 1994-02-03 tzdata94a.tar.gz only 1994-02-07 tzcode94b.tar.gz tzdata94b.tar.gz 1994-02-10 tzcode94c.tar.gz only 1994-02-24 tzcode94d.tar.gz tzdata94d.tar.gz 1994-03-31 tzcode94e.tar.gz only 1994-05-05 tzcode94f.tar.gz only 1994-05-05 tzcode94g.tar.gz only 1994-07-04 tzdata94e.tar.gz only 1994-08-20 tzdata94f.tar.gz only 1994-12-10 tzcode94h.tar.gz tzdata94h.tar.gz 1995-03-11 tzcode95b.tar.gz tzdata95b.tar.gz 1995-03-13 tzcode95c.tar.gz only 1995-07-02 tzdata95c.tar.gz only 1995-07-03 tzdata95d.tar.gz only 1995-07-08 tzdata95e.tar.gz only 1995-08-29 tzdata95f.tar.gz only 1995-09-01 tzdata95g.tar.gz only 1995-09-14 tzcode95d.tar.gz only 1995-09-21 tzdata95h.tar.gz only 1995-09-26 tzdata95i.tar.gz only 1995-10-13 tzcode95e.tar.gz only 1995-10-28 tzcode95f.tar.gz tzdata95j.tar.gz 1995-10-30 tzcode95g.tar.gz tzdata95k.tar.gz 1995-12-19 tzcode95h.tar.gz tzdata95l.tar.gz 1995-12-21 tzcode95i.tar.gz tzdata95m.tar.gz 1996-01-06 tzcode96a.tar.gz tzdata96a.tar.gz 1996-01-11 tzcode96b.tar.gz only 1996-01-16 tzcode96c.tar.gz only 1996-01-27 tzdata96b.tar.gz only 1996-02-12 tzcode96d.tar.gz tzdata96c.tar.gz 1996-02-29 tzcode96e.tar.gz only 1996-03-19 tzdata96d.tar.gz only 1996-03-19 tzdata96e.tar.gz only 1996-04-19 tzdata96f.tar.gz only 1996-05-03 tzcode96f.tar.gz tzdata96g.tar.gz 1996-05-09 tzdata96h.tar.gz only 1996-05-16 tzcode96g.tar.gz only 1996-06-05 tzcode96h.tar.gz only 1996-07-01 tzdata96i.tar.gz only 1996-07-28 tzcode96i.tar.gz only 1996-07-30 tzcode96j.tar.gz only 1996-09-08 tzcode96k.tar.gz tzdata96k.tar.gz 1996-09-08 tzcode96l.tar.gz only 1996-11-05 tzcode1996m.tar.gz tzdata1996l.tar.gz 1996-11-24 tzdata1996m.tar.gz only 1996-12-16 tzcode1996n.tar.gz only 1996-12-28 tzcode1996o.tar.gz tzdata1996n.tar.gz 1997-01-21 tzcode1997a.tar.gz tzdata1997a.tar.gz 1997-02-27 tzcode1997b.tar.gz tzdata1997b.tar.gz 1997-03-04 tzdata1997c.tar.gz only 1997-03-08 tzcode1997c.tar.gz tzdata1997d.tar.gz 1997-03-29 tzcode1997d.tar.gz tzdata1997e.tar.gz 1997-05-03 tzcode1997e.tar.gz tzdata1997f.tar.gz 1997-07-19 tzcode1997f.tar.gz tzdata1997g.tar.gz 1997-09-04 tzcode1997g.tar.gz tzdata1997h.tar.gz 1997-10-07 tzdata1997i.tar.gz only 1997-12-18 tzcode1997h.tar.gz tzdata1997j.tar.gz 1997-12-29 tzcode1997i.tar.gz tzdata1997k.tar.gz 1998-01-13 tzcode1998a.tar.gz tzdata1998a.tar.gz 1998-01-17 tzcode1998b.tar.gz tzdata1998b.tar.gz 1998-02-28 tzcode1998c.tar.gz tzcode1998c.tar.gz 1998-05-14 tzcode1998d.tar.gz tzdata1998d.tar.gz 1998-05-28 tzcode1998e.tar.gz tzdata1998e.tar.gz 1998-06-01 tzcode1998f.tar.gz only 1998-07-20 tzdata1998f.tar.gz only 1998-08-11 tzdata1998g.tar.gz only 1998-09-24 tzcode1998g.tar.gz tzdata1998h.tar.gz 1998-10-01 tzcode1998h.tar.gz tzdata1998i.tar.gz 1999-01-19 tzcode1999a.tar.gz tzdata1999a.tar.gz 1999-02-01 tzcode1999b.tar.gz tzdata1999b.tar.gz 1999-03-25 tzcode1999c.tar.gz tzdata1999c.tar.gz 1999-03-30 tzcode1999d.tar.gz tzdata1999d.tar.gz 1999-08-17 tzcode1999e.tar.gz tzdata1999e.tar.gz 1999-09-23 tzcode1999f.tar.gz tzdata1999f.tar.gz 1999-09-28 tzcode1999g.tar.gz tzdata1999g.tar.gz 1999-10-07 tzdata1999h.tar.gz only 1999-11-08 tzcode1999h.tar.gz tzdata1999i.tar.gz 1999-11-16 tzcode1999i.tar.gz tzdata1999j.tar.gz 2000-01-18 tzcode2000a.tar.gz tzdata2000a.tar.gz 2000-02-21 tzcode2000b.tar.gz tzdata2000b.tar.gz 2000-03-04 tzcode2000c.tar.gz tzdata2000c.tar.gz 2000-03-14 tzdata2000d.tar.gz only 2000-04-20 tzcode2000d.tar.gz only 2000-07-31 tzcode2000e.tar.gz tzdata2000e.tar.gz 2000-08-10 tzcode2000f.tar.gz tzdata2000f.tar.gz 2000-10-10 tzcode2000g.tar.gz tzdata2000g.tar.gz 2000-12-14 tzcode2000h.tar.gz tzdata2000h.tar.gz 2001-03-13 tzcode2001a.tar.gz tzdata2001a.tar.gz 2001-04-05 tzcode2001b.tar.gz tzdata2001b.tar.gz 2001-06-05 tzcode2001c.tar.gz tzdata2001c.tar.gz 2001-10-09 tzcode2001d.tar.gz tzdata2001d.tar.gz 2002-01-28 tzcode2002a.tar tzdata2002a.tar 2002-01-28 tzcode2002b.tar.gz tzdata2002b.tar.gz 2002-04-04 tzcode2002c.tar.gz tzdata2002c.tar.gz 2002-10-15 tzcode2002d.tar.gz tzdata2002d.tar.gz 2003-03-24 tzcode2003a.tar.gz tzdata2003a.tar.gz 2003-09-16 tzcode2003b.tar.gz tzdata2003b.tar.gz 2003-09-16 tzcode2003c.tar.gz tzdata2003c.tar.gz 2003-10-06 tzcode2003d.tar.gz tzdata2003d.tar.gz 2003-12-15 tzcode2003e.tar.gz tzdata2003e.tar.gz 2004-05-27 tzcode2004a.tar.gz tzdata2004a.tar.gz 2004-07-19 tzcode2004b.tar.gz tzdata2004b.tar.gz 2004-08-11 tzcode2004c.tar.gz only 2004-09-22 tzdata2004d.tar.gz only 2004-09-13 tzcode2004d.tar.gz only 2004-10-11 tzcode2004e.tar.gz tzdata2004e.tar.gz 2004-10-21 tzcode2004f.tar.gz only 2004-11-02 tzcode2004g.tar.gz tzdata2004g.tar.gz 2004-12-07 tzcode2004h.tar.gz only 2004-12-14 tzcode2004i.tar.gz only 2005-01-01 tzcode2005a.tar.gz tzdata2005a.tar.gz 2005-01-10 tzcode2005b.tar.gz tzdata2005b.tar.gz 2005-01-17 tzcode2005c.tar.gz tzdata2005c.tar.gz 2005-01-31 tzcode2005d.tar.gz only 2005-02-10 tzcode2005e.tar.gz tzdata2005e.tar.gz 2005-03-01 tzcode2005f.tar.gz tzdata2005f.tar.gz 2005-03-14 tzcode2005g.tar.gz tzdata2005g.tar.gz 2005-04-04 tzcode2005h.tar.gz tzdata2005h.tar.gz 2005-04-21 tzdata2005i.tar.gz only 2005-06-13 tzcode2005j.tar.gz tzdata2005j.tar.gz 2005-07-14 tzcode2005k.tar.gz tzdata2005k.tar.gz 2005-08-22 tzcode2005l.tar.gz tzdata2005l.tar.gz 2005-08-29 tzcode2005m.tar.gz tzdata2005m.tar.gz 2005-10-03 tzcode2005n.tar.gz tzdata2005n.tar.gz 2005-11-28 tzcode2005o.tar.gz tzdata2005o.tar.gz 2005-12-05 tzcode2005p.tar.gz tzdata2005p.tar.gz 2005-12-13 tzcode2005q.tar.gz tzdata2005q.tar.gz 2005-12-27 tzcode2005r.tar.gz tzdata2005r.tar.gz 2006-01-30 tzcode2006a.tar.gz tzdata2006a.tar.gz 2006-02-20 tzdata2006b.tar.gz tz32code2006b.tar.gz tz64code2006b.tar.gz 2006-04-03 tzcode2006c.tar.gz tzdata2006c.tar.gz 2006-04-17 tzcode2006d.tar.gz tzdata2006d.tar.gz 2006-05-01 tzcode2006e.tar.gz tzdata2006e.tar.gz 2006-05-01 tzcode2006f.tar.gz tzdata2006f.tar.gz 2006-05-08 tzcode2006g.tar.gz tzdata2006g.tar.gz 2006-07-24 tzcode2006h.tar.gz only 2006-08-07 tzcode2006i.tar.gz only 2006-08-21 tzcode2006j.tar.gz tzdata2006j.tar.gz 2006-08-28 tzcode2006k.tar.gz tzdata2006k.tar.gz 2006-09-18 tzdata2006l.tar.gz only 2006-10-02 tzcode2006m.tar.gz tzdata2006m.tar.gz 2006-10-10 tzcode2006n.tar.gz tzdata2006n.tar.gz 2006-11-06 tzcode2006o.tar.gz tzdata2006o.tar.gz 2006-11-27 tzcode2006p.tar.gz tzdata2006p.tar.gz 2007-01-08 tzcode2007a.tar.gz tzdata2007a.tar.gz 2007-02-12 tzcode2007b.tar.gz tzdata2007b.tar.gz 2007-02-26 tzcode2007c.tar.gz tzdata2007c.tar.gz 2007-03-20 tzcode2007d.tar.gz tzdata2007d.tar.gz 2007-04-02 tzcode2007e.tar.gz tzdata2007e.tar.gz 2007-05-07 tzcode2007f.tar.gz tzdata2007f.tar.gz 2007-08-20 tzcode2007g.tar.gz tzdata2007g.tar.gz 2007-10-01 tzcode2007h.tar.gz tzdata2007h.tar.gz 2007-11-01 tzdata2007i.tar.gz only 2007-12-03 tzcode2007j.tar.gz tzdata2007j.tar.gz 2007-12-31 tzcode2007k.tar.gz tzdata2007k.tar.gz 2008-03-08 tzcode2008a.tar.gz tzdata2008a.tar.gz 2008-03-24 tzdata2008b.tar.gz only 2008-05-27 tzdata2008c.tar.gz only 2008-07-07 tzdata2008d.tar.gz only 2008-07-28 tzcode2008e.tar.gz tzdata2008e.tar.gz 2008-09-15 tzdata2008f.tar.gz only 2008-10-06 tzcode2008g.tar.gz tzdata2008g.tar.gz 2008-10-13 tzcode2008h.tar.gz tzdata2008h.tar.gz 2008-10-27 tzdata2008i.tar.gz only 2009-01-21 tzcode2009a.tar.gz tzdata2009a.tar.gz 2009-02-09 tzcode2009b.tar.gz tzdata2009b.tar.gz 2009-03-16 tzdata2009c.tar.gz only 2009-03-23 tzcode2009d.tar.gz tzdata2009d.tar.gz 2009-04-06 tzcode2009e.tar.gz tzdata2009e.tar.gz 2009-04-13 tzdata2009f.tar.gz only 2009-04-27 tzdata2009g.tar.gz only 2009-05-26 tzcode2009h.tar.gz tzdata2009h.tar.gz 2009-07-08 tzcode2009i.tar.gz tzdata2009i.tar.gz 2009-07-18 tzdata2009j.tar.gz only 2009-07-20 tzcode2009k.tar.gz tzdata2009k.tar.gz 2009-08-17 tzdata2009l.tar.gz only 2009-09-08 tzdata2009m.tar.gz only 2009-09-28 tzdata2009n.tar.gz only 2009-10-19 tzdata2009o.tar.gz only 2009-10-26 tzdata2009p.tar.gz only 2009-11-02 tzcode2009q.tar.gz tzdata2009q.tar.gz 2009-11-09 tzcode2009r.tar.gz tzdata2009r.tar.gz 2009-11-16 tzdata2009s.tar.gz only 2009-12-21 tzcode2009t.tar.gz tzdata2009t.tar.gz 2009-12-28 tzdata2009u.tar.gz only 2010-01-18 tzdata2010a.tar.gz only 2010-01-25 tzdata2010b.tar.gz only 2010-02-16 tzcode2010a.tar.gz only 2010-03-01 tzcode2010c.tar.gz tzdata2010c.tar.gz 2010-03-08 tzdata2010d.tar.gz only 2010-03-08 tzdata2010e.tar.gz only 2010-03-22 tzcode2010f.tar.gz tzdata2010f.tar.gz 2010-03-29 tzdata2010g.tar.gz only 2010-04-05 tzdata2010h.tar.gz only 2010-04-19 tzdata2010i.tar.gz only 2010-05-10 tzcode2010j.tar.gz tzdata2010j.tar.gz 2010-07-26 tzcode2010k.tar.gz tzdata2010k.tar.gz 2010-08-16 tzcode2010l.tar.gz tzdata2010l.tar.gz 2010-09-27 tzcode2010m.tar.gz tzdata2010m.tar.gz 2010-10-25 tzcode2010n.tar.gz tzdata2010n.tar.gz 2010-11-01 tzdata2010o.tar.gz only 2011-01-24 tzcode2011a.tar.gz tzdata2011a.tar.gz 2011-02-07 tzcode2011b.tar.gz tzdata2011b.tar.gz 2011-03-07 tzcode2011c.tar.gz tzdata2011c.tar.gz 2011-03-14 tzcode2011d.tar.gz tzdata2011d.tar.gz 2011-04-01 tzcode2011e.tar.gz tzdata2011e.tar.gz 2011-04-25 tzcode2011g.tar.gz tzdata2011g.tar.gz 2011-06-27 tzdata2011h.tar.gz only 2011-08-29 tzcode2011i.tar.gz tzdata2011i.tar.gz 2011-09-12 tzdata2011j.tar.gz only 2011-09-26 tzdata2011k.tar.gz only 2011-10-10 tzdata2011l.tar.gz only -zefram

5 5

Fixing make check output...
by Kevin Lyda Oct. 13, 2011

Oct. 13, 2011

To get make check to run on Ubuntu, I had to do the following: apt-get install w3-recs sp cp -a /usr/share/doc/w3-recs/html/www.w3.org/TR/1999/REC-html401-19991224 . find REC-html401-19991224 -name '*.gz' -print0 | xargs -0 gunzip I then copied the command make check wanted to run and tweaked it like so: SGML_CATALOG_FILES=HTML4.cat SGML_SEARCH_PATH=REC-html401-19991224/ SP_CHARSET_FIXED=YES SP_ENCODING=UTF-8 nsgmls -s -B -wall -wno-unused-param tz-art.htm tz-link.htm I'm not really sure what tz-art.htm is for, but this is the diff required to make it actually pass... diff --git a/tz-art.htm b/tz-art.htmindex 902371e..f3064ee 100644--- a/tz-art.htm+++ b/tz-art.htm@@ -213,7 +213,7 @@ Supernaw.</td></tr> <tr><td>ID</td><td>272</td></tr> <tr><td>Total Time</td><td>73:05</td></tr> <tr><td>Notes</td><td>Includes the song "Twilight Time Zone."</td></tr>-<tr><td><a href="http://www.allmusic.com/cg/amg.dll?p=amg&sql=10:w9fpxzykldje">AMG Ra+<tr><td><a href="http://www.allmusic.com/cg/amg.dll?p=amg&sql=10:w9fpxzykldje">AM <tr><td>ADO Rating</td><td>2 stars</td></tr> <tr><td> </td></tr>@@ -224,7 +224,7 @@ Supernaw.</td></tr> <tr><td>Label</td><td>Columbia</td></tr> <tr><td>ID</td><td>CK-8905</td></tr> <tr><td>Total Time</td><td>45:36</td></tr>-<tr><td><a href="http://www.allmusic.com/cg/amg.dll?p=amg&sql=10:gifqxqt5ld0e">AMG Ra+<tr><td><a href="http://www.allmusic.com/cg/amg.dll?p=amg&sql=10:gifqxqt5ld0e">AM <tr><td>ADO Rating</td><td>1.5 stars</td></tr> <tr><td>Notes<td>The title song is also available on "Bob Dylan's Greatest Hits" and <tr><td> </td></tr>@@ -235,7 +235,7 @@ Supernaw.</td></tr> <tr><td>Label</td><td>Universal Jazz France</td></tr> <tr><td>ID</td><td>B0012688-02</td></tr> <tr><td>Total Time</td><td>42:31</td></tr>-<tr><td><a href="http://www.allmusic.com/cg/amg.dll?p=amg&sql=10:3bftxzw0ldhe"</a>AMG+<tr><td><a href="http://www.allmusic.com/cg/amg.dll?p=amg&sql=10:3bftxzw0ldhe">AM <tr><td>ADO Rating</td><td>2.5 stars</td></tr> <tr><td>Notes<td>Includes the song "Fire and Wood" with the lyric "The clocks were turned back you remeber/Think it's still November." -- Kevin Lyda Dublin, Ireland US Citizen overseas? We can vote. Register now: http://www.votefromabroad.org/

1 0

32 municipalities in Mato Grosso, Brazil not to observe DST
by Steffen Thorsen Oct. 13, 2011

Oct. 13, 2011

According to many news sources, 32 municipalities in Mato Grosso will change their clocks for DST the coming weekend, so this will split Mato Grosso into two different zones. One example: http://www.redenergia.com/concessionarias/noticias/5476/Concessionarias-Ger… Biggest city we could find among them was Barra do Garças. Our view of it: http://www.timeanddate.com/news/time/brazil-time-changes-2011.html Best regards, Steffen Thorsen - timeanddate.com

1 0

400-year-repeat edge cases
by Zefram Oct. 12, 2011

Oct. 12, 2011

For tzfile readers that make use of the 400-year cycle where a rule can't be expressed in POSIX-TZ form, I'm concerned that going exactly 400 years beyond the last rule change isn't sufficient. The year at the start of that cycle, the year that would otherwise have been the last one mentioned in the tzfile, might be contaminated by one-shot rules, making it an invalid example of the cyclical rules. Also, the transitions included for the last year of the cycle don't adequately delimit the whole cycle. I propose to avoid these edge problems by adding an extra two years of explicit observations when listing 400 years of the future. One extra year would probably suffice; two certainly does, and allows for conservative tzfile readers to drop poorly-delimited observations at the ends. Think of them as telomeres. Attached patch implements. This affects about six of the tzfiles. (Between five and seven, depending on which of my previous patches you applied.) They mostly get 36 bytes longer. -zefram

1 0

FW: missing extension rules
by Olson, Arthur David (NIH/NCI) [E] Oct. 12, 2011

Oct. 12, 2011

I'm forwarding this message from Zefram; since sending it, Zefram has subscribed to the time zone mailing list. --ado -----Original Message----- From: Zefram [mailto:zefram@fysh.org] Sent: Wednesday, September 28, 2011 6:10 To: tz(a)lecserver.nci.nih.gov Subject: missing extension rules I've found a problem with the tzfiles for Africa/Cairo and America/Argentina/San_Luis. They both show a last known transition in the recent past, and surprisingly lack a POSIX-TZ-format rule for extending the zone into the future. My tzfile parser treats a zone with no extension rule as being undefined for any time following the last explicit transition, so for these two zones it reckons the zone is undefined for the present. In the source files they're each currently configured to observe a set of DST rules, and the ruleset has no transitions configured for the future. So for the present and foreseeable future, the zone is on a constant offset with no DST transitions. The tzfile reflects that by showing no transitions from the present up to 2038 (where zic always fills in a complete set of expected transitions). It should be trivial to also reflect that foreseen behaviour in a POSIX-TZ string that just gives a fixed offset and no DST rule. For example, Africa/Cairo should clearly have "EET-2". I could have a go at a zic patch to fix this, if the regular zic hackers would like to work that way. For America/Argentina/San_Luis there's an extra wrinkle: the last known transition is a transition *to* DST. Its fixed-offset foreseeable behaviour therefore has a fixed is_dst=1, which is moderately silly. It's arguable that in this case it would be incorrect to give a "WARST3" extension rule, because that doesn't accurately express the DST status. Since that DST transition was in 2009, it's also a good bet that they haven't stayed continuously on DST since then, of course. -zefram

3 5

Re: [tz] temporary timezone database home ...
by David Braverman Oct. 11, 2011

Oct. 11, 2011

Um...a statement in a creative work that says "this work is in the public domain" generally *does* put it in the public domain. Anyone who owns property is free to give it away. In the case of the U.S. government, since the government (in theory) is owned by the citizens of the U.S., as a matter of public policy U.S. government works are in the public domain. 17 USC 105 states this explicitly, but does allows the U.S. government to hold copyrights by devise (for example, through a gift or a tax lien). I believe ADO had to clarify that the tzinfo database fell into the first category and not the second; thus, the "public domain" language in the tzinfo files. And IAAL (just not practicing). :) David Braverman http://www.wx-now.com/

4 3

tzdata repo at Google Code is gone
by Øyvind A. Holm Oct. 11, 2011

Oct. 11, 2011

There used to be an svn repo on http://code.google.com/p/tzdata/ containing the tz data in various formats (csv, json, xml, etc), but now it's gone. Does anyone know what happened to it? Anyway, on 2011-10-08 I converted it from Svn to Git, and this repo (with full history, newest version is tzdata2011j) is stored at https://gitorious.org/tz/tzdata . It can be cloned with git clone git://gitorious.org/tz/tzdata.git Regards, Øyvind

1 0

tzdata2011l.tar.gz
by Robert Elz Oct. 10, 2011

Oct. 10, 2011

The file ... ftp://munnari.oz.au/pub/tzdata2011l.tar.gz ...is now available; this reflects changes circulated last week on the time zone mailing list. There are just 2 changes that cause different generated tzdata files from zic, to Asia/Hebron and Pacific/Fiji - the possible change for Bahia, Brazil is included, but commented out. Compared with the diff I sent out last week, this version also includes attributions for the sources for the changes (in much the same format as ado used, but the html tags have not been checked, verified, or used in any way at all, so if there are errors there, please let me know.) Unfortunately, there are no signatures, it turns out that I have not used any form of PGP in so long that getting my keys into a form where they're usable by gpg is somewhat of a challenge - so most probably I'll just generate a new key (as was suggested, and which is obviously the sane approach) for tz distributions - the down side is that at least initially it isn't going to be signed (trusted) by anyone at all... To compensate for this lack of signatures, I'm appending (in this message) a list of digest values, crypto hash function digests generated by a number of different algorithms (all from the NetBSD pkgsrc "digest" program). Those ought to give a fair degree of confidence that the tarball has not been compromised, and by distributing them in this message, essentially no way for anyone to compromise the digest values (which is the one thing that a proper signature would ensure). Lastly, for now, because people seem to be mirroring ftp://munnari.oz.au/pub/oldtz/ I have included the current versions of the data & code files there, as well as their normal home in ftp://munnari.oz.au/pub - previously the oldtz directory contained only the obsolete tarballs. But thanks to Joseph S. Myers, the oldtz directory now includes a few extra archives that I had been missing, including the extremely elusive tzcode2003b which had been replaced before I even new it existed (and no, you don't really want it, it contained a fairly serious bug, which is why it was replaced so quickly...) kre MD5 (tzdata2011l.tar.gz) = bae1b93673e1aef80186c90dfd493f1c RMD160 (tzdata2011l.tar.gz) = b933711b06246c9d452d846a193b53295a966287 SHA1 (tzdata2011l.tar.gz) = c6740ec9645b78750e2109b6d42cd283e16988d7 SHA512 (tzdata2011l.tar.gz) = a1d2dd68ddd3822f94cd817a3e70277e6e9e347c12aa788533d36ad0ad03f0ec39d925301d64c6ab27825212dffd0ec03c3944096ef479318815a8e1f362c841 TIGER (tzdata2011l.tar.gz) = f0578e0cab5f39f13c49b076cc2955da95e9111b98ffe57c WHIRLPOOL (tzdata2011l.tar.gz) = aa6812740e077e064de7348f2deb15e1bfe8cbb93a336dde58e625b76f4832c8c6601bb06437ac04c05b232f142b1119841f5bab50656907b3a1459906c818a1

7 8

Update docs/comments regarding move from elsie to iana
by Kevin Lyda Oct. 10, 2011

Oct. 10, 2011

There are several places in the code that refer to the ftp server and mailing list on elsie. The following patch points people at the currently correct places. Kevin -- Kevin Lyda Dublin, Ireland US Citizen overseas? We can vote. Register now: http://www.votefromabroad.org/

1 0

Digital signing (was Re: Proposed time zone package changes ...)
by Bennett Todd Oct. 9, 2011

Oct. 9, 2011

For signing the data files, I'm fond of pgp, with gpg being the implementation I trust best. Sadly, standardization efforts seem to end up being used to add sponsorship for certificate signing authorities, we all have seen how well that has worked for SSL. Hope you can go with pgp; the current Certificate Authority fiasco follows as expected from the observation that trust doesn't scale. As for details, I don't know anything wrong with the default algorithms that gpg uses. But ideally you shouldn't be using your own key directly, but rather a new, project-specific key for the project's official contact email address. You can start it off by signing it with your key, and other folks can add signatures after verifying the fingerprint with you offline.

3 2

Another mirror + mirror shell script
by Sebastian Majstorovic Oct. 9, 2011

Oct. 9, 2011

I'd be glad to contribute another mirror, FTP and HTTP, based in Germany: ftp://tzmirror.appealingapps.de http://tzmirror.appealingapps.de If anyone else wants to setup a mirror, here's a one-line shell script which sets one up: /usr/bin/lftp -c 'open -e "mirror --parallel=5 -e -x ^[^t][^z] -i oldtz /pub /path/to/local/directory" munnari.oz.au' If you run it daily, e.g. as a cron, the files on the mirror are always kept up-to-date. Best Regards Sebastian

1 1

Re: [tz] A history maintaining repository for tzdata
by Kevin Lyda Oct. 8, 2011

Oct. 8, 2011

On Sat, Oct 8, 2011 at 08:43, Bill Sommerfeld <sommerfeld(a)alum.mit.edu> wrote: > An ancestor of the current tzdata was posted to the usenet mod.sources > newsgroup with a date of March 7, 1986; I found copies at: Fantastic. I got the idea that Usenet was the next place to go, but I had to catch a bus so I put the initial part up to let people know what I was working on. Annoyingly the reason I threw my work up on github in a hurry last night was because I was going to Galway last night. Now I'm here and while I have the CDROM *cases* of the first three volumes of the Walnut Creek Usenet Source Code archive, I suspect the CDROMs themselves are back in Dublin. Argh. Anyway, thanks for the links. Any additional early releases I find will have similar style commits - correct authors, timestamps and message ids. I'm downloading the comp.sources.unix archives now and will get the mod.sources archives next. Was settz posted on alt.sources prior to mod.sources? As for the points raised by other posters - US based hosts and preserving SCCS history... First, I chose github just for a quick place to push the repo. I obviously have the full copy (and more importantly the scripts used to generate it which I'll push up later today) and I'm in Ireland. It lives in a VM on my laptop and I've pushed out all the materials I used to build the repo to a few other machines in other countries. I have two thoughts on US based servers. First, there are a host of other projects on github that have these files in some form so I'm not really concerned. Second, this repository is a work in progress that folks here can evaluate in terms of its structure (see the README for the issues I'd like feedback on). It's my belief that I should send my repo generation scripts and supporting metadata to kre (or ado or eggert) and have them generate the repo that people actually use. Lastly I completely agree that the SCCS history should be preserved if possible. However I don't think I can get access to it without cause ado or eggert a lot of problems. I think I know how to weave in SCCS commits into the resulting git tree. Essentially the algorithm will go something like this (in shell/pythony pseudo code): for commit, next_commit in list_of_tags; do start_date=# get date of this commit end_date=# get date of next commit # get list of changes in sccs repository between those dates # for each change, get the date, commit message and diff # apply diff to repo, commit with correct date and metadata git rebase next_commit done How to do this will depend on what ado actually uses - SCCS or RCS or if he migrated from one to the other at some point. I also suspect there are some tweaks that will be required (I'm not sure how rebase deals with empty commits for instance and if everything is working correctly every rebase will cause an empty commit). And obviously when that happens everyone would need to resync their tree. But I'm happy to help make it happen. In the meantime I'll get the scripts and data kre needs to generate a repo that he can make a "blessed" repository for his own use (and wherever he chooses to publish it - if anywhere). Well, first I'll get the pre-93 sources and the tzcode in there first. Kevin

1 0

Re: [tz] Source material used by ACS atlas book editions
by Alois Treindl Oct. 7, 2011

Oct. 7, 2011

Stephen I don't quite understand why you fear this, but I am not a lawyer and not familiar with US law. I will use other channels for such contributions, if there should be any. As material for Olson's and Eggert's defense I think these quotes of Shanks's sources are relevant. Later (current) editions of the books do no longer mention any sources, only the old editions do. They confirm in writing that Shanks copied most of his data from other published sources. Knowledge of the sources will make it rather easy to clean up TZ files from quotes of Shanks. I think personally that no such cleanup should happen. The lawsuit should be fought and will be won by Olson and Eggert, as their use they make of Shanks' data is fully legitimate. Stephen Colebourne wrote: > Please don't send more information like this. You may contaminate the > new list and expand the lawsuit. > Stephen > >

1 0

(no subject)
by Paw Boel Nielsen Oct. 7, 2011

Oct. 7, 2011

I suggest you let your opinion known here: http://www.facebook.com/pages/Astrolabe-Astrology-Software-and-Services/525…

4 3

Source material used by ACS atlas book editions
by Alois Treindl Oct. 7, 2011

Oct. 7, 2011

I have taken some snapshots to review the sources used for the data collection in ACS American Atlas and International Atlas. The sources are referenced well in the bibliography of the 1st edition of International Atlas. Later editions do not give such information anymore. For American Atlas, the sources are mentioned to some extent in prefaces, acknowledgments, notes and in an advertising found in International Atlas. I think this material can be of relevance to form an opinion about the solidity of the Astrolabe lawsuit against Olson and Eggert.

1 0

mailing list archives
by Zefram Oct. 7, 2011

Oct. 7, 2011

I see the webbified tz(a)iana.org mailing list archive has been prepopulated with tzarchive.gz from elsie. ++ to whoever did that. But tzarchive.gz is incomplete: it bizarrely stopped being updated in May. In light of recent revelations, it's now notable that the last update coincides approximately with Astrolabe sending a takedown notice (2011-05-12 according to the legal complaint). Anyway, it would be nice if the missing five months could be imported too. It's available at <http://news.gmane.org/gmane.comp.time.tz>. -zefram

1 0

Re: [tz] temporary timezone database home ...
by Zefram Oct. 7, 2011

Oct. 7, 2011

If we're going the git route (which is a good idea), I suggest *not* using github. Github has terms of service that can change without notice in problematic ways. The tz collective is large enough that there should be no problem in hosting our own git server, such as the one that Yann Droneaud has provided as a prototype. Ideally we'd have a git server hosted at munnari. I think a single repository covering both code and data files would be better than separate code and data repositories. The two parts are too interconnected to work with separately. Btw, I was one of the unlucky sods (maybe the only unlucky sod?) who, having joined tz@elsie only a week ago, was omitted from the initial subscriber list for tz@iana. Good work getting things going so quickly. -zefram

1 0

Fwd: temporary timezone database home ...
by Alex Mayorga Adame Oct. 7, 2011

Oct. 7, 2011

---------- Forwarded message ---------- From: Alex Mayorga Adame <alex.mayorga(a)gmail.com> Date: Fri, 7 Oct 2011 00:48:50 -0500 Subject: Re: [tz] temporary timezone database home ... To: Robert Elz <kre(a)munnari.oz.au> Hope this nonsense won't grow into to much of a burden for "Olson et al" =( Thanks on your efforts Robert! Can this be made into a .torrent? I do not have permanent hosting other than DynDNS to my laptop in .mx but would gladly contribute some bandwidht if that would help in any way. Alex Mayorga Adame On 10/6/11, Robert Elz <kre(a)munnari.oz.au> wrote: > First, I am assuming this copy of the list is actually functioning, > (and I've just received jhawk's message which demonstrates that it is) > I don't believe it has been used for actual messages before that one, > but as ado has indicated that the list at elsie has been (for now > anyway) terminated - and given the plan was to migrate from it eventually > anyway, may never return, we can but hope this version of the list > is functional. > > Some of you who receive this message may have been removed from the > elsie version of the list recently, or altered your subscription details > - if that applies to you, use the iana.org message sent on the 1st of > this month to all subscribers to their list for instructions on how to > modify or delete your subscription. > > Don't send requests to me (or anyone else on the list) there's nothing I > (or we) can do about it - and most certainly, do not send requests to the > list itself asking to be removed. > > Unfortunately, there are probably a few people who were added to the elsie > list since it was cloned at iana.org but there's nothing much we can do > about that - if anyone is contacted by anyone who believes they should be > on the list, but is no longer receiving messages, direct them to the iana > website for list subscriptions. > > Next, while elsie's ftp server is shut down, munnari.oz.au isn't, and the > tz database & code remains available from here. Further, I will not > respond to requests from (almost) anyone to cease making those files > available (including Arthur and Paul - but by all means feel free to try > if you need to to satisfy some obligation to cease making the data > available - I'll ignore you, but you will at least have used every > reasonable > effort...) > > Second, regardless of this, the world's governments continue to adjust > their view of their local timezones & summer time adjustments, so we > need to continue updating the database (at least). There are several > updates that will be needed soon. > > For now, until someone else volunteers, I'm prepared to make the updates, > in much the same way that Arthur did, and then make new releases available > from munnari's ftp server. I suspect that it is unlikely that either Arthur > or Paul will be able to assist much with this in the coming months, so > I'm hoping that others will assist where possible. > > For now, I'm aware of changes needed for Armenia, Fiji, Bolivia, Brazil, > and of course, the changes that (might be) needed for Russia. If there's > anything else I missed, please let me know. > > Unfortunately, I don't have the sccs (or is it rcs or something these days) > master files, so I won't be able to do quite the same job that Arthur did, > but I can keep all versions so they can be checked into a version control > system later. > > It would be good if a few others, especially people in jurisdictions that > tend not to simply bow down to US court rulings, would keep copies of the > code and data, and make them publicly available via ftp or http (this > is not of huge public interest, the resources needed to provide this > service should not be very noticeable). > > All I know of the lawsuit is what jhawk's message indicated - eventually > I assume we'll find out what trademark or patent that someone believes is > being infringed (a little hard to believe either, but who knows...) > > The URL's of the current versions of the files from munnari.oz.au are ... > > ftp://munnari.oz.au/pub/tzcode2011i.tar.gz > ftp://munnari.oz.au/pub/tzdata2011k.tar.gz > > and of course, the historical files (most versions that were ever previously > released) are in ftp://munnari.oz.au/pub/oldtz/ > > kre > > > -- Enviado desde mi dispositivo móvil

1 0

Fiji Daylight saving
by Sean Evans Oct. 5, 2011

Oct. 5, 2011

Fijidaylight saving time 2011/2012 has been announced: “Prepare to advance your clocks one hour ahead of the standard time, because Fiji’s daylight saving period is about to start from October 23. Minister for Labour, Industrial Relations and Employment, Mr Filipe Bole made the Daylight Saving Order saying this initiative in Fiji has benefitted both the private and public sector over the years. “People of Fiji are urged to take full advantage of the daylight saving period time because this allows more quality time for recreation and to be with family, while also increasing overall economic activity, work and agricultural productivity,” Mr Bole said. Members of the public are reminded to change their time to one hour in advance at 2am to 3am on October 23, 2011 and one hour back at 3am to 2am on February 26 next year. Ends…” Original news release: http://www.fiji.gov.fj/index.php?option=com_content&view=article&id=4966:da… Best regards, Sean.

1 0

Bolivia plan to implement DST
by Alexander Krivenyshev Oct. 4, 2011

Oct. 4, 2011

According to Bolivia Ministry of Hydrocarbons and Energy web site (hidrocarburos.gob.bo) and various media reports: http://www.la-razon.com/version.php?ArticleId=136181&EditionId=2630 Bolivia plan to implement DST "every year" between September and March (in the spring and summer) as an alternative savings and efficient use of electricity. http://www.worldtimezone.com/dst_news/dst_news_bolivia02.html Alexander Krivenyshev - World Time Zone http://www.worldtimezone.com

1 1