weird characters replaced by UTF-8

handbook/finance.html

@@ -92,7 +92,7 @@ After the expedition, the Expo treasurer processes this data to work out who owe
 <li>Pay a deposit.<br/>
 <li>Keep receipts, give them to the expedition treasurer.</li>
 <li>If you are in any doubt whether the expedition will reimburse an expense do not incur</li>
-it before obtaining the expedition treasurer’s agreement.</li>
+it before obtaining the expedition treasurer's agreement.</li>
 <li>Fill in the relevant pages of the Bier Book fastidiously.</li>
 <li>Where possible, enter details of your expenses on the Expo computer.</li>
 <li>Leave money when you leave Austria in order to cover your share of the campsite bill.</li>

handbook/flooding.html

@@ -9,7 +9,7 @@
 <h2 id="tophead">CUCC Expedition Handbook</h2>
 <h1>Flood Risk</h1>
 
-<p>The aim of this summary document is to pass on current knowledge, including between one year and the next year’s expedition, about pitches that have 
+<p>The aim of this summary document is to pass on current knowledge, including between one year and the next year's expedition, about pitches that have 
 significant flood hazards. The same info should also appear in each cave description, but sometimes they are out of date.</p>
 
 <p><b>Last updated July 2016</b></p>
@@ -20,7 +20,12 @@ significant flood hazards. The same info should also appear in each cave descrip
 
 <dl>
   <dt>Entrance Pitch</dt>
-  <dd>The lower two pitches of the entrance series become very wet or fully impassable. This includes the longest (~30m) hang – especially its lower part and ledge, and the final 10m pitch. A short period of rain can cause these pitches to become very drippy and unpleasant, but passable. However, heavy and/or sustained rainfall produces water spouts both on the main hang, and on the bottom pitch; thereby making the entrance series impassable. The response of these pitches to surface rain is quick. It can also take several (or more) hours for the water levels on the pitches to drop. Suitable kit for sitting out a flood (bothy bag, stove, food etc) should therefore be installed from start of expedition at the base of the entrance pitch.</dd>
+  <dd>The lower two pitches of the entrance series become very wet or fully impassable. This includes the longest (~30m) hang - especially its lower 
+part and ledge, and the final 10m pitch. A short period of rain can cause these pitches to become very drippy and unpleasant, but passable. However, 
+heavy and/or sustained rainfall produces water spouts both on the main hang, and on the bottom pitch; thereby making the entrance series impassable. 
+The response of these pitches to surface rain is quick. It can also take several (or more) hours for the water levels on the pitches to drop. 
+Suitable kit for sitting out a flood (bothy bag, stove, food etc) should therefore be installed from start of expedition at the base of the entrance 
+pitch.</dd>
   
   <dt>Darks Arts: final Lleft-hand pitch</dt>
   <dd>The left-hand and deeper (wet) pitch develops a water spout after only moderate rainfall, and responds quickly to surface rainfall.</dd>

handbook/survey/newrig.html

@@ -118,8 +118,9 @@ where they will be linked in to the HTML files for the cave descriptions, e.g.
 
 <p>[ We could dream up some fancy scheme for indexing the rigging for every pitch in the system and add that  
 into troggle but frankly we don't think it's worth the effort.]
+
 <h3>Final editing of cave descriptions</h3>
-<p>If you look in detail at the description of <a href="/1623/204/204.html">Steinbrückenhöhle</a> you will see rigging topos
+<p>If you look in detail at the description of <a href="/1623/204/204.html">Steinbr&uuml;ckenh&ouml;hle</a> you will see rigging topos
 inline as pixel images (not vector files) in the passage descriptions. These are stored with the passage HTML files, e.g. 
 in <a href="/1623/204/rigging/kiwi.png"><var>:expoweb:</var>/1623/204/rigging/kiwi.png</a>, 
 whereas the master copy of this rigging diagram is the vector file at 

handbook/survey/qmentry.html

@@ -30,20 +30,20 @@ compared to including QMs only in survey drawings in Tunnel or writing a cave
 description then putting it on the expo website. 
 
 <p>Svx files are a very stable place to store the data long-
-term: there is no need to rely on a ‘master file’ of any kind, which can be problematic if not everyone
+term: there is no need to rely on a ‘master file' of any kind, which can be problematic if not everyone
 on expo has the same level of computer literacy, and requires just basic text entry to create and update
 the data after a trip.
 
-<h3>How it’s done:</h3>
+<h3>How it's done:</h3>
 <p>
-So, you’ve got your .svx file started (if entering new data), or located and opened (if updating a
+So, you've got your .svx file started (if entering new data), or located and opened (if updating a
 previously surveyed bit of cave after checking out some QMs again), and it looks a bit like this (visual
 format will change depending on your preferred text editor):
 <p>
 <img src="wob-svx-edit-pic.jpg" width=900>
 
 <p>
-If you don’t understand what is in front of you here, then you need to read the <a href="newcave.html#survexformat">survey handbook guide on svx files</a> which will lead you to the survex documentation, or ask
+If you don't understand what is in front of you here, then you need to read the <a href="newcave.html#survexformat">survey handbook guide on svx files</a> which will lead you to the survex documentation, or ask
 someone about basic entry of survey leg and station data into the .svx file format.
 <p>
 Near to the end of the text in the file, you will see a section that looks like this:
