Sync zoneinfo database with tzdata2014h from ftp://ftp.iana.org/tz/releases

Operating Systems / DragonFlyBSD - Sascha Wildner [online.de] - 12 October 2014 07:51 UTC

We're coming from tzdata2014e.

Changes affecting future time stamps:

- Russia will subtract an hour from most of its time zones on 2014-10-26 at 02:00 local time. (Thanks to Alexander Krivenyshev.)

- Turks & Caicos is switching from US eastern time to UTC-4 year-round, modeled as a switch from EST/EDT to AST on 2014-11-02 at 02:00.

- Tons of changes to past time stamps and cleanup. It's really too much to repeat here. Please see the NEWS file for further information.

###

diff --git a/share/zoneinfo/NEWS b/share/zoneinfo/NEWS
index f437c04..5e33102 100644
--- a/share/zoneinfo/NEWS
+++ b/share/zoneinfo/NEWS
@@ -1,5 +1,431 @@
News for the tz database

+Release 2014h - 2014-09-25 18:59:03 -0700
+
+ Changes affecting past time stamps
+
+ America/Jamaica's 1974 spring-forward transition was Jan. 6, not Apr. 28.
+
+ Shanks says Asia/Novokuznetsk switched from LMT (not "NMT") on 1924-05-01,
+ not 1920-01-06. The old entry was based on a misinterpretation of Shanks.
+
+ Some more zones have been turned into links, when they differed
+ from existing zones only for older time stamps. As usual,
+ these changes affect UTC offsets in pre-1970 time stamps only.
+ Their old contents have been moved to the 'backzone' file.
+ The affected zones are: Africa/Blantyre, Africa/Bujumbura,
+ Africa/Gaborone, Africa/Harare, Africa/Kigali, Africa/Lubumbashi,
+ Africa/Lusaka, Africa/Maseru, and Africa/Mbabane.
+
+ Changes affecting code
+
+ zdump -V and -v now output gmtoff= values on all platforms,
+ not merely on platforms defining TM_GMTOFF.
+
+ The tz library's localtime and mktime functions now set tzname to a value
+ appropriate for the requested time stamp, and zdump now uses this
+ on platforms not defining TM_ZONE, fixing a 2014g regression.
+ (Thanks to Tim Parenti for reporting the problem.)
+
+ The tz library no longer sets tzname if localtime or mktime fails.
+
+ zdump -c no longer mishandles transitions near year boundaries.
+ (Thanks to Tim Parenti for reporting the problem.)
+
+ An access to uninitalized data has been fixed.
+ (Thanks to Jörg Richter for reporting the problem.)
+
+ When THREAD_SAFE is defined, the code ports to the C11 memory model.
+ A memory leak has been fixed if ALL_STATE and THREAD_SAFE are defined
+ and two threads race to initialize data used by gmtime-like functions.
+ (Thanks to Andy Heninger for reporting the problems.)
+
+ Changes affecting build procedure
+
+ 'make check' now checks better for properly-sorted data.
+
+ Changes affecting documentation and commentary
+
+ zdump's gmtoff=N output is now documented, and its isdst=D output
+ is now documented to possibly output D values other than 0 or 1.
+
+ zdump -c's treatment of years is now documented to use the
+ Gregorian calendar and Universal Time without leap seconds,
+ and its behavior at cutoff boundaries is now documented better.
+ (Thanks to Arthur David Olson and Tim Parenti for reporting the problems.)
+
+ Programs are now documented to use the proleptic Gregorian calendar.
+ (Thanks to Alan Barrett for the suggestion.)
+
+ Fractional-second GMT offsets have been documented for civil time
+ in 19th-century Chennai, Jakarta, and New York.
+
+
+Release 2014g - 2014-08-28 12:31:23 -0700
+
+ Changes affecting future time stamps
+
+ Turks & Caicos is switching from US eastern time to UTC-4 year-round,
+ modeled as a switch from EST/EDT to AST on 2014-11-02 at 02:00.
+
+ Changes affecting past time stamps
+
+ Time in Russia or the USSR before 1926 or so has been corrected by
+ a few seconds in the following zones: Asia/Irkutsk,
+ Asia/Krasnoyarsk, Asia/Omsk, Asia/Samarkand, Asia/Tbilisi,
+ Asia/Vladivostok, Asia/Yakutsk, Europe/Riga, Europe/Samara. For
+ Asia/Yekaterinburg the correction is a few minutes. (Thanks to
+ Vladimir Karpinsky.)
+
+ The Portuguese decree of 1911-05-26 took effect on 1912-01-01.
+ This affects 1911 time stamps in Africa/Bissau, Africa/Luanda,
+ Atlantic/Azores, and Atlantic/Madeira. Also, Lisbon's pre-1912
+ GMT offset was -0:36:45 (rounded from -0:36:44.68), not -0:36:32.
+ (Thanks to Stephen Colebourne for pointing to the decree.)
+
+ Asia/Dhaka ended DST on 2009-12-31 at 24:00, not 23:59.
+
+ A new file 'backzone' contains data which may appeal to
+ connoisseurs of old time stamps, although it is out of scope for
+ the tz database, is often poorly sourced, and contains some data
+ that is known to be incorrect. The new file is not recommended
+ for ordinary use and its entries are not installed by default.
+ (Thanks to Lester Caine for the high-quality Jersey, Guernsey, and
+ Isle of Man entries.)
+
+ Some more zones have been turned into links, when they differed
+ from existing zones only for older time stamps. As usual,
+ these changes affect UTC offsets in pre-1970 time stamps only.
+ Their old contents have been moved to the 'backzone' file.
+ The affected zones are: Africa/Bangui, Africa/Brazzaville,
+ Africa/Douala, Africa/Kinshasa, Africa/Libreville, Africa/Luanda,
+ Africa/Malabo, Africa/Niamey, and Africa/Porto-Novo.
+
+ Changes affecting code
+
+ Unless NETBSD_INSPIRED is defined to 0, the tz library now
+ supplies functions for creating and using objects that represent
+ time zones. The new functions are tzalloc, tzfree, localtime_rz,
+ mktime_z, and (if STD_INSPIRED is also defined) posix2time_z and
+ time2posix_z. They are intended for performance: for example,
+ localtime_rz (unlike localtime_r) is trivially thread-safe without
+ locking. (Thanks to Christos Zoulas for proposing NetBSD-inspired
+ functions, and to Alan Barrett and Jonathan Lennox for helping to
+ debug the change.)
+
+ zdump now builds with the tz library unless USE_LTZ is defined to 0,
+ This lets zdump use tz features even if the system library lacks them.
+ To build zdump with the system library, use 'make CFLAGS=-DUSE_LTZ=0
+ TZDOBJS=zdump.o CHECK_TIME_T_ALTERNATIVES='.
+
+ zdump now uses localtime_rz if available, as it's significantly faster,
+ and it can help zdump better diagnose invalid time zone names.
+ Define HAVE_LOCALTIME_RZ to 0 to suppress this. HAVE_LOCALTIME_RZ
+ defaults to 1 if NETBSD_INSPIRED && USE_LTZ. When localtime_rz is
+ not available, zdump now uses localtime_r and tzset if available,
+ as this is a bit cleaner and faster than plain localtime. Compile
+ with -DHAVE_LOCALTIME_R=0 and/or -DHAVE_TZSET=0 if your system
+ lacks these two functions.
+
+ If THREAD_SAFE is defined to 1, the tz library is now thread-safe.
+ Although not needed for tz's own applications, which are single-threaded,
+ this supports POSIX better if the tz library is used in multithreaded apps.
+
+ Some crashes have been fixed when zdump or the tz library is given
+ invalid or outlandish input.
+
+ The tz library no longer mishandles leap seconds on platforms with
+ unsigned time_t in time zones that lack ordinary transitions after 1970.
+
+ The tz code now attempts to infer TM_GMTOFF and TM_ZONE if not
+ already defined, to make it easier to configure on common platforms.
+ Define NO_TM_GMTOFF and NO_TM_ZONE to suppress this.
+
+ Unless the new macro UNINIT_TRAP is defined to 1, the tz code now
+ assumes that reading uninitialized memory yields garbage values
+ but does not cause other problems such as traps.
+
+ If TM_GMTOFF is defined and UNINIT_TRAP is 0, mktime is now
+ more likely to guess right for ambiguous time stamps near
+ transitions where tm_isdst does not change.
+
+ If HAVE_STRFTIME_L is defined to 1, the tz library now defines
+ strftime_l for compatibility with recent versions of POSIX.
+ Only the C locale is supported, though. HAVE_STRFTIME_L defaults
+ to 1 on recent POSIX versions, and to 0 otherwise.
+
+ tzselect -c now uses a hybrid distance measure that works better
+ in Africa. (Thanks to Alan Barrett for noting the problem.)
+
+ The C source code now ports to NetBSD when GCC_DEBUG_FLAGS is used,
+ or when time_tz is defined.
+
+ When HAVE_UTMPX_H is set the 'date' command now builds on systems
+ whose file does not define WTMPX_FILE, and when setting
+ the date it updates the wtmpx file if _PATH_WTMPX is defined.
+ This affects GNU/Linux and similar systems.
+
+ For easier maintenance later, some C code has been simplified,
+ some lint has been removed, and the code has been tweaked so that
+ plain 'make' is more likely to work.
+
+ The C type 'bool' is now used for boolean values, instead of 'int'.
+
+ The long-obsolete LOCALE_HOME code has been removed.
+
+ The long-obsolete 'gtime' function has been removed.
+
+ Changes affecting build procedure
+
+ 'zdump' no longer links in ialloc.o, as it's not needed.
+
+ 'make check_time_t_alternatives' no longer assumes GNU diff.
+
+ Changes affecting distribution tarballs
+
+ The files checktab.awk and zoneinfo2tdf.pl are now distributed in
+ the tzdata tarball instead of the tzcode tarball, since they help
+ maintain the data. The NEWS and Theory files are now also
+ distributed in the tzdata tarball, as they're relevant for data.
+ (Thanks to Alan Barrett for pointing this out.) Also, the
+ leapseconds.awk file is no longer distributed in the tzcode
+ tarball, since it belongs in the tzdata tarball (where 2014f
+ inadvertently also distributed it).
+
+ Changes affecting documentation and commentary
+
+ A new file CONTRIBUTING is distributed. (Thanks to Tim Parenti for
+ suggesting a CONTRIBUTING file, and to Tony Finch and Walter Harms
+ for debugging it.)
+
+ The man pages have been updated to use function prototypes,
+ to document thread-safe variants like localtime_r, and to document
+ the NetBSD-inspired functions tzalloc, tzfree, localtime_rz, and
+ mktime_z.
+
+ The fields in Link lines have been renamed to be more descriptive
+ and more like the parameters of 'ln'. LINK-FROM has become TARGET,
+ and LINK-TO has become LINK-NAME.
+
+ tz-link.htm mentions the IETF's tzdist working group; Windows
+ Runtime etc. (thanks to Matt Johnson); and HP-UX's tztab.
+
+ Some broken URLs have been fixed in the commentary. (Thanks to
+ Lester Caine.)
+
+ Commentary about Philippines DST has been updated, and commentary
+ on pre-1970 time in India has been added.
+
+
+Release 2014f - 2014-08-05 17:42:36 -0700
+
+ Changes affecting future time stamps
+
+ Russia will subtract an hour from most of its time zones on 2014-10-26
+ at 02:00 local time. (Thanks to Alexander Krivenyshev.)
+ There are a few exceptions: Magadan Oblast (Asia/Magadan) and Zabaykalsky
+ Krai are subtracting two hours; conversely, Chukotka Autonomous Okrug
+ (Asia/Anadyr), Kamchatka Krai (Asia/Kamchatka), Kemerovo Oblast
+ (Asia/Novokuznetsk), and the Samara Oblast and the Udmurt Republic
+ (Europe/Samara) are not changing their clocks. The changed zones are
+ Europe/Kaliningrad, Europe/Moscow, Europe/Simferopol, Europe/Volgograd,
+ Asia/Yekaterinburg, Asia/Omsk, Asia/Novosibirsk, Asia/Krasnoyarsk,
+ Asia/Irkutsk, Asia/Yakutsk, Asia/Vladivostok, Asia/Khandyga,
+ Asia/Sakhalin, and Asia/Ust-Nera; Asia/Magadan will have two hours
+ subtracted; and Asia/Novokuznetsk's time zone abbreviation is affected,
+ but not its UTC offset. Two zones are added: Asia/Chita (split
+ from Asia/Yakutsk, and also with two hours subtracted) and
+ Asia/Srednekolymsk (split from Asia/Magadan, but with only one hour
+ subtracted). (Thanks to Tim Parenti for much of the above.)
+
+ Changes affecting time zone abbreviations
+
+ Australian eastern time zone abbreviations are now AEST/AEDT not EST,
+ and similarly for the other Australian zones. That is, for eastern
+ standard and daylight saving time the abbreviations are AEST and AEDT
+ instead of the former EST for both; similarly, ACST/ACDT, ACWST/ACWDT,
+ and AWST/AWDT are now used instead of the former CST, CWST, and WST.
+ This change does not affect UTC offsets, only time zone abbreviations.
+ (Thanks to Rich Tibbett and many others.)
+
+ Asia/Novokuznetsk shifts from NOVT to KRAT (remaining on UTC+7)
+ effective 2014-10-26 at 02:00 local time.
+
+ The time zone abbreviation for Xinjiang Time (observed in Ürümqi)
+ has been changed from URUT to XJT. (Thanks to Luther Ma.)
+
+ Prefer MSK/MSD for Moscow time in Russia, even in other cities.
+ Similarly, prefer EET/EEST for eastern European time in Russia.
+
+ Change time zone abbreviations in (western) Samoa to use "ST" and
+ "DT" suffixes, as this is more likely to match common practice.
+ Prefix "W" to (western) Samoa time when its standard-time offset
+ disagrees with that of American Samoa.
+
+ America/Metlakatla now uses PST, not MeST, to abbreviate its time zone.
+
+ Time zone abbreviations have been updated for Japan's two time
+ zones used 1896-1937. JWST now stands for Western Standard
+ Time, and JCST for Central Standard Time (formerly this was CJT).
+ These abbreviations are now used for time in Korea, Taiwan,
+ and Sakhalin while controlled by Japan.
+
+ Changes affecting past time stamps
+
+ China's five zones have been simplified to two, since the post-1970
+ differences in the other three seem to have been imaginary. The
+ zones Asia/Harbin, Asia/Chongqing, and Asia/Kashgar have been
+ removed; backwards-compatibility links still work, albeit with
+ different behaviors for time stamps before May 1980. Asia/Urumqi's
+ 1980 transition to UTC+8 has been removed, so that it is now at
+ UTC+6 and not UTC+8. (Thanks to Luther Ma and to Alois Treindl;
+ Treindl sent helpful translations of two papers by Guo Qingsheng.)
+
+ Some zones have been turned into links, when they differed from existing
+ zones only for older UTC offsets where data entries were likely invented.
+ These changes affect UTC offsets in pre-1970 time stamps only. This is
+ similar to the change in release 2013e, except this time for western
+ Africa. The affected zones are: Africa/Bamako, Africa/Banjul,
+ Africa/Conakry, Africa/Dakar, Africa/Freetown, Africa/Lome,
+ Africa/Nouakchott, Africa/Ouagadougou, Africa/Sao_Tome, and
+ Atlantic/St_Helena. This also affects the backwards-compatibility
+ link Africa/Timbuktu. (Thanks to Alan Barrett, Stephen Colebourne,
+ Tim Parenti, and David Patte for reporting problems in earlier
+ versions of this change.)
+
+ Asia/Shanghai's pre-standard-time UT offset has been changed from
+ 8:05:57 to 8:05:43, the location of Xujiahui Observatory. Its
+ transition to standard time has been changed from 1928 to 1901.
+
+ Asia/Taipei switched to JWST on 1896-01-01, then to JST on 1937-10-01,
+ then to CST on 1945-09-21 at 01:00, and did not observe DST in 1945.
+ In 1946 it observed DST from 05-15 through 09-30; in 1947
+ from 04-15 through 10-31; and in 1979 from 07-01 through 09-30.
+ (Thanks to Yu-Cheng Chuang.)
+
+ Asia/Riyadh's transition to standard time is now 1947-03-14, not 1950.
+
+ Europe/Helsinki's 1942 fall-back transition was 10-04 at 01:00, not
+ 10-03 at 00:00. (Thanks to Konstantin Hyppönen.)
+
+ Pacific/Pago_Pago has been changed from UTC-11:30 to UTC-11 for the period
+ from 1911 to 1950.
+
+ Pacific/Chatham has been changed to New Zealand standard time plus
+ 45 minutes for the period before 1957, reflecting a 1956 remark in
+ the New Zealand parliament.
+
+ Europe/Budapest has several pre-1946 corrections: in 1918 the transition
+ out of DST was on 09-16, not 09-29; in 1919 it was on 11-24, not 09-15; in
+ 1945 it was on 11-01, not 11-03; in 1941 the transition to DST was 04-08
+ not 04-06 at 02:00; and there was no DST in 1920.
+
+ Africa/Accra is now assumed to have observed DST from 1920 through 1935.
+
+ Time in Russia before 1927 or so has been corrected by a few seconds in
+ the following zones: Europe/Moscow, Asia/Irkutsk, Asia/Tbilisi,
+ Asia/Tashkent, Asia/Vladivostok, Asia/Yekaterinburg, Europe/Helsinki, and
+ Europe/Riga. Also, Moscow's location has been changed to its Kilometer 0
+ point. (Thanks to Vladimir Karpinsky for the Moscow changes.)
+
+ Changes affecting data format
+
+ A new file 'zone1970.tab' supersedes 'zone.tab' in the installed data.
+ The new file's extended format allows multiple country codes per zone.
+ The older file is still installed but is deprecated; its format is
+ not changing and it will still be distributed for a while, but new
+ applications should use the new file.
+
+ The new file format simplifies maintenance of obscure locations.
+ To test this, it adds coverage for the Crozet Islands and the
+ Scattered Islands. (Thanks to Tobias Conradi and Antoine Leca.)
+
+ The file 'iso3166.tab' is planned to switch from ASCII to UTF-8.
+ It is still ASCII now, but commentary about the switch has been added.
+ The new file 'zone1970.tab' already uses UTF-8.
+
+ Changes affecting code
+
+ 'localtime', 'mktime', etc. now use much less stack space if ALL_STATE
+ is defined. (Thanks to Elliott Hughes for reporting the problem.)
+
+ 'zic' no longer mishandles input when ignoring case in locales that
+ are not compatible with English, e.g., unibyte Turkish locales when
+ compiled with HAVE_GETTEXT.
+
+ Error diagnostics of 'zic' and 'yearistype' have been reworded so that
+ they no longer use ASCII '-' as if it were a dash.
+
+ 'zic' now rejects output file names that contain '.' or '..' components.
+ (Thanks to Tim Parenti for reporting the problem.)
+
+ 'zic -v' now warns about output file names that do not follow
+ POSIX rules, or that contain a digit or '.'. (Thanks to Arthur
+ David Olson for starting the ball rolling on this.)
+
+ Some lint has been removed when using GCC_DEBUG_FLAGS with GCC 4.9.0.
+
+ Changes affecting build procedure
+
+ 'zic' no longer links in localtime.o and asctime.o, as they're not needed.
+ (Thanks to John Cochran.)
+
+ Changes affecting documentation and commentary
+
+ The 'Theory' file documents legacy names, the longstanding
+ exceptions to the POSIX-inspired file name rules.
+
+ The 'zic' documentation clarifies the role of time types when
+ interpreting dates. (Thanks to Arthur David Olson.)
+
+ Documentation and commentary now prefer UTF-8 to US-ASCII,
+ allowing the use of proper accents in foreign words and names.
+ Code and data have not changed because of this. (Thanks to
+ Garrett Wollman, Ian Abbott, and Guy Harris for helping to debug
+ this.)
+
+ Non-HTML documentation and commentary now use plain-text URLs instead of
+ HTML insertions, and are more consistent about bracketing URLs when they
+ are not already surrounded by white space. (Thanks to suggestions by
+ Steffen Nurpmeso.)
+
+ There is new commentary about Xujiahui Observatory, the five time-zone
+ project in China from 1918 to 1949, timekeeping in Japanese-occupied
+ Shanghai, and Tibet Time in the 1950s. The sharp-eyed can spot the
+ warlord Jin Shuren in the data.
+
+ Commentary about the coverage of each Russian zone has been standardized.
+ (Thanks to Tim Parenti).
+
+ There is new commentary about contemporary timekeeping in Ethiopia.
+
+ Obsolete comments about a 2007 proposal for DST in Kuwait has been removed.
+
+ There is new commentary about time in Poland in 1919.
+
+ Proper credit has been given to DST inventor George Vernon Hudson.
+
+ Commentary about time in Metlakatla, AK and Resolute, NU has been
+ improved, with a new source for the former.
+
+ In zone.tab, Pacific/Easter no longer mentions Salas y Gómez, as it
+ is uninhabited.
+
+ Commentary about permanent Antarctic bases has been updated.
+
+ Several typos have been corrected. (Thanks to Tim Parenti for
+ contributing some of these fixes.)
+
+ tz-link.htm now mentions the JavaScript libraries Moment Timezone,
+ TimezoneJS.Date, Walltime-js, and Timezone. (Thanks to a heads-up
+ from Matt Johnson.) Also, it mentions the Go 'latlong' package.
+ (Thanks to a heads-up from Dirkjan Ochtman.)
+
+ The files usno1988, usno1989, usno1989a, usno1995, usno1997, and usno1998
+ have been removed. These obsolescent US Naval Observatory entries were no
+ longer helpful for maintenance. (Thanks to Tim Parenti for the suggestion.)
+
+
Release 2014e - 2014-06-12 21:53:52 -0700

