Przeglądaj źródła

use lowercase HTML tags

git-svn-id: https://svn.osgeo.org/grass/grass/trunk@48557 15284696-431f-4ddb-bdfa-cd5b030d7da7
Markus Neteler 13 lat temu
rodzic
commit
c5005a4d91
100 zmienionych plików z 1448 dodań i 1448 usunięć
  1. 9 9
      db/db.columns/db.columns.html
  2. 12 12
      db/db.connect/db.connect.html
  3. 6 6
      db/db.copy/db.copy.html
  4. 8 8
      db/db.createdb/db.createdb.html
  5. 7 7
      db/db.databases/db.databases.html
  6. 7 7
      db/db.describe/db.describe.html
  7. 8 8
      db/db.drivers/db.drivers.html
  8. 6 6
      db/db.dropdb/db.dropdb.html
  9. 21 21
      db/db.execute/db.execute.html
  10. 4 4
      db/db.login/db.login.html
  11. 12 12
      db/db.select/db.select.html
  12. 6 6
      db/db.tables/db.tables.html
  13. 4 4
      db/drivers/dbf/grass-dbf.html
  14. 4 4
      db/drivers/mysql/grass-mesql.html
  15. 5 5
      db/drivers/mysql/grass-mysql.html
  16. 9 9
      db/drivers/odbc/grass-odbc.html
  17. 3 3
      db/drivers/ogr/grass-ogr.html
  18. 23 23
      db/drivers/postgres/grass-pg.html
  19. 15 15
      display/d.barscale/d.barscale.html
  20. 5 5
      display/d.colorlist/d.colorlist.html
  21. 41 41
      display/d.colors/d.colors.html
  22. 28 28
      display/d.colortable/d.colortable.html
  23. 2 2
      display/d.extract/d.extract.html
  24. 38 38
      display/d.font/d.font.html
  25. 6 6
      display/d.fontlist/d.fontlist.html
  26. 10 10
      display/d.geodesic/d.geodesic.html
  27. 86 86
      display/d.graph/d.graph.html
  28. 34 34
      display/d.grid/d.grid.html
  29. 46 46
      display/d.his/d.his.html
  30. 12 12
      display/d.histogram/d.histogram.html
  31. 9 9
      display/d.info/d.info.html
  32. 15 15
      display/d.labels/d.labels.html
  33. 33 33
      display/d.legend/d.legend.html
  34. 18 18
      display/d.linegraph/d.linegraph.html
  35. 24 24
      display/d.measure/d.measure.html
  36. 2 2
      display/d.path/d.path.html
  37. 3 3
      display/d.profile/d.profile.html
  38. 29 29
      display/d.rast.arrow/d.rast.arrow.html
  39. 8 8
      display/d.rast.num/d.rast.num.html
  40. 3 3
      display/d.rast/d.rast.html
  41. 35 35
      display/d.rgb/d.rgb.html
  42. 7 7
      display/d.rhumbline/d.rhumbline.html
  43. 37 37
      display/d.text/d.text.html
  44. 8 8
      display/d.thematic.area/d.thematic.area.html
  45. 29 29
      display/d.title/d.title.html
  46. 4 4
      display/d.vect.chart/d.vect.chart.html
  47. 4 4
      display/d.what.rast/d.what.rast.html
  48. 6 6
      display/d.what.vect/d.what.vect.html
  49. 14 14
      display/d.where/d.where.html
  50. 6 6
      display/d.zoom/d.zoom.html
  51. 3 3
      doc/projectionintro.html
  52. 6 6
      doc/raster/r.example/r.example.html
  53. 2 2
      doc/vector/v.example/v.example.html
  54. 10 10
      doc/vector/v.modules.html
  55. 22 22
      doc/vector/vector.html
  56. 15 15
      general/g.access/g.access.html
  57. 2 2
      general/g.cairocomp/g.cairocomp.html
  58. 7 7
      general/g.copy/g.copy.html
  59. 3 3
      general/g.dirseps/g.dirseps.html
  60. 23 23
      general/g.filename/g.filename.html
  61. 12 12
      general/g.findetc/g.findetc.html
  62. 1 1
      general/g.gui/g.gui.html
  63. 5 5
      general/g.list/g.list.html
  64. 5 5
      general/g.mapset/g.mapset.html
  65. 9 9
      general/g.mapsets/g.mapsets.html
  66. 10 10
      general/g.message/g.message.html
  67. 5 5
      general/g.mkfontcap/g.mkfontcap.html
  68. 2 2
      general/g.mlist/g.mlist.html
  69. 1 1
      general/g.mremove/g.mremove.html
  70. 3 3
      general/g.parser/g.parser.html
  71. 2 2
      general/g.pnmcat/g.pnmcat.html
  72. 3 3
      general/g.pnmcomp/g.pnmcomp.html
  73. 3 3
      general/g.ppmtopng/g.ppmtopng.html
  74. 27 27
      general/g.proj/g.proj.html
  75. 8 8
      general/g.region/g.region.html
  76. 4 4
      general/g.remove/g.remove.html
  77. 3 3
      general/g.rename/g.rename.html
  78. 30 30
      general/g.setproj/g.setproj.html
  79. 11 11
      general/g.tempfile/g.tempfile.html
  80. 6 6
      imagery/i.albedo/i.albedo.html
  81. 9 9
      imagery/i.aster.toar/i.aster.toar.html
  82. 9 9
      imagery/i.biomass/i.biomass.html
  83. 22 22
      imagery/i.cca/i.cca.html
  84. 102 102
      imagery/i.class/i.class.html
  85. 56 56
      imagery/i.cluster/i.cluster.html
  86. 11 11
      imagery/i.eb.eta/i.eb.eta.html
  87. 11 11
      imagery/i.eb.evapfr/i.eb.evapfr.html
  88. 8 8
      imagery/i.eb.h_SEBAL01/i.eb.h_sebal01.html
  89. 10 10
      imagery/i.eb.netrad/i.eb.netrad.html
  90. 13 13
      imagery/i.eb.soilheatflux/i.eb.soilheatflux.html
  91. 8 8
      imagery/i.emissivity/i.emissivity.html
  92. 11 11
      imagery/i.evapo.mh/i.evapo.mh.html
  93. 8 8
      imagery/i.evapo.pm/i.evapo.pm.html
  94. 11 11
      imagery/i.evapo.pt/i.evapo.pt.html
  95. 13 13
      imagery/i.evapo.time/i.evapo.time.html
  96. 14 14
      imagery/i.fft/i.fft.html
  97. 40 40
      imagery/i.gensig/i.gensig.html
  98. 56 56
      imagery/i.gensigset/i.gensigset.html
  99. 22 22
      imagery/i.group/i.group.html
  100. 0 0
      imagery/i.his.rgb/i.his.rgb.html

+ 9 - 9
db/db.columns/db.columns.html

@@ -6,7 +6,7 @@ databases are supported through dbf, shp, odbc and pg drivers.
 <h2>NOTE</h2>
 
 If parameters for database connection are already set with 
-<a HREF="db.connect.html">db.connect</a>, they are taken as default values and
+<a href="db.connect.html">db.connect</a>, they are taken as default values and
 do not need to be spcified each time.
 
 <h2>EXAMPLE</h2>
@@ -31,14 +31,14 @@ db.columns table=network driver=dbf database=/daten/grassdata/fire/PERMANENT/dbf
 </pre></div>
 
 <h2>SEE ALSO</h2>
-<em><a HREF="db.connect.html">db.connect</a>,
-<a HREF="db.describe.html">db.describe</a>,
-<a HREF="db.drivers.html">db.drivers</a>,
-<a HREF="db.droptable.html">db.droptable</a>,
-<a HREF="db.execute.html">db.execute</a>,
-<a HREF="db.login.html">db.login</a>,
-<a HREF="db.tables.html">db.tables</a>,
-<a HREF="sql.html">GRASS SQL interface</a></em>
+<em><a href="db.connect.html">db.connect</a>,
+<a href="db.describe.html">db.describe</a>,
+<a href="db.drivers.html">db.drivers</a>,
+<a href="db.droptable.html">db.droptable</a>,
+<a href="db.execute.html">db.execute</a>,
+<a href="db.login.html">db.login</a>,
+<a href="db.tables.html">db.tables</a>,
+<a href="sql.html">GRASS SQL interface</a></em>
 
 <h2>AUTHOR</h2>
 

+ 12 - 12
db/db.connect/db.connect.html

@@ -5,17 +5,17 @@ These parameters are then taken as default values by modules so that the
 user does not need to enter the parameters each time.
 
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 
 Values are stored in the mapset's <tt>VAR</tt> file;
 the connection is not tested for validity.
-<P>
+<p>
 The <b>-p</b> flag will display the current connection parameters. 
-<P>
+<p>
 The <b>-c</b> flag will silently check if the connection parameters have
 been set, and if not will set them to use GRASS's default values.
 (useful in scripts before you attempt to create a new database table)
-<P>
+<p>
 To connect a vector map to a database table, use <em>v.db.connect</em>
 or <em>v.db.addtable</em>.
 
@@ -42,7 +42,7 @@ db.connect driver=sqlite database='$GISDBASE/$LOCATION_NAME/$MAPSET/sqlite.db'
 db.connect -p
 db.tables -p
 </pre></div>
-<P>
+<p>
 The SQLite database is created automatically when used the first time.
 
 
@@ -109,13 +109,13 @@ db.tables -p
 <h2>SEE ALSO</h2>
 
 <em>
-<a HREF="db.columns.html">db.columns</a>,
-<a HREF="db.drivers.html">db.drivers</a>,
-<a HREF="db.login.html">db.login</a>,
-<a HREF="db.tables.html">db.tables</a>,
-<a HREF="v.db.addtable.html">v.db.addtable</a>,
-<a HREF="v.db.connect.html">v.db.connect</a>,
-<a HREF="sql.html">GRASS SQL interface</a></em>
+<a href="db.columns.html">db.columns</a>,
+<a href="db.drivers.html">db.drivers</a>,
+<a href="db.login.html">db.login</a>,
+<a href="db.tables.html">db.tables</a>,
+<a href="v.db.addtable.html">v.db.addtable</a>,
+<a href="v.db.connect.html">v.db.connect</a>,
+<a href="sql.html">GRASS SQL interface</a></em>
 
 
 <h2>AUTHOR</h2>

+ 6 - 6
db/db.copy/db.copy.html

@@ -6,7 +6,7 @@ Databases can be connected through different drivers (see example).
 <h2>NOTES</h2>
 
 Attribute tables can be copied manually using db.copy and 
-<em><a HREF="v.db.connect.html">v.db.connect</a></em>. Current connection 
+<em><a href="v.db.connect.html">v.db.connect</a></em>. Current connection 
 settings are saved in <em>$LOCATION/vector_map/dbln</em>.  
 
 <h2>EXAMPLES</h2>
@@ -61,11 +61,11 @@ db.copy from_driver=sqlite from_database=$HOME/grassdata/spearfish60/user1/sqlit
 
 <h2>SEE ALSO</h2>
 
-<em><a HREF="v.db.connect.html">v.db.connect</a>,
-<a HREF="db.drivers.html">db.drivers</a>,
-<a HREF="db.login.html">db.login</a>,
-<a HREF="v.clean.html">v.clean</a>,
-<a HREF="sql.html">GRASS SQL interface</a></em>
+<em><a href="v.db.connect.html">v.db.connect</a>,
+<a href="db.drivers.html">db.drivers</a>,
+<a href="db.login.html">db.login</a>,
+<a href="v.clean.html">v.clean</a>,
+<a href="sql.html">GRASS SQL interface</a></em>
 
 <h2>AUTHOR</h2>
 

+ 8 - 8
db/db.createdb/db.createdb.html

@@ -23,14 +23,14 @@ db.createdb driver=pg database='host=pgserver.itc.it,dbname=grass60test'
 <h2>SEE ALSO</h2>
 
 <em>
-<a HREF="db.columns.html">db.columns</a>,
-<a HREF="db.describe.html">db.describe</a>,
-<a HREF="db.drivers.html">db.drivers</a>,
-<a HREF="db.droptable.html">db.droptable</a>,
-<a HREF="db.execute.html">db.execute</a>,
-<a HREF="db.login.html">db.login</a>,
-<a HREF="db.tables.html">db.tables</a>,
-<a HREF="sql.html">GRASS SQL interface</a></em>
+<a href="db.columns.html">db.columns</a>,
+<a href="db.describe.html">db.describe</a>,
+<a href="db.drivers.html">db.drivers</a>,
+<a href="db.droptable.html">db.droptable</a>,
+<a href="db.execute.html">db.execute</a>,
+<a href="db.login.html">db.login</a>,
+<a href="db.tables.html">db.tables</a>,
+<a href="sql.html">GRASS SQL interface</a></em>
 
 <h2>AUTHOR</h2>
 

+ 7 - 7
db/db.databases/db.databases.html

@@ -5,13 +5,13 @@ are dbf, shp, odbc and pg.
 
 <h2>SEE ALSO</h2>
 
-<em><a HREF="db.columns.html">db.columns</a>,
-<a HREF="db.describe.html">db.describe</a>,
-<a HREF="db.drivers.html">db.drivers</a>,
-<a HREF="db.execute.html">db.execute</a>,
-<a HREF="db.login.html">db.login</a>,
-<a HREF="db.tables.html">db.tables</a>,
-<a HREF="sql.html">GRASS SQL interface</a></em>
+<em><a href="db.columns.html">db.columns</a>,
+<a href="db.describe.html">db.describe</a>,
+<a href="db.drivers.html">db.drivers</a>,
+<a href="db.execute.html">db.execute</a>,
+<a href="db.login.html">db.login</a>,
+<a href="db.tables.html">db.tables</a>,
+<a href="sql.html">GRASS SQL interface</a></em>
 
 <h2>AUTHOR</h2>
 

+ 7 - 7
db/db.describe/db.describe.html

@@ -6,7 +6,7 @@
 <h2>NOTE</h2>
 
 If parameters for database connection are already set with 
-<a HREF="db.connect.html">db.connect</a>, they are taken as default values and
+<a href="db.connect.html">db.connect</a>, they are taken as default values and
 do not need to be spcified each time.
  
 <h2>EXAMPLE</h2>
@@ -44,12 +44,12 @@ update:yes
 <h2>SEE ALSO</h2>
 
 <em>
-<a HREF="db.columns.html">db.columns</a>,
-<a HREF="db.droptable.html">db.droptable</a>,
-<a HREF="db.execute.html">db.execute</a>,
-<a HREF="db.login.html">db.login</a>,
-<a HREF="db.tables.html">db.tables</a>,
-<a HREF="sql.html">GRASS SQL interface</a></em>
+<a href="db.columns.html">db.columns</a>,
+<a href="db.droptable.html">db.droptable</a>,
+<a href="db.execute.html">db.execute</a>,
+<a href="db.login.html">db.login</a>,
+<a href="db.tables.html">db.tables</a>,
+<a href="sql.html">GRASS SQL interface</a></em>
 
 <h2>AUTHOR</h2>
 

+ 8 - 8
db/db.drivers/db.drivers.html

@@ -13,14 +13,14 @@ db.drivers -p
 <h2>SEE ALSO</h2>
 
 <em>
-<a HREF="db.connect.html">db.connect</a>,
-<a HREF="db.describe.html">db.describe</a>,
-<a HREF="db.drivers.html">db.drivers</a>,
-<a HREF="db.droptable.html">db.droptable</a>,
-<a HREF="db.execute.html">db.execute</a>,
-<a HREF="db.login.html">db.login</a>,
-<a HREF="db.tables.html">db.tables</a>,
-<a HREF="sql.html">GRASS SQL interface</a>
+<a href="db.connect.html">db.connect</a>,
+<a href="db.describe.html">db.describe</a>,
+<a href="db.drivers.html">db.drivers</a>,
+<a href="db.droptable.html">db.droptable</a>,
+<a href="db.execute.html">db.execute</a>,
+<a href="db.login.html">db.login</a>,
+<a href="db.tables.html">db.tables</a>,
+<a href="sql.html">GRASS SQL interface</a>
 </em>
 
 <h2>AUTHOR</h2>

+ 6 - 6
db/db.dropdb/db.dropdb.html

@@ -9,12 +9,12 @@
 
 <h2>SEE ALSO</h2>
 <em>
-<a HREF="db.describe.html">db.describe</a>,
-<a HREF="db.droptable.html">db.droptable</a>,
-<a HREF="db.execute.html">db.execute</a>,
-<a HREF="db.login.html">db.login</a>,
-<a HREF="db.tables.html">db.tables</a>,
-<a HREF="sql.html">GRASS SQL interface</a></em>
+<a href="db.describe.html">db.describe</a>,
+<a href="db.droptable.html">db.droptable</a>,
+<a href="db.execute.html">db.execute</a>,
+<a href="db.login.html">db.login</a>,
+<a href="db.tables.html">db.tables</a>,
+<a href="sql.html">GRASS SQL interface</a></em>
 
 <h2>AUTHOR</h2>
 

+ 21 - 21
db/db.execute/db.execute.html

@@ -6,11 +6,11 @@
 
 <em>db.execute</em> only executes SQL statements and does not return 
 any data. If you need data returned from the database, use <em>db.select</em>.
-<P>
+<p>
 If parameters for database connection are already set with 
-<a HREF="db.connect.html">db.connect</a>, they are taken as default values and
+<a href="db.connect.html">db.connect</a>, they are taken as default values and
 do not need to be specified each time.
-<P>
+<p>
 If you have a large number of SQL commands to process, it is much much faster
 to place all the SQL statements into a text file and use <em>db.execute</em>'s
 <b>input</b> file parameter than it is to process each statement individually
@@ -33,50 +33,50 @@ echo 'create table soils (cat integer, soiltype varchar(10) )' | db.execute
 db.execute driver=odbc database=g60test input=file.sql
 </pre></div>
 
-<P>
+<p>
 <em>Insert new row into attribute table:</em><br>
 <div class="code"><pre>
 echo "INSERT INTO nobugs (id,name,east_gb,north_gb) values (30,'Ala',1657340,5072301)" | db.execute
 </pre></div>
 
-<P>
+<p>
 <em>Update attribute entries to new value based on SQL rule:</em><br>
 <div class="code"><pre>
 echo "UPDATE roads SET travelcost=5 WHERE cat=1" | db.execute
 </pre></div>
 
-<P>
+<p>
 <em>Update attribute entries to new value based on SQL rule:</em><br>
 <div class="code"><pre>
 echo "UPDATE dourokukan SET testc=50 WHERE testc is NULL" | db.execute
 </pre></div>
 
-<P>
+<p>
 <em>Delete selected rows from attribute table:</em><br>
 <div class="code"><pre>
 echo "DELETE FROM gsod_stationlist WHERE latitude < -91" | db.execute
 </pre></div>
 
-<P>
+<p>
 <em>Add new column to attribute table:</em><br>
 <div class="code"><pre>
 echo "ALTER TABLE roads ADD COLUMN length double" | db.execute
 </pre></div>
 
-<P>
+<p>
 <em>Column type conversion - update new column from existing column (all drivers except for DBF):</em><br>
 <div class="code"><pre>
 # 'z_value' is varchar and 'z' is double precision:
 echo "update geodetic_pts SET z = CAST(z_value AS numeric)" | db.execute
 </pre></div>
 
-<P>
+<p>
 <em>Drop column from attribute table:</em><br>
 <div class="code"><pre>
 echo "ALTER TABLE roads DROP COLUMN length" | db.execute
 </pre></div>
 
-<P>
+<p>
 <em>Drop table (not supported by all drivers)</em><br>
 <div class="code"><pre>
 echo "DROP TABLE fmacopy" | db.execute
@@ -92,24 +92,24 @@ UPDATE roads SET travelcost=2 WHERE cat=2;
 cat file.sql | db.execute
 </pre></div>
 
-<P>
+<p>
 <em>Join table 'myroads' into table 'extratab' based on common 'cat' column values (not supported by DBF driver):</em><br>
 <div class="code"><pre>
 echo "UPDATE extratab SET names=(SELECT label FROM myroads WHERE extratab.cat=myroads.cat);" | db.execute
 </pre></div>
 
 <h2>SEE ALSO</h2>
-<em><a HREF="db.columns.html">db.columns</a>,
-<a HREF="db.describe.html">db.describe</a>,
-<a HREF="db.drivers.html">db.drivers</a>,
-<a HREF="db.droptable.html">db.droptable</a>,
-<a HREF="db.login.html">db.login</a>,
-<a HREF="db.select.html">db.select</a>,
-<a HREF="db.tables.html">db.tables</a>,
-<a HREF="sql.html">GRASS SQL interface</a></em>
+<em><a href="db.columns.html">db.columns</a>,
+<a href="db.describe.html">db.describe</a>,
+<a href="db.drivers.html">db.drivers</a>,
+<a href="db.droptable.html">db.droptable</a>,
+<a href="db.login.html">db.login</a>,
+<a href="db.select.html">db.select</a>,
+<a href="db.tables.html">db.tables</a>,
+<a href="sql.html">GRASS SQL interface</a></em>
 
 <h2>AUTHOR</h2>
 
 CERL
 
-<p><i>Last changed: $Date$</i></p>
+<p><i>Last changed: $Date$</i>

+ 4 - 4
db/db.login/db.login.html

@@ -17,7 +17,7 @@ Example 1: Username specified, password will be invisibly queried interactively:
 db.login user=bacava
 </pre></div>
 
-<P>
+<p>
 Example 2: Username and password specified (note that the command
 lines history will store the password in this way):
 
@@ -25,7 +25,7 @@ lines history will store the password in this way):
 db.login user=bacava pass=secret
 </pre></div>
 
-<P>
+<p>
 Example 3: Username and empty password specified (note that the command
 lines history will store the password in this way):
 
@@ -35,8 +35,8 @@ db.login user=bacava pass=""
 
 <h2>SEE ALSO</h2>
 <em>
-<a HREF="db.connect.html">db.connect</a>,
-<a HREF="db.test.html">db.test</a>
+<a href="db.connect.html">db.connect</a>,
+<a href="db.test.html">db.test</a>
 </em>
 
 <h2>AUTHOR</h2>

+ 12 - 12
db/db.select/db.select.html

@@ -7,7 +7,7 @@ to standard output.
 <h2>NOTE</h2>
 
 If parameters for database connection are already set with 
-<a HREF="db.connect.html">db.connect</a>, they are taken as default values and
+<a href="db.connect.html">db.connect</a>, they are taken as default values and
 do not need to be spcified each time. Output will be displayed to stdout or can
 be directed to a file.
 
@@ -28,21 +28,21 @@ or
 db.select -c driver=odbc database=g51test table=roads input=file.sql > result.csv
 </pre></div>
 
-<P>
+<p>
 
 <em>Select some string attribute, exclude others:</em><br>
 <div class="code"><pre>
 echo "SELECT * FROM archsites WHERE str1 &lt;&gt; 'No Name'" | db.select
 </pre></div>
 
-<P>
+<p>
 
 <em>Select some string attribute with ZERO length:</em><br>
 <div class="code"><pre>
 echo "SELECT * FROM archsites WHERE str1 IS NULL" | db.select
 </pre></div>
 
-<P>
+<p>
 
 <em>Select coordinates from PostGIS table:</em><br>
 <div class="code"><pre>
@@ -51,14 +51,14 @@ echo "SELECT x(geo),y(geo) FROM localizzazione" | db.select
 
 <h2>SEE ALSO</h2>
 
-<em><a HREF="sql.html">GRASS SQL interface</a>,
-<a HREF="db.connect.html">db.connect</a>,
-<a HREF="db.describe.html">db.describe</a>,
-<a HREF="db.drivers.html">db.drivers</a>,
-<a HREF="db.droptable.html">db.droptable</a>,
-<a HREF="db.execute.html">db.execute</a>,
-<a HREF="db.login.html">db.login</a>,
-<a HREF="db.tables.html">db.tables</a></em>
+<em><a href="sql.html">GRASS SQL interface</a>,
+<a href="db.connect.html">db.connect</a>,
+<a href="db.describe.html">db.describe</a>,
+<a href="db.drivers.html">db.drivers</a>,
+<a href="db.droptable.html">db.droptable</a>,
+<a href="db.execute.html">db.execute</a>,
+<a href="db.login.html">db.login</a>,
+<a href="db.tables.html">db.tables</a></em>
 
 
 <h2>AUTHOR</h2>

+ 6 - 6
db/db.tables/db.tables.html

@@ -5,7 +5,7 @@
 <h2>NOTE</h2>
 
 If parameters for database connection are already set with 
-<a HREF="db.connect.html">db.connect</a>, they are taken as default values and
+<a href="db.connect.html">db.connect</a>, they are taken as default values and
 do not need to be spcified each time.
 
 <h2>EXAMPLES</h2>
@@ -23,11 +23,11 @@ db.tables driver=dbf database=/home/user/grassdata/fire/PERMANENT/dbf
 </pre></div>
 
 <h2>SEE ALSO</h2>
-<em><a HREF="db.columns.html">db.columns</a>,
-<a HREF="db.droptable.html">db.droptable</a>,
-<a HREF="db.login.html">db.login</a>,
-<a HREF="db.execute.html">db.execute</a>,
-<a HREF="sql.html">GRASS SQL interface</a></em>
+<em><a href="db.columns.html">db.columns</a>,
+<a href="db.droptable.html">db.droptable</a>,
+<a href="db.login.html">db.login</a>,
+<a href="db.execute.html">db.execute</a>,
+<a href="sql.html">GRASS SQL interface</a></em>
 
 <h2>AUTHOR</h2>
 ?

+ 4 - 4
db/drivers/dbf/grass-dbf.html

@@ -115,7 +115,7 @@ SQL parser error: syntax error, unexpected NAME processing 'IN'..
 </pre></div>
 indicates that an unsupported SQL statement (here, 'IN') was used. The only
 solution is to switch the DBMI backend to a real SQL engine (SQLite, 
-PostgreSQL, MySQL etc.). See <a HREF="sql.html">SQL support in GRASS GIS</a>.
+PostgreSQL, MySQL etc.). See <a href="sql.html">SQL support in GRASS GIS</a>.
 
 <p>
 An error message such as:
@@ -133,13 +133,13 @@ column names on the fly.
 <h2>SEE ALSO</h2>
 
 <em>
-<a HREF="db.connect.html">db.connect</a>,
-<a HREF="sql.html">SQL support in GRASS GIS</a><br>
+<a href="db.connect.html">db.connect</a>,
+<a href="sql.html">SQL support in GRASS GIS</a><br>
 <a href="http://shapelib.maptools.org/dbf_api.html">DBF Specifications</a> (Shapelib)
 </em>
 
 <p><i>Last changed: $Date$</i>
 <HR>
-<BR><a href=index.html>Help Index</a>
+<br><a href=index.html>Help Index</a>
 </body>
 </html>

+ 4 - 4
db/drivers/mysql/grass-mesql.html

@@ -57,19 +57,19 @@ mysql.time_zone_leap_second table. This can be fixed in future.
 <h2>SEE ALSO</h2>
 
 <em>
-<a HREF="db.connect.html">db.connect</a>,
-<a HREF="sql.html">SQL support in GRASS GIS</a></em>
+<a href="db.connect.html">db.connect</a>,
+<a href="sql.html">SQL support in GRASS GIS</a></em>
 
 <h2>Credits</h2>
 Development of the driver was sponsored by
 <a href="http://www.faunalia.it">Faunalia</a> (Italy)
 as part of a project for <a href="http://www.atac.roma.it/">ATAC</a>.
 
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
 Radim Blazek
 
 <p><i>Last changed: $Date$</i>
 <HR>
-<BR><a href=index.html>Help Index</a>
+<br><a href=index.html>Help Index</a>
 </body>
 </html>

+ 5 - 5
db/drivers/mysql/grass-mysql.html

@@ -20,7 +20,7 @@ are created automaticaly when a new vector is written and the
 name of the table is the same as the name of the vector it is 
 good practice to create a new database for each GRASS mapset.
 
-<H2>Creating a MySQL database</H2>
+<h2>Creating a MySQL database</h2>
 
 A new database is created within MySQL:
 
@@ -108,19 +108,19 @@ GRASS for MySQL driver.
 <h2>SEE ALSO</h2>
 
 <em>
-<a HREF="db.connect.html">db.connect</a>,
-<a HREF="sql.html">SQL support in GRASS GIS</a></em>
+<a href="db.connect.html">db.connect</a>,
+<a href="sql.html">SQL support in GRASS GIS</a></em>
 	
 <h2>Credits</h2>
 Development of the driver was sponsored by 
 <a href="http://www.faunalia.it">Faunalia</a> (Italy)
 as part of a project for <a href="http://www.atac.roma.it/">ATAC</a>.
 
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
 Radim Blazek
 
 <p><i>Last changed: $Date$</i>
 <HR>
-<BR><a href=index.html>Help Index</a>
+<br><a href=index.html>Help Index</a>
 </body>
 </html>

+ 9 - 9
db/drivers/odbc/grass-odbc.html

@@ -44,15 +44,15 @@ Communication between GRASS and ODBC database for attribute management: <br>
 </table>
 
 
-<H2>Supported SQL commands</H2>
+<h2>Supported SQL commands</h2>
 
 All SQL commands supported by ODBC.
 
-<H2>Operators available in conditions</H2>
+<h2>Operators available in conditions</h2>
 
 All SQL operators supported by ODBC.
 
-<H2>EXAMPLE</H2>
+<h2>EXAMPLE</h2>
 
 In this example we copy the dbf file of a SHAPE map into ODBC, then connect
 GRASS to the ODBC DBMS. Usually the table will be already present in the
@@ -141,7 +141,7 @@ Now the table name 'mytable' should appear.
 <p>
 Doesn't work? Check with 'isql &lt;databasename&gt;' if the ODBC-PostgreSQL
 connection is really established.
-</p></ul>
+</ul>
 
 Note that you can also connect mySQL, Oracle etc. through ODBC to GRASS.
 
@@ -154,16 +154,16 @@ v.db.connect -p mytable.shp
 
 which should print the database connection through ODBC to the defined RDBMS.
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
 <em>
-<a HREF="db.connect.html">db.connect</a>,
-<a HREF="v.db.connect.html">v.db.connect</a>,
+<a href="db.connect.html">db.connect</a>,
+<a href="v.db.connect.html">v.db.connect</a>,
 <a href="http://www.unixODBC.org">unixODBC web site</a>,
-<a HREF="sql.html">SQL support in GRASS GIS</a></em>
+<a href="sql.html">SQL support in GRASS GIS</a></em>
 
 <p><i>Last changed: $Date$</i>
 <HR>
-<BR><a href=index.html>Help Index</a>
+<br><a href=index.html>Help Index</a>
 </body>
 </html>

+ 3 - 3
db/drivers/ogr/grass-ogr.html

@@ -17,11 +17,11 @@ This driver is principally only used by <em>v.external</em>.
 
 <h2>SEE ALSO</h2>
 
-<em><a HREF="sql.html">SQL support in GRASS GIS</a></em>,
-<em><A HREF="v.external.html">v.external</A></em>
+<em><a href="sql.html">SQL support in GRASS GIS</a></em>,
+<em><a href="v.external.html">v.external</A></em>
 
 <p><i>Last changed: $Date$</i>
 <HR>
-<BR><a href=index.html>Help Index</a>
+<br><a href=index.html>Help Index</a>
 </body>
 </html>

