Improve man page formattingHEADmaster

More closely follow common style as described on
https://man7.org/linux/man-pages/man7/man-pages.7.html

Signed-off-by: Alan Coopersmith <alan.coopersmith@oracle.com>
Part-of: <https://gitlab.freedesktop.org/xorg/util/imake/-/merge_requests/14>

9 files changed, 196 insertions, 182 deletions

diff --git a/ccmakedep.1.in b/ccmakedep.1.in
index 0d1a977..5b838bb 100644
--- a/ccmakedep.1.in
+++ b/ccmakedep.1.in
@@ -1,10 +1,10 @@
-.TH ccmakedep 1 "@PACKAGE_STRING@"
+.TH CCMAKEDEP 1 2002-10-12 "@PACKAGE_STRING@"
 .SH NAME
 ccmakedep \- create dependencies in makefiles using a C compiler
 .SH SYNOPSIS
 .B ccmakedep
 [
-.BI cpp-flags
+.I cpp-flags
 ] [
 .BI \-w width
 ] [
@@ -43,7 +43,7 @@ By default,
 places its output in the file named
 .I makefile
 if it exists, otherwise
-.I Makefile.
+.IR Makefile .
 An alternate makefile may be specified with the
 .B \-f
 option.
@@ -105,7 +105,7 @@ This option permits you to specify a different string for
 to look for in the makefile.
 The default is \(lq# DO NOT DELETE\(rq.
 .TP
-.BI \-v
+.B \-v
 Be verbose: display the C compiler command before running it.
 .TP
 .BI \-\^\- " options " \-\^\-
diff --git a/cleanlinks.1.in b/cleanlinks.1.in
index 69ac858..8a724f4 100644
--- a/cleanlinks.1.in
+++ b/cleanlinks.1.in
@@ -1,16 +1,16 @@
-.TH cleanlinks 1 "@PACKAGE_STRING@"
+.TH CLEANLINKS 1 2004-04-23 "@PACKAGE_STRING@"
 .SH NAME
 cleanlinks \- remove dangling symbolic links and empty directories
 .SH SYNOPSIS
 .B cleanlinks
 .SH DESCRIPTION
 The
-.I cleanlinks
+.B cleanlinks
 program searches the directory tree descended from the current directory for
 symbolic links whose targets do not exist, and removes them.
 It then removes all empty directories in that directory tree.
 .PP
-.I cleanlinks
+.B cleanlinks
 is useful for cleaning up a shadow link tree created with
 .BR lndir (1)
 after files have been removed from the real directory.
@@ -20,9 +20,8 @@ directory.
 .SH SEE ALSO
 .BR lndir (1).
 .SH AUTHOR
-.PP
 The version of the
-.I cleanlinks
+.B cleanlinks
 included in this X.Org Foundation release was originally written
 by David Dawes wrote as a part of XFree86.
 .PP
diff --git a/imake.1.in b/imake.1.in
index ba5c9c5..23d8a3f 100644
--- a/imake.1.in
+++ b/imake.1.in
@@ -32,7 +32,7 @@
 .fi
 .RE
 ..
-.TH IMAKE 1 "@PACKAGE_STRING@"
+.TH IMAKE 1 2009-06-22 "@PACKAGE_STRING@"
 .SH NAME
 imake \- C preprocessor interface to the make utility
 .SH SYNOPSIS
@@ -43,63 +43,66 @@ imake \- C preprocessor interface to the make utility
 [ \fB\-s\fP \fIfilename\fP ] [ \fB\-e\fP ]
 [ \fB\-v\fP ]
 .SH DESCRIPTION
-.I Imake
+.B Imake
 is used to
-generate \fIMakefiles\fP from a template, a set of \fIcpp\fP macro functions,
+generate \fIMakefiles\fP from a template, a set of \fBcpp\fP macro functions,
 and a per-directory input file called an \fIImakefile\fP.  This allows machine
 dependencies (such as compiler options, alternate command names, and special
-\fImake\fP rules) to be kept separate from the descriptions of the
+\fBmake\fP rules) to be kept separate from the descriptions of the
 various items to be built.
 .SH OPTIONS
-The following command line options may be passed to \fIimake\fP:
+The following command line options may be passed to \fBimake\fP:
 .TP 8
-.B \-D\fIdefine\fP
-This option is passed directly to \fIcpp\fP.  It is typically used to set
-directory-specific variables.  For example, the X Window System used this
-flag to set \fITOPDIR\fP to the name of the directory containing the top
-of the core distribution and \fICURDIR\fP to the name of the current
+.BI \-D define
+This option is passed directly to \fBcpp\fP.
+It is typically used to set directory-specific variables.
+For example, the X Window System used this flag to set
+\fBTOPDIR\fP to the name of the directory containing the top
+of the core distribution and \fBCURDIR\fP to the name of the current
 directory, relative to the top.
 .TP 8
-.B \-I\fIdirectory\fP
-This option is passed directly to \fIcpp\fP.  It is typically used to
-indicate the directory in which the \fIimake\fP template and configuration
-files may be found.
+.BI \-I directory
+This option is passed directly to \fBcpp\fP.
+It is typically used to indicate the directory in which the
+\fBimake\fP template and configuration files may be found.
 .TP 8
-.B \-U\fIdefine\fP
-This option is passed directly to \fIcpp\fP.  It is typically used to
-unset variables when debugging \fIimake\fP configuration files.
+.BI \-U define
+This option is passed directly to \fBcpp\fP.
+It is typically used to unset variables when
+debugging \fBimake\fP configuration files.
 .TP 8
-.B \-T\fItemplate\fP
+.BI \-T template
 This option specifies the name of the master template file (which is usually
-located in the directory specified with \fI\-I\fP) used by \fIcpp\fP.
-The default is \fIImake.tmpl\fP.
+located in the directory specified with \fB\-I\fP) used by \fBcpp\fP.
+The default is \fBImake.tmpl\fP.
 .TP 8