Changes affecting near-future time stamps
@@ -83,7 +509,7 @@ Release 2014b - 2014-03-24 21:28:50 -0700
Changes affecting code

'zic' and 'localtime' no longer reject locations needing four transitions
- per year for the forseeable future. (Thanks to Andrew Main (Zefram).)
+ per year for the foreseeable future. (Thanks to Andrew Main (Zefram).)
Also, 'zic' avoids some unlikely failures due to integer overflow.

Changes affecting build procedure
@@ -140,9 +566,9 @@ Release 2014a - 2014-03-07 23:30:29 -0800
The boundary of the US Pacific time zone is given more accurately.
(Thanks to Alan Mintz.)

- Chile's 2014 DST will be as predicted. (Thanks to Jose Miguel Garrido.)
+ Chile's 2014 DST will be as predicted. (Thanks to José Miguel Garrido.)

- Paraguay's 2014 DST will be as predicted. (Thanks to Carlos Raul Perasso.)
+ Paraguay's 2014 DST will be as predicted. (Thanks to Carlos Raúl Perasso.)

Better descriptions of countries with same time zone history as
Trinidad and Tobago since 1970. (Thanks to Alan Barrett for suggestion.)
@@ -156,7 +582,7 @@ Release 2014a - 2014-03-07 23:30:29 -0800

