From a7508cd486c295109b3f2c0532be639ce5807f59 Mon Sep 17 00:00:00 2001
From: Philip Sargent <philip.sargent@gmail.com>
Date: Wed, 3 Jul 2024 11:47:39 +0300
Subject: [PATCH] initial text editor stuff

---
 cave_data/cavealiases.txt  | 31 +++++++++++++++++++++++++++++++
 cave_data/pendingcaves.txt |  3 +++
 2 files changed, 34 insertions(+)
 create mode 100644 cave_data/cavealiases.txt

diff --git a/cave_data/cavealiases.txt b/cave_data/cavealiases.txt
new file mode 100644
index 000000000..87fc23ee7
--- /dev/null
+++ b/cave_data/cavealiases.txt
@@ -0,0 +1,31 @@
+; This is the list of cave aliases which is parsed when a database reset is done.
+
+; This is IMPORTANT as it enables old logbook cave ids to be redirected to current cave ids.
+; such as "2017_cucc_28" => "1623-290" is Fishface.
+
+; The format is ("<identifier>","<identifier>")
+; e.g.
+("2017_cucc_28", "1623-290")
+ 
+
+; lines with initial semi-colon ; or hash # are comments
+; extra commas are ignored
+; extra blanks are ignored
+; This capability created in July 2024.
+
+# various funnies to cope with cave names used in logbooks
+        ("kh", "1623-161"),
+        ("161-kh", "1623-161"),
+        ("204-steinBH", "1623-204"),
+        ("stonebridge", "1623-204"),
+        ("hauchhole", "1623-234"),
+        ("hauch", "1623-234"),
+        ("234-hauch", "1623-234"),
+        ("tunnocks", "1623-258"),
+        ("balcony", "1623-264"),
+        ("balkon", "1623-264"),
+        ("fgh", "1623-290"),
+        ("fishface", "1623-290"),
+        ("gsh", "1623-291"),
+        ("1623-2023-lc-01", "1623-318"),
+        ("tempest", "1623-2023-lc-01"),
diff --git a/cave_data/pendingcaves.txt b/cave_data/pendingcaves.txt
index 44c32b048..6154447d1 100644
--- a/cave_data/pendingcaves.txt
+++ b/cave_data/pendingcaves.txt
@@ -1,10 +1,13 @@
 ; IDs listed here will have a Cave object created in troggle
 ; on the next database reset. 
+
 ; The Cave Description will be pre-filled with instructions of how
 ; to find and update the information needed to do it properly.
 
 ; Anything after a semi-colon is ignored as a comment
 
+; This file is only parsed when a full database reset is done on the server.
+
 ; example entry (without the initial semicolon of course):
 ;1626-2019-HT-01 ; Banana Hole, see logbook