- tz - lists.iana.org

Turks & Caicos to resume DST; details unclear
by Paul Eggert Oct. 31, 2017

Oct. 31, 2017

According to an article published in the Bahamas website Magnetic Media, the cabinet of Turks & Caicos decided on Thursday to resume the practice of daylight saving time starting in 2018. The article does not give enough details to update the database (it confuses summer with winter time, among other things). My guess is that Turks & Caicos will revert to its pre-2015 practice of staying in sync with New York, which means that tzdb's predictions for its UTC offsets will become wrong in November 2018, and the abbreviations and tm_isdst flag will become wrong some time between March and November 2018 (although the article implies April, this could well be an error). When the cabinet and/or the Turks & Caicos Weekly News get around to publishing the details of the decision, we should be able to update tzdb to reflect this change with some accuracy. Gordon Z. PDM to reinstate Daylight Savings Time. Magnetic Media 2017-07-20. http://magneticmediatv.com/2017/07/pdm-to-reinstate-daylight-savings-time/ ("PDM" is the People's Democratic Movement.)

4 4

A bill to move Polish time (Europe/Warsaw) permanently to UTC+2
by Sergiusz Wolicki Oct. 29, 2017

Oct. 29, 2017

An internal committee of the Polish parlament (Sejm) has unanimously voted in favor of a bill to stop DST changes and to introduce permanent Central European Summer Time (GMT+2). The law would come in force in autumn 2018. The bill still needs to be voted by Sejm, then Senat (upper house), and then must be signed by the President, so it is far from being the actual law. The bill is not considered conflicting with EU regulations, which only require DST changes to be synchronized across EU but do not actually mandate the use of DST. Reference in Polish: http://wiadomosci.gazeta.pl/wiadomosci/7,114883,22499682,nie-bedziemy-przes… The website <http://sejm.gov.pl/Sejm8.nsf/PrzebiegProc.xsp?nr=1852> of the Sejm has not yet been updated with the result of the voting. Thanks, Sergiusz

7 7

Bug in Latest Release of TZ Database ie 2017c
by Sahil Sethi Oct. 28, 2017

Oct. 28, 2017

Hi Team As decided by Sudan Government to change time zone from GMT+3 to GMT+2, we were testing TZ update from 2017b --> 2017c and we encountered the following error : Linux TZ version : 2017b --> 2017c ... Failed | "backzone", line 149: duplicate zone name Africa/Juba (file "africa", line 1107) | "backzone", line 150: input line of unknown type | "backzone", line 151: input line of unknown type On little debugging we found that in former version there was a link between Africa/Khartoum & Africa/Juba zones in africa file and Africa/Juba zone entry existed in "backzone" file but in later version same zone entry of Africa/Juba exists in both files ie "africa" & "backzone", causing trouble. Looking forward for an acknowledgement. Regards Sahil Sethi Sr Software Engineer GlogbalLogic, India

2 1

2017c zdump outputs "No such file or directory"
by 大山俊成 Oct. 27, 2017

Oct. 27, 2017

Hi, Previously, I tryed 2017b like the following. make TOPDIR=$HOME/tzdir install $HOME/tzdir/etc/zdump -v America/Los_Angeles It works good . Now I tryed 2017c as the same way. make TOPDIR=$HOME/tzdir install $HOME/tzdir/etc/zdump -v America/Los_Angeles But , zdump outputs "America/Los_Angeles: No such file or Directory" Something wrong with me?

3 7

why do Africa/Juba and backzone/Africa/Juba differ?
by Michael Deckers Oct. 24, 2017

Oct. 24, 2017

Puzzles me in 2017c: Africa/Juba and backzone/Africa/Juba differ in their astronomical longitudes: in zone1970.tab: SS +0451+03137 Africa/Juba in zone.tab: SS +0451+03136 Africa/Juba and (correspondingly) in the local mean time used before the switch to zone time in 1931: in africa: Zone Africa/Juba 2:06:28 - LMT 1931 in backzone: Zone Africa/Juba 2:06:24 - LMT 1931 Why? And do we need the backzone entry at all? Michael Deckers. --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

2 1

Anyone else having snprintf issues with 2017c?
by Jon Skeet Oct. 24, 2017

Oct. 24, 2017