+ 23 - 23
db/drivers/postgres/grass-pg.html

@@ -15,12 +15,12 @@
 
 The driver name is 'pg'.
 
-<H2>Creating a PostgreSQL database</H2>
+<h2>Creating a PostgreSQL database</h2>
 
 A new database is created with 'createdb', see the PostgreSQL manual
 for details.
 
-<H2>Connecting GRASS to PostgreSQL</H2>
+<h2>Connecting GRASS to PostgreSQL</h2>
 
 <div class="code"><pre>
 # example for connecting to a PostgreSQL server:
@@ -32,19 +32,19 @@ db.tables -p
 </pre></div>
 
 
-<H2>Supported SQL commands</H2>
+<h2>Supported SQL commands</h2>
 
 All SQL commands supported by PostgreSQL.
 
 It's not possible to use C-like escapes (with backslash
 like \n etc) within SQL syntax. 
 
-<H2>Operators available in conditions</H2>
+<h2>Operators available in conditions</h2>
 
 All SQL operators supported by PostgreSQL.
 
 
-<H2>Adding an unique ID column</H2>
+<h2>Adding an unique ID column</h2>
 
 Import vector module require an unique ID column which can
 be generated as follows in a PostgreSQL table:
@@ -69,7 +69,7 @@ COPY t1 FROM 'filename' USING DELIMITERS ',';
 
 <a href="http://www.klaban.torun.pl/prog/pg2xbase/">pg2xbase</a>: 
 DBF to PostgreSQL converter.
-<BR>
+<br>
 
 <h2>Geometry import from PostgreSQL table</h2>
 
@@ -118,43 +118,43 @@ v.info -t test
 <ul>
 <li><a href="http://postgis.refractions.net/download/">PostGIS with shp2pgsql</a>:<br>
  <tt>shp2pgsql -D lakespy2 lakespy2 test > lakespy2.sql</tt>
-<BR><BR>
+<br><br>
 <li><a href="http://e00pg.sourceforge.net/">e00pg</a>: E00 to PostGIS filter,
 see also <em><a href="v.in.e00.html">v.in.e00</a></em>.
-<BR><BR>
+<br><br>
 <li>GDAL/OGR <a href="http://www.gdal.org/ogr/">ogrinfo and ogr2ogr</a>:
 GIS vector format converter and library, e.g. ArcInfo or SHAPE to PostGIS.<br>
   <tt>ogr2ogr -f "PostgreSQL" shapefile ??</tt>
-<BR><BR>
+<br><br>
 </ul>
 
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
 <em>
-<a HREF="db.connect.html">db.connect</a>,
-<a HREF="db.execute.html">db.execute</a>,<BR>
-<a HREF="databaseintro.html">Database management in GRASS GIS</a>,<BR>
-<a HREF="database.html">Help pages for database modules</a>,<BR>
-<a HREF="sql.html">SQL support in GRASS GIS</a>
+<a href="db.connect.html">db.connect</a>,
+<a href="db.execute.html">db.execute</a>,<br>
+<a href="databaseintro.html">Database management in GRASS GIS</a>,<br>
+<a href="database.html">Help pages for database modules</a>,<br>
+<a href="sql.html">SQL support in GRASS GIS</a>
 </em>
-<BR><BR>
+<br><br>
 <em>
-<a href="http://www.PostgreSQL.org">PostgreSQL web site</a>,<BR>
+<a href="http://www.PostgreSQL.org">PostgreSQL web site</a>,<br>
 <a href="http://www.pgadmin.org/">pgAdmin graphical user interface</a>
 </em>
 <p>
 Book: <a href="http://www.postgresql.org/docs/books/awbook.html">PostgreSQL:
-  Introduction and Concepts</a> by Bruce Momjian<BR>
+  Introduction and Concepts</a> by Bruce Momjian<br>
 <em>
-<a href="http://www.postgresql.org/docs/">PostgreSQL Documentation</a><BR>
-<a href="http://techdocs.postgresql.org/">PostgreSQL Technical Documentation</a><BR>
-<a href="http://www.gdal.org/ogr/drv_pg.html">GDAL/OGR PostgreSQL driver documentation</a><BR>
+<a href="http://www.postgresql.org/docs/">PostgreSQL Documentation</a><br>
+<a href="http://techdocs.postgresql.org/">PostgreSQL Technical Documentation</a><br>
+<a href="http://www.gdal.org/ogr/drv_pg.html">GDAL/OGR PostgreSQL driver documentation</a><br>
 <a href="http://mapserver.gis.umn.edu/cgi-bin/wiki.pl?MapServerWiki">MapServer Wiki</a>
 </em>
 
-<p><i>Last changed: $Date$</i></p>
+<p><i>Last changed: $Date$</i>
 <HR>
-<BR><a href=index.html>Help Index</a>
+<br><a href=index.html>Help Index</a>
 </body>
 </html>

+ 15 - 15
display/d.barscale/d.barscale.html

@@ -1,32 +1,32 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
  
-<EM>d.barscale</EM> displays a barscale on the graphics monitor using either
+<em>d.barscale</em> displays a barscale on the graphics monitor using either
 the mouse or given screen coordinates. It can draw the scale in a couple of
 styles or simply draw a north arrow.
 
 
 <h2>NOTE</h2>
 
-<EM>d.barscale</EM> will not work in Lat/Lon locations as the horizontal
-scale distance changes with latitude. Try <EM>d.grid</EM> instead.
+<em>d.barscale</em> will not work in Lat/Lon locations as the horizontal
+scale distance changes with latitude. Try <em>d.grid</em> instead.
 
 <p>The -l flag will always draw a north arrow <em>and</em> a line scale
 together; it is currently not possible to draw a line scale without a north
-arrow. Instead, the -s flag can be used to draw a barscale only.</p> 
+arrow. Instead, the -s flag can be used to draw a barscale only. 
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
-<EM>
-<A HREF="d.graph.html">d.graph</A><br>
-<A HREF="d.grid.html">d.grid</A><br>
-<A HREF="d.legend.html">d.legend</A><br>
-<A HREF="d.measure.html">d.measure</A><br>
-<A HREF="d.where.html">d.where</A><br>  
-<A HREF="g.region.html">g.region</A><br>
-</EM>
+<em>
+<a href="d.graph.html">d.graph</A><br>
+<a href="d.grid.html">d.grid</A><br>
+<a href="d.legend.html">d.legend</A><br>
+<a href="d.measure.html">d.measure</A><br>
+<a href="d.where.html">d.where</A><br>  
+<a href="g.region.html">g.region</A><br>
+</em>
 
 
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
 unknown.
 
 <p>

+ 5 - 5
display/d.colorlist/d.colorlist.html

@@ -1,14 +1,14 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
-<EM>d.colorlist</EM> report the available color names.
+<em>d.colorlist</em> report the available color names.
 The list contains all available display colors with a configurable 
 separator (default is comma).
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
-<EM><A HREF="d.colors.html">d.colors</A></EM><BR>
+<em><a href="d.colors.html">d.colors</A></em><br>
 
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
 
 Andreas Lange
 

+ 41 - 41
display/d.colors/d.colors.html

@@ -1,42 +1,42 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
 A color table file associates specific colors with the categories of a
 raster map layer. The user can change these map category color assignments
 (i.e., change the map's color table) interactively, by first displaying the
 raster map to the graphics monitor and then running the program
-<EM>d.colors</EM>.
+<em>d.colors</em>.
 
-<P>
-Any color changes made using <EM>d.colors</EM> will not immediately be
+<p>
+Any color changes made using <em>d.colors</em> will not immediately be
 shown on the graphics display; however, any color changes saved will
 still alter the map's color table and will appear next time the raster
-map layer is redisplayed (see <EM><A HREF="d.colortable.html">d.colortable</A></EM>).
+map layer is redisplayed (see <em><a href="d.colortable.html">d.colortable</A></em>).
 
-<P>
+<p>
 The user must first display the relevant raster map layer to the
 active frame on the graphics monitor (e.g., using
-<EM><A HREF="d.rast.html">d.rast</A></EM>) before running
-<EM>d.colors</EM>. The user can then either enter the name of the
+<em><a href="d.rast.html">d.rast</A></em>) before running
+<em>d.colors</em>. The user can then either enter the name of the
 raster map layer whose color table is to be changed on the command
 line (e.g., by typing: <tt>d.colors map=soils</tt>), or type
 <tt>d.colors</tt> without program arguments. If the user simply types
 <tt>d.colors</tt> without program arguments on the command line,
-<EM>d.colors</EM> will ask the user to enter the name of an existing
+<em>d.colors</em> will ask the user to enter the name of an existing
 raster map layer using the standard GRASS interface.
 
-<P>
-In either case, the user is then presented with the <EM>d.colors</EM>
+<p>
+In either case, the user is then presented with the <em>d.colors</em>
 command menu, shown below.
 <!-- This menu is the same as the category and color
-changing portion of the <EM><A HREF="d.display.html">d.display</A></EM>
+changing portion of the <em><a href="d.display.html">d.display</A></em>
 menu. -->
-The <EM>d.colors</EM> commands are listed beneath the Category
+The <em>d.colors</em> commands are listed beneath the Category
 Pointer Movement, Color Modification, Replotting Screen, and Quitting
 sections below.  Commands are invoked by typing in the single-key response
 shown to the left below. (Longer descriptions of these commands appear to
 the right.) Results from invoking these commands will be reflected in the
-Category and Category Number sections of the <EM>d.colors</EM> screen. On
-the <EM>d.colors</EM> screen menu, commands appear in the right half of the
+Category and Category Number sections of the <em>d.colors</em> screen. On
+the <em>d.colors</em> screen menu, commands appear in the right half of the
 screen, and the current status of categories appears in the left half of the
 screen.
 
@@ -85,7 +85,7 @@ first and last categories. The current category is noted on the text screen
 with an arrow, and is indicated on the graphics screen by a box around the 
 current color. 
 
-<P>
+<p>
 
 Changing colors - The color associated with the current category can be 
 changed with the 
@@ -106,16 +106,16 @@ accustomed to red, yellow, and blue being the primary colors, this can
 be confusing. For starters, yellow is made by mixing red and green. The 
 intensities are listed on the text screen in as percentages. 
 
-<P>
+<p>
 
 Keys <B>I</B> and <B>i</B> increase and decrease the
 percentage change that each keystroke of one of the color
-keys (<EM>R, r, G, g, B, b</EM>) causes in its respective
+keys (<em>R, r, G, g, B, b</em>) causes in its respective
 color. The increase increment is initially set to 10%.
-Thus, pressing the <EM>R</EM> key would will increase the
+Thus, pressing the <em>R</em> key would will increase the
 red component of the current category by 10%.
 
-<P>
+<p>
 
 Highlight - The 
 <B>h</B>
@@ -129,14 +129,14 @@ described above, while in highlight mode the category colors will be
 always left showing their actual colors. Only one category is highlighted 
 at any one time. 
 
-<P>
+<p>
 
 Saving the current color table - 
 Pressing the <B>c</B> key will save the current color table as you have 
 modified it. This table will then be used next time you 
 display or paint this raster map layer. 
 
-<P>
+<p>
 
 Color table toggle - Different types of color tables are suitable for 
 different raster map layers. 
@@ -145,7 +145,7 @@ The key
 flips between the following color tables: red, green, blue color ramp; gray 
 scale; smooth changing color wave; random colors; and the saved color table. 
 
-<P>
+<p>
 
 Color table shift - The entire table is shifted up and down using the 
 <B>+</B>
@@ -153,12 +153,12 @@ and
 <B>-</B>
 keys. 
 
-<P>
+<p>
 
-Quitting the <EM>d.colors</EM> program - Pressing the
-<B>Q</B> key will cause you to quit the <EM>d.colors</EM>
+Quitting the <em>d.colors</em> program - Pressing the
+<B>Q</B> key will cause you to quit the <em>d.colors</em>
 program.  If colors have been modified but not saved,
-<EM>d.colors</EM> will ask:
+<em>d.colors</em> will ask:
 <PRE>
          Colors changed
          Save the changes? (y/n)
@@ -169,33 +169,33 @@ If the user types <B>n</B>, the program will ask:
 <PRE>
          Quit anyway? (y/n) 
 </PRE>
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 
-<P>
+<p>
 
 The map whose color table is to be altered with
-<EM>d.colors</EM> must already be on display in the active
+<em>d.colors</em> must already be on display in the active
 display frame on the graphics monitor before
