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

[svn r5851] Corrected some spelling errors

Browse Source
This commit is contained in:
dl267 2004-04-27 09:59:03 +02:00
parent 92cf7c4009
commit 428ff9d1f8
4 changed files with 18 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
handbook/known.htm
View File

@ -17,7 +17,7 @@ not since 1999, certainly not since 2001). Do not rely on it!</em></p>
<table class="trad">
<tr><th>CUCC #</th><th>1623/</th><th>info</th></tr>
<tr><td></td><td><a href="../noinfo/smkridge/28.htm">28</a>
</td><td>red painted omega Marking in Stogerweg near laserpoint
</td><td>red painted omega Marking in Stogerweg near laser point
denotes nearby entrance</td></tr>
<tr><td></td><td><a href="../noinfo/smkridge/31.htm">31</a>

6
handbook/rescue.htm
View File

@ -229,7 +229,7 @@ rescue kit (<a href="#s351">see section 3.5.1</a>), with the aims of:</p>
<p>The others should follow behind carrying the equipment listed in
<a href="#s352">section 3.5.2</a> and a bag of hauling gear
(<a href="#s354">section 3.5.4</a>). They should cave carefully and preserve
their energy as far as possible, as it may be a long resue. Their main aim is
their energy as far as possible, as it may be a long rescue. Their main aim is
to prevent the deterioration of the victim. Their secondary aim is to start
getting the victim(s) out of the cave, if they have sufficient personnel.</p>
@ -287,7 +287,7 @@ href="#s354">3.5.4</a>) if there is any chance of it being needed.</p>
<p>Meanwhile, the Austrian rescue authorities should be alerted. Ask the
BergRestaurant (if it is open) or the <span lang="de-at">Loser
H&uuml;tte</span> to radio for help, or phone directly if a working
mobile phone and german speaker are on hand. Failing this, contact base
mobile phone and German speaker are on hand. Failing this, contact base
camp and get them to alert the rescue services. However, there will probably
be a delay of at least 4 hours before they reach the cave (longer if it is
dark). Do as much as you can in this time. A German speaker is almost
@ -614,7 +614,7 @@ pressing.</li>
part of the patient's body. Start at the head and work down to the toes.
Talk to the patient. All along the exam make sure he can feel your hands.
See if he can grip you hands firmly and equally. You are looking for
additional wounds, swellings, eccymosis (black marks from pooling blood),
additional wounds, swellings, ecchymosis (black marks from pooling blood),
tenderness, etc. Always do this survey. Write down the results.</li>
<li>When you have worked out what is wrong, write down the results. You

2
handbook/stool.htm
View File

@ -36,7 +36,7 @@ to keep the smell down.</p></li>
minging it down with rain. On a hot day the smell will be keen, and disease
rife.</p></li>
<li><p>DO take good aim! The best spots (i.e. relatively comfy, not to far away, and good'n'deep) will be discovered and used by several people. No-one wnats to see or smell yesterday's slop streaked down the side of an otherwise good grike.</p></li>
<li><p>DO take good aim! The best spots (i.e. relatively comfy, not to far away, and good'n'deep) will be discovered and used by several people. No-one wants to see or smell yesterday's slop streaked down the side of an otherwise good grike.</p></li>
<li><p>DO think about where your offerings may be washed during a rain-storm &ndash; into Steinbr&uuml;ckenh&ouml;hle perhaps?</p></li>
</ul>

23
handbook/update.htm
View File

