November 2007 - tz - lists.iana.org

proposed tz patch for Venezuela, St Barthelemy, St Martin (Fr.), etc.
by Paul Eggert Nov. 29, 2007

Nov. 29, 2007

Here's a proposed patch to the tz database to accommodate Venezuela's latest plans, along with the other stuff that has been accumulated recently. The following change affects near-future time stamps. * Venezuela is changing their clocks on December 9 at 03:00, instead of the January 1 at 00:00 that we thought. (Thanks to John Stainforth for the heads-up.) The following change affects the country database, but not the time data. * New links America/St_Barthelemy and America/Marigot, for the new countries St Barthelemy and St Martin (French part). (Thanks to Mark Davis for this.) The following changes affect commentary only. * Add a comment about Iran's readoption of DST. (Thanks to Roozbeh Pournader for this.) * Fix some broken links in tz-link.htm, and remove some dead links. (Thanks to Bert van Heerde for this.) Changes include: - Update links to calconnect, ICU. - Remove links to xmlDate, Austria National Metrology Institute database. - draft-ietf-dhc-timezone-option-04.txt is now Internet RFC 4833. =================================================================== RCS file: RCS/asia,v retrieving revision 2007.9 retrieving revision 2007.9.0.1 diff -pu -r2007.9 -r2007.9.0.1 --- asia 2007/10/30 14:28:10 2007.9 +++ asia 2007/11/29 08:48:52 2007.9.0.1 @@ -577,6 +577,15 @@ Zone Asia/Jayapura 9:22:48 - LMT 1932 No # daylight saving time ... # http://uk.reuters.com/article/oilRpt/idUKBLA65048420070916 # +# From Roozbeh Pournader (2007-11-05): +# This is quoted from Official Gazette of the Islamic Republic of +# Iran, Volume 63, Number 18242, dated Tuesday 1386/6/24 +# [2007-10-16]. I am doing the best translation I can:... +# The official time of the country will be moved forward for one hour +# on the 24 hours of the first day of the month of Farvardin and will +# be changed back to its previous state on the 24 hours of the +# thirtieth day of Shahrivar. +# # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S Rule Iran 1978 1980 - Mar 21 0:00 1:00 D Rule Iran 1978 only - Oct 21 0:00 0 S =================================================================== RCS file: RCS/northamerica,v retrieving revision 2007.9 retrieving revision 2007.9.0.1 diff -pu -r2007.9 -r2007.9.0.1 --- northamerica 2007/10/30 14:28:11 2007.9 +++ northamerica 2007/11/29 08:48:52 2007.9.0.1 @@ -2303,6 +2303,10 @@ Zone America/Grenada -4:07:00 - LMT 1911 # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Guadeloupe -4:06:08 - LMT 1911 Jun 8 # Pointe a Pitre -4:00 - AST +# St Barthelemy +Link America/Guadeloupe America/St_Barthelemy +# St Martin (French part) +Link America/Guadeloupe America/Marigot # Guatemala # =================================================================== RCS file: RCS/southamerica,v retrieving revision 2007.8 retrieving revision 2007.8.0.1 diff -pu -r2007.8 -r2007.8.0.1 --- southamerica 2007/10/01 14:05:30 2007.8 +++ southamerica 2007/11/29 08:48:52 2007.8.0.1 @@ -1107,19 +1107,17 @@ Zone America/Montevideo -3:44:44 - LMT 1 # Venezuela # -# From Kiraz Janicke (2007-09-25), in -# http://www.venezuelanalysis.com/analysis/2645: -# The proposal ... involves turning the clock back half an hour from -# +4.00 Greenwich Mean Time (GMT), to +4.30GMT, the time zone -# Venezuela had until December 31, 1964, when the current time zone -# was adopted. The change was due to take place on September 17 and -# then on September 24, but has since been postponed until December -# 31, to allow for compliance with international organizations, such -# as the International Office of Weights and Measures. +# From John Stainforth (2007-11-28): +# ... the change for Venezuela originally expected for 2007-12-31 has +# been brought forward to 2007-12-09. The official announcement was +# published today in the "Gaceta Oficial de la Republica Bolivariana +# de Venezuela, numero 38.819" (official document for all laws or +# resolution publication) +# http://www.globovision.com/news.php?nid=72208 # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Caracas -4:27:44 - LMT 1890 -4:27:40 - CMT 1912 Feb 12 # Caracas Mean Time? -4:30 - VET 1965 # Venezuela Time - -4:00 - VET 2008 + -4:00 - VET 2007 Dec 9 03:00 -4:30 - VET =================================================================== RCS file: RCS/iso3166.tab,v retrieving revision 2007.1 retrieving revision 2007.1.0.1 diff -pu -r2007.1 -r2007.1.0.1 --- iso3166.tab 2007/01/08 17:17:29 2007.1 +++ iso3166.tab 2007/11/29 08:48:52 2007.1.0.1 @@ -6,7 +6,7 @@ # # This file contains a table with the following columns: # 1. ISO 3166-1 alpha-2 country code, current as of -# ISO 3166-1 Newsletter No. V-12 (2006-09-26). See: +# ISO 3166-1 Newsletter VI-1 (2007-09-21). See: # <a href="http://www.iso.org/iso/en/prods-services/iso3166ma/index.html"> # ISO 3166 Maintenance agency (ISO 3166/MA) # </a>. @@ -47,6 +47,7 @@ BG Bulgaria BH Bahrain BI Burundi BJ Benin +BL St Barthelemy BM Bermuda BN Brunei BO Bolivia @@ -159,6 +160,7 @@ MA Morocco MC Monaco MD Moldova ME Montenegro +MF St Martin (French part) MG Madagascar MH Marshall Islands MK Macedonia =================================================================== RCS file: RCS/zone.tab,v retrieving revision 2007.7 retrieving revision 2007.7.0.1 diff -pu -r2007.7 -r2007.7.0.1 --- zone.tab 2007/08/20 14:45:10 2007.7 +++ zone.tab 2007/11/29 08:48:52 2007.7.0.1 @@ -77,6 +77,7 @@ BG +4241+02319 Europe/Sofia BH +2623+05035 Asia/Bahrain BI -0323+02922 Africa/Bujumbura BJ +0629+00237 Africa/Porto-Novo +BL +1753-06251 America/St_Barthelemy BM +3217-06446 Atlantic/Bermuda BN +0456+11455 Asia/Brunei BO -1630-06809 America/La_Paz @@ -250,6 +251,7 @@ MA +3339-00735 Africa/Casablanca MC +4342+00723 Europe/Monaco MD +4700+02850 Europe/Chisinau ME +4226+01916 Europe/Podgorica +MF +1804-06305 America/Marigot MG -1855+04731 Indian/Antananarivo MH +0709+17112 Pacific/Majuro most locations MH +0905+16720 Pacific/Kwajalein Kwajalein =================================================================== RCS file: RCS/tz-link.htm,v retrieving revision 2007.8 retrieving revision 2007.8.0.1 diff -pu -r2007.8 -r2007.8.0.1 --- tz-link.htm 2007/10/01 14:02:04 2007.8 +++ tz-link.htm 2007/11/29 08:48:52 2007.8.0.1 @@ -8,7 +8,7 @@ <meta http-equiv="Content-type" content='text/html; charset="US-ASCII"'> <meta name="DC.Creator" content="Eggert, Paul"> <meta name="DC.Contributor" content="Olson, Arthur David"> -<meta name="DC.Date" content="2007-08-17"> +<meta name="DC.Date" content="2007-11-29"> <meta name="DC.Description" content="Sources of information about time zones and daylight saving time"> <meta name="DC.Identifier" content="http://www.twinsun.com/tz/tz-link.htm"> @@ -152,7 +152,7 @@ Consortium</a> is promoting further work href="http://www.calconnect.org/publications/icalendartimezoneproblemsandrecommen…">iCalendar TIMEZONE Problems and Recommendations</a> offers guidelines and recommendations for the use of VTIMEZONE and <code>tz</code>.</li> -<li><a href="http://www.calconnect.org/dstlinks.html">Extended Daylight +<li><a href="http://www.calconnect.org/dstlinks.shtml">Extended Daylight Saving Time Links, Advisories and Changes</a> lists vendor material on recent daylight saving time changes.</li> <li><a @@ -198,9 +198,10 @@ available under both the <abbr>GPL</abbr License. DateTime::TimeZone also contains a script <code>tests_from_zdump</code> that generates test cases for each clock transition in the <code>tz</code> database.</li> -<li><a href="http://icu-project.org/"><abbr -title="International Components for Unicode">ICU</abbr></a> -contains a C/C++ library for internationalization that +<li><a href="http://icu-project.org/">International Components for +Unicode (<abbr>ICU</abbr>)</a> contains C/C++ and <a +href="http://en.wikipedia.org/wiki/Java_%28programming_language%29">Java</a> +libraries for internationalization that has a compiler from <code>tz</code> source into an <abbr>ICU</abbr>-specific format. <abbr>ICU</abbr> is freely available under a @@ -211,11 +212,6 @@ contains a class <code>org.joda.time.tz.ZoneInfoCompiler</code> that compiles <code>tz</code> source into a Joda-specific binary format. Joda Time is freely available under a <abbr>BSD</abbr>-style license.</li> -<li><a href="http://mozware.free.fr/devtools/xmlDate/">xmlDate</a> -contains <a -href="http://en.wikipedia.org/wiki/JavaScript">JavaScript</a> code that -parses <samp>tz</samp> source into an internal object that represents -a time zone. It is freely available under the GPL.</li> <li><a href="http://sourceforge.net/projects/pytz/">PyTZ - Python Time Zone Library</a> compiles <code>tz</code> source into <a href="http://www.python.org/">Python</a>. @@ -251,8 +247,7 @@ This library is freely available under t (<abbr title="Lesser General Public License">LGPL</abbr>)</a>, and is widely used in <abbr>GNU</abbr>/Linux systems.</li> <li><a href="http://www.bmsi.com/java/#TZ">ZoneInfo.java</a> -is a <code>tz</code> binary file reader written in <a -href="http://en.wikipedia.org/wiki/Java_%28programming_language%29">Java</a>. +is a <code>tz</code> binary file reader written in Java. It is freely available under the <abbr>LGPL</abbr>.</li> <li>Tcl, mentioned above, also contains a <code>tz</code> binary file reader.</li> @@ -420,10 +415,6 @@ href="http://www.aph.gov.au/LIBRARY/Pubs note on daylight saving time in Australia</a>. The Bureau of Meteorology publishes a list of <a href="http://www.bom.gov.au/climate/averages/tables/dst_times.shtml">Implementation Dates of Daylight Savings Time within Australia</a>.</dd> -<dt>Austria</dt> -<dd>The National Metrology Institute publishes a -table of <a href="http://www.metrologie.at/pdf/sommerzeit.pdf" -hreflang="de">daylight saving time in Austria (in German)</a>.</dd> <dt>Belgium</dt> <dd>The Royal Observatory of Belgium maintains a table of <a href="http://www.astro.oma.be/GENERAL/INFO/nli001a.html" @@ -500,9 +491,9 @@ Time Protocol</a> discusses how to synchronize clocks of Internet hosts.</li> <li><a -href="ftp://ftp.rfc-editor.org/internet-drafts/draft-ietf-dhc-timezone-option-04.…">A +href="ftp://ftp.rfc-editor.org/in-notes/rfc4833.txt">A Timezone Option for <abbr title="Dynamic Host Configuration Protocol">DHCP</abbr></a> -proposes a <a +specifies a <a href="http://www.dhcp.org/">DHCP</a> option for a server to configure a client's time zone and daylight saving settings automatically.</li> <li><a href="http://gauss.gge.unb.ca/GMT.UT.and.the.RGO.html">A Few @@ -608,8 +599,8 @@ abbreviations, identifiers, and formats. French translations for "Eastern European Summer Time", "<abbr title="Eastern European Summer Time">EEST</abbr>", and "Bucharest". <a -href="http://unicode.org/cldr/data/charts/by_type/names.zone.html">By-Type -Chart: names.zone</a> shows these values for many locales. +href="http://www.unicode.org/cldr/data/charts/by_type/names.metazone.html">By-Type +Chart: names.metazone</a> shows these values for many locales. <abbr>ICU</abbr> contains a mechanism for using this data.</li> <li>Alphabetic time zone abbreviations should not be used as unique identifiers for <abbr>UTC</abbr> offsets as they are ambiguous in

