July 2019 - tz - lists.iana.org

Bug Moncton 1973? Where can I find old tzdata releases?
by Alois Treindl July 5, 2019

July 5, 2019

https://data.iana.org/time-zones/ seems to contain only tzdata releases from 2016 upwards. I need to look into pre-2005 ones. Where can I find them? The reason is that I am checking New Brunswick, Canada DST in 1973. The zone America/Moncton was introduced in 2007, to be able to represent an unusual clock time of 0:01 for DST onset. America/Moncton does not list DST for 1973. That is the only year between 1945 and 2020 that NB would not have DST. Nearby zones like Halifax or ST_Johns have 1973 DST, just like the rest of Canada? Is there a bug in America/Moncton ? Shanks has DST in 1973 for New Brunswick.

5 4

Re: [tz] tz Digest, Vol 94, Issue 6
by Andrii Nabok July 5, 2019

July 5, 2019

Dear Paul Eggert, I would like to draw your attention to the fact that the Kyiv time zone is officially defined in the Crimea. In this regard, I have the following statements: 1. This is not a political issue; 2. All projects on the Internet, regardless of their scope, must comply with international law. 3. The territory of Crimea is not a disputed territory. Crimea is an integral part of Ukraine. All countries in the world, except Russia (which started the war in Ukraine), consider Crimea to be part of Ukraine. 4. Also pay attention to the provisions of the BCP 175. *"Changes to existing entries SHALL reflect the consensus on the ground in the region covered by that entry.". *Fake news on Russian sites - is not a consensus. Why is the Tzadat base contributing to Russian invaders and terrorists in conducting an information war against a civilized world? Also, we ask to answer the following questions: 1. On which basis were changes made in 2014? Based on the news on the site in the domain zone. Ru ??? 2. Will you change the time zone in Alaska, if after some time, Russian troops enter Alaska, take prisoner of official representatives of the US government and subsequently publish on all Russian sites the news that the Magadan time zone is set in Alaska??? Sincerely, Andrii Nabok чт, 4 лип. 2019 о 10:36 <tz-request(a)iana.org> пише: > Send tz mailing list submissions to > tz(a)iana.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://mm.icann.org/mailman/listinfo/tz > or, via email, send a message with subject or body 'help' to > tz-request(a)iana.org > > You can reach the person managing the list at > tz-owner(a)iana.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of tz digest..." > > > Today's Topics: > > 1. Re: Simferopol switch near 2014-03-30 (Paul.Koning(a)dell.com) > 2. Re: Simferopol switch near 2014-03-30 (Tim Parenti) > 3. Re: Simferopol switch near 2014-03-30 (Michael H Deckers) > 4. Re: Simferopol switch near 2014-03-30 (Paul Eggert) > 5. [PROPOSED] Cite Rec. ITU-R TF.460-6 for leap seconds (Paul Eggert) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 3 Jul 2019 13:27:29 +0000 > From: <Paul.Koning(a)dell.com> > To: <tz(a)iana.org> > Subject: Re: [tz] Simferopol switch near 2014-03-30 > Message-ID: <43E8DF99-A7A4-4879-9555-5E5DEC7CEC31(a)dell.com> > Content-Type: text/plain; charset="us-ascii" > > > > > On Jul 3, 2019, at 6:44 AM, Sergij Marchenko <makars(a)gmail.com> wrote: > > > > You can continue to live according to the rules imposed by russian > terrorists under the occupation regime of Putin Huylo. > > It's been explained many times already that the TZ project is a technical > one, not a political one, and the issue you raise is out of scope. > > Since you persist in bringing it up in spite of being corrected > repeatedly, it may be time to consider your mail to be spam and filter it > accordingly. > > paul > > > ------------------------------ > > Message: 2 > Date: Wed, 3 Jul 2019 09:33:36 -0400 > From: Tim Parenti <tim(a)timtimeonline.com> > To: Michael H Deckers <michael.h.deckers(a)googlemail.com> > Cc: Time Zone Mailing List <tz(a)iana.org> > Subject: Re: [tz] Simferopol switch near 2014-03-30 > Message-ID: > < > CAFpi07wuB0+X230MukZJGmVwFS2f8PBo5Fcua8CMaB-y+s4PJw(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > On Wed, 3 Jul 2019 at 04:43, Michael H Deckers via tz <tz(a)iana.org> wrote: > > > tzdb currently has the switch in Simferopol from > > 2014-03-30T02:00 to 04:00, following the announcement in > > [https://vz.ru/news/2014/3/17/677464.html] from 2014-03-17. > > > > But the clocks of the main station shown in the video at > > [https://www.rt.com/news/crimea-clocks-moscow-time-173/] > > advance from 22:00 to 00:00. If this is not a fake, the > > switch happened 4 hours earlier. > > > This apparent discrepancy in reporting was discussed contemporaneously > on-list and is already noted in commentary. > https://mm.icann.org/pipermail/tz/2014-March/020814.html > https://mm.icann.org/pipermail/tz/2014-March/020815.html > > Specifically: > > # Simferopol and Sevastopol reportedly changed their central town clocks > > # late the previous day, but this appears to have been ceremonial > > # and the discrepancies are small enough to not worry about. > > > As it so happens, the RT article you linked confirms that particular > perspective ? that the 22:00 transition was merely "ceremonial" and that > the 02:00 transition was official ? more clearly than we had identified at > the time. Quoting the article: > > ?the hands of the main railway station clock in the city of Simferopol > > jumped from 10 pm to 12 am on Saturday. [?] The ceremony follows the > > region?s formal joining the Russian Federation on March 21. Other > Crimeans, > > apart from Simferopol, the region?s capital, were expected to switch > their > > clocks at 2:00 am on Sunday, AFP reported. > > > It appears India's *Business Standard* also contemporaneously reported the > same, at > > https://www.business-standard.com/article/pti-stories/crimea-to-set-clocks-… > : > > ?a symbolic ceremony will be held to move the clocks forward at the railway > > station in the main city of Simferopol. The Black Sea peninsula's prime > > minister Sergei Aksyonov will oversee the switch at 10pm (midnight > Moscow, > > 2000 GMT). Europeans and ordinary Crimeans make the daylight savings > time > > switch at 2am tomorrow. > > > Since the zone is meant to represent the region as a whole, and not > necessarily one or two clocks in the town squares in the representative > city, this is why we settled on 2014-03-30 02:00 for the transition. > > -- > Tim Parenti >

