minor manual changes

[spider.git] / sgml / usermanual_en.sgml

diff --git a/sgml/usermanual_en.sgml b/sgml/usermanual_en.sgml
index a5383cdbd7b25d72dfd2b0db017048d6dc8dee6a..cb2a033f7ca290fe056cbd7ff905fa2f4c0e779f 100644 (file)
--- a/sgml/usermanual_en.sgml
+++ b/sgml/usermanual_en.sgml
@@ -2213,6 +2213,14 @@ You can carry on with the message until you are ready to send it.
 <bf>set/dx</bf> Allow DX messages to come out on your terminal
 </tt>
 
+<P>
+<sect1>set/dxcq
+
+<P>
+<tt>
+<bf>set/dxcq</bf> Show CQ Zones on the end of DX announcements
+</tt>
+
 <P>
 <sect1>set/dxgrid
 
@@ -2222,11 +2230,11 @@ You can carry on with the message until you are ready to send it.
 </tt>
 
 <P>
-<sect1>set/dxstate
+<sect1>set/dxitu
 
 <P>
 <tt>
-<bf>set/dxstate</bf> Allow US State info on the end of DX announcements
+<bf>set/dxitu</bf> Show ITU Zones on the end of DX announcements
 </tt>
 
 <P>
@@ -2385,6 +2393,14 @@ Tell the system where you are. For example:-
 <bf>set/talk</bf> Allow TALK messages to come out on your terminal
 </tt>
 
+<P>
+<sect1>set/usstate
+
+<P>
+<tt>
+<bf>set/usstate</bf> Allow US State info on the end of DX announcements
+</tt>
+
 <P>
 <sect1>set/wcy
 
@@ -2455,6 +2471,23 @@ that prefix.
 
 <P>
 Show all the nodes connected to this node.
+<sect1>show/contest &lt;year and month&gt;
+
+<P>
+<tt>
+<bf>show/contest &lt;year and month&gt;</bf> Show all the contests for a month
+</tt>
+
+<P>
+Show all known contests which are maintained at http://www.sk3bg.se/contest/
+for a particular month or year. The format is reasonably flexible.
+For example:-
+  
+<tscreen><verb>
+  SH/CONTEST sep2003
+  SH/CONTEST 03 march
+</verb></tscreen>
+
 <sect1>show/date &lsqb;&lt;prefix&gt;|&lt;callsign&gt;&rsqb;
 
 <P>
@@ -2604,6 +2637,35 @@ This can be done with the SHOW/DX command like this:-
    SH/DX dxcc w on 20m iota
 </verb></tscreen>
 
+<sect1>show/dxqsl &lt;callsign&gt;
+
+<P>
+<tt>
+<bf>show/dxqsl &lt;callsign&gt;</bf> Show any QSL info gathered from spots
+</tt>
+
+<P>
+The node collects information from the comment fields in spots (things
+like 'VIA EA7WA' or 'QSL-G1TLH') and stores these in a database.
+
+This command allows you to interrogate that database and if the callsign
+is found will display the manager(s) that people have spotted. This 
+information is NOT reliable, but it is normally reasonably accurate if
+it is spotted enough times.
+
+For example:-
+
+<tscreen><verb>
+  sh/dxqsl 4k9w
+</verb></tscreen>
+
+You can check the raw input spots yourself with:-
+
+<tscreen><verb>
+  sh/dx 4k9w qsl
+</verb></tscreen>
+
+This gives you more background information.
 <sect1>show/dxstats &lsqb;days&rsqb; &lsqb;date&rsqb;
 
 <P>
@@ -3327,6 +3389,22 @@ allows you to see them again. This is the default.
 </tt>
 
 <P>
+<sect1>unset/dxcq
+
+<P>
+<tt>
+<bf>unset/dxcq</bf> Stop CQ Zones on the end of DX announcements
+</tt>
+
+<P>
+Display both the Spotter's and the Spotted's CQ Zone on the end
+of a DX announcement (there is just enough room). Some user programs
+cannot cope with this. The Spotter's CQ is on the RHS of the 
+time, the Spotted's CQ is on the LHS.
+
+Conflicts with: SET/DXGRID, SET/DXITU, SHOW/USSTATE
+
+Do a STAT/USER to see which flags you have set if you are confused.  
 <sect1>unset/dxgrid
 
 <P>
@@ -3340,24 +3418,26 @@ that if the spotter's grid square is known it is output on the end
 of a DX announcement (there is just enough room). Some user programs
 cannot cope with this. You can use this command to reset (or set)
 this feature.
-<sect1>unset/dxstate
+
+Conflicts with: SET/DXCQ, SET/DXITU
+
+Do a STAT/USER to see which flags you have set if you are confused.  
+<sect1>unset/dxitu
 
 <P>
 <tt>
-<bf>unset/dxstate</bf> Stop US State info on the end of DX announcements
+<bf>unset/dxitu</bf> Stop ITU Zones on the end of DX announcements
 </tt>
 
 <P>
-If the spotter's or spotted's US State is known it is output on the 
-end of a DX announcement (there is just enough room). 
+Display both the Spotter's and the Spotted's ITU Zone on the end
+of a DX announcement (there is just enough room). Some user programs
+cannot cope with this. The Spotter's ITU is on the RHS of the 
+time, the Spotted's ITU is on the LHS.
 
-A spotter's state will appear on the RHS of the time (like 
-SET/DXGRID) and the spotted's State will appear on the LHS of the
-time field. Any information found will override any locator 
-information from SET/DXGRID.
+Conflicts with: SET/DXGRID, SET/DXCQ, SHOW/USSTATE
 
-Some user programs cannot cope with this. You can use this command 
-to reset (or set) this feature.
+Do a STAT/USER to see which flags you have set if you are confused.  
 <sect1>unset/echo
 
 <P>
@@ -3454,6 +3534,28 @@ normal.
 </tt>
 
 <P>
+<sect1>unset/usstate
+
+<P>
+<tt>
+<bf>unset/usstate</bf> Stop US State info on the end of DX announcements
+</tt>
+
+<P>
+If the spotter's or spotted's US State is known it is output on the 
+end of a DX announcement (there is just enough room). 
+
+A spotter's state will appear on the RHS of the time (like 
+SET/DXGRID) and the spotted's State will appear on the LHS of the
+time field. Any information found will override any locator 
+information from SET/DXGRID.
+
+Some user programs cannot cope with this. You can use this command 
+to reset (or set) this feature.
+
+Conflicts with: SET/DXCQ, SET/DXITU
+
+Do a STAT/USER to see which flags you have set if you are confused.  
 <sect1>unset/wcy
 
 <P>