-.B \-f \fIfilename\fP
-This option specifies the name of the per-directory input file.  The default
-is \fIImakefile\fP.
+.BI \-f " filename"
+This option specifies the name of the per-directory input file.
+The default is \fBImakefile\fP.
 .TP 8
-.B \-C \fIfilename\fP
-This option specifies the name of the .c file that is constructed in the
-current directory.  The default is \fIImakefile.c\fP.
+.BI \-C " filename"
+This option specifies the name of the \fI.c\fP file that is constructed
+in the current directory.
+The default is \fBImakefile.c\fP.
 .TP 8
-.B \-s \fIfilename\fP
-This option specifies the name of the \fImake\fP description file to be
-generated but \fImake\fP should not be invoked.
-If the \fIfilename\fP is a dash (\-), the
-output is written to \fIstdout\fP.  The default is to generate, but
-not execute, a \fIMakefile\fP.
+.BI \-s " filename"
+This option specifies the name of the \fBmake\fP description file to be
+generated but \fBmake\fP should not be invoked.
+If the \fIfilename\fP is a dash (\-), the output is written to \fIstdout\fP.
+The default is to generate, but not execute, a \fBMakefile\fP.
 .TP 8
 .B \-e
-This option indicates the \fIimake\fP should execute the generated
-\fIMakefile\fP.  The default is to leave this to the user.
+This option indicates the \fBimake\fP should execute the generated
+\fIMakefile\fP.
+The default is to leave this to the user.
 .TP 8
 .B \-v
-This option indicates that \fIimake\fP should print the \fIcpp\fP command line
+This option indicates that \fBimake\fP should print the \fBcpp\fP command line
 that it is using to generate the \fIMakefile\fP.
 .SH "HOW IT WORKS"