2 3

[PROPOSED] Cite Rec. ITU-R TF.460-6 for leap seconds
by Paul Eggert July 4, 2019

July 4, 2019

(Inspired by patch proposed by Chris Woodbury.) * leapseconds.awk (BEGIN): * tz-link.html (Precision timekeeping): Add ITU-R citation. * leapseconds.awk (BEGIN): Drop mention of rolling leap seconds, as the ITU-R doesn’t mention them and this script doesn’t generate them. --- leapseconds.awk | 16 +++++++++------- tz-link.html | 4 ++++ 2 files changed, 13 insertions(+), 7 deletions(-) mode change 100644 => 100755 leapseconds.awk diff --git a/leapseconds.awk b/leapseconds.awk old mode 100644 new mode 100755 index 242e9d6..241da92 --- a/leapseconds.awk +++ b/leapseconds.awk @@ -16,6 +16,11 @@ BEGIN { print "# The NTP Timescale and Leap Seconds" print "# <https://www.eecis.udel.edu/~mills/leap.html>." print "" + print "# The rules for leap seconds are specified in Annex 1 (Time scales) of:" + print "# Standard-frequency and time-signal emissions." + print "# International Telecommunication Union - Radiocommunication Sector" + print "# (ITU-R) Recommendation TF.460-6 (02/2002)" + print "# <https://www.itu.int/rec/R-REC-TF.460-6-200202-I/>." print "# The International Earth Rotation and Reference Systems Service" print "# periodically uses leap seconds to keep UTC to within 0.9 s of UT1" print "# (which measures the true angular orientation of the earth in space)" @@ -29,15 +34,12 @@ BEGIN { print "# accounting for the discrepancy between atomic time and the earth's rotation" print "# did not exist. The first (\"1 Jan 1972\") data line in leap-seconds.list" print "# does not denote a leap second; it denotes the start of the current definition" - print"# of UTC." + print "# of UTC." print "" print "# The correction (+ or -) is made at the given time, so lines" - print "# will typically look like:" - print "# Leap YEAR MON DAY 23:59:60 + R/S" - print "# or" - print "# Leap YEAR MON DAY 23:59:59 - R/S" - print "" - print "# If the leap second is Rolling (R) the given time is local time (unused here)." + print "# typically look like this:" + print "# Leap YEAR MON DAY 23:59:60 + S" + print "# A negative leap second's columns 5 and 6 would be '23:59:59' and '-'." monthabbr[ 1] = "Jan" monthabbr[ 2] = "Feb" diff --git a/tz-link.html b/tz-link.html index 85fc001..234c04e 100644 --- a/tz-link.html +++ b/tz-link.html @@ -929,6 +929,10 @@ scales used by each landed mission on Mars.</li> dedicated not only to leap seconds but to precise time and frequency in general. It covers the state of the art in amateur timekeeping, and how the art has progressed over the past few decades.</li> +<li>The rules for leap seconds are specified in Annex 1 (Time scales) of <a +href="https://www.itu.int/rec/R-REC-TF.460-6-200202-I/">Standard-frequency +and time-signal emissions</a>, International Telecommunication Union – +Radiocommunication Sector (ITU-R) Recommendation TF.460-6 (02/2002).</li> <li><a href="https://www.iers.org/IERS/EN/Publications/Bulletins/bulletins.html"><abbr title="International Earth Rotation and Reference Systems Service">IERS</abbr> -- 2.17.1

3 7

Clarification on future direction of POSIXRULES and POSIX TZ specs?
by Tom Lane July 4, 2019

July 4, 2019

The 2019b announcement says that zic's -p feature is being deprecated with an eye to eventual removal. I am wondering what is the game plan there exactly, and in particular what is planned to happen in localtime.c. Will the code that tries to load the TZDEFRULES zone be removed? If so, will the behavior for transition-rule-less POSIX TZ specs be that it always falls back to the hard-wired TZDEFRULESTRING? Or are you planning to go further, say by rejecting such TZ specs entirely? (As far as I can see, doing that would be contrary to the POSIX spec --- although they don't say what the default rule should be, it's pretty clear syntactically that you can omit it.) Also, what sort of time scale might this happen on? regards, tom lane

2 1

Backzone entry for Europe/Vaduz
by Alois Treindl July 4, 2019

July 4, 2019

In the year 2013 I had contributed information that Swiss neighbor country Liechtenstein, represented by Europe/Vaduz in file backzone, did not have daylight saving time in 1941 and 1942, while Switzerland, represented by Europe/Zurich, did have it. A colleague sent me a follow-up question today, which cause me to reconsider the question. I was able to access the online archive of the Vaduz paper Vaterland for free - they offer a special summer deal. I could confirm frm the paper that Liechtenstein did in fact follow the same DST in 1941 and 1942 as Switzerland did. The entry Europe/Vaduz in the file backzone can be removed, so that the link Europe/Zurich Europe/Vaduz remains effective even for those who, like me, compile TZ with backzone included. I attach a few newspaper clippings, not translated.

3 4

Golan Heights and Quneitra
by Alois Treindl July 4, 2019

July 4, 2019

The Golan Heights are not represented by a zone in TZ. Since 1967 under control of Israel, they fall under Asia/Jerusalem, as all differences fall under the 1970 TZ cut-off. Having a zone in backzone would be good, though. There is however one town in the Golan Heights, Quneitra, which was returned from Isreal to Syria in 1974. There have been timezone differences in the years 1967 - 1974 between Israel and Syria. Therefore, Asia/Quneitra would merit its own zone, in my opinion. https://en.wikipedia.org/wiki/Quneitra list a population of 153 for the (destroyed) town itself and 4318 for is 'metropolitan' area.

2 1

Simferopol switch near 2014-03-30
by Michael H Deckers July 3, 2019

July 3, 2019

tzdb currently has the switch in Simferopol from 2014-03-30T02:00 to 04:00, following the announcement in [https://vz.ru/news/2014/3/17/677464.html] from 2014-03-17. But the clocks of the main station shown in the video at [https://www.rt.com/news/crimea-clocks-moscow-time-173/] advance from 22:00 to 00:00. If this is not a fake, the switch happened 4 hours earlier. Michael Deckers.

5 7

From Consulate General of Ukraine in San Francisco
by Consulate General of Ukraine in San Francisco July 2, 2019

July 2, 2019

З повагою/Best regards, Генеральне консульство України в Сан-Франциско/Consulate General of Ukraine in San Francisco 530 Bush Street, Suite 402, San Francisco, CA 94108 Tel: + 1 (415) 398 0240, Fax: +1 (415) 398 5039 http://san-francisco.mfa.gov.ua<http://san-francisco.mfa.gov.ua/> gc_uss(a)mfa.gov.ua<mailto:gc_uss@mfa.gov.ua>

2 1

[tz-announce] 2019b release of tz code and data available
by Paul Eggert July 2, 2019

July 2, 2019

The 2019b release of the tz code and data is available. It reflects the following changes, which were either circulated on the tz mailing list or are relatively minor technical or administrative changes: Briefly: Brazil no longer observes DST. 'zic -b slim' outputs smaller TZif files; please try it out. Palestine's 2019 spring-forward transition was on 03-29, not 03-30. Changes to future timestamps Brazil has canceled DST and will stay on standard time indefinitely. (Thanks to Steffen Thorsen, Marcus Diniz, and Daniel Soares de Oliveira.) Predictions for Morocco now go through 2087 instead of 2037, to work around a problem on newlib when using TZif files output by zic 2019a or earlier. (Problem reported by David Gauchard.) Changes to past and future timestamps Palestine's 2019 spring transition was 03-29 at 00:00, not 03-30 at 01:00. (Thanks to Sharef Mustafa and Even Scharning.) Guess future transitions to be March's last Friday at 00:00. Changes to past timestamps Hong Kong's 1941-06-15 spring-forward transition was at 03:00, not 03:30. Its 1945 transition from JST to HKT was on 11-18 at 02:00, not 09-15 at 00:00. In 1946 its spring-forward transition was on 04-21 at 00:00, not the previous day at 03:30. From 1946 through 1952 its fall-back transitions occurred at 04:30, not at 03:30. In 1947 its fall-back transition was on 11-30, not 12-30. (Thanks to P Chan.) Changes to past time zone abbreviations Italy's 1866 transition to Rome Mean Time was on December 12, not September 22. This affects only the time zone abbreviation for Europe/Rome between those dates. (Thanks to Stephen Trainor and Luigi Rosa.) Changes affecting metadata only Add info about the Crimea situation in zone1970.tab and zone.tab. (Problem reported by Serhii Demediuk.) Changes to code zic's new -b option supports a way to control data bloat and to test for year-2038 bugs in software that reads TZif files. 'zic -b fat' and 'zic -b slim' generate larger and smaller output; for example, changing from fat to slim shrinks the Europe/London file from 3648 to 1599 bytes, saving about 56%. Fat and slim files represent the same set of timestamps and use the same TZif format as documented in tzfile(5) and in Internet RFC 8536. Fat format attempts to work around bugs or incompatibilities in older software, notably software that mishandles 64-bit TZif data or uses obsolete TZ strings like "EET-2EEST" that lack DST rules. Slim format is more efficient and does not work around 64-bit bugs or obsolete TZ strings. Currently zic defaults to fat format unless you compile with -DZIC_BLOAT_DEFAULT=\"slim\"; this out-of-the-box default is intended to change in future releases as the buggy software often mishandles timestamps anyway. zic no longer treats a set of rules ending in 2037 specially. Previously, zic assumed that such a ruleset meant that future timestamps could not be predicted, and therefore omitted a POSIX-like TZ string in the TZif output. The old behavior is no longer needed for current tzdata, and caused problems with newlib when used with older tzdata (reported by David Gauchard). zic no longer generates some artifact transitions. For example, Europe/London no longer has a no-op transition in January 1996. Changes to build procedure tzdata.zi now assumes zic 2017c or later. This shrinks tzdata.zi by a percent or so. Changes to documentation and commentary The Makefile now documents the POSIXRULES macro as being obsolete, and similarly, zic's -p POSIXRULES option is now documented as being obsolete. Although the POSIXRULES feature still exists and works as before, in practice it is rarely used for its intended purpose, and it does not work either in the default reference implementation (for timestamps after 2037) or in common implementations such as GNU/Linux (for contemporary timestamps). Since POSIXRULES was designed primarily as a temporary transition facility for System V platforms that died off decades ago, it is being decommissioned rather than institutionalized. New info on Bonin Islands and Marcus (thanks to Wakaba and Phake Nick). Here are links to the release files: https://www.iana.org/time-zones/repository/releases/tzcode2019b.tar.gz https://www.iana.org/time-zones/repository/releases/tzdata2019b.tar.gz https://www.iana.org/time-zones/repository/releases/tzdb-2019b.tar.lz As usual, links to the latest release files are here: https://www.iana.org/time-zones/repository/tzcode-latest.tar.gz https://www.iana.org/time-zones/repository/tzdata-latest.tar.gz https://www.iana.org/time-zones/repository/tzdb-latest.tar.lz Links are also available via plain HTTP, and via FTP from ftp://ftp.iana.org/tz/releases with the same basenames as above. Each release file has a GPG signature, which can be retrieved by appending ".asc" to the above URLs. Copies of these signatures are appended to this message. This release corresponds to commit 23a01523a5d6a6ae2217df77b2a3f60e10a373d2 dated 2019-07-01 00:09:53 -0700 and tagged '2019b' in the development GitHub repository at <https://github.com/eggert/tz>. Here are the SHA-512 checksums for the release files: bcfb417fe3b7c39e702da0090291db0489744f733010ae183007fce5e441bfce885fb25ed11730cf7f363572e107d7ff0c4b38691bb99def2d8cf7017c05720f tzcode2019b.tar.gz c0104078d994e501d80a41bea31364b1390a75c2fbf42968a8343a090e2ac2eddbc58770ca470b192ea19dec89fcc634141a1de703ea2ffa0325176a64afe1fc tzdata2019b.tar.gz 98030b41258d21b6040fe95ecee4edd6bb9fa3775d89bebf69f460abad009eb47f053197ac755dc2d631b40fe31d4d3650493f139069b14ab3771e529cebcaea tzdb-2019b.tar.lz Here are the GPG checksums for the release files: -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAl0Zs9AACgkQ7ZfpDmKq fjQziw//UmsHJNgU9cwbxWUBNqqu6VqrllAgLEXXLbK0EhZGwQpYsrhW9h5LZrvS OVHUt7EorLaFB4rSkTr2DP6pSqAn7+i7pXVdETxHNmTcF85rbyLwt5Z4OrbMAaN2 f44BxVSOSO4C/A+wWN7JAhAC57fwj++bCvIZ82qlauV1BsBq0AiuURat5OP2ZA16 Wpz3749wy1N4xEtYaMRzBozWQ6mnyYxaCRZUTv2BhuVK8UbUrHZ8I8KkcqAYnOqL E0fTWSKQVRxciApFNWHEreIeeVonOom0DWWEL3dIQcx09IM0YtocpAXgWoyHzOic mU7ibcx0KrpzDW+6nf/owxe/dkUa+CbHgPDs9b5vTJUwJkSk8wrpr3tAPSjBeo9K WN+BvhxeZKihPU9DziWTs8jAzyVtnqGNesBhVi1zecY723Gk/oizdDQNxh9vLbYU VUP3kcc2IqEciJVeI6bDz2wSJVcCif3bFFosuF2fOpTzmpLx+WceYVw+y0NFMcTN euZ/D1AQK7opCshjoBKqbOMB6TvbjjCiEjQ/pkXKLwhYBWCtIPMblgo+33MrI4Eb r/3S+l4o6yDbxslZjn0kNoG6krrbb6F1IrjIfnd4t2PDoeYS2vE7rCi+qhrJNLEI 24ZxbaZgnt4JvAec+5cy9ZnTOzZs7IhDSiMbm40IB0v2zVFT+rQ= =6vQV -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAl0Zs9AACgkQ7ZfpDmKq fjT55Q/9G4BmEDL48wU0slZCAFNMqbvNfizL2MTNHC6Yv60gwdQCl7CgQk+zE+1W b4ir1Vm23eWWVdCjGGwjt4WWy+SlvnEKqjiZxTRFpkB5to8Zi5KNklGlUX0U9iUu vMCVKeIQMFLUr6sAqAk4lgJ2OUF1MNaj2kVwINxS+C8rCyr6wjn6FWWaxvbCO3+D 2Z8sZgCRBWxmckqX+4Nmv2YeCGuL1ZjVTz0flkWi/OduR+PjBe/9PN506PjeEht8 cqOjtRz/V4SEKfbv6rn8jqxDrl6xkrBxfiaF64smWgwSFcQ9yRrxCt2L35tARdal DAP/vb1PemUb0fJawYP/ZhiArk0fCRRZ+wleTZKsk65I4VsrffQ3rYe5ZtMYnUhO +UP+B7OkxNa0gARf+uFwYvrqZefg0HRq/INFqd3TCkza0wa7Rb3mQL9orCzUH7St XLrdhRJYWGcuepGBiTdO4+yPqXkK7k89W3ACo+HiVuRbMRo3Xf+38918kubns41l /itR/C/lSN+/ErokSh6VshelvOuMVcgoghTD7fDAtNaH9IgldEIF/Wf3m1Um+V9R sN646EvAazgkxw3hD1sEDxHxN7TIsxFvTaimVg+uwrX2b8Ok+tffomlalSXoOS8F zK/EyKROm8v2dSJUD0Hf+FvDqJm/Pre0ydKqsdahJYBxIStNnX8= =P/tF -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAl0Zs9IACgkQ7ZfpDmKq fjRlfQ//ev3hI5NxrAoJX8fpb9LAdReo7ZpADinVnNn47AyS0WYUtf6Afaav+lT+ FL+OU39VTJAeQ0zwVrH9JZr3Oy8mIl9mhAEPUsX4NxLw8P7QTdCHO84NmkrzpoM9 l9GEOkBoNTIE5YaM9IezKhMKJv/CyPXkRnx3UBAblgTaBkV0gqkoePPn4sVa0Arh 3Vn6H6AV6oQpC8WtH8yCxBuLXkddiVHFi3zbuM+3MHgFTb+8f/UwTopGUjsZOPoN z00rwFO+jVjdrm2700i1j1bTYGInIe3pIctwfutQfglIQSFK3nQADFYdlhfBLBJM H0NDCYF1z/LKtAWSycWpRhpqU2+25mX6Fldrfp1YhrSiJCrUQYOgQNXRSa32nY1T 5gc71UAe9rQNDRo5deSmOunKXWY5s6tZdxn7Q22FBFWwfrGmCqhR6mrB2dgEBvl8 isjoGxZO1iJYhlTvq7WyxOdnbjR4BLBF0eE8KB2S2F6srb/luPfCG6F9Ier5fYl7 N/NvH5FSeJHC1r2EWw+yy5bjaG5GkX6NP1+FBfw7prKtUNx48x8tpdy11FlULkCN J+zid9ySJBsnMRNL5p/egYbYGaptLGO8yAuKN3s3znaG/f9kh39u+xI1Fo9KFVBd +NvQYaMNYMgTi4qyCaMeCGxUUlJLN/WnjclJyl/ca84sUhpLXRI= =3v1i -----END PGP SIGNATURE----- PS. If your tzdata parser does not yet support negative DST offsets or times past 24:00, this release's data entries can be turned into a rearguard-format tarball that does not use these features. This is intended to be a temporary transition aid for these parsers. To generate a rearguard-format tarball, obtain the full distribution as described above, and run the command 'make rearguard_tarballs' on a development host. Or you can run 'make rearguard.zi' to generate a single file that can be fed directly to a parser that works like 'zic'.

1 0

[PATCH] Allow the gpg2 binary name to be overridden by the environment.
by Matthew Donadio July 1, 2019

July 1, 2019

On some platforms, the gpg2 binary isn't actually called 'gpg2'; on OSX when you install GPG view Homebrew, it is just 'gpg'. This probably affects about three people on the planet, but noticed it when working on build scripts. --Matthew Donadio (matt(a)mxd120.com)

2 1