The tzvalidate <https://github.com/nodatime/tzvalidate> travis build is failing, with both clang and gcc, with this error: zdump.c:803:1: error: static declaration of ‘snprintf’ follows non-static declaration snprintf(char *s, size_t size, char const *format, ...) ^ make: *** [zdump.o] Error 1 It's building fine for me locally, so I'm not quite sure what's wrong. We're currently building on trusty - I may try another distro... The snprintf changes were introduced on June 13th <https://github.com/eggert/tz/commit/399180580f65bcad63cf996997068366cadaf53…>. It's been too long since I've done a lot of C to easily work out what's going on. I'll investigate further myself tomorrow, but I thought I'd just see if anyone else had seen this before then. Jon

7 9

installargs loses part of backward
by Zefram Oct. 23, 2017

Oct. 23, 2017

New in the 2017c release, there's a bug in how INSTALLARGS in the Makefile passes the BACKWARD variable down to an inferior make process. Because the definition of INSTALLARGS doesn't put quotes around the value part of BACKWARD, and because BACKWARD is actually (by default) a space-separated list of two files, the inferior make only gets the first file in its BACKWARD value, treating the second file as something to ensure is up to date (which of course it already is). So the inferior make omits one of the BACKWARD files (pacificnew) from whatever it does. The practical effect of this is that when building the binary zone files by, for example, "make posix_only", without having previously done "make tzdata.zi", the US/Pacific-New link is omitted. It's missing from the directory of binary outputs, and missing from the tzdata.zi file that is created as a side effect of building them (thus affecting anything that later tries to use tzdata.zi). That's the only zone name affected, because it's the only zone name defined in the lost source file. If "make tzdata.zi" is done first then that will create a correct tzdata.zi, and subsequent building of the binary zone files will then include the link. This was spotted by my automation, which sanity checks the directory of generated binary zone files against a list of zone names that it extracts from the source files. I think this a sensible check, and that it ought to pass. The fix is that the definition of INSTALLARGS should quote $(BACKWARD), the same way it quotes $(PACKRATDATA). Or perhaps it should not set BACKWARD at all, just like it doesn't set YDATA et al. (But perhaps it should *also* set YDATA et al.) -zefram

3 4

[tz-announce] 2017c release of tz code and data available
by Paul Eggert Oct. 23, 2017

Oct. 23, 2017