-<EM>d.colors</EM> is run. This can be done using the
-command <em><A HREF="d.rast.html">d.rast</a> map=name</EM> (where <EM>name</EM> is a raster map
+<em>d.colors</em> is run. This can be done using the
+command <em><a href="d.rast.html">d.rast</a> map=name</em> (where <em>name</em> is a raster map
 layer whose color table the user wishes to alter).
 
-<P>
+<p>
 Some color monitors may not support the full range of colors required 
 to display all of the map's categories listed in the map's color table. 
 However, regardless of whether the user can see the color changes he is 
 effecting to a map's color table, any changes to a map's color table 
-made with <EM>d.colors</EM> that are saved will appear in the map's color table. 
+made with <em>d.colors</em> that are saved will appear in the map's color table. 
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
-<EM>
-<A HREF="d.colortable.html">d.colortable</A>,
-<A HREF="d.rast.html">d.rast</A>,
-<A HREF="r.colors.html">r.colors</A>
-</EM>
+<em>
+<a href="d.colortable.html">d.colortable</A>,
+<a href="d.rast.html">d.rast</A>,
+<a href="r.colors.html">r.colors</A>
+</em>
 
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
 
 James Westervelt, U.S. Army Construction Engineering 
 Research Laboratory

+ 28 - 28
display/d.colortable/d.colortable.html

@@ -1,20 +1,20 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
-The GRASS program <EM>d.colortable</EM> 
+The GRASS program <em>d.colortable</em> 
 is used to display the color table associated with a raster map layer in the 
-active frame on the graphics monitor. The <EM>map</EM> name should be 
+active frame on the graphics monitor. The <em>map</em> name should be 
 an available raster map layer in the user's current mapset search path 
 and location. 
 
-<P>
-If the <EM>values</EM> of both <EM>lines</EM> and <EM>cols</EM> are
-not specified by the user, <EM>d.colortable</EM> 
+<p>
+If the <em>values</em> of both <em>lines</em> and <em>cols</em> are
+not specified by the user, <em>d.colortable</em> 
 divides the active frame equally among the number of categories 
 present in the named raster map layer. If one option is specified, 
 the other is automatically set to accommodate all categories. 
 If both are specified, as many categories as possible are displayed. 
 
-<P>
+<p>
 If the user specifies the name of a map on the command line but does not 
 specify the values of other parameters, parameter default values will be used. 
 Alternately, if the user types simply <em>d.colortable</em> on the command line 
@@ -22,32 +22,32 @@ without any program arguments, the program will prompt the user for parameter
 settings using the standard GRASS parser interface.
 
 
-<H2>EXAMPLE</H2>
+<h2>EXAMPLE</h2>
 
 The user running the command: 
 <DL>
 <DD>
-<B>d.colortable map=</B><EM>soils</EM> 
-  <B>color=</B><EM>red</EM>
-  <B>lines=</B><EM>1</EM>
-  <B>cols=</B><EM>3</EM>
+<B>d.colortable map=</B><em>soils</em> 
+  <B>color=</B><em>red</em>
+  <B>lines=</B><em>1</em>
+  <B>cols=</B><em>3</em>
 </DL>
 would see the active graphics frame divided into three columns 
 extending the full frame height. The lines dividing the color table 
-associated with the <EM>soils</EM> map would be displayed in red. 
-The user would see, at most, only three of the colors from the <EM>soils</EM> 
+associated with the <em>soils</em> map would be displayed in red. 
+The user would see, at most, only three of the colors from the <em>soils</em> 
 color table displayed in the active frame (because the user requested 
 that this frame be divided into three sections).
 
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 
 If the user wishes to display the entire color table associated with 
 a map, the user should either stipulate a number of lines (rows) and 
 columns (cols) sufficient to accommodate the number of categories 
 in the map's color table, or fail to assign values to one or both of 
-<EM>lines</EM> and/or <EM>cols</EM>.
-If the user runs <EM>d.colortable</EM> using the default number of 
+<em>lines</em> and/or <em>cols</em>.
+If the user runs <em>d.colortable</em> using the default number of 
 lines and columns (the full graphics frame), all categories from the 
 map's color table will be displayed. However, if the user requests 
 that the color table associated with a map which has 10 data categories 
@@ -55,22 +55,22 @@ be displayed in a graphics frame with only 3 lines (rows) and 2 columns
 (a total of six cells), 
 only six of the ten map categories will be displayed. 
 
-<P>
+<p>
 The user should run the GRASS program 
-<EM><A HREF="d.erase.html">d.erase</A></EM> between 
-runs of <EM>d.colortable</EM> to avoid confusion. 
+<em><a href="d.erase.html">d.erase</A></em> between 
+runs of <em>d.colortable</em> to avoid confusion. 
 
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
-<EM>
-<A HREF="d.colors.html">d.colors</A><br>
-<A HREF="d.erase.html">d.erase</A><br>
-<A HREF="d.legend.html">d.legend</A><br>
-<A HREF="d.rast.html">d.rast</A>
-</EM>
+<em>
+<a href="d.colors.html">d.colors</A><br>
+<a href="d.erase.html">d.erase</A><br>
+<a href="d.legend.html">d.legend</A><br>
+<a href="d.rast.html">d.rast</A>
+</em>
 
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
 
 James Westervelt, U.S. Army Construction Engineering Research Laboratory
 

+ 2 - 2
display/d.extract/d.extract.html

@@ -16,10 +16,10 @@ d.extract input=roads output=interstate
 
 <h2>SEE ALSO</h2>
 
-<em><a HREF="v.extract.html">v.extract</a></em>
+<em><a href="v.extract.html">v.extract</a></em>
 
 <h2>AUTHOR</h2>
 
 Radim Blazek, Markus Neteler
 
-<p><i>Last changed: $Date$</i></p>
+<p><i>Last changed: $Date$</i>

+ 38 - 38
display/d.font/d.font.html

@@ -1,16 +1,16 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
 
-<EM>d.font</EM> allows the user to select use of a specific text font for 
+<em>d.font</em> allows the user to select use of a specific text font for 
 display of text on the graphics monitor. 
 The GRASS program 
-<EM><A HREF="../html/show.fonts.sh.html">show.fonts.sh</A></EM>
+<em><a href="../html/show.fonts.sh.html">show.fonts.sh</A></em>
 is a UNIX Bourne shell macro which 
-names and displays the fonts that can be selected using <EM>d.font</EM>.
+names and displays the fonts that can be selected using <em>d.font</em>.
 If the user does not specify a font when using other GRASS programs 
-that display text, the font type <EM>romans</EM> is used by default. 
+that display text, the font type <em>romans</em> is used by default. 
 
-<P>
+<p>
 The user can run this program either non-interactively or interactively. 
 If the user specifies a font type name on the command line the program will 
 run non-interactively. 
@@ -18,54 +18,54 @@ Alternately, the user can simply type <B>d.font</B> on the command line;
 in this case, the program will prompt the user for a display 
 text font type.
 
-<P>
+<p>
 <B>Parameter:</B> 
 <DL>
-<DT><B>font=</B><EM>name</EM>
+<DT><B>font=</B><em>name</em>
 <DD>Name of a font type, from among the font types italicized below. 
-<BR>
-Default: <EM>romans</EM> 
-<BR>
+<br>
+Default: <em>romans</em> 
+<br>
 Options: (italized) 
-<BR><EM>cyrilc</EM> Cyrillic 
-<BR><EM>gothgbt</EM> Gothic Great Britain triplex 
-<BR><EM>gothgrt</EM> Gothic German triplex 
-<BR><EM>gothitt</EM> Gothic Italian triplex 
-<BR><EM>greekc</EM> Greek complex 
-<BR><EM>greekcs</EM> Greek complex script 
-<BR><EM>greekp</EM> Greek plain 
-<BR><EM>greeks</EM> Greek simplex 
-<BR><EM>italicc</EM> Italian complex 
-<BR><EM>italiccs</EM> Italian complex small 
-<BR><EM>italict</EM> Italian triplex 
-<BR><EM>romanc</EM> Roman complex 
-<BR><EM>romancs</EM> Roman complex small 
-<BR><EM>romand</EM> Roman duplex 
-<BR><EM>romanp</EM> Roman plain 
-<BR><EM>romans</EM> Roman simplex 
-<BR><EM>romant</EM> Roman triplex 
-<BR><EM>scriptc</EM> Script complex 
-<BR><EM>scripts</EM> Script simplex 
+<br><em>cyrilc</em> Cyrillic 
+<br><em>gothgbt</em> Gothic Great Britain triplex 
+<br><em>gothgrt</em> Gothic German triplex 
+<br><em>gothitt</em> Gothic Italian triplex 
+<br><em>greekc</em> Greek complex 
+<br><em>greekcs</em> Greek complex script 
+<br><em>greekp</em> Greek plain 
+<br><em>greeks</em> Greek simplex 
+<br><em>italicc</em> Italian complex 
+<br><em>italiccs</em> Italian complex small 
+<br><em>italict</em> Italian triplex 
+<br><em>romanc</em> Roman complex 
+<br><em>romancs</em> Roman complex small 
+<br><em>romand</em> Roman duplex 
+<br><em>romanp</em> Roman plain 
+<br><em>romans</em> Roman simplex 
+<br><em>romant</em> Roman triplex 
+<br><em>scriptc</em> Script complex 
+<br><em>scripts</em> Script simplex 
 </DL>
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 
 The font type 
-<EM>romans</EM>
+<em>romans</em>
 is the fastest font type to display to the graphics monitor. 
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
-<EM><A HREF="d.text.html">d.text</A></EM><br>
-<EM><A HREF="d.title.html">d.title</A></EM>
+<em><a href="d.text.html">d.text</A></em><br>
+<em><a href="d.title.html">d.title</A></em>
 
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
 
 James Westervelt, U.S. Army Construction Engineering 
 Research Laboratory
 
-<P>
-<EM>d.font</EM> uses the public domain version of the Hershey Fonts created 
+<p>
+<em>d.font</em> uses the public domain version of the Hershey Fonts created 
 by Dr. A.V. Hershey while working at the U.S. National Bureau of 
 Standards.
 

+ 6 - 6
display/d.fontlist/d.fontlist.html

@@ -1,14 +1,14 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
-<EM>d.fontlist</EM> outputs a list of available fonts for use with
+<em>d.fontlist</em> outputs a list of available fonts for use with
 GRASS display commands.
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
-<EM><A HREF="d.text.html">d.text</A></EM><br>
-<EM><A HREF="parser.html">parser</A></EM>
+<em><a href="d.text.html">d.text</A></em><br>
+<em><a href="parser.html">parser</A></em>
 
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
 
 Glynn Clements
 

+ 10 - 10
display/d.geodesic/d.geodesic.html

@@ -1,12 +1,12 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
-<EM>d.geodesic</EM> displays a geodesic line in the active frame on the user's 
+<em>d.geodesic</em> displays a geodesic line in the active frame on the user's 
 graphics monitor. This is also known as the great circle line and traces the 
 shortest distance between two user-specified points on the curved surface of 
 a longitude/latitude data set. The two coordinate locations named must fall 
 within the boundaries of the user's current geographic region. 
 
-<H2>OPTIONS</H2>
+<h2>OPTIONS</h2>
 
 This program can be run either interactively or non-interactively. 
 If the user types <B>d.geodesic</B> on the command line and runs it without other program 
@@ -15,12 +15,12 @@ the mouse to indicate the starting and ending points of each geodesic line
 to be drawn. The default line color (black) and text color (red) 
 will be used. 
 
-<P>
+<p>
 Alternately, the user can specify the starting and ending coordinates 
 of the geodesic, line color, and text color on the command line, 
 and run the program non-interactively. 
 
-<P>
+<p>
 Once the user indicates the starting and ending coordinates 
 of the geodesic, the line and its length (in miles) are displayed to 
 the user's graphics monitor. If the text color is set to <em>none</em>,
@@ -37,20 +37,20 @@ d.geodesic coor=55:58W,33:18S,26:43E,60:37N lcolor=yellow tcolor=red
 
 <p>
 <center>
-<img src="d_geodesic.png" border=1><BR>
+<img src="d_geodesic.png" border=1><br>
 <i>Geodesic line (great circle line)</i>
 </center>
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 
 This program works only with GRASS locations using a longitude/latitude 
 coordinate system. 
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
-<EM><A HREF="d.rhumbline.html">d.rhumbline</A></EM>
+<em><a href="d.rhumbline.html">d.rhumbline</A></em>
 
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
 
 Michael Shapiro, U.S. Army Construction Engineering Research Laboratory
 

+ 86 - 86
display/d.graph/d.graph.html

@@ -1,35 +1,35 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
-<EM>d.graph</EM>
+<em>d.graph</em>
 draws graphics that are described either from standard input (default), 
 or within a file (if an <b>input</b> file name is identified on the 
 command line). If graphics commands are entered from standard input, 
-a <EM>CTRL-d</EM> is used to signal the end of input to <EM>d.graph</EM>.
+a <em>CTRL-d</em> is used to signal the end of input to <em>d.graph</em>.
 Coordinates are given either as a percentage of frame height and width
 (default) or in geographic coordinates (with the <B>-m</B> flag).
-<P>
+<p>
 
 The program can be run interactively or non-interactively. 
 The user can run the program completely non-interactively 
 by specifying the name of a graphics file containing the 
-<EM>d.graph</EM> graphics commands. If run non-interactively the
-<EM>d.graph</EM> command is saved to the display's dedraw history.
+<em>d.graph</em> graphics commands. If run non-interactively the
+<em>d.graph</em> command is saved to the display's dedraw history.
 
 The user can also elect to run the program partially interactively, 
-by specifying any/all of the parameters <EM>except</EM> 
-the graphics file <B>input=</B><EM>name</EM> parameter on the command line. 
-In this case, <EM>d.graph</EM> will expect the user to input <EM>d.graph</EM> 
+by specifying any/all of the parameters <em>except</em> 
+the graphics file <B>input=</B><em>name</em> parameter on the command line. 
+In this case, <em>d.graph</em> will expect the user to input <em>d.graph</em> 
 graphics commands from standard input (i.e., the keyboard) and 
 will (silently) prompt the user for these graphics commands. 
 
-<P>
+<p>
 Alternately, the user can simply type <B>d.graph</B> on the command line, 
 and be prompted for the values of all parameters<!-- (the user can still 
 input graphics commands from either an input file or standard input 
 using this form)-->. In this case, the user is presented with the standard 
 GRASS GUI interface.
 
-<P>
+<p>
 The default coordinate system used is 0-100 percent of the active frame 
 in x and similarly 0-100 in y,
 regardless of the graphics monitor display frame size and aspect. 
@@ -38,11 +38,11 @@ monitor display frame. All values may be floating point.
 If the <B>-m</B> flag is given, geographic coordinates will be used instead.
 
 
-<H2>COMMANDS</H2>
+<h2>COMMANDS</h2>
 
-<P>
+<p>
 The graphics language is simple, and uses the following commands: 
-<BR>
+<br>
 <DL>
 <DD>[
 <a href="#comment">#</a>&nbsp;|
@@ -62,117 +62,117 @@ The graphics language is simple, and uses the following commands:
 
 
 <DL>
-<DT><a name="comment"></a><B>#</B> <EM>comment</EM> 
+<DT><a name="comment"></a><B>#</B> <em>comment</em> 
 <DD>A line of comment which is ignored in the processing. 
 
-<DT><a name="move"></a><B>move</B> <EM>xpos ypos</EM> 
-<DD>The current location is updated to <EM>xpos ypos</EM>. 
+<DT><a name="move"></a><B>move</B> <em>xpos ypos</em> 
+<DD>The current location is updated to <em>xpos ypos</em>. 
 
 Unless the <B>-m</B> flag is used,
 values are stated as a percent of the active display frame's 
-horizontal (<EM>xpos</EM>) and vertical (<EM>ypos</EM>) size, 
+horizontal (<em>xpos</em>) and vertical (<em>ypos</em>) size, 
 and may be floating point values. Values are between 0-100. 
-<B>Note.</B> A space must separate <EM>xpos</EM> and <EM>ypos</EM>.
+<B>Note.</B> A space must separate <em>xpos</em> and <em>ypos</em>.
 
-<DT><a name="draw"></a><B>draw</B> <EM>xpos ypos</EM> 
+<DT><a name="draw"></a><B>draw</B> <em>xpos ypos</em> 
 <DD>A line is drawn in the current color from the current location to the new 
-location <EM>xpos ypos</EM>, which then becomes the current location. 
+location <em>xpos ypos</em>, which then becomes the current location. 
 Unless the <B>-m</B> flag is used,
 values are stated as a percent of the active display frame's 
-horizontal (<EM>xpos</EM>) and vertical (<EM>ypos</EM>) size, 
+horizontal (<em>xpos</em>) and vertical (<em>ypos</em>) size, 
 and may be floating point values. Values are between 0-100. 
-<B>Note.</B> A space must separate <EM>xpos</EM> and <EM>ypos</EM>. 
+<B>Note.</B> A space must separate <em>xpos</em> and <em>ypos</em>. 
 
 <DT><a name="polygon"></a><B>polygon</B> 
-<BR>&nbsp;&nbsp;<EM> xpos ypos</EM> 
-<BR>&nbsp;&nbsp;<EM> xpos ypos</EM> 
-<BR>&nbsp;&nbsp;... 
+<br>&nbsp;&nbsp;<em> xpos ypos</em> 
+<br>&nbsp;&nbsp;<em> xpos ypos</em> 
+<br>&nbsp;&nbsp;... 
 
-<DD>The coordinates appearing beneath the word <EM>polygon</EM>, 
+<DD>The coordinates appearing beneath the word <em>polygon</em>, 
 one pair per line, 
 circumscribe a polygon that is to be filled with the current color. 
 
 <DT><a name="polyline"></a><B>polyline</B> 
-<BR>&nbsp;&nbsp;<EM> xpos ypos</EM> 
-<BR>&nbsp;&nbsp;<EM> xpos ypos</EM> 
-<BR>&nbsp;&nbsp;... 
+<br>&nbsp;&nbsp;<em> xpos ypos</em> 
+<br>&nbsp;&nbsp;<em> xpos ypos</em> 
+<br>&nbsp;&nbsp;... 
 
-<DD>The coordinates appearing beneath the word <EM>polyline</EM>, 
+<DD>The coordinates appearing beneath the word <em>polyline</em>, 
 one pair per line, 
 circumscribe a polygon that is not to be filled with color. 
 
-<DT><a name="color"></a><B>color</B> <EM>color</EM> 
+<DT><a name="color"></a><B>color</B> <em>color</em> 
 <DD>Sets the current color to that stated; subsequent graphics will be drawn 
 in the stated color, until the current color is set to a different color. 
-Options are <EM>red</EM>, 
-<EM>orange</EM>,
-<EM>yellow</EM>,
-<EM>green</EM>,
-<EM>blue</EM>,
-<EM>indigo</EM>,
-<EM>violet</EM>,
-<EM>brown</EM>,
-<EM>magenta</EM>,
-<EM>gray</EM>,
-<EM>white</EM>,
-<EM>black</EM>,
+Options are <em>red</em>, 
+<em>orange</em>,
+<em>yellow</em>,
+<em>green</em>,
+<em>blue</em>,
+<em>indigo</em>,
+<em>violet</em>,
+<em>brown</em>,
+<em>magenta</em>,
+<em>gray</em>,
+<em>white</em>,
+<em>black</em>,
 an R:G:B triplet (separated by colons),
 or the word "none" (draws in the default background color).
 
-<DT><a name="text"></a><B>text</B> <EM>line-of-text</EM> 
+<DT><a name="text"></a><B>text</B> <em>line-of-text</em> 
 <DD>The stated text is drawn at the current location using the current color, 
 and the new current location is then positioned at the end of the text string. 
 
 <a name="size"></a>
-<DT><B>size</B> <EM>xper yper</EM> 
+<DT><B>size</B> <em>xper yper</em> 
 <DD>Subsequent text will be drawn such that the text is 
-<EM>xper</EM> percent of the graphics monitor display frame wide and 
-<EM>yper</EM> percent of the frame high. By default, the text size is set to
+<em>xper</em> percent of the graphics monitor display frame wide and 
+<em>yper</em> percent of the frame high. By default, the text size is set to
 5 percent of the active frame's width and 5 percent of the frame's height.
 If only one value is given, then that value will be used for both x and y 
 scaling.
-<BR>
-<B>Note.</B> A space must separate <EM>xper</EM> and <EM>yper</EM>.
+<br>
+<B>Note.</B> A space must separate <em>xper</em> and <em>yper</em>.
 
-<DT><a name="symbol"></a><B>symbol</B> <EM>type size xper yper [line_color [fill_color]]</EM>
+<DT><a name="symbol"></a><B>symbol</B> <em>type size xper yper [line_color [fill_color]]</em>
 <DD>A symbol is drawn at the given size on the display monitor. The
-<EM>xper</EM> and <EM>yper</EM> options define the center of the icon and
+<em>xper</em> and <em>yper</em> options define the center of the icon and
 are given as a percentage of the display frame (<tt>0,0</tt> is lower left).
 The symbol can be any of those stored in <tt>$GISBASE/etc/symbol/</tt>
 (e.g. <i>basic/circle</i>) or stored in the user's mapset directory in the
 form <tt>$MAPSET/symbol/</tt><em>type/name</em>.
 The colors may be either a standard color name, an R:G:B triplet,
 or "none". If using an R:G:B triplet, each color value can range from 0-255.
-If not specified the default <EM>line_color</EM> is black and the default 
-<EM>fill_color</EM> is grey.
+If not specified the default <em>line_color</em> is black and the default 
+<em>fill_color</em> is grey.
 
-<DT><a name="rotation"></a><B>rotation</B> <EM>angle</EM> 
+<DT><a name="rotation"></a><B>rotation</B> <em>angle</em> 
 <DD>Subsequent text and symbols will be drawn such that they are rotated 
 <em>angle</em> degrees counter-clockwise from east.
 
-<DT><a name="icon"></a><B>icon</B> <EM>type size x y</EM> 
-<DD>Draws an icon of types <EM>o</EM>, <EM>x</EM>, or <EM>+</EM> 
-with specified <EM>size</EM> (in %) at location <EM>x,y</EM>. 
-Note: type <EM>o</EM> designates a square.
-<BR>
+<DT><a name="icon"></a><B>icon</B> <em>type size x y</em> 
+<DD>Draws an icon of types <em>o</em>, <em>x</em>, or <em>+</em> 
+with specified <em>size</em> (in %) at location <em>x,y</em>. 
+Note: type <em>o</em> designates a square.
+<br>
 
-<DT><a name="width"></a><B>width</B> <EM>value</EM> 
+<DT><a name="width"></a><B>width</B> <em>value</em> 
 <DD>Subsequent lines (including non-FreeType text) will be drawn with
 the given pixel thickness.
-<BR>The default value is 0.
+<br>The default value is 0.
 
 </DL>
 
-<H2>EXAMPLES</H2>
+<h2>EXAMPLES</h2>
 
-For an example use of <EM>d.graph</EM>, examine the contents of the  
-command file <EM><a href="grass_logo.txt">grass_logo.txt</a></EM>
-located in the <EM>d.graph</EM> source code directory. It will draw the
-CERL GRASS logo using the <EM>d.graph</EM> graphing commands stored in the file. 
-Note that the coordinates in the <EM><a href="grass_logo.txt">grass_logo.txt</a></EM> file were 
+For an example use of <em>d.graph</em>, examine the contents of the  
+command file <em><a href="grass_logo.txt">grass_logo.txt</a></em>
+located in the <em>d.graph</em> source code directory. It will draw the
+CERL GRASS logo using the <em>d.graph</em> graphing commands stored in the file. 
+Note that the coordinates in the <em><a href="grass_logo.txt">grass_logo.txt</a></em> file were 
 taken directly off an image drawn by hand on graph paper. 
 <!-- formerly names "grass.logo.sh" in GRASS 5 code. -->
-<P>
+<p>
 A dynamic example can be found in the <em>d.polar</em> shell script.
 
 
@@ -204,34 +204,34 @@ EOF
 </pre></div>
 
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 
-<EM>d.graph</EM> remembers the last screen location (<EM>xpos ypos</EM>) to which 
+<em>d.graph</em> remembers the last screen location (<em>xpos ypos</em>) to which 
 the user moved, even after the user erases the display frame. 
-If the user runs <EM>d.graph</EM> repeatedly, and wishes to start anew with 
-the default (xpos ypos) screen location, the user should <EM>clear</EM> the 
-display frame between runs of <EM>d.graph</EM>.
+If the user runs <em>d.graph</em> repeatedly, and wishes to start anew with 
+the default (xpos ypos) screen location, the user should <em>clear</em> the 
+display frame between runs of <em>d.graph</em>.
 
-<H2>LIMITATIONS</H2>
+<h2>LIMITATIONS</h2>
 
 There are no automated ways of generating graphic images. It is anticipated 
 that GRASS user sites will write programs to convert output from a resident 
-graphics editor into GRASS <EM>d.graph</EM> format.
+graphics editor into GRASS <em>d.graph</em> format.
 (e.g. EPS -> <em>d.graph</em>, perhaps with the help of a
 <a href="http://www.pstoedit.net/">pstoedit</a> plugin)
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
-<EM><A HREF="d.font.html">d.font</A></EM><br>
-<EM><A HREF="d.frame.html">d.frame</A></EM><br>
-<EM><A HREF="d.labels.html">d.labels</A></EM><br>
-<!-- <EM><A HREF="d.mapgraph.html">d.mapgraph</A></EM><br> superseded by -m -->
-<EM><A HREF="d.polar.html">d.polar</A></EM><br>
-<EM><A HREF="d.text.html">d.text</A></EM><br>
-<EM><A HREF="d.where.html">d.where</A></EM><br>
-<!-- <EM><A HREF="grass.logo.sh.html">grass.logo.sh</A></EM><br> -->
+<em><a href="d.font.html">d.font</A></em><br>
+<em><a href="d.frame.html">d.frame</A></em><br>
+<em><a href="d.labels.html">d.labels</A></em><br>
+<!-- <em><a href="d.mapgraph.html">d.mapgraph</A></em><br> superseded by -m -->
+<em><a href="d.polar.html">d.polar</A></em><br>
+<em><a href="d.text.html">d.text</A></em><br>
+<em><a href="d.where.html">d.where</A></em><br>
+<!-- <em><a href="grass.logo.sh.html">grass.logo.sh</A></em><br> -->
 
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
 
 James Westervelt, U.S. Army Construction Engineering Research Laboratory
 <br><i>Last changed: $Date$</i>

+ 34 - 34
display/d.grid/d.grid.html

@@ -1,55 +1,55 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
-<EM>d.grid</EM> overlays a grid of user-defined size and
+<em>d.grid</em> overlays a grid of user-defined size and
 color in the active display frame on the graphics monitor.
 The grid can be created as a standard rectangular grid or
 a geographic grid. The grid will overlay, not overwrite,
 the contents of the active display frame.
 
-<P>
+<p>
 
-<EM>d.grid</EM> can be run non-interactively or
+<em>d.grid</em> can be run non-interactively or
 interactively.  If the user specifies the grid
-<EM>size</EM> and (optionally) the grid <EM>color</EM> on
+<em>size</em> and (optionally) the grid <em>color</em> on
 the command line the program will run non-interactively; if
-no grid <EM>color</EM> is given the default will be used.
+no grid <em>color</em> is given the default will be used.
 Alternately, the user may simply type <B>d.grid</B> on the
 command line; in this case, the program will prompt the
 user for parameter values using the standard GRASS graphical 
 user interface.
 
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 
-<EM>d.grid</EM> will not erase grids already displayed in
+<em>d.grid</em> will not erase grids already displayed in
 the active graphics display frame by previous invocations
-of <EM>d.grid</EM>; multiple invocations of <EM>d.grid</EM>
+of <em>d.grid</em>; multiple invocations of <em>d.grid</em>
 will therefore result in the drawing of multiple grids
 inside the active graphics frame.  (A command like 
-<EM><A HREF="d.erase.html">d.erase</A></EM>, which erases the
+<em><a href="d.erase.html">d.erase</A></em>, which erases the
 entire contents of the active display frame, must be run to
 erase previously drawn grids from the display frame.)
 
-<P>
+<p>
 If the user provides a 
-<EM>-g</EM> flag a geographic (projected) grid 
-will be drawn. With the <EM>-g</EM> flag the <EM>size</EM> 
+<em>-g</em> flag a geographic (projected) grid 
+will be drawn. With the <em>-g</em> flag the <em>size</em> 
 argument accepts both decimal degrees and colon separated 
 ddd:mm:ss coordinates (eg. <tt>00:30:00</tt> for half of a degree).
 
 <p>
-A geographic grid cannot be drawn for a <EM>latitude/longitude</EM> 
-or <EM>XY</EM> projection.
+A geographic grid cannot be drawn for a <em>latitude/longitude</em> 
+or <em>XY</em> projection.
 <p>
 Colors may be standard named GRASS colors (red, green, aqua, etc.) or
-a numerical R:G:B triplet, where component values range from 0-255.<BR>
+a numerical R:G:B triplet, where component values range from 0-255.<br>
 <p>
-The grid drawing may be turned off by using the <em>-n</em> flag.<BR>
-The border drawing may be turned off by using the <em>-b</em> flag.<BR>
-The coordinate text may be turned off by using the <em>-t</em> flag.<BR>
+The grid drawing may be turned off by using the <em>-n</em> flag.<br>
+The border drawing may be turned off by using the <em>-b</em> flag.<br>
+The coordinate text may be turned off by using the <em>-t</em> flag.<br>
 
 
-<H2>EXAMPLES</H2>
+<h2>EXAMPLES</h2>
 To draw a red geographic grid with 30 minute grid spacing run 
 either of the following:
 <PRE>
@@ -63,25 +63,25 @@ To draw a blue standard rectangular grid at a 500 (meter) spacing run the follow
 <PRE>
   d.grid size=500 color=blue
 </PRE>
-<BR>
+<br>
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
-<EM><A HREF="d.barscale.html">d.barscale</A></EM><br>
-<EM><A HREF="d.legend.html">d.legend</A></EM><br>
-<EM><A HREF="d.geodesic.html">d.geodesic</A></EM><br>
-<EM><A HREF="d.rhumbline.html">d.rhumbline</A></EM><br>
-<EM><A HREF="d.erase.html">d.erase</A></EM><br>
-<EM><A HREF="d.frame.html">d.frame</A></EM><br>
-<EM><A HREF="d.rast.html">d.rast</A></EM><br>
+<em><a href="d.barscale.html">d.barscale</A></em><br>
+<em><a href="d.legend.html">d.legend</A></em><br>
+<em><a href="d.geodesic.html">d.geodesic</A></em><br>
+<em><a href="d.rhumbline.html">d.rhumbline</A></em><br>
+<em><a href="d.erase.html">d.erase</A></em><br>
+<em><a href="d.frame.html">d.frame</A></em><br>
+<em><a href="d.rast.html">d.rast</A></em><br>
 
 
 
-<H2>AUTHORS</H2>
+<h2>AUTHORS</h2>
 
-James Westervelt, U.S. Army Construction Engineering Research Laboratory<BR>
-Geogrid support: Bob Covill<BR>
-Border support: Markus Neteler<BR>
-Text and RGB support: Hamish Bowman<BR>
+James Westervelt, U.S. Army Construction Engineering Research Laboratory<br>
+Geogrid support: Bob Covill<br>
+Border support: Markus Neteler<br>
+Text and RGB support: Hamish Bowman<br>
 
 <p><i>Last changed: $Date$</i>

+ 46 - 46
display/d.his/d.his.html

@@ -1,25 +1,25 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
-<EM>his</EM> stands for hue, intensity, and saturation.
+<em>his</em> stands for hue, intensity, and saturation.
 This program produces a raster map layer providing a
 visually pleasing combination of hue, intensity, and
 saturation values from two or three user-specified raster
 map layers.
 
-<P>
+<p>
 
 The human brain automatically interprets the vast amount of
 visual information available according to basic rules. 
-Color, or <EM>hue</EM>, is used to categorize objects. 
-Shading, or <EM>intensity</EM>, is interpreted as
+Color, or <em>hue</em>, is used to categorize objects. 
+Shading, or <em>intensity</em>, is interpreted as
 three-dimensional texturing. Finally, the degree of
-haziness, or <EM>saturation</EM>, is associated with
+haziness, or <em>saturation</em>, is associated with
 distance or depth. This program allows data from up to
 three raster map layers to be combined into an image which
-retains the original information in terms of <EM>hue</EM>,
-<EM>intensity</EM>, and <EM>saturation</EM>.
+retains the original information in terms of <em>hue</em>,
+<em>intensity</em>, and <em>saturation</em>.
 
-<H2>OPTIONS</H2>
+<h2>OPTIONS</h2>
 
 This program can be run non-interactively or
 interactively.  It will run non-interactively if the user
@@ -30,7 +30,7 @@ saturation values (<B>s_map</B>).  The resulting image will
 be displayed in the active display frame on the graphics
 monitor.
 
-<P>
+<p>
 
 Alternately, the user can run the program interactively by
 typing <B>d.his</B> without naming parameter values on the
@@ -38,7 +38,7 @@ command line.  In this case, the program will prompt the
 user for parameter values using the standard GRASS 
 GUI interface.
 
-<P>
+<p>
 
 While any raster map layer can be used to represent the hue
 information, map layers with a few very distinct colors
@@ -47,42 +47,42 @@ continuously varying data like elevation, aspect, weights,
 intensities, or amounts can suitably be used to provide
 intensity and saturation information.
 
-<P>
+<p>
 
 For example, a visually pleasing image can be
-made by using a watershed map for the <EM>hue</EM> factor,
-an aspect map for the <EM>intensity</EM> factor, and an
-elevation map for <EM>saturation</EM>.  (The user may wish
+made by using a watershed map for the <em>hue</em> factor,
+an aspect map for the <em>intensity</em> factor, and an
+elevation map for <em>saturation</em>.  (The user may wish
 to leave out the elevation information for a first try.)
 Ideally, the resulting image should resemble the view from
 an aircraft looking at a terrain on a sunny day with a bit
 of haze in the valleys.
 
-<P>
+<p>
 The <b>brighten</b> option does not truly represent a percentage,
 but calling it that makes the option easy to understand, and it
 sounds better than <i>Normalized Scaling Factor</i>.
 
 
-<H2>THE PROCESS</H2>
+<h2>THE PROCESS</h2>
 
 Each map cell is processed individually. First, the working
 color is set to the color of the corresponding cell in the
-map layer chosen to represent <EM>HUE</EM>.  Second, this
-color is multiplied by the <EM>red</EM> intensity of that
-cell in the <EM>INTENSITY</EM> map layer.  This map layer
+map layer chosen to represent <em>HUE</em>.  Second, this
+color is multiplied by the <em>red</em> intensity of that
+cell in the <em>INTENSITY</em> map layer.  This map layer
 should have an appropriate gray-scale color table
 associated with it. You can ensure this by using the color
 manipulation capabilities of
-<EM><A HREF="d.colors.html">d.colors</A></EM> or
-<EM><A HREF="r.colors.html">r.colors</A></EM>.
+<em><a href="d.colors.html">d.colors</A></em> or
+<em><a href="r.colors.html">r.colors</A></em>.
 
 Finally, the color is made somewhat gray-based on the
-<EM>red</EM> intensity of that cell in the
-<EM>SATURATION</EM> map layer.  Again, this map layer
+<em>red</em> intensity of that cell in the
+<em>SATURATION</em> map layer.  Again, this map layer
 should have a gray-scale color table associated with it.
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 
 The name is misleading. The actual conversion used is
 
@@ -98,20 +98,20 @@ where
 
 </PRE>
 
-<P>
+<p>
 
 Either (but not both) of the intensity or the saturation
 map layers may be omitted. This means that it is possible
 to produce output images that represent combinations of
-<EM>his, hi,</EM> or <EM>hs</EM>.
+<em>his, hi,</em> or <em>hs</em>.
 
-<P>
+<p>
 Users wishing to store the result in new raster map layers
 instead of displaying it on the monitor should use the
-program <EM><A HREF="r.his.html">r.his</A></EM>.
+program <em><a href="r.his.html">r.his</A></em>.
 
 
-<H2>EXAMPLE</H2>
+<h2>EXAMPLE</h2>
 <h3>Spearfish dataset</h3>
 
 <div class="code"><pre>
@@ -120,22 +120,22 @@ program <EM><A HREF="r.his.html">r.his</A></EM>.
   d.mon x1
   d.his h=elevation.dem i=elev.shad_relf brighten=50
 </pre></div>
-<BR>
-
-<H2>SEE ALSO</H2>
-
-<EM>
-<A HREF="d.colors.html">d.colors</A>,
-<A HREF="d.colortable.html">d.colortable</A>,
-<A HREF="d.frame.html">d.frame</A>,
-<A HREF="d.rgb.html">d.rgb</A>,
-<A HREF="r.colors.html">r.colors</A>,
-<A HREF="r.his.html">r.his</A>,
-<A HREF="i.his.rgb.html">i.his.rgb</A>,
-<A HREF="i.rgb.his.html">i.rgb.his</A>
-</EM>
-
-<H2>AUTHOR</H2>
+<br>
+
+<h2>SEE ALSO</h2>
+
+<em>
+<a href="d.colors.html">d.colors</A>,
+<a href="d.colortable.html">d.colortable</A>,
+<a href="d.frame.html">d.frame</A>,
+<a href="d.rgb.html">d.rgb</A>,
+<a href="r.colors.html">r.colors</A>,
+<a href="r.his.html">r.his</A>,
+<a href="i.his.rgb.html">i.his.rgb</A>,
+<a href="i.rgb.his.html">i.rgb.his</A>
+</em>
+
+<h2>AUTHOR</h2>
 
 James Westervelt, U.S. Army Construction Engineering Research Laboratory
 

+ 12 - 12
display/d.histogram/d.histogram.html

@@ -1,22 +1,22 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
-<EM>d.histogram</EM> displays the category-value distribution for a
+<em>d.histogram</em> displays the category-value distribution for a
 user-specified raster map layer, in the form of a bar chart or a pie chart. 
 The display will be displayed in the active display frame on the graphics
 monitor, using the colors in the raster map layer's color table.  The
 program determines the raster map's category value distribution by counting
 cells.
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 
-<EM>d.histogram</EM> respects the current geographic region settings 
+<em>d.histogram</em> respects the current geographic region settings 
 and the current MASK (if one exists). 
 
-<P>
-<EM>d.histogram</EM> uses the colors in the map's color look-up table
-(i.e., the map's <EM>colr</EM> or <EM>colr2</EM> file).
+<p>
+<em>d.histogram</em> uses the colors in the map's color look-up table
+(i.e., the map's <em>colr</em> or <em>colr2</em> file).
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
 <em>
 <a href="d.colors.html">d.colors</a>,
@@ -29,12 +29,12 @@ and the current MASK (if one exists).
 <a href="r.stats.html">r.stats</a>
 </em>
 
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
 
 Dave Johnson
-<BR> DBA Systems, Inc. 
-<BR> 10560 Arrowhead Drive 
-<BR> Fairfax, Virginia 22030
+<br> DBA Systems, Inc. 
+<br> 10560 Arrowhead Drive 
+<br> Fairfax, Virginia 22030
 
 <p>
 <i>Last changed: $Date$</i>

+ 9 - 9
display/d.info/d.info.html

@@ -2,22 +2,22 @@
 
 <em>d.info</em> displays information about the active display monitor.
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 
 Units are screen pixels (except for <em>-g</em> flag where map units
-are used).<BR>
-Where two numbers are given the format is: width, height.<BR>
+are used).<br>
+Where two numbers are given the format is: width, height.<br>
 Where four numbers are given the format is: left, right, top, bottom.
-<BR><BR>
+<br><br>
 Note: GRASS display pixel coordinates are measured from the top left.
-<P>
-<BR>
+<p>
+<br>
 
 <h2>SEE ALSO</h2>
 
-<em><a HREF="d.frame.html">d.frame</a></em><br>
-<em><a HREF="d.vect.html">d.vect</a></em><br>
-<em><a HREF="d.rast.html">d.rast</a></em><br>
+<em><a href="d.frame.html">d.frame</a></em><br>
+<em><a href="d.vect.html">d.vect</a></em><br>
+<em><a href="d.rast.html">d.rast</a></em><br>
 
 <h2>AUTHOR</h2>
 

+ 15 - 15
display/d.labels/d.labels.html

@@ -1,39 +1,39 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
-<EM>d.labels</EM> displays a <EM>paint</EM> label file in the 
+<em>d.labels</em> displays a <em>paint</em> label file in the 
 active display frame on the graphics monitor. Each label has components 
 which determine the text, the location of the text on the image, its 
 size, and the background for the text. This file can be generated with 
-the <EM><A HREF="v.label.html">v.label</A></EM> program or simply created 
+the <em><a href="v.label.html">v.label</A></em> program or simply created 
 by the user as an ASCII file (using a text editor) and placed in the 
 appropriate directory under the user's current mapset and location 
 (i.e. <tt>$MAPSET/paint/labels/</tt>).
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 
 Some of the information stored in the label file is unused by 
-<EM>d.labels</EM>.
+<em>d.labels</em>.
 <!-- The unused information found in a label file is printed to standard 
 output. -->
 This extra information is used by such programs as 
-<EM><A HREF="ps.map.html">ps.map</A></EM>.
+<em><a href="ps.map.html">ps.map</A></em>.
 
-<P>
+<p>
 This module was formerly known as <em>d.paint.labels</em>.
 The the old version of <em>d.labels</em> from GRASS 5, which provided
 interactive placement and modification of paint labels, still needs to 
 have its functionality merged into this module.
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
-<EM><A HREF="d.font.html">d.font</A></EM><br>
-<EM><A HREF="d.text.html">d.text</A></EM><br>
-<EM><A HREF="d.title.html">d.title</A></EM><br>
-<EM><A HREF="ps.map.html">ps.map</A></EM><br>
-<EM><A HREF="v.label.html">v.label</A></EM>
-<BR>
+<em><a href="d.font.html">d.font</A></em><br>
+<em><a href="d.text.html">d.text</A></em><br>
+<em><a href="d.title.html">d.title</A></em><br>
+<em><a href="ps.map.html">ps.map</A></em><br>
+<em><a href="v.label.html">v.label</A></em>
+<br>
 
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
 
 James Westervelt, 
 U.S. Army Construction Engineering 

+ 33 - 33
display/d.legend/d.legend.html

@@ -1,27 +1,27 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
-<EM>d.legend</EM> displays a legend for a user-specified
+<em>d.legend</em> displays a legend for a user-specified
 raster map layer in the active frame on the graphics
 monitor.  
-<P>
+<p>
 
-The user can run <EM>d.legend</EM> either non-interactively
+The user can run <em>d.legend</em> either non-interactively
 or interactively.  If the user specifies the name of a
 raster <B>map</B> layer on the command line, the program
 will run non-interactively.  Default legend text
 <B>color</B> and position will be used unless
 the user specifies other values on the command line.
 
-<P>
+<p>
 
 Alternately, the user can simply type <B>d.legend</B> on the command line; 
 in this case, the program will prompt the user for parameter values 
 using the standard GRASS GUI interface.
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 
 The legend's default size is based on the dimensions of the
-active frame, specifically its height.  <EM>d.legend</EM> will only
+active frame, specifically its height.  <em>d.legend</em> will only
 obscure those portions of the active frame that directly underlie the legend.
 <p>
 When using the mouse or <B>at</B> to size &amp; place the legend, a user may
@@ -41,31 +41,31 @@ and/or <B>-n</B> options to reduce the number of categories to be displayed,
 or the <B>-s</B> flag to force a smooth gradient legend.
 <p>
 The <B>lines</B> option will display the first number of categories, as defined
-by <EM>value</EM>, contained in the raster map. When used with the <B>-n</B> flag,
+by <em>value</em>, contained in the raster map. When used with the <B>-n</B> flag,
 it takes on a new meaning: "up to category #". When used with both
 <B>thin</B> and the <B>-n</B> flag, its meaning becomes more obscure. When
 using <B>lines</B>, auto-scaled text similar to "4 of 16 categories" will be placed at 
 the bottom of the legend.
 <p>
 The <B>thin</B> option sets the thinning factor. For raster maps with a 0th
-category, <B>thin=</B><EM>10</EM> gives cats [0,10,20,...]. For raster maps 
-starting at category 1, <B>thin=</B><EM>10</EM> gives cats [1,11,21,...].
+category, <B>thin=</B><em>10</em> gives cats [0,10,20,...]. For raster maps 
+starting at category 1, <B>thin=</B><em>10</em> gives cats [1,11,21,...].
 <p>
 The <B>use</B> option lets the user create a legend made up of arbitrary category
-values. e.g.&nbsp;<B>use=</B><EM>1000,100,10,0,-10,-100,-1000</EM>
+values. e.g.&nbsp;<B>use=</B><em>1000,100,10,0,-10,-100,-1000</em>
 <p>
 The <B>range</B> option lets the user define the minimum and maximum categories
 to be used in the legend. It may also be used to define the limits of a smooth
 gradient legend created from a raster containing floating point values. Note
 the color scale will remain faithful to the category values as defined with
-<EM><A HREF="r.colors.html">r.colors</A></EM>, and the <B>range</B> may be
-extended to the limits defined by the <EM><A HREF="r.colors.html">r.colors</A></EM>
+<em><a href="r.colors.html">r.colors</A></em>, and the <B>range</B> may be
+extended to the limits defined by the <em><a href="r.colors.html">r.colors</A></em>
 color map.
 <p>
 The flag <B>-n</B> is useful for categorial maps, as it suppresses the
 drawing of non-existing categories (otherwise the full range is shown).
 <p>
-Vertical legends produced with <EM>d.legend</EM> will place text labels to the
+Vertical legends produced with <em>d.legend</em> will place text labels to the
 right of the legend box, horizontal legends will place text below. This text
 will be auto-scaled to fit within the frame, reducing the size of the legend
 if necessary. Legends positioned with the mouse or with the <B>at</B> option
@@ -81,7 +81,7 @@ numbers will be expressed in scientific notation, e.g.&nbsp;"1.7e-9".
 <p>
 Legends placed with the mouse are not saved to the display window's history
 for automatic redraw. By setting the Debug level to 1 (see 
-<EM><A HREF="g.gisenv.html">g.gisenv</A></EM>) the corresponding <b>at</b>
+<em><a href="g.gisenv.html">g.gisenv</A></em>) the corresponding <b>at</b>
 setting can be determined.
 <p>
 Note that old scripts which relied on setting <B>lines</B> greater than the
@@ -90,28 +90,28 @@ output, although the auto-scaling should still produce something that looks
 good in this case.
 
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
-<EM><A HREF="d.barscale.html">d.barscale</A></EM><BR>
-<EM><A HREF="d.colors.html">d.colors</A></EM><BR>
-<EM><A HREF="d.colortable.html">d.colortable</A></EM><BR>
-<EM><A HREF="d.erase.html">d.erase</A></EM><BR>
-<EM><A HREF="d.font.html">d.font</A></EM><BR>
-<EM><A HREF="d.grid.html">d.grid</A></EM><BR>
-<EM><A HREF="d.rast.html">d.rast</A></EM><BR>
-<!-- <EM><A HREF="d.rast.labels.html">d.rast.labels</A></EM><BR> -->
-<EM><A HREF="d.rast.leg.html">d.rast.leg</A></EM><BR>
-<EM><A HREF="d.text.html">d.text</A></EM><BR>
-<EM><A HREF="d.vect.thematic.html">d.vect.thematic</A></EM><BR>
-<EM><A HREF="d.what.rast.html">d.what.rast</A></EM><BR>
-<EM><A HREF="g.gisenv.html">g.gisenv</A></EM><BR>
-<EM><A HREF="r.reclass.html">r.reclass</A></EM><BR>
+<em><a href="d.barscale.html">d.barscale</A></em><br>
+<em><a href="d.colors.html">d.colors</A></em><br>
+<em><a href="d.colortable.html">d.colortable</A></em><br>
+<em><a href="d.erase.html">d.erase</A></em><br>
+<em><a href="d.font.html">d.font</A></em><br>
+<em><a href="d.grid.html">d.grid</A></em><br>
+<em><a href="d.rast.html">d.rast</A></em><br>
+<!-- <em><a href="d.rast.labels.html">d.rast.labels</A></em><br> -->
+<em><a href="d.rast.leg.html">d.rast.leg</A></em><br>
+<em><a href="d.text.html">d.text</A></em><br>
+<em><a href="d.vect.thematic.html">d.vect.thematic</A></em><br>
+<em><a href="d.what.rast.html">d.what.rast</A></em><br>
+<em><a href="g.gisenv.html">g.gisenv</A></em><br>
+<em><a href="r.reclass.html">r.reclass</A></em><br>
 
 
-<H2>AUTHORS</H2>
+<h2>AUTHORS</h2>
 Bill Brown, U.S. Army Construction Engineering Research Laboratories
-<BR>Late 2002: Rewrite of much of the code. Hamish Bowman,
+<br>Late 2002: Rewrite of much of the code. Hamish Bowman,
  Otago University, New Zealand
-<BR>Additional improvements from various authors
+<br>Additional improvements from various authors
 
 <p><i>Last changed: $Date$</i>

+ 18 - 18
display/d.linegraph/d.linegraph.html

@@ -1,9 +1,9 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
-<EM>d.linegraph</EM> is a primitive program to draw simple x,y line graphs
+<em>d.linegraph</em> is a primitive program to draw simple x,y line graphs
 based on numerical data contained in separate files.
-<P>
-Data file format<BR>
+<p>
+Data file format<br>
 The X and Y data files for the graph are essentially a column of numbers in
 each file, with one input number per line.  The program expects that each X
 value will have a corresponding Y value, therefore the number of lines in
@@ -17,11 +17,11 @@ according to that Y scale. Therefore, if multiple Y data inputs are used
 with dissimilar units, the graph produced comparing the two will be
 deceptive.
 
-<P>
+<p>
 <DL>
 <DT><B>directoryname</B>
 <DD>Path to the directory where the input files are located. If this option
-is not used, the <EM>d.linegraph</EM> looks for files in the current directory.
+is not used, the <em>d.linegraph</em> looks for files in the current directory.
 <DD>Example format: directory/usr/grass/data/graph
 
 <DT><B>ycoloroption[,option,...]]</B>
@@ -52,7 +52,7 @@ Default is no title unless the need for a unit descriptor is computed by
 the program (i.e. Y: ttiittllee in thousands). Also, see NOTES section
 (below) for a format caveat for multi-word titles. In the case of graphs
 with multiple lines, one may wish to use more specific title placement by
-using the <EM>d.text</EM> or <EM>v.label</EM> programs.
+using the <em>d.text</em> or <em>v.label</em> programs.
 
 <DT><B>titlevalue</B>
 <DD>Title to describe the graph. Will be centered over the top of graph.
@@ -60,35 +60,35 @@ Default is no title. See NOTES section (below) for a format caveat for
 multi-word titles.
 </DL>
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 Since the command line parser is not amiable to multiple word inputs, to
 input titles of more than one word, use the underscore character ("") to
 represent spaces (" ").
-<P>
+<p>
 Example: "titleCensusdata1990" would be printed over the graph as "Census
 data 1990".
-<P>
+<p>
 The way the program locates and labels tic marks is less than perfect: 1)
 although distances between Y tics is proportional to the value, they are
 not proportional on the X axis; 2) decimal values between -1 and 1 can be
 printed on the X axis, but not on Y. (With respect to the later, the input
 for Y values can all be multiplied by a factor of 10 before graphing).
 