-\fIImake\fP invokes \fIcpp\fP with any \fI\-I\fP or \fI\-D\fP flags passed
-on the command line and passes the name of a file containing the
-following 3 lines:
+\fBImake\fP invokes \fBcpp\fP
+with any \fB\-I\fP or \fB\-D\fP flags passed on the command line
+and passes the name of a file containing the following 3 lines:
 .EX
 
 \&		#define IMAKE_TEMPLATE "Imake.tmpl"
@@ -107,97 +110,98 @@ following 3 lines:
 \&		#include IMAKE_TEMPLATE
 
 .EE
-where \fIImake.tmpl\fP and \fIImakefile\fP may be overridden by the
-\fI\-T\fP and \fI\-f\fP command options, respectively.
+where \fBImake.tmpl\fP and \fBImakefile\fP may be overridden by the
+\fB\-T\fP and \fB\-f\fP command options, respectively.
 .PP
-The IMAKE_TEMPLATE typically
+The \fBIMAKE_TEMPLATE\fP typically
 reads in a file containing machine-dependent parameters
-(specified as \fIcpp\fP symbols), a site-specific parameters file,
+(specified as \fBcpp\fP symbols), a site-specific parameters file,
 a file defining variables,
-a file
-containing \fIcpp\fP macro functions for generating \fImake\fP rules, and
-finally the \fIImakefile\fP (specified by INCLUDE_IMAKEFILE) in the current
-directory.  The \fIImakefile\fP uses the macro functions to indicate what
-targets should be built; \fIimake\fP takes care of generating the appropriate
-rules.
+a file containing \fBcpp\fP macro functions for generating \fBmake\fP rules,
+and finally the \fIImakefile\fP (specified by \fBINCLUDE_IMAKEFILE\fP)
+in the current directory.
+The \fIImakefile\fP uses the macro functions to indicate what
+targets should be built;
+\fBimake\fP takes care of generating the appropriate rules.
 .PP
-.I Imake
+.B Imake
 configuration files contain two types of variables, imake variables
-and make variables.  The imake variables are interpreted by cpp when
-.I imake
-is run.  By convention they are mixed case.  The make variables are
-written into the
-.I Makefile
+and make variables.
+The imake variables are interpreted by cpp when
+.B imake
+is run.
+By convention they are mixed case.
+The make variables are written into the
+.B Makefile
 for later interpretation by
-.I make.
+.B make.
 By convention make variables are upper case.
 .PP
-The rules file (usually named \fIImake.rules\fP in the configuration
-directory) contains a variety of \fIcpp\fP macro functions that are
-configured according to the current platform.  \fIImake\fP replaces
-any occurrences of the string ``@@'' with a newline to allow macros that
-generate more than one line of \fImake\fP rules.
+The rules file (usually named \fBImake.rules\fP in the configuration
+directory) contains a variety of \fBcpp\fP macro functions that are
+configured according to the current platform.
+\fBImake\fP replaces any occurrences of the string ``@@'' with a newline
+to allow macros that generate more than one line of \fBmake\fP rules.
 For example, the macro
 .EX
 
-\& #define      program_target(program, objlist)        @@\e
+\&#define      program_target(program, objlist)        @@\e
 program:        objlist         @@\e
         $(CC)  \-o  $@  objlist  $(LDFLAGS)
 
-
 .EE
 when called with
-.I "program_target(foo, foo1.o  foo2.o)"
+.B "program_target(foo, foo1.o  foo2.o)"
 will expand to
 .EX
 
 foo:    foo1.o  foo2.o
         $(CC)  \-o  $@  foo1.o  foo2.o  $(LDFLAGS)
-
 .EE
 .PP
-\fIImake\fP also replaces any occurrences of the word ``XCOMM'' with
+\fBImake\fP also replaces any occurrences of the word ``XCOMM'' with
 the character ``#'' to permit placing comments in the Makefile without
 causing ``invalid directive'' errors from the preprocessor.
 .PP
-Some complex \fIimake\fP macros require generated \fImake\fP variables
+Some complex \fBimake\fP macros require generated \fBmake\fP variables
 local to each invocation of the macro, often because their value
 depends on parameters passed to the macro.