1 0

FW: Dead Links
by Olson, Arthur David (NIH/NCI) [E] Nov. 29, 2007

Nov. 29, 2007

I'm forwarding this message from Bert van Heerde, who is not on the time zone mailing list. Those of you who are on the time zone mailing list should direct replies appropriately. --ado From: Bert van Heerde [mailto:bert@insyde.nl] Sent: Tuesday, October 09, 2007 10:51 To: tz(a)lecserver.nci.nih.gov Subject: Dead Links Dear Twin Sun employee, I was looking for places to submit links for my site world-map.nl and saw your page and the request for corrections. I was a bit bored, so analyzed the page J Below you will find the deadlinks on the page: http://www.twinsun.com/tz/tz-link.htm Maybe this linkchecker can help you out: https://addons.mozilla.org/en-US/firefox/addon/532 since W3C tool http://validator.w3.org/checklink is a bit slow. Have nice day! Bert Dead Links: By-Type Chart: names.zone <http://unicode.org/cldr/data/charts/by_type/names.zone.html> daylight saving time in Austria (in German) <http://www.metrologie.at/pdf/sommerzeit.pdf> . xmlDate <http://mozware.free.fr/devtools/xmlDate/> Extended Daylight Saving Time Links, Advisories and Changes <http://www.calconnect.org/dstlinks.html> Redirects: FTP distribution <ftp://elsie.nci.nih.gov/pub/> archived older versions of code and data <ftp://munnari.oz.au/pub/oldtz/> Internet Calendaring and Scheduling Core Object Specification (iCalendar) <ftp://ftp.rfc-editor.org/in-notes/rfc2445.txt> announcements (in Hebrew) <ftp://ftp.cs.huji.ac.il/pub/tz/announcements/> . A Timezone Option for DHCP <ftp://ftp.rfc-editor.org/internet-drafts/draft-ietf-dhc-timezone-option -04.txt> Internet RFC 2822 <ftp://ftp.rfc-editor.org/in-notes/rfc2822.txt> HTTP <ftp://ftp.rfc-editor.org/in-notes/rfc2616.txt> Internet RFC 3339 <ftp://ftp.rfc-editor.org/in-notes/rfc3339.txt>