-<P>
+<p>
 It might be easier to use a 3rd party tool such as xgraph or GNUplot instead
 of <em>d.linegraph</em>.
 .
 (You can make GNUplot output pretty by using its SVG or PostScript output
 driver and converting that back into a rasterized image in a paint program)
 
-<H2>SEE ALSO</H2>
-<EM>
-<A HREF="d.frame.html">d.frame</A>,
-<A HREF="d.text.html">d.text</A>,
-<A HREF="v.label.html">v.label</A>
-</EM>
+<h2>SEE ALSO</h2>
+<em>
+<a href="d.frame.html">d.frame</A>,
+<a href="d.text.html">d.text</A>,
+<a href="v.label.html">v.label</A>
+</em>
 
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
 Chris Rewerts, Agricultural Engineering, Purdue University
 
 <p>

+ 24 - 24
display/d.measure/d.measure.html

@@ -1,6 +1,6 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
-<EM>d.measure</EM> provides the user with an interactive
+<em>d.measure</em> provides the user with an interactive
 way to measure the lengths and areas of lines and polygons
 drawn by the user in the active frame on the graphics
 monitor.  Lines and polygons are drawn using a pointing
@@ -8,54 +8,54 @@ device (mouse).  Each line segment is drawn in colors
 <b>c1</b> and <b>c2</b>.  A mouse button menu indicates
 that the user can find out the geographic coordinates of
 the cursor location, draw line segments between
-user-specified vertices, and quit <EM>d.measure</EM>. Lines
+user-specified vertices, and quit <em>d.measure</em>. Lines
 and polygons are defined by the series of vertices marked
 by the user. If more than two successive vertices are
-drawn, <EM>d.measure</EM> prints the area encompassed
-(<EM>d.measure</EM> will assume the area is closed even if
+drawn, <em>d.measure</em> prints the area encompassed
+(<em>d.measure</em> will assume the area is closed even if
 the user has not joined the first and last vertices).
 <!-- (not [currently] true!)  Line lengths are stated in the same units
 as those of the current LOCATION. In a XY-LOCATION, where no units are
-available, <EM>d.measure</EM> prints a warning and gives results without
+available, <em>d.measure</em> prints a warning and gives results without
 units. -->
 Areas can be stated in hectares, square miles, square meters and
 square kilometers.
 
-Lines and polygons drawn using <EM>d.measure</EM> will
+Lines and polygons drawn using <em>d.measure</em> will
 overlay (not overwrite) whatever display currently appears
 in the active frame on the graphics monitor.  The user can,
 for example, run 
-<EM><A HREF="d.rast.html">d.rast</A></EM> or 
-<EM><A HREF="d.vect.html">d.vect</A></EM> prior to running
-<EM>d.measure</EM>, and use raster and/or vector maps as a backdrop.
+<em><a href="d.rast.html">d.rast</A></em> or 
+<em><a href="d.vect.html">d.vect</A></em> prior to running
+<em>d.measure</em>, and use raster and/or vector maps as a backdrop.
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 
-<EM>d.measure</EM> uses all segments drawn by the user when computing area. 
+<em>d.measure</em> uses all segments drawn by the user when computing area. 
 If the user draws an area within another area, the combined 
 area of both regions will be output. 
 
-<H2>TODO</H2>
+<h2>TODO</h2>
 
 Output lengths in the same units as those of the current LOCATION as
-found in the <tt>PROJ_UNITS</tt> file (see <EM>g.proj</EM>).
+found in the <tt>PROJ_UNITS</tt> file (see <em>g.proj</em>).
 Volunteers are welcome for this task.
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
-<EM><A HREF="d.frame.html">d.frame</A></EM><br>
-<EM><A HREF="d.graph.html">d.graph</A></EM><br>
-<EM><A HREF="d.rast.html">d.rast</A></EM><br>
-<EM><A HREF="d.vect.html">d.vect</A></EM><br>
-<EM><A HREF="d.where.html">d.where</A></EM><br>
-<EM><A HREF="g.proj.html">g.proj</A></EM>
+<em><a href="d.frame.html">d.frame</A></em><br>
+<em><a href="d.graph.html">d.graph</A></em><br>
+<em><a href="d.rast.html">d.rast</A></em><br>
+<em><a href="d.vect.html">d.vect</A></em><br>
+<em><a href="d.where.html">d.where</A></em><br>
+<em><a href="g.proj.html">g.proj</A></em>
 
 
-<H2>AUTHORS</H2>
+<h2>AUTHORS</h2>
 
 James Westervelt, 
-<BR>
-Michael Shapiro, <BR>
+<br>
+Michael Shapiro, <br>
 U.S. Army Construction Engineering 
 Research Laboratory
 

+ 2 - 2
display/d.path/d.path.html

@@ -13,7 +13,7 @@ points are entered by mouse into the map displayed in the GRASS monitor, or
 if the <b>coor</b> option is used they can be specified non-interactively.
 The actions bound to the mouse buttons are described in the terminal
 window when running the command.
-<P>
+<p>
 To calculate shortest path non-interactively and save the path to a new vector
 map, use the <em>v.net.path</em> module.
 
@@ -34,7 +34,7 @@ d.path -b roads coor=601653.5,4922869.2,593330.8,4924096.6
 <h2>SEE ALSO</h2>
 
 <em>
-<a HREF="v.net.path.html">v.net.path</a>
+<a href="v.net.path.html">v.net.path</a>
 </em>
 
 <h2>AUTHOR</h2>

+ 3 - 3
display/d.profile/d.profile.html

@@ -1,12 +1,12 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
 This command displays the profile for a specified transect.
 
-<H2>BUGS</H2>
+<h2>BUGS</h2>
 
 None known.
 
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
 
 Glynn Clements
 

+ 29 - 29
display/d.rast.arrow/d.rast.arrow.html

@@ -1,20 +1,20 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
-<EM>d.rast.arrow</EM>
+<em>d.rast.arrow</em>
 is designed to help users better visualize surface water flow direction,
 as indicated in an aspect raster map layer.  There are two ways to specify
 the aspect layer the program is to use.  The first is to display the aspect
-map layer on the graphics monitor before running <EM>d.rast.arrow</EM>.
-The second method involves setting the <EM>map</EM> parameter
+map layer on the graphics monitor before running <em>d.rast.arrow</em>.
+The second method involves setting the <em>map</em> parameter
 to the name of the desired aspect map.
 This allows the arrows to be drawn over any other maps already displayed
 on the graphics monitor.
-<P>
+<p>
 
-<EM>d.rast.arrow</EM> will draw an arrow over each displayed cell
+<em>d.rast.arrow</em> will draw an arrow over each displayed cell
 to indicate in which direction the cell slopes. If the aspect
 layer has a category value denoting locations of "unknown" aspect,
-<EM>d.rast.arrow</EM> draws a question mark over the displayed cells
+<em>d.rast.arrow</em> draws a question mark over the displayed cells
 of that category.
 Cells containing null data will be marked with an "X".
 <p>
@@ -29,19 +29,19 @@ the magnitude map to suit your needs (absolute value, inverted direction and
 so on). 
 
 <p>
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 By default, arrows are drawn at the size of a cell and cannot be seen if 
 the raster map is relatively close in scale. You can use the <em>skip</em> 
 option to draw arrows every n-th cell in both directions if you are working 
 with relatively high resolutions. It may be useful to disable the grid in
 this case, which is accomplished by setting its color to "<tt>none</tt>".
-<P>
+<p>
 For GRASS and Compass type aspect maps, the cell values of the aspect map
 will determine the corresponding direction in 360 degrees. ANSWERS type
 aspect maps will be plotted in multiples of 15 degrees, and AGNPS type
 aspect maps will be displayed in D8 representation, i.e. the eight multiples 
 of 45 degrees.
-<P>
+<p>
 GRASS aspect maps are measured using Cartesian conventions, i.e. in degrees 
 counterclockwise from east. e.g.:
 
@@ -53,14 +53,14 @@ counterclockwise from east. e.g.:
 </pre></div>
 
 They can be created from a raster elevation map with <em>r.slope.aspect</em>.
-<P>
+<p>
 Compass type aspect maps are measured in degrees clockwise from north.
-<P>
+<p>
 This module uses oceanographic conventions, i.e. arrows point downslope or 
 direction "to", as opposed to atmospheric conventions (direction "from").
 
 
-<H2>EXAMPLE</H2>
+<h2>EXAMPLE</h2>
 
 Convert U,V velocity component maps into magnitide,direction maps for use 
 with <em>d.rast.arrow</em>:
@@ -71,25 +71,25 @@ r.mapcalc "direction = atan(U_map, V_map)"
 d.rast.arrow map=direction type=grass magnitude_map=magnitude skip=3 grid=none
 </pre></div>
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
-<EM><A HREF="d.frame.html">d.frame</A></EM><BR>
-<EM><A HREF="d.rast.html">d.rast</A></EM><BR>
-<EM><A HREF="d.rast.edit.html">d.rast.edit</A></EM><BR>
-<EM><A HREF="d.rast.num.html">d.rast.num</A></EM><BR>
-<EM><A HREF="g.region.html">g.region</A></EM><BR>
-<EM><A HREF="r.slope.aspect.html">r.slope.aspect</A></EM><BR>
-<BR>
+<em><a href="d.frame.html">d.frame</A></em><br>
+<em><a href="d.rast.html">d.rast</A></em><br>
+<em><a href="d.rast.edit.html">d.rast.edit</A></em><br>
+<em><a href="d.rast.num.html">d.rast.num</A></em><br>
+<em><a href="g.region.html">g.region</A></em><br>
+<em><a href="r.slope.aspect.html">r.slope.aspect</A></em><br>
+<br>
 
-<H2>AUTHORS</H2>
+<h2>AUTHORS</h2>
 
-<u>Original author</u><BR>
-Chris Rewerts<BR>
-<em>Agricultural Engineering,<BR>
-Purdue University</em><BR><BR>
-<u>Magnitude and 360 arrow code</u><BR>
-Hamish Bowman<BR>
-<em>Department of Marine Science, <BR>
+<u>Original author</u><br>
+Chris Rewerts<br>
+<em>Agricultural Engineering,<br>
+Purdue University</em><br><br>
+<u>Magnitude and 360 arrow code</u><br>
+Hamish Bowman<br>
+<em>Department of Marine Science, <br>
 University of Otago, New Zealand</em>
 
 <p><i>Last changed: $Date$</i>

+ 8 - 8
display/d.rast.num/d.rast.num.html

@@ -1,6 +1,6 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
-<EM>d.rast.num</EM>
+<em>d.rast.num</em>
 overlays cell category values onto a raster map layer displayed
 on the user's graphics monitor.
 
@@ -8,16 +8,16 @@ Category values will be displayed in the text color given and scaled
 to fit within a single cell. A grid outlining each map cell will also 
 be overlain in a user-specified color, unless it has been set to "none".
 
-<P>
+<p>
 If no grid color is given the default will be used. If no map layer
 is specified, the program will use whatever raster map layer is
 currently displayed in the active frame on the graphics monitor.
-<P>
+<p>
 If the <b>-f</b> flag is given the displayed number will take on the color 
 of the base map in that cell.
 
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 
 The user is advised to set the current region to a relatively
 small area (i.e., less than 100 rows by 100 columns);
@@ -25,7 +25,7 @@ otherwise, the individual cells being displayed will be small
 and the category value associated with each will be difficult to see.
 No data cells are indicated with "Null".
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
 
 <em><a href="d.frame.html">d.frame</a></em>,
@@ -37,10 +37,10 @@ No data cells are indicated with "Null".
 <em><a href="r.slope.aspect.html">r.slope.aspect</a></em>
 
 
-<H2>AUTHORS</H2>
+<h2>AUTHORS</h2>
 
 Raghavan Srinivasan,
-and Chris Rewerts,<BR>
+and Chris Rewerts,<br>
 Agricultural Engineering, Purdue University
 
 <p><i>Last changed: $Date$</i>

+ 3 - 3
display/d.rast/d.rast.html

@@ -8,9 +8,9 @@ in the active display frame on the graphics monitor.
 
 <h2>SEE ALSO</h2>
 
-<em><a HREF="d.erase.html">d.erase</a></em><br>
-<em><a HREF="d.vect.html">d.vect</a></em><br>
-<!-- <em><a HREF="d.what.rast.html">d.what.rast</a></em><br> -->
+<em><a href="d.erase.html">d.erase</a></em><br>
+<em><a href="d.vect.html">d.vect</a></em><br>
+<!-- <em><a href="d.what.rast.html">d.what.rast</a></em><br> -->
 
 
 <h2>AUTHOR</h2>

+ 35 - 35
display/d.rgb/d.rgb.html

@@ -1,13 +1,13 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
-<EM>RGB</EM> stands for red, green, and blue. This program
+<em>RGB</em> stands for red, green, and blue. This program
 visually combines three raster map layers to form a color
 image. For each layer, the corresponding component from
 the layer's color table is used (e.g. for the red layer,
 the red component is used, and so on). In general, the
 layers should use a grey-scale color table.
 
-<H2>OPTIONS</H2>
+<h2>OPTIONS</h2>
 
 <H3>Flags:</H3> 
 
@@ -20,7 +20,7 @@ displayed in the active graphics frame. Any no-data areas in any of
 the named raster maps will seem transparent, and reveal the underlying
 image previously displayed in the graphics frame. If the <B>-o</B>
 flag is set, only cells containing non-null values will be displayed
-from the <EM>overlaid</EM> raster map. All other areas (i.e., the
+from the <em>overlaid</em> raster map. All other areas (i.e., the
 portions of the overlaid map that contain null values) will leave the
 underlying display untouched.
 
@@ -29,15 +29,15 @@ underlying display untouched.
 <H3>Parameters:</H3>
 
 <DL>
-<DT><B>red=</B><EM>name</EM>
+<DT><B>red=</B><em>name</em>
 <DD>Name of raster map layer to be used for RED component. 
-<DT><B>green=</B><EM>name</EM>
+<DT><B>green=</B><em>name</em>
 <DD>Name of raster map layer to be used for GREEN component. 
-<DT><B>blue=</B><EM>name</EM>
+<DT><B>blue=</B><em>name</em>
 <DD>Name of raster map layer to be used for BLUE component. 
 </DL>
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 
 This is a new version of <B>d.rgb</B>, which sends the
 data to the graphics monitor in true-color RGB format.
@@ -49,45 +49,45 @@ Nor does it have an option to generate a composite layer.
 The image and raster map layers will not display properly
 if the graphics device does not have a reasonable sampling
 of the RGB color-space.
-<P>
+<p>
 
 If color quality of satellite image color composites seems to appear poor,
-run <EM><a href="r.colors.html">r.colors</A></EM> on the selected satellite 
-channels.<P>
+run <em><a href="r.colors.html">r.colors</A></em> on the selected satellite 
+channels.<p>
 Example:
 <dl>
-<dd><B>r.info -r</B> <EM>image.1</EM><BR>
-<tt>min=0<BR>
-max=255</tt><BR>
-
-<dd><B>r.colors map=</B><EM>image.1</EM> <B>color=</B><EM>rules</EM> 
-<< EOF<BR>
-0 black<BR>
-255 white<BR>
-EOF<BR>
-
-<dd><B>r.colors map=</B><EM>image.2</EM> <B>rast=</B><EM>image.1</EM>
-<dd><B>r.colors map=</B><EM>image.3</EM> <B>rast=</B><EM>image.1</EM>
+<dd><B>r.info -r</B> <em>image.1</em><br>
+<tt>min=0<br>
+max=255</tt><br>
+
+<dd><B>r.colors map=</B><em>image.1</em> <B>color=</B><em>rules</em> 
+<< EOF<br>
+0 black<br>
+255 white<br>
+EOF<br>
+
+<dd><B>r.colors map=</B><em>image.2</em> <B>rast=</B><em>image.1</em>
+<dd><B>r.colors map=</B><em>image.3</em> <B>rast=</B><em>image.1</em>
 </dl>
 
-<EM>Note: Future GRASS versions may do this for you automatically.</EM>
-<BR><BR><BR>
+<em>Note: Future GRASS versions may do this for you automatically.</em>
+<br><br><br>
 
 To write out the color composite to a R/G/B raster maps, use 
-<EM><a href="r.composite.html">r.composite</A></EM>.
+<em><a href="r.composite.html">r.composite</A></em>.
 
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
-<EM><A HREF="d.colors.html">d.colors</A></EM><br>
-<EM><A HREF="d.colortable.html">d.colortable</A></EM><br>
-<EM><A HREF="d.his.html">d.his</A></EM><br>
-<EM><A HREF="r.blend.html">r.blend</A></EM><br>
-<EM><A HREF="r.mapcalc.html">r.mapcalc</A></EM><br>
-<EM><A HREF="r.colors.html">r.colors</A></EM><br>
-<EM><A HREF="r.composite.html">r.composite</A></EM>
+<em><a href="d.colors.html">d.colors</A></em><br>
+<em><a href="d.colortable.html">d.colortable</A></em><br>
+<em><a href="d.his.html">d.his</A></em><br>
+<em><a href="r.blend.html">r.blend</A></em><br>
+<em><a href="r.mapcalc.html">r.mapcalc</A></em><br>
+<em><a href="r.colors.html">r.colors</A></em><br>
+<em><a href="r.composite.html">r.composite</A></em>
 
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
 
 Glynn Clements
 

+ 7 - 7
display/d.rhumbline/d.rhumbline.html

@@ -1,4 +1,4 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
 A rhumbline (loxodrome) is a line following a constant angle of the
 compass (i.e., a line of constant direction). It crosses all meridians
@@ -6,7 +6,7 @@ at the same angle, i.e. a path of constant bearing.
 
  <!-- There are 32
 points on the compass (points are roughly 11 degrees 15
-minutes apart). --> <EM>d.rhumbline</EM> displays the
+minutes apart). --> <em>d.rhumbline</em> displays the
 rhumbline joining any two user-specified points in the
 active frame on the user's graphics monitor.  The named
 coordinate locations must fall within the boundaries of the
@@ -30,20 +30,20 @@ d.rhumbline coor=55:58W,33:18S,26:43E,60:37N lcolor=yellow tcolor=red
 
 <p>
 <center>
-<img src="d_rhumbline.png" border=1><BR>
+<img src="d_rhumbline.png" border=1><br>
 <i>Rhumbline (loxodrome)</i>
 </center>
 
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 
 This program works only with longitude-latitude locations. 
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
-<EM><A HREF="d.geodesic.html">d.geodesic</A></EM>
+<em><a href="d.geodesic.html">d.geodesic</A></em>
 
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
 
 Michael Shapiro, 
 U.S. Army Construction Engineering 

+ 37 - 37
display/d.text/d.text.html

@@ -1,6 +1,6 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
-<EM>d.text</EM> draws text in the active display frame on
+<em>d.text</em> draws text in the active display frame on
 the graphics monitor.  Text can be provided through
 standard input or redirected from a file (using the UNIX
 redirection mechanism).
@@ -8,7 +8,7 @@ redirection mechanism).
 In addition to the options provided on the command line,
 colors, text size, font type, rotation angle, and boldness can be adjusted
 with commands in the standard input (i.e., if the user
-invokes <EM>d.text</EM> without options on the command
+invokes <em>d.text</em> without options on the command
 line, and then assigns values to these options on lines
 within the standard input).
 
@@ -16,60 +16,60 @@ within the standard input).
 
 <DL>
 
-<DT><B>.C</B> <EM>color</EM> 
+<DT><B>.C</B> <em>color</em> 
 <DD>
-(where <EM>color</EM> is one of the available colors) causes text appearing on 
+(where <em>color</em> is one of the available colors) causes text appearing on 
 subsequent lines to be drawn in that color. 
 
 
-<DT><B>.G</B> <EM>color</EM>
+<DT><B>.G</B> <em>color</em>
 <DD>
-(where <EM>color</EM> is one of the available colors) causes the background of text
+(where <em>color</em> is one of the available colors) causes the background of text
 appearing on subsequent lines to be drawn in that color.
 
-<DT><B>.S </B> <EM>size</EM>
+<DT><B>.S </B> <em>size</em>
 <DD>
-(where <EM>size</EM> is a percentage within the range 0 to
+(where <em>size</em> is a percentage within the range 0 to
 100) adjusts text size.  Note that a size of 10 would allow
 10 lines to be drawn in the active display frame, 5 would
 allow the drawing of 20 lines, and 50 would allow the
 drawing of 2 lines.
 
-<P>
-<DT><B>.F</B> <EM>font</EM>
+<p>
+<DT><B>.F</B> <em>font</em>
 <DD>
-(where <EM>font</EM> is one of the fonts known by the GRASS program 
-<EM><A HREF="d.font.html">d.font</A></EM>) manipulates
+(where <em>font</em> is one of the fonts known by the GRASS program 
+<em><a href="d.font.html">d.font</A></em>) manipulates
 the font type. Available fonts are listed in the GRASS manual entry for 
-<EM><A HREF="d.font.html">d.font</A></EM>. 
+<em><a href="d.font.html">d.font</A></em>. 
 The default font type used (if unspecified by the user) 
-is <EM>romans</EM>.
+is <em>romans</em>.
 <!-- Run the GRASS macro 
-<EM><A  HREF="show.fonts.sh.html">show.fonts.sh</A></EM> 
+<em><A  HREF="show.fonts.sh.html">show.fonts.sh</A></em> 
 to see what these fonts look like. -->
 
-<DT><B>.R </B> <EM>rotation</EM>
+<DT><B>.R </B> <em>rotation</em>
 <DD>
-(where <EM>rotation</EM> is an angle in degrees, counter-clockwise)
+(where <em>rotation</em> is an angle in degrees, counter-clockwise)
 to rotate the text.
 
 <DT><B>.B 1</B>
 <DD>stipulates that following text be printed in <B>bold</B>.
-This command means <EM>bold on</EM>.
+This command means <em>bold on</em>.
 
 <DT><B>.B 0</B>
-<DD> turns <EM>bold off</EM> of all text appearing on lines beneath 
-     it. (<EM>Bold off</EM> is used by default, if unspecified by the user.) 
+<DD> turns <em>bold off</em> of all text appearing on lines beneath 
+     it. (<em>Bold off</em> is used by default, if unspecified by the user.) 
 
 </DL>
 
-<H2>EXAMPLE</H2>
+<h2>EXAMPLE</h2>
 
 The following command will print the short phrase "This is
 a test of d.text" in the active display frame using the
 color yellow, in bold, and using 4/100'ths (4%) of the
 active frame's vertical space per line:
-<P>
+<p>
 
 
 <pre>
@@ -83,34 +83,34 @@ EOF
 </pre>
 
 
-The user presses <EM>control-d</EM> 
-(the "Ctrl" and "d" keys) to end input to <EM>d.text</EM> (equal to EOF).
+The user presses <em>control-d</em> 
+(the "Ctrl" and "d" keys) to end input to <em>d.text</em> (equal to EOF).
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 
 Note that the GRASS command 
-<EM><A HREF="d.title.html">d.title</A></EM> creates map TITLEs in a format 
-suitable for input to <EM>d.text</EM>.
+<em><a href="d.title.html">d.title</A></em> creates map TITLEs in a format 
+suitable for input to <em>d.text</em>.
 
-<P>
+<p>
 
-<EM>d.text</EM> needs escape sequences that can be used
+<em>d.text</em> needs escape sequences that can be used
 within lines to change colors, boldness, and perhaps size.
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
-<EM><A HREF="d.font.html">d.font</A></EM><br>
-<EM><A HREF="d.title.html">d.title</A></EM><br>
-<!-- <EM><A HREF="show.fonts.sh.html">show.fonts.sh</A></EM><br> -->
-<EM><A HREF="d.labels.html">d.labels</A></EM><br>
+<em><a href="d.font.html">d.font</A></em><br>
+<em><a href="d.title.html">d.title</A></em><br>
+<!-- <em><a href="show.fonts.sh.html">show.fonts.sh</A></em><br> -->
+<em><a href="d.labels.html">d.labels</A></em><br>
 
 
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
 
 James Westervelt, 
 U.S. Army Construction Engineering 
 Research Laboratory
-<P>
+<p>
 Updates by Huidae Cho
 
 <p><i>Last changed: $Date$</i>

Plik diff jest za duży
+ 8 - 8
display/d.thematic.area/d.thematic.area.html


+ 29 - 29
display/d.title/d.title.html

@@ -1,59 +1,59 @@
-<H2>DESCRIPTION</H2>
-
-<EM>d.title</EM> generates to standard output a string which can be used by
-<EM><A HREF="d.text.html">d.text</A></EM> to draw a TITLE for the raster map
-layer <EM>name</EM> in the active display frame on the graphics monitor. 
-Output created by <EM>d.title</EM> can be redirected into a file, or piped
-directly into <EM><A HREF="d.text.html">d.text</A></EM> to display the map
-TITLE created by <EM>d.title</EM>.  The map TITLE created will include the
+<h2>DESCRIPTION</h2>
+
+<em>d.title</em> generates to standard output a string which can be used by
+<em><a href="d.text.html">d.text</A></em> to draw a TITLE for the raster map
+layer <em>name</em> in the active display frame on the graphics monitor. 
+Output created by <em>d.title</em> can be redirected into a file, or piped
+directly into <em><a href="d.text.html">d.text</A></em> to display the map
+TITLE created by <em>d.title</em>.  The map TITLE created will include the
 map layer's name, TITLE, MAPSET, LOCATION_NAME, geographic region boundary
 coordinates, and cell resolution.
-If the <b>-d</b> draw flag is used, then <EM>d.title</EM> will call
-<EM>d.text</EM> for you and the title will be automatically rendered
+If the <b>-d</b> draw flag is used, then <em>d.title</em> will call
+<em>d.text</em> for you and the title will be automatically rendered
 to the display.
 
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 
 The text created with 
-<EM><A HREF="d.text.html">d.text</A></EM> 
+<em><a href="d.text.html">d.text</A></em> 
 will not necessarily fit within the 
 active display frame on the graphics monitor; 
 the user should choose a text size appropriate to this frame. 
 
 
-<H2>EXAMPLES</H2>
+<h2>EXAMPLES</h2>
 
 For example, a user wishing to create a suitable TITLE for the 
-Spearfish, SD <EM>soils</EM> map layer and to display this TITLE in the 
+Spearfish, SD <em>soils</em> map layer and to display this TITLE in the 
 active display frame on the graphics monitor might type the following: 
 <DL>
-<DD> <B>d.title map=</B><EM>soils</EM> <B>color=</B><EM>red</EM> <B>size=</B><EM>5</EM> <B>&gt; TITLE.file</B>
-<DD> <B><A HREF="d.text.html">d.text</A> &lt; TITLE.file</B> 
+<DD> <B>d.title map=</B><em>soils</em> <B>color=</B><em>red</em> <B>size=</B><em>5</em> <B>&gt; TITLE.file</B>
+<DD> <B><a href="d.text.html">d.text</A> &lt; TITLE.file</B> 
 </DL>
-Alternately, the user might pipe <EM>d.title</EM> output directly 
-into <EM><A HREF="d.text.html">d.text</A>:</EM> 
+Alternately, the user might pipe <em>d.title</em> output directly 
+into <em><a href="d.text.html">d.text</A>:</em> 
 <DL>
 <DD>
-<B>d.title map=</B><EM>soils</EM> <B>color=</B><EM>red</EM> <B>size=</B><EM>5</EM> | 
-<A HREF="d.text.html">d.text</A>
+<B>d.title map=</B><em>soils</em> <B>color=</B><em>red</em> <B>size=</B><em>5</em> | 
+<a href="d.text.html">d.text</A>
 </DL>
 
-<P>
-A file created by <EM>d.title</EM> can be displayed 
-with <EM><A HREF="d.text.html">d.text</A></EM>.
+<p>
+A file created by <em>d.title</em> can be displayed 
+with <em><a href="d.text.html">d.text</A></em>.
 Information contained in this file takes precedence over the 
-<EM>color</EM> and <EM>size</EM> parameters for 
-<EM><A HREF="d.text.html">d.text</A></EM>.
+<em>color</em> and <em>size</em> parameters for 
+<em><a href="d.text.html">d.text</A></em>.
 
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
-<EM><A HREF="d.font.html">d.font</A></EM><br>
-<EM><A HREF="d.text.html">d.text</A></EM><br>
+<em><a href="d.font.html">d.font</A></em><br>
+<em><a href="d.text.html">d.text</A></em><br>
 
 
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
 James Westervelt, 
 U.S. Army Construction Engineering 
 Research Laboratory

+ 4 - 4
display/d.vect.chart/d.vect.chart.html

@@ -41,11 +41,11 @@ Example screenshot (zoomed):<br>
 
 <h2>SEE ALSO</h2>
 
-<em><a HREF="d.erase.html">d.erase</a>,
-<a HREF="d.vect.html">d.vect</a>,
+<em><a href="d.erase.html">d.erase</a>,
+<a href="d.vect.html">d.vect</a>,
 <a href="d.vect.thematic.html">d.vect.thematic</a>,
-<a HREF="d.what.vect.html">d.what.vect</a>,
-<a HREF="d.rast.html">d.rast</a></em>
+<a href="d.what.vect.html">d.what.vect</a>,
+<a href="d.rast.html">d.rast</a></em>
 
 <h2>AUTHOR</h2>
 

+ 4 - 4
display/d.what.rast/d.what.rast.html

@@ -140,16 +140,16 @@ The maximum number of raster map layers that can be queried at one time is 15.
 
 <p>
 
-<em><a HREF="d.what.vect.html">d.what.vect</a></em>
+<em><a href="d.what.vect.html">d.what.vect</a></em>
 allows the user to interactively query the category
 contents of multiple vector map layers at user-specified
 locations.
 
 <h2>SEE ALSO</h2>
 
-<em><a HREF="d.rast.html">d.rast</a></em><br>
-<em><a HREF="d.what.vect.html">d.what.vect</a></em><br>
-<em><a HREF="g.region.html">g.region</a></em><br>
+<em><a href="d.rast.html">d.rast</a></em><br>
+<em><a href="d.what.vect.html">d.what.vect</a></em><br>
+<em><a href="g.region.html">g.region</a></em><br>
 
 <h2>AUTHOR</h2>
 

+ 6 - 6
display/d.what.vect/d.what.vect.html

@@ -11,7 +11,7 @@ within the current geographic region in the active display frame on the
 graphic monitor. Query results from map(s) are by default displayed in a new 
 monitor, where label values can be added or changed. Using parameter <b>-x</b> 
 informations will be displayed as plain text to terminal window.
-<P>
+<p>
 This module always reports standard acres, even when the location uses
 US Survey feet as the map unit.
 
@@ -46,11 +46,11 @@ The right button on the mouse is used to quit the <em>d.what.vect</em> session.
 
 <h2>SEE ALSO</h2>
 
-<em><a HREF="d.rast.html">d.rast</a><br>
-<a HREF="d.vect.html">d.vect</a><br>
-<a HREF="d.what.rast.html">d.what.rast</a><br>
-<a HREF="g.region.html">g.region</a><br>
-<a HREF="v.what.html">v.what</a>
+<em><a href="d.rast.html">d.rast</a><br>
+<a href="d.vect.html">d.vect</a><br>
+<a href="d.what.rast.html">d.what.rast</a><br>
+<a href="g.region.html">g.region</a><br>
+<a href="v.what.html">v.what</a>
 </em>
 
 

+ 14 - 14
display/d.where/d.where.html

@@ -1,13 +1,13 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
 
-<EM>d.where</EM> is an <EM>interactive</EM> program that
+<em>d.where</em> is an <em>interactive</em> program that
 allows the user, using the pointing device (mouse), to
 identify the geographic coordinates associated with point
 locations within the current geographic region in the
 active display frame on the graphics monitor.
 
-<P>
+<p>
 Each mouse click will output the easting and northing of the point
 currently located beneath the mouse pointer. 
 A mouse-button menu is presented so the user knows which
@@ -15,7 +15,7 @@ mouse buttons to use. The output is always printed to the
 terminal screen; if the output is redirected into a file,
 it will be written to the file as well.
 
-<P>
+<p>
 Mouse buttons:
 
 <pre>
@@ -29,11 +29,11 @@ the middle mouse button allows to query two points (they are connected by a
 line for convenience). By using the right mouse button the module is left.
 
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 
 This program uses the current geographic region setting and active frame. 
 It is not necessary, although useful, to have displayed a map in the current 
-frame before running <EM>d.where</EM>. The <b>-d</b> flag allows the user to
+frame before running <em>d.where</em>. The <b>-d</b> flag allows the user to
 optionally output latitude/longitude coordinates pair(s) in decimal degree
 rather than DD:MM:SS format. The <b>-w</b> flag is only valid
 if a datum is defined for the current location.
@@ -42,19 +42,19 @@ If the <b>-f</b> flag is given the x,y frame coordinates of the active display
 monitor will be returned (as a percentage, 0,0 is bottom left).
 
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
-<EM><A HREF="d.what.rast.html">d.what.rast</A></EM><br>
-<EM><A HREF="d.what.vect.html">d.what.vect</A></EM><br>
-<EM><A HREF="g.region.html">g.region</A></EM><br>
-<EM><A HREF="v.what.rast.html">v.what.rast</A></EM><br>
-<EM><A HREF="v.what.vect.html">v.what.vect</A></EM>
+<em><a href="d.what.rast.html">d.what.rast</A></em><br>
+<em><a href="d.what.vect.html">d.what.vect</A></em><br>
+<em><a href="g.region.html">g.region</A></em><br>
+<em><a href="v.what.rast.html">v.what.rast</A></em><br>
+<em><a href="v.what.vect.html">v.what.vect</A></em>
 
 
-<H2>AUTHORS</H2>
+<h2>AUTHORS</h2>
 
 James Westervelt, <br>
-Michael Shapiro, <BR>
+Michael Shapiro, <br>
 U.S. Army Construction Engineering 
 Research Laboratory
 

+ 6 - 6
display/d.zoom/d.zoom.html

@@ -3,7 +3,7 @@
 <em>d.zoom</em> allows the user to interactively adjust the settings 
 of the current geographic region using a pointing device such as 
 a mouse. 
-Like <em><a HREF="g.region.html">g.region</a></em>, 
+Like <em><a href="g.region.html">g.region</a></em>, 
 <em>d.zoom</em> re-defines the settings of the geographic
 region.  However, <em>d.zoom</em> allows the user to change
 the current region settings interactively, by either
@@ -18,7 +18,7 @@ directing the user.
 <p>
 
 Additionally the region settings can be modified by
-running <em><a HREF="g.region.html">g.region</a></em>. 
+running <em><a href="g.region.html">g.region</a></em>. 
 
 <h2>NOTES</h2>
 
@@ -29,10 +29,10 @@ pan function, <b>-h </b> facilitates the use for handhelds.
 
 <h2>SEE ALSO</h2>
 
-<em><a HREF="d.erase.html">d.erase</a></em><br>
-<em><a HREF="d.rast.html">d.rast</a></em><br>
-<em><a HREF="d.vect.html">d.vect</a></em><br>
-<em><a HREF="g.region.html">g.region</a></em>
+<em><a href="d.erase.html">d.erase</a></em><br>
+<em><a href="d.rast.html">d.rast</a></em><br>
+<em><a href="d.vect.html">d.vect</a></em><br>
+<em><a href="g.region.html">g.region</a></em>
 
 <h2>AUTHOR</h2>
 

+ 3 - 3
doc/projectionintro.html

@@ -26,9 +26,9 @@ four corner points or by seeking several ground control points
  <a href="i.points.html">i.points</a>) and then transformed into the
 target location (<a href="i.rectify.html">i.rectify</a>). Polynomial
 transformation of 1st, 2nd and 3rd order are supported.