The 2017c 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: Northern Cyprus switches from +03 to +02/+03 on 2017-10-29. Fiji ends DST 2018-01-14, not 2018-01-21. Namibia switches from +01/+02 to +02 on 2018-04-01. Sudan switches from +03 to +02 on 2017-11-01. Tonga likely switches from +13/+14 to +13 on 2017-11-05. Turks & Caicos switches from -04 to -05/-04 on 2018-11-04. A new file tzdata.zi now holds a small text copy of all data. The zic input format has been regularized slightly. Changes to future time stamps Northern Cyprus has decided to resume EU rules starting 2017-10-29, thus reinstituting winter time. Fiji ends DST 2018-01-14 instead of the 2018-01-21 previously predicted. (Thanks to Dominic Fok.) Adjust future predictions accordingly. Namibia will switch from +01 with DST to +02 all year on 2017-09-03 at 02:00. This affects UT offsets starting 2018-04-01 at 02:00. (Thanks to Steffen Thorsen.) Sudan will switch from +03 to +02 on 2017-11-01. (Thanks to Ahmed Atyya and Yahia Abdalla.) South Sudan is not switching, so Africa/Juba is no longer a link to Africa/Khartoum. Tonga has likely ended its experiment with DST, and will not adjust its clocks on 2017-11-05. Although Tonga has not announced whether it will continue to observe DST, the IATA is assuming that it will not. (Thanks to David Wade.) Turks & Caicos will switch from -04 all year to -05 with US DST on 2018-03-11 at 03:00. This affects UT offsets starting 2018-11-04 at 02:00. (Thanks to Steffen Thorsen.) Changes to past time stamps Namibia switched from +02 to +01 on 1994-03-21, not 1994-04-03. (Thanks to Arthur David Olson.) Detroit did not observe DST in 1967. Use railway time for Asia/Kolkata before 1941, by switching to Madras local time (UT +052110) in 1870, then to IST (UT +0530) in 1906. Also, treat 1941-2's +0630 as DST, like 1942-5. Europe/Dublin's 1946 and 1947 fallback transitions occurred at 02:00 standard time, not 02:00 DST. (Thanks to Michael Deckers.) Pacific/Apia and Pacific/Pago_Pago switched from Antipodean to American time in 1892, not 1879. (Thanks to Michael Deckers.) Adjust the 1867 transition in Alaska to better reflect the historical record, by changing it to occur on 1867-10-18 at 15:30 Sitka time rather than at the start of 1867-10-17 local time. Although strictly speaking this is accurate only for Sitka, the rest of Alaska's blanks need to be filled in somehow. Fix off-by-one errors in UT offsets for Adak and Nome before 1867. (Thanks to Michael Deckers.) Add 7 s to the UT offset in Asia/Yangon before 1920. Changes to zone names Remove Canada/East-Saskatchewan from the 'backward' file, as it exceeded the 14-character limit and was an unused misnomer anyway. Changes to build procedure To support applications that prefer to read time zone data in text form, two zic input files tzdata.zi and leapseconds are now installed by default. The commands 'zic tzdata.zi' and 'zic -L leapseconds tzdata.zi' can reproduce the tzdata binary files without and with leap seconds, respectively. To prevent these two new files from being installed, use 'make TZDATA_TEXT=', and to suppress leap seconds from the tzdata text installation, use 'make TZDATA_TEXT=tzdata.zi'. 'make BACKWARD=' now suppresses backward-compatibility names like 'US/Pacific' that are defined in the 'backward' and 'pacificnew' files. 'make check' now works on systems that lack a UTF-8 locale, or that lack the nsgmls program. Set UTF8_LOCALE to configure the name of a UTF-8 locale, if you have one. Y2K runtime checks are no longer enabled by default. Add -DDEPRECATE_TWO_DIGIT_YEARS to CFLAGS to enable them, instead of adding -DNO_RUN_TIME_WARNINGS_ABOUT_YEAR_2000_PROBLEMS_THANK_YOU to disable them. (New name suggested by Brian Inglis.) The build procedure for zdump now works on AIX 7.1. (Problem reported by Kees Dekker.) Changes to code zic and the reference runtime now reject multiple leap seconds within 28 days of each other, or leap seconds before the Epoch. As a result, support for double leap seconds, which was obsolescent and undocumented, has been removed. Double leap seconds were an error in the C89 standard; they have never existed in civil timekeeping. (Thanks to Robert Elz and Bradley White for noticing glitches in the code that uncovered this problem.) zic now warns about use of the obsolescent and undocumented -y option, and about use of the obsolescent TYPE field of Rule lines. zic now allows unambiguous abbreviations like "Sa" and "Su" for weekdays; formerly it rejected them due to a bug. Conversely, zic no longer considers non-prefixes to be abbreviations; for example, it no longer accepts "lF" as an abbreviation for "lastFriday". Also, zic warns about the undocumented usage with a "last-" prefix, e.g., "last-Fri". Similarly, zic now accepts the unambiguous abbreviation "L" for "Link" in ordinary context and for "Leap" in leap-second context. Conversely, zic no longer accepts non-prefixes such as "La" as abbreviations for words like "Leap". zic no longer accepts leap second lines in ordinary input, or ordinary lines in leap second input. Formerly, zic sometimes warned about this undocumented usage and handled it incorrectly. The new macro HAVE_TZNAME governs whether the tzname external variable is exported, instead of USG_COMPAT. USG_COMPAT now governs only the external variables "timezone" and "daylight". This change is needed because the three variables are not in the same category: although POSIX requires tzname, it specifies the other two variables as optional. Also, USG_COMPAT is now 1 or 0: if not defined, the code attempts to guess it from other macros. localtime.c and difftime.c no longer require stdio.h, and .c files other than zic.c no longer require sys/wait.h. zdump.c no longer assumes snprintf. (Reported by Jonathan Leffler.) Calculation of time_t extrema works around a bug in GCC 4.8.4 (Reported by Stan Shebs and Joseph Myers.) zic.c no longer mistranslates formats of line numbers in non-English locales. (Problem reported by Benno Schulenberg.) Several minor changes have been made to the code to make it a bit easier to port to MS-Windows and Solaris. (Thanks to Kees Dekker for reporting the problems.) Changes to documentation and commentary The two new files 'theory.html' and 'calendars' contain the contents of the removed file 'Theory'. The goal is to document tzdb theory more accessibly. The zic man page now documents abbreviation rules. tz-link.htm now covers how to apply tzdata changes to clients. (Thanks to Jorge Fábregas for the AIX link.) It also mentions MySQL. The leap-seconds.list URL has been updated to something that is more reliable for tzdb. (Thanks to Tim Parenti and Brian Inglis.) Here are links to the release files: https://www.iana.org/time-zones/repository/releases/tzcode2017c.tar.gz https://www.iana.org/time-zones/repository/releases/tzdata2017c.tar.gz https://www.iana.org/time-zones/repository/releases/tzdb-2017c.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 812e509d5a30657f8e99ec51cedac7d4229ed784 dated 2017-10-20 14:49:34 -0700 and tagged '2017c' in the development GitHub repository at <https://github.com/eggert/tz>. Here are the SHA-512 checksums for the release files: 0d8c3e07b0de9015a137602450468ceb6358312a50eeda2a860882367107b8ba9ef275880b292570a671b9910afc54e6209e1e642387d246bc9c08c4ff660ffb tzcode2017c.tar.gz feb5c544e617b30c73a397e5a1c51f9847d0fddf1dfa0f9ace2e6f686786f09b666937b2048e07075c84593fc584bd5a25d639fce70eca9735267df28621ab4c tzdata2017c.tar.gz f877cd48bde0e342b9f71490befd7890682c87e9f542480b2e412b3ae08bd284516a3015588222c1fad8e3ec40a0428986404c3b660d7c88da92c1a2b6af10b4 tzdb-2017c.tar.lz Here are the GPG checksums for the release files: -----BEGIN PGP SIGNATURE----- iQIcBAABAgAGBQJZ6nFEAAoJEO2X6Q5iqn40JnoP/i8JCoxp5Vb+oxD2F8hz85+S ikzzi0+l5vMifyI9+/kxU/V+W1YvLC3zbUMLN6moE65WryjRnXCJXfTzNyFUON0H Dg7a1al0mNcq5D4YIvR6C/O5SJdRNW6VNW0A0owXV8ZafAzUbe5ICoUKQ69DC3ps jKXjO9qsyxne7rqjaqCyJAGVRHdx82p7XRvr5JCtU5vEGoclCDglWN4cUP09019q azA1eYfqkqS+uf3KzPVc8e/0slAdXOqOib7NNFY/Y90wFUlKuhgHdOXVy9bIvdeP PQmNlXNi1TC/gYNtqdxoeCsWSnOCMW9f/v9vBZTB8Oh8Ycm6U+YSAKZxlaVP5zUa VEnyMxDjKOD6YcqGHqx035TFxaAfaDDvDRACcA98SdTcBr7TgY4Ubxv0kCQ007Vr BYesKUcVpE8/wsh6dDHbaZzK01bJkJYGr44UZBwOwAbbkyCG+HDv3J6eg4UphQq0 HITxJLsaiJcJnR/l8YVSrzSHXIftwRIhGbab3BFuPAN7nDEZFrhUkZdMwac4B6E8 gsVxLYK3SJyFz9Jx7D4oDBN+Nxt+54O3/GXYVtAF0k2hiytd6UFaIr1WsmdSVLzA kmBQNiyqJ9jOPJ75B/r4x15JRZfNFDKJZ7AMqo6QthKZrurK93uuR20OKZmklnLr Vwcz+6pYTUf9bRrRfyXg =drdL -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- iQIcBAABAgAGBQJZ6nFvAAoJEO2X6Q5iqn40dFwP/31AK4shXM+vRKf28szHxBwk gTHTka+WMvQdhRtkgQvRXDQo1q9QiI/t4l3x0TpxkkuZATA6Yf1AhV7ugFFfl8Ia 0bc+8uXnv8XnpZ3Qbk57B6J6LEsaMOeaXv1vIZ6x8E/oaDECAV4o2+dpDl5kdNTr O6hcUZwY1Rd8CcJCvOPSFfRV1kNcPXCaKQPh0Z5uohqC7DLmxhtagsiMeUmzInV/ Q1bPOJXF4sD9X7A6hKqk4oyFQvJrYjv/JeM5eoreHIXdSLqvvwhhqCSMx6A76NDA 1/rKFZxqBLojlLmG07SXsCMC9OmD2m709sHKPx0foixhlmB9QJjDm62EjPPwfXd9 AH/3jxolQQq8DCC4XyqLblzPORfFNwZ4vWC3QpTNsQOdqBdkKpfNYXIZTxGL/8Ti 6GtCwmp2E5+gXoV1uTHY51nLNjuI47XdUReh+eBWAWh95gJiKspStHebWLFsbUhg /YM9K9efhu5UaA3BxJn3SpXR43zeNDSUOmyIB+kyRQZDXSK/K0ukwgZPMzq8QuR8 aFB7K0YztC8P6SXIGOgMsWuVp06Cx4QQAdnvy9pcx0iDUUNoh/n+isvwfBCvvUvq ETDnuGYxsUTjlDvORG1VHg14sr4AdyTl3PH12cOscVP4fq5JV91cE4FBHwjD3jSx Lp4Yb/wfGxGLgqPmpY/I =C3sx -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- iQIcBAABAgAGBQJZ6nF3AAoJEO2X6Q5iqn40NeQP/iuhDY14PgMC6Y4NjghAv/hZ lv3TV1E9t9bWc1S4whVQMqU8cXKMd0FddIYajylefPyEb/OwxB4R7/9IDlr1qlKG NkwOWsIrmqp60yFAdSGO2sfwkAcYZlLrujU/Bh0rFy2LFbMSFL4fTfB9WnCjWmqk pX5ioFn8L+uRrVCVQf3ruoFZcAF0D+wRSGLyAb3TAxR6dr2Bq8B0eOQsRtcfPwaL 4nBy/Fa85G3BVqSMtJhJXNIK1Vat4qd8wDU8Wr9cVjImefvVGypgCom1DlOTFD/r 5+kAIXr4RPn0t7af1ue8pNVIo6NuLfEfql59JzDREgYyl2HzwfS93+Ga+/YLR9Xz rSL7nOSDhjoo66SD0TAGNEXuRhfm3IJb81NIqIyP3IV0BpnoPyZSN5ZgNNPZwIqy tfXp/jEO1JoPBNuF+S3/RucABYKkEVLrZT5RdRrmHXxVbORop+2g3ZRKYtUeuT9P ablFWRihBao7+5Enj5hMxkfivzRUgF1+Speai6uDWFfuO/wteqntYvKVIawCWN53 +IqkpBVit0LdkA7YYgBJ4SW7wfOwRRidHANWrjEMzyajP1rfFuc3Kh0N1erIdpeV 74yYcEcHZK7dU2vki331d0xr08chB215Cz/Z1Zbm2IQxxz09g0jfYrkYijFfpxuf vyMRiNaT/Hp+EpEroVP0 =0r0r -----END PGP SIGNATURE----- _______________________________________________ tz-announce mailing list tz-announce(a)iana.org https://mm.icann.org/mailman/listinfo/tz-announce