5 5

Japan's rules
by Chris Holt Nov. 28, 2007

Nov. 28, 2007

It seems that Japan is missing its latest rule. The last rule it has is <Rule> <Name>Japan</Name> <From>1950</From> <To>1951</To> <Type>-</Type> <In>May</In> <On>Sun>=1</On> <At>2:00</At> <Save>1:00</Save> <Letter>D</Letter> </Rule> And the timezone is defined as: <Zone> <Name>Asia/Tokyo</Name> <GMTOffset>9:00</GMTOffset> <Rules>Japan</Rules> <Format>J%sT</Format> <Until /> <Comment /> </Zone> This forces the user to use JDT as the timezone abbreviation even though I believe they currently don't do daylight savings time. It seems this should be updated to: <Zone> <Name>Asia/Tokyo</Name> <GMTOffset>9:00</GMTOffset> <Rules>Japan</Rules> <Format>J%sT</Format> <Until>1951</Until> <Comment /> </Zone> <Zone> <Name>Asia/Tokyo</Name> <GMTOffset>9:00</GMTOffset> <Rules>-</Rules> <Format>JST</Format> <Until /> <Comment /> </Zone> Does this make sense? Thanks, Christopher Holt Skyward Innovations, Inc. Office: (603) 206-4552 Cell: (603) 765-0945 cholt(a)skywardinnovations.com www.skywardinnovations.com The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer.

