weird characters replaced by UTF-8

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>