-<P>
+<p>
 A graphical user interface is provided by <a href="wxGUI.html">wxGUI</a>.
-<P>
+<p>
 To simply translate a raster map (without stretching or rotation), the
 <a href="r.region.html">r.region</a> command can be used.
 
@@ -48,7 +48,7 @@ into the location with projection and geocoded within this location by
 defining  four corner points or by seeking several ground control points.
 These points are stored into an ASCII file and then transformed within 
 the same location (<a href="v.transform.html">v.transform</a>).
-<P>
+<p>
 A graphical user interface is provided by <a href="gis.m.html">gis.m</a>.
 
 <h3>References</h3>

+ 6 - 6
doc/raster/r.example/r.example.html

@@ -1,17 +1,17 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
-<EM>r.example</EM> does practically do nothing, except
+<em>r.example</em> does practically do nothing, except
 for illustrating GRASS raster programming. It copies
 over an existing raster map to a new raster map.
 See the source code for details.
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
-<EM><A HREF="r.stats.html">r.stats</A></EM><br>
-<EM><A HREF="http://grass.itc.it/devel/index.php#prog">GRASS Programmer's Manual</A></EM>
+<em><a href="r.stats.html">r.stats</A></em><br>
+<em><a href="http://grass.itc.it/devel/index.php#prog">GRASS Programmer's Manual</A></em>
 
 
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
 
 GRASS Development Team
 

+ 2 - 2
doc/vector/v.example/v.example.html

@@ -10,9 +10,9 @@ the input map.
 v.example input=map output=newmap
 </pre></div>
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
-<EM><A HREF="http://grass.itc.it/devel/index.php#prog">GRASS Programmer's Manual</A></EM>
+<em><a href="http://grass.itc.it/devel/index.php#prog">GRASS Programmer's Manual</A></em>
 
 <h2>AUTHOR</h2>
 

+ 10 - 10
doc/vector/v.modules.html

@@ -2,15 +2,15 @@
 <TITLE>GRASS 5.1/7 Vector - Modules Status</TITLE>
 </HEAD>
 <BODY>
-<P>
+<p>
 <H1>GRASS 5.1/7 Vector - Modules Status</H1>
 
 This document describes the status of update from vector 4.0 (GRASS 4.0 and 5.0) to vector 5.0 (GRASS 5.1/7) format 
 and sites (GRASS 5.0) to vector 5.0 (GRASS 5.1/7) format.
 
-<P>
+<p>
 You are welcome to upgrade some modules. To avoid duplicate work please send
-information to <A href=mailto:blazek@itc.it>blazek@itc.it</A>
+information to <a href=mailto:blazek@itc.it>blazek@itc.it</A>
 before you start.
 
 <HR>
@@ -71,7 +71,7 @@ before you start.
 <TR><TD>libgsf</TD><TD>src/libes/ogsf/Gv3.c</TD>					<TD>Y</TD><TD>-</TD><TD>Y</TD><TD>&nbsp</TD><TD>&nbsp</TD></TR>
 
 <TR><TD>m.clump</TD><TD>src/misc/m.clump/vect.c</TD>					<TD>X</TD><TD>&nbsp</TD><TD>&nbsp</TD><TD>&nbsp</TD><TD>&nbsp</TD></TR>
-<TR><TD>m.in.e00</TD><TD>src/misc/m.in.e00/vector.c</TD>				<TD>X</TD><TD>&nbsp</TD><TD>&nbsp</TD><TD>E00 Should be added to OGR library: http://remotesensing.org/pipermail/gdal-dev/2003-April/000547.html <BR> http://grass.itc.it/pipermail/grass5/2002-February/001918.html</TD><TD>&nbsp</TD></TR>
+<TR><TD>m.in.e00</TD><TD>src/misc/m.in.e00/vector.c</TD>				<TD>X</TD><TD>&nbsp</TD><TD>&nbsp</TD><TD>E00 Should be added to OGR library: http://remotesensing.org/pipermail/gdal-dev/2003-April/000547.html <br> http://grass.itc.it/pipermail/grass5/2002-February/001918.html</TD><TD>&nbsp</TD></TR>
 <TR><TD>m.in.ntf</TD><TD>src/misc/m.in.ntf/cmd/open_vector.c</TD>			<TD>-</TD><TD>-</TD><TD>-</TD><TD>not used in 5.0</TD><TD>&nbsp</TD></TR>
 
 <TR><TD>NVIZ2.2</TD><TD>src.contrib/GMSL/NVIZ2.2/src/query_postgr_orig.c</TD>		<TD>X</TD><TD>&nbsp</TD><TD>&nbsp</TD>		<TD>use DBMI instead of Postgres</TD><TD>&nbsp</TD></TR>
@@ -259,12 +259,12 @@ before you start.
 <TR><TD>v.what</TD><TD>src/mapdev/v.what/cmd/main.c</TD>				<TD>-</TD><TD>-</TD><TD>-</TD><TD>this functionality is available in v.distance</TD><TD>&nbsp</TD></TR>
 </TABLE>
 
-<BR>
-<B>Y</B> : yes, updated <BR>
-<B>N</B> : no, not updated but necessary for 6.0.0 release <BR>
-<B>-</B> : no, not updated, irrelevant <BR>
-<B>X</B> : no, not updated and not expected to be updated for 6.0.0 release <BR>
-<B>?</B> : not sure if necessary for 6.0.0 release <BR>
+<br>
+<B>Y</B> : yes, updated <br>
+<B>N</B> : no, not updated but necessary for 6.0.0 release <br>
+<B>-</B> : no, not updated, irrelevant <br>
+<B>X</B> : no, not updated and not expected to be updated for 6.0.0 release <br>
+<B>?</B> : not sure if necessary for 6.0.0 release <br>
 
 </TABLE>
 

+ 22 - 22
doc/vector/vector.html

@@ -2,26 +2,26 @@
 <TITLE>GRASS 5.7/6 Vector Format and API</TITLE>
 </HEAD>
 <BODY>
-<P>
+<p>
 <H1>GRASS 5.7/6 Vector Format and API</H1>
 
 The API is described in
-<P>
+<p>
 <a href="http://grass.itc.it/devel/index.php#prog">GRASS 6 Programmer's Manual</a>
-<P>
+<p>
 
 source code file:<br>
 lib/vector/vectorlib.dox
 
 <HR>
 
-<H2><A NAME="ascii">Vector ASCII Format Specification</A></H2>
-<P>
+<h2><A NAME="ascii">Vector ASCII Format Specification</A></h2>
+<p>
 
 <i>format notes here are outdated and to be merged into<br>
 vector/v.in.ascii/description.html</i>
 
-<P>
+<p>
 The ASCII format in the new version contains support for categories,
 z-coordinates, and the new types centroid, face, and kernel.
 Points and centroids are saved as one coordinate pair instead of two.
@@ -29,7 +29,7 @@ File is saved in old dig_ascii directory but the name will be probably changed.
 
 <H3>Head</H3>
 The head of the file is similar as the head file of vector binary
-format but contains bounding box also. Key words are:<BR>
+format but contains bounding box also. Key words are:<br>
 <PRE>
 ORGANIZATION
 DIGIT DATE
@@ -65,23 +65,23 @@ TYPE NUMBER_OF_COORDINATES [NUMBER_OF_CATEGORIES]
 Everything above in <B>[ ]</B> is optional.
 Note the coordinate order in the old version (Y X) has been changed
 to (X Y [Z]).
-<BR><BR>
+<br><br>
 
-TYPE may be:<BR>
+TYPE may be:<br>
 <ul>
-<li><B>P</B> point (dot) <BR> 
-<li><B>p</B> dead point (dead dot) <BR> 
-<li><B>L</B> line  <BR>
-<li><B>l</B> dead line <BR> 
-<li><B>B(A)</B> boundary  <BR>
-<li><B>b(a)</B> dead boundary  <BR>
-<li><B>C</B> centroid  <BR>
-<li><B>c</B> dead centroid  <BR>
-<li><B>F</B> face (3D boundary) <BR>
-<li><B>K</B> kernel (3D centroid) <BR>
+<li><B>P</B> point (dot) <br> 
+<li><B>p</B> dead point (dead dot) <br> 
+<li><B>L</B> line  <br>
+<li><B>l</B> dead line <br> 
+<li><B>B(A)</B> boundary  <br>
+<li><B>b(a)</B> dead boundary  <br>
+<li><B>C</B> centroid  <br>
+<li><B>c</B> dead centroid  <br>
+<li><B>F</B> face (3D boundary) <br>
+<li><B>K</B> kernel (3D centroid) <br>
 </ul>
 
-<BR>
+<br>
 Example of records:
 <PRE>
 P 1 1
@@ -95,11 +95,11 @@ L 3 1
 </PRE>
 
 <HR>
-<H2><A NAME="example">Vector module programming example</A></H2>
+<h2><A NAME="example">Vector module programming example</A></h2>
 
 <a href=v.example/>Vector module C programming example</a>
 
-<H2><A NAME="status">Vector module upgrade status</A></H2>
+<h2><A NAME="status">Vector module upgrade status</A></h2>
 
 <a href=v.modules.html>Vector upgrade status</a> (partially outdated)
 

+ 15 - 15
general/g.access/g.access.html

@@ -1,44 +1,44 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
 This program allows the user to control access to the
 current mapset.  Normally, any user can read data from any
 GRASS mapset. But sometimes it is desirable to prohibit
-access to certain sensitive data. The <EM>g.access</EM>
+access to certain sensitive data. The <em>g.access</em>
 command allows a user to restrict read and execute access
-to the current mapset (see UNIX <EM>chmod</EM> command).
-<EM>g.access</EM> will not modify write access to the
+to the current mapset (see UNIX <em>chmod</em> command).
+<em>g.access</em> will not modify write access to the
 current mapset.
 
-<P>
+<p>
 
 The user may, for example, allow only users in the same
 UNIX group to read data files in the mapset, or restrict
 the mapset to personal use only.
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 
 
-<P> Under GRASS, access to the mapset PERMANENT must be open to
+<p> Under GRASS, access to the mapset PERMANENT must be open to
 all users.  This is because GRASS looks for the user's default geographic
 region definition settings and the location TITLE in files that are stored
-under the PERMANENT mapset directory.  The <EM>g.access</EM> command,
+under the PERMANENT mapset directory.  The <em>g.access</em> command,
 therefore, will not allow you to restrict access to the PERMANENT mapset.
 
-<P>
-The <EM><A HREF="g.mapsets.html">g.mapsets</A></EM> command isn't smart
+<p>
+The <em><a href="g.mapsets.html">g.mapsets</A></em> command isn't smart
 enough to tell if access to a specified mapset is restricted, and the user
 is therefore allowed to include the names of restricted mapsets in his
 search path.  However, the data in a restricted mapset is still protected;
 any attempts to look for or use data in a restricted mapset will fail.  The
 user will simply not see any data listed for a restricted mapset.
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
-UNIX manual entries for <EM>chmod</EM> and <EM>group</EM> 
-<BR>
-<EM><A HREF="g.mapsets.html">g.mapsets</A></EM> 
+UNIX manual entries for <em>chmod</em> and <em>group</em> 
+<br>
+<em><a href="g.mapsets.html">g.mapsets</A></em> 
 
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
 
 Michael Shapiro, 
 U.S. Army Construction Engineering Research Laboratory

+ 2 - 2
general/g.cairocomp/g.cairocomp.html

@@ -1,9 +1,9 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
 g.cairocomp is similar to g.pnmcomp, except that it works with X
 Pixmaps instead of PNM files.
 
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
 Glynn Clements
 
 <p><i>Last changed: $Date$</i>

+ 7 - 7
general/g.copy/g.copy.html

@@ -44,9 +44,9 @@ for the named <em>from</em> map in each of the mapset
 directories listed in the user's current mapset search path
 in the order in which mapsets are listed there (see 
 
-<em><a HREF="g.mapsets.html">g.mapsets</a></em>).
+<em><a href="g.mapsets.html">g.mapsets</a></em>).
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 
 If the user does not enter parameter values but instead
 types only <b>g.copy</b> on the command line the program
@@ -66,12 +66,12 @@ files), these support files will also be copied.
 
 <h2>SEE ALSO</h2>
 
-<em><a HREF="g.access.html">g.access</a></em><br>
+<em><a href="g.access.html">g.access</a></em><br>
 
-<em><a HREF="g.list.html">g.list</a></em><br>
-<em><a HREF="g.mapsets.html">g.mapsets</a></em><br>
-<em><a HREF="g.remove.html">g.remove</a></em><br>
-<em><a HREF="g.rename.html">g.rename</a></em>
+<em><a href="g.list.html">g.list</a></em><br>
+<em><a href="g.mapsets.html">g.mapsets</a></em><br>
+<em><a href="g.remove.html">g.remove</a></em><br>
+<em><a href="g.rename.html">g.rename</a></em>
 
 <h2>AUTHOR</h2>
 

+ 3 - 3
general/g.dirseps/g.dirseps.html

@@ -1,10 +1,10 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
-<EM>g.dirseps</EM> is an internal tool only. It copies input string
+<em>g.dirseps</em> is an internal tool only. It copies input string
 to stdout, changing directory separator characters as specified by flags.
 It is used for interoperability between Unix and MS-Windows pathnames.
 
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
 
 Paul Kelly
 

+ 23 - 23
general/g.filename/g.filename.html

@@ -1,4 +1,4 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
 <em>g.filename</em> is designed for Bourne shell scripts that need to know 
 the full file name, including it's path, for mapset elements, like raster,
@@ -13,41 +13,41 @@ g.remove/g.rename/g.copy use to determine which files need to be
 deleted/renamed/copied for a given entity type.
 
 <!-- unused
-<H2>OPTIONS</H2>
+<h2>OPTIONS</h2>
 
 <H3>Parameters:</H3>
 
 <DL>
-<DT><B>element=</B><EM>name</EM> 
+<DT><B>element=</B><em>name</em> 
 
 <DD>The name of a GRASS data base element (i.e., directory
 within the GRASS mapset location).
 
-<DT><B>mapset=</B><EM>name</EM> 
+<DT><B>mapset=</B><em>name</em> 
 
 <DD>The name of a GRASS data base mapset.  As a
 convenience, a single dot (.) can be used to designate the
 current mapset.
 
-<DT><B>file=</B><EM>name</EM> 
+<DT><B>file=</B><em>name</em> 
 
 <DD>The name of a GRASS data base file.
 </DL>
 -->
-<H2>OUTPUT</H2>
+<h2>OUTPUT</h2>
 
-<EM>g.filename</EM>
+<em>g.filename</em>
 writes one line to standard output:
 
 <DL>
 <DD>
-file='<EM>full_file_pathname'</EM>
+file='<em>full_file_pathname'</em>
 </DL>
 
-The output is a <EM>/bin/sh</EM> command to set the
-variable specified by the file <EM>name</EM> to the full
+The output is a <em>/bin/sh</em> command to set the
+variable specified by the file <em>name</em> to the full
 UNIX path name for the data base file.  This variable may
-be set in the <EM>/bin/sh</EM> as follows:
+be set in the <em>/bin/sh</em> as follows:
 
 <DL>
 <DD>
@@ -57,35 +57,35 @@ eval `g.filename element=<em>name</em> mapset=<em>name</em> file=<em>name</em>`
 </DL>
 
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 
 This routine generates the filename, but does not care if the file (or mapset
 or element) exists or not. This feature allows shell scripts to create new data
 base files as well as use existing ones.
 
-<P>
+<p>
 
-If the mapset is the current mapset, <EM>g.filename</EM>
-automatically creates the <EM>element</EM> specified if it
+If the mapset is the current mapset, <em>g.filename</em>
+automatically creates the <em>element</em> specified if it
 doesn't already exist.  This makes it easy to add new files
 to the data base without having to worry about the
 existence of the required data base directories.  (This
 program will not create a new mapset, however, if that
 specified does not currently exist.)
 
-<P>
+<p>
 The program exits with a 0 if everything is ok;  it exits
 with a non-zero value if there is an error, in which case
-file=<EM>'full_file_pathname'</EM> is not output.
+file=<em>'full_file_pathname'</em> is not output.
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
-<EM><A HREF="g.ask.html">g.ask</A></EM><br>
-<EM><A HREF="g.findfile.html">g.findfile</A></EM><br>
-<EM><A HREF="g.gisenv.html">g.gisenv</A></EM><br>
-<EM><A HREF="parser.html">parser</A></EM>
+<em><a href="g.ask.html">g.ask</A></em><br>
+<em><a href="g.findfile.html">g.findfile</A></em><br>
+<em><a href="g.gisenv.html">g.gisenv</A></em><br>
+<em><a href="parser.html">parser</A></em>
 
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
 
 Michael Shapiro,
 U.S.Army Construction Engineering Research Laboratory

+ 12 - 12
general/g.findetc/g.findetc.html

@@ -1,26 +1,26 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
-<EM>g.findetc</EM> is designed for Bourne shell scripts that need to search
+<em>g.findetc</em> is designed for Bourne shell scripts that need to search
 for support data, programs and subfoldrs in any number of directories as
 specified in GRASS_ADDON_ETC, plus the GRASS application etc/ directory. This
 is designed for addon scripts that are installed outside the GRASS application
 directory, such as a user's home or a system addon directory.
 <p>
 
-<H2>OUTPUT</H2>
+<h2>OUTPUT</h2>
 
-<EM>g.findetc</EM> writes the full path to the file or directory to standard output
+<em>g.findetc</em> writes the full path to the file or directory to standard output
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
-<EM><A HREF="g.ask.html">g.ask</A></EM><br>
-<EM><A HREF="g.filename.html">g.filename</A></EM><br>
-<EM><A HREF="g.findfile.html">g.findfile</A></EM><br>
-<EM><A HREF="g.gisenv.html">g.gisenv</A></EM><br>
-<EM><A HREF="g.mapsets.html">g.mapsets</A></EM><br>
-<EM><A HREF="parser.html">parser</A></EM>
+<em><a href="g.ask.html">g.ask</A></em><br>
+<em><a href="g.filename.html">g.filename</A></em><br>
+<em><a href="g.findfile.html">g.findfile</A></em><br>
+<em><a href="g.gisenv.html">g.gisenv</A></em><br>
+<em><a href="g.mapsets.html">g.mapsets</A></em><br>
+<em><a href="parser.html">parser</A></em>
 
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
 
 William Kyngesburye
 

+ 1 - 1
general/g.gui/g.gui.html

@@ -42,7 +42,7 @@ executed.
 
 <h2>AUTHORS</h2>
 
-Martin Landa, FBK-irst, Trento, Italy<BR>
+Martin Landa, FBK-irst, Trento, Italy<br>
 Hamish Bowman, Otago University, Dunedin, New Zealand (fine tuning)
 
 <p>

+ 5 - 5
general/g.list/g.list.html

@@ -9,7 +9,7 @@ and accessible files from <em>mapsets</em> under the user's current location.
 If unspecified, files of the specified <em>type</em> from all mapsets 
 in the user's current search path will be listed to standard output. To 
 find out which mapsets are in the cuurent search path, use 
-<em><a HREF="g.mapsets.html">'g.mapsets</a> -p'</em>.
+<em><a href="g.mapsets.html">'g.mapsets</a> -p'</em>.
 
 <p>
 If the <b>mapset</b> option is set to "." then only maps from the
@@ -18,7 +18,7 @@ current mapset will be displayed.
 <p>
 If the user requests that files from a mapset to which
 access has been restricted (see
-<em><a HREF="g.access.html">g.access</a></em>)
+<em><a href="g.access.html">g.access</a></em>)
 be listed, no files from this mapset will be listed.
 
 
@@ -41,9 +41,9 @@ List all raster and vector maps from mapset &quot;user&quot;:
 
 <h2>SEE ALSO</h2>
 
-<em><a HREF="g.access.html">g.access</a></em><br>
-<em><a HREF="g.mapsets.html">g.mapsets</a></em><br>
-<em><a HREF="g.mlist.html">g.mlist</a></em>
+<em><a href="g.access.html">g.access</a></em><br>
+<em><a href="g.mapsets.html">g.mapsets</a></em><br>
+<em><a href="g.mlist.html">g.mlist</a></em>
 
 
 <h2>AUTHOR</h2>

+ 5 - 5
general/g.mapset/g.mapset.html

@@ -5,18 +5,18 @@
 <h2>NOTES</h2>
 
 The shell continues to use the history for the old mapset. To change this 
-you can switch the history to the new settings by commands:<BR>
-<BR>
+you can switch the history to the new settings by commands:<br>
+<br>
 <div class="code"><pre>
    history -w
    history -r /$GISDBASE/$LOCATION/$MAPSET/.bash_history
    HISTFILE=/$GISDBASE/$LOCATION/$MAPSET/.bash_history
-</pre></div><BR>
+</pre></div><br>
 
 <h2>SEE ALSO</h2>
 
-<em><a HREF="g.gisenv.html">g.gisenv</a></em><br>
-<em><a HREF="g.mapsets.html">g.mapsets</a></em><br>
+<em><a href="g.gisenv.html">g.gisenv</a></em><br>
+<em><a href="g.mapsets.html">g.mapsets</a></em><br>
 
 <h2>AUTHOR</h2>
 

+ 9 - 9
general/g.mapsets/g.mapsets.html

@@ -1,7 +1,7 @@
 <h2>DESCRIPTION</h2>
 
 For basic information about Grass <em>mapset</em>, <em>location</em>
-and <em>data base</em> refer to <a HREF="helptext.html">GRASS Quickstart</a>.
+and <em>data base</em> refer to <a href="helptext.html">GRASS Quickstart</a>.
 
 <p>
 A <em>mapset</em> holds a distinct set of data layers,
@@ -53,7 +53,7 @@ accessed.
 <p>
 When the user specifies the name of a data base element file
 (e.g., a particular vector map, raster map, 
-<a HREF="i.group.html">imagery</a> group file, etc.)
+<a href="i.group.html">imagery</a> group file, etc.)
 to a GRASS program, the program searches for the named file
 under each of the mapsets listed in the user's mapset search path
 in the order listed there until the program finds a file
@@ -63,7 +63,7 @@ drawn;  e.g., the command:
 
 
 <div class="code"><pre>
-<b><a HREF="g.copy.html">g.copy</a> rast=</b><em>'soils.file@PERMANENT',my.soils</em>
+<b><a href="g.copy.html">g.copy</a> rast=</b><em>'soils.file@PERMANENT',my.soils</em>
 </pre></div>
 
 
@@ -109,7 +109,7 @@ The <em>addmapset</em> parameter allows for extending an existing
 Users can restrict others' access to their mapset files
 through use of the GRASS program
 
-<em><a HREF="g.access.html">g.access</a></em>.  
+<em><a href="g.access.html">g.access</a></em>.  
 
 Mapsets to which access is restricted can still be listed
 in another's mapset search path; however, access to these
@@ -118,11 +118,11 @@ mapsets will remain restricted.
 <h2>SEE ALSO</h2>
 
 <em>
-  <a HREF="g.access.html">g.access</a>,
-  <a HREF="g.copy.html">g.copy</a>,
-  <a HREF="g.gisenv.html">g.gisenv</a>,
-  <a HREF="g.list.html">g.list</a>,
-  <a HREF="g.mapset.html">g.mapset</a>
+  <a href="g.access.html">g.access</a>,
+  <a href="g.copy.html">g.copy</a>,
+  <a href="g.gisenv.html">g.gisenv</a>,
+  <a href="g.list.html">g.list</a>,
+  <a href="g.mapset.html">g.mapset</a>
 </em>
 
 <h2>AUTHOR</h2>

+ 10 - 10
general/g.message/g.message.html

@@ -6,43 +6,43 @@ need to use the <tt>echo</tt> program. The advantage of <em>g.message</em> is
 that it formats messages just like other GRASS modules do and that its
 functionality is influenced by the <tt>GRASS_VERBOSE</tt> and
 <tt>GRASS_MESSAGE_FORMAT</tt> environment variables.
-</p>
+
 <p>
 The program can be used for standard informative messages as well as warnings 
 (<b>-w</b> flag) and fatal errors (<b>-e</b> flag). For debugging
 purposes, the <b>-d</b> flag will cause <em>g.message</em> to print a debugging
 message at the given level.
-</p>
+
 
 <h2>NOTES</h2>
 
 Messages containing "<tt>=</tt>" must use the full <b>message=</b> syntax so
 the parser doesn't get confused.
-<P>
+<p>
 If you want a long message (multi-line) to be dealt with as a single
 paragraph, use a single call to <em>g.message</em> with text split in the
 script using the backslash as the last character. (In shell scripts don't
 close the "quote")
-<P>
+<p>
 A blank line may be obtained with: <tt>g.message ""</tt>
-<P>
+<p>
 Redundant whitespace will be stripped away.
-<P>
+<p>
 It's advisable to single quote the messages that are to be printed literally.
 It prevents a number of characters (most notably, space and the dollar sign
 '<tt>$</tt>') from being treated specifically by the Shell.
-<P>
+<p>
 When it is necessary to include, for example, a variable's value as part of
 the message, the double quotes may be used, which do not deprive the
 dollar sign of its special variable-expansion powers.
-<P>
+<p>
 While it is known that the interactive Bash instances may treat the
 exclamation mark '<tt>!</tt>' character specifically (making single quoting
 of it necessary), it shouldn't be the case for the non-interactive
 instances of Bash. None the less, to avoid context-based confusion later on
 you are enouraged to single-quote messages that do not require
 <tt>$VARIABLE</tt> expansion.
-<P>
+<p>
 
 <h3>VERBOSITY LEVELS</h3>
 Controlled by the "<tt>GRASS_VERBOSE</tt>" environment variable. Typically this
