fix broken links

git-svn-id: https://svn.osgeo.org/grass/grass/trunk@49651 15284696-431f-4ddb-bdfa-cd5b030d7da7

imagery/i.gensig/i.gensig.html

@@ -100,7 +100,7 @@ result from the process.
 for creating groups and subgroups.
 
 <p>
-<em><a href="wxGUI.Vector_Digitizing_Tool.html">wxGUI vector digitizer</a></em>
+<em><a href="wxGUI.Vector_Digitizer.html">wxGUI vector digitizer</a></em>
 and
 <em><a href="r.digit.html">r.digit</a></em>
 for interactively  creating the training map.

imagery/i.gensigset/i.gensigset.html

@@ -46,7 +46,7 @@ The user must use
 <em><a href="r.digit.html">r.digit</a></em>,
 
 a combination of
-<em><a href="wxGUI.Vector_Digitizing_Tool.html">wxGUI vector digitizer</a></em>
+<em><a href="wxGUI.Vector_Digitizer.html">wxGUI vector digitizer</a></em>
 and 
 <em><a href="v.to.rast.html">v.to.rast</a></em>,
 or some other import/developement process (e.g.,
@@ -219,7 +219,7 @@ for creating groups and subgroups
 
 
 <p>
-<em><a href="wxGUI.Vector_Digitizing_Tool.html">wxGUI vector digitizer</a></em>
+<em><a href="wxGUI.Vector_Digitizer.html">wxGUI vector digitizer</a></em>
 and
 <em><a href="r.digit.html">r.digit</a></em>
 for interactively creating the training map.

imagery/i.vpoints/i.vpoints.html

@@ -195,7 +195,7 @@ are using coordinates taken from a reference map, circle
 these points and then use whatever means you have available
 to identify as precisely as possible the coordinate values
 for these points.  Digitizing software is recommended,
-especially <a href="wxGUI.Vector_Digitizing_Tool.html">wxGUI vector digitizer</a>. Once you have
+especially <a href="wxGUI.Vector_Digitizer.html">wxGUI vector digitizer</a>. Once you have
 determined the standard coordinates (for example, UTM's) of
 each circled point, you are ready to mark the points on the
 displayed image.

misc/m.cogo/m.cogo.html

@@ -123,7 +123,7 @@ converted to areas with <em>v.centroids</em>.
 <em>
 <a href="v.centroids.html">v.centroids</a>,
 <a href="v.clean.html">v.clean</a>,
-<a href="wxGUI.Vector_Digitizing_Tool.html">wxGUI vector digitizer</a>,
+<a href="wxGUI.Vector_Digitizer.html">wxGUI vector digitizer</a>,
 <a href="v.in.ascii.html">v.in.ascii</a>,
 <a href="v.type.html">v.type</a>
 </em>

raster/r.basins.fill/r.basins.fill.html

@@ -11,7 +11,7 @@ The coded stream network can be generated
 as part of the 
 <em><a href="r.watershed.html">r.watershed</a></em> program, 
 but the map layer of ridges will need to be created by hand
-(for example, through digitizing done in <em><a href="wxGUI.Vector_Digitizing_Tool.html">wxGUI vector digitizer</a></em>).
+(for example, through digitizing done in <em><a href="wxGUI.Vector_Digitizer.html">wxGUI vector digitizer</a></em>).
 
 <p>
 The resulting output raster map layer will 
@@ -40,7 +40,7 @@ r.watershed</a> for further details on the combined use of
 
 <em>
   <a href="r.watershed.html">r.watershed</a>,
-  <a href="wxGUI.Vector_Digitizing_Tool.html">wxGUI vector digitizer</a>
+  <a href="wxGUI.Vector_Digitizer.html">wxGUI vector digitizer</a>
 </em>
 
 <h2>AUTHORS</h2>

raster/r.digit/r.digit.html

@@ -57,7 +57,7 @@ or, finish (go to Step 1).
 <h2>SEE ALSO</h2>
 
 <em>
-  <a href="wxGUI.Vector_Digitizing_Tool.html">wxGUI vector digitizer</a>
+  <a href="wxGUI.Vector_Digitizer.html">wxGUI vector digitizer</a>
   <a href="d.graph.html">d.graph</a>,
   <a href="d.linegraph.html">d.linegraph</a>,
   <a href="g.region.html">g.region</a>,

raster/r.in.poly/r.in.poly.html

@@ -100,7 +100,7 @@ A
   <a href="r.in.xyz.html">r.in.xyz</a>,
   <a href="r.patch.html">r.patch</a>,
   <a href="v.in.ascii.html">v.in.ascii</a>,
-  <a href="wxGUI.Vector_Digitizing_Tool.html">wxGUI vector digitizer</a>
+  <a href="wxGUI.Vector_Digitizer.html">wxGUI vector digitizer</a>
 </em>
 
 <h2>AUTHOR</h2>

raster/r.le/r.le.setup/r.le.setup.html

@@ -92,7 +92,7 @@ command).
 
 <p>
 
-The user can also use the GRASS <em>r.digit</em> or <em><a href="wxGUI.Vector_Digitizing_Tool.html">wxGUI vector digitizer</a></em> 
+The user can also use the GRASS <em>r.digit</em> or <em><a href="wxGUI.Vector_Digitizer.html">wxGUI vector digitizer</a></em> 
 programs to digitize circular or polygonal regions and to create a 
 sampling regions map without using <em>r.le.setup</em>.  Or, as mention 
 above, an existing raster map can be used as a regions map.

raster/r.surf.contour/r.surf.contour.html

@@ -72,7 +72,7 @@ time will grow exponentially with the distance between contour lines.
   <a href="r.slope.aspect.html">r.slope.aspect</a>,
   <a href="r.surf.idw.html">r.surf.idw</a>,
   <a href="r.surf.idw2.html">r.surf.idw2</a>,
-  <a href="wxGUI.Vector_Digitizing_Tool.html">wxGUI vector digitizer</a>,
+  <a href="wxGUI.Vector_Digitizer.html">wxGUI vector digitizer</a>,
   <a href="v.surf.idw.html">v.surf.idw</a>,
   <a href="v.surf.rst.html">v.surf.rst</a>,
   <a href="v.to.rast.html">v.to.rast</a>

raster/r.thin/r.thin.html

@@ -25,7 +25,7 @@ with positive values on a background of 0's in the
 <em>r.thin</em> only creates raster map layers.  The user will need to run 
 <em><a href="r.to.vect.html">r.to.vect</a></em>
 on the resultant raster map to create a vector 
-(<em><a href="wxGUI.Vector_Digitizing_Tool.html">wxGUI vector digitizer</a></em>) map layer.
+(<em><a href="wxGUI.Vector_Digitizer.html">wxGUI vector digitizer</a></em>) map layer.
 
 <p><em>r.thin</em> may create small spurs or "dangling lines"
 during the thinning process.  These spurs may be removed
@@ -64,7 +64,7 @@ converge in &lt;= iterations.
   <a href="g.region.html">g.region</a>,
   <a href="r.to.vect.html">r.to.vect</a>,
   <a href="v.clean.html">v.clean</a>,
-  <a href="wxGUI.Vector_Digitizing_Tool.html">wxGUI vector digitizer</a>,
+  <a href="wxGUI.Vector_Digitizer.html">wxGUI vector digitizer</a>,
   <a href="v.build.html">v.build</a>
 </em>
 

scripts/v.db.addtable/v.db.addtable.html

@@ -13,10 +13,10 @@ usage.
 v.db.addtable will only insert category values into the table for those features 
 which actually have a category value in the relevant layer. The use can add 
 category values automatically by using <em>v.category</em> or manually with 
-<em><a href="wxGUI.Vector_Digitizing_Tool.html">wxGUI vector digitizer</a></em>
+<em><a href="wxGUI.Vector_Digitizer.html">wxGUI vector digitizer</a></em>
 before running v.db.addtable. Or one can run v.db.addtable first
 and then use either a combinatino of <em>v.category</em> + <em>v.to.db</em> or 
-<em><a href="wxGUI.Vector_Digitizing_Tool.html">wxGUI vector digitizer</a></em>
+<em><a href="wxGUI.Vector_Digitizer.html">wxGUI vector digitizer</a></em>
 to add the relevant lines to the table.
 
 The supported types of columns depend on the database backend. However, all

vector/v.build.polylines/v.build.polylines.html

@@ -20,7 +20,7 @@ on what node is initially picked for building polylines. If the
 direction of lines is important (it's not for boundaries to build
 areas), you have to manually change line directions with
 either <em><a href="v.edit.html">v.edit</a></em> or
-the <em><a href="wxGUI.Vector_Digitizing_Tool.html">wxGUI vector
+the <em><a href="wxGUI.Vector_Digitizer.html">wxGUI vector
 digitizer</a></em>.
 
 <p>Polylines provide the most appropriate representation of curved lines when it 

vector/v.category/v.category.html

@@ -22,7 +22,7 @@ geometry specified in 'type' is processed.
 the <b>option</b> parameter set to <b>add</b>, new categories will be
 added to existing centroids. Note however, that new centroids cannot
 be created this way.  To do so, they must be added manually
-using <em><a href="wxGUI.Vector_Digitizing_Tool.html">wxGUI vector
+using <em><a href="wxGUI.Vector_Digitizer.html">wxGUI vector
 digitizer</a></em> or by running <em>v.category</em> with the type
 parameter set to area.
 

vector/v.net.alloc/v.net.alloc.html

@@ -19,7 +19,7 @@ in order to connect points representing center nodes to the network.
 
 Nodes and arcs can be closed using cost = -1. 
 <p>Center nodes can also be assigned to vector nodes using 
-<em><a href="wxGUI.Vector_Digitizing_Tool.html">wxGUI vector digitizer</a></em>. 
+<em><a href="wxGUI.Vector_Digitizer.html">wxGUI vector digitizer</a></em>. 
 
 <h2>EXAMPLES</h2>
 

vector/v.net/v.net.html

@@ -24,7 +24,7 @@ unconnected and unreachable.
 <h3>NOTES</h3>
 
 If vector editing is required to modify the
-graph, <em><a href="wxGUI.Vector_Digitizing_Tool.html">wxGUI vector
+graph, <em><a href="wxGUI.Vector_Digitizer.html">wxGUI vector
 digitizer</a></em> or <em><a href="v.edit.html">v.edit</a></em> can be
 used. Separately,
 <a href="lrs.html">Linear Referencing System</a> is available in
@@ -63,7 +63,7 @@ v.net points=geodetic_swwake_pts output=geodetic_swwake_pts_net operation=arcs f
 <h2>SEE ALSO</h2>
 
 <em>
-  <a href="wxGUI.Vector_Digitizing_Tool.html">wxGUI vector digitizer</a>,
+  <a href="wxGUI.Vector_Digitizer.html">wxGUI vector digitizer</a>,
   <a href="v.edit.html">v.edit</a><br>
   <a href="v.net.iso.html">v.net.iso</a>,
   <a href="v.net.path.html">v.net.path</a>,

vector/vectorintro.html

@@ -101,7 +101,7 @@ possible. The <a href="v.build.html">v.build</a> module is used to
 generate topology. It optionally allows to extract the erroneous
 vector objects into a separate map. Topological errors can be
 corrected either manually
-within <a href="wxGUI.Vector_Digitizing_Tool.html">wxGUI vector
+within <a href="wxGUI.Vector_Digitizer.html">wxGUI vector
 digitizer</a> or, to some extent, automatically
 in <a href="v.clean.html">v.clean</a>.  A dedicated vector editing
 module is <a href="v.edit.html">v.edit</a> which supports global and