Microsoft has some support for tz database names.

- CLDR data is available in both XML and JSON form.
+ CLDR data formats include both XML and JSON.

Mention Maggiolo's map of solar vs standard time.
(Thanks to Arthur David Olson.)
@@ -165,7 +591,7 @@ Release 2014a - 2014-03-07 23:30:29 -0800

Mention the timezone-olson Haskell package.

- Mention zeitverschiebung.net. (Thanks to Martin Jaeger.)
+ Mention zeitverschiebung.net. (Thanks to Martin Jäger.)

Remove moribund links to daylight-savings-time.info and to
Simple Timer + Clocks.
@@ -198,7 +624,7 @@ Release 2013i - 2013-12-17 07:25:23 -0800
Changes affecting documentation and commentary

The files solar87, solar88, and solar89 are no longer distributed.
- They were a negative experiment -- that is, a demonstration that
+ They were a negative experiment - that is, a demonstration that
tz data can represent solar time only with some difficulty and error.
Their presence in the distribution caused confusion, as Riyadh
civil time was generally not solar time in those years.
@@ -231,7 +657,7 @@ Release 2013h - 2013-10-25 15:32:32 -0700
The 'tzselect' command no longer requires the 'select' command,
and should now work with /bin/sh on more platforms. It also works
around a bug in BusyBox awk before version 1.21.0. (Thanks to
- Patrick 'P. J.' McDermott.)
+ Patrick 'P. J.' McDermott and Alan Barrett.)

Changes affecting code

@@ -258,7 +684,7 @@ Release 2013h - 2013-10-25 15:32:32 -0700

Changes affecting documentation and commentary

- tz-link.htm now mentions TC TIMEZONE's draft timezone service protocol
+ tz-link.htm now mentions TC TIMEZONE's draft time zone service protocol
(thanks to Mike Douglass) and TimezoneJS.Date (thanks to Jim Fehrle).

Update URLs in tz-link page. Add URLs for Microsoft Windows, since
@@ -336,7 +762,7 @@ Release 2013f - 2013-09-24 23:37:36 -0700

Changes affecting version-control only

- The experimental github repository now contains annotated and
+ The experimental GitHub repository now contains annotated and
signed tags for recent releases, e.g., '2013e' for Release 2013e.
Releases are tagged starting with 2012e; earlier releases were
done differently, and tags would either not have a simple name or
@@ -365,7 +791,7 @@ Release 2013e - 2013-09-19 23:50:04 -0700
Use ART (UTC-3, standard time), rather than WARST (also UTC-3, but
daylight saving time) for San Luis, Argentina since 2009.

- Changes affecting Godthab time stamps after 2037 if version mismatch
+ Changes affecting Godthåb time stamps after 2037 if version mismatch