1 0

Should time zone info files be tagged with the tzdata version number?
by Jonathan Leffler Nov. 25, 2007

Nov. 25, 2007

I note that the time zone information file has a version number byte and 15 bytes of currently unused (must be zero) space at the heading. Has anyone ever suggested embedding the version number of the time zone data files (eg "2007i") into that space, so that you can tell immediately where the data comes from when looking at the file? If not, may I make the suggestion? Presumably, the version byte would need to become version 3 -- or would we need both version 3 and version 4, with version 3 being like version 0 with 32-bit timestamps only plus the data version and version 4 being like version 2 with both 32-bit and 64-bit time stamps? I would suggest mandating 6 bytes, null terminated, for the version string. I don't think the version numbers for the data files ever got beyond one cycle of the alphabet in a year, so that works for almost the next seven thousand years - and after that, it is someone else's problem anyway (I plan to be retired long before that's an issue). The obvious advantage of this is that an appropriately modified zdump can show which set of rules the time zone information file was created from, which in turn would help decide whether an update is called for. The only immediate downside I can see is that the version information is not readily available in the distributed files - other than as part of the gzipped tar file name. That could be fixed if a VERSION file was released with the data, so each new release had it release number in the file. The zic program could look for that file - or take an optional argument that specifies the version. Since '-v' is for verbose, maybe '-z YYYYv'? I also note that Sun Solaris 10 appears to use the version 0 format for its time zone info files (zic --version gives 7.128). Would it be relevant to provide an output version selector option to the zic command line - so that files could be generated in version 0, 2 or 3 (or even 4) format when appropriate? Perhaps it would use "-o N" for N in 0, 2, 3 (and maybe 4)? Or do we need a more complex scheme where each of the separate data files gets a version tag whenever it is modified, so that you can tell that, for example, the northamerica rules have not changed recently, whereas the asia ones have changed? This would presumably need a new entry type in each data file - maybe Version followed by a version number, or Vrsn to be consistent with 'Rule', 'Zone', 'Link' and 'Leap' lines. -- Jonathan Leffler <jonathan.leffler(a)gmail.com> #include <disclaimer.h> Guardian of DBD::Informix - v2007.0914 - http://dbi.perl.org "Blessed are we who can laugh at ourselves, for we shall never cease to be amused."

2 2

Rules that Don't Exist
by Bill Seymour Nov. 25, 2007

Nov. 25, 2007

A tz newbie question: What happens when switching to a named rule, but no such rule exists? The Europe/Zurich example in zic.8.txt has an example of that (switches to Swiss rules in 1894, but there are no Swiss rules before 1940), but doesn't say what to do. I can make sense of that by making what seems to be the reasonable assumption that SAVE is zero and LETTER/S is null. Is that the intent? If so, then is it also true that, in America/Chicago, we should use "CT" rather than "CST" from 1883 Nov 18 12:09:24 to the last Sunday in March of 1918? Or is there something I'm missing? Thanks, --Bill Seymour

2 3

Update to your Database
by Steve Jewell - WR9G Nov. 24, 2007

Nov. 24, 2007

To whom it may concern, I live in the City of Austin in Scott County which is Indiana. Our county and the surrounding counties all observe EST in the winter months and EDT in spring, summer and fall months. My exact location is 38° 44' 22.1" N 85° 49' 31.9" W. If you have any questions or concerns, please let me know. Thanks, Steve Jewell 116 S Mac Dr Austin, IN 47102-8921 wr9g(a)arrl.net www.wr9g.net

1 0

FW: xmlDate Compiler
by Olson, Arthur David (NIH/NCI) [E] Nov. 20, 2007

Nov. 20, 2007

I'm forwarding this message from Louis Guindon, who is not on the time zone mailing list. Those of you who are on the list should direct replies appropriately. --ado -----Original Message----- From: Louis Guindon [mailto:louis.guindon@gmail.com] Sent: Monday, November 19, 2007 3:30 To: tz(a)lecserver.nci.nih.gov Subject: xmlDate Compiler Hi, The link for xmlDate complier from Philippe GOETZ is not working anymore. I am refering to this entry "xmlDate contains JavaScript code that parses tz source into an internal object that represents a time zone. It is freely available under the GPL. " on the web page http://www.twinsun.com/tz/tz-link.htm. I am very interested by this tool and wandering if you know the new location or the developer contact information. Regards, Louis Guindon

2 1

Re: error "too many transitions"
by Arthur David Olson Nov. 20, 2007

Nov. 20, 2007

That's not a feature, it's a bug. Here are changes to "zic.c" to eliminate the error message, and to "localtime.c" to ensure correct handling of zones to be treated as if they had long-ago DST (rather like proleptic calendars). --ado ------- zic.c ------- *** /tmp/geta13214 Mon Nov 19 17:41:38 2007 --- /tmp/getb13214 Mon Nov 19 17:41:39 2007 *************** *** 2012,2018 **** } for (i = 0; i < zonecount; ++i) { zp = &zpfirst[i]; ! updateminmax(zp->z_untilrule.r_loyear); for (j = 0; j < zp->z_nrules; ++j) { rp = &zp->z_rules[j]; if (rp->r_lowasnum) --- 2012,2019 ---- } for (i = 0; i < zonecount; ++i) { zp = &zpfirst[i]; ! if (i < zonecount - 1) ! updateminmax(zp->z_untilrule.r_loyear); for (j = 0; j < zp->z_nrules; ++j) { rp = &zp->z_rules[j]; if (rp->r_lowasnum) *************** *** 2043,2050 **** else max_year = INT_MAX; } /* ! ** For the benefit of older systems, generate data through 2037. */ if (max_year < 2037) max_year = 2037; for (i = 0; i < zonecount; ++i) { --- 2044,2054 ---- else max_year = INT_MAX; } /* ! ** For the benefit of older systems, ! ** generate data from 1900 through 2037. */ + if (min_year > 1900) + min_year = 1900; if (max_year < 2037) max_year = 2037; for (i = 0; i < zonecount; ++i) { ------- localtime.c ------- *** /tmp/geta13272 Mon Nov 19 17:43:30 2007 --- /tmp/getb13272 Mon Nov 19 17:43:30 2007 *************** *** 177,182 **** --- 177,183 ---- const struct tm * btmp); static time_t transtime(time_t janfirst, int year, const struct rule * rulep, long offset); + static int typesequiv(const struct state * sp, int a, int b); static int tzload(const char * name, struct state * sp, int doextend); static int tzparse(const char * name, struct state * sp, *************** *** 556,570 **** } i = 2 * YEARSPERREPEAT; sp->goback = sp->goahead = sp->timecnt > i; ! sp->goback = sp->goback && sp->types[i] == sp->types[0] && differ_by_repeat(sp->ats[i], sp->ats[0]); sp->goahead = sp->goahead && ! sp->types[sp->timecnt - 1] == sp->types[sp->timecnt - 1 - i] && differ_by_repeat(sp->ats[sp->timecnt - 1], sp->ats[sp->timecnt - 1 - i]); return 0; } static const int mon_lengths[2][MONSPERYEAR] = { { 31, 28, 31, 30, 31, 30, 31, 31, 30, 31, 30, 31 }, { 31, 29, 31, 30, 31, 30, 31, 31, 30, 31, 30, 31 } --- 557,598 ---- } i = 2 * YEARSPERREPEAT; sp->goback = sp->goahead = sp->timecnt > i; ! sp->goback = sp->goback && ! typesequiv(sp, sp->types[i], sp->types[0]) && differ_by_repeat(sp->ats[i], sp->ats[0]); sp->goahead = sp->goahead && ! typesequiv(sp, sp->types[sp->timecnt - 1], ! sp->types[sp->timecnt - 1 - i]) && differ_by_repeat(sp->ats[sp->timecnt - 1], sp->ats[sp->timecnt - 1 - i]); return 0; } + static int + typesequiv(sp, a, b) + const struct state * const sp; + const int a; + const int b; + { + register int result; + + if (sp == NULL || + a < 0 || a >= sp->typecnt || + b < 0 || b >= sp->typecnt) + result = FALSE; + else { + register const struct ttinfo * ap = &sp->ttis[a]; + register const struct ttinfo * bp = &sp->ttis[b]; + result = ap->tt_gmtoff == bp->tt_gmtoff && + ap->tt_isdst == bp->tt_isdst && + ap->tt_ttisstd == bp->tt_ttisstd && + ap->tt_ttisgmt == bp->tt_ttisgmt && + strcmp(&sp->chars[ap->tt_abbrind], + &sp->chars[bp->tt_abbrind]) == 0; + } + return result; + } + static const int mon_lengths[2][MONSPERYEAR] = { { 31, 28, 31, 30, 31, 30, 31, 31, 30, 31, 30, 31 }, { 31, 29, 31, 30, 31, 30, 31, 31, 30, 31, 30, 31 }

2 1

Noncontroversial changes?
by Arthur David Olson Nov. 19, 2007

Nov. 19, 2007

Is there any controversy at all about these changes that were suggested by Ken Pizzini? (I've changed snippets of the form "a == b ? c : d" to "(a == b) ? c : d" for ease of reading--or at least for my own ease of reading.) --ado diff -ru tzcode2007h-less-P-macro/Makefile tzcode2007-pre-i/Makefile --- tzcode2007h-less-P-macro/Makefile 2007-08-20 07:47:41.000000000 -0700 +++ tzcode2007-pre-i/Makefile 2007-11-13 15:08:32.930145602 -0800 @@ -86,7 +86,6 @@ LDLIBS= # Add the following to the end of the "CFLAGS=" line as needed. -# -Dconst= if `const' does not work (SunOS 4.x cc, OSF1 V5.0 cc) # -DHAVE_ADJTIME=0 if `adjtime' does not exist (SVR0?) # -DHAVE_GETTEXT=1 if `gettext' works (GNU, Linux, Solaris); also see LDLIBS # -DHAVE_INCOMPATIBLE_CTIME_R=1 if your system's time.h declares diff -ru tzcode2007h-less-P-macro/date.c tzcode2007-pre-i/date.c --- tzcode2007h-less-P-macro/date.c 2007-11-11 16:56:00.603760665 -0800 +++ tzcode2007-pre-i/date.c 2007-11-13 15:35:01.220657120 -0800 @@ -311,7 +307,7 @@ } static void -dogmt() +dogmt(void) { static char ** fakeenv; diff -ru tzcode2007h-less-P-macro/localtime.c tzcode2007-pre-i/localtime.c --- tzcode2007h-less-P-macro/localtime.c 2007-11-11 16:56:03.611932091 -0800 +++ tzcode2007-pre-i/localtime.c 2007-11-13 15:44:58.578698614 -0800 @@ -1781,12 +1736,8 @@ ** It's okay to guess wrong since the guess ** gets checked. */ - /* - ** The (void *) casts are the benefit of SunOS 3.3 on Sun 2's. - */ sp = (const struct state *) - (((void *) funcp == (void *) localsub) ? - lclptr : gmtptr); + ((funcp == localsub) ? lclptr : gmtptr); #ifdef ALL_STATE if (sp == NULL) return WRONG; @@ -1880,11 +1829,7 @@ ** We try to divine the type they started from and adjust to the ** type they need. */ - /* - ** The (void *) casts are the benefit of SunOS 3.3 on Sun 2's. - */ - sp = (const struct state *) (((void *) funcp == (void *) localsub) ? - lclptr : gmtptr); + sp = (const struct state *) ((funcp == localsub) ? lclptr : gmtptr); #ifdef ALL_STATE if (sp == NULL) return WRONG; diff -ru tzcode2007h-less-P-macro/logwtmp.c tzcode2007-pre-i/logwtmp.c --- tzcode2007h-less-P-macro/logwtmp.c 2007-08-20 07:47:42.000000000 -0700 +++ tzcode2007-pre-i/logwtmp.c 2007-11-13 15:08:32.934145830 -0800 @@ -51,8 +51,8 @@ struct utmp ut; struct stat buf; int fd; - time_t time(); - char *strncpy(); + time_t time(time_t *); + char *strncpy(char *, const char *); if ((fd = open(WTMPFILE, O_WRONLY|O_APPEND, 0)) < 0) return; diff -ru tzcode2007h-less-P-macro/private.h tzcode2007-pre-i/private.h --- tzcode2007h-less-P-macro/private.h 2007-11-11 16:56:05.276026922 -0800 +++ tzcode2007-pre-i/private.h 2007-11-13 15:08:32.934145830 -0800 @@ -109,17 +104,15 @@ #endif /* !defined WEXITSTATUS */ #if HAVE_UNISTD_H -#include "unistd.h" /* for F_OK and R_OK */ +#include "unistd.h" /* for F_OK, R_OK, and other POSIX goodness */ #endif /* HAVE_UNISTD_H */ -#if !HAVE_UNISTD_H #ifndef F_OK #define F_OK 0 #endif /* !defined F_OK */ #ifndef R_OK #define R_OK 4 #endif /* !defined R_OK */ -#endif /* !HAVE_UNISTD_H */ /* Unlike <ctype.h>'s isdigit, this also works if c < 0 | c > UCHAR_MAX. */ #define is_digit(c) ((unsigned)(c) - '0' <= 9) @@ -165,69 +158,13 @@ */ /* -** SunOS 4.1.1 headers lack EXIT_SUCCESS. -*/ - -#ifndef EXIT_SUCCESS -#define EXIT_SUCCESS 0 -#endif /* !defined EXIT_SUCCESS */ - -/* -** SunOS 4.1.1 headers lack EXIT_FAILURE. -*/ - -#ifndef EXIT_FAILURE -#define EXIT_FAILURE 1 -#endif /* !defined EXIT_FAILURE */ - -/* -** SunOS 4.1.1 headers lack FILENAME_MAX. -*/ - -#ifndef FILENAME_MAX - -#ifndef MAXPATHLEN -#ifdef unix -#include "sys/param.h" -#endif /* defined unix */ -#endif /* !defined MAXPATHLEN */ - -#ifdef MAXPATHLEN -#define FILENAME_MAX MAXPATHLEN -#endif /* defined MAXPATHLEN */ -#ifndef MAXPATHLEN -#define FILENAME_MAX 1024 /* Pure guesswork */ -#endif /* !defined MAXPATHLEN */ - -#endif /* !defined FILENAME_MAX */ - -/* -** SunOS 4.1.1 libraries lack remove. -*/ - -#ifndef remove -extern int unlink(const char * filename); -#define remove unlink -#endif /* !defined remove */ - -/* -** Some ancient errno.h implementations don't declare errno. -** But some newer errno.h implementations define it as a macro. -** Fix the former without affecting the latter. -*/ - -#ifndef errno -extern int errno; -#endif /* !defined errno */ - -/* ** Some time.h implementations don't declare asctime_r. ** Others might define it as a macro. ** Fix the former without affecting the latter. */ #ifndef asctime_r -extern char * asctime_r(); +extern char * asctime_r(struct tm const *, char *); #endif /* diff -ru tzcode2007h-less-P-macro/zdump.c tzcode2007-pre-i/zdump.c --- tzcode2007h-less-P-macro/zdump.c 2007-11-11 16:56:10.112302526 -0800 +++ tzcode2007-pre-i/zdump.c 2007-11-13 15:27:06.301593025 -0800 @@ -88,9 +85,12 @@ #define SECSPERNYEAR (SECSPERDAY * DAYSPERNYEAR) #define SECSPERLYEAR (SECSPERNYEAR + SECSPERDAY) +#ifndef HAVE_GETTEXT +#define HAVE_GETTEXT 0 +#endif #if HAVE_GETTEXT #include "locale.h" /* for setlocale */ #include "libintl.h" #endif /* HAVE_GETTEXT */ #ifndef GNUC_or_lint @@ -129,10 +129,6 @@ #define TZ_DOMAIN "tz" #endif /* !defined TZ_DOMAIN */ -#ifndef P -#define P(x) x -#endif /* !defined P */ - extern char ** environ; extern int getopt(int argc, char * const argv[], const char * options); @@ -394,7 +384,7 @@ } static void -setabsolutes() +setabsolutes(void) { if (0.5 == (time_t) 0.5) { /* @@ -592,7 +578,7 @@ */ static const char * -tformat() +tformat(void) { if (0.5 == (time_t) 0.5) { /* floating */ if (sizeof (time_t) > sizeof (double))

3 2

Use of tz database
by Cheryl Sallen Nov. 19, 2007

Nov. 19, 2007

Dear Messrs Olson and Eggert: This is to request assistance with my research into a suitable time zone database for use in updating commercial data products. Tele Atlas North America, Inc. ("TANA") seeks to improve the content and accuracy of time zone information within its national and global, street centerline, proprietary database. Since your website clearly describes the tz database as a public domain database, I will want to proceed as if there are no restrictions on its commercial use. If restrictions do apply, please respond to that effect. TANA data analysts have reviewed a sample of your files. I am tasked with relaying several technical observations / questions: * Is there a metadata file available? * The purpose of the code is not clear. * Can the code be 'tested'? * Will the code produce a list with state, county, and time zone (as applicable for North America, of course)? * Does your naming convention NOT reference counties' association with time zones? * Updates appear to be released 'as needed'. I believe the most recent was Oct. 1, 2007//version h? Is there an update schedule other than as needed? If the answers to these questions exist elsewhere, kindly point me to them? Your time and attention to my request will be much appreciated. Sincerely, Cheryl Cheryl J. Sallen ________________________________ National Projects Leader - Municipal Boundaries North American Data Operations Tele Atlas North America 11 Lafayette St | Lebanon NH 03766-1445 1-800.331-7881 ext: 3239 direct 1-603-643-5414 fax cheryl.sallen(a)teleatlas.com <mailto:cheryl.sallen@teleatlas.com> <http://www.teleatlas./> http://www.teleatlas.com <http://www.teleatlas.com/> This e-mail and any attachments thereto may contain information which is confidential and/or protected by intellectual property rights and are intended for the sole use of the recipient(s)named above. Any use of the information contained herein (including, but not limited to, total or partial reproduction, communication or distribution in any form) by persons other than the designated recipient(s) is prohibited. If you have received this e-mail in error, please notify the sender either by telephone or by email and delete the material from any computer. Thank you for your cooperation. Tele Atlas N.V.

1 0