1 0

Fiji DST Change
by Raymond Kumar Oct. 20, 2017

Oct. 20, 2017

Hi, Can you please advise by when new version of tzdata will be out. As there were some changes to Fiji DST. Thanks, Raymond Kumar Head of Billing & Products +679-7015315 ________________________________ Notice of Confidentiality: The information contained in this communication is intended solely for the use of the individual or entity to whom it is addressed and others authorized to receive it. It may contain confidential or legally privileged information. If you are not the intended recipient you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this information is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by responding to this email and then delete it from your system.

2 1

[PATCH] * tz-link.htm: Update for moved and expired URLs.
by Paul Eggert Oct. 20, 2017

Oct. 20, 2017

--- tz-link.htm | 29 +++++++++-------------------- 1 file changed, 9 insertions(+), 20 deletions(-) diff --git a/tz-link.htm b/tz-link.htm index 03259d2..e7a7c8f 100644 --- a/tz-link.htm +++ b/tz-link.htm @@ -267,9 +267,10 @@ href="https://tools.ietf.org/html/rfc7808">TZDIST</a> (Internet <abbr>RFC</abbr> 7808), a time zone data distribution service, along with <a href="https://tools.ietf.org/html/rfc7809">CalDAV</a> (Internet <abbr>RFC</abbr> 7809), a calendar access protocol for -transferring time zone data by reference. The draft <a id="TZDIST-Geolocate" +transferring time zone data by reference. The (expired) draft <a +id="TZDIST-Geolocate" href="https://tools.ietf.org/html/draft-murchison-tzdist-geolocate-00">TZDIST -Geolocate Extension</a> lets a client determine its time zone region +Geolocate Extension</a> would have let a client determine its time zone region from its geographic location using a <a href="https://tools.ietf.org/html/rfc5870">'geo' URI</a>.</li> <li>The <a href="https://tools.ietf.org/html/rfc5545"> @@ -504,9 +505,6 @@ href="https://www.oracle.com/java/index.html">Oracle Java</a> contains a copy of a subset of a recent <code><abbr>tz</abbr></code> database in a Java-specific format.</li> -<li><a href="https://kimmo.suominen.com/sw/timezone/">Time Zone</a> is -a <a href="https://wordpress.org">WordPress</a> plugin. It is freely -available under a <abbr>BSD</abbr>-style license.</li> <li><a href="http://www.relativedata.com/time-zone-master">Time Zone Master</a> is a Microsoft Windows clock program that can automatically download, compile and use <code>tz</code> releases. The Basic version @@ -589,7 +587,8 @@ maps</a> contains <a href="https://en.wikipedia.org/wiki/Shapefile">shapefiles</a> of sets of <code><abbr>tz</abbr></code> regions. This includes <a href="http://efele.net/maps/tz/world/">tz_world</a>, a shapefile -for all the world's regions</li> +for all the world's regions. These maps are no longer maintained and +are superseded by the Timezone Boundary Builder.</li> <li><a href="https://github.com/straup/whereonearth-timezone">Whereonearth-timezone</a> is in <a href="https://tools.ietf.org/html/rfc7946">GeoJSON</a> format @@ -633,10 +632,7 @@ the <a href="https://timezonedb.com">Time Zone Database & API</a>. Commercial network API access is provided by <a href="https://askgeo.com">AskGeo</a> and <a href="https://www.geogarage.com/blog/news-1/post/geogarage-time-zone-api-31">GeoGarage</a>. -Also, an <a -href="https://mm.icann.org/pipermail/tz/2016-October/024309.html">experimental -server</a> is available for the TZDIST Geolocate Extension mentioned -<a href="#TZDIST-Geolocate">above</a>.</li> +</li> <li>"<a href="https://stackoverflow.com/questions/16086962/how-to-get-a-time-zone-from-a-…">How to get a time zone from a location using latitude and longitude @@ -648,13 +644,10 @@ political subdivision data related to time zones.</li> zone boundaries for multizone countries</a> summarizes legal boundaries between time zones within countries.</li> <li>Manifold.net's <a -href="http://manifold.net/info/freestuff.shtml">Free Stuff for +href="http://manifold.net/info/freestuff.shtml">Free Downloads for Manifold System Users</a> includes a Manifold-format map of world time zone boundaries distributed under the <abbr>GPL</abbr>.</li> -<li>The GeoCommunity lists several commercial sources for <a -href="http://spatialnews.geocomm.com/features/timezones/">International -Time Zones and Time Zone Data</a>.</li> <li>A ship within the <a href="https://en.wikipedia.org/wiki/Territorial_waters">territorial waters</a> of any nation uses that nation's time. In international @@ -723,7 +716,7 @@ href="ftp://ftp.cs.huji.ac.il/pub/tz/announcements" hreflang="he">announcements (in Hebrew)</a>.</dd> <dt>Italy</dt> <dd>The National Institute of Metrological Research maintains a -<a href="http://www.inrim.it/res/tf/ora_legale_i.shtml">table of civil time +<a href="http://www.nanospin.eu/res/tf/ora_legale_i.shtml">table of civil time (in Italian)</a>.</dd> <dt>Mexico</dt> <dd>The Investigation and Analysis Service of the Mexican Library of @@ -763,7 +756,7 @@ Time Zone Proceedings</a> lists changes to time zone boundaries.</dd> <h2 id="precision">Precision timekeeping</h2> <ul> <li><a -href="http://literature.agilent.com/litweb/pdf/5965-7984E.pdf">The +href="http://leapsecond.com/hpan/an1289.pdf">The Science of Timekeeping</a> is a thorough introduction to the theory and practice of precision timekeeping.</li> <li><a href="http://www.ntp.org"><abbr @@ -882,10 +875,6 @@ protocols.</li> <a href="https://www.hackcraft.net/web/datetime/">Date & Time Formats on the Web</a> surveys web- and Internet-oriented date and time formats.</li> -<li> -<a href="http://exit109.com/~ghealton/y2k/yrexamples.html">The -Best of Dates, the Worst of Dates</a> covers many problems encountered -by software developers when handling dates and time stamps.</li> <li>Alphabetic time zone abbreviations should not be used as unique identifiers for <abbr>UTC</abbr> offsets as they are ambiguous in practice. For example, in English-speaking North America -- 2.7.4

1 0