Allow POSIX-like TZ strings where the transition time's hour can
range from -167 through 167, instead of the POSIX-required 0
@@ -399,9 +825,9 @@ Release 2013e - 2013-09-19 23:50:04 -0700
Pacific/Johnston is now a link to Pacific/Honolulu. This corrects
some errors before 1947.

- Some zones have been turned into links, when they differ from
- existing zones only in older data that was likely invented or that
- differs only in LMT or transition from LMT. These changes affect
+ Some zones have been turned into links, when they differ from existing
+ zones only in older data entries that were likely invented or that
+ differ only in LMT or transitions from LMT. These changes affect
only time stamps before 1943. The affected zones are:
Africa/Juba, America/Anguilla, America/Aruba, America/Dominica,
America/Grenada, America/Guadeloupe, America/Marigot,
@@ -458,7 +884,7 @@ Release 2013e - 2013-09-19 23:50:04 -0700
The signatures of 'offtime', 'timeoff', and 'gtime' have been
changed back to the old practice of using 'long' to represent UT
offsets. This had been inadvertently and mistakenly changed to
- 'int_fast32_t'. (Thanks to Christos Zoulos.)
+ 'int_fast32_t'. (Thanks to Christos Zoulas.)

The code avoids undefined behavior on integer overflow in some
more places, including gmtime, localtime, mktime and zdump.
@@ -477,7 +903,7 @@ Release 2013e - 2013-09-19 23:50:04 -0700

Remove from zone.tab the names America/Montreal, America/Shiprock,
and Antarctica/South_Pole, as they are equivalent to existing
- same-country-code zones for post-1970 time stamps. The data for
+ same-country-code zones for post-1970 time stamps. The data entries for
these names are unchanged, so the names continue to work as before.

Changes affecting code internals
@@ -627,7 +1053,7 @@ Release 2013c - 2013-04-19 16:17:40 -0700

Assume that the recent change to Paraguay's DST rules is permanent,
by moving the end of DST to the 4th Sunday in March every year.
- (Thanks to Carlos Raul Perasso.)
+ (Thanks to Carlos Raúl Perasso.)

Changes affecting past time stamps:

@@ -688,7 +1114,7 @@ Release 2013a - 2013-02-27 09:20:35 -0800
Change affecting binary data format:

The zone offset at the end of version-2-format zone files is now
- allowed to be 24:00, as per POSIX.1-2008. (Thanks to Arthor David Olson.)
+ allowed to be 24:00, as per POSIX.1-2008. (Thanks to Arthur David Olson.)

Changes affecting current and future time stamps:

@@ -767,7 +1193,7 @@ Release 2012i - 2012-11-03 12:57:09 -0700
AWK now defaults to 'awk', not 'nawk'.
The shell in tzselect now defaults to /bin/bash, but this can
be overridden by specifying KSHELL.
- The main web page now mentions the unofficial github repository.
+ The main web page now mentions the unofficial GitHub repository.
(Thanks to Mike Frysinger.)

Tarball signatures can now be built by running 'make signatures'.
@@ -889,7 +1315,7 @@ Release 2012a - 2012-03-01 18:28:10 +0700

Other minor changes are:
Corrections to 1918 Canadian summer time end dates.
- Updated URL for UK timezone history (in comments)
+ Updated URL for UK time zone history (in comments)
A few typos in Le Corre's list of free French place names (comments)


@@ -925,7 +1351,7 @@ Release data2011m - 2011-10-24 21:42:16 +0700
version numbers there...)


-Release data2011l - 2011-10-10 11:15:43 +0700
+Release data2011l - 2011-10-10 11:15:43 +0700

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
@@ -955,7 +1381,7 @@ Release 2011i - 2011-08-29 05:56:32 -0400

Release data2011h - 2011-06-15 18:41:48 -0400

- Russia and Curacao changes
+ Russia and Curaçao changes


Release 2011g - 2011-04-25 09:07:22 -0400
@@ -1020,7 +1446,7 @@ Release 2010k - 2010-07-26 10:42:27 -0400

Release 2010j - 2010-05-10 09:07:48 -0400

- changes for Bahia de Banderas and for version naming
+ changes for Bahía de Banderas and for version naming


Release data2010i - 2010-04-16 18:50:45 -0400
@@ -1123,7 +1549,7 @@ Release data2009m - 2009-09-03 10:23:43 -0400

Release data2009l - 2009-08-14 09:13:07 -0400

- Samao (comments only) and Egypt
+ Samoa (comments only) and Egypt


Release 2009k - 2009-07-20 09:46:08 -0400
@@ -1206,7 +1632,7 @@ Release data2008f - 2008-09-09 22:33:26 -0400

Release 2008e - 2008-07-28 14:11:17 -0400

- changes by Arthur David Olson and Jesper Norgaard Welen
+ changes by Arthur David Olson and Jesper Nørgaard Welen


Release data2008d - 2008-07-07 09:51:38 -0400
@@ -1451,7 +1877,7 @@ Release 2005o - 2005-11-28 10:55:26 -0500

Release 2005n - 2005-10-03 09:44:09 -0400