@ -11,7 +11,7 @@
<h2>Rationale for having a system at all: </h2>
<p>For years, the website has been built by hand-editing html pages,
<p>For years, the website has been built by hand-editing HTML pages,
"traditionally" by one or two people, in constant email contact. Obviously
those people were thoroughly familiar with the locations of all the pages,
the conventions used for naming files, the style used throughout the site and
@ -69,7 +69,7 @@ can "check out" a copy of the page they want to change. They then make the
changes or additions required, and "commit" the new page back into the
system. The system keeps a record of all such changes, with a log message
in which you should say why the change was made (the system knows who you
are and when you commited the change, so you don't need to tell it that).</p>
are and when you committed the change, so you don't need to tell it that).</p>
<p>In order to join in the work, the central CVS repository needs to know
about you, so it can allow you to commit changes into the system (and thus
@ -81,20 +81,20 @@ site, or whatever).</p>
<h3>Software requirements</h3>
<p>You need a system which has a CVS client and supports SSH, so that you can
log in without sending a password in clear text over the internet. You need
log in without sending a password in clear text over the Internet. You need
an editor with which you are happy to edit web pages. Ideally this will
NOT be one of the commercial WYSIWYG web editors which add whole loads of
guff to your webpage in a manner that you don't see (and which, incidentally,
makes the pages vastly harder to maintain for the next person who comes
along with a basic html editor, not to mention making the pages load more
along with a basic HTML editor, not to mention making the pages load more
slowly and typically work in fewer browsers). Most of us use basic
text editors with extensions that make editing html easier. The easiest
text editors with extensions that make editing HTML easier. The easiest
way to get all this is to have a Linux machine, since most distributions
have all the tools you need ready built in. The rest of this page assumes
that you are doing all this on a recent Linux system. There are a few
useful links for those using Mac, RISC OS or Windows machines along
with the links to more detailed documentation <a href="#morelinks">at the end of
this page.</a> The cvs machine itself is a Linux box, and some of the
this page.</a> The CVS machine itself is a Linux box, and some of the
commands you need to use involve typing at the command line on that machine,
so some familiarity with Unix/Linux will make you feel more at home.</p>
@ -127,7 +127,7 @@ With recent versions of openssh, you need to type</p>
<pre>ssh-keygen -t dsa</pre>
<p>doeswith older versions, you may find that "-t" is not a valid option, in
<p>while with older versions, you may find that "-t" is not a valid option, in
which case</p>
<pre>ssh-keygen -d</pre>
@ -169,7 +169,7 @@ commands on your own machine, so get out of that command line with</p>
<pre>exit</pre>
<p>To use the CVS commands on your local machine (for checking out pages
to edit and commiting them back) you need to tell cvs where the archive
to edit and committing them back) you need to tell cvs where the archive
is. You can include a "-d <i>username</i>@cvs.cucc.survex.com:/export/cvs" with
cvs commands (useful if you use cvs on more than one repository), but
it is usually easier to add</p>
@ -196,7 +196,7 @@ cvs checkout expoweb</pre>
<p>and then move into the directory tree to make your changes. Thus far,
everything has been at the command line, but often doing the editing
will be more convenient through a desktop interface. You might find that
you want to set your file browser *not* to display an html view of the
you want to set your file browser *not* to display an HTML view of the
files, otherwise you will end up browsing the pages, rather than the
file tree, which makes editing much harder :-(</p>
@ -311,7 +311,7 @@ a "?" are ones which cvs doesn't know about - maybe you haven't "cvs add"ed
them yet.</p>
<h3>Updating the website</h3>
<p>Having commited any changes to the cvs tree, connect to cvs.cucc.survex.com
<p>Having committed any changes to the cvs tree, connect to cvs.cucc.survex.com
via ssh and run the command <tt>/opt/expo/bin/www-update</tt>. (You can do this
all in one step by just typing <tt>ssh cvs.cucc.survex.com
/opt/expo/bin/www-update</tt>.)</p>
@ -364,6 +364,9 @@ info is actually stored and served up.</p>
journals. Complicated by expo articles being in a separate hierarchy.</li>
<li>Translations</li>
<li>Other people's work - the noinfo hierarchy.</li>
<li>Style guide for writing cave descriptions: correct use of boldface
(<i>once</i> for each passage name, at the primary definition thereof; other
uses of the name should be links to this, and certainly should not be bold.)
</ul>
<hr />