-Such variables can be created by using an \fIimake\fP variable
+Such variables can be created by using an \fBimake\fP variable
 of the form \fBXVARdef\fP\fIn\fP, where \fIn\fP is a single digit.
-A unique \fImake\fP variable will be substituted.  Later occurrences
-of the variable \fBXVARuse\fP\fIn\fP will
+A unique \fBmake\fP variable will be substituted.
+Later occurrences of the variable \fBXVARuse\fP\fIn\fP will
 be replaced by the variable created by the corresponding
 \fBXVARdef\fP\fIn\fP.
 .PP
-On systems whose \fIcpp\fP reduces multiple tabs and spaces to a single
-space, \fIimake\fP attempts to put back any necessary tabs (\fImake\fP is
-very picky about the difference between tabs and spaces).  For this reason,
+On systems whose \fBcpp\fP reduces multiple tabs and spaces to a single space,
+\fBimake\fP attempts to put back any necessary tabs
+(\fBmake\fP is very picky about the difference between tabs and spaces).
+For this reason,
 colons (:) in command lines must be preceded by a backslash (\\).
 .SH "USE WITH THE X WINDOW SYSTEM"
-The X Window System used \fIimake\fP extensively up through the X11R6.9
+The X Window System used \fBimake\fP extensively up through the X11R6.9
 release, for both full builds within the source tree and external software.
 X has since moved to GNU autoconf and automake for its build system in
 X11R7.0 and later releases, but still maintains imake for building existing
 external software programs that have not yet converted.
 .PP
-As mentioned above, two special
-variables, \fITOPDIR\fP and \fICURDIR,\fP are set to make referencing files
-using relative path names easier.  For example, the following command is
-generated automatically to build the \fIMakefile\fP in the directory
-\fIlib/X/\fP (relative to the top of the sources):
+As mentioned above, two special variables, \fBTOPDIR\fP and \fBCURDIR,\fP
+are set to make referencing files using relative path names easier.
+For example, the following command is generated automatically
+to build the \fBMakefile\fP in the directory \fBlib/X/\fP
+(relative to the top of the sources):
 .EX
-
 	%  ../.././config/imake  \-I../.././config  \\
 		\-DTOPDIR=../../.   \-DCURDIR=./lib/X
 .EE
-When building X programs outside the source tree, a special symbol
-\fIUseInstalled\fP is defined and \fITOPDIR\fP and
-\fICURDIR\fP are omitted.  If the configuration files have been
-properly installed, the script \fIxmkmf\fP(1) may be used.
+When building X programs outside the source tree,
+a special symbol \fBUseInstalled\fP is defined
+and \fBTOPDIR\fP and \fBCURDIR\fP are omitted.
+If the configuration files have been properly installed,
+the script \fBxmkmf\fP(1) may be used.
 .SH "INPUT FILES"
 Here is a summary of the files read by
-.I imake
+.B imake
 as used by X.
 The indentation shows what files include what other files.
 .EX
@@ -213,49 +217,22 @@ The indentation shows what files include what other files.
             Library.tmpl        library rules
             Server.tmpl server rules
             Threads.tmpl        multi-threaded rules
-
 .EE
 .LP
-Note that \fIsite.def\fP gets included twice, once before the
-\fI*.cf\fP file and once after.  Although most site customizations
-should be specified after the \fI*.cf\fP file, some, such as the
-choice of compiler, need to be specified before, because other
-variable settings may depend on them.
+Note that \fBsite.def\fP gets included twice,
+once before the \fI*.cf\fP file and once after.
+Although most site customizations should be specified after the \fI*.cf\fP file,
+some, such as the choice of compiler, need to be specified before,
+because other variable settings may depend on them.
 .LP