@@ -57,7 +57,7 @@ is set using the <tt>--quiet</tt> or <tt>--verbose</tt> command line options.
 <h3>DEBUG LEVELS</h3>
 Controlled by the "<tt>DEBUG</tt>" GRASS <i>gisenv</i> variable. (set with
 <em><a href="g.gisenv.html">g.gisenv</a></em>)
-<BR>
+<br>
 Recommended levels:
 <ul>
 <li>1 - message is printed once or few times per module

+ 5 - 5
general/g.mkfontcap/g.mkfontcap.html

@@ -1,7 +1,7 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
 <p>
-<EM>g.mkfontcap</EM> is a utilty to generate a GRASS font configuration file
+<em>g.mkfontcap</em> is a utilty to generate a GRASS font configuration file
 ("fontcap") containing details of the fonts available on the current system.
 If <a href="http://freetype.sourceforge.net/">Freetype</a> is not installed,
 the font list will be limited to the set of Hershey stroke fonts supplied
@@ -47,11 +47,11 @@ instead of the system copy.
 The output list of fonts is sorted first by type (Stroke fonts first,
 followed by Freetype) and within each type by the short name of the font.
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
  
-<EM><a href="d.font.html">d.font</a></EM>
+<em><a href="d.font.html">d.font</a></em>
 
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
 
 Paul Kelly
 

+ 2 - 2
general/g.mlist/g.mlist.html

@@ -3,8 +3,8 @@
 <em>g.mlist</em> searches for data files matching a pattern given by
 wildcards or POSIX Extended Regular Expressions.
 
-<P>
-See the <EM>g.list</EM> help page for discussion of module options.
+<p>
+See the <em>g.list</em> help page for discussion of module options.
 
 
 <h2>EXAMPLES</h2>

+ 1 - 1
general/g.mremove/g.mremove.html

@@ -14,7 +14,7 @@ Delete all raster maps starting with "<tt>tmp_</tt>" in the current mapset:
 
 <h2>SEE ALSO</h2>
 
-<em><a HREF="g.remove.html">g.remove</a></em>
+<em><a href="g.remove.html">g.remove</a></em>
 <p>
 <a href="http://en.wikipedia.org/wiki/Regular_expression">Regular expression</a> (from Wikipedia, the free encyclopedia)
 

+ 3 - 3
general/g.parser/g.parser.html

@@ -414,9 +414,9 @@ to the other examples above.
 <h2>SEE ALSO</h2>
 
 <em>
-  <a HREF="g.filename.html">g.filename</a>,
-  <a HREF="g.findfile.html">g.findfile</a>,
-  <a HREF="g.tempfile.html">g.tempfile</a>,
+  <a href="g.filename.html">g.filename</a>,
+  <a href="g.findfile.html">g.findfile</a>,
+  <a href="g.tempfile.html">g.tempfile</a>,
 </em>
 
 and the <tt>SUBMITTING_SCRIPTS</tt> file in the GRASS source code.

+ 2 - 2
general/g.pnmcat/g.pnmcat.html

@@ -1,4 +1,4 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 <p>
 Concatenate PNM tiles into a single image.
 <p>
@@ -18,7 +18,7 @@ in "P6" (binary PPM) format.
 <h2>SEE ALSO</h2>
 <em><a href="nviz.html">NVIZ</a></em>
 
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
 Glynn Clements
 
 <p><i>Last changed: $Date$</i>

+ 3 - 3
general/g.pnmcomp/g.pnmcomp.html

@@ -1,7 +1,7 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
 (culled from the mailing list)
-<BR>
+<br>
 <pre>
 From: Glynn Clements 
 Subject: Re: [GRASS5] Re: [GRASSLIST:10403] Transparency added
@@ -36,7 +36,7 @@ image composition routine in Tcl would be unacceptably slow, hence
 the existence of g.pnmcomp.
 </pre>
 
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
 Glynn Clements
 
 <p><i>Last changed: $Date$</i>

+ 3 - 3
general/g.ppmtopng/g.ppmtopng.html

@@ -1,8 +1,8 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
-<p>A utility to convert between PPM/PGM and PNG image formats.</p>
+<p>A utility to convert between PPM/PGM and PNG image formats.
 
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
 Glynn Clements
 
 <p><i>Last changed: $Date$</i>

+ 27 - 27
general/g.proj/g.proj.html

@@ -1,8 +1,8 @@
 <h2>DESCRIPTION</h2>
 
-<P><em>g.proj</em> provides a means of converting a co-ordinate system
+<p><em>g.proj</em> provides a means of converting a co-ordinate system
 description (i.e. projection information) between various formats.
-If compiled without <A HREF="http://www.gdal.org/ogr/">OGR</A> present, the 
+If compiled without <a href="http://www.gdal.org/ogr/">OGR</A> present, the 
 functionality is limited to:
 <ul>
 <li>Reporting the projection information for the current location, 
@@ -11,13 +11,13 @@ either in conventional GRASS (-p flag) or PROJ.4 (-j flag) format</li>
 the current location</li>
 </ul>
 
-<P>When compiled with OGR, functionality is increased and allows output of 
+<p>When compiled with OGR, functionality is increased and allows output of 
 the projection information in the Well-Known Text (WKT) format popularised 
 by proprietary GIS. In addition, if one of the parameters <em>georef</em>, 
 <em>wkt</em>, <em>proj4</em> or <em>epsg</em> is specified, rather than the 
 projection information being read from the current location it is imported 
 from an external source as follows:
-</P>
+
 <dl>
 <dt>georef=<em>filename</em></dt>
 <dd><em>g.proj</em> attempts to invoke GDAL and OGR in turn to read a
@@ -33,7 +33,7 @@ file.</dd>
 
 <dt>proj4=<em>description</em> or <em>-</em></dt>
 <dd><em>description</em> should be a projection description in 
-<A HREF="http://remotesensing.org/proj/">PROJ.4</a> format, enclosed in
+<a href="http://remotesensing.org/proj/">PROJ.4</a> format, enclosed in
 quotation marks if there are any spaces. If <em>-</em> is given for
 <em>description</em>, the PROJ.4 description will be read from stdin rather 
 than as a directly-supplied command-line parameter.</dd>
@@ -47,27 +47,27 @@ ${GISBASE}/etc/ogr_csv. These can be updated if necessary to support future
 revisions of the EPSG database.</dd>
 </dl>
 
-<P>The -p, -j, -w, etc. flags are all functional when importing projection
+<p>The -p, -j, -w, etc. flags are all functional when importing projection
 information from an external source, meaning that <em>g.proj</em> can be
 used to convert between representations of the information. It is
 <strong>not</strong> required that either the input or output be in GRASS
-format.</P>
+format.
 
-<P>In addition however, if the -c flag is specified, <em>g.proj</em> will 
+<p>In addition however, if the -c flag is specified, <em>g.proj</em> will 
 create new GRASS projection files (PROJ_INFO, PROJ_UNITS, WIND and 
 DEFAULT_WIND) based on the imported information. If the <em>location</em> 
 parameter is specified in addition to -c, then a new location will be created. 
 Otherwise the projection information files in the current location will be
-overwritten. The program will <strong>not</strong> warn before doing this.</P>
+overwritten. The program will <strong>not</strong> warn before doing this.
 
-<P>The final mode of operation of g.proj is to report on the datum
+<p>The final mode of operation of g.proj is to report on the datum
 information and datum transformation parameters associated with the
 co-ordinate system. The -d flag will report a human-readable summary of
-this.</P>
+this.
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 
-<P>If the input co-ordinate system contains a datum name but no
+<p>If the input co-ordinate system contains a datum name but no
 transformation parameters, and there is more than one suitable parameter set
 available (according to the files datum.table and datumtransform.table in
 ${GISBASE}/etc), g.proj will check the value of the <em>datumtrans</em>
@@ -84,20 +84,20 @@ If the <em>-t</em> flag is specified, the module will attempt to change the
 datum transformation parameters using one of the above two methods 
 <strong>even if</strong> a valid parameter set is already specified in the 
 input co-ordinate system. This can be useful to change the datum information
-for an existing location.</P>
+for an existing location.
 
-<P>Output is simply based on the input projection information. g.proj does 
+<p>Output is simply based on the input projection information. g.proj does 
 <strong>not</strong> attempt to verify that the co-ordinate system thus 
 described matches an existing system in use in the world. In particular,
-this means there are no EPSG Authority codes in the WKT output.</P>
+this means there are no EPSG Authority codes in the WKT output.
 
-<P>WKT format shows the false eastings and northings in the projected unit
-(e.g. meters, feet) but in PROJ format it should always be given in meters.</P>
+<p>WKT format shows the false eastings and northings in the projected unit
+(e.g. meters, feet) but in PROJ format it should always be given in meters.
 
-<P>The maximum size of input WKT or PROJ.4 projection descriptions is
-limited to 8000 bytes.</P>
+<p>The maximum size of input WKT or PROJ.4 projection descriptions is
+limited to 8000 bytes.
 
-<H2>EXAMPLES</H2>
+<h2>EXAMPLES</h2>
 
 Print the projection information for the current location:<br>
 
@@ -193,13 +193,13 @@ ogr2ogr -t_srs "`g.proj -wf`" polbnda_italy_GB_ovest.shp polbnda_italy_LL.shp
 </pre></div>
 
 
-<H2>REFERENCES</H2>
+<h2>REFERENCES</h2>
 
 <a href="http://proj.maptools.org">PROJ 4</a>: Projection/datum support library<br>
 <a href="http://www.gdal.org">GDAL raster library and toolset</a><br>
 <a href="http://www.gdal.org/ogr/">OGR vector library and toolset</a>
 
-<P>
+<p>
 <B>Further reading</B>
 <ul>
 <li> <a href="http://www.asprs.org/resources/grids/">ASPRS Grids and Datum</a>
@@ -207,11 +207,11 @@ ogr2ogr -t_srs "`g.proj -wf`" polbnda_italy_GB_ovest.shp polbnda_italy_LL.shp
 <li> <a href="http://www.remotesensing.org/geotiff/proj_list/">Projections Transform List</a> (PROJ4)
 </ul>
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
  
-<EM><a href="g.setproj.html">g.setproj</a></EM><BR>
-<EM><a href="r.in.gdal.html">r.in.gdal</a></EM><BR>
-<EM><a href="v.in.ogr.html">v.in.ogr</a></EM>
+<em><a href="g.setproj.html">g.setproj</a></em><br>
+<em><a href="r.in.gdal.html">r.in.gdal</a></em><br>
+<em><a href="v.in.ogr.html">v.in.ogr</a></em>
 
 <h2>AUTHOR</h2>
 

+ 8 - 8
general/g.region/g.region.html

@@ -43,7 +43,7 @@ current region settings. The north-south and east-west cell
 resolutions need not be the same, thus allowing non-square
 data cells to exist.
 
-<P>
+<p>
 Typically all raster and display modules are affected by the current
 region settings, but not vector modules.
 Some special modules diverge from this rule, for example raster import
@@ -123,7 +123,7 @@ averaged, the results finally printed.
 The <b>-p</b> (or <b>-g</b>) option is recognized
 last.  This means that all changes are applied to the
 region settings before printing occurs.
-<P>
+<p>
 The <b>-g</b> flag prints the current region settings in shell script style.
 This format can be given back to <em>g.region</em> on its command line.
 This may also be used to save region settings as shell environment variables
@@ -478,12 +478,12 @@ projection since it is reprojected on the fly.
 <h2>SEE ALSO</h2>
 
 <em>
-<a HREF="d.zoom.html">d.zoom</a><br>
-<a HREF="g.access.html">g.access</a><br>
-<a HREF="g.mapsets.html">g.mapsets</a><br>
-<a HREF="g.proj.html">g.proj</a><BR>
-<a HREF="g.setproj.html">g.setproj</a><BR>
-environment variables: <a HREF="variables.html#internal">GRASS_REGION and WIND_OVERRIDE</a>
+<a href="d.zoom.html">d.zoom</a><br>
+<a href="g.access.html">g.access</a><br>
+<a href="g.mapsets.html">g.mapsets</a><br>
+<a href="g.proj.html">g.proj</a><br>
+<a href="g.setproj.html">g.setproj</a><br>
+environment variables: <a href="variables.html#internal">GRASS_REGION and WIND_OVERRIDE</a>
 </em>
 
 

+ 4 - 4
general/g.remove/g.remove.html

@@ -11,7 +11,7 @@ the vector maps named <em>roads</em> and <em>rail</em>,
 and the
 
 
-<a HREF="i.group.html">imagery</a> group files
+<a href="i.group.html">imagery</a> group files
 
 named <em>nhap.1</em> and <em>nhap.2</em>, and these files'
 associated support files (e.g., cell header files, category
@@ -44,10 +44,10 @@ types whose files can be removed by the user.
 
 <h2>SEE ALSO</h2>
 
-<em><a HREF="g.copy.html">g.copy</a></em><br>
-<em><a HREF="g.list.html">g.list</a></em><br>
+<em><a href="g.copy.html">g.copy</a></em><br>
+<em><a href="g.list.html">g.list</a></em><br>
 
-<em><a HREF="g.rename.html">g.rename</a></em><br>
+<em><a href="g.rename.html">g.rename</a></em><br>
 <em>g.mremove</em> 
 
 <h2>AUTHOR</h2>

+ 3 - 3
general/g.rename/g.rename.html

@@ -72,9 +72,9 @@ g.rename rast=oldrast,newrast vect=oldvect,newvect
 </pre></div>
 <h2>SEE ALSO</h2>
 
-<em><a HREF="g.copy.html">g.copy</a></em><br>
-<em><a HREF="g.list.html">g.list</a></em><br>
-<em><a HREF="g.remove.html">g.remove</a></em>
+<em><a href="g.copy.html">g.copy</a></em><br>
+<em><a href="g.list.html">g.list</a></em><br>
+<em><a href="g.remove.html">g.remove</a></em>
 
 <h2>AUTHOR</h2>
 

+ 30 - 30
general/g.setproj/g.setproj.html

@@ -9,68 +9,68 @@
 
 <img src="grass_logo.png" alt="GRASS logo"><hr align=center size=6 noshade>
 
-<H2>NAME</H2>
+<h2>NAME</h2>
 
-<EM><b>g.setproj</b></EM>  - Allows the user to create the PROJ_INFO and the 
+<em><b>g.setproj</b></em>  - Allows the user to create the PROJ_INFO and the 
 PROJ_UNITS files to record the projection information associated with a 
 current location. 
-<BR>
+<br>
 
-<H2>SYNOPSIS</H2>
+<h2>SYNOPSIS</h2>
 
 <B>g.setproj</B> 
 
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
 Allows a user to create a PROJ_INFO file in the PERMANENT mapset of the 
 current location. PROJ_INFO file is used to record the projection information 
 associated with the specified mapset. 
 
-<H2>NOTES</H2> 
+<h2>NOTES</h2> 
 
-The user running <EM>g.setproj</EM> must own the PERMANENT 
+The user running <em>g.setproj</em> must own the PERMANENT 
 mapset and it must be currently selected.
-It is highly recommended to run <EM>g.setproj</EM> after
+It is highly recommended to run <em>g.setproj</em> after
 creating a new location so that conversion programs (such
-as <EM>v.proj</EM>) can be run.
+as <em>v.proj</em>) can be run.
 
-<P>The user will be prompted for the projection name. 
+<p>The user will be prompted for the projection name. 
 Most projections are supported. The 
-<A HREF="http://proj.maptools.org/">PROJ.4</A> abbreviations for the names are
+<a href="http://proj.maptools.org/">PROJ.4</A> abbreviations for the names are
 used with two exceptions, viz. 'll', for latitude / longitude geographic
 co-ordinates, and 'stp', for the State Plane Co-ordinate system (used in the
-USA).</P>
+USA).
 
-<P>After the projection name, the user will be asked for a geodetic datum. If 
+<p>After the projection name, the user will be asked for a geodetic datum. If 
 no datum transformation support is needed, the question may be answered with no,
 and no datum will be specified in the PROJ_INFO file. If this is the case
 the user must specify the ellipsoid (model of the curvature of the earth) to
-be used, otherwise it is determined by the datum being used.</P>
+be used, otherwise it is determined by the datum being used.
 
-<P>If the datum or ellipsoid required are not 
+<p>If the datum or ellipsoid required are not 
 listed within this program, the user/administrator may add the definition 
 to the files datum.table, datumtransform.table and ellipse.table in the
-$GISBASE/etc/ directory.</P>
+$GISBASE/etc/ directory.
 
-<P>Depending on the projection selected, the user will then be prompted for
-the various other parameters required to define it.</P>
+<p>Depending on the projection selected, the user will then be prompted for
+the various other parameters required to define it.
 
-<P>
+<p>
 
 The projections of aea, lcc, merc, leae, leac, and 
 tmerc will generate a request to the user for the prime meridian and standard 
 parallel for the output map. 
 
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
-<EM><A HREF="g.proj.html">g.proj</A></EM>,
-<EM><A HREF="m.proj.html">m.proj</A></EM>,
-<EM><A HREF="r.proj.html">r.proj</A></EM>,
-<EM><A HREF="v.proj.html">v.proj</A></EM>,
-<EM><A HREF="http://proj.maptools.org">PROJ.4</A></EM>
+<em><a href="g.proj.html">g.proj</A></em>,
+<em><a href="m.proj.html">m.proj</A></em>,
+<em><a href="r.proj.html">r.proj</A></em>,
+<em><a href="v.proj.html">v.proj</A></em>,
+<em><a href="http://proj.maptools.org">PROJ.4</A></em>
 
-<P>
+<p>
 <B>Further reading</B>
 <ul>
 <li> A guide to <a href="http://erg.usgs.gov/isb/pubs/MapProjections/projections.html">Map Projections</a> by USGS
@@ -79,17 +79,17 @@ parallel for the output map.
 <li> <a href="http://www.remotesensing.org/geotiff/proj_list/">Projections Transform List</a> (PROJ4)
 </ul>
 
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
 
 Irina Kosinovsky, 
 U.S. Army Construction Engineering 
-Research Laboratory<BR>
-Morten Hulden, morten at untamo.net - rewrote module and added 121 projections <BR>
+Research Laboratory<br>
+Morten Hulden, morten at untamo.net - rewrote module and added 121 projections <br>
 Andreas Lange, andreas.lange at rhein-main.de - added prelimnary map datum support
 
 <p>
 <i>Last changed: $Date$</i>
-</p>
+
 
 </body>
 </html>

+ 11 - 11
general/g.tempfile/g.tempfile.html

@@ -1,6 +1,6 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
-<EM>g.tempfile</EM>
+<em>g.tempfile</em>
 is designed for shell scripts that need to use large temporary files. 
 GRASS provides a mechanism for temporary files that does not depend on 
 /tmp. GRASS temporary files are created in the data base with the assumption 
@@ -8,17 +8,17 @@ that there will be enough space under the data base for large files.
 GRASS periodically removes temporary files that have been left behind 
 by programs that failed to remove them before terminating. 
 
-<P>
+<p>
 
-<EM>g.tempfile</EM>
+<em>g.tempfile</em>
 creates an unique file and prints the name. The user is required to provide 
 a process-id which will be used as part of the name of the file. 
 Most Unix shells provide a way to get the process id of the current shell. 
 For /bin/sh and /bin/csh this is $$. 
 It is recommended that $$ be specified as the process-id for 
-<EM>g.tempfile</EM>.
+<em>g.tempfile</em>.
 
-<H2>EXAMPLE</H2>
+<h2>EXAMPLE</h2>
 
 For /bin/sh scripts the following syntax should be used: 
 <div class="code"><PRE>
@@ -31,20 +31,20 @@ set temp1=`g.tempfile pid=$$`
 set temp2=`g.tempfile pid=$$`
 </PRE></div>
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 
-Each call to <EM>g.tempfile</EM>
+Each call to <em>g.tempfile</em>
 creates a different (i.e. unique) name. 
 
 Although GRASS does eventually get around to removing
 tempfiles that have been left behind, the programmer should
 make every effort to remove these files. They often get
 large and take up disk space. If you write /bin/sh scripts,
-learn to use the /bin/sh <EM>trap</EM> command. If you
+learn to use the /bin/sh <em>trap</em> command. If you
 write /bin/csh scripts, learn to use the /bin/csh
-<EM>onintr</EM> command.
+<em>onintr</em> command.
 
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
 
 Michael Shapiro, 
 U.S. Army Construction Engineering 

+ 6 - 6
imagery/i.albedo/i.albedo.html

@@ -1,18 +1,18 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
-<EM>i.albedo</EM> calculates the Albedo, that is the Shortwave surface
+<em>i.albedo</em> calculates the Albedo, that is the Shortwave surface
 reflectance in the range of 0.3-3 micro-meters.  It takes input of
 individual bands of surface reflectance from Modis, AVHRR, Landsat or
 Aster and calculates the Albedo for those.  This is an precursor to
 r.sun and any Energy-Balance processing.
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 It assumes MODIS product surface reflectance in [0;10000]
 
-<H2>TODO</H2>
+<h2>TODO</h2>
 Maybe change input requirement of MODIS to [0.0-1.0]?
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
 <em>
   <a href="r.sun.html">r.sun</a>,
@@ -20,7 +20,7 @@ Maybe change input requirement of MODIS to [0.0-1.0]?
 </em>
 
 
-<H2>AUTHORS</H2>
+<h2>AUTHORS</h2>
 
 Yann Chemin, International Rice Research Institute, The Philippines
 

+ 9 - 9
imagery/i.aster.toar/i.aster.toar.html

@@ -1,10 +1,10 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
-<EM>i.aster.toar</EM> calculates the Top Of Atmosphere (TOA) reflectance for Terra-Aster L1B in the visible, NIR and SWIR bands (9+1 bands) and brigthness temperature for the TIR bands (5 bands), all from L1B DN values. 
+<em>i.aster.toar</em> calculates the Top Of Atmosphere (TOA) reflectance for Terra-Aster L1B in the visible, NIR and SWIR bands (9+1 bands) and brigthness temperature for the TIR bands (5 bands), all from L1B DN values. 
 It is useful after importing your Aster imagery from storage format that is generally in standard DN values range.
 The order of input bands is VNIR: 1,2,3N,3B, SWIR: 4,5,6,7,8,9 TIR: 10,11,12,13,14 in one comma-separated list.
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 Internally, a gain code is defined to modify gains according to spectral bands following the GeoSystems GmbH ATCOR Ver. 2.0 Calibration Files. The function is defined in gain_aster.c file.
 
 <div class="code"><pre>
@@ -15,19 +15,19 @@ Internally, a gain code is defined to modify gains according to spectral bands f
     /*3 - Low 2(Not Applicable for Band 1-3N/B and 10-14)*/
 </pre></div>
 
-<H2>TODO</H2>
+<h2>TODO</h2>
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
 <em>
-<A HREF="i.landsat.toar.html">i.landsat.toar</A><br>
-<A HREF="r.in.aster.html">r.in.aster</A><br>
+<a href="i.landsat.toar.html">i.landsat.toar</A><br>
+<a href="r.in.aster.html">r.in.aster</A><br>
 </em>
 
 
-<H2>AUTHORS</H2>
+<h2>AUTHORS</h2>
 
-Yann Chemin, CSU, Australia<BR>
+Yann Chemin, CSU, Australia<br>
 
 
 <p>

+ 9 - 9
imagery/i.biomass/i.biomass.html

@@ -1,6 +1,6 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
-<EM>i.biomass</EM> Calculates the biomass growth for a day after [1][2]. 
+<em>i.biomass</em> Calculates the biomass growth for a day after [1][2]. 
 
 Input:
 <ul>
@@ -12,28 +12,28 @@ Input:
  <li>Water availability [0.0-1.0], possibly using direct output from i.eb.evapfr.
 </ul>
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 It can use the output of i.eb.evapfr directly as water availability input.
 
-<H2>TODO</H2>
+<h2>TODO</h2>
 remove Latitude, DOY and Tsw from input and replace with a raster input compatible with r.sun output.
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
 <em>
-<A HREF="i.eb.evapfr">i.eb.evapfr</A><br>
+<a href="i.eb.evapfr">i.eb.evapfr</A><br>
 </em>
 
-<H2>REFERENCES</H2>
+<h2>REFERENCES</h2>
 
   <p>[1] Bastiaanssen, W.G.M., Ali, S., 2002. A new crop yield forecasting model based on satellite measurements applied across the Indus Basin, Pakistan. Agriculture, Ecosystems and Environment, 94(3):321-340. 
 
   <p>[2] Chemin, Y., Platonov, A., Abdullaev, I., Ul-Hassan, M. 2005. Supplementing farm level water productivity assessment by remote sensing in transition economies. Water International. 30(4):513-521.
 
 
-<H2>AUTHORS</H2>
+<h2>AUTHORS</h2>
 
-Yann Chemin, Bec de Mortagne, France<BR>
+Yann Chemin, Bec de Mortagne, France<br>
 
 
 <p>

+ 22 - 22
imagery/i.cca/i.cca.html

@@ -1,4 +1,4 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
 
 <B>i.cca</B> is an image processing program that takes from two to eight
@@ -10,17 +10,17 @@ the <a href="http://dbwww.essc.psu.edu/lasdoc/user/canal.html">LAS image
 processing system</a>. CCA is also known as "Canonical components
 transformation".
 
-<P>
+<p>
 
 Typically the user will use the 
-<EM><A HREF="i.class.html">i.class</A></EM> 
+<em><a href="i.class.html">i.class</A></em> 
 program to collect a set of signatures and then pass those
 signatures along with the raster band files to
-<EM>i.cca</EM>.  The raster band file names are specified
+<em>i.cca</em>.  The raster band file names are specified
 on the command line by giving the group and subgroup that
 were used to collect the signatures.
 
-<P>
+<p>
 
 The output raster map names are built by appending a ".1",
 ".2", etc. to the output raster map name specified on the
@@ -30,52 +30,52 @@ command line.
 
 <DL>
 
-<DT><B>group=</B><EM>name</EM> 
+<DT><B>group=</B><em>name</em> 
 
-<DD>Name of the <A HREF="i.group.html">imagery</A> group
+<DD>Name of the <a href="i.group.html">imagery</A> group
 to which the 2 to 8 raster band files used belong.
 
-<DT><B>subgroup=</B><EM>name</EM> 
+<DT><B>subgroup=</B><em>name</em> 
 
-<DD>Name of the <A HREF="i.group.html">imagery</A>
+<DD>Name of the <a href="i.group.html">imagery</A>
 subgroup to which the 2 to 8 raster band files used
 belong.
 
-<DT><B>signature=</B><EM>name</EM> 
+<DT><B>signature=</B><em>name</em> 
 
 <DD>Name of an ASCII file containing spectral signatures.
 
-<DT><B>output=</B><EM>name</EM> 
+<DT><B>output=</B><em>name</em> 
 
 <DD>Output raster map prefix name.  The output raster map
 layer names are built by appending a ".1", ".2", etc. onto
-the <EM>output</EM> name specified by the user.
+the <em>output</em> name specified by the user.
 
 </DL>
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 
-<EM>i.cca</EM> respects the current geographic region definition
+<em>i.cca</em> respects the current geographic region definition
 and the current mask setting while performing the transformation.
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
 Schowengerdt, Robert A.  <B>Techniques for Image Processing and
 Classification in Remote Sensing</B>,  Academic Press, 1983.
 
-<P>
+<p>
 
-<EM><A HREF="i.class.html">i.class</A></EM><br>
-<EM><A HREF="i.pca.html">i.pca</A></EM><br>
-<EM><A HREF="r.covar.html">r.covar</A></EM><br>
-<EM><A HREF="r.mapcalc.html">r.mapcalc</A></EM>
+<em><a href="i.class.html">i.class</A></em><br>
+<em><a href="i.pca.html">i.pca</A></em><br>
+<em><a href="r.covar.html">r.covar</A></em><br>
+<em><a href="r.mapcalc.html">r.mapcalc</A></em>
 
-<H2>AUTHORS</H2>
+<h2>AUTHORS</h2>
 
 David Satnik, GIS Laboratory, 
 Central Washington University
 
-<BR>
+<br>
 
 Ali R. Vali, 
 University of Texas

+ 102 - 102
imagery/i.class/i.class.html

@@ -1,16 +1,16 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
-<EM>i.class</EM>
+<em>i.class</em>
 performs the first pass in the GRASS two-pass supervised image
 classification process;
 the GRASS program 
-<EM><A HREF="i.maxlik.html">i.maxlik</A></EM> executes the second pass.
+<em><a href="i.maxlik.html">i.maxlik</A></em> executes the second pass.
 Both programs must be run to generate a classified map in GRASS
 raster format.
 
-<P>
+<p>
 
-<EM>i.class</EM> is an interactive program that allows the user to outline
+<em>i.class</em> is an interactive program that allows the user to outline
 a region on the screen and calculate the spectral signature based on the
 cells that are within that region.  During this process the user will be
 shown a histogram of the region for each image band.  The user can also
@@ -20,38 +20,38 @@ By doing this, the user can see how much of the image
 is likely to be put into the class associated with the current signature.
 
 
-<P>
+<p>
 
 The spectral signatures that result are composed of region means and
 covariance matrices.  These region means and covariance matrices are used in
-the second pass (<EM><A HREF="i.maxlik.html">i.maxlik</A></EM>) to classify
+the second pass (<em><a href="i.maxlik.html">i.maxlik</A></em>) to classify
 the image.
 
 
-<P>
+<p>
 
-Alternatively, the spectral signatures generated by <EM>i.class</EM> can be
+Alternatively, the spectral signatures generated by <em>i.class</em> can be
 used for seed means for the clusters in the
-<EM><A HREF="i.cluster.html">i.cluster</A></EM> program.
+<em><a href="i.cluster.html">i.cluster</A></em> program.
 
 
-<H2>USER INPUTS</H2>
+<h2>USER INPUTS</h2>
 
 At the command line the user is asked to enter the name of the raster map
 to be displayed during the process of outlining regions.
 Typically, the user will want to enter the name of a color
 composite previously created by
-<EM><A HREF="r.composite.html">r.composite</A></EM>.
+<em><a href="r.composite.html">r.composite</A></em>.
 
 However, the user can enter the name of any existing raster
 map.  This leaves the potential for using a raster map not
 directly derived from the image as a backdrop on which the
 user can outline the classes of interest.
 
-<P>
+<p>
 
-The first screen in the program <EM>i.class</EM> asks the user for the
-<A HREF="i.group.html">imagery</A> <EM>group</EM> and <EM>subgroup</EM>
+The first screen in the program <em>i.class</em> asks the user for the
+<a href="i.group.html">imagery</A> <em>group</em> and <em>subgroup</em>
 to be analyzed:
 
 
@@ -68,45 +68,45 @@ SUBGROUP:   123________   (list will show available subgroups)
                    (OR &lt;Ctrl-C&gt; TO CANCEL)
 </PRE></div>
 
-<P>
+<p>
 
-The <EM>group</EM> should contain the 
+The <em>group</em> should contain the 
 imagery bands that the user wishes
-to classify.  The <EM>subgroup</EM> is a subset of this group.
+to classify.  The <em>subgroup</em> is a subset of this group.
 The user must create a group and a subgroup by running the GRASS program
 
-<EM><A HREF="i.group.html">i.group</A></EM> 
-before running <EM>i.class</EM>.  The subgroup should contain
+<em><a href="i.group.html">i.group</A></em> 
+before running <em>i.class</em>.  The subgroup should contain
 only the image bands that the user wishes to classify.
 Note that this subgroup must contain more than one band.
 