- changes by Paul Eggert (both the Uruguary changes and the Kyrgyzstan
+ changes by Paul Eggert (both the Uruguay changes and the Kyrgyzstan
et al. changes)


@@ -1601,7 +2027,7 @@ Release 2004c - 2004-08-11 12:06:26 -0400

Release 2004b - 2004-07-19 14:33:35 -0400

- data changes by Paul Eggert--most importantly, updates for Argentina
+ data changes by Paul Eggert - most importantly, updates for Argentina


Release 2004a - 2004-05-27 12:00:47 -0400
@@ -1697,7 +2123,7 @@ Release 2001b - 2001-04-05 16:44:38 -0400

changes by Paul Eggert (modulo jnorgard's typo fix)

- tz-art.htm has been htmlified.
+ tz-art.htm has been HTMLified.


Release 2001a - 2001-03-13 12:57:44 -0500
@@ -1718,7 +2144,7 @@ Release 2000h - 2000-12-14 15:33:38 -0500

one typo fix in the "art" file

- With providence, this is the last update of the millenium.
+ With providence, this is the last update of the millennium.


Release 2000g - 2000-10-10 11:35:22 -0400
@@ -1966,7 +2392,7 @@ Release code1997f-data1997g - 1997-07-19 13:15:02 -0400

a small change to a function prototype;

- "Music" has been renamed "Arts.htm", htmlified, and augmented to
+ "Music" has been renamed "Arts.htm", HTMLified, and augmented to
include information on Around the World in Eighty Days.


@@ -1976,7 +2402,7 @@ Release code1997e-data1997f - 1997-05-03 18:52:34 -0400

changes inspired by the item circulated on Slovenia

- The description of Web resources has been htmlified for browsing
+ The description of Web resources has been HTMLified for browsing
convenience.

A new piece of tz-related music has been added to the "Music" file.
@@ -2078,7 +2504,7 @@ Release code96g - 1996-05-16 14:00:26 -0400
fix for the simultaneous-DST-and-zone-change challenge


-Release data96h - 1996-05-09 17:40:51-0400
+Release data96h - 1996-05-09 17:40:51 -0400

changes by Paul Eggert

@@ -2116,7 +2542,7 @@ Release data96d - 1996-03-18 20:49:39 -0500
[not summarized]


-Release code96e - 1996-02-29 15:43:27 -0000
+Release code96e - 1996-02-29 15:43:27 -0000
[tzcode96e.tar.gz is missing!]

internationalization changes and the fix to the documentation for strftime
@@ -2134,7 +2560,7 @@ Release data96b - 1996-01-27 15:44:42 -0500
Kiribati change


-Release code96c - 1996-01-16 16:58:15-0500
+Release code96c - 1996-01-16 16:58:15 -0500

leap-year streamlining and binary-search changes

@@ -2200,8 +2626,8 @@ Release code95e - 1995-10-13 13:23:57 -0400

Release data95i - 1995-09-26 10:43:26 -0400

- For Canada/Central, guess that the Sun customer's ``one week too
- early'' was just a approximation, and the true error is one month
+ For Canada/Central, guess that the Sun customer's "one week too
+ early" was just a approximation, and the true error is one month
too early. This is consistent with the rest of Canada.


@@ -2268,12 +2694,12 @@ Release 94h - 1994-12-10 12:51:14 -0500
* incorporate the table changes by Paul Eggert;

* include (and document) support for universal time specifications in
- data files--but do not (yet) include use of this feature in the
+ data files - but do not (yet) include use of this feature in the
data files.

- Think of this as "TZ Classic"--the software has been set up not to break if
- universal time shows up in its input, and the data has been left as is so as
- not to break existing implementations.
+ Think of this as "TZ Classic" - the software has been set up not to break if
+ universal time shows up in its input, and data entries have been
+ left as is so as not to break existing implementations.


Release data94f - 1994-08-20 12:56:09 -0400
@@ -2324,7 +2750,7 @@ Release 94b - 1994-02-07 10:04:33 -0500
as extensive as Shanks but has a few goodies of its own. I used it
to update the tables. I also fixed some more as a result of
correspondence with Adam David and Peter Ilieve, and move some stray
- links from `europe' to `backward'. I corrected some scanning errors
+ links from 'europe' to 'backward'. I corrected some scanning errors
in usno1989.

As far as the code goes, I fixed zic to allow years in the range
@@ -2352,7 +2778,7 @@ Release 93f - 1993-10-15 12:27:46 -0400

Release 93e - 1993-09-05 21:21:44 -0400

- There's updated data for Israel, England, and Kwajalein; there's
+ This has updated data for Israel, England, and Kwajalein. There's
also an update to "zdump" to cope with Kwajalein's 24-hour jump.
Thanks to Paul Eggert and Peter Ilieve for the changes.

@@ -2374,14 +2800,14 @@ Release 93b - 1993-02-02 14:53:58 -0500

Release 93 - 1993-01-08 07:01:06 -0500

- At kre's suggestion, the package has been split in two--a code piece
+ At kre's suggestion, the package has been split in two - a code piece
(which also includes documentation) that's only of use to folks who
want to recompile things and a data piece useful to anyone who can
run "zic".

The new version has a few changes to the data files, a few
portability changes, and an off-by-one fix (with thanks to
- Tom-Karzes at deshaw.com for providing a description and a
+ Tom Karzes at deshaw.com for providing a description and a
solution).


@@ -2447,10 +2873,14 @@ numbers.
Release time stamps are taken from the release's commit (for newer,
git releases), from the newest file in the tarball (for older
releases, where this info is available) or from the email announcing
-the release (if all else fails; these are marked with a timezone of
+the release (if all else fails; these are marked with a time zone of
-0000 and an "is missing!" comment).

Earlier versions of the code and data were not announced on the tz
list and are not summarized here.

This file is in the public domain.
+
+Local Variables:
+coding: utf-8
+End:
diff --git a/share/zoneinfo/README b/share/zoneinfo/README
index 0b0bbbe..06ef1d9 100644
--- a/share/zoneinfo/README
+++ b/share/zoneinfo/README
@@ -34,7 +34,7 @@ substituting your desired installation directory for "$HOME/tzdir":
Historical local time information has been included here to:

* provide a compendium of data about the history of civil time
- that is useful even if the data are not 100% accurate;
+ that is useful even if not 100% accurate;

* give an idea of the variety of local time rules that have
existed in the past and thus an idea of the variety that may be
@@ -44,19 +44,16 @@ Historical local time information has been included here to:
system.

The information in the time zone data files is by no means authoritative;
-the files currently do not even attempt to cover all time stamps before
-1970, and there are undoubtedly errors even for time stamps since 1970.
-If you know that the rules are different from those in a file, by all means
-feel free to change a file (and please send the changed version to
-tz@iana.org for use in the future). Europeans take note!
+fixes and enhancements are welcome. Please see the file CONTRIBUTING
+for details.

-Thanks to these Timezone Caballeros who've made major contributions to the
-time conversion package: Keith Bostic; Bob Devine; Paul Eggert; Robert Elz;
+Thanks to these Time Zone Caballeros who've made major contributions to the
+time conversion package: Keith Bostic; Bob Devine; Paul Eggert; Robert Elz;
Guy Harris; Mark Horton; John Mackin; and Bradley White. Thanks also to
Michael Bloom, Art Neilson, Stephen Prince, John Sovereign, and Frank Wales
for testing work, and to Gwillim Law for checking local mean time data.
Thanks in particular to Arthur David Olson, the project's founder and first
-maintainer, to whom the timezone community owes the greatest debt of all.
+maintainer, to whom the time zone community owes the greatest debt of all.
None of them are responsible for remaining errors.

Look in for updated versions of these files.
diff --git a/share/zoneinfo/Theory b/share/zoneinfo/Theory
index 0b02ddc..e9be715 100644
--- a/share/zoneinfo/Theory
+++ b/share/zoneinfo/Theory
@@ -87,23 +87,23 @@ POSIX has the following properties and limitations.

* In POSIX, there's no tamper-proof way for a process to learn the
system's best idea of local wall clock. (This is important for
- applications that an administrator wants used only at certain times--
+ applications that an administrator wants used only at certain times -
without regard to whether the user has fiddled the "TZ" environment
variable. While an administrator can "do everything in UTC" to get
around the problem, doing so is inconvenient and precludes handling
- daylight saving time shifts--as might be required to limit phone
+ daylight saving time shifts - as might be required to limit phone
calls to off-peak hours.)

* POSIX requires that systems ignore leap seconds.

-* The tz code attempts attempts to support all the time_t implementations
+* The tz code attempts to support all the time_t implementations
allowed by POSIX. The time_t type represents a nonnegative count of
seconds since 1970-01-01 00:00:00 UTC, ignoring leap seconds.
In practice, time_t is usually a signed 64- or 32-bit integer; 32-bit
signed time_t values stop working after 2038-01-19 03:14:07 UTC, so
new implementations these days typically use a signed 64-bit integer.
Unsigned 32-bit integers are used on one or two platforms,
- and 36-bit integers are also used occasionally.
+ and 36-bit and 40-bit integers are also used occasionally.
Although earlier POSIX versions allowed time_t to be a
floating-point type, this was not supported by any practical
systems, and POSIX.1-2013 and the tz code both require time_t
@@ -127,7 +127,7 @@ These are the extensions that have been made to the POSIX functions:
consideration was given to using some other environment variable
(for example, "TIMEZONE") to hold the string used to generate the
time zone information file name. In the end, however, it was decided
- to continue using "TZ": it is widely used for time zone purposes;
+ to continue using "TZ": it is widely used for time zone purposes;
separately maintaining both "TZ" and "TIMEZONE" seemed a nuisance;
and systems where "new" forms of "TZ" might cause problems can simply
use TZ values such as "EST5EDT" which can be used both by
@@ -156,7 +156,7 @@ These are the extensions that have been made to the POSIX functions:
"tzsetwall();" if such code is moved to "old" systems that don't
provide tzsetwall, you won't be able to generate an executable program.
(These time zone functions also arrange for local wall clock time to be
- used if tzset is called--directly or indirectly--and there's no "TZ"
+ used if tzset is called - directly or indirectly - and there's no "TZ"
environment variable; portable applications should not, however, rely
on this behavior since it's not the way SVR2 systems behave.)

@@ -194,7 +194,7 @@ Points of interest to folks with other systems:

The functions that are conditionally compiled if STD_INSPIRED is defined
should, at this point, be looked on primarily as food for thought. They are
-not in any sense "standard compatible"--some are not, in fact, specified in
+not in any sense "standard compatible" - some are not, in fact, specified in
*any* standard. They do, however, represent responses of various authors to
standardization proposals.

@@ -223,7 +223,7 @@ before computer timekeeping became prevalent.

Clock transitions before 1970 are recorded for each such location,
because most POSIX-compatible systems support negative time stamps and
-could misbehave if data were omitted for pre-1970 transitions.
+could misbehave if data entries were omitted for pre-1970 transitions.
However, the database is not designed for and does not suffice for
applications requiring accurate handling of all past times everywhere,
as it would take far too much effort and guesswork to record all
@@ -233,9 +233,9 @@ details of pre-1970 civil timekeeping.
----- Accuracy of the tz database -----

The tz database is not authoritative, and it surely has errors.
-Corrections are welcome and encouraged. Users requiring authoritative
-data should consult national standards bodies and the references cited
-in the database's comments.
+Corrections are welcome and encouraged; see the file CONTRIBUTING.
+Users requiring authoritative data should consult national standards
+bodies and the references cited in the database's comments.

Errors in the tz database arise from many sources:

@@ -246,7 +246,7 @@ Errors in the tz database arise from many sources:
daylight saving rules, software can mess up after the rule change
if it blithely relies on conversions made before the change.

- * The pre-1970 data in this database cover only a tiny sliver of how
+ * The pre-1970 entries in this database cover only a tiny sliver of how
clocks actually behaved; the vast majority of the necessary
information was lost or never recorded. Thousands more zones would
be needed if the tz database's scope were extended to cover even
@@ -254,12 +254,12 @@ Errors in the tz database arise from many sources:
the current single entry for France would need to split into dozens
of entries, perhaps hundreds.

- * Most of the pre-1970 data comes from unreliable sources, often
+ * Most of the pre-1970 data entries come from unreliable sources, often
astrology books that lack citations and whose compilers evidently
invented entries when the true facts were unknown, without
reporting which entries were known and which were invented.
These books often contradict each other or give implausible entries,
- and on the rare occasions when their old data are checked they are
+ and on the rare occasions when they are checked they are
typically found to be incorrect.

* For the UK the tz database relies on years of first-class work done by
@@ -282,8 +282,8 @@ Errors in the tz database arise from many sources:
transition to GMT is known to be valid only for the L&NW and the
Caledonian railways.

- * The tz database does not record the earliest time for which a
- zone's data is thereafter valid for every location in the region.
+ * The tz database does not record the earliest time for which a zone's
+ data entries are thereafter valid for every location in the region.
For example, Europe/London is valid for all locations in its
region after GMT was made the standard time, but the date of
standardization (1880-08-02) is not in the tz database, other than
@@ -318,14 +318,14 @@ Errors in the tz database arise from many sources:
way to specify Easter, these exceptional years are entered as
separate tz Rule lines, even though the legal rules did not change.

- * The tz database models pre-standard time using the Gregorian
+ * The tz database models pre-standard time using the proleptic Gregorian
calendar and local mean time (LMT), but many people used other
calendars and other timescales. For example, the Roman Empire used
the Julian calendar, and had 12 varying-length daytime hours with a
non-hour-based system at night.

- * Early clocks were less reliable, and the data do not represent this
- unreliability.
+ * Early clocks were less reliable, and data entries do not represent
+ this unreliability.

* As for leap seconds, civil time was not based on atomic time before
1972, and we don't know the history of earth's rotation accurately
@@ -345,7 +345,7 @@ Errors in the tz database arise from many sources:
a leap second, or are slightly slowed while near a leap second.

* The tz database does not represent how uncertain its information is.
- Ideally it would contain information about when the data are
+ Ideally it would contain information about when data entries are
incomplete or dicey. Partial temporal knowledge is a field of
active research, though, and it's not clear how to apply it here.

@@ -405,7 +405,8 @@ in decreasing order of importance:
digits, as that might create an ambiguity with POSIX
TZ strings. A file name component must not exceed 14
characters or start with '-'. E.g., prefer 'Brunei'
- to 'Bandar_Seri_Begawan'.
+ to 'Bandar_Seri_Begawan'. Exceptions: see the discussion
+ of legacy names below.
A name must not be empty, or contain '//', or start or end with '/'.
Do not use names that differ only in case. Although the reference
implementation is case-sensitive, some other implementations
@@ -424,14 +425,14 @@ in decreasing order of importance:
even if subregions' clocks disagreed before 1970.
Otherwise these tables would become annoyingly large.
If a name is ambiguous, use a less ambiguous alternative;
- e.g. many cities are named San Jose and Georgetown, so
+ e.g. many cities are named San José and Georgetown, so
prefer 'Costa_Rica' to 'San_Jose' and 'Guyana' to 'Georgetown'.
Keep locations compact. Use cities or small islands, not countries
or regions, so that any future time zone changes do not split
locations into different time zones. E.g. prefer 'Paris'
to 'France', since France has had multiple time zones.
Use mainstream English spelling, e.g. prefer 'Rome' to 'Roma', and
- prefer 'Athens' to the true name (which uses Greek letters).
+ prefer 'Athens' to the Greek 'Αθήνα' or the Romanized 'Athína'.
The POSIX file name restrictions encourage this rule.
Use the most populous among locations in a zone,
e.g. prefer 'Shanghai' to 'Beijing'. Among locations with
@@ -454,21 +455,32 @@ in decreasing order of importance:
If a name is changed, put its old spelling in the 'backward' file.
This means old spellings will continue to work.

-The file 'zone.tab' lists geographical locations used to name time
+The file 'zone1970.tab' lists geographical locations used to name time
zone rule files. It is intended to be an exhaustive list of names
for geographic regions as described above; this is a subset of the
-names in the data. Although a 'zone.tab' location's longitude
+names in the data. Although a 'zone1970.tab' location's longitude
corresponds to its LMT offset with one hour for every 15 degrees east
longitude, this relationship is not exact.

Older versions of this package used a different naming scheme,
and these older names are still supported.
See the file 'backward' for most of these older names
-(e.g. 'US/Eastern' instead of 'America/New_York');
-excluding 'backward' should not affect the other data.
+(e.g., 'US/Eastern' instead of 'America/New_York').
The other old-fashioned names still supported are
'WET', 'CET', 'MET', and 'EET' (see the file 'europe').

+Older versions of this package defined legacy names that are
+incompatible with the first rule of location names, but which are
+still supported. These legacy names are mostly defined in the file
+'etcetera'. Also, the file 'backward' defines the legacy names
+'GMT0', 'GMT-0', 'GMT+0' and 'Canada/East-Saskatchewan', and the file
+'northamerica' defines the legacy names 'EST5EDT', 'CST6CDT',
+'MST7MDT', and 'PST8PDT'.
+
+Excluding 'backward' should not affect the other data. If
+'backward' is excluded, excluding 'etcetera' should not affect the
+remaining data.
+

----- Time zone abbreviations -----

@@ -530,10 +542,10 @@ in decreasing order of importance:
in some sense, asleep.

Application writers should note that these abbreviations are ambiguous
-in practice: e.g. 'EST' has a different meaning in Australia than
+in practice: e.g. 'CST' has a different meaning in China than
it does in the United States. In new applications, it's often better
-to use numeric UT offsets like '-0500' instead of time zone
-abbreviations like 'EST'; this avoids the ambiguity.
+to use numeric UT offsets like '-0600' instead of time zone
+abbreviations like 'CST'; this avoids the ambiguity.


----- Calendrical issues -----
@@ -542,10 +554,9 @@ Calendrical issues are a bit out of scope for a time zone database,
but they indicate the sort of problems that we would run into if we
extended the time zone database further into the past. An excellent
resource in this area is Nachum Dershowitz and Edward M. Reingold,
-
-Calendrical Calculations: Third Edition
-, Cambridge University Press (2008). Other information and
-sources are given below. They sometimes disagree.
+Calendrical Calculations: Third Edition, Cambridge University Press (2008)
+.
+Other information and sources are given below. They sometimes disagree.


France
@@ -574,7 +585,7 @@ From: Petteri Sulonen (via Usenet)
Date: 14 Jan 1999 00:00:00 GMT
...

-If your source is correct, how come documents between 1929 -- 1940 were
+If your source is correct, how come documents between 1929 and 1940 were
still dated using the conventional, Gregorian calendar?

I can post a scan of a document dated December 1, 1934, signed by
@@ -586,15 +597,14 @@ Executive Committee of the Supreme Soviet, if you like.
Sweden (and Finland)

From: Mark Brader
-
-Subject: Re: Gregorian reform -- a part of locale?
-
+Subject: Re: Gregorian reform - a part of locale?
+
Date: 1996-07-06

In 1700, Denmark made the transition from Julian to Gregorian. Sweden
decided to *start* a transition in 1700 as well, but rather than have one of
those unsightly calendar gaps :-), they simply decreed that the next leap
-year after 1696 would be in 1744 -- putting the whole country on a calendar
+year after 1696 would be in 1744 - putting the whole country on a calendar
different from both Julian and Gregorian for a period of 40 years.

However, in 1704 something went wrong and the plan was not carried through;
@@ -606,9 +616,9 @@ Then in 1753, Sweden made the transition to Gregorian in the usual manner,
getting there only 13 years behind the original schedule.

(A previous posting of this story was challenged, and Swedish readers
-produced the following references to support it: "Tiderakning och historia"
-by Natanael Beckman (1924) and "Tid, en bok om tiderakning och
-kalendervasen" by Lars-Olof Lode'n (no date was given).)
+produced the following references to support it: "Tideräkning och historia"
+by Natanael Beckman (1924) and "Tid, en bok om tideräkning och
+kalenderväsen" by Lars-Olof Lodén (1968).


Grotefend's data
@@ -629,23 +639,23 @@ Gregorian calendar:

21 Dec 1582/
01 Jan 1583 - Holland, Brabant, Flanders, Hennegau
-10/21 Feb 1583 - bishopric of Liege (L"uttich)
+10/21 Feb 1583 - bishopric of Liege (Lüttich)
13/24 Feb 1583 - bishopric of Augsburg
04/15 Oct 1583 - electorate of Trier
05/16 Oct 1583 - Bavaria, bishoprics of Freising, Eichstedt, Regensburg,
Salzburg, Brixen
-13/24 Oct 1583 - Austrian Oberelsass and Breisgau
+13/24 Oct 1583 - Austrian Oberelsaß and Breisgau
20/31 Oct 1583 - bishopric of Basel
-02/13 Nov 1583 - duchy of J"ulich-Berg
-02/13 Nov 1583 - electorate and city of K"oln
-04/15 Nov 1583 - bishopric of W"urzburg
+02/13 Nov 1583 - duchy of Jülich-Berg
+02/13 Nov 1583 - electorate and city of Köln
+04/15 Nov 1583 - bishopric of Würzburg
11/22 Nov 1583 - electorate of Mainz
16/27 Nov 1583 - bishopric of Strassburg and the margraviate of Baden
-17/28 Nov 1583 - bishopric of M"unster and duchy of Cleve
+17/28 Nov 1583 - bishopric of Münster and duchy of Cleve
14/25 Dec 1583 - Steiermark

06/17 Jan 1584 - Austria and Bohemia
-11/22 Jan 1584 - Luzern, Uri, Schwyz, Zug, Freiburg, Solothurn
+11/22 Jan 1584 - Lucerne, Uri, Schwyz, Zug, Freiburg, Solothurn
12/23 Jan 1584 - Silesia and the Lausitz
22 Jan/
02 Feb 1584 - Hungary (legally on 21 Oct 1587)
@@ -664,7 +674,7 @@ Gregorian calendar:
1617 - duchy of Kurland (reverted to the Julian calendar in
1796)

- 1624 - bishopric of Osnabr"uck
+ 1624 - bishopric of Osnabrück

1630 - bishopric of Minden

@@ -683,7 +693,7 @@ Gregorian calendar:
12 Dec 1700 - Utrecht, Overijssel

31 Dec 1700/
- 12 Jan 1701 - Friesland, Groningen, Z"urich, Bern, Basel, Geneva,
+ 12 Jan 1701 - Friesland, Groningen, Zürich, Bern, Basel, Geneva,
Turgau, and Schaffhausen

1724 - Glarus, Appenzell, and the city of St. Gallen
@@ -695,14 +705,14 @@ Gregorian calendar:
17 Feb/
01 Mar 1753 - Sweden

-1760-1812 - Graub"unden
+1760-1812 - Graubünden

The Russian empire (including Finland and the Baltic states) did not
convert to the Gregorian calendar until the Soviet revolution of 1917.

-Source: H. Grotefend, _Taschenbuch der Zeitrechnung des deutschen
+Source: H. Grotefend, _Taschenbuch der Zeitrechnung des deutschen
Mittelalters und der Neuzeit_, herausgegeben von Dr. O. Grotefend
-(Hannover: Hahnsche Buchhandlung, 1941), pp. 26-28.
+(Hannover: Hahnsche Buchhandlung, 1941), pp. 26-28.


----- Time and time zones on Mars -----
@@ -749,3 +759,9 @@ Michael Allison and Robert Schmunk,
Jia-Rui Chong, "Workdays Fit for a Martian", Los Angeles Times

(2004-01-14), pp A1, A20-A21.
+
+
+-----
+Local Variables:
+coding: utf-8
+End:
diff --git a/share/zoneinfo/africa b/share/zoneinfo/africa
index 90f7735..b17c62b 100644
--- a/share/zoneinfo/africa
+++ b/share/zoneinfo/africa
@@ -1,10 +1,10 @@
-# 


 # This file is in the public domain, so clarified as of
 # 2009-05-17 by Arthur David Olson.
 
-# This data is by no means authoritative; if you think you know better,
+# This file is by no means authoritative; if you think you know better,
 # go ahead and edit the file (and please send any changes to
-# tz@iana.org for general use in the future).
+# tz@iana.org for general use in the future).  For more, please see
+# the file CONTRIBUTING in the tz distribution.
 
 # From Paul Eggert (2013-02-21):
 #
@@ -26,8 +26,8 @@
 # I found in the UCLA library.
 #
 # For data circa 1899, a common source is:
-# Milne J. Civil time. Geogr J. 1899 Feb;13(2):173-94
-# .
+# Milne J. Civil time. Geogr J. 1899 Feb;13(2):173-94.
+# http://www.jstor.org/stable/1774359
 #
 # A reliable and entertaining source about time zones is
 # Derek Howse, Greenwich time and longitude, Philip Wilson Publishers (1997).
@@ -35,13 +35,13 @@
 # Previous editions of this database used WAT, CAT, SAT, and EAT
 # for +0:00 through +3:00, respectively,
 # but Mark R V Murray reports that
-# `SAST' is the official abbreviation for +2:00 in the country of South Africa,
-# `CAT' is commonly used for +2:00 in countries north of South Africa, and
-# `WAT' is probably the best name for +1:00, as the common phrase for
-# the area that includes Nigeria is ``West Africa''.
-# He has heard of ``Western Sahara Time'' for +0:00 but can find no reference.
+# 'SAST' is the official abbreviation for +2:00 in the country of South Africa,
+# 'CAT' is commonly used for +2:00 in countries north of South Africa, and
+# 'WAT' is probably the best name for +1:00, as the common phrase for
+# the area that includes Nigeria is "West Africa".
+# He has heard of "Western Sahara Time" for +0:00 but can find no reference.
 #
-# To make things confusing, `WAT' seems to have been used for -1:00 long ago;
+# To make things confusing, 'WAT' seems to have been used for -1:00 long ago;
 # I'd guess that this was because people needed _some_ name for -1:00,
 # and at the time, far west Africa was the only major land area in -1:00.
 # This usage is now obsolete, as the last use of -1:00 on the African
@@ -54,7 +54,7 @@
 #	 2:00	SAST	South Africa Standard Time
 # and Murray suggests the following abbreviation:
 #	 1:00	WAT	West Africa Time
-# I realize that this leads to `WAT' being used for both -1:00 and 1:00
+# I realize that this leads to 'WAT' being used for both -1:00 and 1:00
 # for times before 1976, but this is the best I can think of
 # until we get more information.
 #
@@ -94,9 +94,9 @@ Rule	Algeria	1980	only	-	Oct	31	 2:00	0	-
 # Shanks & Pottenger give 0:09:20 for Paris Mean Time; go with Howse's
 # more precise 0:09:21.
 # Zone	NAME		GMTOFF	RULES	FORMAT	[UNTIL]
-Zone	Africa/Algiers	0:12:12 -	LMT	1891 Mar 15 0:01
-			0:09:21	-	PMT	1911 Mar 11    # Paris Mean Time
-			0:00	Algeria	WE%sT	1940 Feb 25 2:00
+Zone	Africa/Algiers	0:12:12 -	LMT	1891 Mar 15  0:01
+			0:09:21	-	PMT	1911 Mar 11 # Paris Mean Time
+			0:00	Algeria	WE%sT	1940 Feb 25  2:00
 			1:00	Algeria	CE%sT	1946 Oct  7
 			0:00	-	WET	1956 Jan 29
 			1:00	-	CET	1963 Apr 14
@@ -106,87 +106,70 @@ Zone	Africa/Algiers	0:12:12 -	LMT	1891 Mar 15 0:01
 			1:00	-	CET
 
 # Angola
-# Zone	NAME		GMTOFF	RULES	FORMAT	[UNTIL]
-Zone	Africa/Luanda	0:52:56	-	LMT	1892
-			0:52:04	-	AOT	1911 May 26 # Angola Time
-			1:00	-	WAT
-
 # Benin
-# Whitman says they switched to 1:00 in 1946, not 1934;
-# go with Shanks & Pottenger.
-# Zone	NAME		GMTOFF	RULES	FORMAT	[UNTIL]
-Zone Africa/Porto-Novo	0:10:28	-	LMT	1912
-			0:00	-	GMT	1934 Feb 26
-			1:00	-	WAT
+# See Africa/Lagos.
 
 # Botswana
-# From Paul Eggert (2013-02-21):
-# Milne says they were regulated by the Cape Town Signal in 1899;
-# assume they switched to 2:00 when Cape Town did.
-# Zone	NAME		GMTOFF	RULES	FORMAT	[UNTIL]
-Zone	Africa/Gaborone	1:43:40 -	LMT	1885
-			1:30	-	SAST	1903 Mar
-			2:00	-	CAT	1943 Sep 19 2:00
-			2:00	1:00	CAST	1944 Mar 19 2:00
-			2:00	-	CAT
+# See Africa/Maputo.
 
 # Burkina Faso
-# Zone	NAME		GMTOFF	RULES	FORMAT	[UNTIL]
-Zone Africa/Ouagadougou	-0:06:04 -	LMT	1912
-			 0:00	-	GMT
+# See Africa/Abidjan.
 
 # Burundi
-# Zone	NAME		GMTOFF	RULES	FORMAT	[UNTIL]
-Zone Africa/Bujumbura	1:57:28	-	LMT	1890
-			2:00	-	CAT
+# See Africa/Maputo.
 
 # Cameroon
-# Whitman says they switched to 1:00 in 1920; go with Shanks & Pottenger.
-# Zone	NAME		GMTOFF	RULES	FORMAT	[UNTIL]
-Zone	Africa/Douala	0:38:48	-	LMT	1912
-			1:00	-	WAT
+# See Africa/Lagos.
 
 # Cape Verde
+#
+# Shanks gives 1907 for the transition to CVT.
+# Perhaps the 1911-05-26 Portuguese decree
+# http://dre.pt/pdf1sdip/1911/05/12500/23132313.pdf
+# merely made it official?
+#
 # Zone	NAME		GMTOFF	RULES	FORMAT	[UNTIL]
-Zone Atlantic/Cape_Verde -1:34:04 -	LMT	1907			# Praia
+Zone Atlantic/Cape_Verde -1:34:04 -	LMT	1907        # Praia
 			-2:00	-	CVT	1942 Sep
 			-2:00	1:00	CVST	1945 Oct 15
-			-2:00	-	CVT	1975 Nov 25 2:00
+			-2:00	-	CVT	1975 Nov 25  2:00
 			-1:00	-	CVT
 
 # Central African Republic
-# Zone	NAME		GMTOFF	RULES	FORMAT	[UNTIL]
-Zone	Africa/Bangui	1:14:20	-	LMT	1912
-			1:00	-	WAT
+# See Africa/Lagos.
 
 # Chad
 # Zone	NAME		GMTOFF	RULES	FORMAT	[UNTIL]
-Zone	Africa/Ndjamena	1:00:12 -	LMT	1912
+Zone	Africa/Ndjamena	1:00:12 -	LMT	1912        # N'Djamena
 			1:00	-	WAT	1979 Oct 14
 			1:00	1:00	WAST	1980 Mar  8
 			1:00	-	WAT
 
 # Comoros
 # Zone	NAME		GMTOFF	RULES	FORMAT	[UNTIL]
-Zone	Indian/Comoro	2:53:04 -	LMT	1911 Jul   # Moroni, Gran Comoro
+Zone	Indian/Comoro	2:53:04 -	LMT	1911 Jul # Moroni, Gran Comoro
 			3:00	-	EAT
 
-# Democratic Republic of Congo
-# Zone	NAME		GMTOFF	RULES	FORMAT	[UNTIL]
-Zone Africa/Kinshasa	1:01:12 -	LMT	1897 Nov 9
-			1:00	-	WAT
-Zone Africa/Lubumbashi	1:49:52 -	LMT	1897 Nov 9
-			2:00	-	CAT
+# Democratic Republic of the Congo
+# See Africa/Lagos for the western part and Africa/Maputo for the eastern.
 
 # Republic of the Congo
-# Zone	NAME		GMTOFF	RULES	FORMAT	[UNTIL]
-Zone Africa/Brazzaville	1:01:08 -	LMT	1912
-			1:00	-	WAT
+# See Africa/Lagos.
 
-# Cote D'Ivoire
+# Côte d'Ivoire / Ivory Coast
 # Zone	NAME		GMTOFF	RULES	FORMAT	[UNTIL]
 Zone	Africa/Abidjan	-0:16:08 -	LMT	1912
 			 0:00	-	GMT
+Link Africa/Abidjan Africa/Bamako	# Mali
+Link Africa/Abidjan Africa/Banjul	# Gambia
+Link Africa/Abidjan Africa/Conakry	# Guinea
+Link Africa/Abidjan Africa/Dakar	# Senegal
+Link Africa/Abidjan Africa/Freetown	# Sierra Leone
+Link Africa/Abidjan Africa/Lome		# Togo
+Link Africa/Abidjan Africa/Nouakchott	# Mauritania
+Link Africa/Abidjan Africa/Ouagadougou	# Burkina Faso
+Link Africa/Abidjan Africa/Sao_Tome	# São Tomé and Príncipe
+Link Africa/Abidjan Atlantic/St_Helena	# St Helena
 
 # Djibouti
 # Zone	NAME		GMTOFF	RULES	FORMAT	[UNTIL]
@@ -231,13 +214,9 @@ Rule	Egypt	1990	1994	-	May	 1	1:00	1:00	S
 # Egyptians would approve the cancellation."
 #
 # Egypt to cancel daylight saving time
-# 
 # http://www.almasryalyoum.com/en/node/407168
-# 
 # or
-# 
 # http://www.worldtimezone.com/dst_news/dst_news_egypt04.html
-# 
 Rule	Egypt	1995	2010	-	Apr	lastFri	 0:00s	1:00	S
 Rule	Egypt	1995	2005	-	Sep	lastThu	24:00	0	-
 # From Steffen Thorsen (2006-09-19):
@@ -249,7 +228,7 @@ Rule	Egypt	2006	only	-	Sep	21	24:00	0	-
 # From Dirk Losch (2007-08-14):
 # I received a mail from an airline which says that the daylight
 # saving time in Egypt will end in the night of 2007-09-06 to 2007-09-07.
-# From Jesper Norgaard Welen (2007-08-15): [The following agree:]
+# From Jesper Nørgaard Welen (2007-08-15): [The following agree:]
 # http://www.nentjes.info/Bill/bill5.htm
 # http://www.timeanddate.com/worldclock/city.html?n=53
 # From Steffen Thorsen (2007-09-04): The official information...:
@@ -288,15 +267,9 @@ Rule	Egypt	2007	only	-	Sep	Thu>=1	24:00	0	-
 #
 # timeanddate[2] and another site I've found[3] also support that.
 #
-# [1] 
-# https://bugzilla.redhat.com/show_bug.cgi?id=492263
-# 
-# [2] 
-# http://www.timeanddate.com/worldclock/clockchange.html?n=53
-# 
-# [3] 
-# http://wwp.greenwichmeantime.com/time-zone/africa/egypt/
-# 
+# [1] https://bugzilla.redhat.com/show_bug.cgi?id=492263
+# [2] http://www.timeanddate.com/worldclock/clockchange.html?n=53
+# [3] http://wwp.greenwichmeantime.com/time-zone/africa/egypt/
 
 # From Arthur David Olson (2009-04-20):
 # In 2009 (and for the next several years), Ramadan ends before the fourth
@@ -306,14 +279,10 @@ Rule	Egypt	2007	only	-	Sep	Thu>=1	24:00	0	-
 # From Steffen Thorsen (2009-08-11):
 # We have been able to confirm the August change with the Egyptian Cabinet
 # Information and Decision Support Center:
-# 
 # http://www.timeanddate.com/news/time/egypt-dst-ends-2009.html
-# 
 #
 # The Middle East News Agency
-# 
 # http://www.mena.org.eg/index.aspx
-# 
 # also reports "Egypt starts winter time on August 21"
 # today in article numbered "71, 11/08/2009 12:25 GMT."
 # Only the title above is available without a subscription to their service,
@@ -321,25 +290,20 @@ Rule	Egypt	2007	only	-	Sep	Thu>=1	24:00	0	-
 # (at least today).
 
 # From Alexander Krivenyshev (2010-07-20):
-# According to News from Egypt -  Al-Masry Al-Youm Egypt's cabinet has
+# According to News from Egypt - Al-Masry Al-Youm Egypt's cabinet has
 # decided that Daylight Saving Time will not be used in Egypt during
 # Ramadan.
 #
 # Arabic translation:
-# "Clocks to go back during Ramadan--and then forward again"
-# 
+# "Clocks to go back during Ramadan - and then forward again"
 # http://www.almasryalyoum.com/en/news/clocks-go-back-during-ramadan-and-then-forward-again
-# 
-# or
-# 
 # http://www.worldtimezone.com/dst_news/dst_news_egypt02.html
-# 
 
 # From Ahmad El-Dardiry (2014-05-07):
 # Egypt is to change back to Daylight sy
48afb8a Sync zoneinfo database with tzdata2014h from ftp://ftp.iana.org/tz/releases
 share/zoneinfo/NEWS          |  518 ++++++++++++++--
 share/zoneinfo/README        |   15 +-
 share/zoneinfo/Theory        |  124 ++--
 share/zoneinfo/africa        |  522 ++++++----------
 share/zoneinfo/antarctica    |  134 +++--
 share/zoneinfo/asia          |  924 ++++++++++++++--------------
 share/zoneinfo/australasia   |  938 ++++++++++++++---------------
 share/zoneinfo/backward      |    9 +-
 share/zoneinfo/etcetera      |    3 +-
 share/zoneinfo/europe        | 1358 ++++++++++++++++++++++++++----------------
 share/zoneinfo/iso3166.tab   |   12 +-
 share/zoneinfo/leapseconds   |    4 +-
 share/zoneinfo/northamerica  |  708 ++++++++++------------
 share/zoneinfo/southamerica  |  484 +++++++--------
 share/zoneinfo/systemv       |    1 -
 share/zoneinfo/yearistype.sh |    4 +-
 share/zoneinfo/zone.tab      |   69 +--
 17 files changed, 3130 insertions(+), 2697 deletions(-)
Upstream: gitweb.dragonflybsd.org
  • Share
  •