-The first time \fIsite.def\fP is included, the variable BeforeVendorCF
-is defined, and the second time, the variable AfterVendorCF is
-defined.  All code in \fIsite.def\fP should be inside an #ifdef for
-one of these symbols.
-.SH FILES
-.TP
-Imakefile.c
-temporary input file for cpp
-.TP
-/tmp/Imf.XXXXXX
-temporary Makefile for -s
-.TP
-/tmp/IIf.XXXXXX
-temporary Imakefile if specified Imakefile uses # comments
-.TP
-@RAWCPP@
-default C preprocessor
-.SH "SEE ALSO"
-make(1), xmkmf(1)
-.TP
-Paul DuBois
-imake-Related Software and Documentation,
-http://www.snake.net/software/imake-stuff/
-.TP
-Paul DuBois
-Software Portability with imake, Second Edition,
-O'Reilly & Associates, 1996.
-.TP
-S. I. Feldman,
-Make \(em A Program for Maintaining Computer Programs
+The first time \fBsite.def\fP is included,
+the variable \fBBeforeVendorCF\fP is defined,
+and the second time, the variable \fBAfterVendorCF\fP is defined.
+All code in \fBsite.def\fP should be inside an #ifdef for one of these symbols.
 .SH "ENVIRONMENT VARIABLES"
 The following environment variables may be set, however their use is not
 recommended as they introduce dependencies that are not readily apparent
-when \fIimake\fP is run:
+when \fBimake\fP is run:
 .TP 5
 .B IMAKEINCLUDE
 If defined, this specifies a ``\-I'' include argument to pass to the
@@ -265,18 +242,50 @@ C preprocessor.  E.g., ``\-I/usr/X11/config''.
 If defined, this should be a valid path to a preprocessor program.
 E.g., ``/usr/local/cpp''.
 By default,
-.I imake
-will use cc -E or @RAWCPP@, depending on the OS specific configuration.
+.B imake
+will use
+.B cc \-E
+or
+.BR @RAWCPP@ ,
+depending on the OS specific configuration.
 .TP 5
 .B IMAKEMAKE
 If defined, this should be a valid path to a make program,
 such as ``/usr/local/make''.
 By default,
-.I imake
+.B imake
 will use whatever
-.I make
+.B make
 program is found using
-.I execvp(3).
+.BR execvp (3).
 This variable is only used if the ``\-e'' option is specified.
-.SH "AUTHOR"
+.SH FILES
+.TP
+.B Imakefile.c
+temporary input file for cpp
+.TP
+.BI /tmp/Imf. XXXXXX
+temporary Makefile for -s
+.TP
+.BI /tmp/IIf. XXXXXX
+temporary Imakefile if specified Imakefile uses # comments
+.TP
+.B @RAWCPP@
+default C preprocessor
+.SH SEE ALSO
+.BR cpp (1),
+.BR make (1),
+.BR xmkmf (1)
+.TP
+Paul DuBois
+.I imake-Related Software and Documentation,
+http://www.snake.net/software/imake-stuff/
+.TP
+Paul DuBois
+.I Software Portability with imake, Second Edition,
+O'Reilly & Associates, 1996.
+.TP
+S. I. Feldman,
+.I Make \(em A Program for Maintaining Computer Programs
+.SH AUTHORS
 Todd Brunhoff, Tektronix and MIT Project Athena; Jim Fulton, MIT X Consortium
diff --git a/makeg.1.in b/makeg.1.in
index e09df22..ad75e8f 100644
--- a/makeg.1.in
+++ b/makeg.1.in
@@ -23,7 +23,7 @@
 .\" from The Open Group.
 .\"
 .\"
-.TH MAKEG 1 "@PACKAGE_STRING@"
+.TH MAKEG 1 1996-02-02 "@PACKAGE_STRING@"
 .SH NAME
 makeg \- make a debuggable executable
 .SH SYNOPSIS
@@ -35,12 +35,12 @@ makeg \- make a debuggable executable
 ]
 .SH DESCRIPTION
 The
-.I makeg
+.B makeg
 script runs
-.I make,
+.B make,
 passing it variable settings to create a debuggable target when used
 with a Makefile generated by
-.I imake.
+.B imake.
 For example, it arranges for the C compiler to be called with the
 .B \-g
 option.
@@ -48,14 +48,15 @@ option.
 .TP 8
 .B MAKE
 The
-.I make
-program to use.  Default ``make''.
+.B make
+program to use.
+Default ``make''.
 .TP 8
 .B GDB
 Set to a non-null value if using the
-.I gdb
-debugger on Solaris 2, which requires additional debugging options to
-be passed to the compiler.
+.B gdb
+debugger on Solaris 2,
+which requires additional debugging options to be passed to the compiler.
 .SH "SEE ALSO"
-.I make (1),
-.I imake (1)
+.BR make (1),
+.BR imake (1)
diff --git a/mergelib.1.in b/mergelib.1.in
index 3fecec1..2eaf4ce 100644
--- a/mergelib.1.in
+++ b/mergelib.1.in
@@ -1,6 +1,6 @@
 .\" shorthand for double quote that works everywhere.
 .ds q \N'34'
-.TH MERGELIB 1 "@PACKAGE_STRING@"
+.TH MERGELIB 1 2002-10-12 "@PACKAGE_STRING@"
 .SH NAME
 mergelib \- merge one library into another
 .SH SYNOPSIS
@@ -10,7 +10,7 @@ mergelib \- merge one library into another
 .RI [ object-filename-prefix ]
 .SH DESCRIPTION
 The
-.I mergelib
+.B mergelib
 program merges objects from one library into another.
 The names of object files in
 .I from-library
@@ -21,7 +21,7 @@ The merged library will be left in
 .IR to-library .
 .SH AUTHOR
 Jim Fulton wrote the
-.I mergelib
+.B mergelib
 program for the X Consortium.
 .PP
 Colin Watson wrote this manual page, originally for the Debian Project.
diff --git a/mkdirhier.1.in b/mkdirhier.1.in
index e605c9b..3217a0b 100644
--- a/mkdirhier.1.in
+++ b/mkdirhier.1.in
@@ -22,7 +22,7 @@
 .\" dealing in this Software without prior written authorization from The
 .\" Open Group.
 .\"
-.TH MKDIRHIER 1 "@PACKAGE_STRING@"
+.TH MKDIRHIER 1 1988-10-26 "@PACKAGE_STRING@"
 .SH NAME
 mkdirhier \- makes a directory hierarchy
 .SH SYNOPSIS
@@ -30,10 +30,11 @@ mkdirhier \- makes a directory hierarchy
 directory ...
 .SH DESCRIPTION
 The
-.I mkdirhier
-command creates the specified directories. Unlike
-.I mkdir
-if any of the parent directories of the specified directory
-do not exist, it creates them as well.
+.B mkdirhier
+command creates the specified directories.
+Unlike
+.B mkdir
+if any of the parent directories of the specified directory do not exist,
+it creates them as well.
 .SH "SEE ALSO"
-mkdir(1)
+.BR mkdir (1)
diff --git a/mkhtmlindex.1.in b/mkhtmlindex.1.in
index 72196a9..c56827d 100644
--- a/mkhtmlindex.1.in
+++ b/mkhtmlindex.1.in
@@ -1,4 +1,4 @@
-.TH mkhtmlindex 1 "@PACKAGE_STRING@"
+.TH MKHTMLINDEX 1 2004-04-23 "@PACKAGE_STRING@"
 .SH NAME
 mkhtmlindex \- generate index files for HTML man pages
 .SH SYNOPSIS
@@ -6,7 +6,7 @@ mkhtmlindex \- generate index files for HTML man pages
 .I htmlmandir
 .SH DESCRIPTION
 The
-.I mkhtmlindex
+.B mkhtmlindex
 program generates index files for a directory of HTML-formatted manual
 pages.
 It searches for files whose names are of the form \(lqname.1.html\(rq,
@@ -17,7 +17,7 @@ Names and descriptions are found by scanning the first
 .I <H2>
 section of each page.
 .SH OPTIONS
-.I mkhtmlindex
+.B mkhtmlindex
 takes only one argument: the directory to process.
 .SH NOTES
 This utility is currently rather specific to X manual pages.
@@ -25,7 +25,7 @@ In particular, the format of the index files it outputs is not configurable,
 nor is the HTML formatting it expects of manual pages.
 .SH AUTHOR
 The version of the
-.I mkhtmlindex
+.B mkhtmlindex
 included in this X.Org Foundation release was originally written
 by David Dawes wrote as a part of XFree86.
 .PP
diff --git a/revpath.1.in b/revpath.1.in
index 6dadc4a..b0f05ac 100644
--- a/revpath.1.in
+++ b/revpath.1.in
@@ -1,4 +1,4 @@
-.TH REVPATH 1 "@PACKAGE_STRING@"
+.TH REVPATH 1 1999-01-02 "@PACKAGE_STRING@"
 .SH NAME
 revpath \- generate a relative path that can be used to undo a change-directory
 .SH SYNOPSIS
@@ -6,7 +6,7 @@ revpath \- generate a relative path that can be used to undo a change-directory
 .I path
 .SH DESCRIPTION
 The
-.I revpath
+.B revpath
 program prints out a relative path that is the ``reverse'' or ``inverse'' of
 .IR path .
 Start with two directories
@@ -35,8 +35,8 @@ If
 is invalid in some way (e.g., doesn't represent the path to a subdirectory)
 the output is also empty and no error messages are ever generated.
 .SH DIAGNOSTICS
-There are no diagnostics.  Error conditions are silently ignored, and the
-exit status is always 0.
+There are no diagnostics.
+Error conditions are silently ignored, and the exit status is always 0.
 .SH BUGS
 It isn't possible to reverse arbitrary relative paths.
 If any path element between the two end points of
diff --git a/xmkmf.1.in b/xmkmf.1.in
index 468e794..3592b3a 100644
--- a/xmkmf.1.in
+++ b/xmkmf.1.in
@@ -22,41 +22,43 @@
 .\" dealing in this Software without prior written authorization from The
 .\" Open Group.
 .\"
-.TH XMKMF 1 "@PACKAGE_STRING@"
+.TH XMKMF 1 2012-02-10 "@PACKAGE_STRING@"
 .SH NAME
 xmkmf \- create a Makefile from an Imakefile
 .SH SYNOPSIS
 .B xmkmf
-[ -a ] [
+[
+.B \-a
+] [
 .I topdir
 [
 .I curdir
 ] ]
 .SH DESCRIPTION
 The
-.I xmkmf
+.B xmkmf
 command is the normal way to create a
-.I Makefile
+.B Makefile
 from an
-.I Imakefile
+.B Imakefile
 shipped with third-party software.
 .PP
 When invoked with no arguments in a directory containing an
-.I Imakefile,
+.BR Imakefile ,
 the
-.I imake
+.B imake
 program is run with arguments appropriate for your system
 (configured into
-.I imake
+.B imake
 when it was built) and generates a
-.I Makefile.
+.BR Makefile .
 .PP
 When invoked with the
-.I \-a
+.B \-a
 option,
-.I xmkmf
+.B xmkmf
 builds the
-.I Makefile
+.B Makefile
 in the current directory, and then automatically executes
 ``make Makefiles'' (in case there are subdirectories),
 ``make includes'',
@@ -65,15 +67,17 @@ and ``make depend'' for you.
 If a
 .I topdir
 is given,
-.I xmkmf
+.B xmkmf
 assumes nothing is installed on your system and looks for files in
-the build tree instead of using the installed versions.  Optionally,
+the build tree instead of using the installed versions.
+Optionally,
 .I curdir
 may be specified as a relative pathname from the top of the build
-tree to the current directory.  It is necessary to supply
+tree to the current directory.
+It is necessary to supply
 .I curdir
 if the current directory has subdirectories, or the
-.I Makefile
+.B Makefile
 will not be able to build the subdirectories.
 .SH "SEE ALSO"
-imake(1)
+.BR imake (1)