[tz] Reason for removal of several TZ

[Paul Eggert]

Michael H Deckers via tz wrote:

>    This seems to miss
>                     NST/NDT/NWT/NPT Nome

Thanks, fixed in the attached proposed patch.

> 
>    There is also the question of whether Theory covers
>    backzone or not.

backzone is for stuff that's outside the scope of tzdb, so I would say "not". I 
attempted to clarify this point in the attached patch.
-------------- next part --------------
From 361e42e00756afe10e0ac0276c01363ace48d11c Mon Sep 17 00:00:00 2001
From: Paul Eggert <eggert at cs.ucla.edu>
Date: Thu, 7 Dec 2017 23:13:20 -0800
Subject: [PROPOSED] theory.html fixes for Nome and backzone
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

* theory.html: Mention Nome, and document ‘backzone’ as being
outside tzdb scope.  (Reported by Michael H Deckers.)
---
 theory.html | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/theory.html b/theory.html
index dbc7660..5a3cfc7 100644
--- a/theory.html
+++ b/theory.html
@@ -52,6 +52,10 @@ 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
 details of pre-1970 civil timekeeping.
+Athough some information outside the scope of the database is
+collected in a file <code>backzone</code> that is distributed along
+with the database proper, this file is less reliable and does not
+necessarily follow database guidelines.
 </p>
 
 <p>
@@ -338,6 +342,7 @@ MET/MEST Middle European (a backward-compatibility alias for Central European),
 MSK/MSD Moscow,
 MST/MDT/MWT/MPT/MDDT Mountain,
 NST/NDT/NWT/NPT/NDDT Newfoundland,
+NST/NDT/NWT/NPT Nome,
 NZMT/NZST New Zealand through 1945,
 NZST/NZDT New Zealand 1946–present,
 PKT/PKST Pakistan,
@@ -445,7 +450,7 @@ Israel. To avoid ambiguity, use numeric UT offsets like
     <h2 id="accuracy">Accuracy of the tz database</h2>
 <p>
 The tz database is not authoritative, and it surely has errors.
-Corrections are welcome and encouraged; see the file CONTRIBUTING.
+Corrections are welcome and encouraged; see the file <code>CONTRIBUTING</code>.
 Users requiring authoritative data should consult national standards
 bodies and the references cited in the database's comments.
 </p>
-- 
2.7.4