@@ -107,7 +107,7 @@ If these data are not entered along with the rest of the survey data, it is as i
 some of the actual passage data you surveyed: information is being lost and someone will have to
 trawl back through all the survey data at a later time to keep it up-to-date, a very tedious task which
 is a very inefficient use of time. 
-<p>Also if the person reading it hasn’t been to the bit of cave (which is, like, <em>the whole point</em>, then the data has a higher chance of being incorrect. It is not always easy to interpret Tunnel or Therion 
+<p>Also if the person reading it hasn't been to the bit of cave (which is, like, <em>the whole point</em>, then the data has a higher chance of being incorrect. It is not always easy to interpret Tunnel or Therion 
 drawings correctly with this sort of thing. 
 
 <h3>Programming note</h3>

handbook/travel.html

@@ -1,6 +1,6 @@
 <html>
 <head>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
 <title>CUCC's Austria expeditions: Travel</title>
 <link rel="stylesheet" type="text/css" href="../css/main2.css" />
 </head>
@@ -80,7 +80,8 @@ even if you don't actually get off the train there, just change ticket! Book ear
 Salzburg has been annexed by DB and counts as Germany for train purposes. 
 These are only available via Brussels so you need to add a stop of around an hour when searching for tickets.</p>
 
-<p>Paul Fox just paid (2018) &euro;70 all the way from Salzburg to London, including the Eurostar, booked only 3 days in advance. In comparison Eurostar want Â&pound;88 for a seat on the same train from Brussels to London, so the journey across all of Germany was cheaper than free.</p>
+<p>Paul Fox just paid (2018) &euro;70 all the way from Salzburg to London, including the Eurostar, booked only 3 days in advance. 
+In comparison Eurostar want &pound; for a seat on the same train from Brussels to London, so the journey across all of Germany was cheaper than free.</p>
 
 <p>The only catch is that you need to check in with a human at Brussels / London as the Eurostar gates can't read DB ticket barcodes.</p>
 </em>

handbook/troggle/scriptsqms.html

@@ -72,7 +72,7 @@ C1999-204-09    C    Wolp    Hole in floor through dangerous boulders        vei
 Fields in 258/qm.csv are:
 <code><pre><span style="font-size:small">Cave, year, number, Grade, nearest station, description, completion description, found by, completed by
 e.g.
-258  2006  27        C      258.gknodel.4    Small passage to E in Germkn”del          Sandeep Mavadia and Dave Loeffler
+258  2006  27        C      258.gknodel.4    Small passage to E in Germkn&ouml;del          Sandeep Mavadia and Dave Loeffler
 </span></pre></code>
 Fields in 264/qm.csv are:
 <code><pre><span style="font-size:small">Year, number, Grade, Survey folder ref#, Surveyname, Nearest Station number, Area of the cave, Description, Y if marked on drawn-up survey,
@@ -132,7 +132,7 @@ The 2019 copies are online in /expofiles/:
 
 <p>
 This will work on all survex *.svx files even those which have not yet been run through the troggle import process. 
-<p>Phil says (13 April 2020): <em>"The generated files are not meant to be served by the webserver, it’s a tool for people to run locally. Someone could modify it to create HTML output (or post-process the CSV output to do the same), but that is work still to be done."</em>
+<p>Phil says (13 April 2020): <em>"The generated files are not meant to be served by the webserver, it's a tool for people to run locally. Someone could modify it to create HTML output (or post-process the CSV output to do the same), but that is work still to be done."</em>
 
 <h4>troggle/parsers/survex.py</a></h4>
 <p>The QMs inside the survex files are parsed by troggle along with all the other information
@@ -183,9 +183,9 @@ Subject: Re: svx2qm
 
 Hi Philip,
 
-Hope you’re well, thanks for getting in touch about this.
+Hope you're well, thanks for getting in touch about this.
 
-The generated files are not meant to be served by the webserver, it’s a tool for people to run locally. 
+The generated files are not meant to be served by the webserver, it's a tool for people to run locally. 
 Someone could modify it to create HTML output (or post-process the CSV output to do the same), 
 but that is work still to be done.
 
@@ -196,21 +196,21 @@ and it should go into the Makefile too at some point.
 
 Feel free to move it wherever; I am not planning on doing any further work on it. 
 The script itself just expects to be passed some (relative or absolute) paths to SVX files, 
-so can be placed wherever, as long as it’s passed appropriate relative paths.
+so can be placed wherever, as long as it's passed appropriate relative paths.
 
-I haven’t written any other scripts which post-process the data or otherwise format it.
+I haven't written any other scripts which post-process the data or otherwise format it.
 
 I guess it all depends on what questions people are trying to answer using the QM data, 
-as to how (and where) best to present it. I’m afraid I don’t have any suggestions there.
+as to how (and where) best to present it. I'm afraid I don't have any suggestions there.
 
 :Rob Watson wrote some documentation about QMs
 :<a href="../survey/qmentry.html">http://expo.survex.com/handbook/survey/qmentry.html</a> 
 :is there anything subtle missing  as to how they are used ?
 
-Nope, I think Rob’s page covers it all. That page also documents the correct QM format 
+Nope, I think Rob's page covers it all. That page also documents the correct QM format 
 which is what svx2qm.py understands. (There were some older or artisanal QM formats 
 floating around at one point, although I think I reformatted them all so the tool 
-would understand them, and so people would hopefully standardise on what Rob’s 
+would understand them, and so people would hopefully standardise on what Rob's 
 documented from then on.)
 
 Philip</pre>