<div dir="ltr">Not a major issue, but using more precise coordinates for Asia/Jerusalem would also mean using a correspondingly more precise LMT value pre-1880.<br><div><br>diff --git a/asia b/asia<br>index e544fcc..437e15f 100644<br>
--- a/asia<br>+++ b/asia<br>@@ -1244,7 +1244,7 @@ Rule Zion 2028 max - Oct Sun>=2 2:00 0 S<br> #Rule Zion 2082 max - Oct Sun>=2 2:00 0 S<br> <br> # Zone NAME GMTOFF RULES FORMAT [UNTIL]<br>
-Zone Asia/Jerusalem 2:20:56 - LMT 1880<br>+Zone Asia/Jerusalem 2:20:54 - LMT 1880<br> 2:20:40 - JMT 1918 # Jerusalem Mean Time?<br> 2:00 Zion I%sT<br> <br>
<br></div></div><div class="gmail_extra"><br clear="all"><div>--<br>Tim Parenti<br></div>
<br><br><div class="gmail_quote">On 27 May 2013 21:18, Paul Eggert <span dir="ltr"><<a href="mailto:eggert@cs.ucla.edu" target="_blank">eggert@cs.ucla.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
This change stemmed from a long discussion on the tz mailing list<br>
about what country the Jerusalem zone entry is in. The idea of<br>
this change is to deemphasize the role of countries in the tz<br>
database, to lessen the amount of controversy in the future.<br>
Due to backward compatibility concerns this change does not eliminate<br>
the role of countries entirely. With one minor exception this<br>
change does not alter any code or data, just comments.<br>
* Theory, zone.tab: Deemphasize the role of countries in choosing<br>
location names, as they tend to introduce political conflict<br>
during maintenance, and country information isn't needed for<br>
typical uses of the database.<br>
* Theory: Say that names should differ in more than just case, and why;<br>
and explain why 'backward' means old names will continue to work.<br>
(thanks to Norbert Lindenberg for spotting these issues).<br>
Update citation date and URL.<br>
* iso3166.tab: Mention latest maintenance update.<br>
Update citation URL. Add missing comma for BQ.<br>
Be more consistent about abbreviating Sint like Saint.<br>
Mention SX "Dutch part" for consistency with MF "French part".<br>
* iso3166.tab, zone.tab: Add legal/territorial disclaimer.<br>
* zone.tab: Say that country/zone overlaps can occur in both<br>
directions, and that column 2 need not lie within column 1.<br>
(Asia/Jerusalem): Change the coordinates from a sloppy value,<br>
taken from an old astrology book, to a more-precise value, the<br>
site of city hall. The sloppy value sparked some controversy and<br>
the hope is that the more-precise value will be a bit less<br>
controversial.<br>
---<br>
Theory | 27 ++++++++++++++-------------<br>
iso3166.tab | 21 ++++++++++-----------<br>
zone.tab | 17 ++++++++++++-----<br>
3 files changed, 36 insertions(+), 29 deletions(-)<br>
<br>
diff --git a/Theory b/Theory<br>
index b00a492..751b12d 100644<br>
--- a/Theory<br>
+++ b/Theory<br>
@@ -264,12 +264,12 @@ in decreasing order of importance:<br>
TZ strings. A file name component must not exceed 14<br>
characters or start with `-'. E.g., prefer `Brunei'<br>
to `Bandar_Seri_Begawan'.<br>
- Include at least one location per time zone rule set per country.<br>
- One such location is enough. Use ISO 3166 (see the file<br>
- iso3166.tab) to help decide whether something is a country.<br>
- However, uninhabited ISO 3166 regions like Bouvet Island<br>
+ Do not use names that differ only in case. Although the reference<br>
+ implementation is case-sensitive, some other implementations<br>
+ are not, and they would mishandle names differing only in case.<br>
+ Uninhabited regions like the North Pole and Bouvet Island<br>
do not need locations, since local time is not defined there.<br>
- If all the clocks in a country's region have agreed since 1970,<br>
+ If all the clocks in a region have agreed since 1970,<br>
don't bother to include more than one location<br>
even if subregions' clocks disagreed before 1970.<br>
Otherwise these tables would become annoyingly large.<br>
@@ -283,7 +283,7 @@ in decreasing order of importance:<br>
Use mainstream English spelling, e.g. prefer `Rome' to `Roma', and<br>
prefer `Athens' to the true name (which uses Greek letters).<br>
The POSIX file name restrictions encourage this rule.<br>
- Use the most populous among locations in a country's time zone,<br>
+ Use the most populous among locations in a zone,<br>
e.g. prefer `Shanghai' to `Beijing'. Among locations with<br>
similar populations, pick the best-known location,<br>
e.g. prefer `Rome' to `Milan'.<br>
@@ -302,10 +302,11 @@ in decreasing order of importance:<br>
Milan's population has grown to be somewhat greater<br>
than Rome's.<br>
If a name is changed, put its old spelling in the `backward' file.<br>
+ This means old spellings will continue to work.<br>
<br>
The file `zone.tab' lists the geographical locations used to name<br>
time zone rule files. It is intended to be an exhaustive list<br>
-of canonical names for geographic regions.<br>
+of names for geographic regions as described above.<br>
<br>
Older versions of this package used a different naming scheme,<br>
and these older names are still supported.<br>
@@ -359,14 +360,13 @@ in decreasing order of importance:<br>
If this is not available or is a phrase mentioning the country<br>
(e.g. ``Cape Verde Time''), then:<br>
<br>
- When a country has a single or principal time zone region,<br>
+ When a country is identified with a single or principal zone,<br>
append `T' to the country's ISO code, e.g. `CVT' for<br>
Cape Verde Time. For summer time append `ST';<br>
for double summer time append `DST'; etc.<br>
- When a country has multiple time zones, take the first three<br>
- letters of an English place name identifying each zone<br>
- and then append `T', `ST', etc. as before;<br>
- e.g. `VLAST' for VLAdivostok Summer Time.<br>
+ Otherwise, take the first three letters of an English place<br>
+ name identifying each zone and append 'T', 'ST', etc.<br>
+ as before; e.g. 'VLAST' for VLAdivostok Summer Time.<br>
<br>
Use UTC (with time zone abbreviation "zzz") for locations while<br>
uninhabited. The "zzz" mnemonic is that these locations are,<br>
@@ -587,7 +587,8 @@ Sources:<br>
<br>
Michael Allison and Robert Schmunk,<br>
"Technical Notes on Mars Solar Time as Adopted by the Mars24 Sunclock"<br>
-<<a href="http://www.giss.nasa.gov/tools/mars24/help/notes.html" target="_blank">http://www.giss.nasa.gov/tools/mars24/help/notes.html</a>> (2004-07-30).<br>
+<<a href="http://www.giss.nasa.gov/tools/mars24/help/notes.html" target="_blank">http://www.giss.nasa.gov/tools/mars24/help/notes.html</a>> (2012-08-08).<br>
<br>
Jia-Rui Chong, "Workdays Fit for a Martian", Los Angeles Times<br>
+<<a href="http://articles.latimes.com/2004/jan/14/science/sci-marstime14" target="_blank">http://articles.latimes.com/2004/jan/14/science/sci-marstime14</a>><br>
(2004-01-14), pp A1, A20-A21.<br>
diff --git a/iso3166.tab b/iso3166.tab<br>
index b952ca1..c184a81 100644<br>
--- a/iso3166.tab<br>
+++ b/iso3166.tab<br>
@@ -1,16 +1,14 @@<br>
-# <pre><br>
+# ISO 3166 alpha-2 country codes<br>
+#<br>
# This file is in the public domain, so clarified as of<br>
# 2009-05-17 by Arthur David Olson.<br>
-# ISO 3166 alpha-2 country codes<br>
#<br>
-# From Paul Eggert (2006-09-27):<br>
+# From Paul Eggert (2013-05-27):<br>
#<br>
# This file contains a table with the following columns:<br>
# 1. ISO 3166-1 alpha-2 country code, current as of<br>
-# ISO 3166-1 Newsletter VI-1 (2007-09-21). See:<br>
-# <a href="<a href="http://www.iso.org/iso/en/prods-services/iso3166ma/index.html" target="_blank">http://www.iso.org/iso/en/prods-services/iso3166ma/index.html</a>"><br>
-# ISO 3166 Maintenance agency (ISO 3166/MA)<br>
-# </a>.<br>
+# ISO 3166-1 Newsletter VI-15 (2013-05-10). See: Updates on ISO 3166<br>
+# <a href="http://www.iso.org/iso/home/standards/country_codes/updates_on_iso_3166.htm" target="_blank">http://www.iso.org/iso/home/standards/country_codes/updates_on_iso_3166.htm</a><br>
# 2. The usual English name for the country,<br>
# chosen so that alphabetic sorting of subsets produces helpful lists.<br>
# This is not the same as the English name in the ISO 3166 tables.<br>
@@ -20,8 +18,9 @@<br>
#<br>
# Lines beginning with `#' are comments.<br>
#<br>
-# From Arthur David Olson (2011-08-17):<br>
-# Resynchronized today with the ISO 3166 site (adding SS for South Sudan).<br>
+# This table is intended as an aid for users, to help them select time<br>
+# zone data appropriate for their practical needs. It is not intended<br>
+# to take or endorse any position on legal or territorial claims.<br>
#<br>
#country-<br>
#code country name<br>
@@ -54,7 +53,7 @@ BL St Barthelemy<br>
BM Bermuda<br>
BN Brunei<br>
BO Bolivia<br>
-BQ Bonaire Sint Eustatius & Saba<br>
+BQ Bonaire, St Eustatius & Saba<br>
BR Brazil<br>
BS Bahamas<br>
BT Bhutan<br>
@@ -235,7 +234,7 @@ SR Suriname<br>
SS South Sudan<br>
ST Sao Tome & Principe<br>
SV El Salvador<br>
-SX Sint Maarten<br>
+SX St Maarten (Dutch part)<br>
SY Syria<br>
SZ Swaziland<br>
TC Turks & Caicos Is<br>
diff --git a/zone.tab b/zone.tab<br>
index 6b98520..3ec24a7 100644<br>
--- a/zone.tab<br>
+++ b/zone.tab<br>
@@ -1,18 +1,21 @@<br>
-# <pre><br>
+# TZ zone descriptions<br>
+#<br>
# This file is in the public domain, so clarified as of<br>
# 2009-05-17 by Arthur David Olson.<br>
#<br>
-# TZ zone descriptions<br>
-#<br>
-# From Paul Eggert (1996-08-05):<br>
+# From Paul Eggert (2013-05-27):<br>
#<br>
# This file contains a table with the following columns:<br>
# 1. ISO 3166 2-character country code. See the file `iso3166.tab'.<br>
+# This identifies a country that overlaps the zone. The country may<br>
+# overlap other zones and the zone may overlap other countries.<br>
# 2. Latitude and longitude of the zone's principal location<br>
# in ISO 6709 sign-degrees-minutes-seconds format,<br>
# either +-DDMM+-DDDMM or +-DDMMSS+-DDDMMSS,<br>
# first latitude (+ is north), then longitude (+ is east).<br>
+# This location need not lie within the column-1 country.<br>
# 3. Zone name used in value of TZ environment variable.<br>
+# Please see the 'Theory' file for how zone names are chosen.<br>
# 4. Comments; present if and only if the country has multiple rows.<br>
#<br>
# Columns are separated by a single tab.<br>
@@ -22,6 +25,10 @@<br>
#<br>
# Lines beginning with `#' are comments.<br>
#<br>
+# This table is intended as an aid for users, to help them select time<br>
+# zone data appropriate for their practical needs. It is not intended<br>
+# to take or endorse any position on legal or territorial claims.<br>
+#<br>
#country-<br>
#code coordinates TZ comments<br>
AD +4230+00131 Europe/Andorra<br>
@@ -216,7 +223,7 @@ ID -0002+10920 Asia/Pontianak west & central Borneo<br>
ID -0507+11924 Asia/Makassar east & south Borneo, Sulawesi (Celebes), Bali, Nusa Tengarra, west Timor<br>
ID -0232+14042 Asia/Jayapura west New Guinea (Irian Jaya) & Malukus (Moluccas)<br>
IE +5320-00615 Europe/Dublin<br>
-IL +3146+03514 Asia/Jerusalem<br>
+IL +314650+0351326 Asia/Jerusalem<br>
IM +5409-00428 Europe/Isle_of_Man<br>
IN +2232+08822 Asia/Kolkata<br>
IO -0720+07225 Indian/Chagos<br>
<span class="HOEnZb"><font color="#888888">--<br>
1.8.1.2<br>
<br>
</font></span></blockquote></div><br></div>