-<P>
+<p>
 
 After the first screen, the program asks the user for the name of the
 resulting signature file.  The signature file is both the output file for
-<EM>i.class</EM> and the required input file for the GRASS 
-<EM><A HREF="i.maxlik.html">i.maxlik</A></EM> module.
+<em>i.class</em> and the required input file for the GRASS 
+<em><a href="i.maxlik.html">i.maxlik</A></em> module.
 It contains the region means and covariance matrices that are used to
-classify an image in  <EM><A HREF="i.maxlik.html">i.maxlik</A></EM>.
+classify an image in  <em><a href="i.maxlik.html">i.maxlik</A></em>.
 The signature file will be saved in the
 <tt>$MAPSET/group/$GROUP/subgroup/$SUBGROUP/sig/</tt> directory.
 
-<P>
+<p>
 
 After entering the resulting signature file name, the user
 is asked to enter the name of a seed signature file.  This
 is optional.  A "seed" signature file is a previously
 created signature file.  Such a seed signature file may be
-the result of an earlier run of <EM>i.class</EM>.  The seed
+the result of an earlier run of <em>i.class</em>.  The seed
 signature file is copied into the new resulting signature
 file before any new signatures are added by
-<EM>i.class</EM>.  In this way, you can collect the work
-from several sessions with <EM>i.class</EM> into one
+<em>i.class</em>.  In this way, you can collect the work
+from several sessions with <em>i.class</em> into one
 signature file.
 
-<P>
+<p>
 
-At this point the <EM>i.class</EM> graphics screen will be
+At this point the <em>i.class</em> graphics screen will be
 drawn on the graphics monitor and the user will be directed
 to use the mouse.  From this point on the user will
 primarily work with the mouse, selecting options from the
@@ -114,9 +114,9 @@ menus and outlining regions on the screen.  The only time
 that the user will need to return to the text terminal is
 to enter names for the signatures created.
 
-<H2>THE DISPLAY FRAMES</H2>
+<h2>THE DISPLAY FRAMES</h2>
 
-The display frame layout that <EM>i.class</EM> uses is
+The display frame layout that <em>i.class</em> uses is
 represented below for reference.
 
 <div class="code"><PRE>
@@ -145,9 +145,9 @@ represented below for reference.
 </PRE></div>
 
 
-<H2>THE MENUS</H2>
+<h2>THE MENUS</h2>
 
-All of the menus in the <EM>i.class</EM> program are
+All of the menus in the <em>i.class</em> program are
 displayed across the bottom of the graphics monitor in the
 Menu Frame.  To select an option from one of these menus,
 simply place the cursor over your selection and press any
@@ -162,7 +162,7 @@ The Command Menu includes the following selections:
 
 <DL>
 
-<DT><EM>Zoom</EM> 
+<DT><em>Zoom</em> 
 
 <DD>This command allows the user to outline a rectangular
 region in either the Map or Zoom Display Frames and the
@@ -170,7 +170,7 @@ region is displayed, magnified, to fit in the Zoom Display
 Frame.  A red rectangle is drawn in the Map Display Frame,
 indicating what area the Zoom Display Frame shows.
 
-<P>
+<p>
 
 To outline the rectangular region simply use any mouse button to anchor
 the first corner of the border and then use any button to choose the
@@ -178,24 +178,24 @@ other corner.
 
 
 
-<DT><EM>Define region</EM>  
+<DT><em>Define region</em>  
 
 <DD>This selection takes the user to the
-<A HREF="#regionmenu">Region Menu</A>.
+<a href="#regionmenu">Region Menu</A>.
 This menu includes the
 options that allow the user to outline a region of interest
 on the displayed raster map.
 
 
-<DT><EM>Redisplay map</EM> 
+<DT><em>Redisplay map</em> 
 
 <DD>This selection takes the user to the Redisplay Menu.
 The 
-<A HREF="#redisplaymenu">Redisplay Menu</A> 
+<a href="#redisplaymenu">Redisplay Menu</A> 
 allows the user to redraw map display
 frames.
 
-<DT><EM>Analyze region</EM>  
+<DT><em>Analyze region</em>  
 
 <DD>This selection starts the process of analyzing the
 currently defined region.  A histogram of the defined
@@ -208,11 +208,11 @@ data will not fit.  In this case, as much of the data as
 possible, centered around the mean, will be displayed.
 After the histograms are displayed, the user will be given
 the 
-<A HREF="#signaturemenu">Signature Menu</A>.
+<a href="#signaturemenu">Signature Menu</A>.
 
-<DT><EM>Quit</EM> 
+<DT><em>Quit</em> 
 <DD>The user should make this selection 
-to end the session with <EM>i.class</EM>.
+to end the session with <em>i.class</em>.
 
 </DL>
 
@@ -223,11 +223,11 @@ The Region Menu contains the following selections:
 
 <DL>
 
-<DT><EM>Erase region</EM>  
+<DT><em>Erase region</em>  
 <DD>This selection erases any currently defined
 region.
 
-<DT><EM>Draw region</EM>  
+<DT><em>Draw region</em>  
 <DD>This selection allows the user to use the mouse to
 draw a region on either the Map or Zoom Display Frame.  An
 explanation of which mouse buttons to use is displayed in the Menu
@@ -236,21 +236,21 @@ last line of the region will be added when the user selects the
 Complete region option on the Region Menu.
 
 
-<DT><EM>Restore last region</EM> 
+<DT><em>Restore last region</em> 
 <DD>This selection restores the last region
 that was drawn.  After a region is completed, it will be saved to be
 restored later.  Only one previous region is saved.
 
-<DT><EM>Complete region</EM> 
+<DT><em>Complete region</em> 
 <DD>This selection completes the region that is
 currently being drawn.  As noted above, it saves the complete
 region to be restored later, if needed.  Once the user has made a
 complete region, it can be analyzed with the Analyze Region
-selection on the <A HREF="#commandmenu">Command Menu</A>.
+selection on the <a href="#commandmenu">Command Menu</A>.
 
-<DT><EM>Done</EM> 
+<DT><em>Done</em> 
 <DD>Use this selection to return to the 
-<A HREF="#commandmenu">Command Menu</A>.
+<a href="#commandmenu">Command Menu</A>.
 
 </DL>
 
@@ -262,23 +262,23 @@ to redraw the raster maps displayed in the Map and Zoom Display Frames.
 
 <DL>
 
-<DT><EM>Map geographic region</EM> 
+<DT><em>Map geographic region</em> 
 <DD>This selection causes the raster map in the Map
 Display Frame to be redrawn.
 
-<DT><EM>Zoom region</EM> 
+<DT><em>Zoom region</em> 
 <DD>This selection causes the Zoom Display Frame to
 be redrawn.
 
 
-<DT><EM>Both</EM> 
+<DT><em>Both</em> 
 <DD>This selection causes both the Map and Zoom Display
 Frames to be redrawn.
 
-<DT><EM>Cancel</EM> 
+<DT><em>Cancel</em> 
 <DD>Use this selection if you do not want to redisplay
 either of the above regions.  The user will be returned to the 
-<A HREF="#commandmenu">Command Menu</A>.
+<a href="#commandmenu">Command Menu</A>.
 
 </DL>
 
@@ -297,7 +297,7 @@ following selections are available on the Signature Menu:
 
 <DL>
 
-<DT><EM>Set std dev's</EM> 
+<DT><em>Set std dev's</em> 
 
 <DD>This selection allows the user to set the number of
 standard deviations from the mean for the maximum and
@@ -312,13 +312,13 @@ histograms for each band will be redrawn with the maximum
 and minimum range marked.
 
 
-<P>
+<p>
 
 Note that the number in parentheses on this
 selection is the current number of standard deviations.
 
 
-<DT><EM>Set color</EM> 
+<DT><em>Set color</em> 
 
 <DD>This selection allows the user to set the color for the
 display of cells that "match" the current signature.  The
@@ -326,12 +326,12 @@ user is presented with a menu of color choices.  The color
 selected will be used when the Display Matches Menu
 selection is made.
 
-<P>
+<p>
 
 Note that the color in parentheses on this selection is the current
 color for display.
 
-<DT><EM>Display matches</EM> 
+<DT><em>Display matches</em> 
 
 <DD>This selection displays the cells that "match" the
 current signature in the current color.  A cell "matches"
@@ -340,15 +340,15 @@ between the minimum range and maximum range for that band
 defined by the number of standard deviations currently
 set.
 
-<DT><EM>Done</EM> 
+<DT><em>Done</em> 
 
 <DD>When this selection is chosen, the user will be asked
 whether or not he/she would like to save the current
 signature.  If the user answers with the "Yes" selection,
 he/she will be asked to enter a description for the
 resultant signature file on the text terminal keyboard.
-The saved signature file description will be used by <EM>
-<A HREF="i.maxlik.html">i.maxlik</A></EM> to name the
+The saved signature file description will be used by <em>
+<a href="i.maxlik.html">i.maxlik</A></em> to name the
 category that is created from the current signature.  After
 either a "No" answer or the signature description is
 entered, the user is returned to the Command Menu.
@@ -356,74 +356,74 @@ entered, the user is returned to the Command Menu.
 </DL>
 
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 
-<EM>i.class</EM> uses the current MASK to generate the
+<em>i.class</em> uses the current MASK to generate the
 overlay for cells that match a signature.  As a result, if
 a MASK already exists it will be removed during the
 execution of this program.
 
-<P>
+<p>
 The cell values in the image bands cannot fall outside of
-the range of 0 to 255.  <EM>i.class</EM> will report an
+the range of 0 to 255.  <em>i.class</em> will report an
 error if they do.
 
-<P>
-<EM>i.class</EM>, like some of the other 
-<A HREF="imagery.html">imagery</A> programs, does not use the
+<p>
+<em>i.class</em>, like some of the other 
+<a href="imagery.html">imagery</A> programs, does not use the
 
 standard GRASS display frames.  After running
-<EM>i.class</EM>, you will need to create a display frame
+<em>i.class</em>, you will need to create a display frame
 (e.g., using
 
-<EM><A HREF="d.frame.html">d.frame</A></EM> or 
+<em><a href="d.frame.html">d.frame</A></em> or 
 
-<EM><A HREF="d.erase.html">d.erase</A></EM>)
+<em><a href="d.erase.html">d.erase</A></em>)
 before you can use most of the GRASS display (d.) commands.
 
-<P>
-<EM><A HREF="i.group.html">i.group</A></EM>
-must be run before <EM>i.class</EM> to create an 
-<A HREF="i.group.html">imagery</A> group and a subgroup
+<p>
+<em><a href="i.group.html">i.group</A></em>
+must be run before <em>i.class</em> to create an 
+<a href="i.group.html">imagery</A> group and a subgroup
 containing the image bands to be classified.
 
-<P>
+<p>
 The user can perform a supervised image classification by
-running <EM>i.class</EM> followed by
+running <em>i.class</em> followed by
 
-<EM><A HREF="i.maxlik.html">i.maxlik</A></EM>.  
+<em><a href="i.maxlik.html">i.maxlik</A></em>.  
 
 The user can perform an unsupervised classification
 by running 
 
-<EM><A HREF="i.cluster.html">i.cluster</A></EM> followed by 
+<em><a href="i.cluster.html">i.cluster</A></em> followed by 
 
-<EM><A HREF="i.maxlik.html">i.maxlik</A></EM>.
+<em><a href="i.maxlik.html">i.maxlik</A></em>.
 
-<P>
-<EM>i.class</EM> is interactive and requires the user to be running 
-a graphics display monitor (see <EM><A HREF="d.mon.html">d.mon</A></EM>)
+<p>
+<em>i.class</em> is interactive and requires the user to be running 
+a graphics display monitor (see <em><a href="d.mon.html">d.mon</A></em>)
 to run this program.
 
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
 The GRASS 4 <em>
-<A HREF="http://grass.itc.it/gdp/imagery/grass4_image_processing.pdf">Image
-Processing manual</A></EM>
-
-<P>
-<EM><A HREF="d.frame.html">d.frame</A>, 
-<A HREF="d.mon.html">d.mon</A>, 
-<A HREF="g.region.html">g.region</A>, 
-<A HREF="i.cca.html">i.cca</A>,
-<A HREF="i.cluster.html">i.cluster</A>, 
-<A HREF="r.composite.html">r.composite</A>, 
-<A HREF="i.group.html">i.group</A>, 
-<A HREF="i.maxlik.html">i.maxlik</A>, 
-<A HREF="r.mapcalc.html">r.mapcalc</A></EM>
-
-<H2>AUTHOR</H2>
+<a href="http://grass.itc.it/gdp/imagery/grass4_image_processing.pdf">Image
+Processing manual</A></em>
+
+<p>
+<em><a href="d.frame.html">d.frame</A>, 
+<a href="d.mon.html">d.mon</A>, 
+<a href="g.region.html">g.region</A>, 
+<a href="i.cca.html">i.cca</A>,
+<a href="i.cluster.html">i.cluster</A>, 
+<a href="r.composite.html">r.composite</A>, 
+<a href="i.group.html">i.group</A>, 
+<a href="i.maxlik.html">i.maxlik</A>, 
+<a href="r.mapcalc.html">r.mapcalc</A></em>
+
+<h2>AUTHOR</h2>
 
 David Satnik, 
 Central Washington University

+ 56 - 56
imagery/i.cluster/i.cluster.html

@@ -1,17 +1,17 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
 
-<EM>i.cluster</EM>
+<em>i.cluster</em>
 performs the first pass in the GRASS two-pass unsupervised 
-classification of imagery, while the GRASS program <EM>
-<A HREF="i.maxlik.html">i.maxlik</A></EM> executes 
+classification of imagery, while the GRASS program <em>
+<a href="i.maxlik.html">i.maxlik</A></em> executes 
 the second pass. Both programs must be run to complete the unsupervised 
 classification.
 
 
-<P>
+<p>
 
-<EM>i.cluster</EM> is a clustering algorithm that reads
+<em>i.cluster</em> is a clustering algorithm that reads
 through the (raster) imagery data and builds pixel clusters
 based on the spectral reflectances of the pixels (see Figure).
 The pixel clusters are imagery categories that can be related
@@ -23,7 +23,7 @@ initial number of clusters to be discriminated.
 
 <p>
 <center>
-<img src="landsat_cluster.png" border=1><BR>
+<img src="landsat_cluster.png" border=1><br>
 <table border=0 width=590>
 <tr><td><center>
 <i>Fig.: Land use/land cover clustering of LANDSAT scene (simplified)</i>
@@ -32,7 +32,7 @@ initial number of clusters to be discriminated.
 </center>
 <p>
 
-<EM>i.cluster</EM> starts by generating spectral signatures
+<em>i.cluster</em> starts by generating spectral signatures
 for this number of clusters and "attempts" to end up with
 this number of clusters during the clustering process.  The
 resulting number of clusters and their spectral
@@ -44,12 +44,12 @@ the percent convergence, the maximum number of iterations,
 and the row and column sampling intervals.
 
 
-<P>
+<p>
 
 The cluster spectral signatures that result are composed of
 cluster means and covariance matrices.  These cluster means
 and covariance matrices are used in the second pass 
-(<EM><A HREF="i.maxlik.html">i.maxlik</A></EM>) to
+(<em><a href="i.maxlik.html">i.maxlik</A></em>) to
 classify the image.  The clusters or spectral classes
 result can be related to land cover types on the ground.
 
@@ -57,22 +57,22 @@ The user has to specify the name of group file, the name of subgroup
 file, the name of a file to contain result signatures, the
 initial number of clusters to be discriminated, and
 optionally other parameters (see below)
-where the <EM>group</EM> should contain the imagery files
-that the user wishes to classify.  The <EM>subgroup</EM> is
+where the <em>group</em> should contain the imagery files
+that the user wishes to classify.  The <em>subgroup</em> is
 a subset of this group.  The user must create a group and
 subgroup by running the GRASS program
 
-<EM><A HREF="i.group.html">i.group</A></EM> 
+<em><a href="i.group.html">i.group</A></em> 
 
-before running <EM>i.cluster</EM>.  The subgroup should
+before running <em>i.cluster</em>.  The subgroup should
 contain only the imagery band files that the user wishes to
 classify.  Note that this subgroup must contain more than
 one band file.  The purpose of the group and subgroup is to
 collect map layers for classification or analysis. The
-<EM>sigfile</EM> is the file to contain result signatures
+<em>sigfile</em> is the file to contain result signatures
 which can be used as input for
 
-<EM><A HREF="i.maxlik.html">i.maxlik</A></EM>. 
+<em><a href="i.maxlik.html">i.maxlik</A></em>. 
 
 The classes value is the initial number of clusters to be
 discriminated; any parameter values left unspecified are
@@ -96,75 +96,75 @@ messages are printed out.
 <DL>
 
 
-<DT><B>group=</B><EM>name</EM> 
+<DT><B>group=</B><em>name</em> 
 
 <DD>The name of the group file which contains the imagery
 files that the user wishes to classify.
 
-<DT><B>subgroup=</B><EM>name</EM> 
+<DT><B>subgroup=</B><em>name</em> 
 
 <DD>The name of the subset of the group specified in group
 option, which must contain only imagery band files and more
 than one band file. The user must create a group and a
 subgroup by running the GRASS program 
 
-<EM><A HREF="i.group.html">i.group</A></EM> 
+<em><a href="i.group.html">i.group</A></em> 
 
 before
-running <EM>i.cluster</EM>.
+running <em>i.cluster</em>.
 
-<DT><B>sigfile=</B><EM>name</EM> 
+<DT><B>sigfile=</B><em>name</em> 
 
 <DD>The name assigned to output signature file which
 contains signatures of classes and can be used as the input
 file for the GRASS program 
-<EM><A HREF="i.maxlik.html">i.maxlik</A></EM> 
+<em><a href="i.maxlik.html">i.maxlik</A></em> 
 for an unsupervised classification.
 
-<DT><B>classes=</B><EM>value</EM> 
+<DT><B>classes=</B><em>value</em> 
 
 <DD>The number of clusters that will initially be
 identified in the clustering process before the iterations
 begin.
 
-<DT><B>seed=</B><EM>name</EM> 
+<DT><B>seed=</B><em>name</em> 
 
 <DD>The name of a seed signature file is optional. The seed
 signatures are signatures that contain cluster means and
 covariance matrices which were calculated prior to the
-current run of <EM>i.cluster</EM>. They may be acquired
-from a previously run of <EM>i.cluster</EM> or from a
+current run of <em>i.cluster</em>. They may be acquired
+from a previously run of <em>i.cluster</em> or from a
 supervised classification signature training site section
 (e.g., using the signature file output by
 
-<EM><A HREF="i.class.html">i.class</A></EM>). 
+<em><a href="i.class.html">i.class</A></em>). 
 
 The purpose of seed signatures is to optimize the cluster
 decision boundaries (means) for the number of clusters
 specified.
 
-<DT><B>sample=</B><EM>row_interval,col_interval</EM> 
+<DT><B>sample=</B><em>row_interval,col_interval</em> 
 
 <DD>These numbers are optional with default values based on
 the size of the data set such that the total pixels to be
 processed is approximately 10,000 (consider round up).
 
-<DT><B>iterations=</B><EM>value</EM> 
+<DT><B>iterations=</B><em>value</em> 
 
 <DD>This parameter determines the maximum number of
 iterations which is greater than the number of iterations
 predicted to achieve the optimum percent convergence. The
 default value is 30. If the number of iterations reaches
 the maximum designated by the user; the user may want to
-rerun <EM>i.cluster</EM> with a higher number of iterations
-(see <A HREF="#reportfile"><EM>reportfile</EM></A>).
+rerun <em>i.cluster</em> with a higher number of iterations
+(see <a href="#reportfile"><em>reportfile</em></A>).
 
-<BR>
+<br>
 
 Default: 30
 
 <A NAME="convergence"></a>
-<DT><B>convergence=</B><EM>value</EM>
+<DT><B>convergence=</B><em>value</em>
 
 <DD>A high percent convergence is the point at which
 cluster means become stable during the iteration process.
@@ -172,7 +172,7 @@ The default value is 98.0 percent.  When clusters are being
 created, their means constantly change as pixels are
 assigned to them and the means are recalculated to include
 the new pixel.  After all clusters have been created,
-<EM>i.cluster</EM> begins iterations that change cluster
+<em>i.cluster</em> begins iterations that change cluster
 means by maximizing the distances between them.  As these
 means shift, a higher and higher convergence is
 approached.  Because means will never become totally
@@ -183,13 +183,13 @@ number of iterations. If the maximum number of iterations
 is reached, it is probable that the desired percent
 convergence was not reached. The number of iterations is
 reported in the cluster statistics in the report file
-(see <A HREF="#reportfile"><EM>reportfile</EM></A>).
+(see <a href="#reportfile"><em>reportfile</em></A>).
 
-<BR>
+<br>
 
 Default: 98.0
 
-<DT><B>separation=</B><EM>value</EM> 
+<DT><B>separation=</B><em>value</em> 
 
 <DD>This is the minimum separation below which clusters
 will be merged in the iteration process. The default value
@@ -201,25 +201,25 @@ minimum class (or cluster) separation is increased, the
 maximum number of iterations should also be increased to
 achieve this separation with a high percentage of
 convergence
-(see <A HREF="#convergence"><EM>convergence</EM></A>).
+(see <a href="#convergence"><em>convergence</em></A>).
 
-<BR>
+<br>
 
 Default: 0.0
 
-<DT><B>min_size=</B><EM>value</EM> 
+<DT><B>min_size=</B><em>value</em> 
 
 <DD>This is the minimum number of pixels that will be used
 to define a cluster, and is therefore the minimum number of
 pixels for which means and covariance matrices will be
 calculated.
 
-<BR>
+<br>
 
 Default: 17
 
 <A NAME="reportfile"></A>
-<DT><B>reportfile=</B><EM>name</EM>
+<DT><B>reportfile=</B><em>name</em>
 
 <DD>The reportfile is an optional parameter which contains
 the result, i.e., the statistics for each cluster. Also
@@ -230,35 +230,35 @@ achieve the convergence, and the separability matrix.
 </DL>
 
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 
-Running in command line mode, <EM>i.cluster</EM> will
+Running in command line mode, <em>i.cluster</em> will
 overwrite the output signature file and reportfile (if
 required by the user) without prompting if the files
 existed.
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
 The GRASS 4 <em>
-<A HREF="http://grass.itc.it/gdp/imagery/grass4_image_processing.pdf">Image
-Processing manual</A></EM>
+<a href="http://grass.itc.it/gdp/imagery/grass4_image_processing.pdf">Image
+Processing manual</A></em>
 
-<P>
+<p>
 
-<EM>
-<A HREF="i.class.html">i.class</A><br>
-<A HREF="i.group.html">i.group</A><br>
-<A HREF="i.gensig.html">i.gensig</A><br>
-<A HREF="i.maxlik.html">i.maxlik</A>
-</EM>
+<em>
+<a href="i.class.html">i.class</A><br>
+<a href="i.group.html">i.group</A><br>
+<a href="i.gensig.html">i.gensig</A><br>
+<a href="i.maxlik.html">i.maxlik</A>
+</em>
 
-<H2>AUTHORS</H2>
+<h2>AUTHORS</h2>
 
 Michael Shapiro,
 U.S.Army Construction Engineering 
 Research Laboratory
 
-<BR>
+<br>
 
 Tao Wen, 
 University of Illinois at 

+ 11 - 11
imagery/i.eb.eta/i.eb.eta.html

@@ -1,11 +1,11 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
-<EM>i.eb.eta</EM> calculates the actual evapotranspiration (ETa ; mm/d) for
+<em>i.eb.eta</em> calculates the actual evapotranspiration (ETa ; mm/d) for
 diurnal period after [1], implemented in [3].
 It takes input of Diurnal Net Radiation (see r.sun), evaporative fraction (see
 r.eb.evapfr) and surface skin temperature. 
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 Full ETa processing will need those:
 <ul>
   <li>i.vi, i.albedo, i.latlong, i.emissivity
@@ -18,18 +18,18 @@ Full ETa processing will need those:
 
 <p>For more details on the algorithms see [1][2][3].
 
-<H2>TODO</H2>
+<h2>TODO</h2>
 
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
 <em>
-<A HREF="r.sun.html">r.sun</A><br>
-<A HREF="i.eb.evapfr.html">i.eb.evapfr</A><br>
-<A HREF="i.eb.netrad.html">i.eb.netrad</A><br>
+<a href="r.sun.html">r.sun</A><br>
+<a href="i.eb.evapfr.html">i.eb.evapfr</A><br>
+<a href="i.eb.netrad.html">i.eb.netrad</A><br>
 </em>
 
-<H2>REFERENCES</H2>
+<h2>REFERENCES</h2>
 
   <p>[1] Bastiaanssen, W.G.M., 1995.
   Estimation of Land surface paramters by remote sensing under clear-sky
@@ -44,9 +44,9 @@ Zalidis G.C. Integrated methodology for estimating water use in Mediterranean
 agricultural areas. Remote Sensing. -(-):,2009. (submitted))
 
 
-<H2>AUTHORS</H2>
+<h2>AUTHORS</h2>
 
-Yann Chemin, Asian Institute of Technology, Thailand<BR>
+Yann Chemin, Asian Institute of Technology, Thailand<br>
 
 
 <p>

+ 11 - 11
imagery/i.eb.evapfr/i.eb.evapfr.html

@@ -1,25 +1,25 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
-<EM>i.eb.evapfr</EM> calculates the evaporative fraction after [1]. Main
+<em>i.eb.evapfr</em> calculates the evaporative fraction after [1]. Main
 implementation in [3].
 It takes input of Net Radiation (see r.sun, i.eb.netrad (grass-addons)), soil
 heat flux (see i.eb.g0) and sensible heat flux (see i.eb.h_SEBAL01). 
 A flag adds a root zone empirical soil moisture output from the article of
 Makin, Molden and Bastiaanssen (2001).
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 
-<H2>TODO</H2>
+<h2>TODO</h2>
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
 <em>
-<A HREF="r.sun.html">r.sun</A><br>
-<A HREF="i.eb.soilheatflux.html">i.eb.soilheatflux</A><br>
-<A HREF="i.eb.h_SEBAL01.html">i.eb.h_SEBAL01</A><br>
+<a href="r.sun.html">r.sun</A><br>
+<a href="i.eb.soilheatflux.html">i.eb.soilheatflux</A><br>
+<a href="i.eb.h_SEBAL01.html">i.eb.h_SEBAL01</A><br>
 </em>
 
-<H2>REFERENCES</H2>
+<h2>REFERENCES</h2>
 
   <p>[1] Bastiaanssen, W.G.M., 1995.
   Estimation of Land surface paramters by remote sensing under clear-sky
@@ -33,9 +33,9 @@ seasonal for irrigated rice in Zhanghe, China. Asian Journal of Geoinformatics.
 Zalidis G.C. Integrated methodology for estimating water use in Mediterranean
 agricultural areas. Remote Sensing. -(-):,2009. (submitted))
 
-<H2>AUTHORS</H2>
+<h2>AUTHORS</h2>
 
-Yann Chemin, Asian Institute of Technology, Thailand<BR>
+Yann Chemin, Asian Institute of Technology, Thailand<br>
 
 
 <p>

+ 8 - 8
imagery/i.eb.h_SEBAL01/i.eb.h_sebal01.html

@@ -1,6 +1,6 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
-<p><EM>i.eb.h_sebal01</EM> will calculate the sensible heat flux map (h0), given
+<p><em>i.eb.h_sebal01</em> will calculate the sensible heat flux map (h0), given
 both maps of Net Radiation and soil Heat flux (Rn, g0) at instantaneous time,
 the surface roughness (z0m), a map of the altitude corrected temperature
 (t0dem), a point data of the frictional velocity (u*), a value of actual vapour
@@ -16,13 +16,13 @@ Full process will need those:
 
 (for time integration: i.evapo.time_integration)
 
-<p><EM>i.eb.h_sebal01</EM> performs the computation of <i>sensible heat flux</i>
+<p><em>i.eb.h_sebal01</em> performs the computation of <i>sensible heat flux</i>
 [W/m2] after Bastiaanssen, 1995 in [1], used in this form in 2001 by [2]. Implemented
 in this code in [3].
 
-<H2>OPTIONS</H2>
+<h2>OPTIONS</h2>
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 <ul>
 <li> z0m can be alculated by i.eb.z0m or i.eb.z0m0 (grass-addons).
 <li> ea can be calculated with standard meteorological data.<br>
@@ -33,7 +33,7 @@ in this code in [3].
 </ul>
 
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 <ul>
   <li><a href=i.eb.soilheatflux.html>i.eb.soilheatflux</a>,
       <a href=i.eb.h_SEBAL01.html>i.eb.h_SEBAL01</a>,
@@ -41,7 +41,7 @@ in this code in [3].
 </ul>
 
 
-<H2>REFERENCES</H2>
+<h2>REFERENCES</h2>
 
   <p>[1] Bastiaanssen, W.G.M., 1995.
   Estimation of Land surface paramters by remote sensing under clear-sky
@@ -56,7 +56,7 @@ Zalidis G.C. Integrated methodology for estimating water use in Mediterranean
 agricultural areas. Remote Sensing, 1(3):445-465, 2009.
 
 
-<H2>AUTHORS</H2>
+<h2>AUTHORS</h2>
 
   <i>Yann Chemin, International Rice Research Institute, Los Banos, The
 Philippines.

+ 10 - 10
imagery/i.eb.netrad/i.eb.netrad.html

@@ -1,6 +1,6 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
-<EM>i.eb.netrad</EM> calculates the net radiation at the time of satellite
+<em>i.eb.netrad</em> calculates the net radiation at the time of satellite
 overpass, the way it is in the SEBAL model of Bastiaanssen (1995).
 
 It takes input of Albedo, NDVI, Surface Skin temperature, time of satellite
@@ -8,28 +8,28 @@ overpass, surface emissivity, difference of temperature from surface skin and
 about 2 m height (dT), instantaneous satellite overpass single-way atmospheric
 transmissivity (tsw), Day of Year (DOY), and sun zenith angle.
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 In the old methods, dT was taken as flat images (dT=5.0), if you don't have a dT
 map from ground data, you would want to try something in this line, this is to
 calculate atmospherical energy balance. In the same way, a standard tsw is used
 in those equations. Refer to r_net.c for that and for other non-used equations,
 but stored in there for further research convenience.
 
-<H2>TODO</H2>
+<h2>TODO</h2>
 Add more explanations.
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
 <em>
-<A HREF="i.eb.soilheatflux.html">i.eb.soilheatflux</A><br>
-<A HREF="i.eb.h_SEBAL01.html">i.eb.h_SEBAL01</A><br>
-<A HREF="i.albedo.html">i.albedo</A><br>
+<a href="i.eb.soilheatflux.html">i.eb.soilheatflux</A><br>
+<a href="i.eb.h_SEBAL01.html">i.eb.h_SEBAL01</A><br>
+<a href="i.albedo.html">i.albedo</A><br>
 </em>
 
 
-<H2>AUTHORS</H2>
+<h2>AUTHORS</h2>
 
-Yann Chemin, International Rice Research Institute, The Philippines<BR>
+Yann Chemin, International Rice Research Institute, The Philippines<br>
 
 <p>
 <i>Last changed: $Date$</i>

