expo/expoweb
1
0
Fork 0
mirror of https://expo.survex.com/repositories/expoweb/.git/ synced 2024-11-21 23:01:55 +00:00
Code Issues Packages Projects Releases Wiki Activity

moe QM bits

Browse Source
This commit is contained in:
Philip Sargent 2021-12-30 16:20:45 +00:00
parent ef5e5e9509
commit 3cae883304
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
handbook/survey/qm.html
View File

@ -27,8 +27,8 @@ its "<cavenumber>." prefix) is included in an html comment for almost all
leads.]</p>
<p>In general, an unpushed QM will have a link from its QM number in the
cave description file to the list (generated by a perl script), and a link from the list to the relevant point in the
description. If there is no link, it means that I can't yet work out where the
cave description file to the HTML QM list file (generated by a perl script for caves 204, 234 and 258), and a link from the list to the relevant point in the
description. If there is no link, it means that we can't yet work out where the
QM is in the description, or the description doesn't yet exist :-).</p>
<h2>Discoverer identifiers</h2>

2
handbook/survey/qmentry.html
View File

@ -78,7 +78,7 @@ The format for question mark lists is <br>
<li><a href="qm.html">Discoverer identifier</a>, <li>Year of discovery, <li>Cave identifier, <li>serial number.
</ul>
but today, with the QMs inside the survex files, the identifiers are just QM1, QM2 etc.
<p>This format is <a href="../../qm.html">documented in the original QM conventions</a> page (which now needs revising).
<p>This format is <a href="qm.html">documented in the original QM conventions</a> page.
<p>
The example below demonstrates correct and effective use of the QM list referring back to earlier elements in the svx file: