Thu Sep 29 15:18:47 EDT 2011

Author: neteler
Date: 2011-09-29 12:18:47 -0700 (Thu, 29 Sep 2011)
New Revision: 48557

Modified:
   grass/trunk/db/db.columns/db.columns.html
   grass/trunk/db/db.connect/db.connect.html
   grass/trunk/db/db.copy/db.copy.html
   grass/trunk/db/db.createdb/db.createdb.html
   grass/trunk/db/db.databases/db.databases.html
   grass/trunk/db/db.describe/db.describe.html
   grass/trunk/db/db.drivers/db.drivers.html
   grass/trunk/db/db.dropdb/db.dropdb.html
   grass/trunk/db/db.execute/db.execute.html
   grass/trunk/db/db.login/db.login.html
   grass/trunk/db/db.select/db.select.html
   grass/trunk/db/db.tables/db.tables.html
   grass/trunk/db/drivers/dbf/grass-dbf.html
   grass/trunk/db/drivers/mysql/grass-mesql.html
   grass/trunk/db/drivers/mysql/grass-mysql.html
   grass/trunk/db/drivers/odbc/grass-odbc.html
   grass/trunk/db/drivers/ogr/grass-ogr.html
   grass/trunk/db/drivers/postgres/grass-pg.html
   grass/trunk/display/d.barscale/d.barscale.html
   grass/trunk/display/d.colorlist/d.colorlist.html
   grass/trunk/display/d.colors/d.colors.html
   grass/trunk/display/d.colortable/d.colortable.html
   grass/trunk/display/d.extract/d.extract.html
   grass/trunk/display/d.font/d.font.html
   grass/trunk/display/d.fontlist/d.fontlist.html
   grass/trunk/display/d.geodesic/d.geodesic.html
   grass/trunk/display/d.graph/d.graph.html
   grass/trunk/display/d.grid/d.grid.html
   grass/trunk/display/d.his/d.his.html
   grass/trunk/display/d.histogram/d.histogram.html
   grass/trunk/display/d.info/d.info.html
   grass/trunk/display/d.labels/d.labels.html
   grass/trunk/display/d.legend/d.legend.html
   grass/trunk/display/d.linegraph/d.linegraph.html
   grass/trunk/display/d.measure/d.measure.html
   grass/trunk/display/d.path/d.path.html
   grass/trunk/display/d.profile/d.profile.html
   grass/trunk/display/d.rast.arrow/d.rast.arrow.html
   grass/trunk/display/d.rast.num/d.rast.num.html
   grass/trunk/display/d.rast/d.rast.html
   grass/trunk/display/d.rgb/d.rgb.html
   grass/trunk/display/d.rhumbline/d.rhumbline.html
   grass/trunk/display/d.text/d.text.html
   grass/trunk/display/d.thematic.area/d.thematic.area.html
   grass/trunk/display/d.title/d.title.html
   grass/trunk/display/d.vect.chart/d.vect.chart.html
   grass/trunk/display/d.what.rast/d.what.rast.html
   grass/trunk/display/d.what.vect/d.what.vect.html
   grass/trunk/display/d.where/d.where.html
   grass/trunk/display/d.zoom/d.zoom.html
   grass/trunk/doc/projectionintro.html
   grass/trunk/doc/raster/r.example/r.example.html
   grass/trunk/doc/vector/v.example/v.example.html
   grass/trunk/doc/vector/v.modules.html
   grass/trunk/doc/vector/vector.html
   grass/trunk/general/g.access/g.access.html
   grass/trunk/general/g.cairocomp/g.cairocomp.html
   grass/trunk/general/g.copy/g.copy.html
   grass/trunk/general/g.dirseps/g.dirseps.html
   grass/trunk/general/g.filename/g.filename.html
   grass/trunk/general/g.findetc/g.findetc.html
   grass/trunk/general/g.gui/g.gui.html
   grass/trunk/general/g.list/g.list.html
   grass/trunk/general/g.mapset/g.mapset.html
   grass/trunk/general/g.mapsets/g.mapsets.html
   grass/trunk/general/g.message/g.message.html
   grass/trunk/general/g.mkfontcap/g.mkfontcap.html
   grass/trunk/general/g.mlist/g.mlist.html
   grass/trunk/general/g.mremove/g.mremove.html
   grass/trunk/general/g.parser/g.parser.html
   grass/trunk/general/g.pnmcat/g.pnmcat.html
   grass/trunk/general/g.pnmcomp/g.pnmcomp.html
   grass/trunk/general/g.ppmtopng/g.ppmtopng.html
   grass/trunk/general/g.proj/g.proj.html
   grass/trunk/general/g.region/g.region.html
   grass/trunk/general/g.remove/g.remove.html
   grass/trunk/general/g.rename/g.rename.html
   grass/trunk/general/g.setproj/g.setproj.html
   grass/trunk/general/g.tempfile/g.tempfile.html
   grass/trunk/imagery/i.albedo/i.albedo.html
   grass/trunk/imagery/i.aster.toar/i.aster.toar.html
   grass/trunk/imagery/i.biomass/i.biomass.html
   grass/trunk/imagery/i.cca/i.cca.html
   grass/trunk/imagery/i.class/i.class.html
   grass/trunk/imagery/i.cluster/i.cluster.html
   grass/trunk/imagery/i.eb.eta/i.eb.eta.html
   grass/trunk/imagery/i.eb.evapfr/i.eb.evapfr.html
   grass/trunk/imagery/i.eb.h_SEBAL01/i.eb.h_sebal01.html
   grass/trunk/imagery/i.eb.netrad/i.eb.netrad.html
   grass/trunk/imagery/i.eb.soilheatflux/i.eb.soilheatflux.html
   grass/trunk/imagery/i.emissivity/i.emissivity.html
   grass/trunk/imagery/i.evapo.mh/i.evapo.mh.html
   grass/trunk/imagery/i.evapo.pm/i.evapo.pm.html
   grass/trunk/imagery/i.evapo.pt/i.evapo.pt.html
   grass/trunk/imagery/i.evapo.time/i.evapo.time.html
   grass/trunk/imagery/i.fft/i.fft.html
   grass/trunk/imagery/i.gensig/i.gensig.html
   grass/trunk/imagery/i.gensigset/i.gensigset.html
   grass/trunk/imagery/i.group/i.group.html
   grass/trunk/imagery/i.his.rgb/i.his.rgb.html
   grass/trunk/imagery/i.ifft/i.ifft.html
   grass/trunk/imagery/i.landsat.acca/i.landsat.acca.html
   grass/trunk/imagery/i.landsat.toar/i.landsat.toar.html
   grass/trunk/imagery/i.latlong/i.latlong.html
   grass/trunk/imagery/i.maxlik/i.maxlik.html
   grass/trunk/imagery/i.modis.qc/i.modis.qc.html
   grass/trunk/imagery/i.pca/i.pca.html
   grass/trunk/imagery/i.points/i.points.html
   grass/trunk/imagery/i.rectify/i.rectify.html
   grass/trunk/imagery/i.rgb.his/i.rgb.his.html
   grass/trunk/imagery/i.smap/i.smap.html
   grass/trunk/imagery/i.sunhours/i.sunhours.html
   grass/trunk/imagery/i.target/i.target.html
   grass/trunk/imagery/i.vi/i.vi.html
   grass/trunk/imagery/i.vpoints/i.vpoints.html
   grass/trunk/imagery/i.zc/i.zc.html
   grass/trunk/imagery/imageryintro.html
   grass/trunk/lib/db/sqlp/sql.html
   grass/trunk/lib/init/grass7.html
   grass/trunk/lib/init/helptext.html
   grass/trunk/misc/m.cogo/m.cogo.html
   grass/trunk/misc/m.nviz.script/m.nviz.script.html
   grass/trunk/misc/m.transform/m.transform.html
   grass/trunk/ps/ps.map/ps.map.html
   grass/trunk/raster/r.cost/r.cost.html
   grass/trunk/raster/r.distance/r.distance.html
   grass/trunk/raster/r.horizon/r.horizon.html
   grass/trunk/raster/r.in.lidar/r.in.lidar.html
   grass/trunk/raster/r.in.xyz/r.in.xyz.html
   grass/trunk/raster/r.lake/r.lake.html
   grass/trunk/raster/r.le/r.le.patch/r.le.patch.html
   grass/trunk/raster/r.le/r.le.pixel/r.le.pixel.html
   grass/trunk/raster/r.le/r.le.setup/r.le.setup.html
   grass/trunk/raster/r.le/r.le.trace/r.le.trace.html
   grass/trunk/raster/r.li/r.li.cwed/r.li.cwed.html
   grass/trunk/raster/r.li/r.li.daemon/r.li.daemon.html
   grass/trunk/raster/r.li/r.li.dominance/r.li.dominance.html
   grass/trunk/raster/r.li/r.li.edgedensity/r.li.edgedensity.html
   grass/trunk/raster/r.li/r.li.padrange/r.li.padrange.html
   grass/trunk/raster/r.li/r.li.padsd/r.li.padsd.html
   grass/trunk/raster/r.li/r.li.patchdensity/r.li.patchdensity.html
   grass/trunk/raster/r.li/r.li.patchnum/r.li.patchnum.html
   grass/trunk/raster/r.li/r.li.richness/r.li.richness.html
   grass/trunk/raster/r.li/r.li.setup/r.li.setup.html
   grass/trunk/raster/r.li/r.li.shape/r.li.shape.html
   grass/trunk/raster/r.mfilter/r.mfilter.html
   grass/trunk/raster/r.out.png/r.out.png.html
   grass/trunk/raster/r.out.ppm3/r.out.ppm3.html
   grass/trunk/raster/r.out.tiff/r.out.tiff.html
   grass/trunk/raster/r.patch/r.patch.html
   grass/trunk/raster/r.region/r.region.html
   grass/trunk/raster/r.regression.line/r.regression.line.html
   grass/trunk/raster/r.resamp.filter/r.resamp.filter.html
   grass/trunk/raster/r.resamp.interp/r.resamp.interp.html
   grass/trunk/raster/r.resamp.stats/r.resamp.stats.html
   grass/trunk/raster/r.ros/r.ros.html
   grass/trunk/raster/r.slope.aspect/r.slope.aspect.html
   grass/trunk/raster/r.solute.transport/r.solute.transport.html
   grass/trunk/raster/r.spread/r.spread.html
   grass/trunk/raster/r.spreadpath/r.spreadpath.html
   grass/trunk/raster/r.statistics/r.statistics.html
   grass/trunk/raster/r.statistics2/r.statistics2.html
   grass/trunk/raster/r.sun/r.sun.html
   grass/trunk/raster/r.support.stats/r.support.stats.html
   grass/trunk/raster/r.support/r.support.html
   grass/trunk/raster/r.surf.idw/r.surf.idw.html
   grass/trunk/raster/r.texture/r.texture.html
   grass/trunk/raster/r.thin/r.thin.html
   grass/trunk/raster/r.topidx/r.topidx.html
   grass/trunk/raster/r.topmodel/r.topmodel.html
   grass/trunk/raster/r.uslek/r.uslek.html
   grass/trunk/raster/r.walk/r.walk.html
   grass/trunk/raster/r.water.outlet/r.water.outlet.html
   grass/trunk/raster/rasterintro.html
   grass/trunk/raster/simwe/r.sim.sediment/r.sim.sediment.html
   grass/trunk/raster/simwe/r.sim.water/r.sim.water.html
   grass/trunk/raster3d/r3.in.ascii/r3.in.ascii.html
   grass/trunk/raster3d/r3.mkdspf/r3.mkdspf.html
   grass/trunk/scripts/d.correlate/d.correlate.html
   grass/trunk/scripts/d.out.gpsdrive/d.out.gpsdrive.html
   grass/trunk/scripts/d.polar/d.polar.html
   grass/trunk/scripts/d.rast.edit/d.rast.edit.html
   grass/trunk/scripts/db.dropcolumn/db.dropcolumn.html
   grass/trunk/scripts/db.droptable/db.droptable.html
   grass/trunk/scripts/db.in.ogr/db.in.ogr.html
   grass/trunk/scripts/db.test/db.test.html
   grass/trunk/scripts/i.fusion.brovey/i.fusion.brovey.html
   grass/trunk/scripts/i.image.mosaic/i.image.mosaic.html
   grass/trunk/scripts/i.in.spotvgt/i.in.spotvgt.html
   grass/trunk/scripts/i.landsat.rgb/i.landsat.rgb.html
   grass/trunk/scripts/i.spectral/i.spectral.html
   grass/trunk/scripts/i.tasscap/i.tasscap.html
   grass/trunk/scripts/m.proj/m.proj.html
   grass/trunk/scripts/r.fillnulls/r.fillnulls.html
   grass/trunk/scripts/r.in.aster/r.in.aster.html
   grass/trunk/scripts/r.in.srtm/r.in.srtm.html
   grass/trunk/scripts/r.mapcalculator/r.mapcalculator.html
   grass/trunk/scripts/r.mask/r.mask.html
   grass/trunk/scripts/r.out.xyz/r.out.xyz.html
   grass/trunk/scripts/r.reclass.area/r.reclass.area.html
   grass/trunk/scripts/r.shaded.relief/r.shaded.relief.html
   grass/trunk/scripts/r.tileset/r.tileset.html
   grass/trunk/scripts/r3.mapcalculator/r3.mapcalculator.html
   grass/trunk/scripts/v.centroids/v.centroids.html
   grass/trunk/scripts/v.db.droprow/v.db.droprow.html
   grass/trunk/scripts/v.db.join/v.db.join.html
   grass/trunk/scripts/v.in.e00/v.in.e00.html
   grass/trunk/scripts/v.in.geonames/v.in.geonames.html
   grass/trunk/scripts/v.in.gns/v.in.gns.html
   grass/trunk/scripts/v.in.gps/v.in.gps.html
   grass/trunk/scripts/v.in.wfs/v.in.wfs.html
   grass/trunk/scripts/v.out.gps/v.out.gps.html
   grass/trunk/scripts/v.report/v.report.html
   grass/trunk/scripts/v.what.vect/v.what.vect.html
   grass/trunk/sites/s.in.ascii/s.in.ascii.html
   grass/trunk/sites/s.out.ascii/s.out.ascii.html
   grass/trunk/vector/v.buffer/v.buffer.html
   grass/trunk/vector/v.build/v.build.html
   grass/trunk/vector/v.category/v.category.html
   grass/trunk/vector/v.class/v.class.html
   grass/trunk/vector/v.clean/test/description.html
   grass/trunk/vector/v.clean/v.clean.html
   grass/trunk/vector/v.convert/v.convert.html
   grass/trunk/vector/v.db.connect/v.db.connect.html
   grass/trunk/vector/v.db.select/v.db.select.html
   grass/trunk/vector/v.delaunay/v.delaunay.html
   grass/trunk/vector/v.distance/v.distance.html
   grass/trunk/vector/v.drape/v.drape.html
   grass/trunk/vector/v.external/v.external.html
   grass/trunk/vector/v.extract/v.extract.html
   grass/trunk/vector/v.generalize/v.generalize.html
   grass/trunk/vector/v.in.ascii/v.in.ascii.html
   grass/trunk/vector/v.in.db/v.in.db.html
   grass/trunk/vector/v.in.dwg/v.in.dwg.html
   grass/trunk/vector/v.in.lidar/v.in.lidar.html
   grass/trunk/vector/v.in.ogr/v.in.ogr.html
   grass/trunk/vector/v.in.region/v.in.region.html
   grass/trunk/vector/v.info/v.info.html
   grass/trunk/vector/v.kcv/v.kcv.html
   grass/trunk/vector/v.kernel/v.kernel.html
   grass/trunk/vector/v.label.sa/v.label.sa.html
   grass/trunk/vector/v.label/v.label.html
   grass/trunk/vector/v.lidar.correction/v.lidar.correction.html
   grass/trunk/vector/v.lidar.edgedetection/v.lidar.edgedetection.html
   grass/trunk/vector/v.lidar.growing/v.lidar.growing.html
   grass/trunk/vector/v.lrs/lrs.html
   grass/trunk/vector/v.lrs/v.lrs.create/v.lrs.create.html
   grass/trunk/vector/v.lrs/v.lrs.label/v.lrs.label.html
   grass/trunk/vector/v.lrs/v.lrs.segment/v.lrs.segment.html
   grass/trunk/vector/v.lrs/v.lrs.where/v.lrs.where.html
   grass/trunk/vector/v.mkgrid/v.mkgrid.html
   grass/trunk/vector/v.neighbors/v.neighbors.html
   grass/trunk/vector/v.net.alloc/v.net.alloc.html
   grass/trunk/vector/v.net.allpairs/v.net.allpairs.html
   grass/trunk/vector/v.net.bridge/v.net.bridge.html
   grass/trunk/vector/v.net.centrality/v.net.centrality.html
   grass/trunk/vector/v.net.components/v.net.components.html
   grass/trunk/vector/v.net.connectivity/v.net.connectivity.html
   grass/trunk/vector/v.net.distance/v.net.distance.html
   grass/trunk/vector/v.net.flow/v.net.flow.html
   grass/trunk/vector/v.net.iso/v.net.iso.html
   grass/trunk/vector/v.net.path/v.net.path.html
   grass/trunk/vector/v.net.salesman/v.net.salesman.html
   grass/trunk/vector/v.net.spanningtree/v.net.spanningtree.html
   grass/trunk/vector/v.net.steiner/v.net.steiner.html
   grass/trunk/vector/v.net.timetable/v.net.timetable.html
   grass/trunk/vector/v.net.visibility/v.net.visibility.html
   grass/trunk/vector/v.net/v.net.html
   grass/trunk/vector/v.normal/v.normal.html
   grass/trunk/vector/v.out.dxf/v.out.dxf.html
   grass/trunk/vector/v.out.ogr/v.out.ogr.html
   grass/trunk/vector/v.out.pov/v.out.pov.html
   grass/trunk/vector/v.out.svg/v.out.svg.html
   grass/trunk/vector/v.out.vtk/v.out.vtk.html
   grass/trunk/vector/v.outlier/v.outlier.html
   grass/trunk/vector/v.overlay/v.overlay.html
   grass/trunk/vector/v.parallel/v.parallel.html
   grass/trunk/vector/v.patch/v.patch.html
   grass/trunk/vector/v.perturb/v.perturb.html
   grass/trunk/vector/v.proj/v.proj.html
   grass/trunk/vector/v.qcount/v.qcount.html
   grass/trunk/vector/v.random/v.random.html
   grass/trunk/vector/v.reclass/v.reclass.html
   grass/trunk/vector/v.sample/v.sample.html
   grass/trunk/vector/v.segment/v.segment.html
   grass/trunk/vector/v.select/v.select.html
   grass/trunk/vector/v.support/v.support.html
   grass/trunk/vector/v.surf.idw/v.surf.idw.html
   grass/trunk/vector/v.surf.rst/v.surf.rst.html
   grass/trunk/vector/v.to.db/v.to.db.html
   grass/trunk/vector/v.to.points/v.to.points.html
   grass/trunk/vector/v.to.rast/v.to.rast.html
   grass/trunk/vector/v.to.rast3/v.to.rast3.html
   grass/trunk/vector/v.transform/v.transform.html
   grass/trunk/vector/v.type/v.type.html
   grass/trunk/vector/v.univar/v.univar.html
   grass/trunk/vector/v.vect.stats/v.vect.stats.html
   grass/trunk/vector/v.vol.rst/v.vol.rst.html
   grass/trunk/vector/v.voronoi/v.voronoi.html
   grass/trunk/vector/v.what.rast/v.what.rast.html
   grass/trunk/vector/v.what/v.what.html
   grass/trunk/vector/vectorintro.html
   grass/trunk/visualization/nviz/html/bugs_todo.html
   grass/trunk/visualization/nviz/html/index.html
   grass/trunk/visualization/nviz/html/nviz_3dsetting.html
   grass/trunk/visualization/nviz/html/nviz_credit.html
   grass/trunk/visualization/nviz/html/nviz_desc.html
   grass/trunk/visualization/nviz/html/nviz_hints.html
   grass/trunk/visualization/nviz/html/nviz_image.html
   grass/trunk/visualization/nviz/html/nviz_panel_anim.html
   grass/trunk/visualization/nviz/html/nviz_panel_color.html
   grass/trunk/visualization/nviz/html/nviz_panel_cplane.html
   grass/trunk/visualization/nviz/html/nviz_panel_dsf.html
   grass/trunk/visualization/nviz/html/nviz_panel_dsf1.html
   grass/trunk/visualization/nviz/html/nviz_panel_dsf2.html
   grass/trunk/visualization/nviz/html/nviz_panel_dsf3.html
   grass/trunk/visualization/nviz/html/nviz_panel_kanim.html
   grass/trunk/visualization/nviz/html/nviz_panel_labels.html
   grass/trunk/visualization/nviz/html/nviz_panel_lights.html
   grass/trunk/visualization/nviz/html/nviz_panel_move.html
   grass/trunk/visualization/nviz/html/nviz_panel_pos.html
   grass/trunk/visualization/nviz/html/nviz_panel_scale.html
   grass/trunk/visualization/nviz/html/nviz_panel_sdiff.html
   grass/trunk/visualization/nviz/html/nviz_panel_sites.html
   grass/trunk/visualization/nviz/html/nviz_panel_surf.html
   grass/trunk/visualization/nviz/html/nviz_panel_vect.html
   grass/trunk/visualization/nviz/html/nviz_panel_vol.html
   grass/trunk/visualization/nviz/html/nviz_panel_what.html
   grass/trunk/visualization/nviz/html/nviz_quit.html
   grass/trunk/visualization/nviz/html/nviz_script.html
   grass/trunk/visualization/nviz/html/nviz_startup.html
   grass/trunk/visualization/nviz/html/nviz_state.html
   grass/trunk/visualization/nviz/html/nviz_toc.html
   grass/trunk/visualization/nviz/nviz.html
   grass/trunk/visualization/xganim/xganim.html
Log:
use lowercase HTML tags

Modified: grass/trunk/db/db.columns/db.columns.html
===================================================================

--- grass/trunk/db/db.columns/db.columns.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/db/db.columns/db.columns.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -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>
@@ -31,14 +31,14 @@
 </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>
 

Modified: grass/trunk/db/db.connect/db.connect.html
===================================================================
--- grass/trunk/db/db.connect/db.connect.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/db/db.connect/db.connect.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -5,17 +5,17 @@
 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 -p
 db.tables -p
 </pre></div>
-<P>
+<p>
 The SQLite database is created automatically when used the first time.
 
 
@@ -109,13 +109,13 @@
 <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>

Modified: grass/trunk/db/db.copy/db.copy.html
===================================================================
--- grass/trunk/db/db.copy/db.copy.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/db/db.copy/db.copy.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -6,7 +6,7 @@
 <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 @@
 
 <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>
 

Modified: grass/trunk/db/db.createdb/db.createdb.html
===================================================================
--- grass/trunk/db/db.createdb/db.createdb.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/db/db.createdb/db.createdb.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -23,14 +23,14 @@
 <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>
 

Modified: grass/trunk/db/db.databases/db.databases.html
===================================================================
--- grass/trunk/db/db.databases/db.databases.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/db/db.databases/db.databases.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -5,13 +5,13 @@
 
 <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>
 

Modified: grass/trunk/db/db.describe/db.describe.html
===================================================================
--- grass/trunk/db/db.describe/db.describe.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/db/db.describe/db.describe.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -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 @@
 <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>
 

Modified: grass/trunk/db/db.drivers/db.drivers.html
===================================================================
--- grass/trunk/db/db.drivers/db.drivers.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/db/db.drivers/db.drivers.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -13,14 +13,14 @@
 <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>

Modified: grass/trunk/db/db.dropdb/db.dropdb.html
===================================================================
--- grass/trunk/db/db.dropdb/db.dropdb.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/db/db.dropdb/db.dropdb.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -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>
 

Modified: grass/trunk/db/db.execute/db.execute.html
===================================================================
--- grass/trunk/db/db.execute/db.execute.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/db/db.execute/db.execute.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -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 @@
 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 @@
 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>

Modified: grass/trunk/db/db.login/db.login.html
===================================================================
--- grass/trunk/db/db.login/db.login.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/db/db.login/db.login.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -17,7 +17,7 @@
 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 @@
 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 @@
 
 <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>

Modified: grass/trunk/db/db.select/db.select.html
===================================================================
--- grass/trunk/db/db.select/db.select.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/db/db.select/db.select.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -7,7 +7,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. Output will be displayed to stdout or can
 be directed to a file.
 
@@ -28,21 +28,21 @@
 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 @@
 
 <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>

Modified: grass/trunk/db/db.tables/db.tables.html
===================================================================
--- grass/trunk/db/db.tables/db.tables.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/db/db.tables/db.tables.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -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 @@
 </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>
 ?

Modified: grass/trunk/db/drivers/dbf/grass-dbf.html
===================================================================
--- grass/trunk/db/drivers/dbf/grass-dbf.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/db/drivers/dbf/grass-dbf.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -115,7 +115,7 @@
 </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 @@
 <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>

Modified: grass/trunk/db/drivers/mysql/grass-mesql.html
===================================================================
--- grass/trunk/db/drivers/mysql/grass-mesql.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/db/drivers/mysql/grass-mesql.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -57,19 +57,19 @@
 <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>

Modified: grass/trunk/db/drivers/mysql/grass-mysql.html
===================================================================
--- grass/trunk/db/drivers/mysql/grass-mysql.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/db/drivers/mysql/grass-mysql.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -20,7 +20,7 @@
 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 @@
 <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>

Modified: grass/trunk/db/drivers/odbc/grass-odbc.html
===================================================================
--- grass/trunk/db/drivers/odbc/grass-odbc.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/db/drivers/odbc/grass-odbc.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -44,15 +44,15 @@
 </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 @@
 <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 @@
 
 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>

Modified: grass/trunk/db/drivers/ogr/grass-ogr.html
===================================================================
--- grass/trunk/db/drivers/ogr/grass-ogr.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/db/drivers/ogr/grass-ogr.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -17,11 +17,11 @@
 
 <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>

Modified: grass/trunk/db/drivers/postgres/grass-pg.html
===================================================================
--- grass/trunk/db/drivers/postgres/grass-pg.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/db/drivers/postgres/grass-pg.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -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 @@
 </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 @@
 
 <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 @@
 <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>

Modified: grass/trunk/display/d.barscale/d.barscale.html
===================================================================
--- grass/trunk/display/d.barscale/d.barscale.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/display/d.barscale/d.barscale.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -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>

Modified: grass/trunk/display/d.colorlist/d.colorlist.html
===================================================================
--- grass/trunk/display/d.colorlist/d.colorlist.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/display/d.colorlist/d.colorlist.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -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
 

Modified: grass/trunk/display/d.colors/d.colors.html
===================================================================
--- grass/trunk/display/d.colors/d.colors.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/display/d.colors/d.colors.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -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 @@
 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 @@
 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 @@
 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 @@
 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 @@
 <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 @@
 <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

Modified: grass/trunk/display/d.colortable/d.colortable.html
===================================================================
--- grass/trunk/display/d.colortable/d.colortable.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/display/d.colortable/d.colortable.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -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 @@
 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 @@
 (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
 

Modified: grass/trunk/display/d.extract/d.extract.html
===================================================================
--- grass/trunk/display/d.extract/d.extract.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/display/d.extract/d.extract.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -16,10 +16,10 @@
 
 <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>

Modified: grass/trunk/display/d.font/d.font.html
===================================================================
--- grass/trunk/display/d.font/d.font.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/display/d.font/d.font.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -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 @@
 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.
 

Modified: grass/trunk/display/d.fontlist/d.fontlist.html
===================================================================
--- grass/trunk/display/d.fontlist/d.fontlist.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/display/d.fontlist/d.fontlist.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -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
 

Modified: grass/trunk/display/d.geodesic/d.geodesic.html
===================================================================
--- grass/trunk/display/d.geodesic/d.geodesic.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/display/d.geodesic/d.geodesic.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -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 @@
 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 @@
 
 <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
 

Modified: grass/trunk/display/d.graph/d.graph.html
===================================================================
--- grass/trunk/display/d.graph/d.graph.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/display/d.graph/d.graph.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -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 @@
 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 @@
 
 
 <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 @@
 </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>

Modified: grass/trunk/display/d.grid/d.grid.html
===================================================================
--- grass/trunk/display/d.grid/d.grid.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/display/d.grid/d.grid.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -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 @@
 <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>

Modified: grass/trunk/display/d.his/d.his.html
===================================================================
--- grass/trunk/display/d.his/d.his.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/display/d.his/d.his.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -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 @@
 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 @@
 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 @@
 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 @@
 
 </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 @@
   d.mon x1
   d.his h=elevation.dem i=elev.shad_relf brighten=50
 </pre></div>
-<BR>
+<br>
 
-<H2>SEE ALSO</H2>
+<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>
+<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>
+<h2>AUTHOR</h2>
 
 James Westervelt, U.S. Army Construction Engineering Research Laboratory
 

Modified: grass/trunk/display/d.histogram/d.histogram.html
===================================================================
--- grass/trunk/display/d.histogram/d.histogram.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/display/d.histogram/d.histogram.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -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 @@
 <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>

Modified: grass/trunk/display/d.info/d.info.html
===================================================================
--- grass/trunk/display/d.info/d.info.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/display/d.info/d.info.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -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>
 

Modified: grass/trunk/display/d.labels/d.labels.html
===================================================================
--- grass/trunk/display/d.labels/d.labels.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/display/d.labels/d.labels.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -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 

Modified: grass/trunk/display/d.legend/d.legend.html
===================================================================
--- grass/trunk/display/d.legend/d.legend.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/display/d.legend/d.legend.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -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 @@
 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 @@
 <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 @@
 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>

Modified: grass/trunk/display/d.linegraph/d.linegraph.html
===================================================================
--- grass/trunk/display/d.linegraph/d.linegraph.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/display/d.linegraph/d.linegraph.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -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 @@
 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 @@
 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 @@
 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>

Modified: grass/trunk/display/d.measure/d.measure.html
===================================================================
--- grass/trunk/display/d.measure/d.measure.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/display/d.measure/d.measure.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -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 @@
 <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
 

Modified: grass/trunk/display/d.path/d.path.html
===================================================================
--- grass/trunk/display/d.path/d.path.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/display/d.path/d.path.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -13,7 +13,7 @@
 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 @@
 <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>

Modified: grass/trunk/display/d.profile/d.profile.html
===================================================================
--- grass/trunk/display/d.profile/d.profile.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/display/d.profile/d.profile.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -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
 

Modified: grass/trunk/display/d.rast/d.rast.html
===================================================================
--- grass/trunk/display/d.rast/d.rast.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/display/d.rast/d.rast.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -8,9 +8,9 @@
 
 <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>

Modified: grass/trunk/display/d.rast.arrow/d.rast.arrow.html
===================================================================
--- grass/trunk/display/d.rast.arrow/d.rast.arrow.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/display/d.rast.arrow/d.rast.arrow.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -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 @@
 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 @@
 </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 @@
 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>

Modified: grass/trunk/display/d.rast.num/d.rast.num.html
===================================================================
--- grass/trunk/display/d.rast.num/d.rast.num.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/display/d.rast.num/d.rast.num.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -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 @@
 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 @@
 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 @@
 <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>

Modified: grass/trunk/display/d.rgb/d.rgb.html
===================================================================
--- grass/trunk/display/d.rgb/d.rgb.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/display/d.rgb/d.rgb.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -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 @@
 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 @@
 <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 @@
 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.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.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.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
 

Modified: grass/trunk/display/d.rhumbline/d.rhumbline.html
===================================================================
--- grass/trunk/display/d.rhumbline/d.rhumbline.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/display/d.rhumbline/d.rhumbline.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -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 @@
 
  <!-- 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 @@
 
 <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 

Modified: grass/trunk/display/d.text/d.text.html
===================================================================
--- grass/trunk/display/d.text/d.text.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/display/d.text/d.text.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -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 @@
 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 @@
 
 <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 @@
 </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>

Modified: grass/trunk/display/d.thematic.area/d.thematic.area.html
===================================================================
--- grass/trunk/display/d.thematic.area/d.thematic.area.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/display/d.thematic.area/d.thematic.area.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -1,4 +1,4 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
 <em>d.thematic.area</em> draws thematic coropleth vector maps based on an attribute column or an expression involving several columns. It takes a list of class breaks (excluding the minimum and maximum values) and a list of colors to apply to the classes (has to be the number of class breaks + 1).
 
@@ -7,7 +7,7 @@
 The <em>-l</em> flag instructs the module to print legend information (class min | class max | number of observations in class | color) to standard output for futher use in graphical software. When combined with the <em>-e</em> flag, the legend information will be extended with some additional statistical information. If the <em>-n</em> flag is set, the module will only print the legend information without drawing the map. If the user gives a <em>legendfile</em>, the module will write d.graph instructions for painting a legend into that file.
 
 
-<H2>EXAMPLE</H2>
+<h2>EXAMPLE</h2>
 
 <div class="code"><pre>
 d.thematic.area -l map=communes3 data=pop breaks=111393.250000,222785.500000,334177.750000 colors=255:0:0,0:255:0,0:0:255,0,0,0
@@ -18,14 +18,14 @@
 d.thematic.area -l map=communes2 data=pop/area algorithm=std nbclasses=5 colors=0:0:255,50:100:255,255:100:50,255:0:0,156:0:0
 </pre></div>
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
-<EM><A HREF="v.class.html">v.class</A></EM>
-<EM><A HREF="d.vect.html">d.vect</A></EM>
-<EM><A HREF="d.graph.html">d.graph</A></EM>
-<EM><A HREF="v.univar.html">v.univar</A></EM>
+<em><a href="v.class.html">v.class</A></em>
+<em><a href="d.vect.html">d.vect</A></em>
+<em><a href="d.graph.html">d.graph</A></em>
+<em><a href="v.univar.html">v.univar</A></em>
 
 
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
 
 Moritz Lennert

Modified: grass/trunk/display/d.title/d.title.html
===================================================================
--- grass/trunk/display/d.title/d.title.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/display/d.title/d.title.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -1,59 +1,59 @@
-<H2>DESCRIPTION</H2>
+<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
+<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

Modified: grass/trunk/display/d.vect.chart/d.vect.chart.html
===================================================================
--- grass/trunk/display/d.vect.chart/d.vect.chart.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/display/d.vect.chart/d.vect.chart.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -41,11 +41,11 @@
 
 <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>
 

Modified: grass/trunk/display/d.what.rast/d.what.rast.html
===================================================================
--- grass/trunk/display/d.what.rast/d.what.rast.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/display/d.what.rast/d.what.rast.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -140,16 +140,16 @@
 
 <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>
 

Modified: grass/trunk/display/d.what.vect/d.what.vect.html
===================================================================
--- grass/trunk/display/d.what.vect/d.what.vect.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/display/d.what.vect/d.what.vect.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -11,7 +11,7 @@
 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 @@
 
 <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>
 
 

Modified: grass/trunk/display/d.where/d.where.html
===================================================================
--- grass/trunk/display/d.where/d.where.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/display/d.where/d.where.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -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 @@
 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 @@
 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 @@
 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
 

Modified: grass/trunk/display/d.zoom/d.zoom.html
===================================================================
--- grass/trunk/display/d.zoom/d.zoom.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/display/d.zoom/d.zoom.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -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 @@
 <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 @@
 
 <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>
 

Modified: grass/trunk/doc/projectionintro.html
===================================================================
--- grass/trunk/doc/projectionintro.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/doc/projectionintro.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -26,9 +26,9 @@
  <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 @@
 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>

Modified: grass/trunk/doc/raster/r.example/r.example.html
===================================================================
--- grass/trunk/doc/raster/r.example/r.example.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/doc/raster/r.example/r.example.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -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
 

Modified: grass/trunk/doc/vector/v.example/v.example.html
===================================================================
--- grass/trunk/doc/vector/v.example/v.example.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/doc/vector/v.example/v.example.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -10,9 +10,9 @@
 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>
 

Modified: grass/trunk/doc/vector/v.modules.html
===================================================================
--- grass/trunk/doc/vector/v.modules.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/doc/vector/v.modules.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -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 at itc.it>blazek at itc.it</A>
+information to <a href=mailto:blazek at itc.it>blazek at itc.it</A>
 before you start.
 
 <HR>
@@ -71,7 +71,7 @@
 <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 @@
 <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>
 

Modified: grass/trunk/doc/vector/vector.html
===================================================================
--- grass/trunk/doc/vector/vector.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/doc/vector/vector.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -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 @@
 
 <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 @@
 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 @@
 </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)
 

Modified: grass/trunk/general/g.access/g.access.html
===================================================================
--- grass/trunk/general/g.access/g.access.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/general/g.access/g.access.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -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

Modified: grass/trunk/general/g.cairocomp/g.cairocomp.html
===================================================================
--- grass/trunk/general/g.cairocomp/g.cairocomp.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/general/g.cairocomp/g.cairocomp.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -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>

Modified: grass/trunk/general/g.copy/g.copy.html
===================================================================
--- grass/trunk/general/g.copy/g.copy.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/general/g.copy/g.copy.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -44,9 +44,9 @@
 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 @@
 
 <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>
 

Modified: grass/trunk/general/g.dirseps/g.dirseps.html
===================================================================
--- grass/trunk/general/g.dirseps/g.dirseps.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/general/g.dirseps/g.dirseps.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -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
 

Modified: grass/trunk/general/g.filename/g.filename.html
===================================================================
--- grass/trunk/general/g.filename/g.filename.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/general/g.filename/g.filename.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -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 @@
 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 @@
 </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

Modified: grass/trunk/general/g.findetc/g.findetc.html
===================================================================
--- grass/trunk/general/g.findetc/g.findetc.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/general/g.findetc/g.findetc.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -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
 

Modified: grass/trunk/general/g.gui/g.gui.html
===================================================================
--- grass/trunk/general/g.gui/g.gui.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/general/g.gui/g.gui.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -42,7 +42,7 @@
 
 <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>

Modified: grass/trunk/general/g.list/g.list.html
===================================================================
--- grass/trunk/general/g.list/g.list.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/general/g.list/g.list.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -9,7 +9,7 @@
 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 @@
 <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 @@
 
 <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>

Modified: grass/trunk/general/g.mapset/g.mapset.html
===================================================================
--- grass/trunk/general/g.mapset/g.mapset.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/general/g.mapset/g.mapset.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -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>
 

Modified: grass/trunk/general/g.mapsets/g.mapsets.html
===================================================================
--- grass/trunk/general/g.mapsets/g.mapsets.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/general/g.mapsets/g.mapsets.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -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 @@
 <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 @@
 
 
 <div class="code"><pre>
-<b><a HREF="g.copy.html">g.copy</a> rast=</b><em>'soils.file at PERMANENT',my.soils</em>
+<b><a href="g.copy.html">g.copy</a> rast=</b><em>'soils.file at PERMANENT',my.soils</em>
 </pre></div>
 
 
@@ -109,7 +109,7 @@
 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 @@
 <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>

Modified: grass/trunk/general/g.message/g.message.html
===================================================================
--- grass/trunk/general/g.message/g.message.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/general/g.message/g.message.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -6,43 +6,43 @@
 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 @@
 <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

Modified: grass/trunk/general/g.mkfontcap/g.mkfontcap.html
===================================================================
--- grass/trunk/general/g.mkfontcap/g.mkfontcap.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/general/g.mkfontcap/g.mkfontcap.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -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 @@
 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
 

Modified: grass/trunk/general/g.mlist/g.mlist.html
===================================================================
--- grass/trunk/general/g.mlist/g.mlist.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/general/g.mlist/g.mlist.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -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>

Modified: grass/trunk/general/g.mremove/g.mremove.html
===================================================================
--- grass/trunk/general/g.mremove/g.mremove.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/general/g.mremove/g.mremove.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -14,7 +14,7 @@
 
 <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)
 

Modified: grass/trunk/general/g.parser/g.parser.html
===================================================================
--- grass/trunk/general/g.parser/g.parser.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/general/g.parser/g.parser.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -414,9 +414,9 @@
 <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.

Modified: grass/trunk/general/g.pnmcat/g.pnmcat.html
===================================================================
--- grass/trunk/general/g.pnmcat/g.pnmcat.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/general/g.pnmcat/g.pnmcat.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -1,4 +1,4 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 <p>
 Concatenate PNM tiles into a single image.
 <p>
@@ -18,7 +18,7 @@
 <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>

Modified: grass/trunk/general/g.pnmcomp/g.pnmcomp.html
===================================================================
--- grass/trunk/general/g.pnmcomp/g.pnmcomp.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/general/g.pnmcomp/g.pnmcomp.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -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 @@
 the existence of g.pnmcomp.
 </pre>
 
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
 Glynn Clements
 
 <p><i>Last changed: $Date$</i>

Modified: grass/trunk/general/g.ppmtopng/g.ppmtopng.html
===================================================================
--- grass/trunk/general/g.ppmtopng/g.ppmtopng.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/general/g.ppmtopng/g.ppmtopng.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -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>

Modified: grass/trunk/general/g.proj/g.proj.html
===================================================================
--- grass/trunk/general/g.proj/g.proj.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/general/g.proj/g.proj.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -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 @@
 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 @@
 
 <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 @@
 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 @@
 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 @@
 </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 @@
 <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>
 

Modified: grass/trunk/general/g.region/g.region.html
===================================================================
--- grass/trunk/general/g.region/g.region.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/general/g.region/g.region.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -43,7 +43,7 @@
 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 @@
 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 @@
 <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>
 
 

Modified: grass/trunk/general/g.remove/g.remove.html
===================================================================
--- grass/trunk/general/g.remove/g.remove.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/general/g.remove/g.remove.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -11,7 +11,7 @@
 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 @@
 
 <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>

Modified: grass/trunk/general/g.rename/g.rename.html
===================================================================
--- grass/trunk/general/g.rename/g.rename.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/general/g.rename/g.rename.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -72,9 +72,9 @@
 </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>
 

Modified: grass/trunk/general/g.setproj/g.setproj.html
===================================================================
--- grass/trunk/general/g.setproj/g.setproj.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/general/g.setproj/g.setproj.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -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 @@
 <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>

Modified: grass/trunk/general/g.tempfile/g.tempfile.html
===================================================================
--- grass/trunk/general/g.tempfile/g.tempfile.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/general/g.tempfile/g.tempfile.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -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 @@
 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 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 

Modified: grass/trunk/imagery/i.albedo/i.albedo.html
===================================================================
--- grass/trunk/imagery/i.albedo/i.albedo.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/imagery/i.albedo/i.albedo.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -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 @@
 </em>
 
 
-<H2>AUTHORS</H2>
+<h2>AUTHORS</h2>
 
 Yann Chemin, International Rice Research Institute, The Philippines
 

Modified: grass/trunk/imagery/i.aster.toar/i.aster.toar.html
===================================================================
--- grass/trunk/imagery/i.aster.toar/i.aster.toar.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/imagery/i.aster.toar/i.aster.toar.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -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 @@
     /*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>

Modified: grass/trunk/imagery/i.biomass/i.biomass.html
===================================================================
--- grass/trunk/imagery/i.biomass/i.biomass.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/imagery/i.biomass/i.biomass.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -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 @@
  <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>

Modified: grass/trunk/imagery/i.cca/i.cca.html
===================================================================
--- grass/trunk/imagery/i.cca/i.cca.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/imagery/i.cca/i.cca.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -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 @@
 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 @@
 
 <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

Modified: grass/trunk/imagery/i.class/i.class.html
===================================================================
--- grass/trunk/imagery/i.class/i.class.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/imagery/i.class/i.class.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -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 @@
 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 @@
                    (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 @@
 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 @@
 </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 @@
 
 <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 @@
 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 @@
 
 
 
-<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 @@
 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 @@
 
 <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 @@
 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 @@
 
 <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 @@
 
 <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 @@
 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 @@
 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 @@
 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 @@
 </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>
+<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>
+<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>
+<h2>AUTHOR</h2>
 
 David Satnik, 
 Central Washington University

Modified: grass/trunk/imagery/i.cluster/i.cluster.html
===================================================================
--- grass/trunk/imagery/i.cluster/i.cluster.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/imagery/i.cluster/i.cluster.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -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 @@
 
 <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 @@
 </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 @@
 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 @@
 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 @@
 <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 @@
 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 @@
 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 @@
 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 @@
 </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 

Modified: grass/trunk/imagery/i.eb.eta/i.eb.eta.html
===================================================================
--- grass/trunk/imagery/i.eb.eta/i.eb.eta.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/imagery/i.eb.eta/i.eb.eta.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -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 @@
 
 <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 @@
 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>

Modified: grass/trunk/imagery/i.eb.evapfr/i.eb.evapfr.html
===================================================================
--- grass/trunk/imagery/i.eb.evapfr/i.eb.evapfr.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/imagery/i.eb.evapfr/i.eb.evapfr.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -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 @@
 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>

Modified: grass/trunk/imagery/i.eb.h_SEBAL01/i.eb.h_sebal01.html
===================================================================
--- grass/trunk/imagery/i.eb.h_SEBAL01/i.eb.h_sebal01.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/imagery/i.eb.h_SEBAL01/i.eb.h_sebal01.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -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 @@
 
 (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 @@
 </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 @@
 </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 @@
 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.

Modified: grass/trunk/imagery/i.eb.netrad/i.eb.netrad.html
===================================================================
--- grass/trunk/imagery/i.eb.netrad/i.eb.netrad.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/imagery/i.eb.netrad/i.eb.netrad.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -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 @@
 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>

Modified: grass/trunk/imagery/i.eb.soilheatflux/i.eb.soilheatflux.html
===================================================================
--- grass/trunk/imagery/i.eb.soilheatflux/i.eb.soilheatflux.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/imagery/i.eb.soilheatflux/i.eb.soilheatflux.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -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 @@
    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>

Modified: grass/trunk/imagery/i.emissivity/i.emissivity.html
===================================================================
--- grass/trunk/imagery/i.emissivity/i.emissivity.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/imagery/i.emissivity/i.emissivity.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -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>

Modified: grass/trunk/imagery/i.evapo.mh/i.evapo.mh.html
===================================================================
--- grass/trunk/imagery/i.evapo.mh/i.evapo.mh.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/imagery/i.evapo.mh/i.evapo.mh.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -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 @@
 
 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>

Modified: grass/trunk/imagery/i.evapo.pm/i.evapo.pm.html
===================================================================
--- grass/trunk/imagery/i.evapo.pm/i.evapo.pm.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/imagery/i.evapo.pm/i.evapo.pm.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -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 @@
 
 <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 @@
 <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 @@
 
 
 
-<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 @@
   <p>Contact: <a href="mailto:massimiliano.cannata at 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. 

Modified: grass/trunk/imagery/i.evapo.pt/i.evapo.pt.html
===================================================================
--- grass/trunk/imagery/i.evapo.pt/i.evapo.pt.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/imagery/i.evapo.pt/i.evapo.pt.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -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 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>

Modified: grass/trunk/imagery/i.evapo.time/i.evapo.time.html
===================================================================
--- grass/trunk/imagery/i.evapo.time/i.evapo.time.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/imagery/i.evapo.time/i.evapo.time.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -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 @@
 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 @@
 
 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>

Modified: grass/trunk/imagery/i.fft/i.fft.html
===================================================================
--- grass/trunk/imagery/i.fft/i.fft.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/imagery/i.fft/i.fft.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -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 @@
 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

Modified: grass/trunk/imagery/i.gensig/i.gensig.html
===================================================================
--- grass/trunk/imagery/i.gensig/i.gensig.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/imagery/i.gensig/i.gensig.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -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 @@
 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

Modified: grass/trunk/imagery/i.gensigset/i.gensigset.html
===================================================================
--- grass/trunk/imagery/i.gensigset/i.gensigset.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/imagery/i.gensigset/i.gensigset.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -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 @@
 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 @@
 </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 @@
 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 @@
 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 @@
 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 

Modified: grass/trunk/imagery/i.group/i.group.html
===================================================================
--- grass/trunk/imagery/i.group/i.group.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/imagery/i.group/i.group.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -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 

Modified: grass/trunk/imagery/i.his.rgb/i.his.rgb.html
===================================================================
--- grass/trunk/imagery/i.his.rgb/i.his.rgb.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/imagery/i.his.rgb/i.his.rgb.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -1,7 +1,7 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
 
-<EM>i.his.rgb</EM> is an image processing program that
+<em>i.his.rgb</em> is an image processing program that
 processes three input raster map layers as hue, intensity
 and saturation components and produces three output raster
 map layers representing the red, green and blue components
@@ -11,13 +11,13 @@
 is given a linear gray scale color table.  The current
 geographic region and mask settings are respected.
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 
 It is not possible to process three bands with
-<EM>i.his.rgb</EM> and then exactly recover the original
+<em>i.his.rgb</em> and then exactly recover the original
 bands with
 
-<EM><A HREF="i.rgb.his.html">i.rgb.his</A></EM>.  
+<em><a href="i.rgb.his.html">i.rgb.his</A></em>.  
 
 This is due to loss of precision because of integer
 computations and rounding.  Tests have shown that more than
@@ -26,16 +26,16 @@
 be within plus or minus 1.  A few cell values may differ
 significantly from their original values.
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
-<EM><A HREF="r.colors.html">r.colors</A></EM>
+<em><a href="r.colors.html">r.colors</A></em>
 
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
 
 David Satnik, GIS Laboratory, 
 Central Washington University
 
-<P>
+<p>
 
 with acknowledgements to Ali Vali, Univ. of Texas Space Research
 Center, for the core routine.

Modified: grass/trunk/imagery/i.ifft/i.ifft.html
===================================================================
--- grass/trunk/imagery/i.ifft/i.ifft.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/imagery/i.ifft/i.ifft.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -1,53 +1,53 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
 
-<EM>i.ifft</EM> is an image processing program based on the algorithm given
+<em>i.ifft</em> is an image processing program based on the algorithm given
 by Frigo et al. (1998), that converts real and imaginary frequency space
 images (produced by
-<EM><A HREF="i.fft.html">i.fft</A></EM>) into a normal image.
+<em><a href="i.fft.html">i.fft</A></em>) into a normal image.
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 
 The current mask is respected when reading the real and
 imaginary component files;  thus, creating a mask is a 
 primary step for
 selecting the portion of the frequency space data to be included in the
-inverse transform.  The GRASS program <EM>r.digit</EM> can be used to create
+inverse transform.  The GRASS program <em>r.digit</em> can be used to create
 masks while viewing the real or imaginary component image. Alternatively
 <em>r.circle</em> can be used to generate high-, low- and donut filters
 specifying the DC point as circle/ring center.
-When <EM>i.ifft</EM> is executed, it (automatically) uses the same GRASS
+When <em>i.ifft</em> is executed, it (automatically) uses the same GRASS
 region definition setting that was used during the original transformation
-done with <EM><A HREF="i.fft.html">i.fft</A></EM>.
+done with <em><a href="i.fft.html">i.fft</A></em>.
 
-<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 program author and Ali R. Vali, Space Research Center,
 University of Texas, Austin, 1990.
 
-<P>
+<p>
 
-<EM><A HREF="i.cca.html">i.cca</A></EM>, 
-<EM><A HREF="i.class.html">i.class</A></EM>, 
-<EM><A HREF="i.fft.html">i.fft</A></EM>, 
-<EM><A HREF="i.pca.html">i.pca</A></EM>, 
-<EM><A HREF="r.circle.html">r.circle</A></EM>
+<em><a href="i.cca.html">i.cca</A></em>, 
+<em><a href="i.class.html">i.class</A></em>, 
+<em><a href="i.fft.html">i.fft</A></em>, 
+<em><a href="i.pca.html">i.pca</A></em>, 
+<em><a href="r.circle.html">r.circle</A></em>
 
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
 
 David Satnik, GIS Laboratory, 
 Central Washington University

Modified: grass/trunk/imagery/i.landsat.acca/i.landsat.acca.html
===================================================================
--- grass/trunk/imagery/i.landsat.acca/i.landsat.acca.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/imagery/i.landsat.acca/i.landsat.acca.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -47,7 +47,7 @@
     4049: 348-355.</li>
 </ol>
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
 <em>
   <a href="i.landsat.toar.html">i.landsat.toar</a>

Modified: grass/trunk/imagery/i.landsat.toar/i.landsat.toar.html
===================================================================
--- grass/trunk/imagery/i.landsat.toar/i.landsat.toar.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/imagery/i.landsat.toar/i.landsat.toar.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -208,9 +208,9 @@
 <h2>SEE ALSO</h2>
 
 <em>
-  <A href="i.atcorr.html">i.atcorr</a>,
-  <A href="r.mapcalc.html">r.mapcalc</a>,
-  <A href="r.in.gdal.html">r.in.gdal</a>
+  <a href="i.atcorr.html">i.atcorr</a>,
+  <a href="r.mapcalc.html">r.mapcalc</a>,
+  <a href="r.in.gdal.html">r.in.gdal</a>
 </em>
 
 <h2>AUTHOR</h2>

Modified: grass/trunk/imagery/i.latlong/i.latlong.html
===================================================================
--- grass/trunk/imagery/i.latlong/i.latlong.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/imagery/i.latlong/i.latlong.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -1,25 +1,25 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
-<EM>i.latlong</EM> creates a latitude (degree decimal) map, or longitude
+<em>i.latlong</em> creates a latitude (degree decimal) map, or longitude
 if the -l flag is used, from any map in any projection using PROJ.4 library. 
 This is an input to <em>r.sun</em> and <em>i.evapo.potrad</em>.
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 
-The PROJ.4 <A HREF="http://trac.osgeo.org/proj/">website</A>.
+The PROJ.4 <a href="http://trac.osgeo.org/proj/">website</A>.
 
-<H2>TODO</H2>
+<h2>TODO</h2>
 Datum transform is not implemented, the same datum is taken as output.
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
 <em>
-<A HREF="i.evapo.potrad.html">i.evapo.potrad</A><br>
-<A HREF="r.sun.html">r.sun</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, International Rice Research Institute, The Philippines.<br>
 

Modified: grass/trunk/imagery/i.maxlik/i.maxlik.html
===================================================================
--- grass/trunk/imagery/i.maxlik/i.maxlik.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/imagery/i.maxlik/i.maxlik.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -1,48 +1,48 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
 
-<EM>i.maxlik</EM> is a maximum-likelihood discriminant
+<em>i.maxlik</em> is a maximum-likelihood discriminant
 analysis classifier.  It can be used to perform the second
 step in either an unsupervised or a supervised image
 classification.
 
-<P>
+<p>
 Either image classification methods are performed in two
 steps.  The first step in an unsupervised image
 classification is performed by
-<EM><A HREF="i.cluster.html">i.cluster</A></EM>; the
+<em><a href="i.cluster.html">i.cluster</A></em>; the
 first step in a supervised classification is executed by
-the GRASS program <EM>
-<A HREF="i.class.html">i.class</A></EM>. In both cases,
+the GRASS program <em>
+<a href="i.class.html">i.class</A></em>. In both cases,
 the second step in the image classification procedure is
-performed by <EM>i.maxlik</EM>.
+performed by <em>i.maxlik</em>.
 
 
-<P>
+<p>
 In an unsupervised classification, the maximum-likelihood
 classifier uses the cluster means and covariance matrices
-from the <EM><A HREF="i.cluster.html">i.cluster</A></EM>
+from the <em><a href="i.cluster.html">i.cluster</A></em>
 signature file to determine to which category (spectral
 class) each cell in the image has the highest probability
 of belonging. In a supervised image classification, the
 maximum-likelihood classifier uses the region means and
 covariance matrices from the spectral signature file
-generated by <EM>
-<A HREF="i.class.html">i.class</A></EM>, based on regions
+generated by <em>
+<a href="i.class.html">i.class</A></em>, based on regions
 (groups of image pixels) chosen by the user, to determine
 to which category each cell in the image has the highest
 probability of belonging.
 
 
-<P>
+<p>
 In either case, the raster map layer output by
-<EM>i.maxlik</EM> is a classified image in which each cell
+<em>i.maxlik</em> is a classified image in which each cell
 has been assigned to a spectral class (i.e., a category).
 The spectral classes (categories) can be related to
 specific land cover types on the ground.
 
 
-<P>
+<p>
 The program will run non-interactively if the user
 specifies the names of raster map layers, i.e., group and
 subgroup names, seed signature file name, result
@@ -52,23 +52,23 @@
 
 <DL>
 <DD>
-<B>i.maxlik</B>[<B>-q</B>] <B>group=</B><EM>name</EM> 
-<B>subgroup=</B><EM>name</EM>
-<B>sigfile=</B><EM>name</EM> <B>class=</B><EM>name</EM> 
-[<B>reject=</B><EM>name</EM>]
+<B>i.maxlik</B>[<B>-q</B>] <B>group=</B><em>name</em> 
+<B>subgroup=</B><em>name</em>
+<B>sigfile=</B><em>name</em> <B>class=</B><em>name</em> 
+[<B>reject=</B><em>name</em>]
 </DL>
 
 where each flag and options have the meanings stated below.
 
-<P>
+<p>
 
-Alternatively, the user can simply type <EM>i.maxlik</EM>
+Alternatively, the user can simply type <em>i.maxlik</em>
 in the command line without program arguments. In this case
 the user will be prompted for the program parameter
 settings; the program will run foreground.
 
 
-<H2>OPTIONS</H2>
+<h2>OPTIONS</h2>
 
 
 <H3>Flags:</H3>
@@ -85,40 +85,40 @@
 
 <DL>
 
-<DT><B>group=</B><EM>name</EM> 
+<DT><B>group=</B><em>name</em> 
 
-<DD>The <A HREF="i.group.html">imagery</A> group 
+<DD>The <a href="i.group.html">imagery</A> group 
 contains the subgroup to be classified.
 
-<DT><B>subgroup=</B><EM>name</EM> 
+<DT><B>subgroup=</B><em>name</em> 
 
 <DD>The subgroup contains image files, which were used to create 
 the signature file
-in the program <EM><A HREF="i.cluster.html">i.cluster</A></EM>, 
-<EM><A HREF="i.class.html">i.class</A></EM>, or 
-<EM><A HREF="i.gensig.html">i.gensig</A></EM> to be classified.
+in the program <em><a href="i.cluster.html">i.cluster</A></em>, 
+<em><a href="i.class.html">i.class</A></em>, or 
+<em><a href="i.gensig.html">i.gensig</A></em> to be classified.
 
-<DT><B>sigfile=</B><EM>name</EM> 
+<DT><B>sigfile=</B><em>name</em> 
 
 <DD>The name of the signatures to be used for the
 classification. The signature file contains the cluster and
 covariance matrices that were calculated by the GRASS
-program <EM><A HREF="i.cluster.html">i.cluster</A></EM>
+program <em><a href="i.cluster.html">i.cluster</A></em>
 (or the region means and covariance matrices generated by
-<EM><A HREF="i.class.html">i.class</A></EM>, if the
+<em><a href="i.class.html">i.class</A></em>, if the
 user runs a supervised classification). These spectral
 signatures are what determine the categories (classes) to
 which image pixels will be assigned during the
 classification process.
 
-<DT><B>class=</B><EM>name</EM> 
+<DT><B>class=</B><em>name</em> 
 
 <DD>The name of a raster map holds the classification
 results. This new raster map layer will contain categories
 that can be related to land cover categories on the
 ground.
 
-<DT><B>reject=</B><EM>name</EM> 
+<DT><B>reject=</B><em>name</em> 
 
 <DD>The optional name of a raster map holds the reject
 threshold results. This is the result of a chi square test
@@ -134,51 +134,51 @@
 </DL>
 
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 
 The maximum-likelihood classifier assumes that the spectral 
 signatures for each class (category) in each band file
 are normally distributed (i.e., Gaussian in nature).
 Algorithms, such as
-<EM><A HREF="i.cluster.html">i.cluster</A></EM>,
-<EM><A HREF="i.class.html">i.class</A></EM>,
-or <EM><A HREF="i.gensig.html">i.gensig</A></EM>,
+<em><a href="i.cluster.html">i.cluster</A></em>,
+<em><a href="i.class.html">i.class</A></em>,
+or <em><a href="i.gensig.html">i.gensig</A></em>,
 however, can create signatures that are not valid 
 distributed (more likely with 
-<EM><A HREF="i.class.html">i.class</A>).</EM>
+<em><a href="i.class.html">i.class</A>).</em>
 If this occurs, 
-<EM>i.maxlik</EM>
+<em>i.maxlik</em>
 will reject them and display a warning message.
 
-<P>
+<p>
 This program runs interactively if the user types
-<EM>i.maxlik</EM> only. If the user types <EM>i.maxlik</EM>
+<em>i.maxlik</em> only. If the user types <em>i.maxlik</em>
 along with all required options, it will overwrite the
 classified raster map without prompting if this map
 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>
-<EM>
-<A HREF="i.class.html">i.class</A><br>
-<A HREF="i.cluster.html">i.cluster</A><br>
-<A HREF="i.gensig.html">i.gensig</A><br>
-<A HREF="i.group.html">i.group</A>
-</EM>
+<p>
+<em>
+<a href="i.class.html">i.class</A><br>
+<a href="i.cluster.html">i.cluster</A><br>
+<a href="i.gensig.html">i.gensig</A><br>
+<a href="i.group.html">i.group</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 Urbana-Champaign,
 Illinois

Modified: grass/trunk/imagery/i.modis.qc/i.modis.qc.html
===================================================================
--- grass/trunk/imagery/i.modis.qc/i.modis.qc.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/imagery/i.modis.qc/i.modis.qc.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -1,9 +1,9 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
-<EM>i.modis.qc</EM> Extracts Requested Quality Assessment flags from the following Modis products: MOD09A1, MOD09Q1, MOD11A1, MOD11A2, MOD13A2, MCD43B2. This does include MOD09A1 QA_state_500m layer (see Notes).
+<em>i.modis.qc</em> Extracts Requested Quality Assessment flags from the following Modis products: MOD09A1, MOD09Q1, MOD11A1, MOD11A2, MOD13A2, MCD43B2. This does include MOD09A1 QA_state_500m layer (see Notes).
 
 <pre>
-<EM>MOD09A1/Q1: MODLAND QA Bits. bits=[0-1]</EM>
+<em>MOD09A1/Q1: MODLAND QA Bits. bits=[0-1]</em>
 </pre>
 <ul>
  <li>[00]= class 0: Corrected product produced at ideal quality -- all bands</li>
@@ -13,7 +13,7 @@
 </ul>
 
 <pre>
-<EM>MOD09Q1: Cloud State. bits=[2-3] </EM>
+<em>MOD09Q1: Cloud State. bits=[2-3] </em>
 </pre>
 <ul>
  <li>[00]= class 0: Clear -- No clouds</li>
@@ -23,8 +23,8 @@
 </ul>
 
 <pre>
-<EM>MOD09Q1: Band-wise Data Quality 250m bits=[4-7][8-11]</EM>
-<EM>MOD09A1: Band-wise Data Quality 500m bits=[2-5][6-9][10-13][14-17][18-21][22-25][26-29]</EM>
+<em>MOD09Q1: Band-wise Data Quality 250m bits=[4-7][8-11]</em>
+<em>MOD09A1: Band-wise Data Quality 500m bits=[2-5][6-9][10-13][14-17][18-21][22-25][26-29]</em>
 </pre>
 <ul>
  <li>[0000]= class 0: highest quality</li>
@@ -41,7 +41,7 @@
 </ul>
 
 <pre>
-<EM>MOD09A1/Q1: Atmospheric correction bit=[12]/[30]</EM>
+<em>MOD09A1/Q1: Atmospheric correction bit=[12]/[30]</em>
 </pre>
 <ul>
  <li>[0]= class 0: Not Corrected product</li>
@@ -49,7 +49,7 @@
 </ul>
 
 <pre>
-<EM>MOD09A1/Q1: Adjacency correction bit=[13]/[31]</EM>
+<em>MOD09A1/Q1: Adjacency correction bit=[13]/[31]</em>
 </pre>
 <ul>
  <li>[0]= class 0: Not Corrected product</li>
@@ -57,7 +57,7 @@
 </ul>
 
 <pre>
-<EM>MOD09Q1: Different orbit from 500m product, bit=[14]</EM>
+<em>MOD09Q1: Different orbit from 500m product, bit=[14]</em>
 </pre>
 <ul>
  <li>[0]= class 0: same orbit as 500m</li>
@@ -65,7 +65,7 @@
 </ul>
 
 <pre>
-<EM>MOD11A1: Mandatory QA Flags bits=[0-1]</EM>
+<em>MOD11A1: Mandatory QA Flags bits=[0-1]</em>
 </pre>
 <ul>
  <li>[00]= class 0: LST produced, good quality, not necessary to examine more detailed QA</li>
@@ -75,7 +75,7 @@
 </ul>
 
 <pre>
-<EM>MOD11A1: Data Quality Flag bits=[2-3]</EM>
+<em>MOD11A1: Data Quality Flag bits=[2-3]</em>
 </pre>
 <ul>
  <li>[00]= class 0: Good data quality of L1B in bands 31 and 32</li>
@@ -85,7 +85,7 @@
 </ul>
 
 <pre>
-<EM>MOD11A1: Emis Error Flag bits=[4-5]</EM>
+<em>MOD11A1: Emis Error Flag bits=[4-5]</em>
 </pre>
 <ul>
  <li>[00]= class 0: Average emissivity error le 0.01</li>
@@ -95,7 +95,7 @@
 </ul>
 
 <pre>
-<EM>MOD11A1: LST Error Flag bits=[6-7]</EM>
+<em>MOD11A1: LST Error Flag bits=[6-7]</em>
 </pre>
 <ul>
  <li>[00]= class 0: Average LST error le 1</li>
@@ -105,7 +105,7 @@
 </ul>
 <pre>
 
-<EM>MOD11A2: Mandatory QA Flags bits=[0-1]</EM>
+<em>MOD11A2: Mandatory QA Flags bits=[0-1]</em>
 </pre>
 <ul>
  <li>[00]= class 0: LST produced, good quality, not necessary to examine more detailed QA</li>
@@ -115,7 +115,7 @@
 </ul>
 
 <pre>
-<EM>MOD11A2: Data Quality Flag bits=[2-3]</EM>
+<em>MOD11A2: Data Quality Flag bits=[2-3]</em>
 </pre>
 <ul>
  <li>[00]= class 0: Good data quality of L1B in 7 TIR bands</li>
@@ -125,7 +125,7 @@
 </ul>
 
 <pre>
-<EM>MOD11A2: Emis Error Flag bits=[4-5]</EM>
+<em>MOD11A2: Emis Error Flag bits=[4-5]</em>
 </pre>
 <ul>
  <li>[00]= class 0: Average emissivity error le 0.01</li>
@@ -135,7 +135,7 @@
 </ul>
 
 <pre>
-<EM>MOD11A2: LST Error Flag bits=[6-7]</EM>
+<em>MOD11A2: LST Error Flag bits=[6-7]</em>
 </pre>
 <ul>
  <li>[00]= class 0: Average LST error le 1</li>
@@ -145,7 +145,7 @@
 </ul>
 
 <pre>
-<EM>MOD09A1s: Cloud State bits=[0-1]</EM>
+<em>MOD09A1s: Cloud State bits=[0-1]</em>
 </pre>
 <ul>
  <li>[00]= class 0: clear</li>
@@ -155,7 +155,7 @@
 </ul>
 
 <pre>
-<EM>MOD09A1s: Cloud shadow bits=[2]</EM>
+<em>MOD09A1s: Cloud shadow bits=[2]</em>
 </pre>
 <ul>
  <li>[0]= class 0: yes</li>
@@ -163,7 +163,7 @@
 </ul>
 
 <pre>
-<EM>MOD09A1s: Land/Water Flag bits=[3-5]</EM>
+<em>MOD09A1s: Land/Water Flag bits=[3-5]</em>
 </pre>
 <ul>
  <li>[000]= class 0: Shallow ocean</li>
@@ -177,7 +177,7 @@
 </ul>
 
 <pre>
-<EM>MOD09A1s: Aerosol Quantity bits=[6-7]</EM>
+<em>MOD09A1s: Aerosol Quantity bits=[6-7]</em>
 </pre>
 <ul>
  <li>[00]= class 0: Climatology</li>
@@ -187,7 +187,7 @@
 </ul>
 
 <pre>
-<EM>MOD09A1s: Cirrus detected bits=[8-9]</EM>
+<em>MOD09A1s: Cirrus detected bits=[8-9]</em>
 </pre>
 <ul>
  <li>[00]= class 0: None</li>
@@ -197,7 +197,7 @@
 </ul>
 
 <pre>
-<EM>MOD09A1s: Internal Cloud Algorithm Flag bits=[10]</EM>
+<em>MOD09A1s: Internal Cloud Algorithm Flag bits=[10]</em>
 </pre>
 <ul>
  <li>[0]= class 0: Cloud</li>
@@ -205,7 +205,7 @@
 </ul>
 
 <pre>
-<EM>MOD09A1s: Internal Fire Algorithm Flag bits=[11]</EM>
+<em>MOD09A1s: Internal Fire Algorithm Flag bits=[11]</em>
 </pre>
 <ul>
  <li>[0]= class 0: Fire</li>
@@ -213,7 +213,7 @@
 </ul>
 
 <pre>
-<EM>MOD09A1s: MOD35 snow/ice flag bits=[12]</EM>
+<em>MOD09A1s: MOD35 snow/ice flag bits=[12]</em>
 </pre>
 <ul>
  <li>[0]= class 0: Yes</li>
@@ -221,7 +221,7 @@
 </ul>
 
 <pre>
-<EM>MOD09A1s: Pixel adjacent to cloud bits=[13]</EM>
+<em>MOD09A1s: Pixel adjacent to cloud bits=[13]</em>
 </pre>
 <ul>
  <li>[0]= class 0: Yes</li>
@@ -229,7 +229,7 @@
 </ul>
 
 <pre>
-<EM>MOD09A1s: BRDF correction performed bits=[14]</EM>
+<em>MOD09A1s: BRDF correction performed bits=[14]</em>
 </pre>
 <ul>
  <li>[0]= class 0: Yes</li>
@@ -237,7 +237,7 @@
 </ul>
 
 <pre>
-<EM>MOD09A1s: Internal Snow Mask bits=[15]</EM>
+<em>MOD09A1s: Internal Snow Mask bits=[15]</em>
 </pre>
 <ul>
  <li>[0]= class 0: Snow</li>
@@ -245,7 +245,7 @@
 </ul>
 
 <pre>
-<EM>MOD13A2: Mandatory QA Flags 1Km bits[0-1]</EM>
+<em>MOD13A2: Mandatory QA Flags 1Km bits[0-1]</em>
 </pre>
 <ul>
  <li>[00]= class 0: VI produced, good quality</li>
@@ -255,7 +255,7 @@
 </ul>
 
 <pre>
-<EM>MOD13A2: VI Usefulness Flag bits[2-5]</EM>
+<em>MOD13A2: VI Usefulness Flag bits[2-5]</em>
 </pre>
 <ul>
  <li>[0000]= class 0: Highest quality</li>
@@ -272,7 +272,7 @@
 </ul>
 
 <pre>
-<EM>MOD13A2: Aerosol quantity Flags 1Km bits[6-7]</EM>
+<em>MOD13A2: Aerosol quantity Flags 1Km bits[6-7]</em>
 </pre>
 <ul>
  <li>[00]= class 0: Climatology</li>
@@ -282,7 +282,7 @@
 </ul>
 
 <pre>
-<EM>MOD13A2: Adjacent cloud detected 1Km bit[8]</EM>
+<em>MOD13A2: Adjacent cloud detected 1Km bit[8]</em>
 </pre>
 <ul>
  <li>[00]= class 0: No</li>
@@ -290,7 +290,7 @@
 </ul>
 
 <pre>
-<EM>MOD13A2: Atmosphere BRDF correction performed 1Km bit[9]</EM>
+<em>MOD13A2: Atmosphere BRDF correction performed 1Km bit[9]</em>
 </pre>
 <ul>
  <li>[00]= class 0: No</li>
@@ -298,7 +298,7 @@
 </ul>
 
 <pre>
-<EM>MOD13A2: Mixed clouds 1Km bit[10]</EM>
+<em>MOD13A2: Mixed clouds 1Km bit[10]</em>
 </pre>
 <ul>
  <li>[00]= class 0: No</li>
@@ -306,7 +306,7 @@
 </ul>
 
 <pre>
-<EM>MOD13A2: Land/Water Flags 1Km bits[11-13]</EM>
+<em>MOD13A2: Land/Water Flags 1Km bits[11-13]</em>
 </pre>
 <ul>
  <li>[000]= class 0: Shallow Ocean</li>
@@ -320,7 +320,7 @@
 </ul>
 
 <pre>
-<EM>MOD13A2: Possible Snow/Ice 1Km bits[14]</EM>
+<em>MOD13A2: Possible Snow/Ice 1Km bits[14]</em>
 </pre>
 <ul>
  <li>[0]= class 0: No</li>
@@ -328,7 +328,7 @@
 </ul>
 
 <pre>
-<EM>MOD13A2: Possible Shadow 1Km bits[15]</EM>
+<em>MOD13A2: Possible Shadow 1Km bits[15]</em>
 </pre>
 <ul>
  <li>[0]= class 0: No</li>
@@ -337,8 +337,8 @@
 
 
 <pre>
-<EM>MCD43B2: Albedo Quality Ancillary Platform Data 1Km bits[0-3]</EM>
-<EM>SDS: BRDF_Albedo_Ancillary</EM>
+<em>MCD43B2: Albedo Quality Ancillary Platform Data 1Km bits[0-3]</em>
+<em>SDS: BRDF_Albedo_Ancillary</em>
 </pre>
 <ul>
  <li>[0000]= class 0: Satellite Platform: Terra</li>
@@ -349,8 +349,8 @@
 </ul>
 
 <pre>
-<EM>MCD43B2: Albedo Quality Ancillary Land/Water Data 1Km bits[4-7]</EM>
-<EM>SDS: BRDF_Albedo_Ancillary</EM>
+<em>MCD43B2: Albedo Quality Ancillary Land/Water Data 1Km bits[4-7]</em>
+<em>SDS: BRDF_Albedo_Ancillary</em>
 </pre>
 <ul>
  <li>[0000] class 0: Shallow Ocean</li>
@@ -366,8 +366,8 @@
 </ul>
 
 <pre>
-<EM>MCD43B2: Albedo Quality Ancillary Sun Zenith Angle at Local Solar Noon Data 1Km bits[8-14]</EM>
-<EM>SDS: BRDF_Albedo_Ancillary</EM>
+<em>MCD43B2: Albedo Quality Ancillary Sun Zenith Angle at Local Solar Noon Data 1Km bits[8-14]</em>
+<em>SDS: BRDF_Albedo_Ancillary</em>
 </pre>
 <ul>
    Returns integer value [0-90], 127 is Fill Value
@@ -375,8 +375,8 @@
 
 
 <pre>
-<EM>MCD43B2: Band-wise Albedo Quality Data 1Km</EM>
-<EM>SDS: BRDF_Albedo_Band_Quality</EM>
+<em>MCD43B2: Band-wise Albedo Quality Data 1Km</em>
+<em>SDS: BRDF_Albedo_Band_Quality</em>
 </pre>
 bits[0-3][4-7][8-11][12-15][16-19][20-23][24-27]<br>
 <ul>
@@ -390,30 +390,30 @@
 </ul>
 
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 In MOD09A1: It seems that cloud related info is not filled properly in the standard QC (MOD09A1 in this module) since version 3, State-QA 500m images (MOD09A1s in this module) should be used (see Vermote et al., 2008).<br>
 
-<H2>TODO</H2>
+<h2>TODO</h2>
 Add one Day products.<br>
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 <br>
-<A HREF="https://lpdaac.usgs.gov/lpdaac/products/modis_products_table">MODIS Products</A><br>
+<a href="https://lpdaac.usgs.gov/lpdaac/products/modis_products_table">MODIS Products</A><br>
 <br>
 Vermote E.F., Kotchenova S.Y., Ray J.P.<br>
 MODIS Surface Reflectance User's Guide.<br>
 Version 1.2. June 2008.<br>
 MODIS Land Surface Reflectance Science Computing Facility.<br>
-<A HREF="http://modis-sr.ltdri.org">Homepage</A><br>
+<a href="http://modis-sr.ltdri.org">Homepage</A><br>
 
 
-<EM>
-<A HREF="i.vi.html">i.vi</A><br>
-</EM>
+<em>
+<a href="i.vi.html">i.vi</A><br>
+</em>
 
 
-<H2>AUTHORS</H2>
-Yann Chemin<BR>
+<h2>AUTHORS</h2>
+Yann Chemin<br>
 
 
 <p>

Modified: grass/trunk/imagery/i.pca/i.pca.html
===================================================================
--- grass/trunk/imagery/i.pca/i.pca.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/imagery/i.pca/i.pca.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -1,7 +1,7 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
 
-<EM>i.pca</EM> is an image processing program based on the
+<em>i.pca</em> is an image processing program based on the
 algorithm provided by Vali (1990), that processes n
 (n&nbsp;&gt;=&nbsp;2) input raster map layers and produces n output
 raster map layers containing the principal components of
@@ -13,20 +13,20 @@
 option is used, the output files are rescaled to fit the
 min,max range.
 
-<H2>OPTIONS</H2>
+<h2>OPTIONS</h2>
 
 <H3>Parameters:</H3>
 <DL>
-<DT><B>input=</B><EM>name,name</EM>[<EM>,name,name</EM>,...] 
+<DT><B>input=</B><em>name,name</em>[<em>,name,name</em>,...] 
 <DD>Name of two or more input raster map layers.
 
-<DT><B>output=</B><EM>name</EM> 
+<DT><B>output=</B><em>name</em> 
 <DD>The output raster map layer name to which suffixes are
 added.  Each output raster map layer is assigned this
-user-specified <EM>name</EM> with a numerical (.1, .2, ...
+user-specified <em>name</em> with a numerical (.1, .2, ...
 .n) suffix.
 
-<DT><B>rescale=</B><EM>min,max</EM> 
+<DT><B>rescale=</B><em>min,max</em> 
 <DD>The optional output category range. (Default: 0,255) If
 rescale=0,0,  no rescaling is performed on output files.
 
@@ -35,17 +35,17 @@
 </DL>
 
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 
 Richards (1986) gives a good example of the application of principal
 components analysis (pca) to a time series of LANDSAT images of a burned
 region in Australia.
-<P>
+<p>
 Eigenvalue and eigenvector information is stored in the output maps'
 history files. View with <em>r.info</em>.
 
 
-<H2>EXAMPLE</H2>
+<h2>EXAMPLE</h2>
 
 Using the Spearfish Imagery sample dataset
 
@@ -60,33 +60,33 @@
 </pre></div>
 
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
 Richards, John A.,
 <B>Remote Sensing Digital Image Analysis</B>,
 Springer-Verlag, 1986.
 
-<P>
+<p>
 
 Vali, Ali R.,
 Personal communication,
 Space Research Center, 
 University of Texas, Austin, 1990.
 
-<P>
+<p>
 
-<EM>
-<A HREF="i.cca.html">i.cca</A><br>
-<A HREF="i.class.html">i.class</A><br>
-<A HREF="i.fft.html">i.fft</A><br>
-<A HREF="i.ifft.html">i.ifft</A><br>
-<A HREF="m.eigensystem.html">m.eigensystem</A><br>
-<A HREF="r.covar.html">r.covar</A><br>
-<A HREF="r.mapcalc.html">r.mapcalc</A>
-</EM>
+<em>
+<a href="i.cca.html">i.cca</A><br>
+<a href="i.class.html">i.class</A><br>
+<a href="i.fft.html">i.fft</A><br>
+<a href="i.ifft.html">i.ifft</A><br>
+<a href="m.eigensystem.html">m.eigensystem</A><br>
+<a href="r.covar.html">r.covar</A><br>
+<a href="r.mapcalc.html">r.mapcalc</A>
+</em>
 
 
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
 
 David Satnik, GIS Laboratory
 <p>

Modified: grass/trunk/imagery/i.points/i.points.html
===================================================================
--- grass/trunk/imagery/i.points/i.points.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/imagery/i.points/i.points.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -1,18 +1,18 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
-<EM>i.points</EM> is an
-<A HREF="imagery.html">imagery</A> function that enables
+<em>i.points</em> is an
+<a href="imagery.html">imagery</A> function that enables
 the user to mark points on a (raster) image to be rectified
 and then input the geographic coordinates of each point for
 calculation of a coordinate transformation matrix.
-<EM>i.points</EM> must be followed by use of the GRASS
-program <EM><A HREF="i.rectify.html">i.rectify</A></EM>, which
+<em>i.points</em> must be followed by use of the GRASS
+program <em><a href="i.rectify.html">i.rectify</A></em>, which
 rectifies the image using the transformation matrix
-coefficients calculated by <EM>i.points</EM>.
+coefficients calculated by <em>i.points</em>.
 
-<P>
+<p>
 
-<EM>Rectification</EM> is the mapping (transformation) of
+<em>Rectification</em> is the mapping (transformation) of
 an image from one coordinate system to another.  The
 geometry of an image extracted into a GRASS LOCATION having
 an x,y coordinate system is not planimetric.  To create a
@@ -21,47 +21,47 @@
 UTM coordinate system or the State Plane coordinate
 system), points from a map having the standard coordinates
 must be associated with the same points on the image to be
-rectified.  <EM>i.points</EM> enables the user to mark
+rectified.  <em>i.points</em> enables the user to mark
 points on an image and input the standard coordinates for
-that point.  <EM>i.points</EM> then calculates a least
+that point.  <em>i.points</em> then calculates a least
 squares regression using the two coordinate systems (x,y
 and standard) for the marked points.  A matrix containing
 transformation coefficients is the output file for
-<EM>i.points</EM>.
+<em>i.points</em>.
 
-<P>
+<p>
 During the process of marking points and entering map
 coordinates, the user can compute the RMS (root mean
-square) error for each point entered.  <EM>i.points</EM>
+square) error for each point entered.  <em>i.points</em>
 does this by calculating the transformation equation (the
-same one that is calculated in the GRASS program <EM>
-<A HREF="i.rectify.html">i.rectify</A></EM>), and then
+same one that is calculated in the GRASS program <em>
+<a href="i.rectify.html">i.rectify</A></em>), and then
 plugging these results into an equation for RMS error.
 
-<P>
-<EM>i.points</EM> offers a zoom option to locate precisely
+<p>
+<em>i.points</em> offers a zoom option to locate precisely
 the point to be marked on an image.  This program also
 offers the user the option of acquiring standard
 coordinates for a marked point from a map layer in the
 target data base.
 
-<P>
-<EM><A HREF="i.target.html">i.target</A></EM> must be
-run before running <EM>i.points</EM> to enable the PLOT
+<p>
+<em><a href="i.target.html">i.target</A></em> must be
+run before running <em>i.points</em> to enable the PLOT
 RASTER option to be used and to identify a target data base
 LOCATION_NAME and MAPSET for the rectified image.  To run
-<EM>i.points</EM>, a graphics monitor is required.
+<em>i.points</em>, a graphics monitor is required.
 
-<P>
+<p>
 The procedure for marking points, entering coordinates, and
 calculating RMS error is described below.
 
-<P>
+<p>
 The first prompt in the program asks the user for the 
-<A HREF="i.group.html">imagery group</A> to be
+<a href="i.group.html">imagery group</A> to be
 registered.  Note that if 
-<EM><A HREF="i.target.html">i.target</A></EM> is not run
-before <EM>i.points</EM>, the <EM>i.points</EM> program
+<em><a href="i.target.html">i.target</A></em> is not run
+before <em>i.points</em>, the <em>i.points</em> program
 will display the following error message:
 
 <PRE>
@@ -126,22 +126,22 @@
 
 Any single raster map layer in the 
 
-<A HREF="i.group.html">imagery group</A> may be used on
+<a href="i.group.html">imagery group</A> may be used on
 
 which to mark points, and the user can mark points on more
 than one raster map layer in the 
 
-<A HREF="i.group.html">imagery group</A> to accumulate the
+<a href="i.group.html">imagery group</A> to accumulate the
 
 suggested minimum number of 12 points.  Any raster map
-layer in the <A HREF="i.group.html">imagery group</A>
+layer in the <a href="i.group.html">imagery group</A>
 can be rectified (using 
 
-<EM><A HREF="i.rectify.html">i.rectify</A></EM>) based on the
+<em><a href="i.rectify.html">i.rectify</A></em>) based on the
 transformation matrix computed from these points.
 
 
-<P>
+<p>
 
 The imagery file chosen by
 the user is displayed in the upper left quadrant of the
@@ -267,7 +267,7 @@
 left button on the mouse.
 
 
-<P>
+<p>
 
 If the user selects the SCREEN option, then points marked
 on the image will automatically be associated with the
@@ -351,9 +351,9 @@
 displayed in red on the graphics monitor (represented here
 in italics).
 
-<P>
+<p>
 The location of the point marked on the 
-<A HREF="i.group.html">imagery group</A> file is given
+<a href="i.group.html">imagery group</A> file is given
 under the heading "image" and the subheadings "east" and
 "north".  The location of the point in the target data base
 is given under the heading "target" and the subheadings
@@ -365,60 +365,60 @@
 twice.  When a point is excluded, it is not afterwards
 included in the calculation of the RMS error, or included
 in the final transformation matrix.  However, it can be
-retrieved within <EM>i.points</EM> at any time by double
+retrieved within <em>i.points</em> at any time by double
 clicking with the mouse as described above.
 
 <H3>QUIT</H3>
 
-To end the <EM>i.points</EM> program place the mouse cross
+To end the <em>i.points</em> program place the mouse cross
 hairs on the word QUIT;  the marked points (including
 coordinates) will be saved.
 
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 
 A good rule of thumb is to mark at least 12 to 15 points
 which are evenly distributed over the entire 
-<A HREF="i.group.html">imagery group</A> file in order to
+<a href="i.group.html">imagery group</A> file in order to
 obtain an accurate transformation equation for the
 rectification process.  The RMS error may increase with
 more points added, but the transformation equation will be
 more accurate.
 
-<P>
+<p>
 An RMS error of less than or equal to approximately one
 resolution unit (pixel or cell) for the image being
 rectified is generally considered acceptable.
 
-<P>
-In order to use a digitizer with <EM>i.points</EM>, at
+<p>
+In order to use a digitizer with <em>i.points</em>, at
 least one digitizer driver besides "none" (the on-screen
 digitizer) must be available in the digitcap file.
 
-<P>
+<p>
 This program is interactive.
 
 
-<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="g.mapsets.html">g.mapsets</A><br>
-<A HREF="i.group.html">i.group</A><br>
-<A HREF="i.rectify.html">i.rectify</A><br>
-<A HREF="i.target.html">i.target</A><br>
-<A HREF="i.vpoints.html">i.vpoints</A>
-</EM><br>
+<p>
+<em>
+<a href="g.mapsets.html">g.mapsets</A><br>
+<a href="i.group.html">i.group</A><br>
+<a href="i.rectify.html">i.rectify</A><br>
+<a href="i.target.html">i.target</A><br>
+<a href="i.vpoints.html">i.vpoints</A>
+</em><br>
 <em><a href="gm_georect.html">gis.m: GEORECTIFY TOOL</a></em>
 
 
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
 
 Michael Shapiro,
 U.S.Army Construction Engineering Research Laboratory
 <p>
-<i>Last changed: $Date$</i></p>
+<i>Last changed: $Date$</i>

Modified: grass/trunk/imagery/i.rectify/i.rectify.html
===================================================================
--- grass/trunk/imagery/i.rectify/i.rectify.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/imagery/i.rectify/i.rectify.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -1,11 +1,11 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
 
-<EM>i.rectify</EM> uses the control
+<em>i.rectify</em> uses the control
 points identified in 
-<EM><A HREF="i.points.html">i.points</A></EM>
+<em><a href="i.points.html">i.points</A></em>
 or
-<EM><A HREF="i.vpoints.html">i.vpoints</A></EM>
+<em><a href="i.vpoints.html">i.vpoints</A></em>
 
 to calculate a transformation matrix based on a first,
 second, or third order polynomial and then converts x,y
@@ -14,22 +14,22 @@
 transformed coordinate system (i.e., a different coordinate
 system than before it was rectified).
 
-<P>
+<p>
 
-<EM><A HREF="i.points.html">i.points</A></EM>
+<em><a href="i.points.html">i.points</A></em>
 or
-<EM><A HREF="i.vpoints.html">i.vpoints</A></EM>
+<em><a href="i.vpoints.html">i.vpoints</A></em>
 
-must be run before <EM>i.rectify</EM>, and both programs
+must be run before <em>i.rectify</em>, and both programs
 are required to rectify an image. An image must be
 rectified before it can reside in a standard coordinate
 LOCATION, and therefore be analyzed with the other map
 layers in the standard coordinate LOCATION. Upon
-completion of <EM>i.rectify</EM>, the rectified image is
+completion of <em>i.rectify</em>, the rectified image is
 deposited in the target standard coordinate LOCATION. This
 LOCATION is selected using
 
-<EM><A HREF="i.target.html">i.target</A></EM>.
+<em><a href="i.target.html">i.target</A></em>.
 
 <p>More than one raster map may be rectified at a time. Each cell file
 should be given a unique output file name. The rectified image or
@@ -38,14 +38,14 @@
 or removed.
 
 <p>
-If the <b>-c</b> flag is used, <EM>i.rectify</EM> will only rectify that
+If the <b>-c</b> flag is used, <em>i.rectify</em> will only rectify that
 portion of the image or raster map that occurs within the chosen window
 region in the target location, and only that portion of the cell
 file will be relocated in the target database. It is
 important therefore, to check the current mapset window in
 the target LOCATION if the <b>-c</b> flag is used.
 
-<P>
+<p>
 
 If you are rectifying a file with plans to patch it to
 another file using the GRASS program <em>r.patch</em>,
@@ -63,7 +63,7 @@
 window.
 
 <h3>Coordinate transformation</h3>
-<P>
+<p>
 The desired order of transformation (1, 2, or 3) is selected with the
 <b>order</b> option.
 
@@ -87,7 +87,7 @@
 
 <H4>Polynomial Transformation Matrix (2nd, 3d order transformation)</H4>
 
-<EM>i.rectify</EM> uses a first, second, or third order transformation
+<em>i.rectify</em> uses a first, second, or third order transformation
 matrix to calculate the registration coefficients. The number
 of control points required for a selected order of transformation
 (represented by n) is
@@ -139,7 +139,7 @@
 format as the input map. If any of the other interpolations is used, the
 output map is written as floating point.
 
-<P>
+<p>
 <!--
 Note: In interactive mode it is possible to define a new file name
 for the target images. This is (currently) not provided in command line
@@ -156,38 +156,38 @@
 on the hard drive.
 
 
-<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="m.transform.html">m.transform</A>,
-  <A HREF="r.proj.html">r.proj</A>,
-  <A HREF="v.proj.html">v.proj</A>,
-  <A HREF="i.group.html">i.group</A>,
-  <A HREF="i.points.html">i.points</A>,
-  <A HREF="i.vpoints.html">i.vpoints</A>,
-  <A HREF="i.target.html">i.target</A>
+<p>
+<em>
+  <a href="m.transform.html">m.transform</A>,
+  <a href="r.proj.html">r.proj</A>,
+  <a href="v.proj.html">v.proj</A>,
+  <a href="i.group.html">i.group</A>,
+  <a href="i.points.html">i.points</A>,
+  <a href="i.vpoints.html">i.vpoints</A>,
+  <a href="i.target.html">i.target</A>
   <br>
   <a href="wxGUI.GCP_Manager.html">Manage Ground Control Points</a>
 </em>
 
 
-<H2>AUTHORS</H2>
+<h2>AUTHORS</h2>
 
 William R. Enslin, 
 Michigan State University,
 Center for Remote Sensing
 
 <p>
-Modified for GRASS 5.0 by:<BR>
-Luca Palmeri (palmeri at ux1.unipd.it)<BR>
-Bill Hughes<BR>
+Modified for GRASS 5.0 by:<br>
+Luca Palmeri (palmeri at ux1.unipd.it)<br>
+Bill Hughes<br>
 Pierre de Mouveaux (pmx at audiovu.com)
-<BR>
+<br>
 CMD mode by Bob Covill
 
 <p>

Modified: grass/trunk/imagery/i.rgb.his/i.rgb.his.html
===================================================================
--- grass/trunk/imagery/i.rgb.his/i.rgb.his.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/imagery/i.rgb.his/i.rgb.his.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -1,7 +1,7 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
 
-<EM>i.rgb.his</EM> is an image processing program that
+<em>i.rgb.his</em> is an image processing program that
 processes three input raster map layers as red, green, and
 blue components and produces three output raster map layers
 representing the hue, intensity, and saturation of the
@@ -12,15 +12,15 @@
 geographic region definition and mask settings are
 respected.
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
-<EM><A HREF="i.his.rgb.html">i.his.rgb</A></EM>
+<em><a href="i.his.rgb.html">i.his.rgb</A></em>
 
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
 
 David Satnik, GIS Laboratory, 
 Central Washington University, 
-<BR>
+<br>
 with acknowledgements to Ali Vali, Space Research
 Center, for the core routine. 
 

Modified: grass/trunk/imagery/i.smap/i.smap.html
===================================================================
--- grass/trunk/imagery/i.smap/i.smap.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/imagery/i.smap/i.smap.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -1,7 +1,7 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
 
-The <EM>i.smap</EM> program is used to segment
+The <em>i.smap</em> program is used to segment
 multispectral images using a spectral class model known as
 a Gaussian mixture distribution.  Since Gaussian mixture
 distributions include conventional multivariate Gaussian
@@ -9,25 +9,25 @@
 multispectral images based on simple spectral mean and
 covariance parameters.
 
-<P>
+<p>
 
-<EM>i.smap</EM> has two modes of operation.  The first mode
+<em>i.smap</em> has two modes of operation.  The first mode
 is the sequential maximum a posteriori (SMAP) mode
-[<A HREF="#ref1">1</A>,<A HREF="#ref2">2</A>].  The SMAP
+[<a href="#ref1">1</A>,<a href="#ref2">2</A>].  The SMAP
 segmentation algorithm attempts to improve segmentation
 accuracy by segmenting the image into regions rather than
 segmenting each pixel separately 
-(see <A HREF="#notes">NOTES</A>).
+(see <a href="#notes">NOTES</A>).
 
 
-<P>
+<p>
 
 The second mode is the more conventional maximum likelihood (ML)
 classification which classifies each pixel separately,
 but requires somewhat less computation. This mode is selected with
-the <B>-m</B> flag (see <A HREF="#mflag.html">below</A>).
+the <B>-m</B> flag (see <a href="#mflag.html">below</A>).
 
-<H2>OPTIONS</H2>
+<h2>OPTIONS</h2>
 
 <H3>Flags:</H3>
 
@@ -37,7 +37,7 @@
 
 <DD>Use maximum likelihood estimation (instead of smap).
 Normal operation is to use SMAP estimation (see
-<A HREF="#notes">NOTES</A>).
+<a href="#notes">NOTES</A>).
 
 <DT><B>-q</B> 
 
@@ -51,35 +51,35 @@
 <H3>Parameters:</H3>
 
 <DL>
-<DT><B>group=</B><EM>name</EM> 
+<DT><B>group=</B><em>name</em> 
 
-<DD>imagery group<BR>
+<DD>imagery group<br>
 The imagery group that defines the image to be classified.
 
-<DT><B>subgroup=</B><EM>name</EM> 
+<DT><B>subgroup=</B><em>name</em> 
 
-<DD>imagery subgroup<BR>
+<DD>imagery subgroup<br>
 The subgroup within the group specified that specifies the
 subset of the band files that are to be used as image data
 to be classified.
 
-<DT><B>signaturefile=</B><EM>name</EM> 
+<DT><B>signaturefile=</B><em>name</em> 
 
-<DD>imagery signaturefile<BR>
+<DD>imagery signaturefile<br>
 The signature file that contains the spectral signatures (i.e., the
 statistics) for the classes to be identified in the image.
 This signature file is produced by the program
-<EM><A HREF="i.gensigset.html">i.gensigset</A></EM>
-(see <A HREF="#notes">NOTES</A>).
+<em><a href="i.gensigset.html">i.gensigset</A></em>
+(see <a href="#notes">NOTES</A>).
 
-<DT><B>blocksize=</B><EM>value</EM> 
+<DT><B>blocksize=</B><em>value</em> 
 
-<DD>size of submatrix to process at one time<BR>
-default: 128<BR>
+<DD>size of submatrix to process at one time<br>
+default: 128<br>
 This option specifies the size of the "window" to be used when
 reading the image data. 
 
-<P>
+<p>
 
 This program was written to be nice about memory usage
 without influencing the resultant classification. This
@@ -88,7 +88,7 @@
 on how much real memory your machine has and how much
 virtual memory the program uses.
 
-<P>
+<p>
 
 The size of the submatrix used in segmenting the image has
 a principle function of controlling memory usage; however,
@@ -102,14 +102,14 @@
 parameters may be used for each distinctive region of the
 image.
 
-<P>
+<p>
 
 The submatrix size has no effect on the performance of the
 ML segmentation method.
 
-<DT><B>output=</B><EM>name</EM>
+<DT><B>output=</B><em>name</em>
 
-<DD>output raster map.<BR>
+<DD>output raster map.<br>
 The name of a raster map that will contain the
 classification results.  This new raster map layer will
 contain categories that can be related to landcover
@@ -117,13 +117,13 @@
 
 </DL>
 
-<H2>INTERACTIVE MODE</H2>
+<h2>INTERACTIVE MODE</h2>
 
 If none of the arguments are specified on the command line,
-<EM>i.smap</EM> will interactively prompt for the names of
+<em>i.smap</em> will interactively prompt for the names of
 the maps and files.
 
-<A NAME="notes"></A><H2>NOTES</H2>
+<A NAME="notes"></A><h2>NOTES</h2>
 
 The SMAP algorithm exploits the fact that nearby pixels in
 an image are likely to have the same class.  It works by
@@ -134,7 +134,7 @@
 segmentations with larger connected regions of a fixed
 class which may be useful in some applications.
 
-<P>
+<p>
 
 The amount of smoothing that is performed in the
 segmentation is dependent of the behavior of the data in
@@ -143,7 +143,7 @@
 reduce the amount of smoothing.  This ensures that
 excessively large regions are not formed.
 
-<P>
+<p>
 
 The module i.smap does not support MASKed or NULL cells. Therefore 
 it might be necessary to create a copy of the classification results 
@@ -151,7 +151,7 @@
 <p>
 r.mapcalc  MASKed_map=classification results 
 
-<H2>REFERENCES</H2>
+<h2>REFERENCES</h2>
 
 <ul>
 <li>C. Bouman and M. Shapiro,
@@ -169,27 +169,27 @@
 <em>IEEE Trans. on Geoscience and Remote Sensing, 33(6): 1313-1316.</em>
 </ul>
 
-<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="r.mapcalc.html">r.mapcalc</A></EM>
+<em><a href="r.mapcalc.html">r.mapcalc</A></em>
 to copy classification result in order to cut out MASKed subareas
 
-<P>
+<p>
 
-<EM><A HREF="i.gensigset.html">i.gensigset</A></EM>
+<em><a href="i.gensigset.html">i.gensigset</A></em>
 to generate the signature file required by this program
 
-<H2>AUTHORS</H2>
+<h2>AUTHORS</h2>
 
 <a href="http://dynamo.ecn.purdue.edu/~bouman/software/segmentation/">Charles Bouman, 
 School of Electrical Engineering, Purdue University</a>
 
-<BR>
+<br>
 Michael Shapiro,
 U.S.Army Construction Engineering 
 Research Laboratory

Modified: grass/trunk/imagery/i.sunhours/i.sunhours.html
===================================================================
--- grass/trunk/imagery/i.sunhours/i.sunhours.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/imagery/i.sunhours/i.sunhours.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -1,41 +1,41 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
-<EM>i.sunhours</EM> creates a sunshine hours map from any map, it
+<em>i.sunhours</em> creates a sunshine hours map from any map, it
 considers a perfect clear day. This method follows Iqbal (1983)
 as found in the AHAS manual (Parodi, 2000).
 
 <!--
-<P>
+<p>
 The day of year (1-365) raster map can be created with ...?
   why isn't this just a single integer value?
 -->
 
-<P>
+<p>
 The latitude input map can be created with the <em>i.latlong</em>
 module, or with <em>r.mapcalc</em>'s <tt>y()</tt> function in a
 latitude-longitude location (possibly reprojected with <em>r.proj</em>.
 
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 
 Iqbal, M., 1983. An Introduction to Solar Radiation. Iqbal, M.,
  Editorial: Academic Press. Toronto, Canada.
 Parodi, G., 2000. AVHRR Hydrological Analysis System. Algorithms
  and Theory, Version 1.0. WRES - ITC, The Netherlands.
-<H2>TODO</H2>
+<h2>TODO</h2>
 
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
 <em>
-<A HREF="i.evapo.TSA.html">i.evapo.TSA</A><br>
-<A HREF="i.latitude.html">i.latitude</A><br>
+<a href="i.evapo.TSA.html">i.evapo.TSA</A><br>
+<a href="i.latitude.html">i.latitude</A><br>
 </em>
 
 
-<H2>AUTHORS</H2>
+<h2>AUTHORS</h2>
 
-Yann Chemin, GRASS Development Team<BR>
+Yann Chemin, GRASS Development Team<br>
 
 
 <p>

Modified: grass/trunk/imagery/i.target/i.target.html
===================================================================
--- grass/trunk/imagery/i.target/i.target.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/imagery/i.target/i.target.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -1,48 +1,48 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
-<EM>i.target</EM> targets an <A HREF="i.group.html">imagery
+<em>i.target</em> targets an <a href="i.group.html">imagery
 group</a> to a GRASS data base location name and mapset.
 
 A location name and mapset are required for the
-<EM><A HREF="i.rectify.html">i.rectify</A></EM> imagery module, into which
+<em><a href="i.rectify.html">i.rectify</A></em> imagery module, into which
 to write the rectified map just prior to completion of the program;
-<EM>i.target</EM> enables the user to specify this location.
+<em>i.target</em> enables the user to specify this location.
 
-<EM>i.target</EM> must be run before 
-<EM><A HREF="i.points.html">i.points</A></EM> and 
-<EM><A HREF="i.rectify.html">i.rectify</A></EM>.
+<em>i.target</em> must be run before 
+<em><a href="i.points.html">i.points</A></em> and 
+<em><a href="i.rectify.html">i.rectify</A></em>.
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 
-<P>
+<p>
 The module's first option asks for the name of the
-<A HREF="i.group.html">imagery group</A> that needs a target.
+<a href="i.group.html">imagery group</A> that needs a target.
 The imagery group must be present in the user's current mapset.
 
-An <A HREF="i.group.html">imagery group</A> may be targeted to any GRASS
+An <a href="i.group.html">imagery group</A> may be targeted to any GRASS
 location.
-<P>
+<p>
 If a group name is given without setting options, the currently targeted
 group will be displayed.
 
 
-<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.group.html">i.group</A><BR>
-<A HREF="i.points.html">i.points</A><BR>
-<A HREF="i.vpoints.html">i.vpoints</A><BR>
-<A HREF="i.rectify.html">i.rectify</A>
-</EM><br>
+<p>
+<em>
+<a href="i.group.html">i.group</A><br>
+<a href="i.points.html">i.points</A><br>
+<a href="i.vpoints.html">i.vpoints</A><br>
+<a href="i.rectify.html">i.rectify</A>
+</em><br>
 <em><a href="gm_georect.html">gis.m: GEORECTIFY TOOL</a></em>
 
 
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
 
 Michael Shapiro,
 U.S. Army Construction Engineering Research Laboratory<p>

Modified: grass/trunk/imagery/i.vi/i.vi.html
===================================================================
--- grass/trunk/imagery/i.vi/i.vi.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/imagery/i.vi/i.vi.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -1,6 +1,6 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
-<EM>i.vi</EM> calculates vegetation indices based on biophysical
+<em>i.vi</em> calculates vegetation indices based on biophysical
 parameters.
 
 <ul>
@@ -146,7 +146,7 @@
 wdvi( redchan, nirchan, soil_line_weight )
 </pre>
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 
 <pre>
 Originally from kepler.gps.caltech.edu
@@ -162,14 +162,14 @@
 	     Pasadena, CA  91125
 </pre>
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
 <em>
   <a href="i.albedo.html">i.albedo</a>
 </em>
 
 
-<H2>AUTHORS</H2>
+<h2>AUTHORS</h2>
 Baburao Kamble, Asian Institute of Technology, Thailand<br>
 Yann Chemin, Asian Institute of Technology, Thailand<br>
 

Modified: grass/trunk/imagery/i.vpoints/i.vpoints.html
===================================================================
--- grass/trunk/imagery/i.vpoints/i.vpoints.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/imagery/i.vpoints/i.vpoints.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -1,41 +1,41 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
 This program enables the user to identify coordinate pairs of points from a
 vector map or keyboard entry and corresponding points in an image to be
 rectified. The map coordinate values of each point are used to calculate a
 transformation matrix.  The operator may then use the 
-<EM><a href="i.rectify.html">i.rectify</A></EM> program to rectify the image using
+<em><a href="i.rectify.html">i.rectify</A></em> program to rectify the image using
 the transformation matrix coefficients calculated from the control point
-file created in <EM>i.vpoints</EM>.  The
-<EM> <a href="i.rectify.html">i.rectify</A></EM> program performs a first, second or
+file created in <em>i.vpoints</em>.  The
+<em> <a href="i.rectify.html">i.rectify</A></em> program performs a first, second or
 third order transformation of the image.
 
-<P>
+<p>
 The first step is to display the unrectified image and
 corresponding vector map data.  The operator would then
 mark corresponding control point locations on the image and
 map. To identify the precise location of a point to be
-marked, <EM>i.vpoints</EM> has a zoom option.  In addition to
+marked, <em>i.vpoints</em> has a zoom option.  In addition to
 marking control points on an image to be rectified and
 inputting their world coordinate values using the
-keyboard,  <EM>i.vpoints</EM> has the option to simultaneously
+keyboard,  <em>i.vpoints</em> has the option to simultaneously
 display vector map data available in the targeted database,
 and identify on the vector map the location of the
 corresponding marked points.  When this option is chosen,
 the coordinate values are input automatically.  Any GRASS
 map layer or vector map in the targeted database LOCATION
-can be displayed using <EM>i.vpoints</EM>.  The <EM>i.vpoints</EM> program
+can be displayed using <em>i.vpoints</em>.  The <em>i.vpoints</em> program
 also has the capability of overlaying (i.e., warping) the
 vector data onto the raster image to visually check the
 accuracy of the registration based on the current set of
 active control points.  During the process of marking
 points and entering map coordinates, the user can compute
 the RMS (root mean square) error for each point entered.
-The <EM>i.vpoints</EM>  program does this by calculating a
+The <em>i.vpoints</em>  program does this by calculating a
 transformation equation (the same one that is calculated in
 the GRASS program
 
-<A HREF="i.rectify.html">i.rectify</A>
+<a href="i.rectify.html">i.rectify</A>
 2).  Coefficients are
 computed for the equation.  The coefficients are then used in the
 equation along with the x,y coordinates of the marked points.  The
@@ -43,16 +43,16 @@
 interpretation of RMS error is described in the ANALYZE subsection.
 
 
-<P>
+<p>
 The procedures for marking control points (registration
 points), displaying vector map layers,  overlaying vector maps onto
 the raster image, and calculating RMS error are described in the
 following sections .
 
 
-<P>
-To enter the program (the <EM>i.vpoints</EM> program requires the use of a
-graphics monitor) type <EM>i.vpoints</EM>:
+<p>
+To enter the program (the <em>i.vpoints</em> program requires the use of a
+graphics monitor) type <em>i.vpoints</em>:
 
 
 <DL>
@@ -115,38 +115,38 @@
 And the color graphics monitor displays the following
 screen:
 
-<P>
+<p>
      Any single file in the imagery group may be used to mark
 points, and points can be marked on more than one file in the
 imagery group to accumulate the suggested minimum number of points
 (3 for a 1st order transformation, 6 for a 2nd order, and 10 for a
 3rd order).  Any file in the imagery group can be subsequently
-rectified (using <EM><A HREF="i.rectify.html">i.rectify</A></EM>)
+rectified (using <em><a href="i.rectify.html">i.rectify</A></em>)
 based on the transformation matrix computed from these points.
 
-<P>
+<p>
      The chosen file is displayed in the upper left quadrant of the
 monitor at a default magnification based on the extent of the
 current active window.
 
-<P>
+<p>
 
 <B>RASTER IMAGE</B>
 
-<P>
+<p>
      The raster image option on the menu at the bottom of the
 window allows the user to display any single file in the imagery
 group in the upper right quadrant of the window screen.  The option
 provides the same file selection pick list as is presented when you
-first enter the <EM>i.vpoints</EM> program.  When you select this option,
+first enter the <em>i.vpoints</em> program.  When you select this option,
 the program will erase the data contained in all of the four
 quadrant windows and will reinitialize all program values.
 
 
-<P>
+<p>
 
 <B>VECTOR MAPS</B>
-<P>
+<p>
      The vector maps option on the menu at the bottom of the screen
 allows the user to display vector map data in the upper right
 quadrant of the screen.  After selecting the vector map layer to
@@ -154,9 +154,9 @@
 screen. This pick list is used to select the line color (blue,
 gray, green, red, white, or yellow) for the selected vector data
 layer.
-<P>
+<p>
 <B>Refresh</B>
-<P>
+<p>
      The refresh option on the main menu allows the user to
 "refresh" or re-draw the displayed vector data. This function will
 erase all outlines showing the limits of previously zoomed areas. 
@@ -164,9 +164,9 @@
 <PRE>
      Refresh Map ?       NO   YES
 </PRE>
-<P>
+<p>
 <B>Zoom</B>
-<P>
+<p>
      To enlarge a raster or vector image, place the mouse cross
 hairs on the word zoom on the main menu and press the left button. 
 The following menu will be displayed at the bottom. of the screen:
@@ -190,23 +190,23 @@
 enlarged, press the right button  to accept it.
 
 
-<P>
+<p>
 
 The point method for enlarging an image will display a mouse menu
 to guide you in selecting the appropriate enlargement.  To enlarge
 or reduce the magnification factor, place the cursor on the "+" or
 "-" box and press the left button on the mouse.
-<P>
-<P>
+<p>
+<p>
 You may zoom either the raster or the vector display.
-<P>
+<p>
 Upon accepting the new region limits, the raster or vector data are
 redisplayed in either the lower left (raster) or lower right
 (vector) windows.
-<P>
+<p>
 The extent of the zoomed area is outlined on the unzoomed image in
 the main window area.
-<P>
+<p>
      While the main menu is displayed,  you can mark
 corrosponding control points on the raster and vector
 images or enter map coordinates from the keyboard.  If you
@@ -218,7 +218,7 @@
 determined the standard coordinates (for example, UTM's) of
 each circled point, you are ready to mark the points on the
 displayed image.
-<P>
+<p>
      To mark the points on the image, that correspond to the points
 on the standard coordinate map, place the mouse cross hairs on the
 point on the image to be marked (you will probably have to ZOOM to
@@ -233,7 +233,7 @@
           Enter coordinates as east north:
 </PRE>
 <B>Analyze</B>
-<P>
+<p>
 
      After a number of points have been marked (a minimum of 4 for
 a 1st order transformation, 7 for a 2nd order, and 11 for a 3rd
@@ -278,9 +278,9 @@
 twice.  When a point is excluded, it is not included in the
 calculation of the RMS error, or included in the final
 transformation matrix.  However, it can be retrieved within
-<EM>i.vpoints</EM> at any time by double clicking with the mouse as
+<em>i.vpoints</em> at any time by double clicking with the mouse as
 described above.
-<P>
+<p>
 The following menu appears at the bottom of the monitor:
 <PRE>
    DONE   PRINT   FILE   OVERLAY   DELETE ON       Transformation -
@@ -290,9 +290,9 @@
 toggle option is used to allow the user to physically remove a
 control point from the POINTS file instead of just flagging it as
 an non-active reference point.
-<P>
+<p>
 <B>Overlay</B>
-<P>
+<p>
 Overlay allows the user to overlay the vector map(s) onto the
 raster image.  Overlay can be used to warp (register) and display
 the selected vector map data on top of the raster image contained
@@ -309,34 +309,34 @@
 </PRE>
 The program will immediately recalculate the RMSE and the number of
 points required.
-<P>
+<p>
 <B>Quit</B>
-<P>
-     To exit the <EM>i.vpoints</EM> program, place the mouse cross hairs on
+<p>
+     To exit the <em>i.vpoints</em> program, place the mouse cross hairs on
 the word QUIT at the bottom of the monitor and all of the marked
 points (including coordinates) will be saved.
 
-<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="g.mapsets.html">g.mapsets</A><BR>
-<A HREF="i.group.html">i.group</A><BR>
-<A HREF="i.points.html">i.points</A><BR>
-<A HREF="i.rectify.html">i.rectify</A><BR>
-<A HREF="i.target.html">i.target</A>
-</EM><br>
+<p>
+<em>
+<a href="g.mapsets.html">g.mapsets</A><br>
+<a href="i.group.html">i.group</A><br>
+<a href="i.points.html">i.points</A><br>
+<a href="i.rectify.html">i.rectify</A><br>
+<a href="i.target.html">i.target</A>
+</em><br>
 <em><a href="gm_georect.html">gis.m: GEORECTIFY TOOL</a></em>
 
 
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
 
 William R. Enslin, Michigan State University Center for Remote Sensing<br>
-Radim Blazek (update to GRASS 5.7)<BR>
+Radim Blazek (update to GRASS 5.7)<br>
 Hamish Bowman (finish GRASS 6 porting)
 <p>
-<i>Last changed: $Date$</i></p>
+<i>Last changed: $Date$</i>

Modified: grass/trunk/imagery/i.zc/i.zc.html
===================================================================
--- grass/trunk/imagery/i.zc/i.zc.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/imagery/i.zc/i.zc.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -1,7 +1,7 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
 
-<EM>i.zc</EM> is an image processing program used for edge
+<em>i.zc</em> is an image processing program used for edge
 detection.  The raster map produced shows the location of
 "boundaries" on the input map.  Boundaries tend to be found
 in regions of changing cell values and tend to run
@@ -9,21 +9,21 @@
 used for edge detection is one of the "zero-crossing"
 algorithms and is discussed briefly below.
 
-<H2>OPTIONS</H2>
+<h2>OPTIONS</h2>
 
 <H3>Parameters:</H3>
 
 <DL>
 
-<DT><B>input_map=</B><EM>name</EM> 
+<DT><B>input_map=</B><em>name</em> 
 
 <DD>Name of input raster map layer.
 
-<DT><B>zc_map=</B><EM>name</EM> 
+<DT><B>zc_map=</B><em>name</em> 
 
 <DD>Name of raster map layer to be used for zero-crossing values.
 
-<DT><B>width=</B><EM>value</EM> 
+<DT><B>width=</B><em>value</em> 
 
 <DD>This parameter determines the x-y extent of the
 Gaussian filter.  The default value is 9;  higher and lower
@@ -31,34 +31,34 @@
 will result in finding "edges" representing more gradual
 changes in cell values.
 
-<BR>
+<br>
 
 Default:  9
 
-<DT><B>threshold=</B><EM>value</EM> 
+<DT><B>threshold=</B><em>value</em> 
 
 <DD>This parameter determines the "sensitivity" of the
 Gaussian filter.  The default value is 10;  higher and
 lower values can be tested by the user.  Increasing the
 threshold value will result in fewer edges being found.
 
-<BR>
+<br>
 
 Default:  10
 
-<DT><B>orientations=</B><EM>value</EM> 
+<DT><B>orientations=</B><em>value</em> 
 
 <DD>This value is the number of azimuth directions the
 cells on the output raster map layer are categorized into
 (similar to the aspect raster map layer produced by the
 
-<EM><A HREF="r.slope.aspect.html">r.slope.aspect</A></EM>
+<em><a href="r.slope.aspect.html">r.slope.aspect</A></em>
 
 program).  For example, a value of 16 would result in
 detected edges being categorized into one of 16 bins
 depending on the direction of the edge at that point.
 
-<BR>
+<br>
 
 Default:  1
 
@@ -67,7 +67,7 @@
 The current region definition and mask settings are respected
 when reading the input map.
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 
 The procedure to find the "edges" in the image is as follows:
 
@@ -84,15 +84,15 @@
 The resulting raster map layer is output.
 </OL>
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
-<EM><A HREF="i.fft.html">i.fft</A></EM>,
-<EM><A HREF="i.ifft.html">i.ifft</A></EM>,
-<EM><A HREF="r.mapcalc.html">r.mapcalc</A></EM>,
-<EM><A HREF="r.mfilter.html">r.mfilter</A></EM>,
-<EM><A HREF="r.slope.aspect.html">r.slope.aspect</A></EM>
+<em><a href="i.fft.html">i.fft</A></em>,
+<em><a href="i.ifft.html">i.ifft</A></em>,
+<em><a href="r.mapcalc.html">r.mapcalc</A></em>,
+<em><a href="r.mfilter.html">r.mfilter</A></em>,
+<em><a href="r.slope.aspect.html">r.slope.aspect</A></em>
 
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
 
 David Satnik, GIS Laboratory, 
 Central Washington University

Modified: grass/trunk/imagery/imageryintro.html
===================================================================
--- grass/trunk/imagery/imageryintro.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/imagery/imageryintro.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -31,7 +31,7 @@
 modules are available. Always the full map is imported. Imagery data
 can be group (e.g. channel-wise) with <a href="i.group.html">i.group</a>.
 
-<P>
+<p>
 For importing scanned maps, the user will need to create a
 x,y-location, scan the map in the desired resolution and save it into
 an appropriate raster format (e.g. tiff, jpeg, png, pbm) and then use
@@ -120,7 +120,7 @@
    using the Maximum Likelihood classification method</li>
   </ul>
 <li> Combined radiometric/geometric (segmentation based) supervised
-   classification (<A HREF="i.gensigset.html">i.gensigset</A>,
+   classification (<a href="i.gensigset.html">i.gensigset</A>,
    <a href="i.smap.html">i.smap</a>)
 
 </ul>

Modified: grass/trunk/lib/db/sqlp/sql.html
===================================================================
--- grass/trunk/lib/db/sqlp/sql.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/lib/db/sqlp/sql.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -13,7 +13,7 @@
 <img src="grass_logo.png" alt="GRASS logo"><hr align=center size=6 noshade>
 
 <!-- meta page description: SQL support introduction -->
-<H2>SQL support in GRASS GIS</H2>
+<h2>SQL support in GRASS GIS</h2>
 
 GRASS can use various RDBMS and embedded databases. 
 SQL queries are directly passed to the underlying 
@@ -21,7 +21,7 @@
 The set of supported SQL commands depends on the RDMBS 
 and driver selected.  
 
-<H2>Drivers</H2>  
+<h2>Drivers</h2>  
 The list of available drivers can vary in various binary 
 distributions of GRASS. 
 <p>
@@ -48,7 +48,7 @@
 </table>
 
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 
 <ul>
 <li> SQL does not support '.' (dots) in table names.
@@ -156,15 +156,15 @@
 
 <h2>SEE ALSO</h2>
 
-<a href="databaseintro.html">Database management in GRASS GIS</a>,<BR>
-<a href="database.html">Help pages for database modules</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="http://www.redhat.com/docs/manuals/database/RHDB-2.1-Manual/sql/sqlreference.html">
 SQL Guide and Reference</a> (Red Hat)
 
 
-<p><i>Last changed: $Date$</i></p>
+<p><i>Last changed: $Date$</i>
 <HR>
-<BR><a href=index.html>Help Index</a>
-<P>&copy; 2008 <a href="http://grass.osgeo.org">GRASS Development Team</a></P>
+<br><a href=index.html>Help Index</a>
+<p>&copy; 2008 <a href="http://grass.osgeo.org">GRASS Development Team</a>
 </body>
 </html>

Modified: grass/trunk/lib/init/grass7.html
===================================================================
--- grass/trunk/lib/init/grass7.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/lib/init/grass7.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -10,22 +10,22 @@
 
 <img src="grass_logo.png" alt="GRASS logo"><hr align=center size=6 noshade>
 
-<H2>NAME</H2>
+<h2>NAME</h2>
 
-<EM><B>grass70</B></EM>  - The GRASS startup program<BR>
+<em><B>grass70</B></em>  - The GRASS startup program<br>
 
-<H2>SYNOPSIS</H2>
+<h2>SYNOPSIS</h2>
 
 <B>grass70</B> [<B>-</B>] [<B>-v</B>] [<B>-h | -help | --help</B>]
     [<B>-text | -gui | -wxpython | -wx]</B>]
     [[[<B>&lt;GISDBASE&gt;/</B>]<B>&lt;LOCATION_NAME&gt;/</B>]
     	<B>&lt;MAPSET&gt;</B>]
 
-<BR>
+<br>
 
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
-<P>
+<p>
 This command is used to launch GRASS GIS. It will parse the command line
 arguments and then initialize GRASS for the user. Since GRASS programs
 require a specific environment, this program must be called before any other
@@ -34,24 +34,24 @@
 desired mapset to work on.
 
 
-<H2>FEATURES</H2>
+<h2>FEATURES</h2>
 
-<P>
+<p>
 The <em>grass70</em> startup program will remember both the desired user
 interface and mapset. Thus, the next time the user runs GRASS, typing
-<EM>grass70</EM> (without any options) will start GRASS with the previous
+<em>grass70</em> (without any options) will start GRASS with the previous
 settings for the user interface and mapset selected.
 
-<P>
-If you specify a graphical user interface (wxPython) the <EM>grass70</EM>
+<p>
+If you specify a graphical user interface (wxPython) the <em>grass70</em>
 program will try to verify that the system you specified exists and that you
-can access it successfully. If any of these checks fail then <EM>grass70</EM>
+can access it successfully. If any of these checks fail then <em>grass70</em>
 will automatically switch back to the text user interface mode.
 
 
-<H2>OPTIONS</H2>
+<h2>OPTIONS</h2>
 
-<P>
+<p>
 All command line options are optional.
 
 <H3>Flags:</H3>
@@ -89,24 +89,24 @@
 <DD> Initial mapset directory which is a subdirectory of LOCATION_NAME
 </DL>
 
-<BR>
+<br>
 <B><i>Note</i></B>- These parameters must be specified in one of the
 following ways:
 <DL><DD>
-    MAPSET<BR>
-    LOCATION_NAME/MAPSET<BR>
-    GISDBASE/LOCATION_NAME/MAPSET<BR>
+    MAPSET<br>
+    LOCATION_NAME/MAPSET<br>
+    GISDBASE/LOCATION_NAME/MAPSET<br>
     
 </DL>
 
 
-<H2>ENVIRONMENT VARIABLES</H2>
+<h2>ENVIRONMENT VARIABLES</h2>
 
 A number of environment variables are available at GRASS startup to assist
 with automation and customization. Most users will not need to bother with
 these.
 
-<P>
+<p>
 In addition to these shell environment variables GRASS maintains a number of
 GIS environment variables in the <tt>$HOME/.grass7/rc</tt> file. User changes
 to this file will be read during the next startup of GRASS. If this file
@@ -118,29 +118,29 @@
 
 <H3>User Interface Environment Variable</H3>
 
-<P>
-The <EM>grass70</EM> program will check for the existence of an environment
+<p>
+The <em>grass70</em> program will check for the existence of an environment
 variable called GRASS_GUI which indicates the type of user interface for
-GRASS to use. If this variable is not set when <EM>grass70</EM> is run, then
+GRASS to use. If this variable is not set when <em>grass70</em> is run, then
 it will be created and then saved in the <tt>$HOME/.grass7/rc</tt> file for
 the next time GRASS is run. It can be set to "text" or "wxpython".
 
-<P>
-There is an order of precedence in the way <EM>grass70</EM> determines the user
+<p>
+There is an order of precedence in the way <em>grass70</em> determines the user
 interface to use. The following is the hierarchy from highest precedence to
 lowest.
 
 <DL>
  <DT><B>Interface precedence</B>
- <DD>&bull; Command line argument<BR>
-     &bull; Environment variable GRASS_GUI<BR>
-     &bull; Value set in <tt>$HOME/.grass7/rc</tt><BR>
+ <DD>&bull; Command line argument<br>
+     &bull; Environment variable GRASS_GUI<br>
+     &bull; Value set in <tt>$HOME/.grass7/rc</tt><br>
      &bull; Default value - wxpython
 </DL>
 
 <H3>Python Environment Variables</H3>
 
-<P>
+<p>
 If you choose to use the wxPython interface, then
 the following environment variables can be used to override your
 system default <tt>python</tt> command.
@@ -153,14 +153,14 @@
 
 <H4>Example Use of GRASS Python Environment Variable</H4>
 
-<P>
+<p>
 Suppose your system has Python 2.4 installed and you install a personal
 version of the Python 2.5 binaries under <tt>$HOME/bin</tt>. You can use
 the above variables to have GRASS use the Python 2.5 binaries instead.
 
 
 <H4>Example Use of the GRASS Python Environment Variable</H4>
-<P>
+<p>
 <pre>
    GRASS_PYTHON=python2.5
 </pre>
@@ -172,13 +172,13 @@
 This environment variable allows the user to extend the GRASS program search
 paths to include locally developed/installed addon modules which are not
 distributed with the standard GRASS release.
-<P>
+<p>
 <pre>
    GRASS_ADDON_PATH=/usr/mytools
    GRASS_ADDON_PATH=/usr/mytools:/usr/local/othertools
 </pre>
 
-<P>
+<p>
 In this example above path(s) would be added to the standard GRASS path
 environment.
 
@@ -191,7 +191,7 @@
 
 <H3>Location Environment Variables</H3>
 
-<P>
+<p>
 The Synopsis and Options sections above describe options that can be used to
 set the location and mapset that GRASS will use. These values can also be set
 with environment variables. However, specifying the location and mapset
@@ -230,15 +230,15 @@
 
 <H3>Note</H3>
 
-<P>
+<p>
 Note that you will need to set these variables using the appropriate method
 required for the UNIX shell that you use. (e.g. in a Bash shell you must
 "export" the variables for them to propogate)
 
 
-<H2>EXAMPLES</H2>
+<h2>EXAMPLES</h2>
 
-<P>
+<p>
 The following are some examples of how you could start GRASS
 
 <DL>
@@ -275,85 +275,85 @@
 <DL>
 
 <DT><B>Example 1</B>
-<DD> The environment variables are defined as follows:<BR><BR>
+<DD> The environment variables are defined as follows:<br><br>
     
-    LOCATION = /usr/local/share/grassdata/spearfish60/PERMANENT<BR>
-    GISDBASE = /usr/local/share/grassdata<BR>
-    LOCATION_NAME = spearfish60<BR>
-    MAPSET = PERMANENT<BR><BR>
+    LOCATION = /usr/local/share/grassdata/spearfish60/PERMANENT<br>
+    GISDBASE = /usr/local/share/grassdata<br>
+    LOCATION_NAME = spearfish60<br>
+    MAPSET = PERMANENT<br><br>
     
-    Start GRASS with the following command:<BR><BR>
+    Start GRASS with the following command:<br><br>
     
-    grass70 -<BR><BR>
+    grass70 -<br><br>
     
     GRASS will start with the mapset defined by LOCATION since the LOCATION
-    variable overrides the other variables.<BR><BR>
+    variable overrides the other variables.<br><br>
 
 <DT><B>Example 2</B>
-<DD> The environment variables are defined as follows:<BR><BR>
+<DD> The environment variables are defined as follows:<br><br>
     
-    GISDBASE = /usr/local/share/grassdata<BR>
-    LOCATION_NAME = spearfish60<BR>
-    MAPSET = PERMANENT<BR><BR>
+    GISDBASE = /usr/local/share/grassdata<br>
+    LOCATION_NAME = spearfish60<br>
+    MAPSET = PERMANENT<br><br>
     
-    Start GRASS with the following command:<BR><BR>
+    Start GRASS with the following command:<br><br>
     
-    grass70 -<BR><BR>
+    grass70 -<br><br>
     
     GRASS will start with the mapset defined by
-    GISDBASE/LOCATION_NAME/MAPSET.<BR><BR>
+    GISDBASE/LOCATION_NAME/MAPSET.<br><br>
 
 <DT><B>Example 3</B>
-<DD> The environment variables are defined as follows:<BR><BR>
+<DD> The environment variables are defined as follows:<br><br>
     
-    LOCATION = /usr/local/share/grassdata/spearfish60/PERMANENT<BR>
-    GISDBASE = /usr/local/share/grassdata<BR>
-    LOCATION_NAME = spearfish60<BR>
-    MAPSET = PERMANENT<BR><BR>
+    LOCATION = /usr/local/share/grassdata/spearfish60/PERMANENT<br>
+    GISDBASE = /usr/local/share/grassdata<br>
+    LOCATION_NAME = spearfish60<br>
+    MAPSET = PERMANENT<br><br>
     
-    Start GRASS with the following command:<BR><BR>
+    Start GRASS with the following command:<br><br>
     
-    grass70 /usr/home/grass/data/thailand/forests<BR><BR>
+    grass70 /usr/home/grass/data/thailand/forests<br><br>
     
     GRASS will start with the mapset /home/grass/data/thailand/forests which
-    overrides the environment variables.<BR><BR>
+    overrides the environment variables.<br><br>
 
 <DT><B>Example 4</B>
-<DD> The environment variables are defined as follows:<BR><BR>
+<DD> The environment variables are defined as follows:<br><br>
     
-    LOCATION = /usr/local/share/grassdata/spearfish60/PERMANENT<BR>
-    GISDBASE = /usr/local/share/grassdata<BR>
-    LOCATION_NAME = spearfish60<BR>
-    MAPSET = PERMANENT<BR><BR>
+    LOCATION = /usr/local/share/grassdata/spearfish60/PERMANENT<br>
+    GISDBASE = /usr/local/share/grassdata<br>
+    LOCATION_NAME = spearfish60<br>
+    MAPSET = PERMANENT<br><br>
     
-    Start GRASS with the following command:<BR><BR>
+    Start GRASS with the following command:<br><br>
     
-    grass70 swamps<BR><BR>
+    grass70 swamps<br><br>
     
     GRASS will start with the mapset defined by GISDBASE/LOCATION_NAME/swamps
     since the command line argument for the mapset overrides the environment
-    variable MAPSET.<BR><BR>
+    variable MAPSET.<br><br>
 
 <DT><B>Example 5</B>
-<DD> The environment variables are defined as follows:<BR><BR>
+<DD> The environment variables are defined as follows:<br><br>
     
-    LOCATION = /usr/local/share/grassdata/spearfish60/PERMANENT<BR>
-    GISDBASE = /usr/local/share/grassdata<BR>
-    LOCATION_NAME = spearfish60<BR>
-    MAPSET = PERMANENT<BR><BR>
+    LOCATION = /usr/local/share/grassdata/spearfish60/PERMANENT<br>
+    GISDBASE = /usr/local/share/grassdata<br>
+    LOCATION_NAME = spearfish60<br>
+    MAPSET = PERMANENT<br><br>
     
-    Start GRASS with the following command:<BR><BR>
+    Start GRASS with the following command:<br><br>
     
-    grass70 thailand/forests<BR><BR>
+    grass70 thailand/forests<br><br>
     
     GRASS will start with the mapset defined by GISDBASE/thailand/forests
     since the command line arguments for the location and mapset overrides
-    the environment variables LOCATION_NAME and MAPSET.<BR><BR>
+    the environment variables LOCATION_NAME and MAPSET.<br><br>
 
 </DL>
 
 
-<H2>CAVEAT</H2>
+<h2>CAVEAT</h2>
 
 If you start GRASS using the wxPython interface you must have a <tt>python</tt>
 command in your $PATH variable. That is, the command must be named
@@ -362,23 +362,23 @@
 administrator must create an appropriate link to the actual <tt>python</tt>
 program.
 
-<P>
+<p>
 Furthermore, if you have more than one version of Python installed, make sure
 that the version you want to use with GRASS is the first version found in
 your <tt>$PATH</tt> variable. GRASS searches your <tt>$PATH</tt> variable
 until it finds the first version of <tt>python</tt>.
 
 
-<H2>FILES</H2>
+<h2>FILES</h2>
 
-<EM>$UNIX_BIN/grass70</EM> - GRASS startup program (Linux, MacOSX etc.)<BR>
-<EM>$WINDOWS_BIN/grass70.bat</EM> - GRASS startup program (MS-Windows)<BR>
-<EM>$GISBASE/etc/Init.sh</EM> - GRASS initialization script called by
-    <EM>grass70</EM><BR>
-<EM>$GISBASE/etc/wxpython/gis_set.py</EM> - Python script to set the
-    location and mapset to use. Called by <EM>Init.sh</EM><BR><BR>
+<em>$UNIX_BIN/grass70</em> - GRASS startup program (Linux, MacOSX etc.)<br>
+<em>$WINDOWS_BIN/grass70.bat</em> - GRASS startup program (MS-Windows)<br>
+<em>$GISBASE/etc/Init.sh</em> - GRASS initialization script called by
+    <em>grass70</em><br>
+<em>$GISBASE/etc/wxpython/gis_set.py</em> - Python script to set the
+    location and mapset to use. Called by <em>Init.sh</em><br><br>
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
 List of <a href=variables.html>implemented GRASS environment variables</a>.
 <p>
@@ -386,7 +386,7 @@
 <p>
 <a href="http://download.osgeo.org/grass/grass7_progman/">GRASS 7 Programmer's Manual</a>
 
-<H2>AUTHORS (of this page)</H2>
+<h2>AUTHORS (of this page)</h2>
 
 Justin Hickey<br>
 Markus Neteler<br>
@@ -395,7 +395,7 @@
 <p>
 <i>Last changed: $Date$</i>
 <HR>
-<P>
+<p>
 <a href=index.html>Help Index</a>
 
 </body>

Modified: grass/trunk/lib/init/helptext.html
===================================================================
--- grass/trunk/lib/init/helptext.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/lib/init/helptext.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -76,7 +76,7 @@
 
 <p>
 &nbsp;&nbsp;&nbsp;<IMG SRC="help_loc_struct.png" ALT="[GRASS Location structure]">
-<BR>
+<br>
 <i>Fig. 1: GRASS Location structure</i>
 <p>
 
@@ -131,12 +131,12 @@
     <tt>mkdir /home/yourlogin/grassdata</tt>).</LI>
 </OL>
 
-<P>
+<p>
 Sample data such as the "Spearfish" or the "North Carolina" sample datasets
 may be downloaded from 
-<A HREF="http://grass.osgeo.org/download/data.php">http://grass.osgeo.org/download/data.php</A>
+<a href="http://grass.osgeo.org/download/data.php">http://grass.osgeo.org/download/data.php</A>
 and placed in this new database directory.
-<P>
+<p>
 
 
 <h3>A) Create New Location with wxGUI</h3>
@@ -154,7 +154,7 @@
 continue by pressing "ESC"-"RETURN" - i.e. press (NOT hold) the ESC key,
 and then press the RETURN key on your keyboard.
 
-<P>
+<p>
 Next you will need to assign parameters to the location such
 as the coordinate system and datum you want to use, the project area's
 boundary coordinates, and the default resolution for raster data:
@@ -167,7 +167,7 @@
    project area, for example "Topo Map of the Alps".</LI>
 </UL>
 
-<P>
+<p>
 Next you are requested for some more information about the projection.
 Note that the prompts vary from projection to projection, an example follows:
 
@@ -186,10 +186,10 @@
 <LI> Enter plural form of map units: for example, meters
 </UL>
 
-<P>
+<p>
 The next step is the description of the project area's boundary coordinates
 and the definition of the default raster resolution:
-<P>
+<p>
 The default raster resolution (GRID RESOLUTION) has to be chosen
 according to your needs. Generally, it is advisable to work in steps of
 0.25 (0.25, 0.5, 1.75, 2.00, 12.25 etc.). This resolution does not
@@ -197,31 +197,31 @@
 coordinate values. Note that every raster map may have its own
 resolution. You can leave this screen with "ESC"-"RETURN" and then
 if everything is correct accept the list of parameters that appears.
-<P>
+<p>
 You will then be back to the startup screen to enter the mapset's
 name (if not already entered). Another "ESC"-"RETURN" will finally
 let you leave this screen. This mapset is created within the new
 location by answering "yes" to the next question. The mapset will
 use the parameters of the location (such as the region and resolution
 definitions) as its default parameters.
-<P>
+<p>
 Now the project area, i.e. the location including a mapset, has been
 created. You have "arrived" in the GRASS system and can start working
 within this new location.
 
-<H2>Further Reading</H2>
+<h2>Further Reading</h2>
 
 Please have a look at the GRASS web site for tutorials and books:
-<A HREF="http://grass.osgeo.org/gdp/index.php">http://grass.osgeo.org/gdp/index.php</A>.
+<a href="http://grass.osgeo.org/gdp/index.php">http://grass.osgeo.org/gdp/index.php</A>.
 
-<H2>See also</H2>
+<h2>See also</h2>
 <a href="index.html">GRASS 7 Reference Manual</a>
 <br>
 <a href="grass7.html">Manual page of GRASS 7 launch program</a>
 
 <p><i>Last changed: $Date$</i>
 <HR>
-<P><a href=index.html>Help Index</a>
-<P>&copy; 2005-2010 <a href="http://grass.osgeo.org">GRASS Development Team</a></P>
+<p><a href=index.html>Help Index</a>
+<p>&copy; 2005-2010 <a href="http://grass.osgeo.org">GRASS Development Team</a>
 </BODY>
 </HTML>

Modified: grass/trunk/misc/m.cogo/m.cogo.html
===================================================================
--- grass/trunk/misc/m.cogo/m.cogo.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/misc/m.cogo/m.cogo.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -1,19 +1,19 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
-<EM>m.cogo</EM> converts data points between bearing and distance
+<em>m.cogo</em> converts data points between bearing and distance
 and X,Y coordinates.  Only simple bearing/distance or coordinate
 pairs are handled. It assumes a cartesian coordinate system.
 
-<P>
+<p>
 Input can be entered via standard input (default) or from the file
-<B>input=</B><EM>name</EM>. Specifying the input as "-" also
+<B>input=</B><em>name</em>. Specifying the input as "-" also
 specifies standard input, and is useful for using the program in
 a pipeline.  Output will be to standard output unless a file
 name other than "-" is specified.  The input file must
 closely adhere to the following format, where up to a 10 character
 label is allowed but not required (see <B>-l</B> flag).
 
-<P>
+<p>
 <B>Example COGO input:</B>
 <div class="code"><pre>
    P23 N 23:14:12 W 340
@@ -21,47 +21,47 @@
    ...
 </pre></div>
 
-<P>
+<p>
 The first column may contain a label and you must use the <B>-l</B>
 flag so the program knows.  This is followed by a space, and then
 either the character 'N' or 'S' to indicate whether the bearing is
 relative to the north or south directions.  After another space,
 the angle begins in degrees, minutes, and seconds in
 "DDD:MM:SS.SSSS" format. Generally, the angle can be of the form
-<EM>digits + separator + digits + separator + digits [+ '.' + digits]</EM>.
+<em>digits + separator + digits + separator + digits [+ '.' + digits]</em>.
 A space follows the angle, and is then followed by either the 'E' or 'W'
 characters. A space separates the bearing from the distance (which should
 be in appropriate linear units).
 
-<P>
+<p>
 <B>Output of the above input:</B>
 <div class="code"><pre>
    -134.140211 312.420236 P23
    -116.832837 83.072345 P24
    ...
 </pre></div>
-<P>
+<p>
 Unless specified with the <B>coord</B> option, calculations begin from (0,0).
 
-<P>
+<p>
 For those unfamiliar with the notation for bearings: Picture yourself in the
 center of a circle.  The first hemispere notation tell you whether you should
 face north or south.  Then you read the angle and either turn that many
 degrees to the east or west, depending on the second hemisphere notation.  
 Finally, you move &lt;distance&gt; units in that direction to get to the 
 next station.
-</P>
 
-<EM>m.cogo</EM> can be run either non-interactively or
+
+<em>m.cogo</em> can be run either non-interactively or
 interactively.  The program will be run non-interactively
 if the user specifies any parameter or flag. Use "m.cogo -",
 to run the program in a pipeline.  Without any flags or
-parameters, <EM>m.cogo</EM> will prompt for each value
+parameters, <em>m.cogo</em> will prompt for each value
 using the familiar GRASS parser interface.
 
-<P>
+<p>
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 
 This program is very simplistic, and will not handle deviations
 from the input format explained above.  Currently, the
@@ -71,7 +71,7 @@
 vector and/or sites layers.
 
 
-<H2>EXAMPLE</H2>
+<h2>EXAMPLE</h2>
 
 <div class="code"><pre>
    m.cogo -l in=cogo.dat
@@ -125,19 +125,19 @@
 converted to areas with <em>v.centroids</em>.
 
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
 <em>
-<a HREF="v.centroids.html">v.centroids</a>,
-<a HREF="v.clean.html">v.clean</a>,
+<a href="v.centroids.html">v.centroids</a>,
+<a href="v.clean.html">v.clean</a>,
 <a href="wxGUI.Vector_Digitizing_Tool.html">wxGUI vector digitizer</a>,
-<a HREF="v.in.ascii.html">v.in.ascii</a>,
-<a HREF="v.type.html">v.type</a>
+<a href="v.in.ascii.html">v.in.ascii</a>,
+<a href="v.type.html">v.type</a>
 </em>
 
 
 
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
 
 Eric G. Miller
 

Modified: grass/trunk/misc/m.nviz.script/m.nviz.script.html
===================================================================
--- grass/trunk/misc/m.nviz.script/m.nviz.script.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/misc/m.nviz.script/m.nviz.script.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -1,21 +1,21 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
-The <EM>m.nviz.script</EM> program allows the user to easily create a script
+The <em>m.nviz.script</em> program allows the user to easily create a script
 that can be run in NVIZ to fly through a terrain.
 
 The NVIZ flight path can be chosen interactively from the GRASS
-monitor (<EM>-i</EM>) or supplied on the command line as comma
+monitor (<em>-i</em>) or supplied on the command line as comma
 separated coordinates. The program optionally allows a KeyFrame
 file to created (after running the script). This KeyFrame file can
-be loaded into the <EM>Keyframe Animation</EM> panel for fine
+be loaded into the <em>Keyframe Animation</em> panel for fine
 tuning or editing.
 
 <p>
-The script generated by <EM>m.nviz.script</EM> can be run from the NVIZ
+The script generated by <em>m.nviz.script</em> can be run from the NVIZ
 command line (nviz script=script_name) or after NVIZ is started by
-selecting <EM>Scripting->Play Script</EM>.
+selecting <em>Scripting->Play Script</em>.
 
-<H2>OPTIONS</H2>
+<h2>OPTIONS</h2>
 
 <H3>Flags:</H3>
 <DL>
@@ -30,14 +30,14 @@
 <DT><B>-c</B>
 <DD>Flay at constant elevation
 <DD>With this flag the camera will be set to an elevation given by the
-	<EM>ht=</EM> parameter. The default is to fly at <EM>ht=</EM>
+	<em>ht=</em> parameter. The default is to fly at <em>ht=</em>
 	above the topography (i.e. camera height = elevation + ht)
 <DT><B>-k</B>
 <DD>Output KeyFrame file
 <DD>Generate a KeyFrame file that can be loaded from the NVIZ
-	<EM>Keyframe Animation</EM> panel. The KeyFrame file is
+	<em>Keyframe Animation</em> panel. The KeyFrame file is
 	automatically assigned the script name with a
-	<EM>.kanimator</EM> extension.
+	<em>.kanimator</em> extension.
 <DT><B>-o</B>
 <DD>Render the animation in an off-screen context
 <DT><B>-e</B>
@@ -55,7 +55,7 @@
 <DD>The name of the NVIZ script to create.
 
 <DT><B>name</B>
-<DD>The prefix for output images if running in full render mode (<EM>-f</EM>).
+<DD>The prefix for output images if running in full render mode (<em>-f</em>).
 <DD>The defulat preifix is NVIZ (eg. NVIZ0000.ppm).
 
 <DT><B>dist</B>
@@ -63,7 +63,7 @@
 
 <DT><B>ht</B>
 <DD>The height of the camera above the center of view.
-<DD>If the the <EM>-c</EM> flag is set, the height represents the actual camera height.
+<DD>If the the <em>-c</em> flag is set, the height represents the actual camera height.
 
 <DT><B>frames</B>
 <DD>The number of frames in the animation.
@@ -76,11 +76,11 @@
 
 <DT><B>route</B>
 <DD>The comma separated geographic coordinates for keyframe locations.
-<DD>The interactive flag (<EM>-i</EM>) overrides this option.
+<DD>The interactive flag (<em>-i</em>) overrides this option.
 
 </DL>
 
-<H2>EXAMPLE</H2>
+<h2>EXAMPLE</h2>
 To interactively create an NVIZ animation from raster elev.rast with
 500 frames and the camera set to 50 meters above and 250 meters behind
 the scene, run the following:
@@ -96,11 +96,11 @@
 nviz elevation=elevation.dem script=nviz.script.nvscr
 </pre></div>
 
-<H2>NOTES / HINTS</H2>
+<h2>NOTES / HINTS</h2>
 The user must select at least four key-frame locations (points)
  otherwise an error is generated.
 <p>
-If the GRASS region is changed the <EM>m.nviz.script</EM> command must be re-run.
+If the GRASS region is changed the <em>m.nviz.script</em> command must be re-run.
 <p>
 The current GRASS region and the user supplied parameters are included
 as a comment at the top of the output script. This information can be
@@ -111,7 +111,7 @@
 the current window, in which case a non-fatal error is generated
 (Error: selected point is outside region).  This error can result in
 jerky movements during the animation.  To correct this problem reduce
-the <EM>dist=</EM> parameter or increase the current region.
+the <em>dist=</em> parameter or increase the current region.
 
 <h3>Loading the script into NVIZ</h3>
 
@@ -136,11 +136,11 @@
 kanimator script. Once loaded, the key frames will appear in the GUI
 and can then be edited there.
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
-<EM><A HREF="nviz.html">nviz</A></EM>
+<em><a href="nviz.html">nviz</A></em>
 
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
 
-<A HREF="mailto:bcovill at tekmap.ns.ca">Bob Covill</A>
+<a href="mailto:bcovill at tekmap.ns.ca">Bob Covill</A>
 <p><i>Last changed: $Date$</i>

Modified: grass/trunk/misc/m.transform/m.transform.html
===================================================================
--- grass/trunk/misc/m.transform/m.transform.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/misc/m.transform/m.transform.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -1,10 +1,10 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
-<EM>m.transform</EM> is an utility to compute transformation
+<em>m.transform</em> is an utility to compute transformation
 based upon GCPs and output error measurements.
 
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 
 For coordinates given with the <b>coords</b> file option or fed from
 <tt>stdin</tt>, the input format is "x y" with one coordinate pair per
@@ -52,16 +52,16 @@
 the higher coefficients equal to zero.
 
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
-<EM><A HREF="i.rectify.html">i.rectify</A></EM>
+<em><a href="i.rectify.html">i.rectify</A></em>
 
 
-<H2>AUTHORS</H2>
+<h2>AUTHORS</h2>
 
 Brian J. Buckley<br>
 Glynn Clements<br>
 Hamish Bowman
 
 <p>
-<i>Last changed: $Date$</i></p>
+<i>Last changed: $Date$</i>

Modified: grass/trunk/ps/ps.map/ps.map.html
===================================================================
--- grass/trunk/ps/ps.map/ps.map.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/ps/ps.map/ps.map.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -1,33 +1,33 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
-<EM>ps.map</EM> is a cartographic mapping program for producing high quality
+<em>ps.map</em> is a cartographic mapping program for producing high quality
 hardcopy maps in PostScript format. Output can include a raster map, any
 number of vector overlays, text labels, decorations, and other spatial data.
 
-<P>
+<p>
 A file of mapping instructions that describes the various spatial and textual
-information to be printed must be prepared prior to running <EM>ps.map</EM>.
+information to be printed must be prepared prior to running <em>ps.map</em>.
 
 
-<H2>NOTES</H2> 
+<h2>NOTES</h2> 
 
-<P>
+<p>
 The order of commands is generally unimportant but may affect how some layers
 are drawn. For example to plot <B>vpoints</B> above <B>vareas</B> list the
 <B>vpoints</B> entry first. Raster maps are always drawn first, and only a
 single raster map (or 3 if part of a RGB group) may be used.
 
-<P>
+<p>
 The hash character ('<tt>#</tt>') may be used at the beginning of a line
 to indicate that the line is a comment. Blank lines will also be ignored.
 
-<P>
+<p>
 Be aware that some mapping instructions require the <i>end</i> command
 and some do not. Any instruction that allows subcommands will require
 it, any instruction that does not allow subcommands will not.
 
-<P>
-The resolution and extent of raster maps plotted with <EM>ps.map</EM> are
+<p>
+The resolution and extent of raster maps plotted with <em>ps.map</em> are
 controlled by the current region settings via the
 <a href="g.region.html">g.region</a> module. The output filesize is largely
 a function of the region resolution, so special care should be taken
@@ -39,31 +39,31 @@
 output file larger, but with a consumer printer you probably won't be able
 to resolve any better detail in the hardcopy.
 
-<P>
+<p>
 The user can specify negative or greater than 100 percentage values for
 positioning several map decorations and embedded EPS-files, to move them
 outside the current map box region (for example to position a caption,
 barscale, or legend above or below the map box).
 
-<P>
+<p>
 One point ("pixel") is 1/72 of an inch.
 
-<P>
+<p>
 For users wanting to use special characters (such as accented characters) it
 is important to note that <em>ps.map</em> uses <tt>ISO-8859-1</tt> encoding.
 This means that your instructions file will have to be encoded in this
 encoding. If you normally work in a different encoding environment (such as
 <tt>UTF-8</tt>), you have to transform your file to the <tt>ISO-8859-1</tt>
 encoding, for example by using the <tt>iconv</tt> utility:
-</P>
+
 <DIV class="code"><PRE>
 iconv -f UTF-8 -t ISO_8859-1 utf_file > iso_file
 </PRE></DIV>
 
 
-<P><P>
+<p><p>
 
-<H2>MAPPING INSTRUCTIONS</H2>
+<h2>MAPPING INSTRUCTIONS</h2>
 
 The mapping instructions allow the user to specify various spatial data
 to be plotted. These instructions are normally prepared in a regular
@@ -71,7 +71,7 @@
 instructions while others are multiple line. Multiple line instructions
 consist of the main instruction followed by a subsection of one or more
 additional instructions and are terminated with an <i>end</i> instruction.
-<P>
+<p>
 
 <h3>Instruction keywords:</h3>
 [ 
@@ -116,15 +116,15 @@
 different main instructions are:
 
 <DL>
-<DT><B>where</B> <EM>x y</EM>
+<DT><B>where</B> <em>x y</em>
 
 <DD>The top left corner of the bounding box of the item to be plotted
-is located <EM>x</EM> inches from the left edge of the paper and
-<EM>y</EM> inches from the top edge of the paper. If <EM>x</EM> is less than
-or equal to zero, the default horizontal location is used.  If <EM>y</EM>
+is located <em>x</em> inches from the left edge of the paper and
+<em>y</em> inches from the top edge of the paper. If <em>x</em> is less than
+or equal to zero, the default horizontal location is used.  If <em>y</em>
 is less than or equal to zero, the default vertical location is used.
 
-<DT><B>font</B> <EM>font name</EM> 
+<DT><B>font</B> <em>font name</em> 
 
 <DD>The name of the PostScript font.
 Fonts present in all PostScript implementations are:
@@ -142,21 +142,21 @@
 Courier-Bold,
 and
 Courier-BoldOblique</tt>.
-<BR>
+<br>
 The default is Helvetica.
 </DD>
 
 
-<DT><B>fontsize</B> <EM>font size</EM> 
+<DT><B>fontsize</B> <em>font size</em> 
 
 <DD>The size of the PostScript font (in 1/72nds of an inch).
 The default is 10 point.
 </DD>
 
 
-<DT><a name="NAMED_COLORS"></a><B>color</B> <EM>name</EM>
+<DT><a name="NAMED_COLORS"></a><B>color</B> <em>name</em>
 
-<DD>The following colors names are accepted by <EM>ps.map</EM>:
+<DD>The following colors names are accepted by <em>ps.map</em>:
 <tt>
 aqua,
 black,
@@ -175,7 +175,7 @@
 white,
 yellow
 </tt>.
-<BR><BR>
+<br><br>
 For vectors and some plotting commands you can also specify
 '<tt>none</tt>' or '<tt>R:G:B</tt>' (e.g '<tt>255:0:0</tt>').
 </DD>
@@ -190,14 +190,14 @@
 
 
 </DL>
-<P>
-<BR>
+<p>
+<br>
 
 
 <h3>Command usage</h3>
 
 <a name="border"></a>
-<H2>border</H2>
+<h2>border</h2>
 
 Controls the border which is drawn around the map area.
 <PRE>
@@ -210,12 +210,12 @@
 or "none". The width is specified in points, unless followed by an "i"
 in which case it is measured in inches.
 The default is a black border box of width 1 point.
-<P>
+<p>
 The border can be turned off completely with the
 &quot;<tt>border&nbsp;n</tt>&quot; instruction. In this case
 the <B>end</B> command should not be given as the
 main command will be treated as a single line instruction.
-<P>
+<p>
 
 This example would create a grey border 0.1&quot; wide.
 <PRE>
@@ -225,11 +225,11 @@
 	<B>width</B> 0.1i
 	<B>end</B>
 </PRE>
-<P>
+<p>
 
 
 <a name="colortable"></a>
-<H2>colortable</H2>
+<h2>colortable</h2>
 
 Prints the color table legend for the raster map layer anywhere on the page.
 <PRE>
@@ -253,7 +253,7 @@
 the colors for each of a raster map's category values along with its
 associated category label. For a floating point (FCELL or DCELL) map a
 continuous gradient legend will be created.
-<P>
+<p>
 If <B>raster</B> is omitted, the colortable defaults to the previously
 registered raster layer.
 
@@ -263,11 +263,11 @@
 
 Omitting the <B>colortable</B> instruction would result in
 no color table.
-<P>
+<p>
 If the colortable is turned off with a &quot;<tt>colortable&nbsp;N</tt>&quot;
 instruction the <B>end</B> command should not be given as the  
 main command will be treated as a single line instruction.
-<P>
+<p>
 See also the <a href="#vlegend">vlegend</a> command for creating vector map
 legends.
 
@@ -277,13 +277,13 @@
 Adding the <B>nodata N</B> instruction will prevent the "no data" box 
 from being drawn (category based legends only). If you have manually
 added a "no data" label to the cats/ file it will be shown regardless.
-<P> 
+<p> 
 <B>Note</B>:  Be careful about asking for color tables for integer
 raster map layers which have many categories, such as elevation.
 This could result in the printing of an extremely long color table!
 In this situation it is useful to use the <B>discrete N</B> instruction
 to force a continuous color gradient legend.
-<P>
+<p>
 Be aware that the color table only includes categories which
 have a label. You can use the <em>r.category</em> module to add labels.
 
@@ -312,8 +312,8 @@
 <em>r.category</em> or <em>r.support</em> module to set up the range labels
 first.
 
-<BR>
-<P>
+<br>
+<p>
 This example would print a color table immediately below any other map legend
 information, starting at the left margin, with 4 columns:
 <PRE>
@@ -323,11 +323,11 @@
         <B>width</B> 4
         <B>end</B>
 </PRE>
-<P>
+<p>
 
 
 <a name="comments"></a>
-<H2>comments</H2>
+<h2>comments</h2>
 
 Prints comments anywhere on the page.
 <PRE>
@@ -340,15 +340,15 @@
 </PRE>
 The default location is immediately below the last item item printed,
 starting at the left margin. The default text color is black.
-<P>
+<p>
 If you wish to use parentheses spanning multiple lines you will need to
 quote them with a backslash to prevent the PostScript interpreter from 
 getting confused. e.g. '<B><TT>\(</TT></B>' and '<B><TT>\)</TT></B>'
 
-<P>
+<p>
 
 This example prints in blue
-whatever is in the file <EM>veg.comments</EM> starting at
+whatever is in the file <em>veg.comments</em> starting at
 1.5 inches from the left edge of the page and 7.25 inches from the top of
 the page, using a 15/72 inch Helvetica Bold font.
 <PRE>
@@ -362,28 +362,28 @@
 	<B>end</B>
 </PRE>
 Presumably, the file
-<EM>veg.comments</EM>
+<em>veg.comments</em>
 contain comments
-pertaining to the raster map layer <EM>vegetation</EM>,
+pertaining to the raster map layer <em>vegetation</em>,
 such as "This map was created by classifying a LANDSAT TM image".
-<P>
+<p>
 
 
 <a name="copies"></a>
-<H2>copies</H2>
+<h2>copies</h2>
 
 Specifies the number of copies to be printed.
 <PRE>
 USAGE:	<B>copies</B> n
 </PRE>
 Each page will be printed n times.
-<P>
-This instruction is identical to the <EM>copies</EM> command line parameter.
-<P>
+<p>
+This instruction is identical to the <em>copies</em> command line parameter.
+<p>
 
 
 <a name="eps"></a>
-<H2>eps</H2>
+<h2>eps</h2>
 
 Places EPS (Encapsulated PostScript) pictures on the output map.
 <PRE>
@@ -405,9 +405,9 @@
 (default is 0)
 and whether the point is to be <B>masked</B>
 by the current mask.
-(See manual entry for <EM><A HREF="r.mask.html">r.mask</A></EM> 
+(See manual entry for <em><a href="r.mask.html">r.mask</A></em> 
 for more information on the mask.)
-<P>
+<p>
 
 This example would place a EPS file ./epsf/logo.eps
 at the point (E456000 N7890000).  This picture would be
@@ -423,13 +423,13 @@
 	<B>end</B>	
 </PRE>
 Of course, multiple EPS pictures may be drawn with multiple
-<EM>eps</EM>
+<em>eps</em>
 instructions.
-<P>
+<p>
 
 
 <a name="geogrid"></a>
-<H2>geogrid</H2>
+<h2>geogrid</h2>
 
 Overlays a geographic grid onto the output map.
 <PRE>
@@ -454,11 +454,11 @@
 (2), etc., and what color the numbers should be.  The defaults are
 black grid lines, unnumbered.
 
-<P>
+<p>
 
 NOTE: The <B>geogrid</B> draws grid numbers on the east and south borders of the map.
 
-<P>
+<p>
 
 This example would overlay a blue geographic grid with a spacing of 30 minutes
 onto the output map.  Alternate grid
@@ -470,25 +470,25 @@
 	<B>numbers</B> 2 yellow
 	<B>end</B>
 </PRE>
-<P>
+<p>
 
 
 <a name="greyrast"></a>
-<H2>greyrast</H2>
+<h2>greyrast</h2>
 
 Selects a raster map layer for output in shades of grey.
 <PRE>
 USAGE:	<B>greyrast</B> mapname
 </PRE>
 For each 
-<EM>ps.map</EM>
+<em>ps.map</em>
 run, only one raster map layer can be requested (using either the
-<EM>greyrast</EM> or the <EM>raster</EM> instruction).
-<P>
+<em>greyrast</em> or the <em>raster</em> instruction).
+<p>
 
 
 <a name="grid"></a>
-<H2>grid</H2>
+<h2>grid</h2>
 
 Overlays a coordinate grid onto the output map.
 <PRE>
@@ -513,7 +513,7 @@
 with cross size given in geographic coordinate system units.
 The defaults are black grid lines, unnumbered.
 
-<P>
+<p>
 
 This example would overlay a green grid with a spacing of 10000 meters
 (for a metered database, like UTM) onto the output map.  Alternate grid
@@ -525,24 +525,24 @@
 	<B>numbers</B> 2 red
 	<B>end</B>
 </PRE>
-<P>
+<p>
 
 
 <a name="group"></a>
-<H2>group</H2>
+<h2>group</h2>
 
 Selects an RGB imagery group for output.
 <PRE>
-USAGE:	<B>group</B> <EM>groupname</EM>
+USAGE:	<B>group</B> <em>groupname</em>
 </PRE>
-This is similar to <EM>raster</EM>, except that it uses an imagery group
+This is similar to <em>raster</em>, except that it uses an imagery group
 instead of a raster map layer. The group must contain three raster map
 layers, comprising the red, green and blue bands of the image.
-<P>
+<p>
 
 
 <a name="header"></a>
-<H2>header</H2>
+<h2>header</h2>
 
 Prints the map header above the map.
 <PRE>
@@ -553,13 +553,13 @@
 	<B>color</B> text color
 	<B>end</B>
 </PRE>
-If the <EM>file</EM> sub-instruction is absent the header will consist
+If the <em>file</em> sub-instruction is absent the header will consist
 of the map's title <!-- from hist file -->
 and the location's description.<!-- PERMANENT/MYNAME -->
 The text will be centered on the page above the map.
 The default text color is black.
-<P>
-If the <EM>file</EM> sub-instruction is given the header will consist
+<p>
+If the <em>file</em> sub-instruction is given the header will consist
 of the text in the text file specified, with some special formatting keys:
 
 <ul>
@@ -591,9 +591,9 @@
 %_
 </pre></div>
 
-<P>
+<p>
 
-This example prints (in red) whatever is in the file <EM>soils.hdr</EM> above
+This example prints (in red) whatever is in the file <em>soils.hdr</em> above
 the map, using a 20/72 inch <tt>Courier</tt> font.
 <PRE>
 EXAMPLE:	
@@ -604,38 +604,38 @@
 	<B>color</B> red
 	<B>end</B>
 </PRE>
-<P>
+<p>
 
 
 <a name="labels"></a>
-<H2>labels</H2>
+<h2>labels</h2>
 
 Selects a labels file for output (see manual entry for
-<EM>
-<A HREF="v.label.html">v.label</A>
-).</EM>
+<em>
+<a href="v.label.html">v.label</A>
+).</em>
 <PRE>
 USAGE:	<B>labels</B>  labelfile
 	<B>font</B> font name
 	<B>end</B>
 </PRE>
-<P>
+<p>
 NOTE: ps.map can read new option 'ROTATE:' from labels file, which
 specifies counter clockwise rotation in degrees. 
-<P>
+<p>
 This example would paint labels from the labels file called
-<EM>town.names</EM>.  Presumably, these labels would indicate the names of
+<em>town.names</em>.  Presumably, these labels would indicate the names of
 towns on the map.
 <PRE>
 EXAMPLE:	
 	<B>labels</B> town.names
 	<B>end</B>
 </PRE>
-<P>
+<p>
 
 
 <a name="line"></a>
-<H2>line</H2>
+<h2>line</h2>
 
 Draws lines on the output map.
 <PRE>
@@ -652,12 +652,12 @@
 The user may also specify line <B>color</B>, <B>width</B>
 in points (1/72"; accepts decimal values as well as integers),
 and if the line is to be <B>masked</B> by the current mask.
-(See manual entry for <EM><A HREF="r.mask.html">r.mask</A>
-</EM> for more information on the mask.)
+(See manual entry for <em><a href="r.mask.html">r.mask</A>
+</em> for more information on the mask.)
 The line <B>width</B> (if given) is measured in points; an <i>i</i>
 directly following the number indicates that the width is given in
 inches instead.
-<P>
+<p>
 
 This example would draw a yellow line from the point x=10% y=80%
 to the point x=30% y=70%.
@@ -672,13 +672,13 @@
 	<B>end</B>
 </PRE>
 Of course, multiple lines may be drawn with multiple
-<EM>line</EM>
+<em>line</em>
 instructions.
-<P>
+<p>
 
 
 <a name="mapinfo"></a>
-<H2>mapinfo</H2>
+<h2>mapinfo</h2>
 
 Prints the portion of the map legend containing the scale, grid and
 region information, on or below the map.
@@ -696,10 +696,10 @@
 starting at the left edge of the map.
 The default text color is black.
 The default background box color is white.
-<P>
-<EM>border</EM> will draw a border around the legend using the specified color.
+<p>
+<em>border</em> will draw a border around the legend using the specified color.
  (see <a href="#NAMED_COLORS">NAMED COLORS</a>)
-<P>
+<p>
 
 This example prints (in brown) the scale, grid and region information
 immediately below the map and starting 1.5 inches from the left edge
@@ -714,22 +714,22 @@
 	<B>color</B> brown
 	<B>end</B>
 </PRE>
-<P>
+<p>
 
 
 <a name="maploc"></a>
-<H2>maploc</H2>
+<h2>maploc</h2>
 
 Positions the map on the page.
 <PRE>
 USAGE:	<B>maploc</B>  x y [width height]
 </PRE>
-The upper left corner of the map will be positioned <EM>x</EM> inches from
-the left edge of the page and <EM>y</EM> inches from the top of the page.
-If <EM>width</EM> and <EM>height</EM> (in inches) are present, the map will be
+The upper left corner of the map will be positioned <em>x</em> inches from
+the left edge of the page and <em>y</em> inches from the top of the page.
+If <em>width</em> and <em>height</em> (in inches) are present, the map will be
 rescaled, if necessary, to fit.
 
-<P>
+<p>
 
 This example positions the upper left corner of the map 2.0 inches from
 the left edge and 3.5 inches from the top edge of the map.
@@ -737,11 +737,11 @@
 EXAMPLE:
 	<B>maploc</B> 2.0 3.5
 </PRE>
-<P>
+<p>
 
 
 <a name="maskcolor"></a>
-<H2>maskcolor</H2>
+<h2>maskcolor</h2>
 
 Color to be used for mask.
 <PRE>
@@ -750,7 +750,7 @@
 
 
 <a name="outline"></a>
-<H2>outline</H2>
+<h2>outline</h2>
 
 Outlines the areas of a raster map layer with a specified color.
 <PRE>
@@ -771,10 +771,10 @@
 (It is hoped that in the future the outline of a different raster map
 layer other than the one currently being painted may be placed on the map.)
 
-<P>
+<p>
 
 This example would outline the category areas of the
-<EM>soils</EM>
+<em>soils</em>
 raster map layer
 in grey.
 <PRE>
@@ -785,11 +785,11 @@
 	<B>width</B> 2
 	<B>end</B>
 </PRE>
-<P>
+<p>
 
 
 <a name="paper"></a>
-<H2>paper</H2>
+<h2>paper</h2>
 
 Specifies paper size and margins.
 <PRE>
@@ -808,14 +808,14 @@
 <B>left</B>, <B>right</B>, <B>bottom</B> and <B>top</B> are paper margins.
 If the plot is rotated with the <b>-r</b> command line flag, measures
 are applied to the <em>rotated</em> page.
-<P>
+<p>
 
 <PRE>
 EXAMPLE:
 	<B>paper</B> a3
 	<B>end</B>	
 </PRE>
-<P>
+<p>
 <PRE>
 EXAMPLE:
 	<B>paper</B>
@@ -827,11 +827,11 @@
 	<B>top</B> 2
 	<B>end</B>	
 </PRE>
-<P>
+<p>
 
 
 <a name="point"></a>
-<H2>point</H2>
+<h2>point</h2>
 
 Places additional points or icons on the output map.
 <PRE>
@@ -852,15 +852,15 @@
 the <B>size</B> of symbol in points,
 the rotation angle (in degrees CCW), 
 and whether the point is to be <B>masked</B> by the current mask.
-(See manual entry for <EM> <A HREF="r.mask.html">r.mask</A>
-</EM> for more information on the mask.)
+(See manual entry for <em> <a href="r.mask.html">r.mask</A>
+</em> for more information on the mask.)
 The symbol line <B>width</B> (if given) is measured in points; an <i>i</i>
 directly following the number indicates that the width is given in inches
 instead. If a <B>width</B> is not given it will be set proportional to the
 symbol size.
-<P>
+<p>
 This example would place a purple diamond (from icon file
-<EM>diamond</EM>) at the point (E456000 N7890000).  This diamond would be the 
+<em>diamond</em>) at the point (E456000 N7890000).  This diamond would be the 
 the size of a 15 points and would not be masked by the current mask.
 <PRE>
 EXAMPLE:
@@ -873,20 +873,20 @@
 	<B>end</B>	
 </PRE>
 Of course, multiple points may be drawn with multiple
-<EM>point</EM>
+<em>point</em>
 instructions.
-<P>
+<p>
 
 
 <a name="psfile"></a>
-<H2>psfile</H2>
+<h2>psfile</h2>
 
 Copies a file containing PostScript commands into the output file.
 
-<P>
+<p>
 
 <B>Note:</B>
-<EM>ps.map</EM>
+<em>ps.map</em>
 will not search for this file.  The user must be in the
 correct directory or specify the full path on the <B>psfile</B> instruction.
 (Note to /bin/csh users: ~ won't work with this instruction).
@@ -898,76 +898,76 @@
 EXAMPLE:	
 	<B>psfile</B> logo.ps
 </PRE>
-<P>
+<p>
 
 
 <a name="raster"></a>
-<H2>raster</H2>
+<h2>raster</h2>
 
 Selects a raster map layer for output.
 <PRE>
 USAGE:	<B>raster</B> mapname
 </PRE>
-For each <EM>ps.map</EM> run, only one raster map layer (or set
+For each <em>ps.map</em> run, only one raster map layer (or set
 of layers or imagery group; see below) can be requested. If no
 raster map layer is requested, a completely white map will be
 produced. It can be useful to select no raster map layer in
 order to provide a white background for vector maps.
-<P>
-Note that an imagery group selected with the <EM>group</EM>
+<p>
+Note that an imagery group selected with the <em>group</em>
 option, or a set of three raster layers selected with the
-<EM>rgb</EM> option, count as a raster map layer for the
+<em>rgb</em> option, count as a raster map layer for the
 purposes of the preceding paragraph.
-<P>
+<p>
 The PostScript file's internal title will be set to the raster map's
 title, which in turn may be set with the <em>r.suppport</em> module.
-<P>
-This example would paint a map of the raster map layer <EM>soils</EM>.
+<p>
+This example would paint a map of the raster map layer <em>soils</em>.
 
 <PRE>
 EXAMPLE:	
 	<B>raster</B> soils
 </PRE>
-<P>
+<p>
 
 
 <a name="read"></a>
-<H2>read</H2>
+<h2>read</h2>
 
-Provides <EM>ps.map</EM> with a previously prepared input stream.
+Provides <em>ps.map</em> with a previously prepared input stream.
 <PRE>
 USAGE:	<B>read</B> previously prepared UNIX file
 </PRE>
 Mapping instructions can be placed into a file and read into
-<EM>ps.map.</EM>
+<em>ps.map.</em>
 
-<P>
+<p>
 
 <B>Note:</B>
-<EM>ps.map</EM>
+<em>ps.map</em>
 will not search for this file.  The user must be in the
 correct directory or specify the full path on the <B>read</B> instruction.
 (Note to /bin/csh users: ~ won't work with this instruction).
 
-<P>
+<p>
 
-This example reads the UNIX file <EM>pmap.roads</EM> into <EM>ps.map</EM>.
-This file may contain all the <EM>ps.map</EM> instructions for placing
-the vector map layer <EM>roads</EM> onto the output map.
+This example reads the UNIX file <em>pmap.roads</em> into <em>ps.map</em>.
+This file may contain all the <em>ps.map</em> instructions for placing
+the vector map layer <em>roads</em> onto the output map.
 <PRE>
 EXAMPLE: 
 	<B>read</B> pmap.roads
 </PRE>
 The user may have created this file because this vector map layer
-is particularly useful for many <EM>ps.map</EM>
+is particularly useful for many <em>ps.map</em>
 outputs.  By using the <B>read</B> option, the user need not enter all the input
 for the <B>vector</B> instruction, but simply <B>read</B> the previously prepared
 file with the correct instructions.
-<P>
+<p>
 
 
 <a name="rectangle"></a>
-<H2>rectangle</H2>
+<h2>rectangle</h2>
 
 Draws rectangle on the output map.
 <PRE>
@@ -986,14 +986,14 @@
 <B>color</B>, fill color <B>fcolor</B>, <B>width</B>
 in points (accepts decimal points [floating points] as well as integers),
 and if the rectangle is to be <B>masked</B> by the current mask.
-(See manual entry for <EM><A HREF="r.mask.html">r.mask</A></EM>
+(See manual entry for <em><a href="r.mask.html">r.mask</A></em>
 for more information on the mask.)
 The border line <B>width</B> (if given) is measured in points; an <i>i</i>
 directly following the number indicates that the width is given in inches
 instead.
-<BR>
-Multiple rectangles may be drawn by using multiple <EM>rectangle</EM> instructions.
-<P>
+<br>
+Multiple rectangles may be drawn by using multiple <em>rectangle</em> instructions.
+<p>
 
 This example would draw a yellow rectangle filled by green from the point x=10% y=80%
 to the point x=30% y=70%.
@@ -1007,11 +1007,11 @@
 	<B>masked</B> n
 	<B>end</B>
 </PRE>
-<P>
+<p>
 
 
 <a name="region"></a>
-<H2>region</H2>
+<h2>region</h2>
 
 Places the outline of a smaller geographic region
 on the output.
@@ -1021,21 +1021,21 @@
 	<B>width</B> #
 	<B>end</B>
 </PRE>
-Geographic region settings are created and saved using <EM> the 
-<A HREF="g.region.html">g.region</A></EM> module.
-The <EM>ps.map</EM> <EM>region</EM> option can be used to show an outline of
-a smaller region which was printed on a separate run of <EM>ps.map</EM>
+Geographic region settings are created and saved using <em> the 
+<a href="g.region.html">g.region</A></em> module.
+The <em>ps.map</em> <em>region</em> option can be used to show an outline of
+a smaller region which was printed on a separate run of <em>ps.map</em>
 on other user-created maps.
-<P>
+<p>
 The user can specify the <B>color</B>
 and the <B>width</B> in point units (accepts decimal points
 [floating points] as well as integers) of the outline.
 The default is a black border of one point width (1/72").
-<P>
+<p>
 This example would place a white outline, 2 points wide, of the
-geographic region called <EM>fire.zones</EM> onto the output map.
+geographic region called <em>fire.zones</em> onto the output map.
 This geographic region would have been created and saved using 
-<EM><A HREF="g.region.html">g.region</A></EM>.
+<em><a href="g.region.html">g.region</A></em>.
 <PRE>
 EXAMPLE:
 	<B>region</B> fire.zones
@@ -1043,35 +1043,35 @@
 	<B>width</B> 2
 	<B>end</B>
 </PRE>
-<P>
+<p>
 
 
 <a name="rgb"></a>
-<H2>rgb</H2>
+<h2>rgb</h2>
 
 Selects three raster map layers for output as an RGB color image.
 <PRE>
-USAGE:	<B>rgb</B> <EM>red</EM> <EM>green</EM> <EM>blue</EM>
+USAGE:	<B>rgb</B> <em>red</em> <em>green</em> <em>blue</em>
 </PRE>
-This is similar to <EM>raster</EM>, except that it uses three
+This is similar to <em>raster</em>, except that it uses three
 raster map layers instead of a single layer. The three layers
-are composed to form a color image, similar to <EM>d.rgb</EM>.
-<P>
+are composed to form a color image, similar to <em>d.rgb</em>.
+<p>
 
 For each layer, only one of the components of the layer's color
 table is used: the red component for the red layer, and so on. 
 This will give the desired result if all of the layers have a
 grey-scale color table, or if each layer's color table uses the
 hue appropriate to the layer.
-<P>
+<p>
 
 
 <a name="scale"></a>
-<H2>scale</H2>
+<h2>scale</h2>
 
 Selects a scale for the output map.
 <PRE>
-USAGE:	<B>scale</B> <EM>scale</EM>
+USAGE:	<B>scale</B> <em>scale</em>
 </PRE>
 The scale can be selected either as:
 <DL>
@@ -1081,13 +1081,13 @@
 <DD>an absolute width of the printed map, e.g. 10 inches;
 <DT> 
 <DD>the number of printed paper panels, e.g. 3 panels
-<EM>.I</EM>
+<em>.I</em>
 (at the present time, only 1 panel is supported);
 <DT> 
 <DD>the number of miles per inch, e.g. 1 inch equals 4 miles.
 </DD>
 </DL>
-<P>
+<p>
 
 This example would set the scale of the map to 1 unit = 25000
 units.
@@ -1095,11 +1095,11 @@
 EXAMPLE:	
 	<B>scale</B> 1:25000
 </PRE>
-<P>
+<p>
 
 
 <a name="scalebar"></a>
-<H2>scalebar</H2>
+<h2>scalebar</h2>
 
 Draws a scalebar on the map.
 <PRE>
@@ -1128,14 +1128,14 @@
 numbers every n-th segment.
 
 The <B>background</B> command can turn off the background box for the text.
-<P>
+<p>
 The scalebar <B>length</B> is the only required argument. The defaults are a
 fancy scalebar with 4 segments, each segment labeled, and a height of 0.1
 inches. The default location is 2 inches from the top of the page and
 halfway across.
-<P>
+<p>
 NOTE: The scalebar is centered on the location given.
-<P>
+<p>
 This example draws a simple scalebar 1000 meters (for a metered database,
 like UTM) long, with tics every 200 meters, labeled every second tic.
 The scalebar is drawn 5 inches from the top and 4 inches from the left
@@ -1153,7 +1153,7 @@
 
 
 <a name="setcolor"></a>
-<H2>setcolor</H2>
+<h2>setcolor</h2>
 
 Overrides the color assigned to one or more categories
 of the raster map layer.
@@ -1161,7 +1161,7 @@
 USAGE:	<B>setcolor</B> cat(s) color
 </PRE>
 This example would set the color for categories 2,5 and 8 of the raster
-map layer <EM>watersheds</EM> to white and category 10 to green.
+map layer <em>watersheds</em> to white and category 10 to green.
 (<B>NOTE</B>: no spaces are inserted between the category values.)
 <PRE>
 EXAMPLE:	
@@ -1169,17 +1169,17 @@
 	<B>setcolor</B> 2,5,8 white
 	<B>setcolor</B> 10 green
 </PRE>
-Of course, <EM>setcolor</EM>
+Of course, <em>setcolor</em>
 can be requested more than once to override the default color for additional
 categories.  More than one category can be changed for each request by listing
 all the category values separated by commas (but with no spaces). Also ranges
 can be included, for example "1,2,6-10,12". Colors for "<tt>null</tt>" and the
 "<tt>default</tt>" (i.e. out-of-range) color may also be reassigned.
-<P>
+<p>
 
 
 <a name="text"></a>
-<H2>text</H2>
+<h2>text</h2>
 
 Places text on the map.
 <PRE>
@@ -1207,61 +1207,61 @@
 More than one line of text can be specified by notating the end of a line with
 <B>\n</B>
 (e.g. USA<B>\n</B>CERL).
-<P>
+<p>
 The user can then specify various text features:
-<P>
+<p>
 <B>font:</B>
 the PostScript font. Common possibilities are listed at the start of this
 help page. The default is <tt>Helvetica</tt>.
-<P>
+<p>
 <B>color</B>
 (see <a href="#NAMED_COLORS">NAMED COLORS</a>);
-<P>
+<p>
 <B>width</B>
 of the lines used to draw the text to make thicker letters
 (accepts decimal points [floating points] as well as integers);
-<P>
+<p>
 <B>size</B> and <B>fontsize.</B>&nbsp;
 <B>size</B> gives the vertical height of the letters in meters on the
 ground (text size will grow or shrink depending on the scale at which
 the map is painted). Alternatively <B>fontsize</B> can set the font
 size directly. If neither <B>size</B> or <B>fontsize</B> is given, a 
 default font size of 10 will be used;
-<P>
+<p>
 the highlight color (<B>hcolor</B>) and
 the width of the highlight color (<B>hwidth</B>);
-<P>
+<p>
 the text-enclosing-box <B>background</B> color;
 the text box <B>border</B> color;
-<P>
+<p>
 <B>ref.</B>
 This reference point specifies the text handle - what
 part of the text should be placed on the location specified by the map
 coordinates.  Reference points can refer to:
 [lower|upper|center] [left|right|center] of the text to be printed;
 The default is center center, i.e. the text is centered on the reference point.
-<P>
+<p>
 <B>rotate</B>
 sets the text rotation angle, measured in degrees counter-clockwise.
-<P>
+<p>
 <B>yoffset</B>,
 which provides finer placement of text by shifting the
 text a vertical distance in points (1/72") from the specified north.
 The vertical offset will shift the location to the south if positive,
 north if negative;
-<P>
+<p>
 <B>xoffset</B>,
 which shifts the text a horizontal distance in points from
 the specified east The horizontal offset will shift the location east if 
 positive, west if negative;
-<P>
+<p>
 <B>opaque</B>,
 whether or not the text should be <B>opaque</B> to vectors.  Entering <B>no</B>
 to the opaque option will allow the user to see any vectors which go
 through the text's background box.  Otherwise, they will end at the box's edge.
-<P>
-<BR>
-The following example would place the text <EM>SPEARFISH LAND COVER</EM>
+<p>
+<br>
+The following example would place the text <em>SPEARFISH LAND COVER</em>
 at the coordinates E650000 N7365000. The text would be a total of
 3 points wide (2 pixels of red text and 1 pixel black highlight), have a white
 background enclosed in a red box, and be 500 meters in size.  The lower right
@@ -1282,11 +1282,11 @@
 	<B>opaque</B> y
 	<B>end</B>
 </PRE>
-<P>
+<p>
 
 
 <a name="vareas"></a>
-<H2>vareas</H2>
+<h2>vareas</h2>
 
 Selects a vector map layer for output and plots areas.
 <PRE>
@@ -1307,34 +1307,34 @@
 	<B>end</B>
 </PRE>
 The user can specify:
-<P>
+<p>
 <B>color</B> - color of the vector lines or area boundaries;
-<P>
+<p>
 <B>fcolor</B> - the area fill color;
-<P>
+<p>
 <B>rgbcolumn</B> - name of color definition column used for the area fill color;
-<P>
+<p>
 <B>width</B> - width of the vectors lines or area boundaries in points
 (accepts decimal points [floating points] as well as integers);
-<P>
+<p>
 <B>masked</B> - whether or not the raster map layer is to be masked
 by the current mask;
-(see manual entry <EM><A HREF="r.mask.html">r.mask</A></EM>
+(see manual entry <em><a href="r.mask.html">r.mask</A></em>
 for more information on the mask)
-<P>
+<p>
 <B>cats</B> - which categories should be plotted (default is all);
-<P>
+<p>
 <B>where</B> - select features using a SQL where statement.
 For example: <tt>vlastnik = 'Cimrman'</tt>;
-<P>
+<p>
 <B>label</B> - for description in <a href="#vlegend">vlegend</a>.
 Default is: map(mapset);
-<P>
+<p>
 <B>lpos</B> - position vector is plotted in legend. If lpos is
 0 then this vector is omitted in legend. If more vectors used the 
 same lpos then their symbols in legend are merged and label for
 first vector is used.
-<P>
+<p>
 <B>pat</B> - full path to pattern file. The pattern file contains header and
 simple PostScript commands. It is similar to EPS but more limited, meaning that
 while each pattern file is a true EPS file, most EPS files are not useful as pattern
@@ -1360,12 +1360,12 @@
 </PRE></div>
 
 
-<P>
+<p>
 <B>scale</B> - pattern scale
-<P>
+<p>
 <B>pwidth</B> - pattern line width, width is used by pattern until the width is overwritten
 in pattern file.
-<P>
+<p>
 
 <PRE>
 EXAMPLE:	
@@ -1376,11 +1376,11 @@
 	<B>cats</B> 2,5-7	
 	<B>end</B>
 </PRE>
-<P>
+<p>
 
 
 <a name="vlines"></a>
-<H2>vlines</H2>
+<h2>vlines</h2>
 
 Selects a vector map layer for output and plots lines.
 <PRE>
@@ -1406,40 +1406,40 @@
 	<B>end</B>
 </PRE>
 The user can specify:
-<P>
+<p>
 <B>type</B> - the default is lines only;
-<P>
+<p>
 <B>color</B> - color of the vector lines or area boundaries;
-<P>
+<p>
 <B>rgbcolumn</B> - name of color definition column used for the vector lines
 or area boundaries;
-<P>
+<p>
 <B>width</B> - width of the vectors lines or area boundaries in points
 (accepts decimal points [floating points] as well as integers);
-<P>
+<p>
 <B>cwidth</B> - width of the vectors lines. If cwidth is used then 
 width of line is equal to cwidth * category value and width is 
 used in legend;
-<P>
+<p>
 <B>hcolor</B> - the highlight color for the vector lines;
-<P>
+<p>
 <B>hwidth</B> - the width of the highlight color in points;
-<P>
+<p>
 <B>offset</B> (experimental) - offset for the vectors lines in points (1/72")
 for plotting parallel lines in distance equal to offset (accepts positive or 
 negative decimal points). Useful to print streets with several parallel lanes;
-<P>
+<p>
 <B>coffset</B> (experimental) - offset for the vectors lines. If coffset
 is used then  offset of line is equal to coffset * category value and offset
 is used in legend;
-<P>
+<p>
 <B>ref</B> (experimental) - line justification. 
-<P>
+<p>
 <B>masked</B> - whether or not the raster map layer is to be masked
 by the current mask;
-(see manual entry <EM><A HREF="r.mask.html">r.mask</A></EM>
+(see manual entry <em><a href="r.mask.html">r.mask</A></em>
 for more information on the mask);
-<P>
+<p>
 <B>style</B> - the line style allows the vectors to be dashed in different
 patterns.  This is done by either typing "solid", "dashed", "dotted", or
 "dashdotted", or as a series of 0's and 1's in a desired sequence or pattern.
@@ -1448,24 +1448,24 @@
 An even number of blocks will repeat the pattern, an odd number of blocks
 will alternate the pattern.
 The default is "solid";
-<P>
+<p>
 <B>linecap</B> - the linecap specifies the look of the ends of the line,
 or the end of the dashes in a dashed line. The parameters are:
 'butt' for butt caps (default), 'round' for round caps and 'extended_butt'
 for extended butt caps. The shape of the round and the extended butt caps
 is related to the line thickness: for round butts the radius is half the
 linewidth, while for extended butt the line will extend for half the linewidth.  
-<P>
+<p>
 <B>cats</B> - which categories should be plotted (default is all);
-<P>
+<p>
 <B>label</B> - for description in <a href="#vlegend">vlegend</a>.
 Default is: map(mapset);
-<P>
+<p>
 <B>lpos</B> - position vector is plotted in legend. If lpos is
 0 then this vector is omitted in legend. If more vectors used the 
 same lpos then their symbols in legend are merged and label for
 first vector is used.
-<P>
+<p>
 
 <PRE>
 EXAMPLE:	
@@ -1479,11 +1479,11 @@
 	<B>label</B> Streams - category 2
 	<B>end</B>
 </PRE>
-<P>
+<p>
 
 
 <a name="vpoints"></a>
-<H2>vpoints</H2>
+<h2>vpoints</h2>
 
 Selects vector point data to be placed on the output map
 <PRE>
@@ -1514,7 +1514,7 @@
 the <B>eps</B> Encapsulated Postscript file to be used to represent the presence of a site
 (if '<B>$</B>' is used in the EPS file path it will be replaced by category number); 
 and <B>rotate</B> (in degrees) for counter-clockwise rotation.
-<BR>
+<br>
 The size of the icon (number of times larger than the size it is in
 the icon file) is typically given by the <B>size</B> option. Alternatively
 the size of the symbol or EPS graphic can be taken from an attribute column 
@@ -1531,10 +1531,10 @@
 	<B>size</B> 10
 	<B>end</B>
 </PRE>
-<P>
+<p>
 
 <a name="vlegend"></a>
-<H2>vlegend</H2>
+<h2>vlegend</h2>
 
 Prints the portion of the map legend containing the 
 vector information, on or below the map.
@@ -1552,32 +1552,32 @@
 </PRE>
 The default location is immediately below the legend containing the
 scale, grid and region information, starting at the left edge of the map.
-If the <EM>where</EM> instruction is present and <EM>y</EM> is less than or
+If the <em>where</em> instruction is present and <em>y</em> is less than or
 equal to zero, the vector legend will be positioned immediately below
-the map, starting <EM>x</EM> inches from the left edge of the page.
-<P>
-<EM>width</EM> is the width in inches of the color symbol (for lines)
+the map, starting <em>x</em> inches from the left edge of the page.
+<p>
+<em>width</em> is the width in inches of the color symbol (for lines)
 in front of the legend text. The default is 1/24 * fontsize inches.
-<P>
-<EM>cols</EM> is the number of columns to split the legend into. The
+<p>
+<em>cols</em> is the number of columns to split the legend into. The
 default is one column. The maximum number of colums is 10, or equal
 to the number of legend entries if there are less than 10 entries.
-<P>
-<EM>span</EM> is the column separation distance between the left edges of
+<p>
+<em>span</em> is the column separation distance between the left edges of
 two columns in a multicolumn legend. It is given in inches.
 The default is automatic scaling based on the left margin and the right
 hand side of the map box.
-<P>
-<EM>border</EM> will draw a border around the legend using the specified color.
+<p>
+<em>border</em> will draw a border around the legend using the specified color.
  (see <a href="#NAMED_COLORS">NAMED COLORS</a>)
-<P>
+<p>
 Alternatively, the user can create a custom legend by using the 
 <a href="#rectangle">rectangle</a>, <a href="#point">point</a>, and 
 <a href="#text">text</a> instructions.
-<P>
+<p>
 See also the <a href="#colortable">colortable</a> command for creating
 raster map legends.
-<P>
+<p>
 This example prints the vector legend
 immediately below the map and starting 4.5 inches from the left edge
 of the page, using a 12/72 inch Helvetica font.
@@ -1590,28 +1590,28 @@
 	<B>fontsize</B> 12
 	<B>end</B>
 </PRE>
-<P>
+<p>
 
 
 <a name="end"></a>
-<H2>end</H2>
+<h2>end</h2>
 
 Terminates input and begin painting the map.
 
 <PRE>
 USAGE:	<B>end</B>
 </PRE>
-<BR>
-<P>
+<br>
+<p>
 
 
-<H2>EXAMPLES</H2>
+<h2>EXAMPLES</h2>
 
 
-The following are examples of <EM>ps.map</EM> script files.
-<P>
+The following are examples of <em>ps.map</em> script files.
+<p>
 <h3>Simple example</h3>
-The file has been named <EM>spear.basic</EM>:
+The file has been named <em>spear.basic</em>:
 
 <PRE>
 # this ps.map example draws a map of Spearfish, SD
@@ -1631,7 +1631,7 @@
 
 
 <h3>More complicated example</h3>
-The file has been named <EM>spear.soils</EM>:
+The file has been named <em>spear.soils</em>:
 
 <PRE>
 # this ps.map example draws a map of Spearfish, SD
@@ -1713,33 +1713,33 @@
  ps.map input=spear.soils output=soils.ps
 </pre></div>
 
-<P>
+<p>
 More examples can be found on the
 <a href="http://grass.osgeo.org/wiki/Ps.map_scripts">GRASS Wiki</a>
 help site.
-<P>
+<p>
 
 
-<H2>CHANGES BETWEEN VERSION 5.0.x/5.4.x and 6.0</H2>
+<h2>CHANGES BETWEEN VERSION 5.0.x/5.4.x and 6.0</h2>
 <UL>
 <LI>Devices and ps.select do not exist any more. Paper is defined by the
-<EM>paper</EM> instruction.</LI> 
-<LI><EM>vpoints</EM> are used instead of <EM>sites</EM> (points are read from vector).</LI>
-<LI><EM>vector</EM> is substituted by <EM>vpoints</EM>, <EM>vlines</EM> and <EM>vareas</EM>.</LI>
+<em>paper</em> instruction.</LI> 
+<LI><em>vpoints</em> are used instead of <em>sites</em> (points are read from vector).</LI>
+<LI><em>vector</em> is substituted by <em>vpoints</em>, <em>vlines</em> and <em>vareas</em>.</LI>
 <LI>Symbols are used instead of icons (different format and directory).</LI>
 <LI>Map legend can be printed in columns.</LI>
 </UL>
 
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 <em>
 <a href="g.region.html">g.region</a>,
 <a href="v.label.html">v.label</a>
 </em>
 
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
 
-Paul Carlson, USDA, SCS, NHQ-CGIS<BR>
+Paul Carlson, USDA, SCS, NHQ-CGIS<br>
 Modifications: Radim Blazek, Glynn Clements, Bob Covill, Hamish Bowman
 <p>
 <i>Last changed: $Date$</i>

Modified: grass/trunk/raster/r.cost/r.cost.html
===================================================================
--- grass/trunk/raster/r.cost/r.cost.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/raster/r.cost/r.cost.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -14,7 +14,7 @@
 direction to the next cell on the path back to the start point (see 
 <a href="#move">Movement Direction</a>). This program uses the current geographic region settings.
 The <b>output</b> map will be of the same data format as the <b>input</b>
-map, integer or floating point.</p>
+map, integer or floating point.
 
 <h2>OPTIONS</h2>
 
@@ -53,7 +53,7 @@
 When input map null cells are given a cost with the <b>null_cost</b>
 option, the corresponding cells in the output map are no longer null
 cells. By using the <b>-n</b> flag, the null cells of the input map are
-retained as null cells in the output map.</p>
+retained as null cells in the output map.
 
 <p>
 As <em>r.cost</em> can run for a very long time, it can be useful to 
@@ -66,7 +66,7 @@
 neighbors marked with an <tt>X</tt> are always considered for cumulative cost
 updates. With the <b>-k</b> option, the neighbors marked with a <tt>K</tt> are
 also considered. 
-</p>
+
 <div class="code"><pre>
  . . . . . . . . . . . . . . .
  .   .   . K .   . K .   .   .
@@ -157,7 +157,7 @@
 <h2>EXAMPLES</h2>
 
 <p>Consider the following example: 
-</p>
+
 <div class="code"><pre>
        Input:
          COST SURFACE
@@ -278,6 +278,6 @@
 
 <p>Updated for Grass 5<br>
 Pierre de Mouveaux (pmx at audiovu.com) 
-</p>
 
+
 <p><i>Last changed: $Date$</i>

Modified: grass/trunk/raster/r.distance/r.distance.html
===================================================================
--- grass/trunk/raster/r.distance/r.distance.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/raster/r.distance/r.distance.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -64,4 +64,4 @@
 <h2>AUTHOR</h2>
 Michael Shapiro, U.S. Army Construction Engineering Research Laboratory
 
-<p><i>Last changed: $Date$</i></p>
+<p><i>Last changed: $Date$</i>

Modified: grass/trunk/raster/r.horizon/r.horizon.html
===================================================================
--- grass/trunk/raster/r.horizon/r.horizon.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/raster/r.horizon/r.horizon.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -1,4 +1,4 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
 <B>r.horizon</B> computes the angular height of terrain horizon in
 radians. It reads a raster of elevation data and outputs the horizon
@@ -13,7 +13,7 @@
 height in a specific direction. One raster is created for each direction.
 </ul>
 
-<P>
+<p>
 The directions are given as azimuthal angles (in degrees), with
 the angle starting with 0 towards East and moving counterclockwise
 (North is 90, etc.). The calculation takes into account the actual
@@ -35,43 +35,43 @@
 
 
 <H3>Input parameters:</H3>
-<P>The <I>elevin</I> parameter is an input elevation raster map. If
+<p>The <I>elevin</I> parameter is an input elevation raster map. If
 the buffer options are used (see below), this raster should extend
 over the area that accommodate the presently defined region plus
 defined buffer zones. 
-</P>
-<P>The <I>horizonstep</I> parameter gives the angle step (in degrees)
+
+<p>The <I>horizonstep</I> parameter gives the angle step (in degrees)
 between successive azimuthal directions for the calculation of the
 horizon. Thus, a value of 5 for the <I>horizonstep</I> will give a total of
 360/5=72 directions (72 rasters if used in the raster mode). 
-</P>
-<P>The <I>direction</I> parameter gives the initial direction of the
+
+<p>The <I>direction</I> parameter gives the initial direction of the
 first output. This parameter acts as an direction angle offset. For
 example, if you want to get horizon angles for directions 45 and 225
 degrees, the <I>direction</I> should be set to 45 and <I>horizonstep</I> to
 180. If you only want one single direction, use this parameter to
 specify desired direction of horizon angle, and set the <I>horizonstep</I>
 size to 0 degrees. 
-</P>
-<P>The <I>dist </I>controls the sampling distance step size for the
+
+<p>The <I>dist </I>controls the sampling distance step size for the
 search for horizon along the line of sight. The default value is 1.0
 meaning that the step size will be taken from the raster resolution.
 Setting the value below 1.0 might slightly improve results for
 directions apart from the cardinal ones, but increasing the
 processing load of the search algorithm. 
-</P>
-<P>The <I>maxdistance</I> value gives a maximum distance to move away
+
+<p>The <I>maxdistance</I> value gives a maximum distance to move away
 from the origin along the line of sight in order to search for the
 horizon height. The smaller this value the faster the calculation but
 the higher the risk that you may miss a terrain feature that can
-contribute significantly to the horizon outline.</P>
-<P>The <I>coord</I> parameter takes a pair of easting-northing values
+contribute significantly to the horizon outline.
+<p>The <I>coord</I> parameter takes a pair of easting-northing values
 in the current coordinate system and calculates the values of angular
 height of the horizon around this point. To achieve the
 consistency of the results, the point coordinate is
 aligned to the midpoint of the closest elevation raster cell. 
-</P>
-<P>If an analyzed point (or raster cell) lies close to the edge of
+
+<p>If an analyzed point (or raster cell) lies close to the edge of
 the defined region, the horizon calculation may not be realistic,
 since it may not see some significant terrain features which could
 have contributed to the horizon, because these features are outside
@@ -83,25 +83,25 @@
 a buffer size individually for each of the four directions. The
 buffer parameters influence only size of the read elevation map,
 while the analysis in the raster mode will be done only for the
-area specified by the current region definition.</P>
-<P>The <I>horizon </I>parameter gives the prefix of the output
+area specified by the current region definition.
+<p>The <I>horizon </I>parameter gives the prefix of the output
 horizon raster maps. The raster name of each horizon direction
 raster will be constructed as <I>horizon_</I>NNN , where NNN counts
 upwards from 0 to total number of directions. If you use <B>r.horizon</B>
 in the single point mode this option will be ignored. 
-</P>
 
+
 <p>
 At the moment the elevation and maximum distance must be measured in meters, 
 even if you use geographical coordinates (longitude/latitude). If your 
 projection is based on distance (easting and northing), these too must 
 be in meters. The buffer parameters must be in the same units as the 
 raster coordinates.
-</p>
 
 
-<H2>METHOD</H2>
-<P>The calculation method is based on the method used in <B>r.sun</B>
+
+<h2>METHOD</h2>
+<p>The calculation method is based on the method used in <B>r.sun</B>
 to calculate shadows. It starts at a very shallow angle and walks
 along the line of sight and asks at each step whether the line of
 sight &quot;hits&quot; the terrain. If so, the angle is increased to
@@ -115,11 +115,11 @@
 of the Earth whereby remote features will seem to be lower than they
 actually are. It also accounts for the changes of angles towards
 cardinal directions caused by the projection (see above). 
-</P>
 
 
-<H2>EXAMPLE</H2>
 
+<h2>EXAMPLE</h2>
+
 Single point mode:
 <div class="code"><pre>
 r.horizon elevin=DEM horizonstep=30 direction=15 bufferzone=200 \
@@ -135,57 +135,57 @@
 </pre></div>
 
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
 <em>
-<A HREF="r.sun.html">r.sun</A>,
-<A HREF="r.sunmask.html">r.sunmask</A>,
-<A HREF="r.los.html">r.los</A></em>
+<a href="r.sun.html">r.sun</A>,
+<a href="r.sunmask.html">r.sunmask</A>,
+<a href="r.los.html">r.los</A></em>
 
 
-<H2>REFERENCES</H2>
-<P>Hofierka J., 1997. Direct solar radiation modelling within an
+<h2>REFERENCES</h2>
+<p>Hofierka J., 1997. Direct solar radiation modelling within an
 open GIS environment. Proceedings of JEC-GI'97 conference in Vienna,
 Austria, IOS Press Amsterdam, 575-584 
-</P>
-<P>Hofierka J., Huld T., Cebecauer T., Suri M., 2007. Open Source Solar 
+
+<p>Hofierka J., Huld T., Cebecauer T., Suri M., 2007. Open Source Solar 
 Radiation Tools for Environmental and Renewable Energy Applications,
 <a href="http://www.isess.org/papers.asp?year=2007">International Symposium on 
-Environmental Software Systems</a>, Prague, 2007</P>
-<P>Neteler M., Mitasova H., 2004. Open Source GIS: A GRASS GIS
-Approach, <A HREF="http://www.springer.com/geography/gis+cartography/book/978-0-387-35767-6">Springer</A>, New York.
+Environmental Software Systems</a>, Prague, 2007
+<p>Neteler M., Mitasova H., 2004. Open Source GIS: A GRASS GIS
+Approach, <a href="http://www.springer.com/geography/gis+cartography/book/978-0-387-35767-6">Springer</A>, New York.
 ISBN: 1-4020-8064-6, 2nd Edition 2004 (reprinted 2005), 424 pages 
-</P>
-<P>Project <A HREF="http://re.jrc.ec.europa.eu/pvgis/">PVGIS</A>, European 
-Commission, DG Joint Research Centre 2001-2007</P>
-<P>Suri M., Hofierka J., 2004.
+
+<p>Project <a href="http://re.jrc.ec.europa.eu/pvgis/">PVGIS</A>, European 
+Commission, DG Joint Research Centre 2001-2007
+<p>Suri M., Hofierka J., 2004.
 A New GIS-based Solar Radiation Model and Its Application for
-Photovoltaic Assessments. <A HREF="http://www.blackwellpublishing.com/toc.asp?ref=1361-1682">Transactions
-in GIS</A>, 8(2), 175-190</P>
+Photovoltaic Assessments. <a href="http://www.blackwellpublishing.com/toc.asp?ref=1361-1682">Transactions
+in GIS</A>, 8(2), 175-190
 
 
-<H2>AUTHORS</H2>
-<P>
+<h2>AUTHORS</h2>
+<p>
 Thomas Huld, Joint Research Centre of
 the European Commission, Ispra, Italy 
 <br>
-<P>
+<p>
 Tomas Cebecauer, Joint Research Centre
 of the European Commission, Ispra, Italy 
 <br>
-<P>
+<p>
 Jaroslav Hofierka, GeoModel s.r.o.,
-Bratislava, Slovakia <BR>Marcel Suri, Joint Research Centre of the
-European Commission, Ispra, Italy</P>
-<P>
+Bratislava, Slovakia <br>Marcel Suri, Joint Research Centre of the
+European Commission, Ispra, Italy
+<p>
 &copy; 2007, Thomas Huld, Tomas Cebecauer, Jaroslav Hofierka, Marcel Suri 
-</P>
 
-<ADDRESS STYLE="margin-bottom: 0.2in"><A HREF="mailto:Thomas.Huld at jrc.it">Thomas.Huld at jrc.it</A>
-<A HREF="mailto:Tomas.Cebecauer at jrc.it">Tomas.Cebecauer at jrc.it</A>
-<A HREF="mailto:hofi at geomodel.sk">hofierka at geomodel.sk</A>
-<A HREF="mailto:Marcel.Suri at jrc.it">Marcel.Suri at jrc.it</A> 
+
+<ADDRESS STYLE="margin-bottom: 0.2in"><a href="mailto:Thomas.Huld at jrc.it">Thomas.Huld at jrc.it</A>
+<a href="mailto:Tomas.Cebecauer at jrc.it">Tomas.Cebecauer at jrc.it</A>
+<a href="mailto:hofi at geomodel.sk">hofierka at geomodel.sk</A>
+<a href="mailto:Marcel.Suri at jrc.it">Marcel.Suri at jrc.it</A> 
 </ADDRESS>
 
-<P>
+<p>
 <I>Last changed: $Date$</I> 

Modified: grass/trunk/raster/r.in.lidar/r.in.lidar.html
===================================================================
--- grass/trunk/raster/r.in.lidar/r.in.lidar.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/raster/r.in.lidar/r.in.lidar.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -262,7 +262,7 @@
 <p>
 <i><a href="http://www.ivarch.com/programs/pv.shtml">pv</a></i>
  - The UNIX pipe viewer utility
-<BR><BR>
+<br><br>
 
 
 <h2>AUTHORS</h2>
@@ -272,4 +272,4 @@
 
 <br>
 <p>
-<i>Last changed: $Date$</i></p>
+<i>Last changed: $Date$</i>

Modified: grass/trunk/raster/r.in.xyz/r.in.xyz.html
===================================================================
--- grass/trunk/raster/r.in.xyz/r.in.xyz.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/raster/r.in.xyz/r.in.xyz.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -263,7 +263,7 @@
 <p>
 <i><a href="http://www.ivarch.com/programs/pv.shtml">pv</a></i>
  - The UNIX pipe viewer utility
-<BR><BR>
+<br><br>
 
 
 <h2>AUTHORS</h2>
@@ -278,4 +278,4 @@
 
 <br>
 <p>
-<i>Last changed: $Date$</i></p>
+<i>Last changed: $Date$</i>

Modified: grass/trunk/raster/r.lake/r.lake.html
===================================================================
--- grass/trunk/raster/r.lake/r.lake.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/raster/r.lake/r.lake.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -3,19 +3,19 @@
 <p>The module fills a lake to a target water level from a given start point. The user
 can think of it as <em>r.grow</em> with additional checks for elevation.  The resulting
 raster map contains cells with values representing lake depth and NULL for all other 
-cells beyond the lake.</p>
+cells beyond the lake.
 
 <p>This module uses a 3x3 moving window approach to find all cells that
 match three criteria and to define the lake:
-</p>
 
+
 <ul>
  <li>cells are below the specified elevation (i.e., water level);</li>
  <li>cells are connected with an initial cell (seed or E,N value);</li>
  <li>cells are not NULL or masked.</li>
 </ul>
 
-<p>The water level must be in DEM units.</p>
+<p>The water level must be in DEM units.
 
 <h2>NOTES</h2>
 <p>
@@ -26,7 +26,7 @@
 the DEM. When a raster map is used as a seed, however, no such checks are done. 
 Specifying a target water level below surface represented by DEM will result in an 
 empty map. Note: a raster lake map created in a previous run can also be used
-as a seed map for a new run to simulate rising water levels.</p>
+as a seed map for a new run to simulate rising water levels.
 
 <p>
 
@@ -35,12 +35,12 @@
 <b>-o</b> flag to create animations of rising water level without
 producing a separate map for each frame.  An initial seed map must be created 
 to start the sequence, and will be overwritten during subsequent runs with resulting
-water levels maps (i.e., a single file serves for both input and output).</p>
+water levels maps (i.e., a single file serves for both input and output).
 
 <p>
 
 Negative output (the <b>-n</b> flag) is useful for visualisations in NVIZ. 
-It equals the mapcalc's expression <em>"negative = 0 - positive"</em>.</p>
+It equals the mapcalc's expression <em>"negative = 0 - positive"</em>.
 
 <h3>MAPCALC EQUIVALENT - FOR GRASS HACKERS</h3>
 
@@ -67,7 +67,7 @@
 The ${seedmap} variable is replaced by seed map names, ${dem} with DEM map name, and
 ${wlevel} with target water level.  To get single water level, this code block is
 called with same level numerous times (in a loop) as the lake grows by single cells
-during single run.</p>
+during single run.
 
 <h2>BUGS/KNOWN ISSUES</h2>
 
@@ -87,4 +87,4 @@
 <h2>AUTHOR</h2>
 Maris Nartiss (maris.nartiss gmail.com)
 
-<p><i>Last changed: $Date$</i></p>
+<p><i>Last changed: $Date$</i>

Modified: grass/trunk/raster/r.le/r.le.patch/r.le.patch.html
===================================================================
--- grass/trunk/raster/r.le/r.le.patch/r.le.patch.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/raster/r.le/r.le.patch/r.le.patch.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -18,7 +18,7 @@
 landscape structure using the GRASS geographical information system.
 Landscape Ecology 7(4):291-302.
 <p>
-The <A href="http://grass.osgeo.org/gdp/landscape/r_le_manual5.pdf"><i>r.le</i>
+The <a href="http://grass.osgeo.org/gdp/landscape/r_le_manual5.pdf"><i>r.le</i>
 manual: Quantitative analysis of landscape structures</a> (GRASS 5; 2001)
 
 <h2>SEE ALSO</h2>

Modified: grass/trunk/raster/r.le/r.le.pixel/r.le.pixel.html
===================================================================
--- grass/trunk/raster/r.le/r.le.pixel/r.le.pixel.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/raster/r.le/r.le.pixel/r.le.pixel.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -17,7 +17,7 @@
 landscape structure using the GRASS geographical information system.
 Landscape Ecology 7(4):291-302.
 <p>
-The <A href="http://grass.osgeo.org/gdp/landscape/r_le_manual5.pdf"><i>r.le</i>
+The <a href="http://grass.osgeo.org/gdp/landscape/r_le_manual5.pdf"><i>r.le</i>
 manual: Quantitative analysis of landscape structures</a> (GRASS 5; 2001)
 
 <h2>SEE ALSO</h2>

Modified: grass/trunk/raster/r.le/r.le.setup/r.le.setup.html
===================================================================
--- grass/trunk/raster/r.le/r.le.setup/r.le.setup.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/raster/r.le/r.le.setup/r.le.setup.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -449,7 +449,7 @@
 landscape structure using the GRASS geographical information system.
 Landscape Ecology 7(4):291-302.
 <p>
-The <A href="http://grass.osgeo.org/gdp/landscape/r_le_manual5.pdf"><i>r.le</i>
+The <a href="http://grass.osgeo.org/gdp/landscape/r_le_manual5.pdf"><i>r.le</i>
 manual: Quantitative analysis of landscape structures</a> (GRASS 5; 2001)
 
 

Modified: grass/trunk/raster/r.le/r.le.trace/r.le.trace.html
===================================================================
--- grass/trunk/raster/r.le/r.le.trace/r.le.trace.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/raster/r.le/r.le.trace/r.le.trace.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -19,7 +19,7 @@
 landscape structure using the GRASS geographical information system.
 Landscape Ecology 7(4):291-302.
 <p>
-The <A href="http://grass.osgeo.org/gdp/landscape/r_le_manual5.pdf"><i>r.le</i>
+The <a href="http://grass.osgeo.org/gdp/landscape/r_le_manual5.pdf"><i>r.le</i>
 manual: Quantitative analysis of landscape structures</a> (GRASS 5; 2001)
 
 

Modified: grass/trunk/raster/r.li/r.li.cwed/r.li.cwed.html
===================================================================
--- grass/trunk/raster/r.li/r.li.cwed/r.li.cwed.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/raster/r.li/r.li.cwed/r.li.cwed.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -1,65 +1,65 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
-<EM>r.li.cwed</EM> (contrast weighted edge density) calculates the edge density
+<em>r.li.cwed</em> (contrast weighted edge density) calculates the edge density
 between patch types specified:
-<P><img src="rlicwed_formula.png"> </P>
-<P>with:
+<p><img src="rlicwed_formula.png"> 
+<p>with:
 
 <ul>
-<li> <B>k</B>: attribute<BR>
-<li> <B>m</B>: number of non-null attributes in the sampling area<BR>
-<li> <B>e<small><small>ik</small></small></B>: total length of edge in landscape between patch types i and k<BR>
-<li><B> d<small><small>ik</small></small></B>: dissimilarity (edge contrast weight) between patch types i and k<BR>
-<li> <B>Area</B>: total landscape area<BR>
-</ul><BR>
+<li> <B>k</B>: attribute<br>
+<li> <B>m</B>: number of non-null attributes in the sampling area<br>
+<li> <B>e<small><small>ik</small></small></B>: total length of edge in landscape between patch types i and k<br>
+<li><B> d<small><small>ik</small></small></B>: dissimilarity (edge contrast weight) between patch types i and k<br>
+<li> <B>Area</B>: total landscape area<br>
+</ul><br>
 
 The input file have a row for each couple of patch type that we want to
-consider in the calculation. Each row must to have this syntax:<BR>
-<small>patchType1,patchType2,dissimilarityBetweenPatchType1andPatchType2</small><BR>
+consider in the calculation. Each row must to have this syntax:<br>
+<small>patchType1,patchType2,dissimilarityBetweenPatchType1andPatchType2</small><br>
 
-<H2>EXAMPLES</H2>
+<h2>EXAMPLES</h2>
 To calculate mean pixel attribute index on map my_map, using
 my_conf configuration file and saving results in
-my_out file run:<BR>
+my_out file run:<br>
 <div class="code"><pre>
 r.li.cwed input=my_map conf=my_conf path=my_file output=my_out
 </pre></div>
 
-<BR>Example of input file:<BR>
-12,16,0.65<BR>
-44,123,0.32<BR>
-56,12,0.54<BR>
-23,66,0.99<BR>
+<br>Example of input file:<br>
+12,16,0.65<br>
+44,123,0.32<br>
+56,12,0.54<br>
+23,66,0.99<br>
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 Do not use absolute path names for output files. They are raster if
 moving window disposition was selected, otherwise they are in
 ~/.r.li/output folder.
-<BR>
+<br>
 If the raster is full of null value it is considered to have 0 patch and CWED=0.
 If Area is 0 r.li.cwed returns -1. This is possible
-only if the map is masked.<BR>
-If you want to have null values instead run <BR>
+only if the map is masked.<br>
+If you want to have null values instead run <br>
 <div class="code"><pre>
 r.null setnull=-1 map=my_map
 </pre></div>
-after index calculation.<BR>
-<BR>
+after index calculation.<br>
+<br>
 
-<H2>REFERENCES</H2>
+<h2>REFERENCES</h2>
 McGarigal, K., and B. J. Marks. 1995. FRAGSTATS: spatial pattern
 analysis program for quantifying landscape structure. USDA For. Serv.
 Gen. Tech. Rep. PNW-351.
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
-<EM><A HREF="r.li.html">r.li</A></EM> package overview <BR>
-<EM><A HREF="r.li.daemon.html">r.li.daemon</A></EM><BR>
-<EM><A HREF="r.li.setup.html">r.li.setup</A></EM>
+<em><a href="r.li.html">r.li</A></em> package overview <br>
+<em><a href="r.li.daemon.html">r.li.daemon</A></em><br>
+<em><a href="r.li.setup.html">r.li.setup</A></em>
 
-<H2>AUTHORS</H2>
-Serena Pallecchi student of Computer Science University of Pisa (Italy).<BR>
+<h2>AUTHORS</h2>
+Serena Pallecchi student of Computer Science University of Pisa (Italy).<br>
 Commission from Faunalia Pontedera (PI), Italy (www.faunalia.it)
 
-<p><i>Last changed: $Date$</i></p>
+<p><i>Last changed: $Date$</i>
 

Modified: grass/trunk/raster/r.li/r.li.daemon/r.li.daemon.html
===================================================================
--- grass/trunk/raster/r.li/r.li.daemon/r.li.daemon.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/raster/r.li/r.li.daemon/r.li.daemon.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -9,12 +9,12 @@
 
 <img src="grass_logo.png" alt="GRASS logo"><hr align=center size=6 noshade>
 
-<H2>NAME</H2>
-<EM><B>libgrass_rli</B></EM> - r.li landscape index support library
+<h2>NAME</h2>
+<em><B>libgrass_rli</B></em> - r.li landscape index support library
 
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
-<EM>r.li.daemon</EM> provides support for landscape index calculations on raster
+<em>r.li.daemon</em> provides support for landscape index calculations on raster
 maps. It hides the managment of areas, defined using <a href="r.li.setup.html">r.li.setup</a>
 command. It is not used like a standalone program, but its functions are 
 a library used by all <em>r.li.[index]</em> commands.<br>
@@ -56,7 +56,7 @@
 </ol>
 Compile it using a changed Makefile based on the file for <em>r.li.patchdensity</em>.
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 Using GRASS library function to access raster rows can slow down moving windows 
 execution. It is recommended to use 
 <br><div class="code"><pre>
@@ -67,14 +67,14 @@
 to use an ad hoc build memory managment developed to speed up the system.
 The documentation is in doxygen files.
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
-<EM><A HREF="http://grass.osgeo.org/gdp/landscape/r_le_manual5.pdf">old r.le manual</A></EM><BR>
-<EM><A HREF="r.li.html">r.li</A></EM> package overview <BR>
-<EM><A HREF="r.li.patchdensity.html">r.li.patchdensity</A></EM>,
-<EM><A HREF="r.li.setup.html">r.li.setup</A></EM>
+<em><a href="http://grass.osgeo.org/gdp/landscape/r_le_manual5.pdf">old r.le manual</A></em><br>
+<em><a href="r.li.html">r.li</A></em> package overview <br>
+<em><a href="r.li.patchdensity.html">r.li.patchdensity</A></em>,
+<em><a href="r.li.setup.html">r.li.setup</A></em>
 
-<H2>AUTHORS</H2>
+<h2>AUTHORS</h2>
 Claudio Porta and Lucio Davide Spano, students of Computer Science 
 University of Pisa (Italy).<br>
 Commission from Faunalia Pontedera (PI)<br>
@@ -86,6 +86,6 @@
 <i>Last changed: $Date$</i>
 
 <HR>
-<P><a href="index.html">Main index</a> - <a href="raster.html">raster index</a> - <a href="full_index.html">Full index</a>
+<p><a href="index.html">Main index</a> - <a href="raster.html">raster index</a> - <a href="full_index.html">Full index</a>
 </body>
 </html>

Modified: grass/trunk/raster/r.li/r.li.dominance/r.li.dominance.html
===================================================================
--- grass/trunk/raster/r.li/r.li.dominance/r.li.dominance.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/raster/r.li/r.li.dominance/r.li.dominance.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -38,4 +38,4 @@
 Serena Pallecchi student of Computer Science University of Pisa (Italy).<br>
 Commission from Faunalia Pontedera (PI), Italy (www.faunalia.it)
 
-<p><i>Last changed: $Date$</i></p>
+<p><i>Last changed: $Date$</i>

Modified: grass/trunk/raster/r.li/r.li.edgedensity/r.li.edgedensity.html
===================================================================
--- grass/trunk/raster/r.li/r.li.edgedensity/r.li.edgedensity.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/raster/r.li/r.li.edgedensity/r.li.edgedensity.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -8,13 +8,13 @@
 	or<br><br></li>
    <li> the density of all the edge in the sampling area if i isn't specified<br>
 	<img src="rliEdgeDensity_formula2.png"><br></li></ul>
-<p>with:</p>
+<p>with:
 <ul>
   <li><b>k</b>: patch type<br></li>
   <li><b>m</b>: number of patch type<br> </li>
   <li><b>n</b>: number of edge segment of patch type k</li>
   <li><b>e<small><small>ik </small></small></b>:total length of edge in landscape involving patch type k</li>
-  <li> <B>Area</B>: total landscape area<BR>
+  <li> <B>Area</B>: total landscape area<br>
 </ul>
 
 <h2>REFERENCES</h2>

Modified: grass/trunk/raster/r.li/r.li.padrange/r.li.padrange.html
===================================================================
--- grass/trunk/raster/r.li/r.li.padrange/r.li.padrange.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/raster/r.li/r.li.padrange/r.li.padrange.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -47,5 +47,5 @@
 Serena Pallecchi student of Computer Science University of Pisa (Italy).<br>
 Commission from Faunalia Pontedera (PI), Italy (www.faunalia.it)
 
-<p><i>Last changed: $Date$</i></p>
+<p><i>Last changed: $Date$</i>
 

Modified: grass/trunk/raster/r.li/r.li.padsd/r.li.padsd.html
===================================================================
--- grass/trunk/raster/r.li/r.li.padsd/r.li.padsd.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/raster/r.li/r.li.padsd/r.li.padsd.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -43,4 +43,4 @@
 Serena Pallecchi student of Computer Science University of Pisa (Italy).<br>
 Commission from Faunalia Pontedera (PI), Italy (www.faunalia.it)
 
-<p><i>Last changed: $Date$</i></p>
+<p><i>Last changed: $Date$</i>

Modified: grass/trunk/raster/r.li/r.li.patchdensity/r.li.patchdensity.html
===================================================================
--- grass/trunk/raster/r.li/r.li.patchdensity/r.li.patchdensity.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/raster/r.li/r.li.patchdensity/r.li.patchdensity.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -1,5 +1,5 @@
-<H2>DESCRIPTION</H2>
-<EM>r.li.patchdensity</EM> is a patch index for <em>r.li</em> suite.
+<h2>DESCRIPTION</h2>
+<em>r.li.patchdensity</em> is a patch index for <em>r.li</em> suite.
 It calculates the function:
 
 <div class="code"><pre>
@@ -9,7 +9,7 @@
 that is 1000000 by number of patch for area unit.
 This index is calculated using a 4 neighbour algorithm.
 
-<H2>EXAMPLES</H2>
+<h2>EXAMPLES</h2>
 To calculate patch density index on map <em>my_map</em>, using <em>my_conf</em>
 configuration file (previously defined with <em>r.li.setup</em>) and saving
 results in the raster map <em>my_out</em>, run:
@@ -34,7 +34,7 @@
 d.vect forests type=boundary
 </pre></div>
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 
 A map of NULL values is considered to have zero patches. <br>
 If you want to have null values instead run <br>
@@ -46,12 +46,12 @@
 If raster area is 0, <em>r.li.patchdensity</em> returns -1. This is only possible
 if the raster is masked.
 
-<H2>SEE ALSO</H2>
-<EM><A HREF="r.li.html">r.li</A></EM> package overview <BR>
-<EM><A HREF="r.li.daemon.html">r.li.daemon</A></EM><BR>
-<EM><A HREF="r.li.setup.html">r.li.setup</A></EM>
+<h2>SEE ALSO</h2>
+<em><a href="r.li.html">r.li</A></em> package overview <br>
+<em><a href="r.li.daemon.html">r.li.daemon</A></em><br>
+<em><a href="r.li.setup.html">r.li.setup</A></em>
 
-<H2>AUTHORS</H2>
+<h2>AUTHORS</h2>
 Claudio Porta and Lucio Davide Spano, students of Computer Science 
 University of Pisa (Italy).<br>
 Commission from Faunalia Pontedera (PI) (www.faunalia.it)<br>

Modified: grass/trunk/raster/r.li/r.li.patchnum/r.li.patchnum.html
===================================================================
--- grass/trunk/raster/r.li/r.li.patchnum/r.li.patchnum.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/raster/r.li/r.li.patchnum/r.li.patchnum.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -1,10 +1,10 @@
-<H2>DESCRIPTION</H2>
-<EM>r.li.patchnum</EM> is a patch index for r.li program.<br>
+<h2>DESCRIPTION</h2>
+<em>r.li.patchnum</em> is a patch index for r.li program.<br>
 It calculates the function <br>
 <I> f(sample_area)= Patch_Number </I><br>
 This index is calculated using a 4 neighbour algorithm<br>
 
-<H2>EXAMPLES</H2>
+<h2>EXAMPLES</h2>
 To calculate patch number index on map my_map, using 
 <em>my_conf</em> configuration file and saving results in
 my_out file run:
@@ -12,7 +12,7 @@
 r.li.patchnumber input=my_map conf=my_conf out=my_out
 </pre></div>
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 
 An that is full of null values is considered to have zero patch. <br>
 If you want to have null values instead run <br>
@@ -21,12 +21,12 @@
 </pre></div>
 after index calculation.<br>
 
-<H2>SEE ALSO</H2>
-<EM><A HREF="r.li.html">r.li</A></EM> package overview <BR>
-<EM><A HREF="r.li.daemon.html">r.li.daemon</A></EM><BR>
-<EM><A HREF="r.li.setup.html">r.li.setup</A></EM>
+<h2>SEE ALSO</h2>
+<em><a href="r.li.html">r.li</A></em> package overview <br>
+<em><a href="r.li.daemon.html">r.li.daemon</A></em><br>
+<em><a href="r.li.setup.html">r.li.setup</A></em>
 
-<H2>AUTHORS</H2>
+<h2>AUTHORS</h2>
 Claudio Porta and Lucio Davide Spano, students of Computer Science 
 University of Pisa (Italy).<br>
 Commission from Faunalia Pontedera (PI) (www.faunalia.it)<br>

Modified: grass/trunk/raster/r.li/r.li.richness/r.li.richness.html
===================================================================
--- grass/trunk/raster/r.li/r.li.richness/r.li.richness.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/raster/r.li/r.li.richness/r.li.richness.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -36,5 +36,5 @@
 Serena Pallecchi student of Computer Science University of Pisa (Italy).<br>
 Commission from Faunalia Pontedera (PI), Italy (www.faunalia.it)
 
-<p><i>Last changed: $Date$</i></p>
+<p><i>Last changed: $Date$</i>
 

Modified: grass/trunk/raster/r.li/r.li.setup/r.li.setup.html
===================================================================
--- grass/trunk/raster/r.li/r.li.setup/r.li.setup.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/raster/r.li/r.li.setup/r.li.setup.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -1,6 +1,6 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
-<EM>r.li.setup</EM>  creates and shows configuration files for the 
+<em>r.li.setup</em>  creates and shows configuration files for the 
 others r.li programs. For a general introduction, see 
 <a href="r.li.html">r.li</a>.
 <br>
@@ -132,18 +132,18 @@
 <li><em><b>Close</b></em> module window.
 </ol>
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 Configuration files are raster map independent because areas are saved using 
 relative coordinates.
 
-<H2>SEE ALSO</H2>
-<EM><A HREF="http://grass.osgeo.org/gdp/landscape/r_le_manual5.pdf">
-old r.le manual</A></EM><BR>
-<EM><A HREF="r.li.html">r.li</A></EM> package overview <BR>
-<EM><A HREF="r.li.daemon.html">r.li.daemon</A></EM>,
-<EM><A HREF="r.li.patchdensity.html">r.li.patchdensity</A></EM>
+<h2>SEE ALSO</h2>
+<em><a href="http://grass.osgeo.org/gdp/landscape/r_le_manual5.pdf">
+old r.le manual</A></em><br>
+<em><a href="r.li.html">r.li</A></em> package overview <br>
+<em><a href="r.li.daemon.html">r.li.daemon</A></em>,
+<em><a href="r.li.patchdensity.html">r.li.patchdensity</A></em>
 
-<H2>AUTHORS</H2>
+<h2>AUTHORS</h2>
 Claudio Porta and Lucio Davide Spano, students of Computer Science 
 University of Pisa (Italy).<br>
 Commission from Faunalia Pontedera (PI)<br>

Modified: grass/trunk/raster/r.li/r.li.shape/r.li.shape.html
===================================================================
--- grass/trunk/raster/r.li/r.li.shape/r.li.shape.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/raster/r.li/r.li.shape/r.li.shape.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -1,9 +1,9 @@
-<H2>DESCRIPTION</H2>
-<EM>r.li.shape</EM> is a patch index for r.li program.<br>
+<h2>DESCRIPTION</h2>
+<em>r.li.shape</em> is a patch index for r.li program.<br>
 It calculates the function <br>
 <I> f(sample_area)= Area </I><br>
 
-<H2>EXAMPLES</H2>
+<h2>EXAMPLES</h2>
 To calculate area index on map my_map, using 
 <em>my_conf</em> configuration file and saving results in
 my_out file run:
@@ -11,12 +11,12 @@
 r.li.shape input=my_map conf=my_conf out=my_out
 </pre></div>
 
-<H2>SEE ALSO</H2>
-<EM><A HREF="r.li.html">r.li</A></EM> package overview <BR>
-<EM><A HREF="r.li.daemon.html">r.li.daemon</A></EM><BR>
-<EM><A HREF="r.li.setup.html">r.li.setup</A></EM>
+<h2>SEE ALSO</h2>
+<em><a href="r.li.html">r.li</A></em> package overview <br>
+<em><a href="r.li.daemon.html">r.li.daemon</A></em><br>
+<em><a href="r.li.setup.html">r.li.setup</A></em>
 
-<H2>AUTHORS</H2>
+<h2>AUTHORS</h2>
 Claudio Porta and Lucio Davide Spano, students of Computer Science 
 University of Pisa (Italy).<br>
 Commission from Faunalia Pontedera (PI) (www.faunalia.it)<br>

Modified: grass/trunk/raster/r.mfilter/r.mfilter.html
===================================================================
--- grass/trunk/raster/r.mfilter/r.mfilter.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/raster/r.mfilter/r.mfilter.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -84,8 +84,8 @@
 More than one filter may be specified in the filter file.
 The additional filter(s) are described just like the first.
 For example, the following describes two filters:
-</p>
 
+
 </dl>
 
 

Modified: grass/trunk/raster/r.out.png/r.out.png.html
===================================================================
--- grass/trunk/raster/r.out.png/r.out.png.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/raster/r.out.png/r.out.png.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -23,7 +23,7 @@
 
 <h2>AUTHORS</h2>
 
-Alex Shevlakov<BR>
+Alex Shevlakov<br>
 Hamish Bowman
 
 <p>

Modified: grass/trunk/raster/r.out.ppm3/r.out.ppm3.html
===================================================================
--- grass/trunk/raster/r.out.ppm3/r.out.ppm3.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/raster/r.out.ppm3/r.out.ppm3.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -14,7 +14,7 @@
 g.region rast=[mapname]
 </pre></div>
 
-<p>before running <em>r.out.ppm3</em>.</p>
+<p>before running <em>r.out.ppm3</em>.
 
 <h2>NOTES</h2>
 

Modified: grass/trunk/raster/r.out.tiff/r.out.tiff.html
===================================================================
--- grass/trunk/raster/r.out.tiff/r.out.tiff.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/raster/r.out.tiff/r.out.tiff.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -2,29 +2,29 @@
 
 <p>This program converts a GRASS raster map to a TIFF raster map. Output may
 be 8 or 24 bit (TrueColor).  Optionally, a TIFF World file compatible with
-ESRI's and other's products may be output.</p>
+ESRI's and other's products may be output.
 
 <p>
 The program prompts the user for the name of a GRASS raster map, an output
 TIFF file, whether an 8 or 24 bit format is desired, and whether or not to
 create a TIFF world file.  Currently only uncompressed, packpit, or deflate
 TIFF files are written.  These output formats are known to be compatible
-with r.in.tiff.</p>
+with r.in.tiff.
 
 <p>
 The output filename will always have the suffix <code>.tif</code>, and the Tiff World
 file (if requested) <code>.tfw</code>. Any <code>.tif</code> or
 <code>.tiff</code> suffix (case insensitive) specified in the output filename 
-will be discarded.</p>
+will be discarded.
 
 <p>
 When writing with "-l" option, tiles are written at 128x128 pixels.  For
 programs that can utilize tiles, it can help speed up some drawing
-operations.</p>
+operations.
 
 <p>
 The user may adjust region and resolution before export using
-<a href="g.region.html">g.region</a>.</p>
+<a href="g.region.html">g.region</a>.
 
 <p>
 A better choice to export GRASS raster data might be

Modified: grass/trunk/raster/r.patch/r.patch.html
===================================================================
--- grass/trunk/raster/r.patch/r.patch.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/raster/r.patch/r.patch.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -112,4 +112,4 @@
 <br>
 -z flag by Huidae Cho
 
-<p><i>Last changed: $Date$</i></p>
+<p><i>Last changed: $Date$</i>

Modified: grass/trunk/raster/r.region/r.region.html
===================================================================
--- grass/trunk/raster/r.region/r.region.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/raster/r.region/r.region.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -21,7 +21,7 @@
 settings are recomputed from the boundaries and the number of rows and
 columns in the raster map.
 
-<P>
+<p>
 The n=<em>value</em> may also be specified as a
 function of its current value:  n=n+<em>value</em>
 increases the current northing, while n=n-<em>value</em>

Modified: grass/trunk/raster/r.regression.line/r.regression.line.html
===================================================================
--- grass/trunk/raster/r.regression.line/r.regression.line.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/raster/r.regression.line/r.regression.line.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -1,6 +1,6 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
-<EM>r.regression.line</EM> Calculates linear regression from two raster maps, 
+<em>r.regression.line</em> Calculates linear regression from two raster maps, 
 according to the formula y = a + b*x, where x and y represent raster maps. 
 Optionally saves regression coefficients to an ASCII file. 
 The result includes the following coefficients:
@@ -9,11 +9,11 @@
 (sdX, sdY), and the F test for testing the significance of the
 regression model as a whole (F).
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 The results for offset/intercept (a) and gain/slope (b) are 
 identical to that obtained from R-stats's lm() function. 
 
-<H2>EXAMPLE</H2>
+<h2>EXAMPLE</h2>
 
 Comparison of the old and the new DEM in Spearfish:
 <div class="code"><pre>
@@ -38,11 +38,11 @@
 </pre></div>
 
 
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
 
-Dr. Agustin Lobo - alobo at ija.csic.es<BR>
-Updated to GRASS 5.7 Michael Barton, Arizona State University<BR>
-Script style output Markus Neteler<BR>
+Dr. Agustin Lobo - alobo at ija.csic.es<br>
+Updated to GRASS 5.7 Michael Barton, Arizona State University<br>
+Script style output Markus Neteler<br>
 Conversion to C module Markus Metz
 
 <p><i>Last changed: $Date$</i>

Modified: grass/trunk/raster/r.resamp.filter/r.resamp.filter.html
===================================================================
--- grass/trunk/raster/r.resamp.filter/r.resamp.filter.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/raster/r.resamp.filter/r.resamp.filter.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -3,41 +3,41 @@
 <p>
 <em>r.resamp.filter</em> resamples an input raster, filtering the
 input with an analytic kernel.
-</p>
+
 <p>
 All of the kernels specified by the filter= option are multiplied
 together. Typical usage will use either a single kernel or an infinite
 kernel along with a finite window.
-</p>
 
+
 <h2>NOTES</h2>
 
 <p>
 Resampling modules (<em>r.resample, r.resamp.stats, r.resamp.interp,
 r.resamp.rst, r.resamp.filter</em>) resample the map to match the
 current region settings.
-</p>
+
  
 <p>
 When using a kernel which can have negative values (sinc, Lanczos),
 the <em>-n</em> flag should be used. Otherwise, extreme values can
 arise due to the total weight being close (or even equal) to zero.
-</p>
+
  
 <p>
 Kernels with infinite extent (Gauss, normal, sinc, Hann, Hamming,
 Blackman) must be used in conjunction with a finite windowing function
 (box, Bartlett, Hermite, Lanczos)
-</p>
 
+
 <p>
 For longitude-latitude locations, the interpolation algorithm is based on
 degree fractions, not on the absolute distances between cell centers.  Any
 attempt to implement the latter would violate the integrity of the
 interpolation method.
-</p>
 
 
+
 <h2>SEE ALSO</h2>
 
 <em><a href="g.region.html">g.region</a></em>,

Modified: grass/trunk/raster/r.resamp.interp/r.resamp.interp.html
===================================================================
--- grass/trunk/raster/r.resamp.interp/r.resamp.interp.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/raster/r.resamp.interp/r.resamp.interp.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -18,30 +18,30 @@
 This module is intended for reinterpolation of continuous data
 to a different resolution rather than for interpolation from scattered data
 (use the <em>v.surf.*</em> modules for that purpose).
-</p>
 
 
+
 <h2>NOTES</h2>
 
 <p>
 Resampling modules (<em>r.resample, r.resamp.stats, r.resamp.interp,
 r.resamp.rst</em>) resample the map to match the current region settings.
-</p>
+
  
 <p>
 Note that for bilinear, bicubic and lanczos interpolation,
 cells of the output raster that cannot be bounded by the appropriate number
 of input cell centers are set to NULL (NULL propagation). This could occur
 due to the input cells being outside the current region, being NULL or MASKed.
-</p>
 
+
 <p>
 For longitude-latitude locations, the interpolation algorithm is based on
 degree fractions, not on the absolute distances between cell centers.  Any
 attempt to implement the latter would violate the integrity of the
 interpolation method.
-</p>
 
+
 <h2>EXAMPLE</h2>
 
 Resample elevation raster map to a higher resolution (from 500m to 250m;

Modified: grass/trunk/raster/r.resamp.stats/r.resamp.stats.html
===================================================================
--- grass/trunk/raster/r.resamp.stats/r.resamp.stats.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/raster/r.resamp.stats/r.resamp.stats.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -3,26 +3,26 @@
 <p>
 <em>r.resamp.stats</em> fills a grid cell (raster) matrix with
 aggregated values generated from a set of input layer data points.
-</p>
 
+
 <p>
 Without the <em>-w</em> switch, the aggregate is computed over all of
 the input cells whose centers lie within the output cell.
-</p>
+
 <p>
 With the <em>-w</em> switch, the aggregate uses the values from all
 input cells which intersect the output cell, weighted according to the
 proportion of the source cell which lies inside the output cell. This
 is slower, but produces a more accurate result.
-</p>
 
 
+
 <h2>NOTES</h2>
 
 <p>
 Resampling modules (<em>r.resample, r.resamp.stats, r.resamp.interp,
 r.resamp.rst</em>) resample the map to match the current region settings.
-</p>
+
 <p>
 The notion of weighting doesn't make any sense for the min and max
 aggregates. However, the <em>-w</em> flag still has significance in
@@ -35,8 +35,8 @@
 <p>
 Resample elevation raster map to a lower resolution (from 6m to 20m;
 North Carolina sample dataset):
-</p>
 
+
 <div class="code"><pre>
 g.region rast=el_D782_6m -p
 g.region res=20 -ap

Modified: grass/trunk/raster/r.ros/r.ros.html
===================================================================
--- grass/trunk/raster/r.ros/r.ros.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/raster/r.ros/r.ros.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -83,7 +83,7 @@
 
 <h3>OPTIONS</h3>
 
-<P>If the options <b>moisture_1h</b>, <b>moisture_10h</b>, and
+<p>If the options <b>moisture_1h</b>, <b>moisture_10h</b>, and
 <b>moisture_100h</b> are partially given, the program will assign
 values to the missing option using the formula:
 

Modified: grass/trunk/raster/r.slope.aspect/r.slope.aspect.html
===================================================================
--- grass/trunk/raster/r.slope.aspect/r.slope.aspect.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/raster/r.slope.aspect/r.slope.aspect.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -38,9 +38,9 @@
   <td>
   <center>
     <img src="dem.png" border="1">
-    <P>
+    <p>
     Example DEM
-    <BR><BR>
+    <br><br>
   </center>
   </td>
   <td>
@@ -51,17 +51,17 @@
   <td>
   <center>
     <img src="slope.png" border="1">
-    <P>
+    <p>
     Slope (degree) from example DEM
-    <BR><BR>
+    <br><br>
   </center>
   </td>
   <td>
   <center>
     <img src="aspect.png" border="1">
-    <P>
+    <p>
     Aspect (degree) from example DEM
-    <BR><BR>
+    <br><br>
   </center>
   </td>
  </tr>
@@ -70,17 +70,17 @@
   <td>
   <center>
     <img src="tcurv.png" border="1">
-    <P>
+    <p>
     Tangential curvature (m<sup>-1</sup>) from example DEM
-    <BR><BR>
+    <br><br>
   </center>
   </td>
   <td>
   <center>
     <img src="pcurv.png" border="1">
-    <P>
+    <p>
     Profile curvature (m<sup>-1</sup>) from example DEM
-    <BR><BR>
+    <br><br>
   </center>
   </td>
   <td>
@@ -176,7 +176,7 @@
 <em><a href="r.rescale.html">r.rescale</a></em>
 
 <h2>AUTHORS</h2>
-Michael Shapiro, U.S.Army Construction Engineering Research Laboratory<BR>
+Michael Shapiro, U.S.Army Construction Engineering Research Laboratory<br>
 Olga Waupotitsch, U.S.Army Construction Engineering Research Laboratory
 
 <p>

Modified: grass/trunk/raster/r.solute.transport/r.solute.transport.html
===================================================================
--- grass/trunk/raster/r.solute.transport/r.solute.transport.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/raster/r.solute.transport/r.solute.transport.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -1,4 +1,4 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 This numerical program calculates numerical implicit transient and steady state
 solute transport in porous media in the saturated zone of an aquifer. The computation is based on
 raster maps and the current region settings. All initial- and boundary-conditions must be provided as
@@ -15,7 +15,7 @@
 with r.out.vtk.
 <br>
 <br>
-Use <A HREF="r.gwflow.html">r.gwflow</A> to compute the piezometric heights
+Use <a href="r.gwflow.html">r.gwflow</A> to compute the piezometric heights
 of the aquifer. The piezometric heights and the hydraulic conductivity
 are used to compute the flow direction and the mean velocity of the groundwater.
 This is the base of the solute transport computation.
@@ -31,7 +31,7 @@
 the finite volume discretization, you can use small time steps and choose between full
 and exponential upwinding.
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 The solute transport calculation is based on a diffusion/convection partial differential equation and
 a numerical implicit finite volume discretization. Specific for this kind of differential
 equation is the combination of a diffusion/dispersion term and a convection term.
@@ -84,7 +84,7 @@
 (maps of size 10.000 cells will need more than one gigabyte of ram).
 Always prefer a sparse matrix solver.
 
-<H2>EXAMPLE</H2>
+<h2>EXAMPLE</h2>
 Use this small python script to create a working
 groundwater flow / solute transport area and data. 
 Make sure you are not in a lat/lon projection.
@@ -145,11 +145,11 @@
 
 </pre></div>
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
-<EM><A HREF="r.gwflow.html">r.gwflow</A></EM><br>
-<EM><A HREF="r3.gwflow.html">r3.gwflow</A></EM><br>
-<EM><A HREF="r.out.vtk.html">r.out.vtk</A></EM><br>
+<em><a href="r.gwflow.html">r.gwflow</A></em><br>
+<em><a href="r3.gwflow.html">r3.gwflow</A></em><br>
+<em><a href="r.out.vtk.html">r.out.vtk</A></em><br>
 
 <h2>AUTHOR</h2>
 S&ouml;ren Gebbert

Modified: grass/trunk/raster/r.spread/r.spread.html
===================================================================
--- grass/trunk/raster/r.spread/r.spread.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/raster/r.spread/r.spread.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -1,23 +1,23 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
 Spread phenomena usually show uneven movement over space. Such unevenness
 is due to two reasons:
-<BR>1) the uneven conditions from location to location, which can be called
+<br>1) the uneven conditions from location to location, which can be called
 SPATIAL HETEROGENEITY, and
-<BR>2) the uneven conditions in different directions, which can be called
+<br>2) the uneven conditions in different directions, which can be called
 ANISOTROPY.
-<BR>The anisotropy of spread occurs when any of the determining factors
+<br>The anisotropy of spread occurs when any of the determining factors
 have directional components. For example, wind and topography cause anisotropic
 spread of wildfires.
 
-<P>One of the simplest spatial heterogeneous and anisotropic spread
+<p>One of the simplest spatial heterogeneous and anisotropic spread
 is elliptical spread, in which, each local spread shape can be thought
 as an ellipse. In a raster setting, cell centers are foci of the spread
 ellipses, and the spread phenomenon moves fastest toward apogees and slowest
 to perigees. The sizes and shapes of spread ellipses may vary cell by cell.
 So the overall spread shape is commonly not an ellipse.
 
-<P><I>r.spread </I>simulates elliptically anisotropic spread phenomena,
+<p><I>r.spread </I>simulates elliptically anisotropic spread phenomena,
 given three raster map layers about ROS (base ROS, maximum ROS and direction
 of the maximum ROS) plus a raster map layer showing the starting sources.
 These ROS layers define unique ellipses for all cell locations in the current
@@ -26,17 +26,17 @@
 GRASS raster program r.ros. The actual locations reached by a spread event
 are constrained by the actual spread origins and the elapsed spread time.
 
-<P><I>r.spread </I>optionally produces raster maps to contain backlink
+<p><I>r.spread </I>optionally produces raster maps to contain backlink
 UTM coordinates for each raster cell of the spread time map. The spread
 paths can be accurately traced based on the backlink information by another
 GRASS raster program r.spreadpath.
 
-<P>Part of the spotting function in r.spread is based on Chase (1984)
-and Rothermel (1983). More information on <I>r.spread</I>, <I><A HREF="r.ros.html">r.ros</A></I>
-and <I><A HREF="r.spreadpath.html">r.spreadpath</A></I> can be found in
+<p>Part of the spotting function in r.spread is based on Chase (1984)
+and Rothermel (1983). More information on <I>r.spread</I>, <I><a href="r.ros.html">r.ros</A></I>
+and <I><a href="r.spreadpath.html">r.spreadpath</A></I> can be found in
 Xu (1994).
 
-<H2>Flags:</H2>
+<h2>Flags:</h2>
 <DL>
 
 <DT>-d
@@ -47,7 +47,7 @@
 <DD> For wildfires, also consider spotting.
 </DL>
 
-<H2>Parameters</H2>
+<h2>Parameters</h2>
 <DL>
  
 <DT><B>max=</B>name
@@ -128,91 +128,91 @@
 cell.
 </DL>
 
-<H2>OPTIONS</H2>
+<h2>OPTIONS</h2>
 The user can run r.spread either interactively or non- interactively. The
 program is run interactively if the user types <I>r.spread</I> without
 specifying flag settings and parameter values on the command line. In this
 case, the user will be prompted for input.
 
-<P>Alternately, the user can run r.spread non-interactively, by specifying
+<p>Alternately, the user can run r.spread non-interactively, by specifying
 the names of raster map layers and desired options on the command line,
 using the form:
 
-<P>r.spread [-vds] max=name dir=name base=name start=name [spot_dist=name]
+<p>r.spread [-vds] max=name dir=name base=name start=name [spot_dist=name]
 [w_speed=name] [f_mois=name] [least_size=odds int] [comp_dens=decimal]
 [init_time=int (&gt;=0)] [lag=int (&gt;= 0)] [backdrop=name] output=name [x_output=name]
 [y_output=name] The -d option can only be used after a graphics window
 is opened and selected.
 
-<P>Options spot_dist=name, w_speed=name and f_mois=name must all
+<p>Options spot_dist=name, w_speed=name and f_mois=name must all
 be given if the -s option is used.
 
 
-<H2>EXAMPLE</H2>
+<h2>EXAMPLE</h2>
 Assume we have inputs, the following simulates a spotting- involved wildfire
 on the graphics window and generates three raster maps to contain spread
 time, backlink information in UTM northing and easting coordinates:
 
-<P>r.spread -ds max=my_ros.max dir=my_ros.maxdir base=my_ros.base
+<p>r.spread -ds max=my_ros.max dir=my_ros.maxdir base=my_ros.base
 start=fire_origin spot_dist=my_ros.spotdist w_speed=wind_speed f_mois=1hour_moisture
 backdrop=image_burned output=my_spread x_output=my_spread.x y_output=my_spread.y
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 1. r.spread is a specific implementation of the shortest path algorithm.
 r.cost GRASS program served as the starting point for the development of
 r.spread. One of the major differences between the two programs is that
 r.cost only simulates ISOTROPIC spread while r.spread can simulate ELLIPTICALLY
 ANISOTROPIC spread, including isotropic spread as a special case.
 
-<P>2. Before running r.spread, the user should prepare the ROS (base,
+<p>2. Before running r.spread, the user should prepare the ROS (base,
 max and direction) maps using appropriate models. For some wildfire spread,
 a separate GRASS program r.ros based on Rothermel's fire equation does
 such work. The combination of the two forms a simulation of wildfire spread.
 
-<P>3. The relationship of the start map and ROS maps should be logically
+<p>3. The relationship of the start map and ROS maps should be logically
 correct, i.e. a starting source (a positive value in the start map) should
 not be located in a spread BARRIER (zero value in the ROS maps). Otherwise
 the program refuses to run.
 
-<P>4. r.spread uses the current geographic region settings. The output
+<p>4. r.spread uses the current geographic region settings. The output
 map layer will not go outside the boundaries set in the region, and will
 not be influenced by starting sources outside. So any change of the current
 region may influence the output. The recommendation is to use slightly
 larger region than needed. Refer to g.region to set an appropriate geographic
 region.
 
-<P>5. The inputs to r.spread should be in proper units.
+<p>5. The inputs to r.spread should be in proper units.
 
-<P>6. r.spread is a computationally intensive program. The user may
+<p>6. r.spread is a computationally intensive program. The user may
 need to choose appropriate size of the geographic region and resolution.
 
-<P>7. A low and medium (i.e. &lt;= 0.5) sampling density can improve
+<p>7. A low and medium (i.e. &lt;= 0.5) sampling density can improve
 accuracy for elliptical simulation significantly, without adding significantly
 extra running time. Further increasing the sample density will not gain
 much accuracy while requiring greatly additional running time.
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
-<EM><A HREF="g.region.html">g.region</A></EM>,
-<EM><A HREF="r.cost.html">r.cost</A></EM>,
-<!-- <EM><A HREF="r.mask.html">r.mask</A></EM>, -->
-<EM><A HREF="r.spreadpath.html">r.spreadpath</A></EM>,
-<EM><A HREF="r.ros.html">r.ros</A></EM>
+<em><a href="g.region.html">g.region</A></em>,
+<em><a href="r.cost.html">r.cost</A></em>,
+<!-- <em><a href="r.mask.html">r.mask</A></em>, -->
+<em><a href="r.spreadpath.html">r.spreadpath</A></em>,
+<em><a href="r.ros.html">r.ros</A></em>
 
-<H2>REFERENCES</H2>
+<h2>REFERENCES</h2>
 Chase, Carolyn, H., 1984, Spotting distance from wind-driven surface fires
 -- extensions of equations for pocket calculators, US Forest Service, Res.
 Note INT-346, Ogden, Utah.
 
-<P>Rothermel, R. C., 1983, How to predict the spread and intensity
+<p>Rothermel, R. C., 1983, How to predict the spread and intensity
 of forest and range fires. US Forest Service, Gen. Tech. Rep. INT-143.
 Ogden, Utah.
 
-<P>Xu, Jianping, 1994, Simulating the spread of wildfires using a
+<p>Xu, Jianping, 1994, Simulating the spread of wildfires using a
 geographic information system and remote sensing, Ph. D. Dissertation,
 Rutgers University, New Brunswick, New Jersey.
 
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
 Jianping Xu and Richard G. Lathrop, Jr., Center for Remote Sensing and
 Spatial Analysis, Rutgers University.
 

Modified: grass/trunk/raster/r.spreadpath/r.spreadpath.html
===================================================================
--- grass/trunk/raster/r.spreadpath/r.spreadpath.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/raster/r.spreadpath/r.spreadpath.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -1,47 +1,47 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
-<EM>r.spreadpath</EM> recursively traces the least cost path backwards to
+<em>r.spreadpath</em> recursively traces the least cost path backwards to
 the origin, given backlink information input map layers and target locations
 from where paths are to be traced. The backlink information map layers
 record each cell's backlink UTM northing (the y_input) and easting (the
 x_input) coordinates from which the cell's cumulative cost was determined.
 
-<P>
+<p>
 
 The backlink inputs can be generated from another GRASS raster program
-<EM>r.spread</EM>. One of the major applications of <EM>r.spreadpath</EM>
-along with <EM>r.spread</EM> is to accurately find the least cost corridors
-and/or paths on a raster setting. More information on <EM>r.spread</EM> and
-<EM>r.spreadpath</EM> can be found in Xu (1994).
+<em>r.spread</em>. One of the major applications of <em>r.spreadpath</em>
+along with <em>r.spread</em> is to accurately find the least cost corridors
+and/or paths on a raster setting. More information on <em>r.spread</em> and
+<em>r.spreadpath</em> can be found in Xu (1994).
 
-<H2>Parameters:</H2>
+<h2>Parameters:</h2>
 <DL>
-<DT><B>x_input=</B><EM>name</EM>
+<DT><B>x_input=</B><em>name</em>
 <DD>Name of input raster map layer containing backlink UTM easting
 coordinates.
 
-<DT><B>y_input=</B><EM>name</EM>
+<DT><B>y_input=</B><em>name</em>
 <DD>Name of input raster map layer containing backlink UTM northing coordinates.
 
-<DT><B>coordinate=</B><EM>x,y[,x,y,x,y, ...]</EM>
+<DT><B>coordinate=</B><em>x,y[,x,y,x,y, ...]</em>
 <DD>Each x,y coordinate pair gives the easting and northing (respectively) geographic coordinates of a target point from which to backwards trace the least cost path. As many
 points as desired can be entered by the user.
 
-<DT><B>output=</B><EM>name</EM>
+<DT><B>output=</B><em>name</em>
 <DD>Name of raster map layer to contain output. Also can be used as the map layer of the input target points. If so used, the input target point map will be overwritten by the output.
 </DL>
 
-<H2>SEE ALSO</H2>
-<EM><A HREF="r.spread.html">r.spread</A></EM>,
-<EM><A HREF="r.ros.html">r.ros</A></EM>
+<h2>SEE ALSO</h2>
+<em><a href="r.spread.html">r.spread</A></em>,
+<em><a href="r.ros.html">r.ros</A></em>
 
 
-<H2>REFERENCES</H2>
+<h2>REFERENCES</h2>
 Xu, Jianping, 1994, Simulating the spread of wildfires using a geographic
 information system and remote sensing, Ph. D. Dissertation, Rutgers University,
 New Brunswick, New Jersey.
 
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
 Jianping Xu and Richard G. Lathrop, Jr., Center for Remote Sensing and
 Spatial Analysis, Rutgers University.
 

Modified: grass/trunk/raster/r.statistics/r.statistics.html
===================================================================
--- grass/trunk/raster/r.statistics/r.statistics.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/raster/r.statistics/r.statistics.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -66,4 +66,4 @@
 <h2>AUTHOR</h2>
 Martin Schroeder, Geographisches Institut Heidelberg, Germany
 
-<p><i>Last changed: $Date$</i></p>
+<p><i>Last changed: $Date$</i>

Modified: grass/trunk/raster/r.statistics2/r.statistics2.html
===================================================================
--- grass/trunk/raster/r.statistics2/r.statistics2.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/raster/r.statistics2/r.statistics2.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -13,4 +13,4 @@
 <h2>AUTHOR</h2>
 Glynn Clements
 
-<p><i>Last changed: $Date$</i></p>
+<p><i>Last changed: $Date$</i>

Modified: grass/trunk/raster/r.sun/r.sun.html
===================================================================
--- grass/trunk/raster/r.sun/r.sun.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/raster/r.sun/r.sun.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -10,7 +10,7 @@
 the shadowing effect directly from the digital elevation model or using rasters
 of the horizon height which is much faster. The horizon rasters can be
 constructed using  <a href="r.horizon.html">r.horizon</a>.
-<P>
+<p>
 For latitude-longitude coordinates it requires that the elevation map is in meters.
 The rules are:
 <ul>
@@ -43,7 +43,7 @@
 model accounts for sky obstruction by local relief features. Several solar
 parameters are saved in the resultant maps' history files, which may be viewed
 with the <a href="r.info.html">r.info</a> command.
-</p>
+
 <p>
 The solar incidence angle raster map <i>incidout</i> is computed specifying 
 elevation raster map <i>elevin</i>, aspect raster map <i>aspin</i>, slope 
@@ -62,7 +62,7 @@
 The specified day <i>day</i> is the number of the day of the general year
 where January 1 is day no.1 and December 31 is 365. Time <i>time</i> must
 be a local (solar) time (i.e. NOT a zone time, e.g. GMT, CET) in decimal system,
-e.g. 7.5 (= 7h 30m A.M.), 16.1 = 4h 6m P.M.. </p>
+e.g. 7.5 (= 7h 30m A.M.), 16.1 = 4h 6m P.M.. 
 <p>
 Setting the solar declination <i>declin</i> by user is an option to override
 the value computed by the internal routine for the day of the year. The value
@@ -71,7 +71,7 @@
 over a large region. The geographical latitude must be also in decimal system
 with positive values for northern hemisphere and negative for southern one.
 In similar principle the Linke turbidity factor (<i>linkein</i>, <i>lin</i>
-) and ground albedo (<i>albedo</i>, <i>alb</i>) can be set. </p>
+) and ground albedo (<i>albedo</i>, <i>alb</i>) can be set. 
 <p>
 Besides clear-sky radiations, the user can compute a real-sky radiation (beam,
 diffuse) using <i>coefbh</i> and <i>coefdh </i>input raster maps defining
@@ -91,7 +91,7 @@
 factor for an absolutely clear atmosphere is <i>lin</i>=1.0. See notes below
 to learn more about this factor. The incidence solar angle is the angle between
 horizon and solar beam vector. 
-<P>
+<p>
 The solar radiation maps for a given day are computed by integrating the
 relevant irradiance between sunrise and sunset times for that day. The
 user can set a finer or coarser time step used for all-day radiation
@@ -104,7 +104,7 @@
 <i>step</i> to 4 minutes or less. <i>step</i><tt>=0.05</tt> is equivalent
 to every 3 minutes. Of course setting the time step to be very fine
 proportionally increases the module's running time.
-<P>
+<p>
 The output units are in Wh per squared meter per given
 day [Wh/(m*m)/day]. The incidence angle and irradiance/irradiation maps can
 be computed without shadowing influence of relief by default or they can
@@ -128,7 +128,7 @@
 speed. Values greater than 2.0 may produce estimates with lower accuracy
 in highly dissected relief. The fully shadowed areas are written to the ouput
 maps as zero values. Areas with NULL data are considered as no barrier with
-shadowing effect .</p>
+shadowing effect .
 <p>The maps' history files are generated containing the following listed 
 parameters used in the computation: <br>
 - Solar constant 1367 W.m-2 <br>
@@ -140,18 +140,18 @@
 - Daylight lengths <br>
 - Geographical latitude (min-max) <br>
 - Linke turbidity factor (min-max) <br>
-- Ground albedo (min-max) </p>
+- Ground albedo (min-max) 
 <p>The user can use a nice shellcript with variable
 day to compute radiation for some time interval within the year (e.g. vegetation
 or winter period). Elevation, aspect and slope input values should not be
 reclassified into coarser categories. This could lead to incorrect results. 
-</p>
 
+
 <h2> OPTIONS</h2>
-<P>Currently, there are two modes of r.sun.
+<p>Currently, there are two modes of r.sun.
 In the first mode it calculates solar incidence angle and solar irradiance
 raster maps using the set local time. In the second mode daily sums of solar
-irradiation [Wh.m-2.day-1] are computed for a specified day. </p>
+irradiation [Wh.m-2.day-1] are computed for a specified day. 
 
 <h2>
 NOTES</h2>
@@ -171,12 +171,12 @@
 this component is often the largest source of estimation error. Taking into
 consideration the existing models and their limitation the European Solar
 Radiation Atlas team selected the Muneer (1990) model as it has a sound theoretical
-basis and thus more potential for later improvement. </p>
+basis and thus more potential for later improvement. 
 <p>
 Details of underlying equations used in this program can be found in the
 reference literature cited below or book published by Neteler and Mitasova: 
 Open Source GIS: A GRASS GIS Approach (published in Kluwer Academic Publishers 
-in 2002). </p>
+in 2002). 
 <p>
 Average monthly values of the Linke turbidity coefficient for a mild climate
 in the northern hemisphere (see reference literature for your study area):
@@ -189,7 +189,7 @@
 <tr><td>industrial</td><td>4.1</td><td>4.3</td><td>4.7</td><td>5.3</td><td>5.5</td><td>5.7</td><td>5.8</td><td>5.7</td><td>5.3</td><td>4.9</td><td>4.5</td><td>4.2</td><td>5.00</td></tr>
 </table>
 
-<P>
+<p>
 Planned improvements include the use of the SOLPOS algorithm for solar 
 geometry calculations and internal computation of aspect and slope.
 
@@ -260,48 +260,48 @@
 <p>
 Hofierka, J. (1997). Direct solar radiation modelling within an open GIS
 environment. Proceedings of JEC-GI'97 conference in Vienna, Austria, IOS
-Press Amsterdam, 575-584. </p>
+Press Amsterdam, 575-584. 
 <p>
 Jenco, M. (1992). Distribution of direct solar radiation on georelief and
 its modelling by means of complex digital model of terrain (in Slovak). Geograficky
-casopis, 44, 342-355. </p>
+casopis, 44, 342-355. 
 <p>
 Kasten, F. (1996). The Linke turbidity factor based on improved values of
-the integral Rayleigh optical thickness. Solar Energy, 56 (3), 239-244. </p>
+the integral Rayleigh optical thickness. Solar Energy, 56 (3), 239-244. 
 <p>
 Kasten, F., Young, A. T. (1989). Revised optical air mass tables and approximation
-formula. Applied Optics, 28, 4735-4738. </p>
+formula. Applied Optics, 28, 4735-4738. 
 <p>
 Kittler, R., Mikler, J. (1986): Basis of the utilization of solar radiation 
-(in Slovak). VEDA, Bratislava, p. 150. </p>
+(in Slovak). VEDA, Bratislava, p. 150. 
 <p>
 Krcho, J. (1990). Morfometrická analza a digitálne modely georeliéfu
 (Morphometric analysis and digital models of georelief). VEDA,
-Bratislava (in Slovak). </p>
+Bratislava (in Slovak). 
 <p>
 Muneer, T. (1990). Solar radiation model for Europe. Building services engineering
-research and technology, 11, 4, 153-163. </p>
+research and technology, 11, 4, 153-163. 
 <p>
 Neteler, M., Mitasova, H. (2002): Open Source GIS: A GRASS GIS Approach, Kluwer
-Academic Publishers/Springer. </p>
+Academic Publishers/Springer. 
 <p>
 Page, J. ed. (1986). Prediction of solar radiation on inclined surfaces. Solar
 energy R&amp;D in the European Community, series F -- Solar radiation data,
-Dordrecht (D. Reidel), 3, 71, 81-83. </p>
+Dordrecht (D. Reidel), 3, 71, 81-83. 
 <p>
 Page, J., Albuisson, M., Wald, L. (2001). The European solar radiation atlas:
-a valuable digital tool. Solar Energy, 71, 81-83. </p>
+a valuable digital tool. Solar Energy, 71, 81-83. 
 <p>
 Rigollier, Ch., Bauer, O., Wald, L. (2000). On the clear sky model of the
 ESRA - European Solar radiation Atlas - with respect to the Heliosat method.
-Solar energy, 68, 33-48. </p>
+Solar energy, 68, 33-48. 
 <p>
 Scharmer, K., Greif, J., eds., (2000). The European solar radiation atlas,
 Vol. 2: Database and exploitation software. Paris (Les Presses de l'École
-des Mines). </p>
+des Mines). 
 <p>
 Suri, M., Hofierka, J. (2004): A new GIS-based solar radiation model and its
-application to photovoltaic assessments. Transactions in GIS 8, pp. 175-190.</p>
+application to photovoltaic assessments. Transactions in GIS 8, pp. 175-190.
 
 <p>Joint Research Centre: <a href="http://re.jrc.ec.europa.eu/pvgis/">GIS solar radiation database for Europe</a> and
 <a href="http://re.jrc.ec.europa.eu/pvgis/solres/solmod3.htm">Solar radiation and GIS</a>
@@ -320,4 +320,4 @@
 <a href="MAILTO:suri at geomodel.sk">suri at geomodel.sk</a>
 </address>
 
-<p><i>Last changed: $Date$</i> </p>
+<p><i>Last changed: $Date$</i> 

Modified: grass/trunk/raster/r.support/r.support.html
===================================================================
--- grass/trunk/raster/r.support/r.support.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/raster/r.support/r.support.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -39,4 +39,4 @@
 
 <p>
 <i>Last changed: $Date$</i>
-</p>
+

Modified: grass/trunk/raster/r.support.stats/r.support.stats.html
===================================================================
--- grass/trunk/raster/r.support.stats/r.support.stats.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/raster/r.support.stats/r.support.stats.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -19,4 +19,4 @@
 Micharl Shapiro, CERL: Original author<br>
 <a href="MAILTO:rez at touchofmadness.com">Brad Douglas</a>: GRASS 6 Port<br>
 
-<p><i>Last changed: $Date$</i> </p>
+<p><i>Last changed: $Date$</i> 

Modified: grass/trunk/raster/r.surf.idw/r.surf.idw.html
===================================================================
--- grass/trunk/raster/r.surf.idw/r.surf.idw.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/raster/r.surf.idw/r.surf.idw.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -52,7 +52,7 @@
 <em><a href="r.surf.idw2.html">r.surf.idw2</a></em> except when the input data
 layer contains few non-zero data, i.e. when the cost of the search exceeds
 the cost of the additional distance calculations performed by 
-<em><A HREF="r.surf.idw2.html">r.surf.idw2</a></em>. The relative performance
+<em><a href="r.surf.idw2.html">r.surf.idw2</a></em>. The relative performance
 of these utilities will depend on the comparative speed of boolean, integer
 and floating point operations on a particular platform.
 

Modified: grass/trunk/raster/r.texture/r.texture.html
===================================================================
--- grass/trunk/raster/r.texture/r.texture.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/raster/r.texture/r.texture.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -111,7 +111,7 @@
 The code was taken by permission from <em>pgmtexture</em>, part of
 PBMPLUS (Copyright 1991, Jef Poskanser and Texas Agricultural Experiment
 Station, employer for hire of James Darrell McCauley). <br>
-Manual page of <a href="http://netpbm.sourceforge.net/doc/pgmtexture.html">pgmtexture</a></p>
+Manual page of <a href="http://netpbm.sourceforge.net/doc/pgmtexture.html">pgmtexture</a>
 
 <ul> 
 <li>Haralick, R.M., K. Shanmugam, and I. Dinstein (1973). Textural features for

Modified: grass/trunk/raster/r.thin/r.thin.html
===================================================================
--- grass/trunk/raster/r.thin/r.thin.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/raster/r.thin/r.thin.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -24,7 +24,7 @@
 
 <h2>NOTE</h2>
 
-<em>r.thin</em> only creates raster map layers.  You will need to run 
+<em>r.thin</em> only creates raster map layers.  The user will need to run 
 <em><a href="r.to.vect.html">r.to.vect</a></em>
 on the resultant raster map to create a vector 
 (<em><a href="wxGUI.Vector_Digitizing_Tool.html">wxGUI vector digitizer</a></em>) map layer.
@@ -51,9 +51,7 @@
 object while retaining any pixels whose removal would alter
 the connectivity or shorten the legs of the sceleton."
 
-
 <p>
-
 The sceleton is finally thinned when the thinning process
 converges; i.e., "no further pixels can be removed without
 altering the connectivity or shortening the sceleton legs"

Modified: grass/trunk/raster/r.topidx/r.topidx.html
===================================================================
--- grass/trunk/raster/r.topidx/r.topidx.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/raster/r.topidx/r.topidx.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -39,4 +39,4 @@
 GRASS port by <a href="mailto:grass4u at gmail com">Huidae Cho</a><br>
 Hydro Laboratory, Kyungpook National University, South Korea
 
-<p><i>Last changed: $Date$</i></p>
+<p><i>Last changed: $Date$</i>

Modified: grass/trunk/raster/r.topmodel/r.topmodel.html
===================================================================
--- grass/trunk/raster/r.topmodel/r.topmodel.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/raster/r.topmodel/r.topmodel.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -45,7 +45,7 @@
 K. Beven, R. Lamb, P. Quinn, R. Romanowicz, and J. Freer.
 TOPMODEL, in V.P. Singh (Ed.). Computer Models of Watershed Hydrology.
 Water Resources Publications, 1995.
-<P>
+<p>
 S.C. Liaw, Streamflow simulation using a physically based hydrologic
 model in humid forested watersheds (Dissertation).
 Colorado State University, CO. p163, 1988.

Modified: grass/trunk/raster/r.uslek/r.uslek.html
===================================================================
--- grass/trunk/raster/r.uslek/r.uslek.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/raster/r.uslek/r.uslek.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -1,25 +1,31 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
-<EM>r.uslek</EM> calculates the USLE K factor, that is the Soil Erodibility Factor.
-It takes input of soil texture classes (sand, clay, silt) and organic matter, all in range of [0.0-1.0]. The FAO World Soil CD documentation was used to produce the conversion system between soil textures and soil classes. The soil classes are in number of 12 and apparently come from a USDA publication of 1951 (p.209). Once the soil classes have been identified (by vector cross-products tests), a general conversion table was applied for transforming soil classes into K factor.
+<em>r.uslek</em> calculates the USLE K factor, that is the Soil Erodibility
+Factor. It takes input of soil texture classes (sand, clay, silt) and
+organic matter, all in range of [0.0-1.0]. The FAO World Soil CD
+documentation was used to produce the conversion system between soil
+textures and soil classes. The soil classes are in number of 12 and
+apparently come from a USDA publication of 1951 (p.209). Once the soil
+classes have been identified (by vector cross-products tests), a general
+conversion table was applied for transforming soil classes into K factor.
 
-<H2>NOTES</H2>
-r.watershed provides for USLE L,S,LS factors.
+<h2>NOTES</h2>
+<em>r.watershed</em> provides for USLE L, S, LS factors.
 
-<H2>TODO</H2>
+<h2>TODO</h2>
 
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
 <em>
-<A HREF="r.usler.html">r.usler</A><br>
-<A HREF="r.watershed.html">r.watershed</A><br>
+<a href="r.usler.html">r.usler</A><br>
+<a href="r.watershed.html">r.watershed</A><br>
 </em>
 
 
-<H2>AUTHORS</H2>
+<h2>AUTHORS</h2>
 
-Yann Chemin, SIC-ISDC, Turkmenistan<BR>
+Yann Chemin, SIC-ISDC, Turkmenistan<br>
 
 
 <p>

Modified: grass/trunk/raster/r.walk/r.walk.html
===================================================================
--- grass/trunk/raster/r.walk/r.walk.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/raster/r.walk/r.walk.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -72,11 +72,11 @@
 algorithm, that find an optimum solution (for more details see
 <em>r.cost</em>, that uses the same algorithm).
 <a name="move"></a>
-<H2>Movement Direction</H2>
+<h2>Movement Direction</h2>
 <p>
 The movement direction surface is created to record the sequence of
 movements that created the cost accumulation surface. Without it 
-<EM>r.drain</EM> would not correctly create a path from an end point 
+<em>r.drain</em> would not correctly create a path from an end point 
 back to the start point. The direction shown in each cell points <b>away</b> 
 from the cell that came before it. The directions are recorded as
 GRASS standard directions:<div class="code"><pre>

Modified: grass/trunk/raster/r.water.outlet/r.water.outlet.html
===================================================================
--- grass/trunk/raster/r.water.outlet/r.water.outlet.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/raster/r.water.outlet/r.water.outlet.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -65,7 +65,7 @@
 
 <p>
 <center>
-<img src="r_water_outlet.png" border=0><BR>
+<img src="r_water_outlet.png" border=0><br>
 <i>Watershed draped over flow accumulation</i>
 </center>
 

Modified: grass/trunk/raster/rasterintro.html
===================================================================
--- grass/trunk/raster/rasterintro.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/raster/rasterintro.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -14,7 +14,7 @@
 i.e. the geographic extent of the map is described by the outer bounds of
 all cells within the map.
 
-<P>
+<p>
 As a general rule in GRASS:
 <ol>
 <li> Raster output maps have their bounds and resolution equal to those
@@ -32,11 +32,11 @@
 reading non-georeferenced data, the imported map will usually have its
 lower-left corner at (0,0) in the location's coordinate system; the user
 needs to use <a href="r.region.html">r.region</a> to "place" the imported map.
-<P>
+<p>
 Some programs which need to perform specific types of resampling (e.g.
 <a href="r.resamp.rst.html">r.resamp.rst</a>) read the input maps at
 their original resolution then do the resampling themselves.
-<P>
+<p>
 <a href="r.proj.html">r.proj</a> has to deal with two regions (source
 and destination) simultaneously; both will have an impact upon the
 final result.
@@ -49,14 +49,14 @@
 the default region to match the extent of the imported raster map.
 For special cases, other import modules are available. The full map
 is always imported.
-<P>
+<p>
 For importing scanned maps, the user will need to create a
 x,y-location, scan the map in the desired resolution and save it into
 an appropriate raster format (e.g. tiff, jpeg, png, pbm) and then use
 <a href="r.in.gdal.html">r.in.gdal</a> to import it. Based on
 reference points the scanned map can be recified to obtain geocoded
 data.
-<P>
+<p>
 Raster maps are exported with <a href="r.out.gdal.html">r.out.gdal</a>
 into common formats. Also <a href="r.out.bin.html">r.out.bin</a>,
 <a href="r.out.vtk.html">r.out.vtk</a>, <a href="r.out.ascii.html">r.out.ascii</a>
@@ -165,7 +165,7 @@
 a variety of statistical methods in creating the new raster.
 <p>
 
-Otherwise, for interpolation of scattered data, use the <EM>v.surf.*</EM> set of
+Otherwise, for interpolation of scattered data, use the <em>v.surf.*</em> set of
 modules.
 
 <h4>Raster MASKs</h4>
@@ -179,7 +179,7 @@
 floating-point map, the values will be converted to integers using the
 map's quantisation rules (this defaults to round-to-nearest, but can
 be changed with r.quant).
-<P>
+<p>
 (see <a href="r.mask.html">r.mask</a>)
 
 <h3>Raster map statistics</h3>

Modified: grass/trunk/raster/simwe/r.sim.sediment/r.sim.sediment.html
===================================================================
--- grass/trunk/raster/simwe/r.sim.sediment/r.sim.sediment.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/raster/simwe/r.sim.sediment/r.sim.sediment.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -69,7 +69,7 @@
 csthaxto at unity.ncsu.edu</a></address>
 <h2>
 REFERENCES</h2>
-<P>
+<p>
 <a href="http://skagit.meas.ncsu.edu/~helena/gmslab/papers/II.6.8_Mitasova_044.pdf">
 Mitasova, H., Thaxton, C., Hofierka, J., McLaughlin, R., Moore, A., Mitas L., 2004,</a>
 Path sampling method for modeling overland water flow, sediment transport
@@ -77,15 +77,15 @@
 In: C.T. Miller, M.W. Farthing, V.G. Gray, G.F. Pinder eds.,
 Proceedings of the XVth International Conference on Computational Methods in Water
 Resources (CMWR XV), June 13-17 2004, Chapel Hill, NC, USA, Elsevier, pp. 1479-1490.
-<P>
+<p>
 <a href="http://skagit.meas.ncsu.edu/~helena/gmslab/gisc00/duality.html">
 Mitasova H, Mitas, L., 2000, Modeling spatial processes in multiscale framework: 
 exploring duality between particles and fields, </a>
 plenary talk at GIScience2000 conference, Savannah, GA.
-<P>
+<p>
 Mitas, L., and Mitasova, H., 1998, Distributed soil erosion simulation
 for effective erosion prevention. Water Resources Research, 34(3), 505-516.
-<P>
+<p>
 <a href="http://skagit.meas.ncsu.edu/~helena/gmslab/papers/LLEmiterev1.pdf">
  Mitasova, H., Mitas, L., 2001, Multiscale soil erosion simulations for land use management, </a>
 In: Landscape erosion and landscape evolution modeling, Harmon R. and Doe W. eds.,
@@ -94,7 +94,7 @@
 <a href="http://www.grassbook.org">
 Neteler, M. and Mitasova, H., 2008, Open Source GIS: A GRASS GIS Approach. Third Edition.</a>
 The International Series in Engineering and Computer Science: Volume 773. Springer New York Inc, p. 406.
-<P>
+<p>
 <p><br>
-Last changed: $Date$</p>
+Last changed: $Date$
 

Modified: grass/trunk/raster/simwe/r.sim.water/r.sim.water.html
===================================================================
--- grass/trunk/raster/simwe/r.sim.water/r.sim.water.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/raster/simwe/r.sim.water/r.sim.water.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -71,7 +71,7 @@
 organized as a table. A single header identifies the category number of the logged vector points.
 In case of invalid water depth data the value -1 is used.
 
-<P>
+<p>
 Overland flow is routed based on partial derivatives of elevation
 field or other landscape features influencing water flow. Simulation
 equations include a diffusion term (<i>diffc</i> parameter) which enables 

Modified: grass/trunk/raster3d/r3.in.ascii/r3.in.ascii.html
===================================================================
--- grass/trunk/raster3d/r3.in.ascii/r3.in.ascii.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/raster3d/r3.in.ascii/r3.in.ascii.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -19,7 +19,7 @@
 Default is <em>none</em>.
 
 <center>
-<img src="g3d_volume_layout.png" border=0><BR>
+<img src="g3d_volume_layout.png" border=0><br>
 <table border=0 width=700>
 <tr><td><center>
 <i>The volume coordinate system and tile layout of the inported voxel map</i>

Modified: grass/trunk/raster3d/r3.mkdspf/r3.mkdspf.html
===================================================================
--- grass/trunk/raster3d/r3.mkdspf/r3.mkdspf.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/raster3d/r3.mkdspf/r3.mkdspf.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -1,4 +1,4 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
 Creates a display file from an existing grid3 file according to
 specified threshold levels.  The display file is a display list
@@ -42,7 +42,7 @@
 <DD>Default: 7
 </DL>
 
-<H2>Example:</H2>
+<h2>Example:</h2>
 With grid3 data (<I>phdata</I>) in the range 3-7, 
 we only want to see isosurface values for the range 4-6.  
 Any of these commands will produce the same results:<br>
@@ -52,7 +52,7 @@
 r3.mkdspf phdata dspf=iso min=4.0 max=6.0 step=0.5
 </pre>
 
-<H2>NOTE</H2>
+<h2>NOTE</h2>
 Currently the grid3 file must be in the user's mapset since the 
 display files being created are specific to particular grid3 
 files and are contained in directories under them.  
@@ -60,9 +60,9 @@
 may make display files from others' grid3 files without having to
 copy them to their mapset.  
 
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
 <p>Bill Brown,
-<A HREF="mailto:brown at gis.uiuc.edu">bbrown at gis.uiuc.edu</A>
-</p>
+<a href="mailto:brown at gis.uiuc.edu">bbrown at gis.uiuc.edu</A>
 
+
 <p><i>Last changed: $Date$</i>

Modified: grass/trunk/scripts/d.correlate/d.correlate.html
===================================================================
--- grass/trunk/scripts/d.correlate/d.correlate.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/scripts/d.correlate/d.correlate.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -37,7 +37,7 @@
 <h2>AUTHOR</h2>
 
 Michael Shapiro,
-<a HREF="http://www.cecer.army.mil/">U.S.Army Construction Engineering Research Laboratory</a>
+<a href="http://www.cecer.army.mil/">U.S.Army Construction Engineering Research Laboratory</a>
 <p>
 Rewritten to GRASS 6 (from csh to sh) by Markus Neteler; from sh to Python by Glynn Clements
 

Modified: grass/trunk/scripts/d.out.gpsdrive/d.out.gpsdrive.html
===================================================================
--- grass/trunk/scripts/d.out.gpsdrive/d.out.gpsdrive.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/scripts/d.out.gpsdrive/d.out.gpsdrive.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -1,27 +1,27 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
-<EM>d.out.gpsdrive</EM> exports the current GRASS display monitor to a 
-<A HREF="http://www.gpsdrive.de">GpsDrive</a> compatible backdrop 
+<em>d.out.gpsdrive</em> exports the current GRASS display monitor to a 
+<a href="http://www.gpsdrive.de">GpsDrive</a> compatible backdrop 
 image and updates the GpsDrive image list with the appropriate geo-referencing
 information.
 
-<P>
+<p>
 <b><em>Use at your own risk. Do not use as a primary means of navigation.
 This software comes with absolutely no warranty.</em></b>
 
 
-<P>
-<H2>NOTES</H2>
+<p>
+<h2>NOTES</h2>
 
 Maps are saved in the user's <tt>~/.gpsdrive/maps/</tt> directory.
 Geo-referencing information is added to the user's
 <tt>~/.gpsdrive/maps/map_koord.txt</tt> file.
 
-<P>
+<p>
 JPEG output requires the <tt>pngtopnm</tt> and <tt>pnmtojpeg</tt> programs
 from the <a href="http://netpbm.sourceforge.net">NetPBM tools</a>.
 
-<P>
+<p>
 GpsDrive assumes northings are not rotated compared to true-geographic north.
 If you are using a projection with significant curvature away from the central
 meridian, or a map datum with a significant rotational component, then you will 
@@ -31,15 +31,15 @@
 centered directly on the center of your map. You can check the local
 convergence angle (difference between grid north and true north) with
 "<tt>g.region -n</tt>".
-<P>
+<p>
 To avoid distortion, anything more global than 1:150k to 1:500k
 should come from a lat/lon location. Anything more local than that
 will look better coming from a projected system such as UTM.
-<P>
+<p>
 The extent of a map given a target scale can be calculated with 
 <tt>x_ext=scale*(1280/2817.95)</tt>. e.g. 1:50,000 translates to approx
 a 22.7km x 18.2km image window in the GIS.
-<P>
+<p>
 For your convenience (calculations are rough, but nominal):
 <div class="code"><pre>
 1:50,000 uses a region 22.7km x 18.2km.
@@ -47,26 +47,26 @@
 1:100,000 uses a region  45.4km x 36.3km.
 1:175,000 uses a region  79.5km x 63.6km.
 </pre></div>
-<BR>
+<br>
 
 
 Maps exported from lat-lon locations will be given a "<tt>top_</tt>" prefix.
 Maps exported from locations of other projections will be given a 
 "<tt>map_</tt>" prefix. This is done so GpsDrive knows how to scale the 
 image correctly.
-<P>
+<p>
 GpsDrive requires backdrop images to be 1280x1024 pixels in size. While this
 script takes care of that automatically, to avoid annoying bands on the sides
 of your image you may want to set up your display monitor at half-scale (same
 aspect ratio) and use d.zoom to select the full frame. For example:
-<P>
+<p>
 <div class="code"><pre>
 export GRASS_WIDTH=640
 export GRASS_HEIGHT=512
 d.mon wx0
 </pre></div>
 
-<BR>
+<br>
 Map scaling is set from the region settings so should work correctly even 
 when the display's aspect ratio does not match that of the output image.
 
@@ -76,7 +76,7 @@
 It may be desirable to create a series of image tiles covering a large area.
 An easy way to do this is to run <em>d.out.gpsdrive</em> in a shell loop.
 Here is an example Bash script contributed by Manuel Morales:
-<P>
+<p>
 <div class="code"><pre>
 #!/bin/bash
 
@@ -115,35 +115,35 @@
 done
 </pre></div>
 
-<BR>
+<br>
 Note that to get a smoother transition between backdrop maps this script
 creates overlapping tiles. For best results at least 1/3rd overlap should
 be maintained.
 
 
-<BR><BR>
-<H2>SEE ALSO</H2>
+<br><br>
+<h2>SEE ALSO</h2>
 
-<EM><A HREF="d.info.html">d.info</A></EM>,
-<EM><A HREF="d.grid.html">d.grid</A></EM>,
-<EM><A HREF="d.out.file.html">d.out.file</A></EM>,
-<EM><A HREF="d.out.png.html">d.out.png</A></EM>,
-<EM><A HREF="d.save.html">d.save</A></EM>,
-<EM><A HREF="g.region.html">g.region</A></EM>,
-<EM><A HREF="v.in.garmin.html">v.in.garmin</A></EM>
-<BR><BR>
-The GRASS <A HREF="pngdriver.html">PNG driver</A><BR>
+<em><a href="d.info.html">d.info</A></em>,
+<em><a href="d.grid.html">d.grid</A></em>,
+<em><a href="d.out.file.html">d.out.file</A></em>,
+<em><a href="d.out.png.html">d.out.png</A></em>,
+<em><a href="d.save.html">d.save</A></em>,
+<em><a href="g.region.html">g.region</A></em>,
+<em><a href="v.in.garmin.html">v.in.garmin</A></em>
+<br><br>
+The GRASS <a href="pngdriver.html">PNG driver</A><br>
 
-The <A HREF="http://www.gpsdrive.de">GpsDrive</a> project<BR>
-The <A HREF="http://gpsd.berlios.de">gpsd</a> personal GPS server project
-<BR><BR>
+The <a href="http://www.gpsdrive.de">GpsDrive</a> project<br>
+The <a href="http://gpsd.berlios.de">gpsd</a> personal GPS server project
+<br><br>
 
-<H2>AUTHOR</H2>
-Hamish Bowman<BR> <i>
-Department of Marine Science<BR>
-University of Otago<BR>
-New Zealand</i><BR>
-<BR>
+<h2>AUTHOR</h2>
+Hamish Bowman<br> <i>
+Department of Marine Science<br>
+University of Otago<br>
+New Zealand</i><br>
+<br>
 
 <p>
 <i>Last changed: $Date$</i>

Modified: grass/trunk/scripts/d.polar/d.polar.html
===================================================================
--- grass/trunk/scripts/d.polar/d.polar.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/scripts/d.polar/d.polar.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -5,16 +5,16 @@
 The input angle map orientation must be counter-clockwise (CCW)
 from east, and the angle map units must be degrees. This refers
 to the standard orientation of GRASS (e.g., see <em>r.slope.aspect</em>).
-<P>
+<p>
 The radius of the outer circle is defined by the total number
 of pixels in the map. If the polar diagram does not reach the
 outer circle, no data (NULL) pixels were found in the map.
-<P>
+<p>
 The vector in the diagram indicates a prevailing direction, its length
 the strength of such direction. In case all angle vectors are oriented
 along the same direction, the length for the vector is maximal (in fact 
 it is equal to length of the most populated bin of the underlying histogram).
-<P>
+<p>
 As a side effect, the quality of the angle map can be derived from
 the diagram. Strong spikes may indicate an over-representation of
 the related angle(s) which happens in particular if integer maps
@@ -26,7 +26,7 @@
 as EPS file. If the <b>-x</b> flag is used <em>xgraph</em> is lauched.
 Otherwise <em>d.polar</em> will use <em>d.graph</em> to draw the plot
 in the current display frame.
-<P>
+<p>
 If <em>d.polar</em> is used on an aspect map generated by
 <em>r.slope.aspect</em>, the <b>undef</b> parameter should be
 set to 0 to distinguish NO DATA (NULL) areas from areas where
@@ -73,8 +73,8 @@
 
 <h2>AUTHORS</h2>
 
-Markus Neteler, ITC-irst, Italy<BR>
-Bruno Caprile, ITC-irst, Italy<BR>
-Hamish Bowman, Otago University, New Zealand<BR>
+Markus Neteler, ITC-irst, Italy<br>
+Bruno Caprile, ITC-irst, Italy<br>
+Hamish Bowman, Otago University, New Zealand<br>
 
-<p><i>Last changed: $Date$</i></p>
+<p><i>Last changed: $Date$</i>

Modified: grass/trunk/scripts/d.rast.edit/d.rast.edit.html
===================================================================
--- grass/trunk/scripts/d.rast.edit/d.rast.edit.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/scripts/d.rast.edit/d.rast.edit.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -1,11 +1,11 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
-The <EM>d.rast.edit</EM> program allows users to interactively
+The <em>d.rast.edit</em> program allows users to interactively
 edit cell category values in a raster map layer displayed to the
 graphics monitor using a mouse cursor.
 
 
-<H2>USAGE</H2>
+<h2>USAGE</h2>
 
 <B><I>Note: this help page refers to the old Tcl/Tk version of this
 program. Parts of it may be out of date or wrong.</I></B>
@@ -23,14 +23,14 @@
 Cell editing is done using a mouse cursor to choose menu selections
 and indicate areas on the displayed raster map that are to be edited.
 
-<P>
+<p>
 Selections available at the top of the edit window are <b>Save</b> and
 <b>Exit</b>.
-<P>
+<p>
 
 As the mouse travels over the cells in the edit window you are shown the
 current coordinates and current cell values under the cursor.
-<P>
+<p>
 To change the value of a cell put the new value to use in the "New value"
 box at the bottom left of the edit window under the coordinate information
 bar. A value of "*" indicates a NULL value should be used.
@@ -39,31 +39,31 @@
 <H3>Arrows</H3>
 
 This function is available for users editing aspect maps.  The
-<EM><A HREF="d.rast.arrow.html">d.rast.arrow</A></EM> program is
+<em><a href="d.rast.arrow.html">d.rast.arrow</A></em> program is
 called, which draws arrows over the displayed
 cells to indicate the downslope direction of the cell.
 You can set the aspect map to use on the command line.
 Aspect maps are expected to be in regular "GRASS" format, as produced by
-<EM><A HREF="r.slope.aspect.html">r.slope.aspect</A></EM>; i.e. degrees
+<em><a href="r.slope.aspect.html">r.slope.aspect</A></em>; i.e. degrees
 counter-clockwise from east.
 
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 
 There is no "undo" command or way to exit edit mode without saving
 changes.
-<P>
+<p>
 Any MASK in place will be respected when writing the new raster map layer,
 including any edits to the MASKed areas.
 
 <H3>Geographic Region Concerns</H3>
 
-<EM>d.rast.edit</EM> reads the region definition for the raster map layer
+<em>d.rast.edit</em> reads the region definition for the raster map layer
 being edited from its internal cell header file. The new, edited copy of
 the raster layer will be created with the same resolution and region
 dimensions.
-<P>
-The primary bane of the <EM>d.rast.edit</EM> program involves large map
+<p>
+The primary bane of the <em>d.rast.edit</em> program involves large map
 layers with lots of rows and columns) and/or slow computers,
 since the program must read and write raster map layers row by row for
 the full size of the map layer as dictated by its region size and resolution.
@@ -73,49 +73,49 @@
 times during the editing session).
 
 
-<H2>TODO</H2>
+<h2>TODO</h2>
 
 <!-- not true, but it would be nice
-<EM>d.rast.edit</EM> will not create a new raster map layer if
+<em>d.rast.edit</em> will not create a new raster map layer if
 the user makes no cell edits while running the program.
-<P>
+<p>
 -->
 
-It would be nice to incorporate a scrollable version of <EM>
-<A HREF="d.legend.html">d.legend</A>
-</EM>
+It would be nice to incorporate a scrollable version of <em>
+<a href="d.legend.html">d.legend</A>
+</em>
 (such that one could see a label legend for files with many categories on
 a standard size sub-frame).  It would be even nicer to be able
 to select the category values from a graphical legend when editing
 cell values (thereby saving a trip to the text frame to type in the
 new value).
 
-<P>
+<p>
 Perhaps method(s) for multiple  or mass cell edits would be useful.
-This could be done by providing modes in which the user may:<BR>
-1) edit a block of cells to a given value by drawing a box;<BR>
+This could be done by providing modes in which the user may:<br>
+1) edit a block of cells to a given value by drawing a box;<br>
 2) be able to choose a given value which is automatically used as
 the new value on each cell chosen until a different value is desired.
 
-<P>
+<p>
 There is no interrupt handling. <!-- ?? --> This could leave files in .tmp
 or (rarely) result in half-baked raster maps.  The original file
 would survive unscathed by an interrupt at most any point in execution.
 Beware of exiting the program
-by means other than using <EM>exit</EM> on the <EM>Main Menu</EM>.
+by means other than using <em>exit</em> on the <em>Main Menu</em>.
 
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
 <em>
 <a href="d.rast.arrow.html">d.rast.arrow</a>,
 <a href="d.rast.num.html">d.rast.num</a>
 </em>
 
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
 
-Tcl/Tk and wxPython versions: Glynn Clements<BR>
-<BR>
+Tcl/Tk and wxPython versions: Glynn Clements<br>
+<br>
 Replaces Xdriver version in C by Chris Rewerts,
 Agricultural Engineering,
 Purdue University

Modified: grass/trunk/scripts/db.dropcolumn/db.dropcolumn.html
===================================================================
--- grass/trunk/scripts/db.dropcolumn/db.dropcolumn.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/scripts/db.dropcolumn/db.dropcolumn.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -31,11 +31,11 @@
 <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="v.db.dropcolumn.html">v.db.dropcolumn</a>,
-<a HREF="sql.html">GRASS SQL interface</a>
+<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="v.db.dropcolumn.html">v.db.dropcolumn</a>,
+<a href="sql.html">GRASS SQL interface</a>
 </em>
 
 <h2>AUTHOR</h2>

Modified: grass/trunk/scripts/db.droptable/db.droptable.html
===================================================================
--- grass/trunk/scripts/db.droptable/db.droptable.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/scripts/db.droptable/db.droptable.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -28,13 +28,13 @@
 <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="v.db.droptable.html">v.db.droptable</a>,
-<a HREF="sql.html">GRASS SQL interface</a>
+<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="v.db.droptable.html">v.db.droptable</a>,
+<a href="sql.html">GRASS SQL interface</a>
 </em>
 
 <h2>AUTHOR</h2>

Modified: grass/trunk/scripts/db.in.ogr/db.in.ogr.html
===================================================================
--- grass/trunk/scripts/db.in.ogr/db.in.ogr.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/scripts/db.in.ogr/db.in.ogr.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -49,7 +49,7 @@
 
 <h2>SEE ALSO</h2>
 
-<em><a HREF="v.in.ogr.html">v.in.ogr</a></em><br>
+<em><a href="v.in.ogr.html">v.in.ogr</a></em><br>
 <em><a href="sql.html">GRASS SQL interface</a></em>
 
 <h2>AUTHOR</h2>

Modified: grass/trunk/scripts/db.test/db.test.html
===================================================================
--- grass/trunk/scripts/db.test/db.test.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/scripts/db.test/db.test.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -1,6 +1,6 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
-<EM>db.test</EM> tests database driver and database server running 
+<em>db.test</em> tests database driver and database server running 
 set of SQL queries. Database must exist and connection must be set
 by db.connect.
 
@@ -16,12 +16,12 @@
 <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="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>
 </em>
 
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
 Radim Blazek
 <p><i>Last changed: $Date$</i>

Modified: grass/trunk/scripts/i.fusion.brovey/i.fusion.brovey.html
===================================================================
--- grass/trunk/scripts/i.fusion.brovey/i.fusion.brovey.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/scripts/i.fusion.brovey/i.fusion.brovey.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -1,6 +1,6 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
-<EM>i.fusion.brovey</EM> performs a Brovey transformation using
+<em>i.fusion.brovey</em> performs a Brovey transformation using
 three multispectral and the panchromatic satellite image scene 
 channels. Three new channels are calculated according to the
 formula:
@@ -15,7 +15,7 @@
 The module's help text (above) suggests for LANDSAT-7, QuickBird and SPOT.
 
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 The command changes temporarily to the high resolution of the
 panchromatic channels for creating the three output channels,
 then restores the previous region settings. The current
@@ -23,7 +23,7 @@
 channels may be combined with <em>d.rgb</em> or <em>r.composite</em>.
 
 
-<H2>EXAMPLE</H2>
+<h2>EXAMPLE</h2>
 
 Calculation of Brovey fusion map from North Carolina Landsat scene:
 
@@ -73,17 +73,17 @@
 Colors may be optionally optimized.
 
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
-<EM>
-<A HREF="i.his.rgb.html">i.his.rgb</A>,
-<A HREF="i.rgb.his.html">i.rgb.his</A>,
-<A HREF="d.rgb.html">d.rgb</A>,
-<A HREF="r.composite.html">r.composite</A>
-</EM>
+<em>
+<a href="i.his.rgb.html">i.his.rgb</A>,
+<a href="i.rgb.his.html">i.rgb.his</A>,
+<a href="d.rgb.html">d.rgb</A>,
+<a href="r.composite.html">r.composite</A>
+</em>
 
 
-<H2>REFERENCES</H2>
+<h2>REFERENCES</h2>
 
 <ul>
 <li>Original Brovey formula reference unknown, probably <br>
@@ -104,7 +104,7 @@
 </ul>
 
 
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
 
 Markus Neteler, ITC-irst, Italy
 <p>

Modified: grass/trunk/scripts/i.image.mosaic/i.image.mosaic.html
===================================================================
--- grass/trunk/scripts/i.image.mosaic/i.image.mosaic.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/scripts/i.image.mosaic/i.image.mosaic.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -3,7 +3,7 @@
 <em>i.image.mosaic</em> mosaics several images or raster maps using the
 GRASS GIS map calculator, and extends the colormap to the range of all images.
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
 <em>
 <a href="r.patch.html">r.patch</a>,

Modified: grass/trunk/scripts/i.in.spotvgt/i.in.spotvgt.html
===================================================================
--- grass/trunk/scripts/i.in.spotvgt/i.in.spotvgt.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/scripts/i.in.spotvgt/i.in.spotvgt.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -4,7 +4,7 @@
 After import the digital numbers (DN) are remapped to VEGETATION NDVI
 values and the NDVI color table is applied. The imported DN map is 
 removed after remapping.
-<P>
+<p>
 Apparently missing raster cells due to bad pixel quality are reconstructed
 by the SPOT operating team in the NDVI file. The differences between the
 filtered (-a flag) and raw NDVI map should be compared.
@@ -35,11 +35,11 @@
 <h2>SEE ALSO</h2>
 
 <em>
-<a HREF="r.in.gdal.html">r.in.gdal</a>,
-<a HREF="r.out.gdal.html">r.out.gdal</a>
+<a href="r.in.gdal.html">r.in.gdal</a>,
+<a href="r.out.gdal.html">r.out.gdal</a>
 </em>
 
-<H2>REFERENCES</H2>
+<h2>REFERENCES</h2>
 
 <a href="http://free.vgt.vito.be/">SPOT Vegetation (1km, global) NDVI data set server</a><br>
 <a href="http://www.vgt.vito.be/faqnew/index.html">SPOT Vegetation FAQ</a><br>

Modified: grass/trunk/scripts/i.landsat.rgb/i.landsat.rgb.html
===================================================================
--- grass/trunk/scripts/i.landsat.rgb/i.landsat.rgb.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/scripts/i.landsat.rgb/i.landsat.rgb.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -29,7 +29,7 @@
 afterwards.
 
 
-<H2>EXAMPLE</H2>
+<h2>EXAMPLE</h2>
 
 North Carolina sample dataset:
 <div class="code"><pre>

Modified: grass/trunk/scripts/i.spectral/i.spectral.html
===================================================================
--- grass/trunk/scripts/i.spectral/i.spectral.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/scripts/i.spectral/i.spectral.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -7,7 +7,7 @@
 
 This script needs gnuplot to be installed.
 
-<H2>EXAMPLE</H2>
+<h2>EXAMPLE</h2>
 
 North Carolina sample dataset:
 
@@ -22,9 +22,9 @@
 
 <h2>SEE ALSO</h2>
 
-<em><a HREF="d.what.rast.html">d.what.rast</a></em><br>
-<em><a HREF="d.where.html">d.where</a></em><br>
-<em><a HREF="r.what.html">r.what</a></em><br>
+<em><a href="d.what.rast.html">d.what.rast</a></em><br>
+<em><a href="d.where.html">d.where</a></em><br>
+<em><a href="r.what.html">r.what</a></em><br>
 
 <h2>AUTHOR</h2>
 

Modified: grass/trunk/scripts/i.tasscap/i.tasscap.html
===================================================================
--- grass/trunk/scripts/i.tasscap/i.tasscap.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/scripts/i.tasscap/i.tasscap.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -1,6 +1,6 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
-<EM>i.tasscap</EM> calculates Tasseled Cap (Kauth Thomas, TC) transformation
+<em>i.tasscap</em> calculates Tasseled Cap (Kauth Thomas, TC) transformation
 for LANDSAT-TM data (TM4, TM5, TM7).
 
 <!-- ok, but what is Tasseled Cap ? -->
@@ -15,7 +15,7 @@
 </ul>
 
 
-<H2>EXAMPLE</H2>
+<h2>EXAMPLE</h2>
 
 Calculation of TC maps from North Carolina Landsat scene:
 
@@ -69,7 +69,7 @@
 <br>
 
 
-<H2>REFERENCES</H2>
+<h2>REFERENCES</h2>
 
 <ul>
 <li>LANDSAT-4/LANDSAT-5: TC-factor changed to CRIST et al. 1986,
@@ -87,7 +87,7 @@
 </ul>
 
 
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
 
 Markus Neteler, ITC-irst
 <p>

Modified: grass/trunk/scripts/m.proj/m.proj.html
===================================================================
--- grass/trunk/scripts/m.proj/m.proj.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/scripts/m.proj/m.proj.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -1,4 +1,4 @@
-<H2>DESCRIPTION</H2> 
+<h2>DESCRIPTION</h2> 
 
 This program allows a user to convert coordinates from one projection to
 another. Coordinates can be read from one file, converted, and results
@@ -10,59 +10,59 @@
 <em>cs2cs</em> utility. The <b>-i</b> or <b>-o</b> flags make the task
 especially easy for the common problem of converting to or from lat/long
 WGS84.
-<P>
+<p>
 <i>Note</i>: This program does not transform GRASS maps, it is designed to determine
 the equivalent coordinate values of an individual position or list of
 positions. Use <em>v.proj</em> or <em>r.proj</em> to reproject GRASS maps.
 
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 
 <em>cs2cs</em> expects input data to formatted as "<tt>x y</tt>", so if working
 with latitude-longitude data be sure to send the <tt>x</tt> value first,
 i.e., "<tt>longitude&nbsp;latitude</tt>". Output data will be exported using
 the same convention.
-<P>
+<p>
 <em>cs2cs</em> will treat a third data column as a <tt>z</tt> value (elevation)
 and will modify the value accordingly. This usually translates into small but
 real differences in that data column.
-<P>
+<p>
 <em>cs2cs</em> does not expect the input stream to contain column headings,
 only numbers. If your data file has lines you wish to have passed through
 without being processed, they must start with the '<tt>#</tt>' character.
-<P>
+<p>
 If sending <em>m.proj</em> data from <tt>stdin</tt>, be aware that the data is
 first stored to a temporary file before being processed with <em>cs2cs</em>.
 It is therefore not advisable to send <em>m.proj</em> data from an open data
 stream. The module will stop listening for incoming data after 2 seconds of
 inactivity. You may use the projection parameters gleaned from <em>m.proj</em>'s
 verbose mode (<b>-v</b>) with <em>cs2cs</em> directly in this case.
-<P>
+<p>
 Custom projection parameters can be used via the <b>proj_in</b> and
 <b>proj_out</b> options. Full documentation of the projection parameter
 format may be found on the <tt><a href="http://proj.maptools.org">PROJ.4</a></tt>
 website. Using these options will fully override the default parameters the
 module would normally use.
-<P>
+<p>
 By using the <b>-v</b> verbose flag, the user can see exactly what projection
 parameters will be used in the conversion as well as some other informative
 messages.
-<P>
+<p>
 If output is to lat/long, it will be formatted using <tt>PROJ.4</tt>'s 
 Degree:Minute:Second (DMS) convention of <tt>DDDdMM'SSS.SS"H</tt>. This can be handy
 if you wish to quickly convert lat/long decimal degree data into its DMS
-equivalent.<BR>
+equivalent.<br>
 Alternatively, to have <em>m.proj</em> output data in decimal degrees, use the
 <b>-d</b> flag. This flag can also be used with non-lat/long data to force a
 higher number of decimal places (the <em>cs2cs</em> default is 2).
-<P>
+<p>
 Lat/long output can be converted to GRASS's DMS convention (<tt>DDD:MM:SSS.SSSH</tt>)
 by piping the results of <em>m.proj</em> through the <em>sed</em> stream
 editor as follows.
 <div class="code"><pre>
 m.proj -o | sed -e 's/d/:/g' -e "s/'/:/g"  -e 's/"//g'
 </pre></div>
-<P>
+<p>
 The <em>m.proj</em> module is designed to work seamlessly with point data 
 exported from the GIS with <em>v.out.ascii</em>, as the following example
 shows.
@@ -71,7 +71,7 @@
 </pre></div>
 
 
-<H2>EXAMPLES</H2>
+<h2>EXAMPLES</h2>
 
 To convert a WGS84 long/lat coordinate to the current map projection using
 the <b>-i</b> flag to set projection parameters automaticlly:
@@ -80,7 +80,7 @@
 2316541.70      5479193.51 1.23
 </pre></div>
 
-<P><BR>
+<p><br>
 The same, but load points from a file named "<tt>waypoints.txt</tt>" and
 continue on to import the results into a GRASS vector points map in the
 current map projection:
@@ -90,14 +90,14 @@
 Here the standard UNIX <em>cut</em> tool is used to discard the <tt>z</tt>
 residual.
 
-<P><BR>
+<p><br>
 To convert all coordinates from a vector points map in the current projection
 to WGS84 long/lat, with output in decimal form:
 <div class="code"><pre>
 v.out.ascii bugsites | m.proj -od
 </pre></div>
 
-<P><BR>
+<p><br>
 To transform points from a UTM projection into the Gauss-Kr&uuml;ger Grid
 System, importing and exporting to files:
 
@@ -108,7 +108,7 @@
     +x_0=3500000.0" <b>input</b>=utm.coord.txt <b>output</b>=new.gk.coord.txt
 </pre></div>
 
-<P>
+<p>
 Projection parameters provided in the above case: "<tt>+proj</tt>" (projection
 type), "<tt>+name</tt>" (projection name), "<tt>+a</tt>" (ellipsoid: equatorial
 radius), "<tt>+es</tt>" (ellipsoid: eccentricity squared), "<tt>+zone</tt>"
@@ -120,13 +120,13 @@
 <a href="http://www.remotesensing.org/proj/"><tt>PROJ.4</tt> projection library</a>
 performs an inverse projection to latitude-longitude and then projects the 
 coordinate list to the target projection.
-<P><BR>
+<p><br>
 <!-- HB 4/2006: I'm leaving this in from the GRASS 5 help page, but is it accurate? -->
 Datum conversions are automatically handled by the <tt>PROJ.4</tt> library if
 "<tt>+datum</tt>" setings are specified on <b>both</b> the input <b>and</b> output
 projections on the command line. The "<tt>+towgs84</tt>" parameter can be used to 
 define either 3 or 7 term datum transform coefficients, satisfying this requirement.
-<P>
+<p>
 If a datum is specified there is no need for the '<tt>+ellps=</tt>' or underlying
 parameters, '<tt>+a=</tt>', '<tt>+es=</tt>', etc.
 <p>
@@ -144,46 +144,46 @@
     +y_0=250000 +k=1.000035" <B>proj_out</B>="+proj=ll +datum=wgs84" <B>input</B>=wpt.txt
 </pre></div>
 
-<P>
+<p>
 In this example no datum transformation will take place as a datum was not
 specified for the input projection. The datum specified for the output
 projection will thus be silently ignored and may be left out; all that is
 achieved a simple conversion from projected to geodetic co-ordinates,
-keeping the same datum (and thus also the same ellipsoid).</p>
+keeping the same datum (and thus also the same ellipsoid).
 
 <p>
 For more usage examples, see the documentation for the 
 <tt><a href="http://proj.maptools.org">PROJ.4</a></tt> <em>cs2cs</em> program.
 
 
-<H2>REFERENCES</H2>
+<h2>REFERENCES</h2>
 
 [1] Evenden, G.I.  (1990) <a href="http://proj.maptools.org/">Cartographic projection procedures for
 the UNIX environment - a user's manual.</a>  USGS Open-File Report 90-284 (OF90-284.pdf)
 See also there: Interim Report and 2nd Interim Report on Release 4, Evenden 1994).
-<P>
+<p>
 [2] <tt><a href="http://proj.maptools.org">PROJ.4</a></tt> Cartographic Projection Library
 
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
-<EM>
-<A HREF="v.proj.html">v.proj</A>,
-<A HREF="r.proj.html">r.proj</A>,
-<A HREF="g.proj.html">g.proj</A>,
-<A HREF="g.setproj.html">g.setproj</A>,
-<A HREF="i.rectify.html">i.rectify</A>,
-<!-- <A HREF="i.rectify3.html">i.rectify3</A> -->
-<A HREF="v.in.ascii.html">v.in.ascii</A>,
-<A HREF="v.out.ascii.html">v.out.ascii</A>
-</EM>
+<em>
+<a href="v.proj.html">v.proj</A>,
+<a href="r.proj.html">r.proj</A>,
+<a href="g.proj.html">g.proj</A>,
+<a href="g.setproj.html">g.setproj</A>,
+<a href="i.rectify.html">i.rectify</A>,
+<!-- <a href="i.rectify3.html">i.rectify3</A> -->
+<a href="v.in.ascii.html">v.in.ascii</A>,
+<a href="v.out.ascii.html">v.out.ascii</A>
+</em>
 
 
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
 
-M. Hamish Bowman, Dept. Marine Science, Otago University, New Zealand<BR>
+M. Hamish Bowman, Dept. Marine Science, Otago University, New Zealand<br>
 Functionality inspired by the <em>m.proj</em> and <em>m.proj2</em> modules for
 GRASS GIS 5.
 
-<p><i>Last changed: $Date$</i></p>
+<p><i>Last changed: $Date$</i>
 

Modified: grass/trunk/scripts/r.fillnulls/r.fillnulls.html
===================================================================
--- grass/trunk/scripts/r.fillnulls/r.fillnulls.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/scripts/r.fillnulls/r.fillnulls.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -73,7 +73,7 @@
 </em>
 
 <h2>REFERENCES</h2>
-<P> Mitas, L., Mitasova, H., 1999, Spatial Interpolation. In: P.Longley,
+<p> Mitas, L., Mitasova, H., 1999, Spatial Interpolation. In: P.Longley,
 M.F. Goodchild, D.J. Maguire, D.W.Rhind (Eds.), Geographical Information
 Systems: Principles, Techniques, Management and Applications, Wiley,
 pp.481-492
@@ -93,7 +93,7 @@
 II. Application to Terrain Modeling and Surface Geometry Analysis,
 <i>Mathematical Geology</i> 25, 657-667.
 
-<H2>AUTHORS</H2>
+<h2>AUTHORS</h2>
 r.fillnulls: Markus Neteler, University of Hannover<p>
 and authors of v.surf.rst<br>
 Improvement by Hamish Bowman, NZ

Modified: grass/trunk/scripts/r.in.aster/r.in.aster.html
===================================================================
--- grass/trunk/scripts/r.in.aster/r.in.aster.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/scripts/r.in.aster/r.in.aster.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -6,9 +6,9 @@
 <p>The program may be run interactively or non-interactively from the command 
   line. In either case, the user must specify an <b>input</b> *.hdf file name, 
   the <b>type</b> of processing used, the image <b>band</b> to import, and an 
-  <b>output</b> GRASS raster map name. </p>
-<p>The <b>type</b> paremeter can take values of L1A, L1B, or DEM. </p>
-<p>The <B>band</B> parameter can take values of 1, 2, 3n, 3b, 4-14</p>
+  <b>output</b> GRASS raster map name. 
+<p>The <b>type</b> paremeter can take values of L1A, L1B, or DEM. 
+<p>The <B>band</B> parameter can take values of 1, 2, 3n, 3b, 4-14
 
 
 <h2>NOTES</h2>

Modified: grass/trunk/scripts/r.in.srtm/r.in.srtm.html
===================================================================
--- grass/trunk/scripts/r.in.srtm/r.in.srtm.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/scripts/r.in.srtm/r.in.srtm.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -1,12 +1,12 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
-<EM>r.in.srtm</EM> imports SRTM hgt files into GRASS.
+<em>r.in.srtm</em> imports SRTM hgt files into GRASS.
 
 SRTM data sets can be downloaded from NASA at this FTP site (Version 1 and the
 improved Version 2):<br>
 <a href="ftp://e0srp01u.ecs.nasa.gov/srtm/">ftp://e0srp01u.ecs.nasa.gov/srtm/</a>
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 
 SRTM tiles are of 1 degree by 1 degree size. The SRTM filename contains the
 coordinates which refer to the <b>center</b> of the lower left pixel (e.g., N51E010: 
@@ -19,23 +19,23 @@
 
 To import TOPEX/SRTM30 PLUS data, use <em>r.in.bin</em>.
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
-<EM>
+<em>
 <a href="r.in.bin.html">r.in.bin</A>
-</EM>
+</em>
 <p>
 The <a href="http://www2.jpl.nasa.gov/srtm/">Shuttle Radar Topography Mission</a>
 homepage at NASA's JPL.
 <br>
 The <a href="http://pub7.bravenet.com/forum/537683448/">SRTM Web Forum</a>
 
-<H2>REFERENCES</H2>
+<h2>REFERENCES</h2>
 
 M. Neteler, 2005. <a href="http://grass.itc.it/newsletter/GRASSNews_vol3.pdf">SRTM and VMAP0 data in OGR and GRASS.</a> <i><a href="http://grass.itc.it/newsletter/">GRASS Newsletter</a></i>, Vol.3, pp. 2-6, June 2005. ISSN 1614-8746.
 
 
-<H2>AUTHORS</H2>
+<h2>AUTHORS</h2>
 
 Markus Neteler<br>
 Improved by W. Kyngesburye and H. Bowman

Modified: grass/trunk/scripts/r.mapcalculator/r.mapcalculator.html
===================================================================
--- grass/trunk/scripts/r.mapcalculator/r.mapcalculator.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/scripts/r.mapcalculator/r.mapcalculator.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -14,7 +14,7 @@
 
 <h2>SEE ALSO</h2>
 
-<em><A HREF="r.mapcalc.html">r.mapcalc</A></em>
+<em><a href="r.mapcalc.html">r.mapcalc</A></em>
 
 
 <h2>AUTHOR</h2>

Modified: grass/trunk/scripts/r.mask/r.mask.html
===================================================================
--- grass/trunk/scripts/r.mask/r.mask.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/scripts/r.mask/r.mask.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -86,8 +86,8 @@
 
 <h2>SEE ALSO</h2>
 <em>
-<a HREF="g.region.html">g.region</a>,
-<a HREF="r.mapcalc.html">r.mapcalc</a>,
+<a href="g.region.html">g.region</a>,
+<a href="r.mapcalc.html">r.mapcalc</a>,
 <a href="r.reclass.html">r.reclass</a>,
 <a href="g.remove.html">g.remove</a>,
 <a href="g.rename.html">g.rename</a>
@@ -98,4 +98,4 @@
 Michael Barton, Arizona State University
 
 <p>
-<i>Last changed: $Date$</i></p>
+<i>Last changed: $Date$</i>

Modified: grass/trunk/scripts/r.out.xyz/r.out.xyz.html
===================================================================
--- grass/trunk/scripts/r.out.xyz/r.out.xyz.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/scripts/r.out.xyz/r.out.xyz.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -29,7 +29,7 @@
 
 <h2>TODO</h2>
 
-Implement this script as a <EM>r.out.ascii</EM> option?
+Implement this script as a <em>r.out.ascii</em> option?
 
 
 <h2>SEE ALSO</h2>

Modified: grass/trunk/scripts/r.reclass.area/r.reclass.area.html
===================================================================
--- grass/trunk/scripts/r.reclass.area/r.reclass.area.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/scripts/r.reclass.area/r.reclass.area.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -17,9 +17,9 @@
 
 <h2>SEE ALSO</h2>
 
-<em><a HREF="r.reclass.html">r.reclass</a></em><br>
-<em><a HREF="r.clump.html">r.clump</a></em><br>
-<em><a HREF="r.stats.html">r.stats</a></em><br>
+<em><a href="r.reclass.html">r.reclass</a></em><br>
+<em><a href="r.clump.html">r.clump</a></em><br>
+<em><a href="r.stats.html">r.stats</a></em><br>
 
 <h2>AUTHORS</h2>
 

Modified: grass/trunk/scripts/r.shaded.relief/r.shaded.relief.html
===================================================================
--- grass/trunk/scripts/r.shaded.relief/r.shaded.relief.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/scripts/r.shaded.relief/r.shaded.relief.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -78,9 +78,9 @@
 and Jim Westervelt, U.S. Army Construction Engineering Research Laboratory
 (March/1991) (available from the GRASS web site).
 
-<P>
+<p>
 <!-- RGB version not ported to GRASS 6:
-  <EM><A HREF="shade.clr.sh.html">shade.clr.sh</A></EM><BR>
+  <em><a href="shade.clr.sh.html">shade.clr.sh</A></em><br>
  -->
 <em>
 <a href="d.his.html">d.his</a>,

Modified: grass/trunk/scripts/r.tileset/r.tileset.html
===================================================================
--- grass/trunk/scripts/r.tileset/r.tileset.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/scripts/r.tileset/r.tileset.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -63,7 +63,7 @@
 Generates tiles in latitude longitude that cover the current
 region, each tile will be less than 1024 cells high and 2048 cells
 across. The bounds and sizes of tiles in the output are separated by | (pipe):
-<p></p>
+<p>
 <div class="code"><pre>
 r.tileset sourceproj=+init=epsg:4326 maxrows=1024 maxcols=2048
 </pre></div>

Modified: grass/trunk/scripts/r3.mapcalculator/r3.mapcalculator.html
===================================================================
--- grass/trunk/scripts/r3.mapcalculator/r3.mapcalculator.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/scripts/r3.mapcalculator/r3.mapcalculator.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -14,7 +14,7 @@
 
 <h2>SEE ALSO</h2>
 
-<em><A HREF="r3.mapcalc.html">r3.mapcalc</A></em>
+<em><a href="r3.mapcalc.html">r3.mapcalc</A></em>
 
 
 <h2>AUTHOR</h2>

Modified: grass/trunk/scripts/v.centroids/v.centroids.html
===================================================================
--- grass/trunk/scripts/v.centroids/v.centroids.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/scripts/v.centroids/v.centroids.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -18,7 +18,7 @@
 example, represent a road between two parcels of land. In this case it
 is entirely appropriate for the boundary to contain category information.
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
 <em>
 <a href="v.category.html">v.category</a>

Modified: grass/trunk/scripts/v.db.droprow/v.db.droprow.html
===================================================================
--- grass/trunk/scripts/v.db.droprow/v.db.droprow.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/scripts/v.db.droprow/v.db.droprow.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -35,15 +35,15 @@
 <h2>SEE ALSO</h2>
 
 <em>
-<a HREF="db.droptable.html">db.droptable</a>,
-<a HREF="db.execute.html">db.execute</a>,
-<a HREF="v.db.addcolumn.html">v.db.addcolumn</a>,
-<a HREF="v.db.addtable.html">v.db.addtable</a>,
-<a HREF="v.db.connect.html">v.db.connect</a>,
-<a HREF="v.db.dropcol.html">v.db.dropcol</a>,
-<a HREF="v.db.droptable.html">v.db.droptable</a>,
-<a HREF="v.db.select.html">v.db.select</a>,
-<a HREF="v.db.update.html">v.db.update</a>
+<a href="db.droptable.html">db.droptable</a>,
+<a href="db.execute.html">db.execute</a>,
+<a href="v.db.addcolumn.html">v.db.addcolumn</a>,
+<a href="v.db.addtable.html">v.db.addtable</a>,
+<a href="v.db.connect.html">v.db.connect</a>,
+<a href="v.db.dropcol.html">v.db.dropcol</a>,
+<a href="v.db.droptable.html">v.db.droptable</a>,
+<a href="v.db.select.html">v.db.select</a>,
+<a href="v.db.update.html">v.db.update</a>
 </em>
 
 <h2>AUTHOR</h2>

Modified: grass/trunk/scripts/v.db.join/v.db.join.html
===================================================================
--- grass/trunk/scripts/v.db.join/v.db.join.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/scripts/v.db.join/v.db.join.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -67,9 +67,9 @@
 <h2>SEE ALSO</h2>
 
 <em>
-<a HREF="db.execute.html">db.execute</a>,
-<a HREF="db.in.ogr.html">db.in.ogr</a>,
-<a HREF="v.db.update.html">v.db.update</a><br>
+<a href="db.execute.html">db.execute</a>,
+<a href="db.in.ogr.html">db.in.ogr</a>,
+<a href="v.db.update.html">v.db.update</a><br>
 <a href="sql.html">GRASS SQL interface</a>
 </em>
 

Modified: grass/trunk/scripts/v.in.e00/v.in.e00.html
===================================================================
--- grass/trunk/scripts/v.in.e00/v.in.e00.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/scripts/v.in.e00/v.in.e00.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -9,14 +9,14 @@
 filename.e02 etc. The user must take care to download them all, the scripts
 automatically detects the presence of such multiple files.
 
-<H2>REFERENCES</H2>
+<h2>REFERENCES</h2>
 
 <a href="http://avce00.maptools.org">AVCE00 library</a> (providing 'avcimport' and 'e00conv')<br>
 <a href="http://www.gdal.org/ogr/">OGR vector library</a>
 
 <h2>SEE ALSO</h2>
 
-<em><a HREF="v.in.ogr.html">v.in.ogr</a></em>
+<em><a href="v.in.ogr.html">v.in.ogr</a></em>
 
 <h2>AUTHORS</h2>
 

Modified: grass/trunk/scripts/v.in.geonames/v.in.geonames.html
===================================================================
--- grass/trunk/scripts/v.in.geonames/v.in.geonames.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/scripts/v.in.geonames/v.in.geonames.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -44,8 +44,8 @@
 <h2>SEE ALSO</h2>
 
 <em>
-<a HREF="db.connect.html">db.connect</a>,
-<a HREF="v.select.html">v.select</a>
+<a href="db.connect.html">db.connect</a>,
+<a href="v.select.html">v.select</a>
 </em>
 
 <h2>REFERENCES</h2>

Modified: grass/trunk/scripts/v.in.gns/v.in.gns.html
===================================================================
--- grass/trunk/scripts/v.in.gns/v.in.gns.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/scripts/v.in.gns/v.in.gns.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -23,8 +23,8 @@
 <h2>SEE ALSO</h2>
 
 <em>
-<a HREF="db.connect.html">db.connect</a>,
-<a HREF="v.select.html">v.select</a>
+<a href="db.connect.html">db.connect</a>,
+<a href="v.select.html">v.select</a>
 </em>
 
 <h2>REFERENCES</h2>

Modified: grass/trunk/scripts/v.in.gps/v.in.gps.html
===================================================================
--- grass/trunk/scripts/v.in.gps/v.in.gps.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/scripts/v.in.gps/v.in.gps.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -79,7 +79,7 @@
 </em>
 
 <a href="http://www.gpsbabel.org">gpsbabel</a> from gpsbabel.org<br>
-cs2cs from <A HREF="http://trac.osgeo.org/proj/">PROJ.4</a>
+cs2cs from <a href="http://trac.osgeo.org/proj/">PROJ.4</a>
 
 <h2>AUTHORS</h2>
 Claudio Porta and Lucio Davide Spano, students of Computer Science at

Modified: grass/trunk/scripts/v.in.wfs/v.in.wfs.html
===================================================================
--- grass/trunk/scripts/v.in.wfs/v.in.wfs.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/scripts/v.in.wfs/v.in.wfs.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -23,7 +23,7 @@
 
 <h2>SEE ALSO</h2>
 
-<em><a HREF="v.in.ogr.html">v.in.ogr</a></em>
+<em><a href="v.in.ogr.html">v.in.ogr</a></em>
 
 <h2>AUTHORS</h2>
 

Modified: grass/trunk/scripts/v.out.gps/v.out.gps.html
===================================================================
--- grass/trunk/scripts/v.out.gps/v.out.gps.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/scripts/v.out.gps/v.out.gps.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -80,25 +80,25 @@
 </pre></div>
 
 
-<H2>SEE ALSO</H2>
-<EM>
-<A HREF="m.proj.html">m.proj</A><BR>
-<A HREF="v.in.ascii.html">v.in.ascii</A><BR>
-<A HREF="v.out.ascii.html">v.out.ascii</A><BR>
-<A HREF="v.in.garmin.html">v.in.garmin</A><BR>
-<A HREF="v.in.gpsbabel.html">v.in.gpsbabel</A><BR>
-<A HREF="v.db.renamecolumn.html">v.db.renamecolumn</A><BR>
-<A HREF="v.extract.html">v.extract</A>
-</EM>
-<BR>
-<BR>
+<h2>SEE ALSO</h2>
+<em>
+<a href="m.proj.html">m.proj</A><br>
+<a href="v.in.ascii.html">v.in.ascii</A><br>
+<a href="v.out.ascii.html">v.out.ascii</A><br>
+<a href="v.in.garmin.html">v.in.garmin</A><br>
+<a href="v.in.gpsbabel.html">v.in.gpsbabel</A><br>
+<a href="v.db.renamecolumn.html">v.db.renamecolumn</A><br>
+<a href="v.extract.html">v.extract</A>
+</em>
+<br>
+<br>
 
-<A HREF="http://www.gpsbabel.org">GpsBabel.org</a><BR>
-The <A HREF="http://www.gdal.org/ogr/drv_gpx.html">GDAL/OGR GPX format page</a><BR>
-cs2cs from <A HREF="http://proj.osgeo.org">PROJ.4</a><BR>
+<a href="http://www.gpsbabel.org">GpsBabel.org</a><br>
+The <a href="http://www.gdal.org/ogr/drv_gpx.html">GDAL/OGR GPX format page</a><br>
+cs2cs from <a href="http://proj.osgeo.org">PROJ.4</a><br>
 
 
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
 Hamish Bowman, Dunedin New Zealand
 
 <p>

Modified: grass/trunk/scripts/v.report/v.report.html
===================================================================
--- grass/trunk/scripts/v.report/v.report.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/scripts/v.report/v.report.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -1,4 +1,4 @@
-<h2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
 <em>v.report</em> generates a table showing the area present in 
 each of the categories of a user-selected data layer.
@@ -29,9 +29,9 @@
 <h2>SEE ALSO</h2>
 
 <em>
-<a HREF="v.in.region.html">v.in.region</a>,
-<a HREF="v.to.db.html">v.to.db</a>,
-<a HREF="v.overlay.html">v.overlay</a>
+<a href="v.in.region.html">v.in.region</a>,
+<a href="v.to.db.html">v.to.db</a>,
+<a href="v.overlay.html">v.overlay</a>
 </em>
 
 

Modified: grass/trunk/scripts/v.what.vect/v.what.vect.html
===================================================================
--- grass/trunk/scripts/v.what.vect/v.what.vect.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/scripts/v.what.vect/v.what.vect.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -12,11 +12,11 @@
 Use dmax parameter to control query distance tolerance (how far points/centroids
 can be from <b>qvector</b> features). For more options, use
 <em>v.distance</em> instead.
-<P>
+<p>
 In case of a multipoint input <b>vector</b> map, with several points having the
 same category number, it can happen, that the query result is NULL, if the same
 category number falls into different <b>qvector</b> polygons.
-<P>
+<p>
 When transferring attributes from a point map to a polygon map, usually <b>dmax</b>
 has to be larger than zero (determined by distance between query points and
 polygon centroids).
@@ -35,7 +35,7 @@
 # verification:
 v.db.select myhospitals
 </pre></div>
-<P>
+<p>
 
 In this example, city names, population data and more from
 <a href="http://download.geonames.org/export/dump/">Geonames.org country files</a> are
@@ -59,11 +59,11 @@
 <h2>SEE ALSO</h2>
 
 <em>
-<a HREF="v.db.addcolumn.html">v.db.addcolumn</a>,
-<a HREF="v.db.select.html">v.db.select</a>,
-<a HREF="v.distance.html">v.distance</a>,
-<a HREF="v.rast.stats.html">v.rast.stats</a>,
-<a HREF="v.what.rast.html">v.what.rast</a>
+<a href="v.db.addcolumn.html">v.db.addcolumn</a>,
+<a href="v.db.select.html">v.db.select</a>,
+<a href="v.distance.html">v.distance</a>,
+<a href="v.rast.stats.html">v.rast.stats</a>,
+<a href="v.what.rast.html">v.what.rast</a>
 </em>
 
 
@@ -72,4 +72,4 @@
 Markus Neteler
 
 <p>
-<i>Last changed: $Date$</i></p>
+<i>Last changed: $Date$</i>

Modified: grass/trunk/sites/s.in.ascii/s.in.ascii.html
===================================================================
--- grass/trunk/sites/s.in.ascii/s.in.ascii.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/sites/s.in.ascii/s.in.ascii.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -1,25 +1,25 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
 
-<EM>s.in.ascii</EM> converts an ASCII listing of site
+<em>s.in.ascii</em> converts an ASCII listing of site
 locations and category labels into GRASS vector format.
 
-<P>
+<p>
 
 Input can be entered via standard input or from the file
-<B>input=</B><EM>name</EM>. Each line of input should
+<B>input=</B><em>name</em>. Each line of input should
 contain the easting, northing, and either the category value
 or category label associated with a site.  The
-<B>fs=</B><EM>name</EM> option (where <EM>name</EM> is
+<B>fs=</B><em>name</em> option (where <em>name</em> is
 either a character, a space, or a tab) can be used to
 specify the use of a particular field separator between
 these three input fields. This is useful when input is
 obtained from other programs (see NOTES, below).  Output is
-stored in the vector map <B>output=</B><EM>name</EM>.
+stored in the vector map <B>output=</B><em>name</em>.
 
-<P>
+<p>
 
-The GRASS program <EM><a href="s.out.ascii.html">s.out.ascii</a></EM>
+The GRASS program <em><a href="s.out.ascii.html">s.out.ascii</a></em>
 can be used to perform the reverse function, converting a file in GRASS
 vector sites format into an ASCII listing of eastings, northings, and 
 category labels associated with site locations.
@@ -28,38 +28,38 @@
 <H3>Parameters:</H3>
 
 <DL>
-<DT><B>output=</B><EM>name</EM>
+<DT><B>output=</B><em>name</em>
 <DD>Name of the new GRASS site list file to be output. 
-<DT><B>input=</B><EM>name</EM>
+<DT><B>input=</B><em>name</em>
 <DD>Name of an existing ASCII file containing site locations and labels. 
-<DT><B>d=</B><EM>value</EM>
+<DT><B>d=</B><em>value</em>
 <DD>number of dimensions (default=2)
-<DT><B>fs=</B><EM>character|space|tab</EM>
+<DT><B>fs=</B><em>character|space|tab</em>
 <DD>The field separator separating the easting, northing, and category label 
-    in each line of the <EM>input</EM> file. 
+    in each line of the <em>input</em> file. 
     The field separator can be a character, a space, or a tab. 
-<BR>
+<br>
     Default: space 
-<DT><B>date=</B><EM>timestamp</EM>[/<EM>timestamp</EM>]
+<DT><B>date=</B><em>timestamp</em>[/<em>timestamp</em>]
 <DD>String specifying timestamp or timestamp range.
 </DL>
 
-<P>
+<p>
 
-<EM>s.in.ascii</EM> can be run either non-interactively or
+<em>s.in.ascii</em> can be run either non-interactively or
 interactively.  The program will be run non-interactively
 if the user specifies a name to be assigned to the
 <B>sites</B> file output, the name of an existing ASCII
 file containing <B>input</B>, and (optionally) a field
 separator <B>fs</B> appearing in the <B>input</B> file.
 
-<P>
+<p>
 
 Alternately, the user can simply type <B>s.in.ascii</B> on
 the command line, without program arguments. In this case,
 the user will be prompted for parameter values using the
 standard GRASS parser interface described in the manual
-entry for <EM><a href="parser.html">parser</a></EM>. If 
+entry for <em><a href="parser.html">parser</a></em>. If 
 the user does not specify the name of an <B>input</B> 
 file containing site locations and category attributes,
 these should be entered to the program via standard input. 
@@ -67,27 +67,27 @@
 than 2 dimensions will be imported. Otherwise the third (or 
 further) column in the <B>input</B> file will be treated as an attribute.
 
-<P>To define a <B>date</B> (timestamp), several date strings are accepted.
-Please see <EM><A HREF="r.timestamp.html">r.timestamp</A></EM> for details.
+<p>To define a <B>date</B> (timestamp), several date strings are accepted.
+Please see <em><a href="r.timestamp.html">r.timestamp</A></em> for details.
 
 <p>
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 
 <B>Importing from other GRASS programs</B>
 <p>
 Other GRASS programs can be used to produce output in a
-format suitable for input to <EM>s.in.ascii</EM>. For
+format suitable for input to <em>s.in.ascii</em>. For
 example, the user might pipe output produced by
-<EM><a href="d.where.html">d.where</a></EM> into 
-<EM>s.in.ascii</EM> to create a site
-list file called <EM>my.sites</EM> containing site
+<em><a href="d.where.html">d.where</a></em> into 
+<em>s.in.ascii</em> to create a site
+list file called <em>my.sites</em> containing site
 locations pointed to with the mouse, as illustrated below.
 In this example it is unnecessary to specify the field
-separator used in the input, since <EM>d.where</EM> output
+separator used in the input, since <em>d.where</em> output
 separates the easting and northing values with spaces, and
 spaces are the default field separator assumed by
-<EM>s.in.ascii</EM>.
-<P>
+<em>s.in.ascii</em>.
+<p>
 <DL>
 <DD><B>d.where</B> | <B>s.in.ascii output=</B>my.sites
 </DL>
@@ -96,7 +96,7 @@
 <p>
 Data may be imported from many spreadsheet programs by saving the spreadsheet
 as a comma separated variable (.csv) text file, and then using 
-the "<b>fs=</b><EM>,</EM>" command line parameter with <EM>s.in.ascii</EM>.
+the "<b>fs=</b><em>,</em>" command line parameter with <em>s.in.ascii</em>.
 <p>
 <b>Importing latitude/longitude data</b>
 <p>
@@ -131,15 +131,15 @@
 This data has three dimensions (assume easting, northing, and
 elevation),  five string attributes, and one decimal attribute.
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
-<EM><A HREF="d.vect.html">d.sites</A></EM>,
-<EM><A HREF="d.what.vect.html">d.what.vect</A></EM>,
-<EM><A HREF="d.where.html">d.where</A></EM>,
-<EM><A HREF="r.timestamp.html">r.timestamp</A></EM>,
-<EM><A HREF="s.out.ascii.html">s.out.ascii</A></EM>
+<em><a href="d.vect.html">d.sites</A></em>,
+<em><a href="d.what.vect.html">d.what.vect</A></em>,
+<em><a href="d.where.html">d.where</A></em>,
+<em><a href="r.timestamp.html">r.timestamp</A></em>,
+<em><a href="s.out.ascii.html">s.out.ascii</A></em>
 
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
 
 Michael Shapiro,  
 U.S. Army Construction Engineering 

Modified: grass/trunk/sites/s.out.ascii/s.out.ascii.html
===================================================================
--- grass/trunk/sites/s.out.ascii/s.out.ascii.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/sites/s.out.ascii/s.out.ascii.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -1,30 +1,30 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
-<EM>s.out.ascii</EM> converts an existing site list file
-(<B>input=</B><EM>name</EM>) into an ASCII listing of site
+<em>s.out.ascii</em> converts an existing site list file
+(<B>input=</B><em>name</em>) into an ASCII listing of site
 locations and (optionally) their category labels, in a
 format suitable for input to other program). 
 
-<P>
+<p>
 
 Each line of output consists of the easting, northing, and
 category label for a site listed in the named <B>vector points</B> (sites)
-file.  The <B>fs=</B><EM>name</EM> option (where
-<EM>name</EM> is either a character, a space, or a tab) can
+file.  The <B>fs=</B><em>name</em> option (where
+<em>name</em> is either a character, a space, or a tab) can
 be used to place a particular field separator between these
 three output fields. This is useful when output is to be
-manipulated by other programs, like <EM>awk</EM> or
-<EM>sed</EM>.
+manipulated by other programs, like <em>awk</em> or
+<em>sed</em>.
 
-<P>
+<p>
 
-The GRASS program <EM>s.in.ascii</EM> can be used to
+The GRASS program <em>s.in.ascii</em> can be used to
 perform the reverse function, converting a UNIX file
 containing eastings, northings, and category labels
 associated with site locations into GRASS site list file
 format.
 
-<H2>OPTIONS</H2>
+<h2>OPTIONS</h2>
 
 <H3>Flags:</H3>
 
@@ -46,7 +46,7 @@
 
 <DL>
 
-<DT><B>input=</B><EM>name</EM>
+<DT><B>input=</B><em>name</em>
 
 <DD>Name of an existing site list file. 
 
@@ -57,26 +57,26 @@
 output.  The field separator can be a character, a space,
 or a tab.
 
-<BR>
+<br>
 Default: space 
 </DL>
 
-<EM>s.out.ascii</EM> can be run either non-interactively or
+<em>s.out.ascii</em> can be run either non-interactively or
 interactively.  The program will be run non-interactively
 if the user specifies the name of an existing site list
 file and (optionally) a value for <B>fs</B>, using the form
 
-<P>
+<p>
 <DL>
 <DD>
 <B>s.out.ascii</B> 
 [<B>-adi</B>] 
-<B>input=</B><EM>name</EM> 
+<B>input=</B><em>name</em> 
 [<B>fs=</B>character|space|tab] 
 </DL>
 
 
-where <EM>name</EM> is the name of an existing site list
+where <em>name</em> is the name of an existing site list
 file to be converted to a brief ASCII listing, and
 <B>fs</B> is the field separator to be placed between
 output fields. The user can also the <B>-a</B> and
@@ -84,18 +84,18 @@
 <B>sites</B> file and to include site descriptions in the
 output.
 
-<P>
+<p>
 
 Alternately, the user can simply type <B>s.out.ascii</B> on
 the command line, without program arguments. In this case,
 the user will be prompted for parameter values using the
 standard GRASS 
 
-<A HREF="parser.html">parser</A>
+<a href="parser.html">parser</A>
 
 interface.
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 
 To output GRASS data in x,y,z ASCII style, the s.out.ascii may be used:
 <p>
@@ -118,32 +118,32 @@
 subsequently as described above.
 
 <p>
-The output from <EM>s.out.ascii</EM> may be placed into a
+The output from <em>s.out.ascii</em> may be placed into a
 file by using the UNIX redirection mechanism; e.g.:
 
-<P>
+<p>
 <DL>
 <DD>
 <B>s.out.ascii input=</B>archsites &gt; out.file
 </DL>
 
-<EM>s.out.ascii</EM> output may also be redirected into
+<em>s.out.ascii</em> output may also be redirected into
 other programs; e.g.:
 
-<P>
+<p>
 <DL>
 <DD>
 <B>s.out.ascii input=</B>archsites | d.points <B>color=</B>red <B>size=</B>10 <B>type=</B>diamond
 </DL>
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
-<EM><A HREF="d.points.html">d.points</A></EM><br>
-<EM><A HREF="d.vect.html">d.vect</A></EM><br>
-<EM><A HREF="s.in.ascii.html">s.in.ascii</A></EM><br>
-<EM><A HREF="r.to.vect.html">r.to.vect</A></EM>
+<em><a href="d.points.html">d.points</A></em><br>
+<em><a href="d.vect.html">d.vect</A></em><br>
+<em><a href="s.in.ascii.html">s.in.ascii</A></em><br>
+<em><a href="r.to.vect.html">r.to.vect</A></em>
 
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
 
 Michael Shapiro,  
 U.S. Army Construction Engineering 

Modified: grass/trunk/vector/v.buffer/v.buffer.html
===================================================================
--- grass/trunk/vector/v.buffer/v.buffer.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/vector/v.buffer/v.buffer.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -45,11 +45,11 @@
 <h2>SEE ALSO</h2>
 
 <em>
-<a HREF="r.buffer.html">r.buffer</a>,
-<a HREF="v.extract.html">v.extract</a>,
-<a HREF="v.type.html">v.type</a>,
-<a HREF="v.patch.html">v.patch</a>,
-<a HREF="v.db.connect.html">v.db.connect</a>
+<a href="r.buffer.html">r.buffer</a>,
+<a href="v.extract.html">v.extract</a>,
+<a href="v.type.html">v.type</a>,
+<a href="v.patch.html">v.patch</a>,
+<a href="v.db.connect.html">v.db.connect</a>
 </em>
 
 

Modified: grass/trunk/vector/v.build/v.build.html
===================================================================
--- grass/trunk/vector/v.build/v.build.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/vector/v.build/v.build.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -23,7 +23,7 @@
 v.build map=geology at PERMANENT
 </pre></div>
 
-<P>
+<p>
 In case of errors, the user can optionally generate an <em>error</em>
 vector map containing the erroneous vectors for later inspection.
 

Modified: grass/trunk/vector/v.category/v.category.html
===================================================================
--- grass/trunk/vector/v.category/v.category.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/vector/v.category/v.category.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -90,7 +90,7 @@
 </pre></div>
 
 Results can be tested
-using <em><a HREF="d.what.vect.html">d.what.vect</a></em>.
+using <em><a href="d.what.vect.html">d.what.vect</a></em>.
 
 <h3>Print vector categories of given layer</h3>
 

Modified: grass/trunk/vector/v.class/v.class.html
===================================================================
--- grass/trunk/vector/v.class/v.class.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/vector/v.class/v.class.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -1,4 +1,4 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
 <em>v.class</em> classifies vector attribute data into classes, for example for thematic mapping. Classification can be on a column or on an expression including several columns, all in the table linked to the vector map. The user indicates the number of classes desired and the algorithm to use for classification.
 
@@ -6,19 +6,19 @@
 
 It can be used to pipe class breaks into thematic mapping modules such as d.thematic.area (see example below);
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 
-<P>The <em>equal interval</em> algorithm simply divides the range max-min by the number of breaks to determine the interval between class breaks.</P>
+<p>The <em>equal interval</em> algorithm simply divides the range max-min by the number of breaks to determine the interval between class breaks.
 
-<P>The <em>quantiles</em> algorithm creates classes which all contain approximately the same number of observations.</P>
+<p>The <em>quantiles</em> algorithm creates classes which all contain approximately the same number of observations.
 
-<P>The <em>standard deviations</em> algorithm creates class breaks which are a combination of the mean +/- the standard deviation. It calculates a scale factor (<1) by which to multiply the standard deviation in order for all of the class breaks to fall into the range min-max of the data values.</P>
+<p>The <em>standard deviations</em> algorithm creates class breaks which are a combination of the mean +/- the standard deviation. It calculates a scale factor (<1) by which to multiply the standard deviation in order for all of the class breaks to fall into the range min-max of the data values.
 
-<P>The <em>equiprobabilites</em> algorithm creates classes that would be equiprobable if the distribution was normal. If some of the class breaks fall outside the range min-max of the data values, the algorithm prints a warning and reduces the number of breaks, but the probabilities used are those of the number of breaks asked for.</P>
+<p>The <em>equiprobabilites</em> algorithm creates classes that would be equiprobable if the distribution was normal. If some of the class breaks fall outside the range min-max of the data values, the algorithm prints a warning and reduces the number of breaks, but the probabilities used are those of the number of breaks asked for.
 
-<P>The <em>discont</em> algorithm systematically searches discontinuities in the slope of the cumulated frequencies curve, by approximating this curve through straight line segments whose vertices define the class breaks. The first approximation is a straight line which links the two end nodes of the curve. This line is then replaced by a two-segmented polyline whose central node is the point on the curve which is farthest from the preceding straight line. The point on the curve furthest from this new polyline is then chosen as a new node to create break up one of the two preceding segments, and so forth. The problem of the difference in terms of units between the two axes is solved by rescaling both amplitudes to an interval between 0 and 1. In the original algorithm, the process is stopped when the difference between the slopes of the two new segments is no longer significant (alpha = 0.05). As the slope is the ratio between the frequency and the amplitude of the correspon
 ding interval, i.e. its density, this effectively tests whether the frequencies of the two newly proposed classes are different from those obtained by simply distributing the sum of their frequencies amongst them in proportion to the class amplitudes. In the GRASS implementation, the algorithm continues, but a warning is printed.</P>
+<p>The <em>discont</em> algorithm systematically searches discontinuities in the slope of the cumulated frequencies curve, by approximating this curve through straight line segments whose vertices define the class breaks. The first approximation is a straight line which links the two end nodes of the curve. This line is then replaced by a two-segmented polyline whose central node is the point on the curve which is farthest from the preceding straight line. The point on the curve furthest from this new polyline is then chosen as a new node to create break up one of the two preceding segments, and so forth. The problem of the difference in terms of units between the two axes is solved by rescaling both amplitudes to an interval between 0 and 1. In the original algorithm, the process is stopped when the difference between the slopes of the two new segments is no longer significant (alpha = 0.05). As the slope is the ratio between the frequency and the amplitude of the correspon
 ding interval, i.e. its density, this effectively tests whether the frequencies of the two newly proposed classes are different from those obtained by simply distributing the sum of their frequencies amongst them in proportion to the class amplitudes. In the GRASS implementation, the algorithm continues, but a warning is printed.
 
-<H2>EXAMPLE</H2>
+<h2>EXAMPLE</h2>
 
 Classify column pop of map communes into 5 classes using quantiles:
 
@@ -38,13 +38,13 @@
 d.thematic.area -l map=communes2 data=pop/area breaks=`v.class -g map=communes2 column=pop/area algo=std nbcla=5` colors=0:0:255,50:100:255,255:100:50,255:0:0,156:0:0
 </pre></div>
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
-<EM><A HREF="v.univar.html">v.univar</A></EM>
-<EM><A HREF="d.thematic.area.html">d.area.thematic</A></EM>
+<em><a href="v.univar.html">v.univar</A></em>
+<em><a href="d.thematic.area.html">d.area.thematic</A></em>
 
 
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
 
 Moritz Lennert
 

Modified: grass/trunk/vector/v.clean/test/description.html
===================================================================
--- grass/trunk/vector/v.clean/test/description.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/vector/v.clean/test/description.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -4,8 +4,8 @@
 
 <h2>SEE ALSO</h2>
 
-<em><a HREF="v.clean.html">v.clean</a></em><br>
-<em><a HREF="v.build.html">v.build</a></em><br>
+<em><a href="v.clean.html">v.clean</a></em><br>
+<em><a href="v.build.html">v.build</a></em><br>
 
 <h2>AUTHOR</h2>
 

Modified: grass/trunk/vector/v.clean/v.clean.html
===================================================================
--- grass/trunk/vector/v.clean/v.clean.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/vector/v.clean/v.clean.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -190,7 +190,7 @@
 
 <h2>NOTES</h2>
 
-The user does <b>not</b> have to run <em><a HREF="v.build.html">v.build</a></em>
+The user does <b>not</b> have to run <em><a href="v.build.html">v.build</a></em>
 on the <em>output</em> vector, unless the <em>-b</em> flag was used. The
 <em>-b</em> flag affects <b>only</b> the <em>output</em> vector - 
 topology is always built for <em>error</em> vector.
@@ -205,7 +205,7 @@
 
 <h3>Cleaning OGR imported data (Simple Feature data)</h3>
 
-The import of areas with <em><a HREF="v.in.ogr.html">v.in.ogr</a> -c</em>
+The import of areas with <em><a href="v.in.ogr.html">v.in.ogr</a> -c</em>
 (no cleaning) requires a subsequent run of <em>v.clean</em> to update 
 the map to a topologically valid structure (removal of duplicate 
 collinear lines etc). The tools used for that are <em>bpol</em> and 
@@ -272,10 +272,10 @@
 <h2>SEE ALSO</h2>
 
 <em>
-<a HREF="v.info.html">v.info</a>,
-<a HREF="v.build.html">v.build</a>,
-<a HREF="v.digit.html">v.digit</a>,
-<a HREF="v.edit.html">v.edit</a>
+<a href="v.info.html">v.info</a>,
+<a href="v.build.html">v.build</a>,
+<a href="v.digit.html">v.digit</a>,
+<a href="v.edit.html">v.edit</a>
 </em>
 
 <h2>AUTHORS</h2>
@@ -284,4 +284,4 @@
 Radim Blazek, ITC-irst, Trento, Italy<br>
 Martin Landa, FBK-irst (formerly ITC-irst), Trento, Italy<br>
 
-<p><i>Last changed: $Date$</i></p>
+<p><i>Last changed: $Date$</i>

Modified: grass/trunk/vector/v.convert/v.convert.html
===================================================================
--- grass/trunk/vector/v.convert/v.convert.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/vector/v.convert/v.convert.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -7,15 +7,15 @@
 Vector maps from 5.0/5.3/5.4 and 5.7/6.x do not interfere. They are stored in different 
 directories, so you can use the same names. Old vector maps can be listed with
 <em>g.list oldvect</em>.
-<P>
+<p>
 If you need to convert back from 5.7/6.x into the 5.0/5.3/5.4 vector format,
 use <em>v.out.ogr</em> (to SHAPE format) and then <em>v.in.shape</em>
 in the old GRASS program.
 Alternatively use "<em>v.out.ascii -o</em>" and <em>v.in.ascii</em>.
-<P>
+<p>
 As this GRASS version uses SQL for attribute management, there are
 some <a href=sql.html>SQL restrictings concerning the file names</a>.
-<P>
+<p>
 Missing centroids can be added with <em>v.category</em>.
 
 <h2>EXAMPLE</h2>
@@ -25,12 +25,12 @@
 
 <h2>SEE ALSO</h2>
 
-<A HREF="g.list.html">g.list</A>,
-<A HREF="v.category.html">v.category</A>,
-<A HREF="v.convert.all.html">v.convert.all</A>,
-<A HREF="v.out.ascii.html">v.out.ascii</A>,
-<A HREF="v.in.ascii.html">v.in.ascii</A>,
-<A HREF="v.out.ogr.html">v.out.ogr</A>
+<a href="g.list.html">g.list</A>,
+<a href="v.category.html">v.category</A>,
+<a href="v.convert.all.html">v.convert.all</A>,
+<a href="v.out.ascii.html">v.out.ascii</A>,
+<a href="v.in.ascii.html">v.in.ascii</A>,
+<a href="v.out.ogr.html">v.out.ogr</A>
 
 
 <h2>AUTHOR</h2>

Modified: grass/trunk/vector/v.db.connect/v.db.connect.html
===================================================================
--- grass/trunk/vector/v.db.connect/v.db.connect.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/vector/v.db.connect/v.db.connect.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -7,7 +7,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.
 
 <p>
@@ -17,10 +17,10 @@
 
 <p>
 <b>Attention:</b> Removing a vector map will also delete all tables
-linked to it! If you use <a HREF="db.connect.html">v.db.connect </a>to
+linked to it! If you use <a href="db.connect.html">v.db.connect </a>to
 link further tables to your map, it is advisable to make a copy from
 those tables first and connect the copied tables to the vector map
-(see also <a HREF="v.overlay.html">v.overlay</a>).
+(see also <a href="v.overlay.html">v.overlay</a>).
 
 <h2>EXAMPLE</h2>
 
@@ -147,7 +147,7 @@
 </pre></div>
 
 An alternative is to create a "view" of only ID, x, y [,z] columns and
-to use <a HREF="v.in.db.html">v.in.db</a> on this view, then connect the original
+to use <a href="v.in.db.html">v.in.db</a> on this view, then connect the original
 table to the geometry. This will be faster if the original table
 is very large.
 
@@ -190,16 +190,16 @@
 <h2>SEE ALSO</h2>
 
 <em>
-<a HREF="db.connect.html">db.connect</a>,
-<a HREF="db.copy.html">db.copy</a>,
-<a HREF="db.tables.html">db.tables</a>,
-<a HREF="v.db.addtable.html">v.db.addtable</a>,
-<a HREF="v.db.droptable.html">v.db.droptable</a>,
-<a HREF="v.db.addcolumn.html">v.db.addcolumn</a>,
-<a HREF="v.db.dropcolumn.html">v.db.dropcolumn</a>,
-<a HREF="v.external.html">v.external</a>,
-<a HREF="v.in.db.html">v.in.db</a>,
-<a HREF="v.overlay.html">v.overlay</a>
+<a href="db.connect.html">db.connect</a>,
+<a href="db.copy.html">db.copy</a>,
+<a href="db.tables.html">db.tables</a>,
+<a href="v.db.addtable.html">v.db.addtable</a>,
+<a href="v.db.droptable.html">v.db.droptable</a>,
+<a href="v.db.addcolumn.html">v.db.addcolumn</a>,
+<a href="v.db.dropcolumn.html">v.db.dropcolumn</a>,
+<a href="v.external.html">v.external</a>,
+<a href="v.in.db.html">v.in.db</a>,
+<a href="v.overlay.html">v.overlay</a>
 </em>
 
 <h2>AUTHOR</h2>

Modified: grass/trunk/vector/v.db.select/v.db.select.html
===================================================================
--- grass/trunk/vector/v.db.select/v.db.select.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/vector/v.db.select/v.db.select.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -42,7 +42,7 @@
 
 <h2>SEE ALSO</h2>
 
-<em><a HREF="db.select.html">db.select</a></em>
+<em><a href="db.select.html">db.select</a></em>
 
 <h2>AUTHOR</h2>
 

Modified: grass/trunk/vector/v.delaunay/v.delaunay.html
===================================================================
--- grass/trunk/vector/v.delaunay/v.delaunay.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/vector/v.delaunay/v.delaunay.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -1,13 +1,13 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
-<EM>v.delaunay</EM> uses an existing vector points map (<B>input</B>)
+<em>v.delaunay</em> uses an existing vector points map (<B>input</B>)
 to create a Delaunay triangulation vector map (<B>output</B>).
-<P>
+<p>
 
-<BR>
+<br>
 Delaunay triangulation and Voronoi diagram example:
 <center>
-<img src=v_voronoi_delaunay.png border=1><BR>  <!-- installed by v.voronoi -->
+<img src=v_voronoi_delaunay.png border=1><br>  <!-- installed by v.voronoi -->
 <table border=0 width=590>
 <tr><td><center>
 <i>Delaunay Triangulation (left pane), Voronoi diagram (center pane),
@@ -17,7 +17,7 @@
 </center>
 
 
-<H2>EXAMPLE</H2>
+<h2>EXAMPLE</h2>
 
 Commands used with the Spearfish dataset to create the above figure.
 <div class="code"><pre>
@@ -43,27 +43,27 @@
 </pre></div>
 
 
-<H2>REFERENCES</H2>
-<EM>Leonid Guibas and Jorge Stolfi, (1985). 
+<h2>REFERENCES</h2>
+<em>Leonid Guibas and Jorge Stolfi, (1985). 
 Primitives for the 
 Manipulation of General Subdivisions and the Computation of
 Voronoi Diagrams, ACM Transactions on Graphics, Vol 4, No. 2, 
 April 1985, Pages 74-123
-</EM>
+</em>
 
 
-<H2>SEE ALSO</H2>
-<EM>
-<A HREF="v.voronoi.html">v.voronoi</A>, 
-<A HREF="v.hull.html">v.hull</A>
-</EM>
+<h2>SEE ALSO</h2>
+<em>
+<a href="v.voronoi.html">v.voronoi</A>, 
+<a href="v.hull.html">v.hull</A>
+</em>
 
 
-<H2>AUTHORS</H2>
+<h2>AUTHORS</h2>
 Martin Pavlovsky, Google Summer of Code 2008, Student<br>
 Paul Kelly, Mentor<br>
 Based on "dct" by Geoff Leach, Department of Computer Science, RMIT.<br>
 
 
 <p>
-<i>Last changed: $Date$</i></p>
+<i>Last changed: $Date$</i>

Modified: grass/trunk/vector/v.distance/v.distance.html
===================================================================
--- grass/trunk/vector/v.distance/v.distance.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/vector/v.distance/v.distance.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -1,17 +1,17 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
-<EM>v.distance</EM> finds the nearest element in vector map
+<em>v.distance</em> finds the nearest element in vector map
 (<em>to</em>) for elements in vector map (<em>from</em>). Various
 information about the vectors' relationships (distance, category, etc.) may be uploaded
 to the attribute table attached to the first vector map, or printed to
 'stdout'.  A new vector map may be created where lines connecting
 nearest points on features are written. <em>dmin</em> and/or <em>dmax</em> can be used to limit the search radius.
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 
 If a nearest feature does not have a category, the attribute column is updated
 to <em>null</em>.  This is true also for areas, which means for example,
-that if a point is in an island (area WITHOUT category), <EM>v.distance</EM> 
+that if a point is in an island (area WITHOUT category), <em>v.distance</em> 
 does not search for the nearest area WITH category; the island is identified 
 as the nearest and category updated to null.
 <p>
@@ -21,11 +21,11 @@
 and <em>to_along</em>) in meters not in degrees calculated as geodesic
 distances on a sphere.
 
-<h2>EXAMPLES</H2>
+<h2>EXAMPLES</h2>
 
 <H3>Find nearest lines</H3>
 
-Find <EM>nearest lines</EM> in vector map <B>ln</B> for points from
+Find <em>nearest lines</em> in vector map <B>ln</B> for points from
 vector map <B>pnt</B> within the given threshold and write related
 line categories to column <B>linecat</B> in an attribute table attached
 to vector map <B>pnt</B>:
@@ -36,7 +36,7 @@
 
 <H3>Find nearest area</H3>
 
-For each point from vector map <B>pnt</B>, find the <EM>nearest area</EM>
+For each point from vector map <B>pnt</B>, find the <em>nearest area</em>
 from map <B>ar</B> within the given threshold and write the related
 area categories to column <B>areacat</B> in an attribute table attached
 to vector map <B>pnt</B> (in the case that a point falls into a polygon area,
@@ -48,8 +48,8 @@
 
 <H3>Create a new vector map</H3>
 
-Create a new vector map which contains <EM>lines connecting nearest
-features</EM> of maps <B>pnt</B> and map <B>ln</B>. The resulting
+Create a new vector map which contains <em>lines connecting nearest
+features</em> of maps <B>pnt</B> and map <B>ln</B>. The resulting
 vector map can be used for example to connect points to a network as
 needed for network analysis:
 
@@ -59,7 +59,7 @@
 
 <H3>Query information</H3>
 
-Query information from selected point(s). <EM>v.distance</EM> takes
+Query information from selected point(s). <em>v.distance</em> takes
 points from a vector map as input instead of stdin. A new vector map
 with query points has to be created before the map can be analysed.
 <p>
@@ -82,7 +82,7 @@
 points not falling into any area, the category of the nearest area is
 recorded.
 <br>
-For each point from vector map <B>pnt</B>, find the <EM>area</EM> from
+For each point from vector map <B>pnt</B>, find the <em>area</em> from
 vector map <B>ar</B> in which the individual point falls, and
 write the related area categories to column <B>areacat</B> into
 the attribute table attached to vector map <B>pnt</B>:
@@ -128,24 +128,24 @@
 v.distance -pa from=archsites to=archsites upload=dist col=dist
 </pre></div>
 
-Note: Matrix-like output is enabled only for flag <EM>-a</EM> and one
+Note: Matrix-like output is enabled only for flag <em>-a</em> and one
 given upload option.
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
-<EM>
+<em>
 <a href="r.distance.html">r.distance</a>,
 <a href="v.db.addcolumn.html">v.db.addcolumn</a>,
 <a href="v.what.vect.html">v.what.vect</a>
-</EM>
+</em>
 
 
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
 
-Janne Soimasuo 1994, University of Joensuu, Faculty of Forestry, Finland<BR>
-Cmd line coordinates support: Markus Neteler, ITC-irst, Trento, Italy<BR>
-Updated for 5.1: Radim Blazek, ITC-irst, Trento, Italy<BR>
-Matrix-like output by Martin Landa, FBK-irst, Trento, Italy<BR>
+Janne Soimasuo 1994, University of Joensuu, Faculty of Forestry, Finland<br>
+Cmd line coordinates support: Markus Neteler, ITC-irst, Trento, Italy<br>
+Updated for 5.1: Radim Blazek, ITC-irst, Trento, Italy<br>
+Matrix-like output by Martin Landa, FBK-irst, Trento, Italy<br>
 Improved processing speed: Markus Metz
 
 <p><i>Last changed: $Date$</i>

Modified: grass/trunk/vector/v.drape/v.drape.html
===================================================================
--- grass/trunk/vector/v.drape/v.drape.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/vector/v.drape/v.drape.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -3,23 +3,23 @@
 <p><em>v.drape</em> converts 2D/3D vector data into 3D vector format via
 sampling of an elevation surface. Three sampling algorithms adapted
 from <a href="v.sample.html">v.sample</a> were incorporated into this
-module: nearest neighbor, bilinear, and cubic convultion.</p>
+module: nearest neighbor, bilinear, and cubic convultion.
 
 <p>v.drape will skip vector features outside of current computational region or
 where raster map has NULL value. It's possible to include all vector features
 by specifying height value that will be assigned to verticles whose values
-can not be determined from raster map.</p>
+can not be determined from raster map.
 
 <h2>NOTES</h2>
 <p>
 Additional vertices can be added to the input 2D vector map
-with <a href="v.split.html">v.split</a>.</p>
+with <a href="v.split.html">v.split</a>.
 
 <p>
 The module can be used in conjunction
 with <a href="v.out.pov.html">v.out.pov</a> and
 <a href="r.out.pov.html">r.out.pov</a> to export a complete set of
-vector and raster data for display in POVRAY.</p>
+vector and raster data for display in POVRAY.
 
 <h2>EXAMPLES</h2>
 

Modified: grass/trunk/vector/v.external/v.external.html
===================================================================
--- grass/trunk/vector/v.external/v.external.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/vector/v.external/v.external.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -65,7 +65,7 @@
 See <em><a href="v.db.connect.html">v.db.connect</a></em> for an example of
 maintaining attributes in external DBMS in also writeable mode.
 
-<H2>REFERENCES</H2>
+<h2>REFERENCES</h2>
 
 <a href="http://www.gdal.org/ogr/">OGR vector library</a>
 <br>

Modified: grass/trunk/vector/v.extract/v.extract.html
===================================================================
--- grass/trunk/vector/v.extract/v.extract.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/vector/v.extract/v.extract.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -17,7 +17,7 @@
 Only features with a category number will be extracted. So if you want to 
 extract boundaries (which are usually without category, as that information
 is normally held in the area's centroid) you must first use 
-<em><a HREF="v.category.html">v.category</a></em> to add them.
+<em><a href="v.category.html">v.category</a></em> to add them.
 
 <h2>EXAMPLES</h2>
 
@@ -122,10 +122,10 @@
 <h2>SEE ALSO</h2>
 
 <em>
-<a HREF="v.category.html">v.category</a>,
-<a HREF="v.dissolve.html">v.dissolve</a>,
-<a HREF="v.reclass.html">v.reclass</a>,
-<a HREF="sql.html">GRASS SQL interface</a>
+<a href="v.category.html">v.category</a>,
+<a href="v.dissolve.html">v.dissolve</a>,
+<a href="v.reclass.html">v.reclass</a>,
+<a href="sql.html">GRASS SQL interface</a>
 </em>
 
 <h2>AUTHORS</h2>

Modified: grass/trunk/vector/v.generalize/v.generalize.html
===================================================================
--- grass/trunk/vector/v.generalize/v.generalize.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/vector/v.generalize/v.generalize.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -53,7 +53,7 @@
 <li> <i>Douglas-Peucker</i> - "Quicksort" of line simplification, the 
      most widely used algorithm. Input parameters: <b>input</b>, 
      <b>threshold</b>. For more information, see: <br>
-     <A href="http://geometryalgorithms.com/Archive/algorithm_0205/algorithm_0205.htm">http://geometryalgorithms.com/Archive/algorithm_0205/algorithm_0205.htm</a>.</li>
+     <a href="http://geometryalgorithms.com/Archive/algorithm_0205/algorithm_0205.htm">http://geometryalgorithms.com/Archive/algorithm_0205/algorithm_0205.htm</a>.</li>
 <li> <i>Douglas-Peucker Reduction Algorithm</i> is essentially the same 
      algorithm as the algorithm above, the difference being that it takes 
      an additional <b>reduction</b> parameter which denotes the percentage 
@@ -63,7 +63,7 @@
 <li> <i>Lang</i> - Another standard algorithm. Input parameters: 
      <b>input</b>, <b>threshold</b>, <b>look_ahead</b>. 
      For an excellent description, see:  <br>
-     <A href="http://www.sli.unimelb.edu.au/gisweb/LGmodule/LGLangVisualisation.htm">http://www.sli.unimelb.edu.au/gisweb/LGmodule/LGLangVisualisation.htm</a>.</li>
+     <a href="http://www.sli.unimelb.edu.au/gisweb/LGmodule/LGLangVisualisation.htm">http://www.sli.unimelb.edu.au/gisweb/LGmodule/LGLangVisualisation.htm</a>.</li>
 <li> <i>Vertex Reduction</i> - Simplest among the algorithms. Input 
      parameters: <b>input</b>, <b>threshold</b>.
      Given a line, this algorithm removes the points of this line which 
@@ -75,7 +75,7 @@
      <b>threshold</b>. 
      This algorithm quite reasonably preserves the global characteristics 
      of the lines. For more information, see:  <br> 
-     <A href="http://www.ifp.uni-stuttgart.de/lehre/vorlesungen/GIS1/Lernmodule/Lg/LG_de_6.html">http://www.ifp.uni-stuttgart.de/lehre/vorlesungen/GIS1/Lernmodule/Lg/LG_de_6.html</a> (german).</li>
+     <a href="http://www.ifp.uni-stuttgart.de/lehre/vorlesungen/GIS1/Lernmodule/Lg/LG_de_6.html">http://www.ifp.uni-stuttgart.de/lehre/vorlesungen/GIS1/Lernmodule/Lg/LG_de_6.html</a> (german).</li>
 </ul>
 
 <i>Douglas-Peucker</i> and <i>Douglas-Peucker Reduction Algorithm</i> 

Modified: grass/trunk/vector/v.in.ascii/v.in.ascii.html
===================================================================
--- grass/trunk/vector/v.in.ascii/v.in.ascii.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/vector/v.in.ascii/v.in.ascii.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -226,7 +226,7 @@
 593549.3|4925500.7|442.6|mineralni pramen|mineral spring
 600375.7|4925235.6|342.2|kozi stezka|goat path
 </pre></div>
-<P>
+<p>
 Import into GRASS:
 <div class="code"><pre>
 #As the 'cat' option is set to 0 by default, an extra column 'cat'

Modified: grass/trunk/vector/v.in.db/v.in.db.html
===================================================================
--- grass/trunk/vector/v.in.db/v.in.db.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/vector/v.in.db/v.in.db.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -1,9 +1,9 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
 <em>v.in.db</em> 
 creates new vector (points) map from database table containing coordinates. 
 
-<H2>EXAMPLE</H2>
+<h2>EXAMPLE</h2>
 
 <h3>1) Creating a map from PostgreSQL table:</h3>
 
@@ -11,7 +11,7 @@
 v.in.db driver=pg database="host=myserver.itc.it,dbname=mydb" \
         table=pat_stazioni x=east y=north z=quota key=id output=pat_stazioni
 </pre></div>
-<P>
+<p>
 If an ID column is not not present in the PostgreSQL table,
 a new column should be added. See <a href="grass-pg.html">pg</a> driver
 page for detail.
@@ -23,7 +23,7 @@
 v.in.db driver=pg database="host=myserver.itc.it,dbname=mydb" \
         table=station x="x(geom)" y="y(geom)" z="z(geom)" key=id out=meteostations
 </pre></div>
-<P>
+<p>
 If an ID column is not not present in the PostgreSQL table,
 a new column should be added. See <a href="grass-pg.html">pg</a> driver 
 page for detail.
@@ -40,7 +40,7 @@
 v.info dtmpoints
 v.info -c dtmpoints
 </pre></div>
-<P>
+<p>
 If an ID column is missing in the DBF file, it has to be added beforehand, e.g. with OpenOffice.
 Alternatively, import the table with <em>db.in.ogr</em> into GRASS and then with <em>v.in.db</em>
 from the imported table (<em>db.in.ogr</em> optionally adds an unique ID column).
@@ -57,15 +57,15 @@
 v.info dtmpoints
 v.info -c dtmpoints
 </pre></div>
-<P>
+<p>
 If an ID column is missing in the table, it has to be added beforehand with 'sqlite3' or
 <em>db.execute</em>.
 
 
 <h3>5) Import of a points table (x, y, z) from DBF file to vector points map for selected points only:</h3>
-<P>
+<p>
 The user can import only selected vector points from a table using the <em>where</em> parameter
-(see above for general DBF handling):<P>
+(see above for general DBF handling):<p>
 <div class="code"><pre>
 v.in.db driver=dbf  database=/home/user/tables/ table=pointsfile x=x y=y z=z \
         key=idcol out=dtmpoints where="x NOT NULL and z > 100"
@@ -79,11 +79,11 @@
 <a href="v.info.html">v.info</a>,
 <a href="v.in.ogr.html">v.in.ogr</a>,
 <a href="v.to.db.html">v.to.db</a>,<br>
-<a HREF="sql.html">SQL support in GRASS GIS</a>
+<a href="sql.html">SQL support in GRASS GIS</a>
 </em>
 
 
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
 
 Radim Blazek
 

Modified: grass/trunk/vector/v.in.dwg/v.in.dwg.html
===================================================================
--- grass/trunk/vector/v.in.dwg/v.in.dwg.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/vector/v.in.dwg/v.in.dwg.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -11,7 +11,7 @@
 
 v.in.dwg requires OpenDWG toolkit. To get this toolkit you must become at
 least "Associate Member" of OpenDWG Alliance (http://www.opendesign.com/).
-<P>
+<p>
 The toolkit, for example <tt>ad27linx.tar</tt>, unpack in a directory
 (e.g. /home/usr1/opendwg27) and use the related <tt>configure</tt> options
 to tell GRASS about it:
@@ -25,7 +25,7 @@
 </pre></div>
 
 Then you can compile this module.
-<P>
+<p>
 Not all entity types are supported (warning printed).
 
 

Modified: grass/trunk/vector/v.in.lidar/v.in.lidar.html
===================================================================
--- grass/trunk/vector/v.in.lidar/v.in.lidar.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/vector/v.in.lidar/v.in.lidar.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -8,11 +8,11 @@
 The compressed LAS format can be imported only if libLAS has been compiled 
 with laszip support. It is also recommended to compile libLAS with GDAL, 
 needed to text for matching projections.
-<P>
+<p>
 For larger datasets, it is recommended to not build topology (-b flag).
 Also, creating a table with attributes can take some time for larger datasets.
 
-<P>
+<p>
 The optional <b>spatial</b> parameter defines spatial query extents.
 This parameter allows the user to restrict the region to a spatial subset
 while importing the data. All LiDAR points falling into this rectangle 
@@ -20,7 +20,7 @@
 but uses the current region settings as the spatial bounds 
 (see <em><a href="g.region.html">g.region</a></em>).
 
-<H2>Location Creation</H2>
+<h2>Location Creation</h2>
 
 <em>v.in.lidar</em> attempts to preserve projection information when importing
 datasets if the source format includes projection information, and if
@@ -30,12 +30,12 @@
 match current location</tt>") and then report the PROJ_INFO parameters of
 the source dataset.
 
-<P>
+<p>
 If the user wishes to ignore the difference between the apparent coordinate
 system of the source data and the current location, they may pass the 
 <b>-o</b> flag to override the projection check.
 
-<P>
+<p>
 If the user wishes to import the data with the full projection definition,
 it is possible to have <em>v.in.lidar</em> automatically create a new location based
 on the projection and extents of the file being read.  This is accomplished
@@ -45,7 +45,7 @@
 imported with the indicated <b>output</b> name into the PERMANENT mapset.
 
 
-<H2>REFERENCES</H2>
+<h2>REFERENCES</h2>
 
 <a href="http://www.asprs.org/a/society/committees/standards/lidar_exchange_format.html">
 ASPRS LAS format</a><br>

Modified: grass/trunk/vector/v.in.ogr/v.in.ogr.html
===================================================================
--- grass/trunk/vector/v.in.ogr/v.in.ogr.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/vector/v.in.ogr/v.in.ogr.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -5,12 +5,12 @@
 OGR (Simple Features Library) is part of the 
 <a href="http://www.gdal.org">GDAL</a> library, so you need to
 install GDAL to use <em>v.in.ogr</em>. 
-<P>
+<p>
 If the <b>layer</b> parameter is not given, all available layers 
 are imported as separate GRASS layers into one GRASS vector map. If
 several OGR layer names are given, all these layers are imported as
 separate GRASS layers into one GRASS vector map.
-<P>
+<p>
 The optional <b>spatial</b> parameter defines spatial query extents.
 This parameter allows the user to restrict the region to a spatial subset
 while importing the data. All vector features completely or partially
@@ -38,7 +38,7 @@
 <a href="http://www.gdal.org/ogr/ogr_formats.html">OGR web site</a>.
 
 
-<H2>Location Creation</H2>
+<h2>Location Creation</h2>
 
 <em>v.in.ogr</em> attempts to preserve projection information when importing
 datasets if the source format includes projection information, and if
@@ -48,12 +48,12 @@
 match current location</tt>") and then report the PROJ_INFO parameters of
 the source dataset.
 
-<P>
+<p>
 If the user wishes to ignore the difference between the apparent coordinate
 system of the source data and the current location, they may pass the 
 <b>-o</b> flag to override the projection check.
 
-<P>
+<p>
 If the user wishes to import the data with the full projection definition,
 it is possible to have <em>v.in.ogr</em> automatically create a new location based
 on the projection and extents of the file being read.  This is accomplished
@@ -77,23 +77,23 @@
 <div class="code"><pre>
 v.in.ogr dsn=/home/user/shape_data layer=test_shape output=grass_map 
 </pre></div>
-<BR>
+<br>
 
 <li><B>MapInfo files</B>
 <div class="code"><pre>
 v.in.ogr dsn=./ layer=mapinfo_test output=grass_map
 </pre></div>
-<BR>
+<br>
 
-<li><B>Arc Coverage</B><BR>
+<li><B>Arc Coverage</B><br>
  We import the Arcs and Label points, the module takes care to
  build areas:<br>
 <div class="code"><pre>
 v.in.ogr dsn=gemeinden layer=LAB,ARC type=centroid,boundary output=mymap
 </pre></div>
-<BR>
+<br>
 
-<li><B>E00 file</B> (see also <em><a href="v.in.e00.html">v.in.e00</a></em>)<BR>
+<li><B>E00 file</B> (see also <em><a href="v.in.e00.html">v.in.e00</a></em>)<br>
  First we have to convert the E00 file to an Arc Coverage with 'avcimport' 
  (<a href="http://avce00.maptools.org/avce00/index.html">AVCE00 tools</a>,
  use <em>e00conv</em> first in case that <em>avcimport</em> fails):<br>
@@ -101,29 +101,29 @@
 avcimport e00file coverage
 v.in.ogr dsn=coverage layer=LAB,ARC type=centroid,boundary output=mymap
 </pre></div>
-<BR>
+<br>
 
-<li><B>SDTS files</B> (you have to select the CATD file)<BR>
+<li><B>SDTS files</B> (you have to select the CATD file)<br>
 <div class="code"><pre>
 v.in.ogr dsn=CITXCATD.DDF output=cities
 </pre></div>
-<BR>
+<br>
 
-<li><B>TIGER files</B><BR>
+<li><B>TIGER files</B><br>
 <div class="code"><pre>
 v.in.ogr dsn=input/2000/56015/ layer=CompleteChain,PIP output=t56015_all \
 type=boundary,centroid snap=-1
 </pre></div>
-<BR>
+<br>
 
-<li><B>PostGIS maps</B> (area example)<BR>
+<li><B>PostGIS maps</B> (area example)<br>
 <div class="code"><pre>
 v.in.ogr dsn="PG:host=localhost dbname=postgis user=postgres" layer=polymap \
 output=polygons type=boundary,centroid
 </pre></div>
-<BR>
+<br>
 
-<li><B>Oracle Spatial maps </B><BR>
+<li><B>Oracle Spatial maps </B><br>
 Note that you have to set the environment-variables <tt>ORACLE_BASE,
 ORACLE_SID, ORACLE_HOME</tt> and <tt>TNS_ADMIN</tt> accordingly.
 <div class="code"><pre>
@@ -133,11 +133,11 @@
 
 <h3>Support of database schema:</h3>
 
-<P>
+<p>
 For schema support, first set a default schema with 
 <em><a href="db.connect.html">db.connect</a></em>. If schema support is
 used the schema name must be specified whenever a db.* module is called.
-<P>
+<p>
 Example:
 <div class="code"><pre>
 db.connect driver=pg database=test schema=user1 group=group1
@@ -171,7 +171,7 @@
 if the attribute table is stored in a SQL DBMS such as PostgreSQL).
 The <b>cnames</b> parameter is used to define new column names during import.
 
-<P>
+<p>
 The DBF database specification limits column names to 10 characters.
 If the default DB is set to DBF and the input data contains longer
 column/field names, they will be truncated. If this results in multiple
@@ -207,7 +207,7 @@
 upon the projection information in the file. If desired, you can then re-project
 it to another location with <em>v.proj</em>.
 
-<H2>REFERENCES</H2>
+<h2>REFERENCES</h2>
 
 <a href="http://www.gdal.org/ogr/">OGR vector library</a> <br>
 <a href="http://www.gdal.org/ogr/ogr__api_8h.html">OGR vector library C API</a> documentation
@@ -216,15 +216,15 @@
 <h2>SEE ALSO</h2>
 
 <em>
-<a HREF="db.connect.html">db.connect</a>,
-<a HREF="v.clean.html">v.clean</a>,
-<a HREF="v.build.polylines.html">v.build.polylines</a>,
-<a HREF="v.edit.html">v.edit</a>,
-<a HREF="v.external.html">v.external</a>,
+<a href="db.connect.html">db.connect</a>,
+<a href="v.clean.html">v.clean</a>,
+<a href="v.build.polylines.html">v.build.polylines</a>,
+<a href="v.edit.html">v.edit</a>,
+<a href="v.external.html">v.external</a>,
 <a href="v.in.db.html">v.in.db</a>,
 <a href="v.in.e00.html">v.in.e00</a>,
-<a HREF="v.out.ogr.html">v.out.ogr</a>,<br>
-<a HREF="grass-pg.html">PostGIS driver</a>
+<a href="v.out.ogr.html">v.out.ogr</a>,<br>
+<a href="grass-pg.html">PostGIS driver</a>
 </em>
 
 

Modified: grass/trunk/vector/v.in.region/v.in.region.html
===================================================================
--- grass/trunk/vector/v.in.region/v.in.region.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/vector/v.in.region/v.in.region.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -4,8 +4,8 @@
 
 <h2>SEE ALSO</h2>
 
-<em><a HREF="g.region.html">g.region</a></em><br>
-<em><a HREF="d.vect.html">d.vect</a></em><br>
+<em><a href="g.region.html">g.region</a></em><br>
+<em><a href="d.vect.html">d.vect</a></em><br>
 
 <h2>AUTHOR</h2>
 

Modified: grass/trunk/vector/v.info/v.info.html
===================================================================
--- grass/trunk/vector/v.info/v.info.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/vector/v.info/v.info.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -154,4 +154,4 @@
 Updated to GRASS 7 by Martin Landa, CTU in Prague, Czech Republic
 
 <p>
-<i>Last changed: $Date$</i></p>
+<i>Last changed: $Date$</i>

Modified: grass/trunk/vector/v.kcv/v.kcv.html
===================================================================
--- grass/trunk/vector/v.kcv/v.kcv.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/vector/v.kcv/v.kcv.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -1,4 +1,4 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
        <I>v.kcv</I>  randomly  divides  a  points  lists  into  <I>k</I> sets of
        test/train data (for <B>k</B>-fold <B>c</B>ross <B>v</B>alidation).
        Test  partitions  are  mutually  exclusive.  That  is,  a point will
@@ -17,7 +17,7 @@
        testing).  This  process of filling up a test partition is
        done <I>k</I> times.
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
        An ideal random sites generator will follow a Poisson dis
       <!-- BUG: missing text -->
        only be as random as the  original  points.   This  program
@@ -28,21 +28,21 @@
 
        This program may not work properly with Lat-long data.
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 <I><a href=v.random.html>v.random</a></I> and 
 <I><a href=g.region.html>g.region</a></I>
 
 
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
 
-<A HREF="http://mccauley-usa.com/">James Darrell McCauley</A>
-<A HREF="mailto:darrell at mccauley-usa.com">&lt;darrell at mccauley-usa.com&gt;</A>,
+<a href="http://mccauley-usa.com/">James Darrell McCauley</A>
+<a href="mailto:darrell at mccauley-usa.com">&lt;darrell at mccauley-usa.com&gt;</A>,
 <br>when he was at: 
-<A HREF="http://ABE.www.ecn.purdue.edu/ABE/">Agricultural
+<a href="http://ABE.www.ecn.purdue.edu/ABE/">Agricultural
 Engineering</A>
-<A HREF="http://www.purdue.edu/">Purdue University</A>
+<a href="http://www.purdue.edu/">Purdue University</A>
 
-<P>
+<p>
 Update to 5.7 Radim Blazek 10 / 2004
 
 <p><i>Last changed: $Date$</i>

Modified: grass/trunk/vector/v.kernel/v.kernel.html
===================================================================
--- grass/trunk/vector/v.kernel/v.kernel.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/vector/v.kernel/v.kernel.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -1,4 +1,4 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
 <em>v.kernel</em> generates a raster density map from vector points data using
 a moving kernel. Available <a href="http://en.wikipedia.org/wiki/Kernel_(statistics)#Kernel_functions_in_common_use">kernel density functions</a> are <em>uniform, 
@@ -12,36 +12,36 @@
 method uses the kernel function selected with the <em>kernel</em> option 
 and can be enabled with <em>node=split</em>.
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 
 The <em>mult</em> option is needed to overcome the limitation that
 the resulting density in case of a vector map output is stored as category
 (Integer). The density result stored as category may be multiplied by this number.
-<P>
+<p>
 With the <em>-o</em> flag (experimental) the command tries to calculate an 
 optimal standard deviation. The value of <em>stddeviation</em> is taken 
 as maximum value. Standard deviation is calculated using ALL points, 
 not just those in the current region.
 
 
-<H2>LIMITATIONS</H2>
+<h2>LIMITATIONS</h2>
 The module only considers the presence of points, but not 
 (yet) any attribute values.
 
-<H2>SEE ALSO</H2>
-<A HREF="v.surf.rst.html">v.surf.rst</A>
+<h2>SEE ALSO</h2>
+<a href="v.surf.rst.html">v.surf.rst</A>
 
-<H2>REFERENCES</H2>
+<h2>REFERENCES</h2>
 Okabe, A., Satoh, T., Sugihara, K. (2009). <i>A kernel density estimation 
 method for networks, its computational method and a GIS-based tool</i>.
 <b>International Journal of Geographical Information Science</b>, Vol 23(1), 
 pp. 7-32.<br>
 DOI: <a href="http://dx.doi.org/10.1080/13658810802475491">10.1080/13658810802475491</a>
 
-<H2>AUTHORS</H2>
+<h2>AUTHORS</h2>
 
 Stefano Menegon, <a href="http://mpa.itc.it/">ITC-irst</a>, Trento, Italy
-<BR>
+<br>
 Radim Blazek (additional kernel density functions and network part)
 
 <p><i>Last changed: $Date$</i>

Modified: grass/trunk/vector/v.label/v.label.html
===================================================================
--- grass/trunk/vector/v.label/v.label.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/vector/v.label/v.label.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -1,26 +1,26 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
-<EM>v.label</EM> makes a label-file from a GRASS vector map
+<em>v.label</em> makes a label-file from a GRASS vector map
 with labels created from attributes in the attached table.
 If no label file name is given, the name of the source map is used.
 
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 
 If the <em>fontsize</em> option is given then the <em>space</em> option
 is determined automatically <em>from the current display window</em>, 
 otherwise the <em>space</em> option should be set roughly the same
 as the <em>size</em> option.
-<P>
+<p>
 
-<BR>
-A description of the labels file follows.<P> 
+<br>
+A description of the labels file follows.<p> 
 The file is located in <tt>$MAPSET/paint/labels/</tt>.
 The file is a plain-text ASCII file containing the following fields:
-<BR>
+<br>
 <h4>Caution: The following information may be incomplete, out of date, 
 and wrong!</h4>
-<P>
+<p>
 The label information that must be provided in the <em>labels</em> file is:
 
 <DL>
@@ -29,15 +29,15 @@
 <DD><!--Up to four lines of text.-->
 Lines in multiple line labels will appear one above the next.
 More than one line of text can be specified by notating the end of a 
-line with a '<b><tt>\n</tt></b>'.<BR>
+line with a '<b><tt>\n</tt></b>'.<br>
 (e.g. <tt>SPEARFISH<b>\n</b>SOUTH DAKOTA)</tt>.
 
 
 <!-- I don't think it exists. -HB 6/2005
 <DT><B>SKIP</B>:
 
-<DD>yes|no. If <EM>no</EM>, label will be printed.  If
-<EM>yes</EM>, the label will be retained in the file but
+<DD>yes|no. If <em>no</em>, label will be printed.  If
+<em>yes</em>, the label will be retained in the file but
 not printed.
 -->
 
@@ -58,7 +58,7 @@
 
 <DD>Determines which part of the label to which the
 location refers.  If placement is unspecified, the label is
-centered (<EM>center</EM>), by default.  Label placement
+centered (<em>center</em>), by default.  Label placement
 may be specified as:
 
 <PRE>
@@ -78,21 +78,21 @@
 <DT><B>FONT</B>:
 
 <DD>This specifies the font to use.
-<P>
+<p>
 The following fonts are available for use with
   <a href="d.labels.html"><i>d.labels</i></a>:
-<P><pre>
+<p><pre>
   cyrilc gothgbt gothgrt gothitt greekc greekcs greekp greeks
   italicc italiccs italict romanc romancs romand romans romant
   scriptc scripts
 </pre>
-<P>
+<p>
 Alternatively the path to a FreeType (.ttf) font may be given.
 (for <em>d.labels</em> only)
-<P>
-The word <EM>standard</EM> can be used to specify the default font 
-(which is <EM>romans</EM>).
-<P>
+<p>
+The word <em>standard</em> can be used to specify the default font 
+(which is <em>romans</em>).
+<p>
 Note <a href="ps.map.html"><em>ps.map</em></a> can override this setting
 to use other fonts. Its default font is Helvetica.
 
@@ -109,30 +109,30 @@
 <DT><A NAME="textcolor"><B>TEXT COLOR</B></A>:
 
 <DD>This selects the text color.  If unspecified, the
-label's text is drawn in <EM>black</EM>, by default.  The
+label's text is drawn in <em>black</em>, by default.  The
 text color can be specified in one of several ways:
 
 <OL>
 <LI>By color name:
 
-<BR>
+<br>
 <tt>aqua black blue brown cyan gray green grey indigo
 magenta orange purple red violet white yellow</tt>
 
-<LI>As red, green, blue component values. (0-255)<BR>
+<LI>As red, green, blue component values. (0-255)<br>
 for example: <tt>128:100:200</tt>
 
 <!-- eh?
 <LI>As red, green, blue percentages.
 for example: .5 .4 .7
-<BR>
+<br>
 (This form is not supported by 
-<EM><A HREF="d.labels.html">d.labels</A></EM>.)
+<em><a href="d.labels.html">d.labels</A></em>.)
 
 <LI>By printer color number to get the exact printer color.
-<BR>
+<br>
 (This form is not supported by 
-<EM><A HREF="d.labels.html">d.labels</A></EM>.)
+<em><a href="d.labels.html">d.labels</A></em>.)
 -->
 
 <LI>Specify "<tt>none</tt>" to suppress the lettering.
@@ -141,7 +141,7 @@
 
 <DT><B>WIDTH</B>:
 
-<DD>This determines the line thickness of the border box.<BR>
+<DD>This determines the line thickness of the border box.<br>
 The maximum value is 25.0.
 
 <DT><B>HIGHLIGHT COLOR</B>:
@@ -153,7 +153,7 @@
 ("<tt>none</tt>") is used by default, if unspecified by the
 user.  To specify use of no highlight color, specify
 "<tt>none</tt>".
-(See <A HREF="#textcolor">TEXT COLOR</A>
+(See <a href="#textcolor">TEXT COLOR</A>
 above for a list of permissible color names.)
 
 
@@ -161,7 +161,7 @@
 
 <DD>Specifies how far from the text lines (in units of
 pixels) the highlight color should extend.  The default
-highlight width is set to <EM>0</EM> (i.e., no highlight
+highlight width is set to <em>0</em> (i.e., no highlight
 color).
 
 
@@ -169,8 +169,8 @@
 
 <DD>Text may be boxed in a solid color by specifying a background color.
 Specify "<tt>none</tt>" for no background.  The default background color
-setting, if unspecified by the user, is <EM>white</EM>.
-(See <A HREF="#textcolor">TEXT COLOR</A>
+setting, if unspecified by the user, is <em>white</em>.
+(See <a href="#textcolor">TEXT COLOR</A>
 above for a list of permissible color names.)
 
 
@@ -178,25 +178,25 @@
 
 <DD>Select a color for the border around the background.
 Specify "<tt>none</tt>" to suppress the border.
-The default border color used, if unspecified, is <EM>black</EM>.
-(See <A HREF="#textcolor">TEXT COLOR</A>
+The default border color used, if unspecified, is <em>black</em>.
+(See <a href="#textcolor">TEXT COLOR</A>
 above for a list of permissible color names.)
 
 
 <DT><B>OPAQUE TO VECTORS</B>:
 
-<DD><EM>yes|no</EM>.  This field only has meaning if a
-background color is selected.  <EM>yes</EM> will prevent
-vector lines from entering the background.  <EM>no</EM>
+<DD><em>yes|no</em>.  This field only has meaning if a
+background color is selected.  <em>yes</em> will prevent
+vector lines from entering the background.  <em>no</em>
 will allow vector lines to enter the background.  The
 default setting, if unspecified by the user, is
-<EM>yes</EM>.
+<em>yes</em>.
 
 </DL>
-<BR>
+<br>
 
 
-<H2>EXAMPLE</H2>
+<h2>EXAMPLE</h2>
 
 Spearfish example with TrueType font (path may differ):
 
@@ -219,19 +219,19 @@
 
 
 
-<H2>SEE ALSO</H2>
-<EM>
-<A HREF="d.labels.html">d.labels</A><br>
-<A HREF="ps.map.html">ps.map</A>
-</EM>
+<h2>SEE ALSO</h2>
+<em>
+<a href="d.labels.html">d.labels</A><br>
+<a href="ps.map.html">ps.map</A>
+</em>
 <br>
 
 
-<H2>AUTHORS</H2>
+<h2>AUTHORS</h2>
 
 Philip Verhagen (original s.label)<br>
 Radim Blazek (GRASS 6 port)<br>
-Hamish Bowman (enhancements)<BR>
+Hamish Bowman (enhancements)<br>
 
 <p>
 <i>Last changed: $Date$</i>

Modified: grass/trunk/vector/v.label.sa/v.label.sa.html
===================================================================
--- grass/trunk/vector/v.label.sa/v.label.sa.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/vector/v.label.sa/v.label.sa.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -1,12 +1,12 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
-<EM>v.label.sa</EM> makes a label-file from a GRASS vector map
+<em>v.label.sa</em> makes a label-file from a GRASS vector map
 with labels created from attributes in the attached table. The labels are
 placed in as optimal place as possible. The label file has the same syntax
-as the one created by <A HREF="v.label.html">v.label</A>
+as the one created by <a href="v.label.html">v.label</A>
 
 
-<H2>EXAMPLE</H2>
+<h2>EXAMPLE</h2>
 
 North Carolina example:
 <p>
@@ -33,20 +33,20 @@
 </center>
 
 
-<H2>REFERENCES</H2>
+<h2>REFERENCES</h2>
 Edmondson, Christensen, Marks and Shieber: A General Cartographic
 Labeling Algorithm, Cartographica, Vol. 33, No. 4, Winter 1996, pp. 13-23
 The algorithm works by the principle of Simulated Annealing.
 
-<H2>SEE ALSO</H2>
-<EM>
-<A HREF="v.labels.html">d.label</A><br>
-<A HREF="d.labels.html">d.labels</A><br>
-<A HREF="ps.map.html">ps.map</A>
-<A href="http://en.wikipedia.org/wiki/Simulated_Annealing">Wikipedia article on simulated annealing</A>
-</EM><br>
+<h2>SEE ALSO</h2>
+<em>
+<a href="v.labels.html">d.label</A><br>
+<a href="d.labels.html">d.labels</A><br>
+<a href="ps.map.html">ps.map</A>
+<a href="http://en.wikipedia.org/wiki/Simulated_Annealing">Wikipedia article on simulated annealing</A>
+</em><br>
 
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
 Wolf Bergenheim
 <br>
 <p><i>Last changed: $Date$</i>

Modified: grass/trunk/vector/v.lidar.correction/v.lidar.correction.html
===================================================================
--- grass/trunk/vector/v.lidar.correction/v.lidar.correction.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/vector/v.lidar.correction/v.lidar.correction.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -61,17 +61,17 @@
 </pre></div>
 
 <h2>SEE ALSO</h2>
-<em><a HREF="v.lidar.edgedetection.html">v.lidar.edgedetection</a></em>,
-<em><a HREF="v.lidar.growing.html">v.lidar.growing</a></em>,
-<em><a HREF="v.surf.bspline.html">v.surf.bspline</a></em>
+<em><a href="v.lidar.edgedetection.html">v.lidar.edgedetection</a></em>,
+<em><a href="v.lidar.growing.html">v.lidar.growing</a></em>,
+<em><a href="v.surf.bspline.html">v.surf.bspline</a></em>
 
 <h2>AUTHORS</h2>
 Original version of program in GRASS 5.4:
-<BR>
+<br>
 Maria Antonia Brovelli, Massimiliano Cannata, Ulisse Longoni and Mirko Reguzzoni
-<BR><BR>
+<br><br>
 Update for GRASS 6.X:
-<BR>
+<br>
 Roberto Antolin and Gonzalo Moreno
 
 <h2>REFERENCES</h2>
@@ -100,7 +100,7 @@
 <br>
 <br>
 Performances of the filter can be seen in the
-<a HREF="http://www.itc.nl/isprswgIII-3/filtertest/MainDoc.htm">ISPRS WG III/3 Comparison of Filters</a> 
+<a href="http://www.itc.nl/isprswgIII-3/filtertest/MainDoc.htm">ISPRS WG III/3 Comparison of Filters</a> 
 report by Sithole, G. and Vosselman, G., 2003. 
 
 <p><i>Last changed: $Date$</i>

Modified: grass/trunk/vector/v.lidar.edgedetection/v.lidar.edgedetection.html
===================================================================
--- grass/trunk/vector/v.lidar.edgedetection/v.lidar.edgedetection.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/vector/v.lidar.edgedetection/v.lidar.edgedetection.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -71,19 +71,19 @@
 
 <h2>SEE ALSO</h2>
 <em>
-<a HREF="v.lidar.growing.html">v.lidar.growing</a>,
-<a HREF="v.lidar.correction.html">v.lidar.correction</a>,
-<a HREF="v.surf.bspline.html">v.surf.bspline</a>
+<a href="v.lidar.growing.html">v.lidar.growing</a>,
+<a href="v.lidar.correction.html">v.lidar.correction</a>,
+<a href="v.surf.bspline.html">v.surf.bspline</a>
 </em>
 
 
 <h2>AUTHORS</h2>
 Original version of program in GRASS 5.4:
-<BR>
+<br>
 Maria Antonia Brovelli, Massimiliano Cannata, Ulisse Longoni and Mirko Reguzzoni
-<BR><BR>
+<br><br>
 Update for GRASS 6.X:
-<BR>
+<br>
 Roberto Antolin and Gonzalo Moreno
 
 
@@ -113,7 +113,7 @@
 <br>
 <br>
 Performances of the filter can be seen in the
-<a HREF="http://www.itc.nl/isprswgIII-3/filtertest/MainDoc.htm">ISPRS WG III/3 Comparison of Filters</a> 
+<a href="http://www.itc.nl/isprswgIII-3/filtertest/MainDoc.htm">ISPRS WG III/3 Comparison of Filters</a> 
 report by Sithole, G. and Vosselman, G., 2003. 
 
 <br>

Modified: grass/trunk/vector/v.lidar.growing/v.lidar.growing.html
===================================================================
--- grass/trunk/vector/v.lidar.growing/v.lidar.growing.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/vector/v.lidar.growing/v.lidar.growing.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -48,17 +48,17 @@
 </pre></div>
 
 <h2>SEE ALSO</h2>
-<em><a HREF="v.lidar.edgedetection.html">v.lidar.edgedetection</a></em>,
-<em><a HREF="v.lidar.correction.html">v.lidar.correction</a></em>,
-<em><a HREF="v.surf.bspline.html">v.surf.bspline</a></em>
+<em><a href="v.lidar.edgedetection.html">v.lidar.edgedetection</a></em>,
+<em><a href="v.lidar.correction.html">v.lidar.correction</a></em>,
+<em><a href="v.surf.bspline.html">v.surf.bspline</a></em>
 
 <h2>AUTHOR</h2>
 Original version of program in GRASS 5.4:
-<BR>
+<br>
 Maria Antonia Brovelli, Massimiliano Cannata, Ulisse Longoni and Mirko Reguzzoni
-<BR><BR>
+<br><br>
 Update for GRASS 6.X:
-<BR>
+<br>
 Roberto Antolin and Gonzalo Moreno
 
 <h2>REFERENCES</h2>
@@ -87,7 +87,7 @@
 <br>
 <br>
 Performances of the filter can be seen in the
-<a HREF="http://www.itc.nl/isprswgIII-3/filtertest/MainDoc.htm">ISPRS WG III/3 Comparison of Filters</a> 
+<a href="http://www.itc.nl/isprswgIII-3/filtertest/MainDoc.htm">ISPRS WG III/3 Comparison of Filters</a> 
 report by Sithole, G. and Vosselman, G., 2003. 
 <br>
 

Modified: grass/trunk/vector/v.lrs/lrs.html
===================================================================
--- grass/trunk/vector/v.lrs/lrs.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/vector/v.lrs/lrs.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -168,9 +168,9 @@
 
 Explanations of selected options:
 <ul>
-<li>llayer: vector layer in line map (usually 1; see <a HREF="vectorintro.html">vectorintro</a>
+<li>llayer: vector layer in line map (usually 1; see <a href="vectorintro.html">vectorintro</a>
     for "layer" concept)
-<li>player: vector layer in point map (usually 1; see <a HREF="vectorintro.html">vectorintro</a>
+<li>player: vector layer in point map (usually 1; see <a href="vectorintro.html">vectorintro</a>
     for "layer" concept)
 <li>rsdriver: Driver name for LRS table - DBMI SQL driver (dbf, pg, mysql, sqlite, etc)
 <li>rsdatabase: Database name for LRS table - DBMI SQL database name (e.g., "lrsdb")
@@ -179,14 +179,14 @@
 
 <h2>SEE ALSO</h2>
 
-<em>R. Blazek, 2004, <a HREF="http://gisws.media.osaka-cu.ac.jp/grass04/viewpaper.php?id=50">Introducing the Linear Reference System in GRASS</a>, Bangkok, GRASS User Conf. Proc.</em><br>
-<em>R. Blazek, 2005, <a HREF="http://www.j-geoinfo.net/Content/fulmar05/IJG_095-100.pdf">Introducing the Linear Reference System in GRASS</a>, International Journal of Geoinformatics, Vol. 1(3), pp. 95-100</em><br>
+<em>R. Blazek, 2004, <a href="http://gisws.media.osaka-cu.ac.jp/grass04/viewpaper.php?id=50">Introducing the Linear Reference System in GRASS</a>, Bangkok, GRASS User Conf. Proc.</em><br>
+<em>R. Blazek, 2005, <a href="http://www.j-geoinfo.net/Content/fulmar05/IJG_095-100.pdf">Introducing the Linear Reference System in GRASS</a>, International Journal of Geoinformatics, Vol. 1(3), pp. 95-100</em><br>
 <p>
-<em><a HREF="v.build.polylines.html">v.build.polylines</a></em>,
-<em><a HREF="v.lrs.create.html">v.lrs.create</a></em>,
-<em><a HREF="v.lrs.segment.html">v.lrs.segment</a></em>,
-<em><a HREF="v.lrs.where.html">v.lrs.where</a></em>,
-<em><a HREF="v.lrs.label.html">v.lrs.label</a></em>
+<em><a href="v.build.polylines.html">v.build.polylines</a></em>,
+<em><a href="v.lrs.create.html">v.lrs.create</a></em>,
+<em><a href="v.lrs.segment.html">v.lrs.segment</a></em>,
+<em><a href="v.lrs.where.html">v.lrs.where</a></em>,
+<em><a href="v.lrs.label.html">v.lrs.label</a></em>
 
 <h2>AUTHOR</h2>
 

Modified: grass/trunk/vector/v.lrs/v.lrs.create/v.lrs.create.html
===================================================================
--- grass/trunk/vector/v.lrs/v.lrs.create/v.lrs.create.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/vector/v.lrs/v.lrs.create/v.lrs.create.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -141,13 +141,13 @@
 
 <h2>SEE ALSO</h2>
 
-<em><a HREF="lrs.html">LRS tutorial</a></em>,<br>
-<em><a HREF="http://gisws.media.osaka-cu.ac.jp/grass04/viewpaper.php?id=50">Introducing the Linear Reference System in GRASS</a></em>,
+<em><a href="lrs.html">LRS tutorial</a></em>,<br>
+<em><a href="http://gisws.media.osaka-cu.ac.jp/grass04/viewpaper.php?id=50">Introducing the Linear Reference System in GRASS</a></em>,
 <p>
-<em><a HREF="v.build.polylines.html">v.build.polylines</a></em>,
-<em><a HREF="v.lrs.segment.html">v.lrs.segment</a></em>,
-<em><a HREF="v.lrs.where.html">v.lrs.where</a></em>,
-<em><a HREF="v.lrs.label.html">v.lrs.label</a></em>
+<em><a href="v.build.polylines.html">v.build.polylines</a></em>,
+<em><a href="v.lrs.segment.html">v.lrs.segment</a></em>,
+<em><a href="v.lrs.where.html">v.lrs.where</a></em>,
+<em><a href="v.lrs.label.html">v.lrs.label</a></em>
 
 <h2>AUTHOR</h2>
 

Modified: grass/trunk/vector/v.lrs/v.lrs.label/v.lrs.label.html
===================================================================
--- grass/trunk/vector/v.lrs/v.lrs.label/v.lrs.label.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/vector/v.lrs/v.lrs.label/v.lrs.label.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -22,11 +22,11 @@
 
 <h2>SEE ALSO</h2>
 
-<em><a HREF="lrs.html">LRS tutorial</a></em>,<br>
-<em><a HREF="http://gisws.media.osaka-cu.ac.jp/grass04/viewpaper.php?id=50">Introducing the Linear Reference System in GRASS</a></em>,<br>
-<em><a HREF="v.lrs.create.html">v.lrs.create</a></em>,
-<em><a HREF="v.lrs.segment.html">v.lrs.segment</a></em>,
-<em><a HREF="v.lrs.where.html">v.lrs.where</a></em>
+<em><a href="lrs.html">LRS tutorial</a></em>,<br>
+<em><a href="http://gisws.media.osaka-cu.ac.jp/grass04/viewpaper.php?id=50">Introducing the Linear Reference System in GRASS</a></em>,<br>
+<em><a href="v.lrs.create.html">v.lrs.create</a></em>,
+<em><a href="v.lrs.segment.html">v.lrs.segment</a></em>,
+<em><a href="v.lrs.where.html">v.lrs.where</a></em>
 
 <h2>AUTHOR</h2>
 

Modified: grass/trunk/vector/v.lrs/v.lrs.segment/v.lrs.segment.html
===================================================================
--- grass/trunk/vector/v.lrs/v.lrs.segment/v.lrs.segment.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/vector/v.lrs/v.lrs.segment/v.lrs.segment.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -3,8 +3,8 @@
 <em>v.lrs.segment</em> creates points/segments from input lines,
 linear reference system and positions read from <tt>standard in</tt>
 or a file.
-<P>
-The format is as follows:<BR>
+<p>
+The format is as follows:<br>
 
 <div class="code"><pre>
 P &lt;point_id&gt; &lt;line_id&gt; &lt;milepost&gt;+&lt;offset&gt; [&lt;side offset&gt;]
@@ -47,12 +47,12 @@
 <h2>SEE ALSO</h2>
 
 <em>
-<a HREF="lrs.html">LRS tutorial</a>,<br>
-<a HREF="http://gisws.media.osaka-cu.ac.jp/grass04/viewpaper.php?id=50">Introducing the Linear Reference System in GRASS</a>,<br>
-<a HREF="v.lrs.create.html">v.lrs.create</a>,
-<a HREF="v.lrs.where.html">v.lrs.where</a>,
-<a HREF="v.lrs.label.html">v.lrs.label</a>,
-<a HREF="v.segment.html">v.segment</a>
+<a href="lrs.html">LRS tutorial</a>,<br>
+<a href="http://gisws.media.osaka-cu.ac.jp/grass04/viewpaper.php?id=50">Introducing the Linear Reference System in GRASS</a>,<br>
+<a href="v.lrs.create.html">v.lrs.create</a>,
+<a href="v.lrs.where.html">v.lrs.where</a>,
+<a href="v.lrs.label.html">v.lrs.label</a>,
+<a href="v.segment.html">v.segment</a>
 </em>
 
 <h2>AUTHOR</h2>

Modified: grass/trunk/vector/v.lrs/v.lrs.where/v.lrs.where.html
===================================================================
--- grass/trunk/vector/v.lrs/v.lrs.where/v.lrs.where.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/vector/v.lrs/v.lrs.where/v.lrs.where.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -36,11 +36,11 @@
 
 <h2>SEE ALSO</h2>
 
-<em><a HREF="lrs.html">LRS tutorial</a></em>,<br>
-<em><a HREF="http://gisws.media.osaka-cu.ac.jp/grass04/viewpaper.php?id=50">Introducing the Linear Reference System in GRASS</a></em>,<br>
-<em><a HREF="v.lrs.create.html">v.lrs.where</a></em>,
-<em><a HREF="v.lrs.segment.html">v.lrs.segment</a></em>,
-<em><a HREF="v.lrs.label.html">v.lrs.label</a></em>
+<em><a href="lrs.html">LRS tutorial</a></em>,<br>
+<em><a href="http://gisws.media.osaka-cu.ac.jp/grass04/viewpaper.php?id=50">Introducing the Linear Reference System in GRASS</a></em>,<br>
+<em><a href="v.lrs.create.html">v.lrs.where</a></em>,
+<em><a href="v.lrs.segment.html">v.lrs.segment</a></em>,
+<em><a href="v.lrs.label.html">v.lrs.label</a></em>
 
 <h2>AUTHOR</h2>
 

Modified: grass/trunk/vector/v.mkgrid/v.mkgrid.html
===================================================================
--- grass/trunk/vector/v.mkgrid/v.mkgrid.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/vector/v.mkgrid/v.mkgrid.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -1,27 +1,27 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
-<EM>v.mkgrid</EM> will create a vector map representation of a regular coordinate grid.
+<em>v.mkgrid</em> will create a vector map representation of a regular coordinate grid.
 Both point and area vector grids can be created.
 
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 
 Grid points created with the <b>-p</b> flag will be placed at the
 <i>center</i> of each grid cell, not at the grid line nodes.
-<P>
+<p>
 This is NOT to be used to generate a vector map of USGS quadrangles,
 because USGS quads are not exact rectangles.
 
 
-<H2>EXAMPLES</H2>
+<h2>EXAMPLES</h2>
 
 Make a 4x3 grid, cells 20km a side, with lower left corner at 2716500,6447000:
 <div class="code"><pre>
 v.mkgrid map=coro_grid grid=4,3 position=coor coor=2716500,6447000 box=20000,20000
 </pre></div>
-<BR>
+<br>
 
-<P>
+<p>
 Make a 10x12 lat/lon grid, cells 2 arc-min a side, with lower left corner
 at 167deg 52min east, 47deg 6min south. For use with e.g. QGIS you can then
 pull this grid into a projected location with <em>v.proj</em> before
@@ -32,18 +32,18 @@
 </pre></div>
 
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
-<A HREF="v.patch.html">v.patch</A>,
-<A HREF="d.grid.html">d.grid</A>
+<a href="v.patch.html">v.patch</A>,
+<a href="d.grid.html">d.grid</A>
 
 
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
 
 Michael Higgins,
 U.S.Army Construction Engineering 
 Research Laboratory
-<P>
+<p>
 Update for new vectors Radim Blazek 10/2004 
 
 <p>

Modified: grass/trunk/vector/v.neighbors/v.neighbors.html
===================================================================
--- grass/trunk/vector/v.neighbors/v.neighbors.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/vector/v.neighbors/v.neighbors.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -1,14 +1,14 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
 Makes each cell value a function of the attribute values assigned to the
 vector points or centroids around it, and stores new cell values in
 an output raster map layer.
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
-<A HREF="r.neighbors.html">r.neighbors</A>
+<a href="r.neighbors.html">r.neighbors</A>
 
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
 
 Radim Blazek
 

Modified: grass/trunk/vector/v.net/v.net.html
===================================================================
--- grass/trunk/vector/v.net/v.net.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/vector/v.net/v.net.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -67,11 +67,11 @@
 
 <em>
   <a href="wxGUI.Vector_Digitizing_Tool.html">wxGUI vector digitizer</a>,
-  <a HREF="v.edit.html">v.edit</a><br>
-  <a HREF="v.net.iso.html">v.net.iso</a>,
-  <a HREF="v.net.path.html">v.net.path</a>,
-  <a HREF="v.net.steiner.html">v.net.steiner</a>,
-  <a HREF="v.net.salesman.html">v.net.salesman</a>
+  <a href="v.edit.html">v.edit</a><br>
+  <a href="v.net.iso.html">v.net.iso</a>,
+  <a href="v.net.path.html">v.net.path</a>,
+  <a href="v.net.steiner.html">v.net.steiner</a>,
+  <a href="v.net.salesman.html">v.net.salesman</a>
 </em>
 
 <h2>AUTHORS</h2>

Modified: grass/trunk/vector/v.net.alloc/v.net.alloc.html
===================================================================
--- grass/trunk/vector/v.net.alloc/v.net.alloc.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/vector/v.net.alloc/v.net.alloc.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -144,12 +144,12 @@
 
 <h2>SEE ALSO</h2>
 
-<em><a HREF="d.path.html">d.path</a></em>,
-<em><a HREF="v.net.html">v.net</a></em>,
-<em><a HREF="v.net.iso.html">v.net.iso</a></em>,
-<em><a HREF="v.net.path.html">v.net.path</a></em>,
-<em><a HREF="v.net.steiner.html">v.net.steiner</a></em>,
-<em><a HREF="v.net.salesman.html">v.net.salesman</a></em>
+<em><a href="d.path.html">d.path</a></em>,
+<em><a href="v.net.html">v.net</a></em>,
+<em><a href="v.net.iso.html">v.net.iso</a></em>,
+<em><a href="v.net.path.html">v.net.path</a></em>,
+<em><a href="v.net.steiner.html">v.net.steiner</a></em>,
+<em><a href="v.net.salesman.html">v.net.salesman</a></em>
 
 <h2>AUTHOR</h2>
 

Modified: grass/trunk/vector/v.net.allpairs/v.net.allpairs.html
===================================================================
--- grass/trunk/vector/v.net.allpairs/v.net.allpairs.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/vector/v.net.allpairs/v.net.allpairs.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -30,14 +30,14 @@
 <div class="code"><pre>
 v.net.allpairs input=roads output=roads_pairs afcol=SHAPE_LEN where="crossing=1"
 </pre></div>
-<P>
+<p>
 
 
 <h2>SEE ALSO</h2>
 
 <em>
-<a HREF="v.net.path">v.net.path</a>,
-<a HREF="v.net.distance">v.net.distance</a>
+<a href="v.net.path">v.net.path</a>,
+<a href="v.net.distance">v.net.distance</a>
 </em>
 
 

Modified: grass/trunk/vector/v.net.bridge/v.net.bridge.html
===================================================================
--- grass/trunk/vector/v.net.bridge/v.net.bridge.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/vector/v.net.bridge/v.net.bridge.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -26,7 +26,7 @@
 
 <div class="code"><pre>
 </pre></div>
-<P>
+<p>
 
 <div class="code"><pre>
 </pre></div>
@@ -35,7 +35,7 @@
 <h2>SEE ALSO</h2>
 
 <em>
-<a HREF="v.category.html">v.category</a>,
+<a href="v.category.html">v.category</a>,
 </em>
 
 <h2>AUTHORS</h2>

Modified: grass/trunk/vector/v.net.centrality/v.net.centrality.html
===================================================================
--- grass/trunk/vector/v.net.centrality/v.net.centrality.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/vector/v.net.centrality/v.net.centrality.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -29,7 +29,7 @@
 <div class="code"><pre>
 v.net.centrality input=roads output=roads_cent closeness=close betweenness=betw -a
 </pre></div>
-<P>
+<p>
 
 <div class="code"><pre>
 </pre></div>
@@ -38,7 +38,7 @@
 <h2>SEE ALSO</h2>
 
 <em>
-<a HREF="v.generalize.html">v.generalize</a>
+<a href="v.generalize.html">v.generalize</a>
 </em>
 
 <h2>AUTHORS</h2>

Modified: grass/trunk/vector/v.net.components/v.net.components.html
===================================================================
--- grass/trunk/vector/v.net.components/v.net.components.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/vector/v.net.components/v.net.components.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -26,7 +26,7 @@
 <div class="code"><pre>
 v.net.components input=roads output=roads_components method=strong
 </pre></div>
-<P>
+<p>
 
 <div class="code"><pre>
 </pre></div>
@@ -35,7 +35,7 @@
 <h2>SEE ALSO</h2>
 
 <em>
-<a HREF="v.category.html">v.category</a>,
+<a href="v.category.html">v.category</a>,
 </em>
 
 <h2>AUTHORS</h2>

Modified: grass/trunk/vector/v.net.connectivity/v.net.connectivity.html
===================================================================
--- grass/trunk/vector/v.net.connectivity/v.net.connectivity.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/vector/v.net.connectivity/v.net.connectivity.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -7,7 +7,7 @@
 <h2>NOTES</h2>
 Two sets (<em>set1</em> and <em>set2</em>) are specified by respective 
 <b>layer</b>, <b>where</b> and <b>cats</b> parameters. Similarly to 
-<a HREF="v.net.flow.html">v.net.flow</a> module, capacities of nodes can 
+<a href="v.net.flow.html">v.net.flow</a> module, capacities of nodes can 
 be given by <b>ncolumn</b> option. <em>v.net.connectivity</em> finds the 
 set of nodes of minimum total capacitiy separating the two given sets and 
 outputs map containing points on the positions of these nodes. Default 
@@ -19,7 +19,7 @@
 <div class="code"><pre>
 v.net.connectivity input=roads output=roads_conn set1_where="bank=left" set2_where="bank=right"
 </pre></div>
-<P>
+<p>
 
 <div class="code"><pre>
 v.net.connectivity input=airtraffic output=connectivity set1_where="name=JFK" set2_where="name=Heathrow" ncolumn=capacity
@@ -29,8 +29,8 @@
 <h2>SEE ALSO</h2>
 
 <em>
-<a HREF="v.net.flow.html">v.net.flow</a>,
-<a HREF="v.net.bridge.html">v.net.bridge</a>
+<a href="v.net.flow.html">v.net.flow</a>,
+<a href="v.net.bridge.html">v.net.bridge</a>
 </em>
 
 <h2>AUTHORS</h2>

Modified: grass/trunk/vector/v.net.distance/v.net.distance.html
===================================================================
--- grass/trunk/vector/v.net.distance/v.net.distance.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/vector/v.net.distance/v.net.distance.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -31,15 +31,15 @@
 v.net.distance input=city output=nearest from_where="type=school" to_where="type=hospital" afcolumn=SHAPE_LEN
 d.vect nearest cats=1
 </pre></div>
-<P>
+<p>
 
 <h2>SEE ALSO</h2>
 
 <em>
-<a HREF="v.net.path.html">v.net.path</a>,
-<a HREF="v.net.allpairs.html">v.net.allpairs</a>,
-<a HREF="v.distance.html">v.net.distance</a>,
-<a HREF="v.net.alloc.html">v.net.alloc</a>
+<a href="v.net.path.html">v.net.path</a>,
+<a href="v.net.allpairs.html">v.net.allpairs</a>,
+<a href="v.distance.html">v.net.distance</a>,
+<a href="v.net.alloc.html">v.net.alloc</a>
 </em>
 
 <h2>AUTHORS</h2>

Modified: grass/trunk/vector/v.net.flow/v.net.flow.html
===================================================================
--- grass/trunk/vector/v.net.flow/v.net.flow.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/vector/v.net.flow/v.net.flow.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -30,7 +30,7 @@
 <div class="code"><pre>
 v.net.flow input=roads output=roads_flow cut=roads_cut afcolumn=SPEED source_where="type=factory" sink_where="type=store"
 </pre></div>
-<P>
+<p>
 
 If all the capacties are one then the minimum cut corresponds to the 
 minimum number of edges separating sources from sinks. 
@@ -42,7 +42,7 @@
 <h2>SEE ALSO</h2>
 
 <em>
-<a HREF="v.net.connectivity.html">v.net.connectivity</a>
+<a href="v.net.connectivity.html">v.net.connectivity</a>
 </em>
 
 

Modified: grass/trunk/vector/v.net.iso/v.net.iso.html
===================================================================
--- grass/trunk/vector/v.net.iso/v.net.iso.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/vector/v.net.iso/v.net.iso.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -27,7 +27,7 @@
 <h2>EXAMPLES</h2>
 
 The map must contain at least one center (point) on the vector network 
-which can be patched into with <a HREF="v.net.html">v.net</a>.
+which can be patched into with <a href="v.net.html">v.net</a>.
 
 <p>
 Isonetwork using distance:
@@ -158,13 +158,13 @@
 
 <h2>SEE ALSO</h2>
 
-<em><a HREF="d.path.html">d.path</a></em>,
-<em><a HREF="v.net.html">v.net</a></em>,
-<em><a HREF="v.net.alloc.html">v.net.alloc</a></em>,
-<em><a HREF="v.net.path.html">v.net.path</a></em>,
-<em><a HREF="v.net.salesman.html">v.net.salesman</a></em>,
-<em><a HREF="v.net.steiner.html">v.net.steiner</a></em>,
-<em><a HREF="v.patch.html">v.patch</a></em>
+<em><a href="d.path.html">d.path</a></em>,
+<em><a href="v.net.html">v.net</a></em>,
+<em><a href="v.net.alloc.html">v.net.alloc</a></em>,
+<em><a href="v.net.path.html">v.net.path</a></em>,
+<em><a href="v.net.salesman.html">v.net.salesman</a></em>,
+<em><a href="v.net.steiner.html">v.net.steiner</a></em>,
+<em><a href="v.patch.html">v.patch</a></em>
 
 <h2>AUTHOR</h2>
 

Modified: grass/trunk/vector/v.net.path/v.net.path.html
===================================================================
--- grass/trunk/vector/v.net.path/v.net.path.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/vector/v.net.path/v.net.path.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -22,7 +22,7 @@
 <p>
 Least cost paths are written to the output vector map with an 
 attached attribute table.
-<P>
+<p>
 Nodes can be piped into the program from file or from stdin. The
 syntax is as follows:
 <div class="code"><pre>
@@ -44,7 +44,7 @@
 
 <p>
 The attribute table will contain the following attributes:
-</p>
+
 <ul>
     <li>cat  - path unique category assigned by module</li>
     <li>id   - path id (read from input)</li>
@@ -67,7 +67,7 @@
 If the cost columns 'afcol', 'abcol' and 'ncol' are not
 specified, the length of network segments is measured and 
 zero costs are assumed for nodes.
-<P>
+<p>
 When using attributes, the length of segments is not used. To get
 accurate results, the line length must be taken into account when 
 assigning costs as attributes. For example, to get the <b>fastest path</b>, 
@@ -156,13 +156,13 @@
 
 <h2>SEE ALSO</h2>
 
-<em><a HREF="d.path.html">d.path</a></em>,
-<em><a HREF="v.net.html">v.net</a></em>,
-<em><a HREF="v.net.alloc.html">v.net.alloc</a></em>,
-<em><a HREF="v.net.iso.html">v.net.iso</a></em>,
-<em><a HREF="v.net.salesman.html">v.net.salesman</a></em>,
-<em><a HREF="v.net.steiner.html">v.net.steiner</a></em>,
-<em><a HREF="v.to.db.html">v.to.db</a></em>
+<em><a href="d.path.html">d.path</a></em>,
+<em><a href="v.net.html">v.net</a></em>,
+<em><a href="v.net.alloc.html">v.net.alloc</a></em>,
+<em><a href="v.net.iso.html">v.net.iso</a></em>,
+<em><a href="v.net.salesman.html">v.net.salesman</a></em>,
+<em><a href="v.net.steiner.html">v.net.steiner</a></em>,
+<em><a href="v.to.db.html">v.to.db</a></em>
 
 <h2>AUTHOR</h2>
 

Modified: grass/trunk/vector/v.net.salesman/v.net.salesman.html
===================================================================
--- grass/trunk/vector/v.net.salesman/v.net.salesman.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/vector/v.net.salesman/v.net.salesman.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -136,12 +136,12 @@
 
 <h2>SEE ALSO</h2>
 
-<em><a HREF="d.path.html">d.path</a></em>,
-<em><a HREF="v.net.html">v.net</a></em>,
-<em><a HREF="v.net.alloc.html">v.net.alloc</a></em>,
-<em><a HREF="v.net.iso.html">v.net.iso</a></em>,
-<em><a HREF="v.net.path.html">v.net.path</a></em>,
-<em><a HREF="v.net.steiner.html">v.net.steiner</a></em>
+<em><a href="d.path.html">d.path</a></em>,
+<em><a href="v.net.html">v.net</a></em>,
+<em><a href="v.net.alloc.html">v.net.alloc</a></em>,
+<em><a href="v.net.iso.html">v.net.iso</a></em>,
+<em><a href="v.net.path.html">v.net.path</a></em>,
+<em><a href="v.net.steiner.html">v.net.steiner</a></em>
 
 <h2>AUTHOR</h2>
 

Modified: grass/trunk/vector/v.net.spanningtree/v.net.spanningtree.html
===================================================================
--- grass/trunk/vector/v.net.spanningtree/v.net.spanningtree.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/vector/v.net.spanningtree/v.net.spanningtree.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -19,12 +19,12 @@
 <div class="code"><pre>
 v.net.spanningtree input=projected_pipelines output=spanningtree accol=cost 
 </pre></div>
-<P>
+<p>
 
 <h2>SEE ALSO</h2>
 
 <em>
-<a HREF="v.net.steiner.html">v.net.steiner</a>
+<a href="v.net.steiner.html">v.net.steiner</a>
 </em>
 
 <h2>AUTHORS</h2>

Modified: grass/trunk/vector/v.net.steiner/v.net.steiner.html
===================================================================
--- grass/trunk/vector/v.net.steiner/v.net.steiner.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/vector/v.net.steiner/v.net.steiner.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -3,7 +3,7 @@
 <em>v.net.steiner</em> calculates the optimal connection of nodes on a
 vector network.
 
-<P>
+<p>
 A Steiner tree is used to calculate the minimum-cost vector network
 connecting some number of end nodes in a network framework.
 For example it could be used to find the path following a road system
@@ -119,12 +119,12 @@
 
 <h2>SEE ALSO</h2>
 
-<em><a HREF="d.path.html">d.path</a></em>,
-<em><a HREF="v.net.html">v.net</a></em>,
-<em><a HREF="v.net.alloc.html">v.net.alloc</a></em>,
-<em><a HREF="v.net.iso.html">v.net.iso</a></em>,
-<em><a HREF="v.net.path.html">v.net.path</a></em>,
-<em><a HREF="v.net.salesman.html">v.net.salesman</a></em>
+<em><a href="d.path.html">d.path</a></em>,
+<em><a href="v.net.html">v.net</a></em>,
+<em><a href="v.net.alloc.html">v.net.alloc</a></em>,
+<em><a href="v.net.iso.html">v.net.iso</a></em>,
+<em><a href="v.net.path.html">v.net.path</a></em>,
+<em><a href="v.net.salesman.html">v.net.salesman</a></em>
 
 <h2>AUTHOR</h2>
 

Modified: grass/trunk/vector/v.net.timetable/v.net.timetable.html
===================================================================
--- grass/trunk/vector/v.net.timetable/v.net.timetable.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/vector/v.net.timetable/v.net.timetable.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -132,8 +132,8 @@
 <h2>SEE ALSO</h2>
 
 <em>
-<a HREF="v.net.path.html">v.net.path</a>,
-<a HREF="v.net.distance.html">v.net.distance</a>
+<a href="v.net.path.html">v.net.path</a>,
+<a href="v.net.distance.html">v.net.distance</a>
 </em>
 
 <h2>AUTHORS</h2>

Modified: grass/trunk/vector/v.net.visibility/v.net.visibility.html
===================================================================
--- grass/trunk/vector/v.net.visibility/v.net.visibility.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/vector/v.net.visibility/v.net.visibility.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -108,13 +108,13 @@
 
 <h2>SEE ALSO</h2>
 
-<em><a HREF="d.path.html">d.path</a></em>,
-<em><a HREF="v.net.html">v.net</a></em>,
-<em><a HREF="v.net.alloc.html">v.net.alloc</a></em>,
-<em><a HREF="v.net.iso.html">v.net.iso</a></em>,
-<em><a HREF="v.net.salesman.html">v.net.salesman</a></em>,
-<em><a HREF="v.net.steiner.html">v.net.steiner</a></em>,
-<em><a HREF="v.to.db.html">v.to.db</a></em>
+<em><a href="d.path.html">d.path</a></em>,
+<em><a href="v.net.html">v.net</a></em>,
+<em><a href="v.net.alloc.html">v.net.alloc</a></em>,
+<em><a href="v.net.iso.html">v.net.iso</a></em>,
+<em><a href="v.net.salesman.html">v.net.salesman</a></em>,
+<em><a href="v.net.steiner.html">v.net.steiner</a></em>,
+<em><a href="v.to.db.html">v.to.db</a></em>
 
 <h2>AUTHOR</h2>
 Maximilian Maldacker<br>

Modified: grass/trunk/vector/v.normal/v.normal.html
===================================================================
--- grass/trunk/vector/v.normal/v.normal.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/vector/v.normal/v.normal.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -1,10 +1,10 @@
-<H2>DESCRIPTION</H2>
-<EM>v.normal</EM>
+<h2>DESCRIPTION</h2>
+<em>v.normal</em>
 computes tests of normality on vector points.
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 
-The tests that <EM>v.normal</EM> performs are indexed
+The tests that <em>v.normal</em> performs are indexed
 below.  The tests that are performed are specified by
 giving an index, ranges of indices, or multiple thereof.
 
@@ -27,7 +27,7 @@
 <LI> Kotz Separate-Families Test for Lognormality vs. Normality
 </OL>
 
-<H2>EXAMPLE</H2>
+<h2>EXAMPLE</h2>
 
 <!-- do a meaning ful example -->
 <div class="code"><pre>
@@ -40,21 +40,21 @@
 computes the sample skewness and kurtosis, Geary's
 a-statistic and an approximate normal transformation,
 extreme normal deviates, and Royston's W for the
-<EM>random</EM> vector points.
+<em>random</em> vector points.
 
 <!-- TODO: find references , e.g.
      http://www.itl.nist.gov/div898/handbook/eda/section3/eda35.htm
 -->
 
-<H2>SEE ALSO</H2>
-<A HREF="v.univar.html">v.univar</A>
+<h2>SEE ALSO</h2>
+<a href="v.univar.html">v.univar</A>
 
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
 
-<A HREF="http://mccauley-usa.com/">James Darrell McCauley</A>
-<A HREF="mailto:darrell at mccauley-usa.com">&lt;darrell at mccauley-usa.com&gt;</A>,
+<a href="http://mccauley-usa.com/">James Darrell McCauley</A>
+<a href="mailto:darrell at mccauley-usa.com">&lt;darrell at mccauley-usa.com&gt;</A>,
 <br>when he was at:
-<A HREF="http://ABE.www.ecn.purdue.edu/ABE/">Agricultural
+<a href="http://ABE.www.ecn.purdue.edu/ABE/">Agricultural
 Engineering</A>
-<A HREF="http://www.purdue.edu/">Purdue University</A>
+<a href="http://www.purdue.edu/">Purdue University</A>
 <p><i>Last changed: $Date$</i>

Modified: grass/trunk/vector/v.out.dxf/v.out.dxf.html
===================================================================
--- grass/trunk/vector/v.out.dxf/v.out.dxf.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/vector/v.out.dxf/v.out.dxf.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -1,29 +1,29 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
-The GRASS program <EM>v.out.dxf</EM> conversion program
+The GRASS program <em>v.out.dxf</em> conversion program
 generates an ASCII DXF (AutoCAD) file from a GRASS vector.
 The output file is placed in the user's current
 working directory unless the user specifies a full pathname
-for the <EM>output</EM>.
+for the <em>output</em>.
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 DXF files output by AutoCAD have the suffix <KBD>.dxf</KBD>
 
-<H2>REFERENCES</H2>
+<h2>REFERENCES</h2>
 
 <a href="http://en.wikipedia.org/wiki/AutoCAD_DXF">AutoCad DXF</a> (from Wikipedia, the free encyclopedia)
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
-<EM><A HREF="v.in.dxf.html">v.in.dxf</A></EM>,
-<EM><a href="vectorintro.html">Introduction to GRASS vector map processing</a></EM>
+<em><a href="v.in.dxf.html">v.in.dxf</A></em>,
+<em><a href="vectorintro.html">Introduction to GRASS vector map processing</a></em>
 
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
 
 Charles Ehlschlaeger, U.S. Army Construction Engineering
 Research Laboratory,<br>
-wrote original <EM>v.out.dxf</EM> program in 4/89.
-<P>
+wrote original <em>v.out.dxf</em> program in 4/89.
+<p>
 Update to GRASS 5.7 Radim Blazek, 10/2004
 
 

Modified: grass/trunk/vector/v.out.ogr/v.out.ogr.html
===================================================================
--- grass/trunk/vector/v.out.ogr/v.out.ogr.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/vector/v.out.ogr/v.out.ogr.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -117,7 +117,7 @@
 </pre></div>
 
 
-<H2>REFERENCES</H2>
+<h2>REFERENCES</h2>
 
 <a href="http://www.gdal.org/ogr/">OGR vector library</a>
 <br>
@@ -127,11 +127,11 @@
 
 <h2>SEE ALSO</h2>
 
-<EM>
-<A HREF="db.out.ogr.html">db.out.ogr</A>,
-<A HREF="v.external.html">v.external</A>,
-<a HREF="v.in.ogr.html">v.in.ogr</a>
-</EM>
+<em>
+<a href="db.out.ogr.html">db.out.ogr</A>,
+<a href="v.external.html">v.external</A>,
+<a href="v.in.ogr.html">v.in.ogr</a>
+</em>
 
 <h2>AUTHORS</h2>
 
@@ -139,4 +139,4 @@
 Some contributions: Markus Neteler, Martin Landa
 <p>
 <i>Last changed: $Date$</i>
-</p>
+

Modified: grass/trunk/vector/v.out.pov/v.out.pov.html
===================================================================
--- grass/trunk/vector/v.out.pov/v.out.pov.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/vector/v.out.pov/v.out.pov.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -12,14 +12,14 @@
 #include "vector3d.pov"
 </pre></div>
 
-<H2>REFERENCES</H2>
+<h2>REFERENCES</h2>
 
 <a href="http://www.povray.com">POV-Ray</a>
 
 
 <h2>SEE ALSO</h2>
 
-<em><a HREF="r.out.pov.html">r.out.pov</a></em>
+<em><a href="r.out.pov.html">r.out.pov</a></em>
 
 <h2>AUTHOR</h2>
 

Modified: grass/trunk/vector/v.out.svg/v.out.svg.html
===================================================================
--- grass/trunk/vector/v.out.svg/v.out.svg.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/vector/v.out.svg/v.out.svg.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -34,7 +34,7 @@
 v.out.svg input=archsites output=/tmp/output.svg type=point precision=0 attrib=str1
 </pre></div>
 
-<H2>REFERENCES</H2>
+<h2>REFERENCES</h2>
 
 <a href="http://svg.cc/grass/index.html">Modul v.out.svg at svg.cc</a>
 <br>
@@ -43,7 +43,7 @@
 
 <h2>SEE ALSO</h2>
 
-<em><A HREF="v.out.ogr.html">v.out.ogr</A></em>
+<em><a href="v.out.ogr.html">v.out.ogr</A></em>
 
 <h2>AUTHOR</h2>
 

Modified: grass/trunk/vector/v.out.vtk/v.out.vtk.html
===================================================================
--- grass/trunk/vector/v.out.vtk/v.out.vtk.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/vector/v.out.vtk/v.out.vtk.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -3,7 +3,7 @@
 <em>v.out.vtk</em> 
 converts a GRASS vector map in binary format to the VTK ASCII 
 output. 
-<P>
+<p>
 If the <b>output</b> parameter is not given, the output will be send to stdout.
 
 <h2>NOTES</h2>
@@ -51,20 +51,20 @@
 </ul>
 <p>
 The VTK file can be visualized with
-<EM><A HREF="http://www.vtk.org">VTK Toolkit</A></EM>,
-<EM><A HREF="http://www.paraview.org">Paraview</A></EM> and
-<EM><A HREF="http://mayavi.sourceforge.net">MayaVi</A></EM>.
+<em><a href="http://www.vtk.org">VTK Toolkit</A></em>,
+<em><a href="http://www.paraview.org">Paraview</A></em> and
+<em><a href="http://mayavi.sourceforge.net">MayaVi</A></em>.
 
 <h3>Attention</h3>
 <p>
 If areas or faces are exported, the data have to be triangulated within Paraview or
 MayaVi.
-</p>
 
+
 <h2>EXAMPLE</h2>
 
 Spearfish example:
-<P>
+<p>
 Export the soils with cats in layer 1:
 <div class="code"><pre>
 v.out.vtk input=soils type=area layer=1 output=/tmp/soils.vtk
@@ -81,9 +81,9 @@
 <h2>SEE ALSO</h2>
 
 <em>
-<a HREF="v.out.ascii.html">v.out.ascii</a><BR>
-<a HREF="r.out.vtk.html">r.out.vtk</a><BR>
-<a HREF="r3.out.vtk.html">r3.out.vtk</a><BR>
+<a href="v.out.ascii.html">v.out.ascii</a><br>
+<a href="r.out.vtk.html">r.out.vtk</a><br>
+<a href="r3.out.vtk.html">r3.out.vtk</a><br>
 </em>
 
 

Modified: grass/trunk/vector/v.outlier/v.outlier.html
===================================================================
--- grass/trunk/vector/v.outlier/v.outlier.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/vector/v.outlier/v.outlier.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -46,16 +46,16 @@
 
 <h2>SEE ALSO</h2>
 
-<em><a HREF="v.surf.bspline.html">v.surf.bspline</a></em>
+<em><a href="v.surf.bspline.html">v.surf.bspline</a></em>
 
 <h2>AUTHORS</h2>
 
 Original version of the program in GRASS 5.4:
-<BR>
+<br>
 Maria Antonia Brovelli, Massimiliano Cannata, Ulisse Longoni and Mirko Reguzzoni
-<BR><BR>
+<br><br>
 Updates for GRASS 6:
-<BR>
+<br>
 Roberto Antolin
 
 <p>

Modified: grass/trunk/vector/v.overlay/v.overlay.html
===================================================================
--- grass/trunk/vector/v.overlay/v.overlay.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/vector/v.overlay/v.overlay.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -61,7 +61,7 @@
 </pre></div>
 
 <center>
-<img src="v_overlay_area_lines.png" alt="GRASS v.overlay: Line to polygon clipping"><BR>
+<img src="v_overlay_area_lines.png" alt="GRASS v.overlay: Line to polygon clipping"><br>
 <table border=0 width=590>
 <tr><td><center>
 <i>v.overlay: Line to polygon clipping</i>

Modified: grass/trunk/vector/v.parallel/v.parallel.html
===================================================================
--- grass/trunk/vector/v.parallel/v.parallel.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/vector/v.parallel/v.parallel.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -1,15 +1,15 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
-<EM>v.parallel</EM> creates parallel lines to the input vector lines which
+<em>v.parallel</em> creates parallel lines to the input vector lines which
 can be used as half-buffers.
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
-<EM>
-<A HREF="v.buffer.html">v.buffer</A>
-</EM>
+<em>
+<a href="v.buffer.html">v.buffer</A>
+</em>
 
-<H2>AUTHORS</H2>
+<h2>AUTHORS</h2>
 
 Radim Blazek<br>
 Rewritten by Rosen Matev (with support through the Google Summer of Code program 2008)

Modified: grass/trunk/vector/v.patch/v.patch.html
===================================================================
--- grass/trunk/vector/v.patch/v.patch.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/vector/v.patch/v.patch.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -11,18 +11,18 @@
 patched together (e.g., border lines) will have to be
 edited or removed after <em>v.patch</em> is run. Such
 editing can be done automatically using
-<em><a HREF="v.clean.html">v.clean</a></em>.
+<em><a href="v.clean.html">v.clean</a></em>.
 <p>
 Lines may need to be
-snapped with <em><a HREF="v.clean.html">v.clean</a>
+snapped with <em><a href="v.clean.html">v.clean</a>
 tool=snap,break,rmdupl</em>.
 <p>
 Boundaries may need to be cleaned with
-<em><a HREF="v.clean.html">v.clean</a> tool=break,rmdupl,rmsa</em>
+<em><a href="v.clean.html">v.clean</a> tool=break,rmdupl,rmsa</em>
 repeatedly until the <em>rmsa</em> tool (Remove small angles at nodes)
 no longer modifies any boundaries. If vector topology is still not
 clean, boundaries may also need to be snapped with
-<em><a HREF="v.clean.html">v.clean</a> tool=snap,break,rmdupl</em>.
+<em><a href="v.clean.html">v.clean</a> tool=snap,break,rmdupl</em>.
 <p>
 When using the <em>-a</em> flag, the user has to make sure that the
 features in the different maps added to the output map do not have
@@ -39,7 +39,7 @@
    v.patch input=geology,streams out=geol_streams
 </pre></div>
 
-<BR>
+<br>
 Append one map to another:
 <div class="code"><pre>
    g.copy vect=roads,transport
@@ -49,10 +49,10 @@
 
 <h2>SEE ALSO</h2>
 
-<em><a HREF="v.clean.html">v.clean</a></em>,
-<em><a HREF="v.build.html">v.build</a></em>,
-<em><a HREF="v.select.html">v.select</a></em>,
-<em><a HREF="v.overlay.html">v.overlay</a></em>
+<em><a href="v.clean.html">v.clean</a></em>,
+<em><a href="v.build.html">v.build</a></em>,
+<em><a href="v.select.html">v.select</a></em>,
+<em><a href="v.overlay.html">v.overlay</a></em>
 
 
 <h2>AUTHORS</h2>

Modified: grass/trunk/vector/v.perturb/v.perturb.html
===================================================================
--- grass/trunk/vector/v.perturb/v.perturb.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/vector/v.perturb/v.perturb.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -1,12 +1,12 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
-<EM>v.perturb</EM>
+<em>v.perturb</em>
 reads a vector map of points and writes the same points but
-<EM>perturbs</EM> the eastings and northings by
+<em>perturbs</em> the eastings and northings by
 adding either a uniform or normal delta value. Perturbation means that
 a variating spatial deviation is added to the coordinates.
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 
 The uniform distribution is always centered about zero.
 The associated <em>parameter</em> is constrained to be positive and
@@ -14,31 +14,31 @@
 the negation of that parameter. Do perturb into a ring around the
 center, the <em>minimum</em> parameter can be used.
 
-<P>
+<p>
 
 Usually, the mean (first parameter) of the normal
 distribution is zero (i.e., the distribution is centered at
 zero). The standard deviation (second parameter) is
 naturally constrained to be positive.
 
-<P>
+<p>
 
 Output vector points are not guaranteed to be contained within the
 current geographic region.
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
-<EM><A HREF="v.random.html">v.random</A></EM><br>
-<EM><A HREF="v.univar.html">v.univar</A></EM><br>
+<em><a href="v.random.html">v.random</A></em><br>
+<em><a href="v.univar.html">v.univar</A></em><br>
 
 
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
 
-<A HREF="http://mccauley-usa.com/">James Darrell McCauley</A>
+<a href="http://mccauley-usa.com/">James Darrell McCauley</A>
 <br>when he was at: 
-<A HREF="http://ABE.www.ecn.purdue.edu/ABE/">Agricultural Engineering</A>
-<A HREF="http://www.purdue.edu/">Purdue University</A>
-<P>
+<a href="http://ABE.www.ecn.purdue.edu/ABE/">Agricultural Engineering</A>
+<a href="http://www.purdue.edu/">Purdue University</A>
+<p>
 Random number generators originally written in FORTRAN by Wes Peterson and
 translated to C using <i>f2c</i>.
 

Modified: grass/trunk/vector/v.proj/v.proj.html
===================================================================
--- grass/trunk/vector/v.proj/v.proj.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/vector/v.proj/v.proj.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -1,4 +1,4 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
 <em>v.proj</em> allows a user to convert a vector map in a specified mapset
 of a specified location (different from current) with projection of input
@@ -7,35 +7,35 @@
 corresponding PROJ_INFO files).
 
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 
 If <B>out</B> is not specified it is set to be the same as input map name.
 
-<BR>
+<br>
 If <B>dbase</B> is not specified it is assumed to be the current database.
 The user only has to specify <B>dbase</B> if the source location is stored
 in another separate GRASS database.
 
-<BR>
+<br>
 If <B>set</B> is not specified, its name is assumed to be the same as the current
  mapset's name. 
 
-<P>
-<EM>v.proj</EM> supports general datum transformations, making use of the
-<EM>PROJ.4</EM> co-ordinate system translation library.
-</P>
+<p>
+<em>v.proj</em> supports general datum transformations, making use of the
+<em>PROJ.4</em> co-ordinate system translation library.
 
-<H2>EXAMPLES</H2>
 
+<h2>EXAMPLES</h2>
+
 <div class="code"><pre>
 v.proj in=mymap location=latlong mapset=user1
 </pre></div>
 
-<H2>REFERENCES</H2>
+<h2>REFERENCES</h2>
 
 <a href="http://proj.maptools.org/">PROJ 4</a>: Projection/datum support library.
 
-<P>
+<p>
 <B>Further reading</B>
 <ul>
 <li> <a href="http://www.asprs.org/resources/grids/">ASPRS Grids and Datum</a>
@@ -43,25 +43,25 @@
 <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="r.proj.html">r.proj</A>,
-<A HREF="g.proj.html">g.proj</A>,
-<A HREF="g.setproj.html">g.setproj</A>,
-<A HREF="i.rectify.html">i.rectify</A>,  
-<A HREF="r.stats.html">r.stats</A>,  
-<A HREF="v.sample.html">v.sample</A>,
-<A HREF="v.surf.idw.html">v.surf.idw</A>,
-<A HREF="v.surf.rst.html">v.surf.rst</A>
-</EM>
+<em>
+<a href="r.proj.html">r.proj</A>,
+<a href="g.proj.html">g.proj</A>,
+<a href="g.setproj.html">g.setproj</A>,
+<a href="i.rectify.html">i.rectify</A>,  
+<a href="r.stats.html">r.stats</A>,  
+<a href="v.sample.html">v.sample</A>,
+<a href="v.surf.idw.html">v.surf.idw</A>,
+<a href="v.surf.rst.html">v.surf.rst</A>
+</em>
 
-<H2>AUTHORS</H2>
+<h2>AUTHORS</h2>
 
 Irina Kosinovsky, US ARMY CERL
-<BR>
+<br>
 M.L. Holko, USDA, SCS, NHQ-CGIS
-<BR>
+<br>
 R.L. Glenn, USDA, SCS, NHQ-CGIS
 
 <p><i>Last changed: $Date$</i>

Modified: grass/trunk/vector/v.qcount/v.qcount.html
===================================================================
--- grass/trunk/vector/v.qcount/v.qcount.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/vector/v.qcount/v.qcount.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -1,104 +1,104 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
-<EM>v.qcount</EM> chooses <B>n</B> circular quadrats of
+<em>v.qcount</em> chooses <B>n</B> circular quadrats of
 radius <B>r</B> such that they are completely within the
 bounds of the current region and no two quadrats overlap.
 The number of points falling within each quadrat are counted
 and indices are calculated to estimate the departure of
 point locations from complete spatial randomness.
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 
 This program may not work properly with lat-long data. It uses 
-<EM>hypot()</EM>
-in two files: <EM>count.c</EM> and <EM>findquads.c</EM>.
+<em>hypot()</em>
+in two files: <em>count.c</em> and <em>findquads.c</em>.
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
-<EM><A HREF="v.random.html">v.random</A></EM> 
+<em><a href="v.random.html">v.random</A></em> 
 
-<P>
+<p>
 
-<EM>Complete Spatial Randomness and Quadrat Methods</EM>  - 
-GRASS Tutorial on <EM>v.qcount</EM>
+<em>Complete Spatial Randomness and Quadrat Methods</em>  - 
+GRASS Tutorial on <em>v.qcount</em>
 (only available as older file s.qcount-tutorial.ps),
 
-<P>
+<p>
 
 General references include:
 
-<BR>
+<br>
 
 Noel A. C. Cressie.
-<EM>Statistics for Spatial Data</EM>.
+<em>Statistics for Spatial Data</em>.
 Wiley Series in Probability and Mathematical Statistics. John Wiley
 &amp; Sons, New York, NY, 1st edition, 1991.
 
-<BR>
+<br>
 
 Brian D. Ripley.
-<EM>Spatial Statistics</EM>.
+<em>Spatial Statistics</em>.
 John Wiley \&amp; Sons, New York, NY, 1981.
 
 
-<P>
+<p>
 
 References to the indices include:
 
-<BR>
+<br>
 
 F. N. David and P. G. Moore.
 Notes on contagious distributions in plant populations.
-<EM>Annals of Botany</EM>, 
+<em>Annals of Botany</em>, 
 18:47-53, 1954.
 
-<BR>
+<br>
 
 J. B. Douglas.  Clustering and aggregation.
-<EM>Sankhya B</EM>, 
+<em>Sankhya B</em>, 
 37:398-417, 1975.
 
-<BR>
+<br>
 
 R. A. Fisher, H. G. Thornton, and W. A. Mackenzie.
 The accuracy of the plating method of estimating the density of
 bacterial populations.
-<EM>Annals of Applied Biology</EM>, 
+<em>Annals of Applied Biology</em>, 
 9:325-359, 1922.
 
-<BR>
+<br>
 
 M. Lloyd.
 Mean crowding.
-<EM>Journal of Animal Ecology</EM>, 
+<em>Journal of Animal Ecology</em>, 
 36:1-30, 1967.
 
-<BR>
+<br>
 
 M. Morista.
 Measuring the dispersion and analysis of distribution patterns.
-<EM>Memoires of the Faculty of Science, Kyushu University, Series E.
-Biology</EM>, 2:215-235, 1959.
+<em>Memoires of the Faculty of Science, Kyushu University, Series E.
+Biology</em>, 2:215-235, 1959.
 
-<H2>BUGS</H2>
-<P>
+<h2>BUGS</h2>
+<p>
 Timestamp not working for header part of counts output. (2000-10-28)
-<P>
+<p>
 Please send all bug fixes and comments to the author
 or the grass development team. <br>
 <a href="http://grass.itc.it"><tt>http://grass.itc.it</tt></a>.
 
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
 
-<A HREF="http://mccauley-usa.com/">James Darrell McCauley</A>
-<A HREF="mailto:darrell at mccauley-usa.com">&lt;darrell at mccauley-usa.com&gt;</A>,
+<a href="http://mccauley-usa.com/">James Darrell McCauley</A>
+<a href="mailto:darrell at mccauley-usa.com">&lt;darrell at mccauley-usa.com&gt;</A>,
 <br>when he was at: 
-<A HREF="http://ABE.www.ecn.purdue.edu/ABE/">Agricultural Engineering</A>
-<A HREF="http://www.purdue.edu/">Purdue University</A>
+<a href="http://ABE.www.ecn.purdue.edu/ABE/">Agricultural Engineering</A>
+<a href="http://www.purdue.edu/">Purdue University</A>
 
-<P>
+<p>
 Modified for GRASS 5.0 by Eric G. Miller (2000-10-28)
-<BR>
+<br>
 Modified for GRASS 5.7 by R. Blazek (2004-10-14)
 
 

Modified: grass/trunk/vector/v.random/v.random.html
===================================================================
--- grass/trunk/vector/v.random/v.random.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/vector/v.random/v.random.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -1,6 +1,6 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
-<EM>v.random</EM> randomly generates vector points within the
+<em>v.random</em> randomly generates vector points within the
 current region using the selected random number generator.
 
 <p><em>v.random</em> can generate also 3D vector points or
@@ -40,32 +40,32 @@
 v.what.vect vector=random_samples layer=1 column=geology qvector=geology at PERMANENT qlayer=1 qcolumn=label 
 </pre></div>
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
-UNIX man pages for <EM>rand(3)</EM> and <EM>drand48(3)</EM>.
-<P>
-<EM>
-<A HREF="g.region.html">g.region</a>,
-<A HREF="r.random.html">r.random</a>,
-<A HREF="v.perturb.html">v.perturb</A>,
-<A HREF="v.sample.html">v.sample</A>
+UNIX man pages for <em>rand(3)</em> and <em>drand48(3)</em>.
+<p>
+<em>
+<a href="g.region.html">g.region</a>,
+<a href="r.random.html">r.random</a>,
+<a href="v.perturb.html">v.perturb</A>,
+<a href="v.sample.html">v.sample</A>
 <a href="v.what.rast.html">v.what.rast</a>
 <a href="v.what.vect.html">v.what.vect</a>
-</EM>
+</em>
 
-<H2>BUGS</H2>
+<h2>BUGS</h2>
 
 The RNG used by 
-<EM><A HREF="v.perturb.html">v.perturb</A></EM>
-should probably be added to this program.<BR>
+<em><a href="v.perturb.html">v.perturb</A></em>
+should probably be added to this program.<br>
 
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
 
-<A HREF="http://mccauley-usa.com/">James Darrell McCauley</A>
-<A HREF="mailto:darrell at mccauley-usa.com">&lt;darrell at mccauley-usa.com&gt;</A>,
+<a href="http://mccauley-usa.com/">James Darrell McCauley</A>
+<a href="mailto:darrell at mccauley-usa.com">&lt;darrell at mccauley-usa.com&gt;</A>,
 <br>when he was at: 
-<A HREF="http://ABE.www.ecn.purdue.edu/ABE/">Agricultural
+<a href="http://ABE.www.ecn.purdue.edu/ABE/">Agricultural
 Engineering</A>
-<A HREF="http://www.purdue.edu/">Purdue University</A>
+<a href="http://www.purdue.edu/">Purdue University</A>
 
 <p><i>Last changed: $Date$</i>

Modified: grass/trunk/vector/v.reclass/v.reclass.html
===================================================================
--- grass/trunk/vector/v.reclass/v.reclass.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/vector/v.reclass/v.reclass.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -1,6 +1,6 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
-<EM>v.reclass</EM> allows user to create a new vector map based on
+<em>v.reclass</em> allows user to create a new vector map based on
 the reclassification of an existing vector map. It also allows the user
 to change the <i>key column</i> away from the default of "<b>cat</b>" with
 the <b>column</b> option.
@@ -17,7 +17,7 @@
 
 
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 
 No table is created for the reclassed map if the <B>column</B> option is
 used and the column type is integer (as the result could contain ambiguities).
@@ -27,13 +27,13 @@
 column containing the unique string column values, sorted in alphabetical
 order.
 
-<P>
+<p>
 For dissolving common boundaries, see 
 <em><a href="v.dissolve.html">v.dissolve</a></em>.
 
 
 
-<H2>EXAMPLES</H2>
+<h2>EXAMPLES</h2>
 
 
 <H3>Example 1: Reclass by rules</H3>
@@ -52,8 +52,8 @@
 where use = 'E14'
 </pre></div>
 
-Produces a new vector area map <EM>land_u</EM> containing boundaries from
-<EM>land</EM> with area category values selected from database by SQL
+Produces a new vector area map <em>land_u</em> containing boundaries from
+<em>land</em> with area category values selected from database by SQL
 select statement:
 <br>
 <tt>select id from tland where use = 'E13' and owner = 'Jara Cimrman'</tt>
@@ -78,24 +78,24 @@
 </pre></div>
 
 
-<H2>BUGS</H2>
+<h2>BUGS</h2>
 
 No table is created for reclassed layer if <B>rules</B> option is used.
 
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
 <em>
-<a HREF="v.dissolve.html">v.dissolve</a>,
-<A HREF="v.extract.html">v.extract</A>
+<a href="v.dissolve.html">v.dissolve</a>,
+<a href="v.extract.html">v.extract</A>
 </em>
 <p>
-<em><a HREF="sql.html">GRASS SQL interface</a></em>
+<em><a href="sql.html">GRASS SQL interface</a></em>
 
 
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
 
-R.L. Glenn, USDA, SCS, NHQ-CGIS<BR>
+R.L. Glenn, USDA, SCS, NHQ-CGIS<br>
 from v.reclass to v.db.reclass and later to v.reclass in 5.7 rewritten
 by Radim Blazek
 

Modified: grass/trunk/vector/v.sample/v.sample.html
===================================================================
--- grass/trunk/vector/v.sample/v.sample.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/vector/v.sample/v.sample.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -1,40 +1,40 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
-<EM>v.sample</EM> samples a GRASS raster map at the point
+<em>v.sample</em> samples a GRASS raster map at the point
 locations in the input file by either cubic convolution
 interpolation, bilinear interpolation, or nearest neighbor
 sampling (default).
 
-<P>
+<p>
 
 This program may be especially useful when sampling for
 cross validation of interpolations whose output is a raster
 map.
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 
 The output points will have the easting and northing of the input points.
 The input category value is used. The input attribute, raster value 
 and difference is written to output.
 
-<P>
+<p>
 When NULL values are encountered for a cell, zero value is used
 instead.  In these cases, more acurrate results may be obtained
 by using the default nearest neighbor comparisons.
 
-<P>
+<p>
 
 This program may not work properly with lat-long data when
 the <B>-BC</B> flags are used.
 
-<P>
+<p>
 
 When interpolation is done (i.e., the <B>-BC</B> flags are
 used), values are assumed to be located at the centroid of
 grid cells.  Therefore, current resolution settings are
 important.
 
-<H2>EXAMPLE</H2>
+<h2>EXAMPLE</h2>
 
 Comparison of "elevation.dem" and "elevation.10m" Spearfish maps
 at random places:
@@ -60,28 +60,28 @@
 </pre></div>
 
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
-<EM>
-<A HREF="v.random.html">v.random</A>,
-<A HREF="g.region.html">g.region</A>
-</EM>
+<em>
+<a href="v.random.html">v.random</A>,
+<a href="g.region.html">g.region</A>
+</em>
 
 
-<EM>Image Sampling Methods</EM> - GRASS Tutorial on <EM>s.sample</EM>
+<em>Image Sampling Methods</em> - GRASS Tutorial on <em>s.sample</em>
 (available as 
-<A HREF="http://grass.itc.it/gdp/sites/">s.sample-tutorial.ps.gz</A>) 
+<a href="http://grass.itc.it/gdp/sites/">s.sample-tutorial.ps.gz</A>) 
 
 
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
 
-<A HREF="http://mccauley-usa.com/">James Darrell McCauley</A>
+<a href="http://mccauley-usa.com/">James Darrell McCauley</A>
 <br>when he was at: 
-<A HREF="http://ABE.www.ecn.purdue.edu/ABE/">Agricultural Engineering</A>
-<A HREF="http://www.purdue.edu/">Purdue University</A>
-<P>
+<a href="http://ABE.www.ecn.purdue.edu/ABE/">Agricultural Engineering</A>
+<a href="http://www.purdue.edu/">Purdue University</A>
+<p>
 Updated for GRASS 5.0 by Eric G. Miller
-<BR>
+<br>
 Updated for GRASS 5.7 by Radim Blazek
 
 <p><i>Last changed: $Date$</i>

Modified: grass/trunk/vector/v.segment/v.segment.html
===================================================================
--- grass/trunk/vector/v.segment/v.segment.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/vector/v.segment/v.segment.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -3,7 +3,7 @@
 <em>v.segment</em> generates segments or points from input lines and from
 positions read from a text file or '<tt>stdin</tt>'.
 
-<P>
+<p>
 The format is:
 <div class="code"><pre>
 P &lt;point id&gt;   &lt;line cat&gt; &lt;offset&gt; [&lt;side offset&gt;]
@@ -21,10 +21,10 @@
 (pipe or redirect from file into the command).<br>
 
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 
 A segment is only created for the first line found of the specified category.
-<P>
+<p>
 Points are generated along the lines at the given distance(s) from the
 beginning of the vector line.
 <p>
@@ -34,9 +34,9 @@
 the direction of vector lines). As the segment distance is measured along the
 original line, side-offset lines will be longer than the start-end segment distance
 for outside corners of curving lines, and shorter for inside corners.
-<P>
+<p>
 All offsets are measured in map units (see "<em>g.proj -p</em>").
-<P>
+<p>
 To place a point in the middle of a line, the <em>v.to.db</em> module may be
 used to find the line's length. Then half of that distance can be used as the
 along-line offset.
@@ -113,14 +113,14 @@
 <h2>SEE ALSO</h2>
 
 <em>
-<a href="lrs.html">LRS tutorial</a> (Linear Referencing System),<BR>
+<a href="lrs.html">LRS tutorial</a> (Linear Referencing System),<br>
 <a href="d.vect.html">d.vect</a>,
 <a href="v.build.polylines.html">v.build.polylines</a>,
 <a href="v.lrs.segment.html">v.lrs.segment</a>,
 <a href="v.parallel.html">v.parallel</a>,
 <a href="v.split.html">v.split</a>,
-<a HREF="v.to.db.html">v.to.db</a>,
-<a HREF="v.to.points.html">v.to.points</a>
+<a href="v.to.db.html">v.to.db</a>,
+<a href="v.to.points.html">v.to.points</a>
 </em>
 
 <h2>AUTHOR</h2>

Modified: grass/trunk/vector/v.select/v.select.html
===================================================================
--- grass/trunk/vector/v.select/v.select.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/vector/v.select/v.select.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -61,13 +61,13 @@
 <h2>SEE ALSO</h2>
 
 <em>
-<a HREF="v.category.html">v.category</a>,
-<a HREF="v.overlay.html">v.overlay</a>
+<a href="v.category.html">v.category</a>,
+<a href="v.overlay.html">v.overlay</a>
 </em>
 
 <p>
 <em>
-<a HREF="sql.html">GRASS SQL interface</a>
+<a href="sql.html">GRASS SQL interface</a>
 </em>
 
 

Modified: grass/trunk/vector/v.support/v.support.html
===================================================================
--- grass/trunk/vector/v.support/v.support.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/vector/v.support/v.support.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -13,12 +13,12 @@
 v.info myvectmap
 </pre></div>
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
-<EM>
-	<A HREF="v.build.html">v.build</A>,
-        <A HREF="v.info.html">v.info</A>
-</EM>
+<em>
+	<a href="v.build.html">v.build</A>,
+        <a href="v.info.html">v.info</A>
+</em>
 
 <h2>AUTHOR</h2>
 

Modified: grass/trunk/vector/v.surf.idw/v.surf.idw.html
===================================================================
--- grass/trunk/vector/v.surf.idw/v.surf.idw.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/vector/v.surf.idw/v.surf.idw.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -1,7 +1,7 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
 <p>
-<EM>v.surf.idw</EM> fills a raster matrix with interpolated
+<em>v.surf.idw</em> fills a raster matrix with interpolated
 values generated from a set of irregularly spaced data
 points using numerical approximation (weighted averaging)
 techniques. The interpolated value of a cell is determined
@@ -11,14 +11,14 @@
 more complex surfaces (particularly those with anomalous
 features), restricts the spatial influence of any errors,
 and generates the interpolated surface from the data
-points.</p>
+points.
 
-<P>
+<p>
 This program allows the user to use a GRASS vector point map file,
-rather than a raster map layer, as input.</p>
+rather than a raster map layer, as input.
 
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 
 <p>
 The amount of memory used by this program is related to the number
@@ -27,14 +27,14 @@
 not be able to get all the memory it needs from the
 system.  The time required to execute is related to the 
 resolution of the current region, after an initial delay 
-determined by the time taken to read the input vector points map.</p>
+determined by the time taken to read the input vector points map.
 
 <p>
 To read and interpolate from the elevation co-ordinates as 3rd dimension
 of the vector geometry, use the <em>-z</em> flag. In this case no <em>column</em>
-parameter has to be specified.</p>
+parameter has to be specified.
 
-<P>
+<p>
 If the user has a mask set, then interpolation is only done
 for those cells that fall within the mask. However, all
 vector points in the current region are used even
@@ -43,37 +43,37 @@
 be set and a mask used to limit interpolation to a smaller area
 if it is desired to use vector points from outside the region in the
 interpolation. The <em>-n</em> flag may also be used to
-achieve a similar result.</p>
+achieve a similar result.
 
 <p>
-If more than <EM>count</EM> points fall into one target raster cell, 
+If more than <em>count</em> points fall into one target raster cell, 
 the mean of all the site values will determine the cell value (unless
-the -n flag is specified, in which case only the <EM>count</EM> 
-points closest to the centre of the cell will be interpolated).</p>
+the -n flag is specified, in which case only the <em>count</em> 
+points closest to the centre of the cell will be interpolated).
 
-<P>
-By setting <EM>npoints=1</EM>, the module can be used 
-to calculate raster Voronoi diagrams (Thiessen polygons).</p>
+<p>
+By setting <em>npoints=1</em>, the module can be used 
+to calculate raster Voronoi diagrams (Thiessen polygons).
 
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
-<EM><A HREF="d.vect.html">d.vect</A></EM><br>
-<EM><A HREF="g.region.html">g.region</A></EM><br>
-<EM><A HREF="r.surf.contour.html">r.surf.contour</A></EM><br>
-<EM><A HREF="r.surf.idw.html">r.surf.idw</A></EM><br>
-<EM><A HREF="r.surf.idw2.html">r.surf.idw2</A></EM><br>
-<EM><A HREF="r.surf.gauss.html">r.surf.gauss</A></EM><br>
-<EM><A HREF="r.surf.fractal.html">r.surf.fractal</A></EM><br>
-<EM><A HREF="r.surf.random.html">r.surf.random</A></EM><br>
-<EM><A HREF="v.surf.rst.html">v.surf.rst</A></EM>
+<em><a href="d.vect.html">d.vect</A></em><br>
+<em><a href="g.region.html">g.region</A></em><br>
+<em><a href="r.surf.contour.html">r.surf.contour</A></em><br>
+<em><a href="r.surf.idw.html">r.surf.idw</A></em><br>
+<em><a href="r.surf.idw2.html">r.surf.idw2</A></em><br>
+<em><a href="r.surf.gauss.html">r.surf.gauss</A></em><br>
+<em><a href="r.surf.fractal.html">r.surf.fractal</A></em><br>
+<em><a href="r.surf.random.html">r.surf.random</A></em><br>
+<em><a href="v.surf.rst.html">v.surf.rst</A></em>
 
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
 
 Michael Shapiro,  
 U.S. Army Construction Engineering 
 Research Laboratory
-<BR>
+<br>
 Improved algorithm (indexes points according to cell and ignores
 points outside current region) by Paul Kelly
 

Modified: grass/trunk/vector/v.surf.rst/v.surf.rst.html
===================================================================
--- grass/trunk/vector/v.surf.rst/v.surf.rst.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/vector/v.surf.rst/v.surf.rst.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -59,7 +59,7 @@
 which represent the quad tree used for segmentation and overlapping neighborhoods
 from which additional points for approximation on each segment were taken.
 
-<P>
+<p>
 
 Predictive error of surface approximation for given parameters can be computed using the 
 <b>-c</b> flag. A crossvalidation procedure is then performed using the data given in the vector map 
@@ -99,7 +99,7 @@
 360 to the East, the values increase counterclockwise. Curvatures are positive
 for convex and negative for concave areas. Singular points with undefined
 curvatures have assigned zero values.
-</p><p><em>Tension</em> and <em>smooth</em>ing allow user to tune the surface character.
+<p><em>Tension</em> and <em>smooth</em>ing allow user to tune the surface character.
 For most landscape scale applications the default values should provide adequate results.
 The program gives warning when significant overshoots appear in the resulting
 surface and higher tension or smoothing should be used.
@@ -128,7 +128,7 @@
 to <em>dnorm</em> (dnorm rescales the coordinates depending on the average
 data density so that the size of segments with <em>segmax=</em>40 points
 is around 1 - this ensures the numerical stability of the computation):
-</p><p>1. Default: the given <em>tension</em>
+<p>1. Default: the given <em>tension</em>
 is applied to normalized data (x/<em>dnorm</em>..), that means that
 the distances are multiplied (rescaled) by <em>tension/dnorm</em>. If density
 of points is changed, e.g., by using higher <em>dmin</em>, the <em>dnorm</em>
@@ -152,9 +152,9 @@
 20-30. If it is lower or higher, the given <em>tension</em> parameter
 should be changed accordingly.
 
-</p><p>The default is a recommended choice, however for the applications where
+<p>The default is a recommended choice, however for the applications where
 the user needs to change density of data and preserve the approximation
-character the <b>-t</b> flag can be helpful.</p>
+character the <b>-t</b> flag can be helpful.
 <p>Anisotropic data (e.g. geologic phenomena) can be interpolated using <em>theta</em> 
 and <em>scalex</em> defining orientation 
 and ratio of the perpendicular axes put on the longest/shortest side of the feature, respectively.
@@ -168,8 +168,8 @@
 parameters may not be computed correctly) - if there are
 problems, please report to GRASS bugtracker 
 (accessible from <a href="http://grass.osgeo.org/">http://grass.osgeo.org/</a>).<br>
-</p>
 
+
 <!--
 <p>The program gives warning when significant overshoots appear and higher
 tension should be used. However, with tension too high the resulting surface
@@ -182,8 +182,8 @@
 <p>For data with values changing over several magnitudes (sometimes the
 concentration or density data) it is suggested to interpolate the log of
 the values rather than the original ones.
-</p>
 
+
 <p>The program checks the numerical stability of the algorithm by computing
 the values in given points, and prints the root mean square deviation (rms)
 found into the history file of raster map <em>elev</em>. For computation
@@ -194,14 +194,14 @@
 to the trend. The rms then represents a measure of smoothing effect on
 data. More detailed analysis of smoothing effects can be performed using
 the output deviations option.
-</p>
 
+
 <h3>SQL support</h3>
 
 Using the <em>where</em> parameter, the interpolation can be limited to use
 only a subset of the input vectors.
 
-<P>
+<p>
 Spearfish example (we simulate randomly distributed elevation measures):
 
 <div class="code"><pre>
@@ -249,38 +249,38 @@
 The parameters found by minimizing the predictive (CV) error may not not be the best for
 for poorly sampled phenomena (result could be strongly smoothed with lost details and fluctuations)
 or when significant noise is present that needs to be smoothed out.
-</p>
 
+
 <p>The program writes the values of parameters used in computation into
 the comment part of history file <em>elev</em> as well as the following values
 which help to evaluate the results and choose the suitable parameters:
 minimum and maximum z values in the data file (zmin_data, zmax_data) and
 in the interpolated raster map (zmin_int, zmax_int), rescaling parameter
 used for normalization (dnorm), which influences the tension.
-</p><p>If visible connection of segments appears, the program should be rerun
+<p>If visible connection of segments appears, the program should be rerun
 with higher <em>npmin</em> to get more points from the neighborhood of given
 segment and/or with higher tension.
 
-</p><p>When the number of points in a vector map is not too large (less than
+<p>When the number of points in a vector map is not too large (less than
 800), the user can skip segmentation by setting <em>segmax</em> to the number
 of data points or <em>segmax=700</em>.
-</p><p>The program gives warning when user wants to interpolate outside the
+<p>The program gives warning when user wants to interpolate outside the
 rectangle given by minimum and maximum coordinates in the vector map,
 zoom into the area where the given data are is suggested in this case.
-</p><p>When a mask is used, the program takes all points in the given region
+<p>When a mask is used, the program takes all points in the given region
 for approximation, including those in the area which is masked out, to
 ensure proper approximation along the border of the mask. It therefore
 does not mask out the data points, if this is desirable, it must be done
 outside <em>v.surf.rst</em>.
-</p>
 
+
 <p>For examples of applications see
 <a href="http://skagit.meas.ncsu.edu/~helena/gmslab/">GRASS4 implementation</a> and
 <a href="http://skagit.meas.ncsu.edu/~helena/">GRASS5 and GRASS6 implementation</a>.
-</p><p>The user must run <a href="g.region.html">g.region</a> before the program
+<p>The user must run <a href="g.region.html">g.region</a> before the program
 to set the region and resolution for approximation.
-</p>
 
+
 <h2>SEE ALSO</h2>
 
 <em><a href="v.vol.rst.html">v.vol.rst</a></em>
@@ -292,64 +292,64 @@
 USA (1990-2000); Department of Physics, North Carolina State University, Raleigh
 <br>Helena Mitasova, USA CERL, Department of Geography, University of Illinois at
 Urbana-Champaign, USA (1990-2001); MEAS, North Carolina State University, Raleigh 
-</p><p><em>Modified program (translated to C, adapted for GRASS, new segmentation
+<p><em>Modified program (translated to C, adapted for GRASS, new segmentation
 procedure):</em>
 <br>Irina Kosinovsky, US Army CERL, Dave Gerdes, US Army CERL
-</p><p><em>Modifications for new sites format and timestamping:</em>
+<p><em>Modifications for new sites format and timestamping:</em>
 <br>Darrel McCauley, Purdue University, Bill Brown, US Army CERL
-</p><p><em>Update for GRASS5.7, GRASS6 and addition of crossvalidation:</em>
+<p><em>Update for GRASS5.7, GRASS6 and addition of crossvalidation:</em>
 Jaroslav Hofierka, University of Presov; Radim Blazek, ITC-irst
-</p>
 
+
 <h2> REFERENCES</h2>
-<P>
+<p>
 <a href="http://skagit.meas.ncsu.edu/~helena/gmslab/papers/IEEEGRSL2005.pdf">
 Mitasova, H., Mitas, L. and Harmon, R.S., 2005,</a> 
 Simultaneous spline approximation and topographic analysis for
 lidar elevation data in open source GIS, IEEE GRSL 2 (4), 375- 379.
-<P>
+<p>
 Hofierka, J., 2005, Interpolation of Radioactivity Data Using Regularized Spline with Tension. Applied GIS, Vol. 1, No. 2, 
 pp. 16-01 to 16-13. DOI: 10.2104/ag050016
-</P>
-<P>
+
+<p>
 <a href="http://skagit.meas.ncsu.edu/~helena/gmslab/papers/TGIS2002_Hofierka_et_al.pdf">
 Hofierka J., Parajka J.,  Mitasova H., Mitas L., 2002,</a>
 Multivariate Interpolation of Precipitation Using Regularized Spline with Tension.
 Transactions in GIS 6(2), pp. 135-150.
-</P>
-<P>
+
+<p>
 H. Mitasova, L. Mitas, B.M. Brown, D.P. Gerdes, I. Kosinovsky, 1995, Modeling
 spatially and temporally distributed phenomena: New methods and tools for
 GRASS GIS. International Journal of GIS, 9 (4), special issue on Integrating
 GIS and Environmental modeling, 433-446.
-</P>
+
 <p>
 <a href="http://skagit.meas.ncsu.edu/~helena/gmslab/papers/MG-I-93.pdf">
 Mitasova, H. and Mitas, L., 1993</a>: 
 Interpolation by Regularized Spline with Tension: 
 I. Theory and Implementation, Mathematical Geology ,25, 641-655.
-</p>
+
 <p>
 <a href="http://skagit.meas.ncsu.edu/~helena/gmslab/papers/MG-II-93.pdf">
 Mitasova, H. and Hofierka, J., 1993</a>: Interpolation
 by Regularized Spline with Tension: II. Application to Terrain Modeling
 and Surface Geometry Analysis, Mathematical Geology 25, 657-667.
-</p>
+
 <p>
 <a href="http://skagit.meas.ncsu.edu/~helena/gmslab/papers/CMA1988.pdf">
 Mitas, L., and Mitasova H., 1988, </a> General variational approach to the approximation
 problem, Computers and Mathematics with Applications, v.16, p. 983-992.
-</p>
 
+
 <p>
 <a href="http://www.grassbook.org">
 Neteler, M. and Mitasova, H., 2008, Open Source GIS: A GRASS GIS Approach, 3rd Edition, </a> 
 Springer, New York, 406 pages.
-</p>
 
+
 <p>Talmi, A. and Gilat, G., 1977 : Method for Smooth Approximation of Data,
 Journal of Computational Physics, 23, p.93-123.
-</p>
+
 <p>Wahba, G., 1990, : Spline Models for Observational Data, CNMS-NSF Regional
 Conference series in applied mathematics, 59, SIAM, Philadelphia, Pennsylvania.
 

Modified: grass/trunk/vector/v.to.db/v.to.db.html
===================================================================
--- grass/trunk/vector/v.to.db/v.to.db.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/vector/v.to.db/v.to.db.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -1,4 +1,4 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
 <em>v.to.db</em> loads vector map features or metrics into a database
 table, or prints them (or the SQL queries used to obtain them) in a
@@ -7,10 +7,10 @@
 found or multiple categories were found. For line azimuths '-1' is used
 for closed lines (start equals end).
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 The units <em>miles</em>, <em>feet</em>, <em>meters</em> and
 <em>kilometers</em> are square for <em>option=area</em>.
-<P>
+<p>
 Feet and acre units are always reported in their common versions
 (i.e. the International Foot, exactly 5280 feet in a mile), even
 when the location's standard map unit is the US Survey foot.
@@ -44,7 +44,7 @@
 <em><a href="v.db.addcolumn.html">v.db.addcolumn</a></em> to add new columns if
 needed.
 
-<H2>EXAMPLES</H2>
+<h2>EXAMPLES</h2>
 
 <h3>Updating attribute tables</h3>
 
@@ -86,7 +86,7 @@
 v.to.db usa_income_employment2002 option=query col=FIPS_NUM qcol=STATE_FIPS
 </pre></div>
 
-<P>
+<p>
 Upload category numbers of left and right area, to an attribute table of
 boundaries common for the areas:<br>
 <div class="code"><pre>
@@ -176,7 +176,7 @@
 </ul>
 
 
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
 
 Radim Blazek, ITC-irst, Trento, Italy<br>
 Line sinuousity implemented by Wolf Bergenheim

Modified: grass/trunk/vector/v.to.points/v.to.points.html
===================================================================
--- grass/trunk/vector/v.to.points/v.to.points.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/vector/v.to.points/v.to.points.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -11,13 +11,13 @@
 The <em>dmax</em> parameter is the maximum limit but not an exact
 distance. To place points with exact distance from the beginning
 of the vector line the user should use
-<a HREF="v.segment.html">v.segment</a>.
+<a href="v.segment.html">v.segment</a>.
 
 <p>
 The <em>type</em> parameter is used to control which input vector
 geometry types to convert into points. 
 Some caveats to consider about this parameter:
-</p>
+
 <ul>
 <li>
 Points and centroids can be considered as "lines" with only one
@@ -64,7 +64,7 @@
 <h2>EXAMPLE</h2>
 
 In this example, the 't_powerlines' vector lines map in the
-<a HREF="http://grass.itc.it/download/data6.php">Spearfish 6</a>
+<a href="http://grass.itc.it/download/data6.php">Spearfish 6</a>
 location is used to create points along the input lines:
 
 <div class="code"><pre>
@@ -75,12 +75,12 @@
 <h2>SEE ALSO</h2>
 
 <em>
-<a HREF="v.segment.html">v.segment</a>,
-<a HREF="v.to.rast.html">v.to.rast</a>,
-<a HREF="v.to.db.html">v.to.db</a></em>
+<a href="v.segment.html">v.segment</a>,
+<a href="v.to.rast.html">v.to.rast</a>,
+<a href="v.to.db.html">v.to.db</a></em>
 
 <h2>AUTHOR</h2>
 
 Radim Blazek
 
-<p><i>Last changed: $Date$</i></p>
+<p><i>Last changed: $Date$</i>

Modified: grass/trunk/vector/v.to.rast/v.to.rast.html
===================================================================
--- grass/trunk/vector/v.to.rast/v.to.rast.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/vector/v.to.rast/v.to.rast.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -13,11 +13,11 @@
 therefore ensure that the current geographic region is
 correctly set and that the region resolution is at the
 desired level.
-<P>
+<p>
 Either the <em><b>column</b></em> parameter or the <em><b>value</b></em>
 parameter must be specified.  The <em><b>use</b></em> option may be 
 specified alone when using the <em>dir</em> option.
-<P>
+<p>
 <em><b>use</b></em> options are:
 <ul>
 <LI>
@@ -31,22 +31,22 @@
 <LI>
 <em>dir</em>  - output as flow direction in degrees (lines only)
 </ul>
-<P>
+<p>
 The <em><b>column</b></em> parameter uses an existing column from the vector map
 database table as the category value in the output raster map. Existing table 
 columns can be shown by using <em><a href="db.describe.html">db.describe</a></em>.
-<P>
+<p>
 An empty raster map layer will be created if the vector map layer has not
 been assigned category/attribute labels (e.g., through use of 
 <a href="v.category.html">v.category option=add</a>). 
-<P>
+<p>
 Otherwise:
 <ul>
 <LI>
 Labeled areas and/or centroids will produce filled raster coverages with edges 
 that straddle the original area boundary <b>as long as the boundary is NOT 
 labeled</b>.
-<BR>(Use <tt>v.category option=del type=boundary</tt> to remove.)
+<br>(Use <tt>v.category option=del type=boundary</tt> to remove.)
 <LI>
 Labeled lines and boundaries will produce lines of raster cells which touch the 
 original vector line. This tends to be more aggressive than area-only conversions.
@@ -54,11 +54,11 @@
 Points and orphaned centroids will be converted into single cells on the
 resultant raster map.
 </ul>
-<P>
-<P>
+<p>
+<p>
 <b>Flow directions</b> are given in degrees counterclockwise from east.
-<P>
-<P>
+<p>
+<p>
 Raster category labels are supported for all of <em>use=</em> except <em>use=z</em>.
 
 <h2>EXAMPLES</h2>
@@ -77,15 +77,15 @@
 v.to.rast in=vect_map out=raster_map col=SPEED
 </pre></div>
 
-<P>
-<P>
+<p>
+<p>
 <em>2. Calculate stream directions from a river vector map (Spearfish)</em><br>
 <div class="code"><pre>
 v.to.rast in=streams out=streamsdir use=dir
 </pre></div>
 
-<P>
-<P>
+<p>
+<p>
 <em>3. Convert a vector polygon map to raster including descriptive labels (Spearfish)</em><br>
 <div class="code"><pre>
 v.to.rast in=fields out=myfields use=attr col=cat labelcol=label
@@ -94,8 +94,8 @@
 
 <h2>SEE ALSO</h2>
 <em>
-<a HREF="db.describe.html">db.describe</a>,
-<a HREF="v.category.html">v.category</a>
+<a href="db.describe.html">db.describe</a>,
+<a href="v.category.html">v.category</a>
 </em>
 <br>
 
@@ -111,5 +111,5 @@
 <p>
 <p>
 <i>Last changed: $Date$</i>
-</p>
 
+

Modified: grass/trunk/vector/v.to.rast3/v.to.rast3.html
===================================================================
--- grass/trunk/vector/v.to.rast3/v.to.rast3.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/vector/v.to.rast3/v.to.rast3.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -1,8 +1,8 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
-<EM>v.to.rast3</EM> converts a GRASS 3D vector point map to a GRASS raster3d map.
+<em>v.to.rast3</em> converts a GRASS 3D vector point map to a GRASS raster3d map.
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 
 When converting from a 3D vector point layer to a raster3d map
 a vector point is converted into a single 3d cell
@@ -11,7 +11,7 @@
 
 
 <center>
-<img src=v.to.rast3.test.png border=0><BR>
+<img src=v.to.rast3.test.png border=0><br>
 <table border=0 width=600>
 <tr><td><center>
 <i>This screenshot shows the result of the v.to.rast3 test. Visualized are the cube of the
@@ -21,11 +21,11 @@
 </table>
 </center>
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
-<EM><A HREF="g.region.html">g.region</A></EM>
+<em><a href="g.region.html">g.region</A></em>
 
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
 
 Original s.to.rast3: Jaro Hofierka, Geomodel s.r.o.<br>
 Updated by Radim Blazek

Modified: grass/trunk/vector/v.transform/v.transform.html
===================================================================
--- grass/trunk/vector/v.transform/v.transform.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/vector/v.transform/v.transform.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -29,7 +29,7 @@
 </pre></div>
 
 <p>The ground control points may be also (ir)regularly distributed
-and can be more than four points.</p>
+and can be more than four points.
 
 <p>Transformation parameters (i.e. <em>xshift</em>, <em>yshift</em>,
 etc.) can be fetched from attribute table connected to the vector
@@ -55,7 +55,7 @@
 
 <p>Most DXF/DWG drawings are done within XY coordinate space. To transform 
 them to a national grid, we can use 'v.transform' with a 4 point 
-transformation.</p>
+transformation.
 
 <div class="code"><pre>
 v.transform -t in=watertowerXY out=watertowerUTM points=wt.points zscale=0.04 zshift=1320
@@ -105,7 +105,7 @@
 
 <h2>SEE ALSO</h2>
 
-<em><a HREF="v.in.ogr.html">v.in.ogr</a></em>
+<em><a href="v.in.ogr.html">v.in.ogr</a></em>
 
 <h2>AUTHOR</h2>
 

Modified: grass/trunk/vector/v.type/v.type.html
===================================================================
--- grass/trunk/vector/v.type/v.type.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/vector/v.type/v.type.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -10,7 +10,7 @@
 </pre></div>
 
 <h2>SEE ALSO</h2>
-<EM><A HREF="v.to.points.html">v.to.points</A></EM>
+<em><a href="v.to.points.html">v.to.points</A></em>
 
 <h2>AUTHOR</h2>
 

Modified: grass/trunk/vector/v.univar/v.univar.html
===================================================================
--- grass/trunk/vector/v.univar/v.univar.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/vector/v.univar/v.univar.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -1,4 +1,4 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
 <em>v.univar</em> calculates univariate statistics of vector map features.
 This includes the number of features counted, minimum and maximum values,
@@ -6,12 +6,12 @@
 Variance and standard deviation is calculated only for points if
 <tt>type=point</tt> is defined.
 
-<P>
+<p>
 
 Extended statistics adds median, 1st and 3rd quartiles, and 90th
 percentile.
 
-<H2>EXAMPLE</H2>
+<h2>EXAMPLE</h2>
 
 <div class="code"><pre>
 g.region rast=elevation.10m -p
@@ -24,12 +24,12 @@
 </pre></div>
 
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
-<EM><A HREF="v.neighbors.html">v.neighbors</A></EM>
+<em><a href="v.neighbors.html">v.neighbors</A></em>
 
 
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
 
 Radim Blazek, ITC-irst
 

Modified: grass/trunk/vector/v.vect.stats/v.vect.stats.html
===================================================================
--- grass/trunk/vector/v.vect.stats/v.vect.stats.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/vector/v.vect.stats/v.vect.stats.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -1,6 +1,6 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
-<EM>v.vect.stats</EM> counts the number of points in vector map
+<em>v.vect.stats</em> counts the number of points in vector map
 <em>points</em> falling into each area in vector map <em>areas</em>.
 Optionally statistics on point attributes in <em>points</em> are
 calculated for each area. The results are either uploaded to the
@@ -68,7 +68,7 @@
 </dl>
 
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 
 Points not falling into any area are ignored. Areas without category
 (no centroid attached or centroid without category) are ignored. 
@@ -79,16 +79,16 @@
 existing. If they do already exist, the <em>count_column</em> must be of
 type integer and the <em>stats_column</em> of type double.
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
-<EM>
+<em>
 <a href="v.distance.html">v.distance</a>,
 <a href="r.distance.html">r.distance</a>,
 <a href="v.what.vect.html">v.what.vect</a>
-</EM>
+</em>
 
 
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
 
 Markus Metz
 

Modified: grass/trunk/vector/v.vol.rst/v.vol.rst.html
===================================================================
--- grass/trunk/vector/v.vol.rst/v.vol.rst.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/vector/v.vol.rst/v.vol.rst.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -19,7 +19,7 @@
 parameteres are saved as
 3d raster maps <b>gradient, aspect1, aspect2, ncurv, gcurv, mcurv</b>,
 respectively.
-</p>
+
 <p>At first, data points are checked for identical positions and points
 that are closer to each other than given <b>dmin</b> are removed.
 Parameters <b>wmult</b> and <b>zmult</b> allow the user to re-scale 
@@ -31,7 +31,7 @@
 distances; if that is the case, the value of <b>zmult</b>
 should be selected so that the vertical and horizontal distances
 have about the same magnitude.
-</p>
+
 <p>Regularized spline with tension method is used in the interpolation.
 The <b>tension</b> parameter controls the distance over which 
 each given point influences the resulting volume (with very high tension, 
@@ -44,11 +44,11 @@
 smoothing parameter set to zero (<b>smooth=0</b>) the resulting volume
 passes exactly through the data points. 
 When smoothing is used, it is possible to output a vector map <b>devi</b>
-containing deviations of the resulting volume from the given data. </p>
+containing deviations of the resulting volume from the given data. 
 <p>The user can define a 2D raster map named <b>maskmap</b>, which will
 be used as a mask. The interpolation is skipped for 3-dimensional cells
 whose 2-dimensional projection has a zero value in the mask. Zero values will
-be assigned to these cells in all output 3d raster maps. </p>
+be assigned to these cells in all output 3d raster maps. 
 <p>If the number of given points is greater than 700, segmented
 processing is used. The region is split into 3-dimensional "box"
 segments, each having less than <b>segmax</b> points and interpolation
@@ -60,7 +60,7 @@
 must
 be larger than <b>segmax</b> and less than 700. This limit of 700 was
 selected to ensure the numerical stability and efficiency of the
-algorithm. </p>
+algorithm. 
 
 <h2>EXAMPLES</h2>
 
@@ -138,10 +138,10 @@
 very long time, so it might be worth to use just a sample data
 representing the whole dataset.
 
-<P>
+<p>
 <i>Example 
  (based on <a href="http://www.grassbook.org/data_menu2nd.phtml">Slovakia3d dataset</a>):</i>
-<P>
+<p>
 <div class="code"><pre>
 v.info -c precip3d
 v.vol.rst -c input=precip3d wcolumn=precip zmult=50 segmax=700 cvdev=cvdevmap tension=10
@@ -152,7 +152,7 @@
 Based on these results, the parameters will have to be optimized. It is
 recommended to plot the CV error as curve while modifying
 the parameters.
-<P>
+<p>
 The best approach is to start with <b>tension</b>, <b>smooth</b>
 and <b>zmult</b> with rough steps, or to set <b>zmult</b> to a
 constant somewhere between 30-60. This helps to find minimal RMSE
@@ -179,7 +179,7 @@
 <p><em>v.vol.rst</em> uses regularized spline with tension for
 interpolation from point data (as described in Mitasova and Mitas,
 1993). The implementation has an improved segmentation procedure based
-on Oct-trees which enhances the efficiency for large data sets. </p>
+on Oct-trees which enhances the efficiency for large data sets. 
 
 <p>Geometric parameters - magnitude of gradient (<b>gradient</b>),
 horizontal (<b>aspect1</b>) and vertical (<b>aspect2) </b>aspects,
@@ -187,7 +187,7 @@
 mean curvatures (<b>mcurv</b>) are computed directly from the
 interpolation function so that the important relationships between
 these parameters are preserved. More information on these parameters
-can be found in Mitasova et al., 1995 or Thorpe, 1979.</p>
+can be found in Mitasova et al., 1995 or Thorpe, 1979.
 
 <p>The program gives warning when significant overshoots appear and
 higher tension should be used. However, with tension too high the
@@ -195,27 +195,27 @@
 and everywhere else the volume goes rapidly to trend. With a smoothing
 parameter greater than zero, the volume will not pass through the data 
 points and the higher the parameter the closer the volume will be to the 
-trend. For theory on smoothing with splines see Talmi and Gilat, 1977 or Wahba, 1990. </p>
+trend. For theory on smoothing with splines see Talmi and Gilat, 1977 or Wahba, 1990. 
 
 <p>If a visible connection of segments appears, the program should be
 rerun with higher <b>npmin</b> to get more points from the
-neighborhood of given segment. </p>
+neighborhood of given segment. 
 
 <p>If the number of points in a vector map is less than 400, <b>segmax</b>
 should be set to 400 so that segmentation is not performed when it is
-not necessary. </p>
+not necessary. 
 
 <p>The program gives a warning when the user wants to interpolate outside the
 "box" given by minimum and maximum coordinates in the input vector map. 
 To remedy this, zoom into the area encompassing the input vector data points.
-</p>
 
+
 <p>For large data sets (thousands of data points), it is suggested to
 zoom into a smaller representative area and test whether the parameters
-chosen (e.g. defaults) are appropriate. </p>
+chosen (e.g. defaults) are appropriate. 
 
 <p>The user must run <em>g.region</em> before the program to set the
-3D region for interpolation. </p>
+3D region for interpolation. 
 
 <h2>BUGS</h2>
 <b>devi</b> file is written as 2D and deviations are not written as attributes.
@@ -224,49 +224,49 @@
 <p>Hofierka J., Parajka J., Mitasova H., Mitas L., 2002, Multivariate
 Interpolation of Precipitation Using Regularized Spline with Tension.
 Transactions in
-GIS&nbsp; 6, pp. 135-150. </p>
+GIS&nbsp; 6, pp. 135-150. 
 <p><a href="http://skagit.meas.ncsu.edu/%7Ehelena/gmslab/">Mitas, L.,
 Mitasova, H.</a>, 1999, Spatial Interpolation. In: P.Longley, M.F.
 Goodchild, D.J. Maguire, D.W.Rhind (Eds.), Geographical Information
 Systems: Principles, Techniques, Management and Applications, Wiley,
-pp.481-492 </p>
+pp.481-492 
 <p>Mitas L., Brown W. M., Mitasova H., 1997, <a
  href="http://skagit.meas.ncsu.edu/%7Ehelena/gmslab/lcgfin/cg-mitas.html">Role
 of dynamic cartography in simulations of landscape processes based on
 multi-variate fields.</a> Computers and Geosciences, Vol. 23, No. 4,
-pp. 437-446 (includes CDROM and WWW: www.elsevier.nl/locate/cgvis) </p>
+pp. 437-446 (includes CDROM and WWW: www.elsevier.nl/locate/cgvis) 
 <p>Mitasova H., Mitas L.,&nbsp; Brown W.M.,&nbsp; D.P. Gerdes, I.
 Kosinovsky, Baker, T.1995, Modeling spatially and temporally
 distributed phenomena:
 New methods and tools for GRASS GIS. International Journal of GIS, 9
 (4),
-special issue on Integrating GIS and Environmental modeling, 433-446. </p>
+special issue on Integrating GIS and Environmental modeling, 433-446. 
 <p> Mitasova, H., Mitas, L., Brown, B., Kosinovsky, I., Baker, T.,
 Gerdes, D. (1994): <a
  href="http://skagit.meas.ncsu.edu/%7Ehelena/gmslab/viz/ches.html">Multidimensional
-interpolation and visualization in GRASS GIS</a> </p>
+interpolation and visualization in GRASS GIS</a> 
 <p><a
  href="http://skagit.meas.ncsu.edu/%7Ehelena/gmslab/papers/lmg.rev1.ps">Mitasova
 H. and Mitas L. 1993</a>: Interpolation by Regularized Spline with
 Tension: I. Theory and Implementation, <i>Mathematical Geology</i> 25,
-641-655. </p>
+641-655. 
 <p><a
  href="http://skagit.meas.ncsu.edu/%7Ehelena/gmslab/papers/hmg.rev1.ps">Mitasova
 H. and Hofierka J. 1993</a>: Interpolation by Regularized Spline with
 Tension: II. Application to Terrain Modeling and Surface Geometry
-Analysis, <i>Mathematical Geology</i> 25, 657-667. </p>
+Analysis, <i>Mathematical Geology</i> 25, 657-667. 
 <p>Mitasova, H., 1992 : New capabilities for interpolation and
-topographic analysis in GRASS, GRASSclippings 6, No.2 (summer), p.13. </p>
+topographic analysis in GRASS, GRASSclippings 6, No.2 (summer), p.13. 
 <p>Wahba, G., 1990 : Spline Models for Observational Data, CNMS-NSF
 Regional Conference series in applied mathematics, 59, SIAM,
-Philadelphia, Pennsylvania. </p>
+Philadelphia, Pennsylvania. 
 <p>Mitas, L., Mitasova H., 1988 : General variational approach to the
 interpolation problem, Computers and Mathematics with Applications 16,
-p. 983 </p>
+p. 983 
 <p>Talmi, A. and Gilat, G., 1977 : Method for Smooth Approximation of
-Data, Journal of Computational Physics, 23, p.93-123. </p>
+Data, Journal of Computational Physics, 23, p.93-123. 
 <p>Thorpe, J. A. (1979): Elementary Topics in Differential Geometry.
-Springer-Verlag, New York, pp. 6-94.</p>
+Springer-Verlag, New York, pp. 6-94.
 
 <h2>SEE ALSO</h2>
 <a href="g.region.html">g.region</a>,
@@ -284,18 +284,18 @@
 <a href="mailto:lubos_mitas at ncsu.edu">lubos_mitas at ncsu.edu</a><br>
 Helena Mitasova, Department of Marine, Earth and Atmospheric Sciences,
 North Carolina State University, Raleigh, USA, <a
- href="mailto:hmitaso at unity.ncsu.edu">hmitaso at unity.ncsu.edu</a></p>
+ href="mailto:hmitaso at unity.ncsu.edu">hmitaso at unity.ncsu.edu</a>
 <p>Modified program (translated to C, adapted for GRASS, new
 segmentation procedure): <br>
 Irina Kosinovsky, US Army CERL, Champaign, Illinois, USA <br>
-Dave Gerdes, US Army CERL, Champaign, Illinois, USA </p>
+Dave Gerdes, US Army CERL, Champaign, Illinois, USA 
 <p>Modifications for g3d library, geometric parameters,
 cross-validation, deviations: <br>
 Jaro Hofierka, Department of Geography and Regional Development,
 University of Presov, Presov, Slovakia, <a
  href="MAILTO:hofierka at fhpv.unipo.sk">hofierka at fhpv.unipo.sk</a>, <a
  href="http://www.geomodel.sk">http://www.geomodel.sk</a> <br>
-&nbsp; </p>
+&nbsp; 
 
 
-<p><i>Last changed: $Date$</i> </p>
+<p><i>Last changed: $Date$</i> 

Modified: grass/trunk/vector/v.voronoi/v.voronoi.html
===================================================================
--- grass/trunk/vector/v.voronoi/v.voronoi.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/vector/v.voronoi/v.voronoi.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -1,16 +1,16 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
-<EM>v.voronoi</EM> uses an existing vector points map (<B>input</B>) to create
+<em>v.voronoi</em> uses an existing vector points map (<B>input</B>) to create
 a Voronoi diagram (Thiessen polygons) in a new vector map (<B>output</B>).
-<P>
+<p>
 The bounds of the output map are limited by the current region.
 (see <em>g.region</em>)
-<P>
+<p>
 
-<BR>
+<br>
 Voronoi diagram and Delaunay triangulation example:
 <center>
-<img src=v_voronoi_delaunay.png border=1><BR>
+<img src=v_voronoi_delaunay.png border=1><br>
 <table border=0 width=590>
 <tr><td><center>
 <i>Delaunay Triangulation (left pane), Voronoi diagram (center pane),
@@ -20,16 +20,16 @@
 </center>
 
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 
 Voronoi diagrams may be used for nearest-neighbor flood filling.
 Give the centroids attributes (start with
-<em><A HREF="v.db.addcolumn.html">v.db.addcolumn</A></em>),
+<em><a href="v.db.addcolumn.html">v.db.addcolumn</A></em>),
 then optionally convert to a raster map with
-<em><A HREF="v.to.rast.html">v.to.rast</A></em>.
+<em><a href="v.to.rast.html">v.to.rast</A></em>.
 
 
-<H2>EXAMPLE</H2>
+<h2>EXAMPLE</h2>
 
 Commands used with the Spearfish dataset to create the above figure.
 <div class="code"><pre>
@@ -55,27 +55,27 @@
 </pre></div>
 
 
-<H2>BUGS</H2>
+<h2>BUGS</h2>
 Only attribute table of field 1 is copied. 
 
 
-<H2>REFERENCES</H2>
-<EM>Steve J. Fortune,  (1987).  A Sweepline Algorithm for
-    Voronoi Diagrams, Algorithmica 2, 153-174.</EM>
+<h2>REFERENCES</h2>
+<em>Steve J. Fortune,  (1987).  A Sweepline Algorithm for
+    Voronoi Diagrams, Algorithmica 2, 153-174.</em>
 
 
-<H2>SEE ALSO</H2>
-<EM>
-<A HREF="g.region.html">g.region</A>,
-<A HREF="v.delaunay.html">v.delaunay</A>, 
-<A HREF="v.hull.html">v.hull</A>
-</EM>
+<h2>SEE ALSO</h2>
+<em>
+<a href="g.region.html">g.region</A>,
+<a href="v.delaunay.html">v.delaunay</A>, 
+<a href="v.hull.html">v.hull</A>
+</em>
 
 
-<H2>AUTHORS</H2>
+<h2>AUTHORS</h2>
 James Darrell McCauley, Purdue University<br>
 GRASS 5 update, improvements: <a href="mailto:aaime at libero.it">Andrea Aime</a>, Modena, Italy<br>
 GRASS 5.7 update: Radim Blazek
 
 <p>
-<i>Last changed: $Date$</i></p>
+<i>Last changed: $Date$</i>

Modified: grass/trunk/vector/v.what/v.what.html
===================================================================
--- grass/trunk/vector/v.what/v.what.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/vector/v.what/v.what.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -6,7 +6,7 @@
 <em>d.what.vect</em> module by removing all interactive code and
 modification of the output for easy parsing. Using the <em>-g</em> flag permits to
 generate script style output which is easily parsable.
-<P>
+<p>
 This module always reports standard acres, even when the location uses
 US Survey feet as the map unit.
 
@@ -21,7 +21,7 @@
 
 <h2>SEE ALSO</h2>
 
-<em><a HREF="d.what.vect.html">d.what.vect</a></em>
+<em><a href="d.what.vect.html">d.what.vect</a></em>
 
 
 <h2>AUTHOR</h2>

Modified: grass/trunk/vector/v.what.rast/v.what.rast.html
===================================================================
--- grass/trunk/vector/v.what.rast/v.what.rast.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/vector/v.what.rast/v.what.rast.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -1,4 +1,4 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
 <em>v.what.rast</em> reads raster value for each point in the vector and updates <b>col</b> 
 column in vector attribute table by this value. The column should be type
@@ -7,12 +7,12 @@
 If more points have the same category, attribute value is set to NULL.
 If raster values is NULL, attribute value is set to NULL.
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 
 <em>v.what.rast</em> operates on the attribute table. To modify the vector
 geometry instead, use <em>v.drape</em>.
 
-<H2>EXAMPLES</H2>
+<h2>EXAMPLES</h2>
 
 A) Reading values from raster map at position of vector points, writing these values
    into column of vector map:
@@ -21,7 +21,7 @@
 v.what.rast vect=pnts rast=elevation col=heights
 </pre></div>
 
-<P>
+<p>
 B) In case of a vector map without attached attribute table, first add
 a new attribute table. This table is then populated with values
 queried from the raster map:
@@ -43,18 +43,18 @@
 v.univar map=vectpoints col=myvalue type=point
 </pre></div>
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
-<EM>
+<em>
 <a href="v.db.addtable.html">v.db.addtable</a>,
-<a HREF="v.db.select.html">v.db.select</a>,
-<A HREF="v.drape.html">v.drape</a>,
-<A HREF="v.univar.html">v.univar</a>,
-<a HREF="v.rast.stats.html">v.rast.stats</a>,
+<a href="v.db.select.html">v.db.select</a>,
+<a href="v.drape.html">v.drape</a>,
+<a href="v.univar.html">v.univar</a>,
+<a href="v.rast.stats.html">v.rast.stats</a>,
 <a href="v.what.vect.html">v.what.vect</a>
-</EM>
+</em>
 
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
 Radim Blazek
 
 <p>

Modified: grass/trunk/vector/vectorintro.html
===================================================================
--- grass/trunk/vector/vectorintro.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/vector/vectorintro.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -94,7 +94,7 @@
 consist of one or more areas and are used internally to maintain correct
 topology for areas.
 
-<P>
+<p>
 The <a href="v.type.html">v.type</a> module can be used to convert
 between vector types if
 possible. The <a href="v.build.html">v.build</a> module is used to
@@ -109,7 +109,7 @@
 
 Adjacent polygons can be found by <a href="v.to.db.html">v.to.db</a>
 (see 'sides' option).
-<P>
+<p>
 Many operations including extraction, queries, overlay, and export will
 only act on features which have been assigned a category number. Typically
 a centroid will hold the attribute data for the area between it and its
@@ -184,12 +184,12 @@
 the table must be populated with one row per category (using <a href="v.to.db.html">v.to.db</a>).
 However, this can be performed in a single step using <a href="v.db.addtable.html">v.db.addtable</a>
 along with the definition of table column types. Column adding and dropping
-can be done with <a HREF="v.db.addcolumn.html">v.db.addcolumn</a> and
-<a HREF="v.db.dropcolumn.html">v.db.dropcolumn</a>. A table column can be renamed with
-<a HREF="v.db.renamecolumn.html">v.db.renamecolumn</a>. To drop a table from a map, use
-<a HREF="v.db.droptable.html">v.db.droptable</a>. Values in a table can be updated
-with <a HREF="v.db.update.html">v.db.update</a>. Tables can be joined with with
-<a HREF="v.db.join.html">v.db.join</a>.
+can be done with <a href="v.db.addcolumn.html">v.db.addcolumn</a> and
+<a href="v.db.dropcolumn.html">v.db.dropcolumn</a>. A table column can be renamed with
+<a href="v.db.renamecolumn.html">v.db.renamecolumn</a>. To drop a table from a map, use
+<a href="v.db.droptable.html">v.db.droptable</a>. Values in a table can be updated
+with <a href="v.db.update.html">v.db.update</a>. Tables can be joined with with
+<a href="v.db.join.html">v.db.join</a>.
 
 
 <h3>Editing vector attributes</h3>

Modified: grass/trunk/visualization/nviz/html/bugs_todo.html
===================================================================
--- grass/trunk/visualization/nviz/html/bugs_todo.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/visualization/nviz/html/bugs_todo.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -14,10 +14,10 @@
 <hr width="100%" align=center size=4 noshade>
 <p>
 <a href="nviz_toc.html">CONTENTS</a>
-</p>
 
+
 <h2>Bugs / Todo</h2>
-<p>Updated January 8, 2004</p>
+<p>Updated January 8, 2004
 
 <pre>
 1. Missing/not working which worked in SGI version

Modified: grass/trunk/visualization/nviz/html/index.html
===================================================================
--- grass/trunk/visualization/nviz/html/index.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/visualization/nviz/html/index.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -10,29 +10,29 @@
 
 <h2>nviz - A GRASS Visualization Program</h2>
 
-<p><img src="img/nv/inter1b.gif"><hr></p>
+<p><img src="img/nv/inter1b.gif"><hr>
 
 <p><strong>nviz</strong> is a GRASS module-in-progress which allows users
 to realistically render multiple surfaces in a 3D space, optionally
 using thematic coloring, draping GRASS vector maps over the surfaces, 
 and displaying GRASS site files either draped on the surfaces or 
-as 3D point locations.</p>
+as 3D point locations.
 
 <p>We are currently in the process of rewriting the tcl/tk interface to make
 it easier for programmers to add functionality, and porting the
-graphics from IRIS GL to OpenGL.</p>
+graphics from IRIS GL to OpenGL.
 
 
-<p><strong><a href="nviz_toc.html">Reference Manual</a></strong></p>
+<p><strong><a href="nviz_toc.html">Reference Manual</a></strong>
 
-<p><strong><a href="http://skagit.meas.ncsu.edu/~helena/gmslab/viz97/brown/">Features - Slides from Visualization 97 Conference</a></strong></p>
+<p><strong><a href="http://skagit.meas.ncsu.edu/~helena/gmslab/viz97/brown/">Features - Slides from Visualization 97 Conference</a></strong>
 
 <hr>
-<p>Maintained list of <a href="http://freegis.org/cgi-bin/viewcvs.cgi/~checkout~/grass/src.contrib/gmsl/nviz2.2/bugs_todo">BUGS in NVIZ</a> (we are working on these bugs).</p>
+<p>Maintained list of <a href="http://freegis.org/cgi-bin/viewcvs.cgi/~checkout~/grass/src.contrib/gmsl/nviz2.2/bugs_todo">BUGS in NVIZ</a> (we are working on these bugs).
 
 <hr>
 <p><strong>Animations</strong>. Since each surface often consists of hundreds of thousands of
-polygons, with render times of several seconds to a minute, we represent the surfaces with wire meshes as a rough approximation when a user is</p> 
+polygons, with render times of several seconds to a minute, we represent the surfaces with wire meshes as a rough approximation when a user is 
 
 <ul>
 <li><a href="http://skagit.meas.ncsu.edu/~helena/gmslab/viz/movies/position.mpg">
@@ -49,7 +49,7 @@
 <hr>
 
 <p><strong>Snapshots</strong>. These thumbnail images are links to full size screen dumps 
-showing some of the multiple surface features of nviz.</p>
+showing some of the multiple surface features of nviz.
 
 <a href="img/nv/cplane.gif"> <img src="img/nv/cplane_i.gif"></a>
 <a href="img/nv/inter1.gif"> <img src="img/nv/inter1_i.gif"></a>

Modified: grass/trunk/visualization/nviz/html/nviz_3dsetting.html
===================================================================
--- grass/trunk/visualization/nviz/html/nviz_3dsetting.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/visualization/nviz/html/nviz_3dsetting.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -12,9 +12,9 @@
 <hr width="100%" align=center size=4 noshade>
 <p>
 <a href="nviz_toc.html">CONTENTS</a>
-</p>
 
 
+
 <h2>3D Settings</h2>
 <p>You can save or load a particular 3D view. <strong>NVIZ</strong> 
 saves 3D view files in the <strong>GRASS</strong> <em>3d.view</em> 
@@ -22,25 +22,25 @@
 coordinates, lighting options, mesh resolution, and surface resolution. 
 These files use the same format as the <strong>GRASS 5</strong> program 
 <em><strong>d.3d</strong></em>.
-</p> 
+ 
 
-<BR><BR>
+<br><br>
 <DL><DD>
 <img src="nvimg/panel/file_menu.gif" alt="File Menu" width="302" height="323">
 </DD></DL>
-<BR><BR>
+<br><br>
 
 <h2>Load 3D Settings</h2>
 <p>
 Loads a previously saved 3D view. The <strong>Movement</strong> panel 
 updates to the new view.
-</p>
 
+
 <h2>Save 3D Settings</h2>
 <p>
 Saves the current 3D view to a user defined file.
-</p>
-<BR><BR>
 
+<br><br>
+
 </body>
 </html>

Modified: grass/trunk/visualization/nviz/html/nviz_credit.html
===================================================================
--- grass/trunk/visualization/nviz/html/nviz_credit.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/visualization/nviz/html/nviz_credit.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -13,24 +13,24 @@
 <hr width="100%" align=center size=4 noshade>
 <p>
 <a href="nviz_toc.html">CONTENTS</a>
-</p>
 
+
 <h2>Credits</h2>
 
 <p><strong></strong> written by Bill Brown, Terry Baker, Mark
 Astley, and David Gerdes, U.S. Army Corps of Engineers Research
 Laboratories, Champaign, Illinois and UI GMS Laboratory, Urbana, IL.
-</p>  
+  
 
 <p>
 Original documentation written by Terry Baker (spring 1995), and updated by Mark Astley, based on a document written by Bill Brown.
-</p>
 
+
 <p>
 Program and documentation (2004) updates by Bob Covill, Tekmap Consulting. 
-</p>
 
 
 
+
 </body>
 </html>

Modified: grass/trunk/visualization/nviz/html/nviz_desc.html
===================================================================
--- grass/trunk/visualization/nviz/html/nviz_desc.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/visualization/nviz/html/nviz_desc.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -13,13 +13,13 @@
 <hr width="100%" align=center size=4 noshade>
 <p>
 <a href="nviz_toc.html">CONTENTS</a>
-</p>
 
+
 <h2>Description</h2>
 <p><strong>NVIZ</strong> is a <strong>GRASS</strong> tool used for viewing 
 data surfaces in three dimensions. It evolved from the earlier 
 <strong>GRASS</strong> program <em>SG3d</em>.
-</p> 
+ 
 
 <p>Developers emphasized on the ease and speed of viewer
 positioning and provided flexibility for using a wide range of data.  A low 
@@ -29,7 +29,7 @@
 lighting.  Grid and polygon resolution controls allow the user to
 further refine drawing speed and detail as needed.  Continuous scaling
 of elevation provides the ability to
-use various data types for the vertical dimension.</p> 
+use various data types for the vertical dimension. 
 
 </body>
 </html>

Modified: grass/trunk/visualization/nviz/html/nviz_hints.html
===================================================================
--- grass/trunk/visualization/nviz/html/nviz_hints.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/visualization/nviz/html/nviz_hints.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -10,23 +10,23 @@
 
 <img src="grass_logo.png"><hr align=center size=6 noshade>
 
-<p><a href="nviz_toc.html">INDEX</a></p>
+<p><a href="nviz_toc.html">INDEX</a>
 
 <h2>NVIZ - Hints</h2>
 
 <h3>Animation</h3>
 
 <p><strong>NOTE:</strong> This page is still under construction. Future additions will include: Keyframe animation, off-screen rendering, how to assemble an animation, tips on NVIZ sliders, NVIZ environment variables, etc.
-</p>
 
-<p>This examples shows you how to create an animation.</p>  
 
+<p>This examples shows you how to create an animation.  
+
 <h4> Key frames </h4>
 
 <p>Using key frames is one of the easiest methods of animation it just
 takes some getting use to the <strong>Key Frame</strong> slider.  For
 practice, just try making a circular path while always looking at the
-center of the data:</p> 
+center of the data: 
 
 <ol>
  
@@ -58,9 +58,9 @@
 </ol>
 
 <p>You should now have enough key frames marked to define a path. Click <strong>show path</strong> and then <strong>run</strong>(NOT <strong>run and save images</strong>).  If nothing happens,
-clear all key frames and go back to step 1.</p>  
+clear all key frames and go back to step 1.  
 
-<p>Now let's complete the circular path:</p>
+<p>Now let's complete the circular path:
 
 <ol>
 <li>Repeat step 5.</li>
@@ -85,10 +85,10 @@
 frames to .rgb files, you would now toggle <strong>show path</strong>
 OFF and click <strong>run and save images</strong>, but why not
 wait until you get a little more creative - image files use a lot of
-disk space.</p>
+disk space.
 
 <h4>Changing key frames</h4>
-<p>With the above key frames loaded, try changing a key frame as follows:</p> 
+<p>With the above key frames loaded, try changing a key frame as follows: 
 
 <ol>
 
@@ -122,7 +122,7 @@
 1........2..3..4  
 </pre>
 
-<p>Run again, notice how movement speed was affected.</p></li>
+<p>Run again, notice how movement speed was affected.</li>
 
 <li>Reverse the direction of travel by swapping the positions of the
 two interior key frame markers.</li>
@@ -137,7 +137,7 @@
 fixed center of view.  Now run the path again.  Click on <strong>look
 cancel</strong> and run again. 
 <a href="http://www2.gis.uiuc.edu:2280/modviz/viz/movies/flight.mpg">This</a>
-is an example animation created in this way.</p>
+is an example animation created in this way.
 
 <h4>Image File Management</h4>
 
@@ -159,7 +159,7 @@
 zoom option (this will cause a loss of resolution though, since the
 zoom just replicates pixels).  If you are making an animation to be
 recorded onto video tape, it may be necessary to set the width and
-height to specific dimensions.</p>
+height to specific dimensions.
 
 <p>New SGI programs released with IRIX 4.0.5,
 <strong><em>moviemaker</em></strong> and <strong><em>movieplayer</em></strong>, are
@@ -168,7 +168,7 @@
 frame rates.  With <strong><em>movieplayer</em></strong>, much longer
 animations may be replayed than with <strong><em>movie</em></strong> since the
 frames are read directly from disk at run time rather than having to
-be loaded into memory.</p>
+be loaded into memory.
 
 </body>
 </html>

Modified: grass/trunk/visualization/nviz/html/nviz_image.html
===================================================================
--- grass/trunk/visualization/nviz/html/nviz_image.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/visualization/nviz/html/nviz_image.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -12,9 +12,9 @@
 <hr width="100%" align=center size=4 noshade>
 <p>
 <a href="nviz_toc.html">CONTENTS</a>
-</p>
 
 
+
 <h2>Image Dump</h2>
 
 <p>Image Dump saves the contents of the current <strong>NVIZ</strong> 
@@ -24,13 +24,13 @@
 of the saved image. With the exception of the <strong>Max. Resolution 
 PPM</strong>, the image has the same dimensions as the <strong>NVIZ</strong> 
 viewer.
-</p> 
+ 
 
-<BR><BR>
+<br><br>
 <DL><DD>
 <img src="nvimg/panel/image_dump.gif" alt="Image Dump" width="302" height="323">
 </DD></DL>
-<BR><BR>
+<br><br>
 
 <dl>
 <dt><strong>IRIS RGB Image</strong></dt>
@@ -40,10 +40,10 @@
 <dt><strong>PPM Image</strong></dt>
 <dd>Saves the scene to a PPM image file.
 You can convert a PPM image to a PNG image with the widely installed 
-NetPBM tools.<BR>
+NetPBM tools.<br>
 e.g.:
 <DL><dd><tt>pnmtopng image.ppm > image.png</tt></dd></DL>
-<BR>
+<br>
 </dd>
 
 <dt><strong>TIFF Image</strong></dt>

Modified: grass/trunk/visualization/nviz/html/nviz_panel_anim.html
===================================================================
--- grass/trunk/visualization/nviz/html/nviz_panel_anim.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/visualization/nviz/html/nviz_panel_anim.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -14,20 +14,20 @@
 <hr width="100%" align=center size=4 noshade>
 <p>
 <a href="nviz_toc.html">CONTENTS</a>
-</p>
 
+
 <h2>Animation Panel</h2>
 
 
 <p>Using the <strong>Animation</strong> panel, you can create a simple 
-fly-through animation.</p>
+fly-through animation.
 
 
-<BR><BR>
+<br><br>
 <DL><DD>
 <img src="nvimg/panel/anim.gif" alt="Animation Panel" width="308" height="298">
 </DD></DL>
-<BR><BR>
+<br><br>
 
 
 <h3>OPTIONS</h3>

Modified: grass/trunk/visualization/nviz/html/nviz_panel_color.html
===================================================================
--- grass/trunk/visualization/nviz/html/nviz_panel_color.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/visualization/nviz/html/nviz_panel_color.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -14,18 +14,18 @@
 <hr width="100%" align=center size=4 noshade>
 <p>
 <a href="nviz_toc.html">CONTENTS</a>
-</p>
 
+
 <h2>Color Panel</h2>
 
 <p>The <strong>Color</strong> panel sets the background color
-of the <strong>NVIZ</strong> viewer.</p> 
+of the <strong>NVIZ</strong> viewer. 
 
-<BR><BR>
+<br><br>
 <DL><DD>
 <img src="nvimg/panel/color.gif" alt="Color Panel" width="292" height="106">
 </DD></DL>
-<BR><BR>
+<br><br>
 
 
 <h3>OPTIONS</h3>

Modified: grass/trunk/visualization/nviz/html/nviz_panel_cplane.html
===================================================================
--- grass/trunk/visualization/nviz/html/nviz_panel_cplane.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/visualization/nviz/html/nviz_panel_cplane.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -14,19 +14,19 @@
 <hr width="100%" align=center size=4 noshade>
 <p>
 <a href="nviz_toc.html">CONTENTS</a>
-</p>
 
+
 <h2>Cutting Planes Panel</h2>
 
 <p>The <strong>Cutting Planes</strong> panel controls the cutting planes 
 (slices) between two or more surfaces. 
-</p>
 
-<BR><BR>
+
+<br><br>
 <DL><DD>
 <img src="nvimg/panel/cut.gif" alt="Cutting Plane Panel" width="292" height="186">
 </DD></DL>
-<BR><BR>
+<br><br>
 
 
 

Modified: grass/trunk/visualization/nviz/html/nviz_panel_dsf.html
===================================================================
--- grass/trunk/visualization/nviz/html/nviz_panel_dsf.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/visualization/nviz/html/nviz_panel_dsf.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -13,20 +13,20 @@
 <hr width="100%" align=center size=4 noshade>
 <p>
 <a href="nviz_toc.html">CONTENTS</a>
-</p>
 
+
 <h2>Mkdspf Panel</h2>
 
 <p>
 The <strong>Mkdspf</strong> panel lets you create isosurfaces display files 
 (dspf) from <strong>GRASS</strong> volume data (grid3 files).
-</p> 
+ 
 
-<BR><BR>
+<br><br>
 <DL><DD>
 <img src="nvimg/panel/mkdspf.gif" alt="Mkdpsf Panel" width="291" height="359">
 </DD></DL>
-<BR><BR>
+<br><br>
 
 <h3>OPTIONS</h3>
 

Modified: grass/trunk/visualization/nviz/html/nviz_panel_dsf1.html
===================================================================
--- grass/trunk/visualization/nviz/html/nviz_panel_dsf1.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/visualization/nviz/html/nviz_panel_dsf1.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -16,20 +16,20 @@
 <a href="nviz_toc.html">CONTENTS</a>
 <br>
 <a href="nviz_panel_dsf.html">BACK</a>
-</p>
 
+
 <h2>Mkdspf Panel - Individual Thresholds</h2>
 
 <p>
 On the <strong>Mkdspf Panel</strong>, you use the <strong>Individual</strong> 
 thresholds option to add individual or custom isosurface thresholds.
-</p> 
+ 
 
-<BR><BR>
+<br><br>
 <DL><DD>
 <img src="nvimg/panel/mkdspf.gif" alt="Mkdspf Individual Menu" width="291" height="359">
 </DD></DL>
-<BR><BR>
+<br><br>
 
 <h3>OPTIONS</h3>
 

Modified: grass/trunk/visualization/nviz/html/nviz_panel_dsf2.html
===================================================================
--- grass/trunk/visualization/nviz/html/nviz_panel_dsf2.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/visualization/nviz/html/nviz_panel_dsf2.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -16,22 +16,22 @@
 <a href="nviz_toc.html">CONTENTS</a>
 <br>
 <a href="nviz_panel_dsf.html">BACK</a>
-</p>
 
+
 <h2>Mkdspf Panel - Complete Threshold</h2>
 
 <p>
 On the <strong>Mkdspf Panel</strong>, you use the <strong>Complete</strong> 
 threshold option to create an evenly spaced set of display isosurfaces 
 covering the complete range of the <strong>Input File</strong>.
-</p> 
+ 
 
 
-<BR><BR>
+<br><br>
 <DL><DD>
 <img src="nvimg/panel/mkdspf_complete.gif" alt="Mkdspf Complete Menu" width="291" height="214">
 </DD></DL>
-<BR><BR>
+<br><br>
 
 
 <h3>OPTIONS</h3>

Modified: grass/trunk/visualization/nviz/html/nviz_panel_dsf3.html
===================================================================
--- grass/trunk/visualization/nviz/html/nviz_panel_dsf3.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/visualization/nviz/html/nviz_panel_dsf3.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -16,22 +16,22 @@
 <a href="nviz_toc.html">CONTENTS</a>
 <br>
 <a href="nviz_panel_dsf.html">BACK</a>
-</p>
 
+
 <h2>Mkdspf Panel - Range Threshold</h2>
 
 <p>
 On the <strong>Mkdspf Panel</strong>, you use the <strong>Range</strong> 
 threshold option to create an evenly spaced set of display isosurfaces 
 covering a user defined range of the <strong>Input File</strong>.
-</p> 
+ 
 
 
-<BR><BR>
+<br><br>
 <DL><DD>
 <img src="nvimg/panel/mkdspf_range.gif" alt="Mkdspf Range Menu" width="294" height="268" >
 </DD></DL>
-<BR><BR>
+<br><br>
 
 
 <h3>OPTIONS</h3>

Modified: grass/trunk/visualization/nviz/html/nviz_panel_kanim.html
===================================================================
--- grass/trunk/visualization/nviz/html/nviz_panel_kanim.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/visualization/nviz/html/nviz_panel_kanim.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -12,8 +12,8 @@
 <hr width="100%" align=center size=4 noshade>
 <p>
 <a href="nviz_toc.html">CONTENTS</a>
-</p>
 
+
 <h2>Keyframe Animation Panel</h2>
 
 <p>The <strong>Keyframe Animation</strong> panel lets you create complex 
@@ -26,11 +26,11 @@
 may be used to automatically create Keyframe animation templates which can
 be loaded by this panel.
 
-<BR><BR>
+<br><br>
 <DL><DD>
 <img src="nvimg/panel/keyanim.gif" alt="Keyframe Animation Panel" width="355" height="436">
 </DD></DL>
-<BR><BR>
+<br><br>
 
 
 <h3>OPTIONS</h3>
@@ -235,7 +235,7 @@
 <p>
 Change back to the keyframe animation panel (<em>Panel->Keyframe</em>
 animation in the menu).
-<P>
+<p>
 Set first view, click [Add].<br>
 Set [New key time] to 0:02:00, change view, click [Add].<br>
 Set [New key time] to 0:04:00, change view, click [Add].<br>
@@ -266,20 +266,20 @@
 </pre></div>
 
 
-<P>
+<p>
 Alternatively, NVIZ can encode to a MPEG-1 movie automatically.
-(simpler, but lower quality)<BR>
+(simpler, but lower quality)<br>
 <i>Assuming NVIZ was built with FFMPEG support for live MPEG rendering:</i>
-<BR><BR>
+<br><br>
 Next click "Animation: [Run and Save]",
 type in a basename.mpg,
 click the "<>&nbsp;MPEG-1&nbsp;button",
 click the "<>&nbsp;Full&nbsp;Rendering" button,
 click [Ok].
 <p>
-whiz-bang-whirl.<BR>
+whiz-bang-whirl.<br>
 Done.
-</P>
 
+
 </body>
 </html>

Modified: grass/trunk/visualization/nviz/html/nviz_panel_labels.html
===================================================================
--- grass/trunk/visualization/nviz/html/nviz_panel_labels.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/visualization/nviz/html/nviz_panel_labels.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -14,20 +14,20 @@
 <hr width="100%" align=center size=4 noshade>
 <p>
 <a href="nviz_toc.html">CONTENTS</a>
-</p>
 
+
 <h2>Label Panel</h2>
 
 
 <p>The <strong>Label</strong> panel lets you place labels and/or legends 
-in the <strong>NVIZ</strong> viewer.</p>
+in the <strong>NVIZ</strong> viewer.
 
 
-<BR><BR>
+<br><br>
 <DL><DD>
 <img src="nvimg/panel/labels.gif" alt="Label Panel" width="286" height="388">
 </DD></DL>
-<BR><BR>
+<br><br>
 
 
 <h3>OPTIONS</h3>
@@ -35,8 +35,8 @@
 <p>
 On the <strong>Label</strong> panel, the first (top) menu has options for 
 setting the font attributes for both the labels and the legend.
-</p>
 
+
 <dl>
 
 <dt> <strong>Font Size</strong></dt>
@@ -83,8 +83,8 @@
 <p>
 Use the next menu in the <strong>Label</strong> panel to place labels in 
 the <strong>NVIZ</strong> viewer.
-</p>
 
+
 <dl>
 <dt> <strong>Place Label</strong></dt>
 <dd>Places the text from <strong>Label Text</strong> in the 
@@ -109,8 +109,8 @@
 <p>
 Use the next menu in the <strong>Label</strong> panel to place a surface 
 (raster) legend in the <strong>NVIZ</strong> viewer.
-</p>
 
+
 <dl>
 <dt> <strong>Place Legend</strong></dt>
 <dd>Places the legend for the current surface (see 
@@ -163,8 +163,8 @@
 <p>
 Use the next menu in the <strong>Label</strong> panel to draw sites file 
 labels in the <strong>NVIZ</strong> viewer. This menu is not yet implemented.
-</p>
 
+
 <dl>
 <dt> <strong>Label Sites</strong></dt>
 <dd>This option is not yet implemented.

Modified: grass/trunk/visualization/nviz/html/nviz_panel_lights.html
===================================================================
--- grass/trunk/visualization/nviz/html/nviz_panel_lights.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/visualization/nviz/html/nviz_panel_lights.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -14,8 +14,8 @@
 <hr width="100%" align=center size=4 noshade>
 <p>
 <a href="nviz_toc.html">CONTENTS</a>
-</p>
 
+
 <h2>Lighting Panel</h2>
 
 <p>The <strong>Lighting</strong> panel has options to control the position, 
@@ -25,13 +25,13 @@
 The main light controls the shading, which you adjust using the 
 <strong>Lighting</strong> panel. As you adjust the lighting, a lighting 
 model (sphere) appears on the surface and continually shows the effects 
-of the lighting changes.</p>  
+of the lighting changes.  
 
-<BR><BR>
+<br><br>
 <DL><DD>
 <img src="nvimg/panel/light.gif" alt="Light Panel" width="292" height="276">
 </DD></DL>
-<BR><BR>
+<br><br>
 
 <h3>OPTIONS</h3>
 

Modified: grass/trunk/visualization/nviz/html/nviz_panel_move.html
===================================================================
--- grass/trunk/visualization/nviz/html/nviz_panel_move.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/visualization/nviz/html/nviz_panel_move.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -13,8 +13,8 @@
 <hr width="100%" align=center size=4 noshade>
 <p>
 <a href="nviz_toc.html">CONTENTS</a>
-</p>
 
+
 <h2>Movement Panel</h2>
 
 <p>The <strong>Movement</strong> panel always appears at the top of the 
@@ -22,13 +22,13 @@
 panel to set the position, direction, and perspective of the view. As you 
 change movement options, a low resolution or wire grid of the surface 
 redraws (<strong><em>fast display mode</em></strong>) showing the results 
-of your changes.</p>
+of your changes.
 
-<BR><BR>
+<br><br>
 <DL><DD>
 <img src="nvimg/panel/main.gif" alt = "Movement Panel" width="302" height="323">
 </DD></DL>
-<BR><BR>
+<br><br>
 
 <h3>OPTIONS</h3>
 

Modified: grass/trunk/visualization/nviz/html/nviz_panel_pos.html
===================================================================
--- grass/trunk/visualization/nviz/html/nviz_panel_pos.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/visualization/nviz/html/nviz_panel_pos.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -14,8 +14,8 @@
 <hr width="100%" align=center size=4 noshade>
 <p>
 <a href="nviz_toc.html">CONTENTS</a>
-</p>
 
+
 <h2>Position Panel</h2>
 
 
@@ -23,13 +23,13 @@
 <strong>From</strong> (eye) position and the <strong>To</strong> (surface) 
 position. You can manually enter coordinates or calculate coordinates 
 based upon a range, bearing, and elevation.
-</p>
 
-<BR><BR>
+
+<br><br>
 <DL><DD>
 <img src="nvimg/panel/position.gif" alt="Position Panel" width="308" height="194">
 </DD></DL>
-<BR><BR>
+<br><br>
 
 
 <h3>OPTIONS</h3>

Modified: grass/trunk/visualization/nviz/html/nviz_panel_scale.html
===================================================================
--- grass/trunk/visualization/nviz/html/nviz_panel_scale.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/visualization/nviz/html/nviz_panel_scale.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -14,20 +14,20 @@
 <hr width="100%" align=center size=4 noshade>
 <p>
 <a href="nviz_toc.html">CONTENTS</a>
-</p>
 
+
 <h2>Decorations and Scale Panel</h2>
 
 
 <p>The <strong>Decorations and Scale</strong> panel lets you place scale objects and/or a 
-north arrow in the <strong>NVIZ</strong> viewer.</p>
+north arrow in the <strong>NVIZ</strong> viewer.
 
 
-<BR><BR>
+<br><br>
 <DL><DD>
 <img src="nvimg/panel/scale.gif" alt="Decorations and Scale Panel" width="293" height="253">
 </DD></DL>
-<BR><BR>
+<br><br>
 
 
 <h3>OPTIONS</h3>
@@ -42,7 +42,7 @@
 <p>
 Use one of the next four options to set the type of <strong>Scale 
 object</strong>.
-</p>
+
 <dl>
 <dt> <strong></strong></dt>
 <dd>
@@ -76,10 +76,10 @@
 <strong>NOTE:</strong> The North arrow is automatically scaled according to 
 scene size and zoom level. There are still some bugs in the scaling which 
 can result in over or under sized arrows.
-</p>
 
 
-<BR><BR><BR>
+
+<br><br><br>
 <dl>
 <dt> <strong>Draw Fringe</strong></dt>
 <dd>Draws a fringe shadow or "flower box" around base of elevation map. <!-- HB: ???? -->

Modified: grass/trunk/visualization/nviz/html/nviz_panel_sdiff.html
===================================================================
--- grass/trunk/visualization/nviz/html/nviz_panel_sdiff.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/visualization/nviz/html/nviz_panel_sdiff.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -14,21 +14,21 @@
 <hr width="100%" align=center size=4 noshade>
 <p>
 <a href="nviz_toc.html">CONTENTS</a>
-</p>
 
+
 <h2>Scaled Difference Panel</h2>
 
 
 <p>The <strong>Scaled Difference</strong> panel lets you exaggerate the 
 distance between multiple surfaces. This exaggeration does not effect 
-the surface properties and intersection points.</p>
+the surface properties and intersection points.
 
 
-<BR><BR>
+<br><br>
 <DL><DD>
 <img src="nvimg/panel/scale_diff.gif" alt="Scaled Difference Panel" width="288" height="126">
 </DD></DL>
-<BR><BR>
+<br><br>
 
 
 

Modified: grass/trunk/visualization/nviz/html/nviz_panel_sites.html
===================================================================
--- grass/trunk/visualization/nviz/html/nviz_panel_sites.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/visualization/nviz/html/nviz_panel_sites.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -14,18 +14,18 @@
 <hr width="100%" align=center size=4 noshade>
 <p>
 <a href="nviz_toc.html">CONTENTS</a>
-</p>
 
+
 <h2>Vector Points Panel</h2>
 
 
 <p>The <strong>Vector Points</strong> panel controls how sites (vector points)
-are displayed.</p>
-<BR><BR>
+are displayed.
+<br><br>
 <dl><dd>
 <img src="nvimg/panel/sites.gif" alt="Vector Points Panel" width="294" height="202">
 </dd></dl>
-<BR><BR>
+<br><br>
 
 <h3>OPTIONS</h3>
 
@@ -47,7 +47,7 @@
 <br><br></dd>
 
 <dt> <strong>Line Width</strong></dt>
-<dd>Sets the width (in pixels) of the line used to draw the site markers.<BR>
+<dd>Sets the width (in pixels) of the line used to draw the site markers.<br>
 (Only applies to wire-frame markers)
 <br><br></dd>
 </dl>

Modified: grass/trunk/visualization/nviz/html/nviz_panel_surf.html
===================================================================
--- grass/trunk/visualization/nviz/html/nviz_panel_surf.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/visualization/nviz/html/nviz_panel_surf.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -14,20 +14,20 @@
 <hr width="100%" align=center size=4 noshade>
 <p>
 <a href="nviz_toc.html">CONTENTS</a>
-</p>
 
+
 <h2>Surface Panel</h2>
 
 <p>The <strong>Surface</strong> panel controls how loaded surfaces are 
 drawn. The top half of the panel has drawing style options. The bottom 
 half has options to add, delete, select, and change attributes of the 
-current surface.</p> 
+current surface. 
 
-<BR><BR>
+<br><br>
 <DL><DD>
 <img src="nvimg/panel/surf.gif" alt="Surface Panel" width="292" height="238">
 </DD></DL>
-<BR><BR>
+<br><br>
 
 
 

Modified: grass/trunk/visualization/nviz/html/nviz_panel_vect.html
===================================================================
--- grass/trunk/visualization/nviz/html/nviz_panel_vect.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/visualization/nviz/html/nviz_panel_vect.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -14,17 +14,17 @@
 <hr width="100%" align=center size=4 noshade>
 <p>
 <a href="nviz_toc.html">CONTENTS</a>
-</p>
 
+
 <h2>Vector Lines Panel</h2>
 
 <p>The <strong>Vector Lines</strong> panel controls how vectors are displayed.
-</p> 
-<BR><BR>
+ 
+<br><br>
 <dl><dd>
 <img src="nvimg/panel/vect.gif" alt="Vector Panel" width="291" height="193">
 </dd></dl>
-<BR><BR>
+<br><br>
 
 
 <h3>OPTIONS</h3>
@@ -57,8 +57,8 @@
 surface(s) at a specified height.
 Use the <strong>Vect. Z</strong> scale to set the flat elevation or the drape 
 height above the surface(s).
-</p>
 
+
 <dl>
 <dt> <strong>Display Flat</strong></dt>
 <dd>Draws the current vector on a flat plane at the elevation set by 

Modified: grass/trunk/visualization/nviz/html/nviz_panel_vol.html
===================================================================
--- grass/trunk/visualization/nviz/html/nviz_panel_vol.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/visualization/nviz/html/nviz_panel_vol.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -14,20 +14,20 @@
 <hr width="100%" align=center size=4 noshade>
 <p>
 <a href="nviz_toc.html">CONTENTS</a>
-</p>
 
+
 <h2>Volume Panel</h2>
 
 <p>The <strong>Volume</strong> (voxels) panel controls how loaded volumes are 
 drawn. The bottom half of the panel has drawing style options. The top 
 half has options to add, delete, select, and change attributes of the 
-current volume.</p> 
+current volume. 
 
-<BR><BR>
+<br><br>
 <DL><DD>
 <img src="nvimg/panel/volumes.gif" alt="Volume Panel" width="360" height="388">
 </DD></DL>
-<BR><BR>
+<br><br>
 
 
 

Modified: grass/trunk/visualization/nviz/html/nviz_panel_what.html
===================================================================
--- grass/trunk/visualization/nviz/html/nviz_panel_what.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/visualization/nviz/html/nviz_panel_what.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -14,8 +14,8 @@
 <hr width="100%" align=center size=4 noshade>
 <p>
 <a href="nviz_toc.html">CONTENTS</a>
-</p>
 
+
 <h2>What's Here Panel</h2>
 
 <p>The <strong>What's Here</strong> panel lets you interactively query 
@@ -23,13 +23,13 @@
 Query results appear in the <strong>What's Here</strong> text box.
 You can also pipe results directly to a text file.
 Query points appear in the <strong>NVIZ</strong> viewer as icons.
-</p>
 
-<BR><BR>
+
+<br><br>
 <DL><DD>
 <img src="nvimg/panel/whats.gif" alt="What's Here Panel" width="292" height="284">
 </DD></DL>
-<BR><BR>
+<br><br>
 
 <h3>OPTIONS</h3>
 

Modified: grass/trunk/visualization/nviz/html/nviz_quit.html
===================================================================
--- grass/trunk/visualization/nviz/html/nviz_quit.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/visualization/nviz/html/nviz_quit.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -13,16 +13,16 @@
 <hr width="100%" align=center size=4 noshade>
 <p>
 <a href="nviz_toc.html">CONTENTS</a>
-</p>
 
 
+
 <h2>Reset</h2>
 
-<p>Resets <strong>NVIZ</strong> to default values.</p> 
+<p>Resets <strong>NVIZ</strong> to default values. 
 
 <h2>Quit</h2>
 
-<p>Exits the program and closes all <strong>NVIZ</strong> windows.</p> 
+<p>Exits the program and closes all <strong>NVIZ</strong> windows. 
 
 </body>
 </html>

Modified: grass/trunk/visualization/nviz/html/nviz_script.html
===================================================================
--- grass/trunk/visualization/nviz/html/nviz_script.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/visualization/nviz/html/nviz_script.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -14,19 +14,19 @@
 <hr width="100%" align=center size=4 noshade>
 <p>
 <a href="nviz_toc.html">CONTENTS</a>
-</p>
 
+
 <h2>Scripting</h2>
 
 
 <h3>NVIZ - Introduction</h3>
-<P><strong>NOTE:</strong> The scripting tools are still under developemnt. 
+<p><strong>NOTE:</strong> The scripting tools are still under developemnt. 
 A number of the functions in these menus are not yet fully functional.
-</p>
 
+
 <p>The scripting environment lets you develop a one-time script file that 
 can handle 
-complex changes to the <strong>NVIZ</strong> environment.</p>
+complex changes to the <strong>NVIZ</strong> environment.
 
 <p>Scripting is controlled by the commands provided in the scripting
 pulldown menu.  A script
@@ -34,10 +34,10 @@
 in the menu.  Scripting can become more powerful,
 however, by adding loops around a sequence of script events, or by
 using higher-level tools.  
-</p>
 
 
 
 
+
 </body>
 </html>

Modified: grass/trunk/visualization/nviz/html/nviz_startup.html
===================================================================
--- grass/trunk/visualization/nviz/html/nviz_startup.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/visualization/nviz/html/nviz_startup.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -14,14 +14,14 @@
 <hr width="100%" align=center size=4 noshade>
 <p>
 <a href="nviz_toc.html">CONTENTS</a>
-</p>
 
+
 <h2>Startup</h2>
 
-<p>The syntax for starting <strong>NVIZ</strong> is:</p> 
+<p>The syntax for starting <strong>NVIZ</strong> is: 
 
 <p><strong><em>nviz [-q]
-[elevation=name[,name,...]] [vector=name[,name,...]] [sites=name[,name,...]] [state=name] [script=name]</em></strong></p>
+[elevation=name[,name,...]] [vector=name[,name,...]] [sites=name[,name,...]] [state=name] [script=name]</em></strong>
 
 <h3>Flag:</h3> 
 
@@ -55,19 +55,19 @@
 </dl>
 
 <p>If you type <strong><em>nviz</em></strong> on the command line without
-any arguments, the program prompts you for the arguments.</p>
+any arguments, the program prompts you for the arguments.
 
 <p>After startup, you have two windows:
 <ul>
 <li>The <strong>NVIZ</strong> viewer (the main window that displays the scene)</li>
 <li>The <strong>Controls</strong> window (where you can change and set display options)</li>
 </ul>
-</p>
 
+
 <p>
 By default, the <strong>Controls</strong> window always appears with the <a href="nviz_panel_move.html"><strong>Movement</strong> panel</a> open.
 All other panels open below the <strong>Movement</strong> panel.
-</p>
 
+
 </body>
 </html>

Modified: grass/trunk/visualization/nviz/html/nviz_state.html
===================================================================
--- grass/trunk/visualization/nviz/html/nviz_state.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/visualization/nviz/html/nviz_state.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -13,9 +13,9 @@
 <hr width="100%" align=center size=4 noshade>
 <p>
 <a href="nviz_toc.html">CONTENTS</a>
-</p>
 
 
+
 <h2>State</h2>
 
 <p>For each session of <strong>NVIZ</strong>, you might want the same set of
@@ -23,13 +23,13 @@
 For consistency between sessions, <strong>NVIZ</strong> provides tools for 
 saving and loading the current &#034;state&#034; of the system.  
 To access these tools, on the <strong>File</strong> menu, use 
-<strong>Load State</strong> and <strong>Save State</strong>.</p> 
+<strong>Load State</strong> and <strong>Save State</strong>. 
 
-<BR><BR>
+<br><br>
 <DL><DD>
 <img src="nvimg/panel/file_menu.gif" alt="File Menu" width="302" height="323">
 </DD></DL>
-<BR><BR>
+<br><br>
 
 <h2>Load State</h2>
 <p>
@@ -37,15 +37,15 @@
 <strong>Controls</strong> window settings change to the newly loaded state.
 You can also load an <strong>NVIZ</strong> state file at startup using the 
 &#034;state=&#034; <a href="nviz_startup.html">command line option</a>.
-</p>
 
 
+
 <h2>Save State</h2>
 <p>
 Records the current status of <strong>NVIZ</strong>, including all
 current maps, color settings, and camera viewpoint into a user
 defined file.
-</p>
 
+
 </body>
 </html>

Modified: grass/trunk/visualization/nviz/html/nviz_toc.html
===================================================================
--- grass/trunk/visualization/nviz/html/nviz_toc.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/visualization/nviz/html/nviz_toc.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -34,7 +34,7 @@
 <li><a href="nviz_quit.html">Reset</a></li>
 <li><a href="nviz_quit.html">Quit</a></li>
 </ul></li>
-<BR>
+<br>
 
 <li>Panel
 <ul>
@@ -55,7 +55,7 @@
 <li> <a href="nviz_panel_scale.html">Decorations</a></li>
 <li> <a href="nviz_panel_pos.html">Position</a></li>
 </ul></li>
-<BR>
+<br>
 
 <li>Scripting
 <ul>
@@ -68,7 +68,7 @@
 <li><a href="nviz_script.html">Script Tools</a></li>
 
 </ul></li>
-<BR>
+<br>
 
 <!-- <li>Help<br></li> -->
 

Modified: grass/trunk/visualization/nviz/nviz.html
===================================================================
--- grass/trunk/visualization/nviz/nviz.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/visualization/nviz/nviz.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -65,6 +65,6 @@
 Please refer to the detailed manual inside NVIZ (HELP menu) or see the
 <a href="nviz/index.html">NVIZ Tutorial</a>.
 <HR>
-<P><a href="index.html">Main index</a> - <a href="full_index.html">Full index</a></P>
+<p><a href="index.html">Main index</a> - <a href="full_index.html">Full index</a>
 </body>
 </html>

Modified: grass/trunk/visualization/xganim/xganim.html
===================================================================
--- grass/trunk/visualization/xganim/xganim.html	2011-09-29 11:14:28 UTC (rev 48556)
+++ grass/trunk/visualization/xganim/xganim.html	2011-09-29 19:18:47 UTC (rev 48557)
@@ -1,6 +1,6 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
-<EM>xganim</EM> is a tool for animating a series of GRASS raster
+<em>xganim</em> is a tool for animating a series of GRASS raster
 files. At startup, a graphics window is opened containing VCR-like
 button controls for: rewind, reverse play, step back, stop, step
 forward, forward play, loop, swing, slower, faster, show filenames,
@@ -8,14 +8,14 @@
 left of the controls. Each raster map is read into memory, then the
 animation is played once beginning to end. The user may then replay
 the series or play continuous animation by using the buttons.
-<P>
+<p>
 The user may define up to four "views", or sub-windows, to animate
 simultaneously. e.g., View 1 could be rainfall, View 2 flooded areas,
 View 3 damage to bridges or levees, View 4 other economic damage, all
 animated as a time series. There is an arbitrary limit of 400 files
 per view (400 animation frames), but the practical limit may be less
 depending on the window size and amount of available RAM.
-<P>
+<p>
 The environment variable XGANIM_SIZE is checked for a value to use as
 the dimension, in pixels, of the longest dimension of the animation
 window. If XGANIM_SIZE is not set, the animation size defaults to the
@@ -24,23 +24,23 @@
 the current GRASS region is maintained, independent of window size. 
 Resizing the window after the program is running will have no effect
 on the animation size.
-<P>
+<p>
 UNIX - style wild cards may be used with the command line version in
 place of a raster map name, but it must be quoted.
-<P>
+<p>
 If the number of files differs for each view, the view with the fewest
 files will determine the number of frames in the animation.
 
-<H2>EXAMPLE</H2>
+<h2>EXAMPLE</h2>
 
 <div class="code"><pre>
 export XGANIM_SIZE=800
 xganim view1="rain[1-9]","rain1[0-2]" view2="temp*"
 </pre></div>
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 
-For wildcard matching, <EM>xganim</EM> understands whatever the shell 
+For wildcard matching, <em>xganim</em> understands whatever the shell 
 understands (as it invokes "ls" via the shell to expand wildcards). 
 E.g., a user can use "rast[0-9][0-9]" to match "rast00" through "rast99" inclusive.
 If the maps if interest have varying numbers of digits, multiple patterns
@@ -54,21 +54,21 @@
 to match rast0 through rast99 inclusive.
 
 
-<H2>BUGS</H2>
+<h2>BUGS</h2>
 On some displays that need to use private colormaps, the interface
 buttons may become difficult to see.
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
 <em><a href="d.slide.show.html">d.slide.show</a></em>,
 <em><a href="gm_animate.html">gis.m: ANIMATE TOOL</a></em>
 
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
 
 Bill Brown, U.S. Army Construction Engineering Research Laboratories
 
 <!-- left in for historical purposes :)
-<H2>NOTICE</H2>
+<h2>NOTICE</h2>
 This program is part of the contrib section of the GRASS distribution. 
 As such, it is externally contributed code that has not been examined
 or tested by the Office of GRASS Integration.