+ 13 - 13
imagery/i.eb.soilheatflux/i.eb.soilheatflux.html

@@ -1,28 +1,28 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
-<EM>i.eb.soilheatflux</EM> calculates the soil heat flux approximation (g0)
+<em>i.eb.soilheatflux</em> calculates the soil heat flux approximation (g0)
 after Bastiaanssen (1995). The main reference for implementation is Alexandridis, submitted.
 It takes input of Albedo, NDVI, Surface Skin temperature, Net Radiation (see 
 <em>r.sun</em>), time of satellite overpass, and a flag for the Roerink empirical
 modification from the HAPEX-Sahel experiment.
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 
 
-<H2>TODO</H2>
+<h2>TODO</h2>
 
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
 <em>
-<A HREF="r.sun.html">r.sun</A><br>
-<A HREF="i.albedo.html">i.albedo</A><br>
-<A HREF="i.emissivity.html">i.emissivity</A><br>
-<A HREF="i.eb.h_SEBAL01.html">i.eb.h_SEBAL01</A><br>
-<A HREF="i.eb.evapfr.html">i.eb.evapfr</A><br>
+<a href="r.sun.html">r.sun</A><br>
+<a href="i.albedo.html">i.albedo</A><br>
+<a href="i.emissivity.html">i.emissivity</A><br>
+<a href="i.eb.h_SEBAL01.html">i.eb.h_SEBAL01</A><br>
+<a href="i.eb.evapfr.html">i.eb.evapfr</A><br>
 </em>
 
-<H2>REFERENCES</H2>
+<h2>REFERENCES</h2>
 
 <p>Bastiaanssen, W.G.M., 1995.
   Estimation of Land surface parameters by remote sensing under clear-sky 
@@ -36,9 +36,9 @@ modification from the HAPEX-Sahel experiment.
    agricultural areas. Remote Sensing. -(-):,2009. (submitted))
 
 
-<H2>AUTHORS</H2>
+<h2>AUTHORS</h2>
 
-Yann Chemin, Asian Institute of Technology, Thailand<BR>
+Yann Chemin, Asian Institute of Technology, Thailand<br>
 
 <p>
 <i>Last changed: $Date$</i>

+ 8 - 8
imagery/i.emissivity/i.emissivity.html

@@ -1,24 +1,24 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
-<EM>i.emissivity</EM> calculates the emissivity in the longwave radiation spectrum, according to the semi-empirical equation related to NDVI by Caselles and Colles (1997), valid in the NDVI range of 0.16 to 0.74.
+<em>i.emissivity</em> calculates the emissivity in the longwave radiation spectrum, according to the semi-empirical equation related to NDVI by Caselles and Colles (1997), valid in the NDVI range of 0.16 to 0.74.
 
 Estimation in the 8-14 micrometers range for sparse canopy
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 
 
-<H2>TODO</H2>
+<h2>TODO</h2>
 
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
 <em>
-<A HREF="i.eb.netrad.html">i.eb.netrad</A><br>
+<a href="i.eb.netrad.html">i.eb.netrad</A><br>
 </em>
 
 
-<H2>AUTHORS</H2>
-Yann Chemin, GRASS Development Team<BR>
+<h2>AUTHORS</h2>
+Yann Chemin, GRASS Development Team<br>
 
 
 <p>

+ 11 - 11
imagery/i.evapo.mh/i.evapo.mh.html

@@ -1,8 +1,8 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
-<EM>i.evapo.MH</EM> Calculates the reference ET after Hargreaves (1985) and Modified Hargreaves (2001). 
+<em>i.evapo.MH</em> Calculates the reference ET after Hargreaves (1985) and Modified Hargreaves (2001). 
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 Hargreaves GL, Hargreaves GH, Riley JP, 1985. Agricultural benefits for Senegal River Basin. Journal of Irrigation and Drainange Engineering, ASCE, 111(2):113-124.
 
 Droogers P, Allen RG, 2002. Towards a simplified global reference evapotranspiration equation. Irrigation Science.
@@ -10,23 +10,23 @@ Droogers, P., and R.G. Allen. 2002. Estimating reference evapotranspiration unde
 
 Hargreaves and Samani, 1985.
 
-<H2>TODO</H2>
+<h2>TODO</h2>
 
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
 <em>
-<A HREF="i.evapo.PT.html">i.evapo.PT</A><br>
-<A HREF="i.evapo.PM.html">i.evapo.PM</A><br>
-<A HREF="i.evapo.potrad.html">i.evapo.potrad</A><br>
-<A HREF="r.sun.html">r.sun</A><br>
+<a href="i.evapo.PT.html">i.evapo.PT</A><br>
+<a href="i.evapo.PM.html">i.evapo.PM</A><br>
+<a href="i.evapo.potrad.html">i.evapo.potrad</A><br>
+<a href="r.sun.html">r.sun</A><br>
 
 </em>
 
 
-<H2>AUTHORS</H2>
+<h2>AUTHORS</h2>
 
-Yann Chemin, GRASS Development team, 2007-2011<BR>
+Yann Chemin, GRASS Development team, 2007-2011<br>
 
 
 <p>

+ 8 - 8
imagery/i.evapo.pm/i.evapo.pm.html

@@ -1,6 +1,6 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
-<p><EM>i.evapo.PM</EM> given the vegetation height (hc), humidity (RU), 
+<p><em>i.evapo.PM</em> given the vegetation height (hc), humidity (RU), 
 wind speed at two meters height (WS), temperature (T), digital terrain model (DEM), 
 and net radiation (NSR) raster input maps, 
 calculates the potential evapotranspiration map (EPo).
@@ -21,7 +21,7 @@ and the appropriate soil heat flux is calculated.
 
 <p>For more details on the algorithms see [1,2,3].
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 
 <p>Net solar radiation map in MJ/(m2*h) can be computed from the combination of the r.sun , 
 run in mode 1, and the r.mapcalc commands.
@@ -29,13 +29,13 @@ run in mode 1, and the r.mapcalc commands.
 <p>The sum of the three radiation components outputted by r.sun (beam, diffuse, and reflected) 
 multiplied by the Wh to Mj conversion factor (0.0036) and optionally by a 
 clear sky factor [0-1] allows the generation of a map to be used as 
-an NSR input for the <EM>i.evapo.PM</EM> command.<br>
+an NSR input for the <em>i.evapo.PM</em> command.<br>
 example:<br>
 <br>r.sun -s elevin=dem aspin=aspect slopein=slope lin=2 albedo=alb_Mar incidout=out beam_rad=beam diff_rad=diffuse refl_rad=reflected day=73 time=13:00 dist=100;
 <br>r.mapcalc 'NSR=0.0036*(beam+diffuse+reflected)';
 
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 <ul>
   <li>The <a href="http://istgis.ist.supsi.ch:8001/geomatica/">HydroFOSS</a> 
 project at IST-SUPSI (Institute of Earth Sciences - University school of applied science for the Southern Switzerland)
@@ -46,7 +46,7 @@ project at IST-SUPSI (Institute of Earth Sciences - University school of applied
 
 
 
-<H2>AUTHORS</H2>
+<h2>AUTHORS</h2>
   
   <p>Original version of program: The <a href="http://istgis.ist.supsi.ch:8001/geomatica/index.php?id=1">HydroFOSS</a> project, 2006, IST-SUPSI. (http://istgis.ist.supsi.ch:8001/geomatica/index.php?id=1)
   <i>
@@ -57,9 +57,9 @@ project at IST-SUPSI (Institute of Earth Sciences - University school of applied
   <p>Contact: <a href="mailto:massimiliano.cannata@supsi.ch"> Massimiliano Cannata</a>
 
 
-<H2>REFERENCES</H2>
+<h2>REFERENCES</h2>
 
-  <p>[1] Cannata M., 2006. <A HREF="http://istgis.ist.supsi.ch:8001/geomatica/index.php?id=1">
+  <p>[1] Cannata M., 2006. <a href="http://istgis.ist.supsi.ch:8001/geomatica/index.php?id=1">
   GIS embedded approach for Free & Open Source Hydrological Modelling</A>. PhD thesis, Department of Geodesy and Geomatics, Polytechnic of Milan, Italy.
 
   <p>[2] Allen, R.G., L.S. Pereira, D. Raes, and M. Smith. 1998. 

+ 11 - 11
imagery/i.evapo.pt/i.evapo.pt.html

@@ -1,9 +1,9 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
-<EM>i.evapo.PT</EM> Calculates the diurnal evapotranspiration after Prestley and Taylor (1972). 
+<em>i.evapo.PT</em> Calculates the diurnal evapotranspiration after Prestley and Taylor (1972). 
 The Priestley-Taylor model (Priestley and Taylor, 1972) is a modification of Penman’s more theoretical equation.
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 RNETD optional output from i.evapo.potrad is giving good results as input for net radiation in this module.
 
 Alpha values:
@@ -14,22 +14,22 @@ Alpha values:
 Alpha values extracted from:
 http://www.civil.uwaterloo.ca/Watflood/Manual/02_03_1.htm
 
-<H2>TODO</H2>
+<h2>TODO</h2>
 
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
 <em>
-<A HREF="i.evapo.PM.html">i.evapo.PM</A><br>
-<A HREF="i.evapo.potrad.html">i.evapo.potrad</A><br>
-<A HREF="i.eb.netrad.html">i.eb.netrad</A><br>
-<A HREF="i.eb.g0.html">i.eb.g0</A><br>
+<a href="i.evapo.PM.html">i.evapo.PM</A><br>
+<a href="i.evapo.potrad.html">i.evapo.potrad</A><br>
+<a href="i.eb.netrad.html">i.eb.netrad</A><br>
+<a href="i.eb.g0.html">i.eb.g0</A><br>
 </em>
 
 
-<H2>AUTHORS</H2>
+<h2>AUTHORS</h2>
 
-Yann Chemin, GRASS Development team, 2007-08<BR>
+Yann Chemin, GRASS Development team, 2007-08<br>
 
 
 <p>

+ 13 - 13
imagery/i.evapo.time/i.evapo.time.html

@@ -1,6 +1,6 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
-<EM>i.evapo.time_integration</EM> integrates ETa in time following a reference ET (typically) from a set of meteorological stations dataset.
+<em>i.evapo.time_integration</em> integrates ETa in time following a reference ET (typically) from a set of meteorological stations dataset.
 
 Inputs:
 - ETa images
@@ -20,7 +20,7 @@ DOYbeforeETa[i] = ( DOYofETa[i] - DOYofETa[i-1] ) / 2
 DOYafterETa[i] = ( DOYofETa[i+1] - DOYofETa[i] ) / 2
 
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 
 ETo images preparation:
 If you only have one meteorological station data, the easiest way is:
@@ -38,21 +38,21 @@ If you have several meteorological stations data, then you need to grid them, Th
 
 For multi-year calculations, just continue incrementing DOY values above 366, it will continue working, up to maximum input of 400 satellite images.
 
-<H2>TODO</H2>
+<h2>TODO</h2>
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
 <em>
-<A HREF="i.eb.eta.html">i.eb.eta</A><br>
-<A HREF="i.evapo.potrad.html">i.evapo.potrad</A><br>
-<A HREF="i.evapo.SENAY.html">i.evapo.SENAY</A><br>
-<A HREF="r.surf.idw.html">r.surf.idw</A><br>
-<A HREF="r.surf.idw2.html">r.surf.idw2</A><br>
-<A HREF="r.bilinear.html">r.bilinear</A><br>
+<a href="i.eb.eta.html">i.eb.eta</A><br>
+<a href="i.evapo.potrad.html">i.evapo.potrad</A><br>
+<a href="i.evapo.SENAY.html">i.evapo.SENAY</A><br>
+<a href="r.surf.idw.html">r.surf.idw</A><br>
+<a href="r.surf.idw2.html">r.surf.idw2</A><br>
+<a href="r.bilinear.html">r.bilinear</A><br>
 </em>
 
 
-<H2>AUTHORS</H2>
-Yann Chemin, International Rice Research Institute, The Philippines<BR>
+<h2>AUTHORS</h2>
+Yann Chemin, International Rice Research Institute, The Philippines<br>
 <p>
 <i>Last changed: $Date$</i>

+ 14 - 14
imagery/i.fft/i.fft.html

@@ -1,12 +1,12 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
 
-<EM>i.fft</EM> is an image processing program based on the FFT algorithm
+<em>i.fft</em> is an image processing program based on the FFT algorithm
 given by Frigo et al. (1998), that processes a single input raster map layer
 (<B>input_image</B>) and constructs the real and imaginary Fourier
 components in frequency space.
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 
 The real and imaginary components are stored into the
 <B>real_image</B> and <B>imaginary_image</B> raster map
@@ -17,41 +17,41 @@ the high frequency components are toward the edges.  The
 color table is assigned to the resultant map layer.
 
 
-<P>
+<p>
 
 The current geographic region and mask settings are respected when
 reading the input file. The presence of nulls or a mask will make the
 resulting fast Fourier transform invalid.
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
 M. Frigo and S. G. Johnson (1998): "FFTW: An Adaptive Software Architecture
 for the FFT". See <a href="http://www.fftw.org/">www.fftw.org</a>: FFTW is a C subroutine library
 for computing the Discrete Fourier Transform (DFT) in one or more
 dimensions, of both real and complex data, and of arbitrary input size.
 
-<P>
+<p>
 
 <B>Remote Sensing Digital Image Analysis</B>,
 by John A. Richards,
 Springer-Verlag, 1986.
 
 
-<P>
+<p>
 
 Personal communication,
 between progam author and Ali R. Vali,
 Space Research Center, 
-<A HREF="http://www.utexas.edu">University of Texas</A>, Austin, 1990.
+<a href="http://www.utexas.edu">University of Texas</A>, Austin, 1990.
 
-<P>
+<p>
 
-<EM><A HREF="i.cca.html">i.cca</A></EM><br>
-<EM><A HREF="i.class.html">i.class</A></EM><br>
-<EM><A HREF="i.ifft.html">i.ifft</A></EM><br>
-<EM><A HREF="i.pca.html">i.pca</A></EM>
+<em><a href="i.cca.html">i.cca</A></em><br>
+<em><a href="i.class.html">i.class</A></em><br>
+<em><a href="i.ifft.html">i.ifft</A></em><br>
+<em><a href="i.pca.html">i.pca</A></em>
 
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
 
 David Satnik, GIS Laboratory, 
 Central Washington University

+ 40 - 40
imagery/i.gensig/i.gensig.html

@@ -1,100 +1,100 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
 
-<EM>i.gensig</EM>
+<em>i.gensig</em>
 is a non-interactive method for generating input into 
-<EM><A HREF="i.maxlik.html">i.maxlik</A></EM>.
+<em><a href="i.maxlik.html">i.maxlik</A></em>.
 It can be used as the first pass in the GRASS two-pass 
 classification process (instead of 
-<EM><A HREF="i.cluster.html">i.cluster</A></EM>
+<em><a href="i.cluster.html">i.cluster</A></em>
  or 
-<EM><A HREF="i.class.html">i.class</A></EM>).
+<em><a href="i.class.html">i.class</A></em>).
 
 It reads a raster map layer, called the training map, which
 has some of the pixels or regions already classified.
-<EM>i.gensig</EM> will then extract spectral signatures
+<em>i.gensig</em> will then extract spectral signatures
 from an image based on the classification of the pixels in
 the training map and make these signatures available to
 
-<EM><A HREF="i.maxlik.html">i.maxlik</A></EM>.
+<em><a href="i.maxlik.html">i.maxlik</A></em>.
 
 
-<P>
+<p>
 
 The user would then execute the GRASS program 
-<EM><A HREF="i.maxlik.html">i.maxlik</A></EM>
+<em><a href="i.maxlik.html">i.maxlik</A></em>
 to actually create the final classified map.
 
 
-<H2>OPTIONS</H2>
+<h2>OPTIONS</h2>
 
 <H3>Parameters</H3>
 
 <DL>
 
-<DT><B>trainingmap=</B><EM>name</EM>
+<DT><B>trainingmap=</B><em>name</em>
 
 <DD>ground truth training map
 
-<P>
+<p>
 
 This map must be prepared by the user in advance using vector or
 raster digitizer. Of course other methods could be devised by the user
-for creating this training map - <EM>i.gensig</EM> makes no assumption
+for creating this training map - <em>i.gensig</em> makes no assumption
 about the origin of this map layer. It simply creates signatures for
 the classes defined in the training map for the image to be classified
 (the image is specified in other options - see below).
 
-<DT><B>group=</B><EM>name</EM> 
+<DT><B>group=</B><em>name</em> 
 
 <DD>imagery group
 
-<P>
+<p>
 
 This is the name of the group that contains the band files
-which comprise the image to be analyzed. The <EM>
-<A HREF="i.group.html">i.group</A> </EM> command is
+which comprise the image to be analyzed. The <em>
+<a href="i.group.html">i.group</A> </em> command is
 used to construct groups of raster layers which comprise an
 image.
 
 
-<P>
+<p>
 
-<DT><A NAME="subgroup"></A><B>subgroup=</B><EM>name</EM>
+<DT><A NAME="subgroup"></A><B>subgroup=</B><em>name</em>
 
 <DD>subgroup containing image files
 
-<P>
+<p>
 
 This names the subgroup within the group that selects a
-subset of the bands to be analyzed. The <EM>
-<A HREF="i.group.html">i.group</A> </EM> command is
+subset of the bands to be analyzed. The <em>
+<a href="i.group.html">i.group</A> </em> command is
 also used to prepare this subgroup.  The subgroup mechanism
 allows the user to select a subset of all the band files
 that form an image.
 
 
-<DT><B>signaturefile=</B><EM>name</EM> 
+<DT><B>signaturefile=</B><em>name</em> 
 
 <DD>resultant signature file
 
-<P>
+<p>
 
 This is the resultant signature file (containing the means
 and covariance matrices) for each class in the training map
 that is associated with the band files in the subgroup
-select (see <A HREF="#subgroup">above</A>).
+select (see <a href="#subgroup">above</A>).
 
 </DL>
 
-<H2>INTERACTIVE MODE</H2>
+<h2>INTERACTIVE MODE</h2>
 
 If none of the arguments are specified on the command line, 
-<EM>i.gensig</EM>
+<em>i.gensig</em>
 will interactively prompt for the names of these maps and files.
 
 
-<P>
+<p>
 
 It should be noted that interactive mode here only means
 interactive prompting for maps and files.
@@ -102,32 +102,32 @@ It does not mean visualization of the signatures that
 result from the process.
 
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
-<EM><A HREF="i.group.html">i.group</A></EM>
+<em><a href="i.group.html">i.group</A></em>
 for creating groups and subgroups.
 
-<P>
+<p>
 
-<EM><A HREF="wxGUI.Vector_Digitizing_Tool.html">wxGUI vector digitizer</A></EM>
+<em><a href="wxGUI.Vector_Digitizing_Tool.html">wxGUI vector digitizer</A></em>
 and
-<EM><A HREF="r.digit.html">r.digit</A></EM>
+<em><a href="r.digit.html">r.digit</A></em>
 for interactively  creating the training map.
 
-<P>
+<p>
 
-<EM><A HREF="i.cluster.html">i.cluster</A></EM>
+<em><a href="i.cluster.html">i.cluster</A></em>
 for unsupervised clustering as an alternative to 
-<EM>i.gensig</EM> to create signatures.
+<em>i.gensig</em> to create signatures.
 
 
-<P>
+<p>
 
-<EM><A HREF="i.class.html">i.class</A></EM>
+<em><a href="i.class.html">i.class</A></em>
 for a graphic/interactive as an alternative to 
-<EM>i.gensig</EM> to create signatures.
+<em>i.gensig</em> to create signatures.
 
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
 
 Michael Shapiro,
 U.S.Army Construction Engineering Research Laboratory

+ 56 - 56
imagery/i.gensigset/i.gensigset.html

@@ -1,40 +1,40 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
 
-<EM>i.gensigset</EM>
+<em>i.gensigset</em>
 is a non-interactive method for generating input into
 
-<EM><A HREF="i.smap.html">i.smap</A>.</EM>
+<em><a href="i.smap.html">i.smap</A>.</em>
 
 It is used as the first pass in the a two-pass
 classification process.  It reads a raster map layer,
 called the training map, which has some of the pixels or
-regions already classified.  <EM>i.gensigset</EM> will then
+regions already classified.  <em>i.gensigset</em> will then
 extract spectral signatures from an image based on the
 classification of the pixels in the training map and make
 these signatures available to
 
-<EM><A HREF="i.smap.html">i.smap</A>.</EM>
+<em><a href="i.smap.html">i.smap</A>.</em>
 
 
-<P>
+<p>
 
-The user would then execute the GRASS program <EM>
-<A HREF="i.smap.html">i.smap</A></EM> to create the
+The user would then execute the GRASS program <em>
+<a href="i.smap.html">i.smap</A></em> to create the
 final classified map.
 
-<H2>OPTIONS</H2>
+<h2>OPTIONS</h2>
 
 <H3>Parameters</H3>
 
 <DL>
 
-<DT><B>trainingmap=</B><EM>name</EM> 
+<DT><B>trainingmap=</B><em>name</em> 
 
 <DD>ground truth training map
 
 
-<P>
+<p>
 
 This raster layer, supplied as input by the user, has some
 of its pixels already classified, and the rest (probably
@@ -42,88 +42,88 @@ most) of the pixels unclassified.  Classified means that
 the pixel has a non-zero value and unclassified means that
 the pixel has a zero value.
 
-<P>
+<p>
 
 This map must be prepared by the user in advance.
 The user must use
 
-<EM><A HREF="r.digit.html">r.digit</A></EM>,
+<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_Digitizing_Tool.html">wxGUI vector digitizer</A></em>
 and 
-<EM><A HREF="v.to.rast.html">v.to.rast</A></EM>,
+<em><a href="v.to.rast.html">v.to.rast</A></em>,
 or some other import/developement process (e.g.,
-<EM><A HREF="v.in.transects.html">v.in.transects</A>)</EM>
+<em><a href="v.in.transects.html">v.in.transects</A>)</em>
 to define the areas
 representative
 of the classes in the image.
 
 
-<P>
+<p>
 
 At present, there is no fully-interactive tool specifically
 designed for producing this layer.
 
-<DT><B>group=</B><EM>name</EM> 
+<DT><B>group=</B><em>name</em> 
 
 <DD>imagery group
 
-<P>
+<p>
 
 This is the name of the group that contains the band files
 which comprise the image to be analyzed. The
 
-<EM><A HREF="i.group.html">i.group</A></EM>
+<em><a href="i.group.html">i.group</A></em>
 
 command is used to construct groups of raster layers which
 comprise an image.
 
-<P>
+<p>
 
-<DT><B>subgroup=</B><EM>name</EM> 
+<DT><B>subgroup=</B><em>name</em> 
 
 <DD>subgroup containing image files
 
 
-<P>
+<p>
 
 This names the subgroup within the group that selects a
 subset of the bands to be analyzed. The
 
-<EM><A HREF="i.group.html">i.group</A></EM>
+<em><a href="i.group.html">i.group</A></em>
 
 command is also used to prepare this subgroup.  The
 subgroup mechanism allows the user to select a subset of
 all the band files that form an image.
 
 
-<DT><B>signaturefile=</B><EM>name</EM>
+<DT><B>signaturefile=</B><em>name</em>
 
 <DD>resultant signature file
 
-<P>
+<p>
 
 This is the resultant signature file (containing the means
 and covariance matrices) for each class in the training map
 that is associated with the band files in the subgroup
 selected.
 
-<P>
+<p>
 
 
-<DT><B>maxsig=</B><EM>value</EM> 
+<DT><B>maxsig=</B><em>value</em> 
 
 <DD>maximum number of sub-signatures in any class
 
-<BR>
+<br>
 
 default: 10
 
-<P>
+<p>
 
 The spectral signatures which are produced by this program
-are "mixed" signatures (see <A HREF="#notes">NOTES</A>).
+are "mixed" signatures (see <a href="#notes">NOTES</A>).
 Each signature contains one or more subsignatures
 (represeting subclasses).  The algorithm in this program
 starts with a maximum number of subclasses and reduces this
@@ -134,25 +134,25 @@ starting value with this option.
 </DL>
 
 
-<H2>INTERACTIVE MODE</H2>
+<h2>INTERACTIVE MODE</h2>
 
 If none of the arguments are specified on the command line,
-<EM>i.gensigset</EM> will interactively prompt for the
+<em>i.gensigset</em> will interactively prompt for the
 names of these maps and files.
 
-<P>
+<p>
 
 It should be noted that interactive mode here only means
 interactive prompting for maps and files.  It does not mean
 visualization of the signatures that result from the
 process.
 
-<P>
+<p>
 
 
-<A NAME="notes"></A><H2>NOTES</H2>
+<A NAME="notes"></A><h2>NOTES</h2>
 
-The algorithm in <EM>i.gensigset</EM> determines the
+The algorithm in <em>i.gensigset</em> determines the
 parameters of a spectral class model known as a Gaussian
 mixture distribution.  The parameters are estimated using
 multispectral image data and a training map which labels
@@ -161,7 +161,7 @@ class parameters are stored as a class signature which can
 be used for subsequent segmentation (i.e., classification)
 of the multispectral image.
 
-<P>
+<p>
 
 The Gaussian mixture class is a useful model because it can
 be used to describe the behavior of an information class
@@ -175,7 +175,7 @@ forest may contain a variety of different tree species each
 with its own spectral behavior.
 
 
-<P>
+<p>
 
 The objective of mixture classes is to improve segmentation
 performance by modeling each information class as a
@@ -189,73 +189,73 @@ Therefore, care should be taken to provided accurate
 training data.
 
 
-<P>
+<p>
 
 This clustering algorithm estimates both the number of
 distinct subclasses in each class, and the spectral mean
 and covariance for each subclass.  The number of subclasses
 is estimated using Rissanen's minimum description length
 (MDL) criteria 
-[<A HREF="#rissanen83">1</A>].  
+[<a href="#rissanen83">1</A>].  
 This criteria attempts to determine
 the number of subclasses which "best" describe the data.
 The approximate maximum likelihood estimates of the mean
 and covariance of the subclasses are computed using the
 expectation maximization (EM) algorithm 
-[<A HREF="#dempster77">2</A>,<A HREF="#redner84">3</A>].  
+[<a href="#dempster77">2</A>,<a href="#redner84">3</A>].  
 
 
-<H2>REFERENCES</H2>
+<h2>REFERENCES</h2>
 
 <OL>
 
 <LI><A NAME="rissanen83">J. Rissanen,</A>
 "A Universal Prior for Integers and Estimation by Minimum
 Description Length,"
-<EM>Annals of Statistics,</EM>
+<em>Annals of Statistics,</em>
 vol. 11, no. 2, pp. 417-431, 1983.
 
 
 <LI><A NAME="dempster77">A. Dempster, N. Laird and D. Rubin,</A>
 "Maximum Likelihood from Incomplete Data via the EM Algorithm,"
-<EM>J. Roy. Statist. Soc. B,</EM>
+<em>J. Roy. Statist. Soc. B,</em>
 vol. 39, no. 1, pp. 1-38, 1977.
 
 <LI><A NAME="redner84">E. Redner and H. Walker,</A>
 "Mixture Densities, Maximum Likelihood and the EM Algorithm,"
-<EM>SIAM Review,</EM>
+<em>SIAM Review,</em>
 vol. 26, no. 2, April 1984.
 
 </OL>
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
-<EM><A HREF="i.group.html">i.group</A></EM>
+<em><a href="i.group.html">i.group</A></em>
 for creating groups and subgroups
 
 
-<P>
+<p>
 
-<EM><A HREF="wxGUI.Vector_Digitizing_Tool.html">wxGUI vector digitizer</A></EM>
+<em><a href="wxGUI.Vector_Digitizing_Tool.html">wxGUI vector digitizer</A></em>
 and
-<EM><A HREF="r.digit.html">r.digit</A></EM>
+<em><a href="r.digit.html">r.digit</A></em>
 for interactively creating the training map.
 
 
-<P>
+<p>
 
-<EM><A HREF="i.smap.html">i.smap</A></EM>
+<em><a href="i.smap.html">i.smap</A></em>
 for creating a final classification layer from the signatures
-generated by <EM>i.gensigset.</EM>
+generated by <em>i.gensigset.</em>
 
 
-<H2>AUTHORS</H2>
+<h2>AUTHORS</h2>
 
 Charles Bouman, 
 School of 
 Electrical Engineering, 
 Purdue University
-<BR>
+<br>
 
 Michael Shapiro,
 U.S.Army Construction Engineering 

+ 22 - 22
imagery/i.group/i.group.html

@@ -1,46 +1,46 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
-<EM>i.group</EM> allows the user to collect raster map layers in an imagery
+<em>i.group</em> allows the user to collect raster map layers in an imagery
 group by assigning them to user-named subgroups or other groups. This
 enables the user to run analyses on any combination of the raster map layers
 in a group.  The user creates the groups and subgroups and selects the
 raster map layers that are to reside in them. Imagery analysis programs like
-<EM><A HREF="i.points.html">i.points</A></EM>, 
-<EM><a href="i.rectify.html">i.rectify</A></EM>,
-<EM><a href="i.ortho.photo.html">i.ortho.photo</A></EM> and
+<em><a href="i.points.html">i.points</A></em>, 
+<em><a href="i.rectify.html">i.rectify</A></em>,
+<em><a href="i.ortho.photo.html">i.ortho.photo</A></em> and
 others ask the user for the name of an imagery group whose data are to be
 analyzed. Imagery analysis programs like
-<EM><a href="i.cluster.html">i.cluster</A></EM> and 
-<EM><a href="i.maxlik.html">i.maxlik</A></EM> ask the user for the imagery group
+<em><a href="i.cluster.html">i.cluster</A></em> and 
+<em><a href="i.maxlik.html">i.maxlik</A></em> ask the user for the imagery group
 and imagery subgroup whose data are to be analyzed.
 
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 
-The <EM>i.group</EM> options are only available for 
+The <em>i.group</em> options are only available for 
 imagery map layers in the current LOCATION_NAME.
 
-<P>
+<p>
 Subgroup names may not contain more than 12 characters.
 
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
 The GRASS 4 <em>
-<A HREF="http://grass.itc.it/gdp/imagery/grass4_image_processing.pdf">Image
-Processing manual</A></EM>
+<a href="http://grass.itc.it/gdp/imagery/grass4_image_processing.pdf">Image
+Processing manual</A></em>
 
-<P>
-<EM>
-<A HREF="i.cluster.html">i.cluster</A><br>
-<A HREF="i.maxlik.html">i.maxlik</A><br>
-<A HREF="i.points.html">i.points</A><br>
-<A HREF="i.rectify.html">i.rectify</A><br>
-<a HREF="i.ortho.photo.html">i.ortho.photo</A>
-</EM>
+<p>
+<em>
+<a href="i.cluster.html">i.cluster</A><br>
+<a href="i.maxlik.html">i.maxlik</A><br>
+<a href="i.points.html">i.points</A><br>
+<a href="i.rectify.html">i.rectify</A><br>
+<a href="i.ortho.photo.html">i.ortho.photo</A>
+</em>
 
 
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
 
 Michael Shapiro,
 U.S.Army Construction Engineering 

+ 0 - 0
imagery/i.his.rgb/i.his.rgb.html


Niektóre pliki nie zostały wyświetlone z powodu dużej ilości zmienionych plików