* src/preproc/html/pre-html.cpp (usage): Don't describe options but

mention that it should never be called stand-alone.

* tmac/groff_www.man, doc/groff.texinfo, man/groff_font.man,
man/groff_tmac.man, man/groff_out.man, README, README.MinGW,
src/roff/groff/groff.man: Mention -Txhtml.

* man/groff_font.man, man/groff_tmac.man, man/roff.man: Revised.

1 files changed, 25 insertions, 24 deletions

diff --git a/README.MinGW b/README.MinGW
index 95ac8801..8905b823 100644
--- a/README.MinGW
+++ b/README.MinGW
@@ -1,4 +1,4 @@
-    Copyright (C) 2003, 2004, 2007
+    Copyright (C) 2003, 2004, 2007, 2008
       Free Software Foundation, Inc.
 
     Copying and distribution of this file, with or without modification,
@@ -31,9 +31,9 @@
   installer can then automatically set up the proper environment for running
   MinGW.
 
-  Additionally, if you wish to compile groff with support for its HTML output
-  capability, some additional tools are required as decribed in the section
-  PREREQUISITES FOR HTML OUTPUT later in this file.
+  Additionally, if you wish to compile groff with support for its HTML (and
+  XHTML) output capability, some additional tools are required as decribed in
+  the section PREREQUISITES FOR HTML OUTPUT later in this file.
 
 
   BUILDING GROFF WITH MINGW
@@ -66,11 +66,11 @@
      the groff source tree.  You should now change directory, to make this
      ./groff-<version> your working directory.
 
-  3. If you are intending to build groff with support for HTML output, then
-     you must now ensure that the prerequisites described in the later section
-     PREREQUISITES FOR HTML OUTPUT are satisfied, before proceeding to build
-     groff; in particular, please ensure that all required support programs
-     are installed in the current PATH.
+  3. If you are intending to build groff with support for HTML (and XHTML)
+     output, then you must now ensure that the prerequisites described in the
+     later section PREREQUISITES FOR HTML OUTPUT are satisfied, before
+     proceeding to build groff; in particular, please ensure that all required
+     support programs are installed in the current PATH.
 
   4. You are now ready to configure, build, and install groff.  This is
      accomplished using the conventional procedure, as described in the file
@@ -174,18 +174,19 @@
   PREREQUISITES FOR HTML OUTPUT
   -----------------------------
 
-  If you intend to use groff for production of HTML output, then there are a
-  few dependencies which must be satisfied.  Ideally, these should be resolved
-  before attempting to configure and build groff, since the configuration
-  script does check them.
+  If you intend to use groff for production of HTML or XHTML output, then
+  there are a few dependencies which must be satisfied.  Ideally, these should
+  be resolved before attempting to configure and build groff, since the
+  configuration script does check them.
 
-  In order to produce HTML output, you first require a working implementation
-  of Ghostscript; either the AFPL Ghostscript or the GNU Ghostscript
-  implementation for MS-Windows should be suitable, depending on your
-  licensing preference.  It is highly recommended to use version 8.11 or
-  higher due to bugs in older versions.  These may be obtained, in the form of
-  self-installing binary packages, by following the download links for the
-  chosen licensing option, from http://sourceforge.net/projects/ghostscript.
+  In order to produce HTML or XHTML output, you first require a working
+  implementation of Ghostscript; either the AFPL Ghostscript or the GNU
+  Ghostscript implementation for MS-Windows should be suitable, depending on
+  your licensing preference.  It is highly recommended to use version 8.11
+  or higher due to bugs in older versions.  These may be obtained, in the
+  form of self-installing binary packages, by following the download links
+  for the chosen licensing option, from
+  http://sourceforge.net/projects/ghostscript.
 
   Please note that these packages install the Ghostscript interpreter required
   by groff in the ./bin subdirectory of the Ghostscript installation
@@ -277,10 +278,10 @@
     network share, where the user does not have write permission in the root
     directory of the share, causes groff to fail with a `permission denied'
     exception, if the TMP environment variable is not appropriately defined;
-    it may also be necessary to define the TEMP environment variable, to avoid
-    a similar failure mode, when using the -Thtml output mode of groff.  This
-    problem is more fully discussed in the preceding section, GROFF RUNTIME
-    ENVIRONMENT.
+    it may also be necessary to define the TEMP environment variable, to
+    avoid a similar failure mode, when using the -Thtml or -Txhtml output
+    mode of groff.  This problem is more fully discussed in the preceding
+    section, GROFF RUNTIME ENVIRONMENT.
 
   o When running groff (or nroff) to process standard input, where the
     standard input stream is obtained directly from the RXVT console provided