Lots more GOOBE stuff. Now works with 'make html'!

1 files changed, 33 insertions, 28 deletions

diff --git a/doc/wish.1 b/doc/wish.1
index d50539d..1df677e 100644
--- a/doc/wish.1
+++ b/doc/wish.1
@@ -5,7 +5,7 @@
 '\" See the file "license.terms" for information on usage and redistribution
 '\" of this file, and for a DISCLAIMER OF ALL WARRANTIES.
 '\" 
-'\" RCS: @(#) $Id: wish.1,v 1.7 2007/10/26 20:13:23 dgp Exp $
+'\" RCS: @(#) $Id: wish.1,v 1.8 2007/10/29 16:04:14 dkf Exp $
 '\" 
 .so man.macros
 .TH wish 1 8.0 Tk "Tk Applications"
@@ -14,7 +14,7 @@
 .SH NAME
 wish \- Simple windowing shell
 .SH SYNOPSIS
-\fBwish\fR ?-encoding \fIname\fR? ?\fIfileName arg arg ...\fR?
+\fBwish\fR ?\fB\-encoding \fIname\fR? ?\fIfileName arg arg ...\fR?
 .SH OPTIONS
 .IP "\fB\-encoding \fIname\fR" 20
 .VS 8.5
@@ -58,7 +58,6 @@ variable without interpreting them.
 This provides a mechanism for passing arguments such as \fB\-name\fR
 to a script instead of having \fBwish\fR interpret them.
 .BE
-
 .SH DESCRIPTION
 .PP
 \fBWish\fR is a simple program consisting of the Tcl command
@@ -66,19 +65,21 @@ language, the Tk toolkit, and a main program that reads commands
 from standard input or from a file.
 It creates a main window and then processes Tcl commands.
 If \fBwish\fR is invoked with arguments, then the first few
-arguments, ?\fB-encoding \fIname\fR? ?\fIfileName\fR? specify the
+arguments, ?\fB\-encoding \fIname\fR? ?\fIfileName\fR? specify the
 name of a script file, and, optionally, the
 encoding of the text data stored in that script file.  A value
 for \fIfileName\fR is recognized if the appropriate argument
-does not start with ``\-''.
+does not start with
+.QW \- .
 .PP
 If there are no arguments, or the arguments do not specify a \fIfileName\fR,
 then wish reads Tcl commands interactively from standard input.
 It will continue processing commands until all windows have been
 deleted or until end-of-file is reached on standard input.
-If there exists a file \fB.wishrc\fR in the home directory of
-the user, \fBwish\fR evaluates the file as a Tcl script
-just before reading the first command from standard input.
+If there exists a file
+.QW \fB.wishrc\fR
+in the home directory of the user, \fBwish\fR evaluates the file as a
+Tcl script just before reading the first command from standard input.
 .PP
 If arguments to \fBwish\fR do specify a \fIfileName\fR, then 
 \fIfileName\fR is treated as the name of a script file.
@@ -86,25 +87,25 @@ If arguments to \fBwish\fR do specify a \fIfileName\fR, then
 presumably creates a user interface), then it will respond to events
 until all windows have been deleted.
 Commands will not be read from standard input.
-There is no automatic evaluation of \fB.wishrc\fR when the name
-of a script file is presented on the \fBwish\fR command line,
+There is no automatic evaluation of
+.QW \fB.wishrc\fR
+when the name of a script file is presented on the \fBwish\fR command line,
 but the script file can always \fBsource\fR it if desired.
-
-.SH "OPTIONS"
+.SH "OPTION PROCESSING"
 .PP
 \fBWish\fR automatically processes all of the command-line options
 described in the \fBOPTIONS\fR summary above.
 Any other command-line arguments besides these are passed through
 to the application using the \fBargc\fR and \fBargv\fR variables
 described later.
-
 .SH "APPLICATION NAME AND CLASS"
 .PP
 The name of the application, which is used for purposes such as
 \fBsend\fR commands, is taken from the \fB\-name\fR option,
 if it is specified;  otherwise it is taken from \fIfileName\fR,
 if it is specified, or from the command name by which
-\fBwish\fR was invoked.  In the last two cases, if the name contains a ``/''
+\fBwish\fR was invoked.  In the last two cases, if the name contains a
+.QW /
 character, then only the characters after the last slash are used
 as the application name.
 .PP
@@ -112,7 +113,6 @@ The class of the application, which is used for purposes such as
 specifying options with a \fBRESOURCE_MANAGER\fR property or .Xdefaults
 file, is the same as its name except that the first letter is
 capitalized.
-
 .SH "VARIABLES"
 .PP
 \fBWish\fR sets the following Tcl variables:
@@ -123,8 +123,8 @@ not including the options described above.
 .TP 15
 \fBargv\fR
 Contains a Tcl list whose elements are the \fIarg\fR arguments
-that follow a \fB\-\|\-\fR option or don't match any of the
-options described in OPTIONS above, in order, or an empty string
+that follow a \fB\-\|\-\fR option or do not match any of the
+options described in \fBOPTIONS\fR above, in order, or an empty string
 if there are no such arguments.
 .TP 15
 \fBargv0\fR
@@ -142,7 +142,6 @@ window's geometry.
 Contains 1 if \fBwish\fR is reading commands interactively (\fIfileName\fR
 was not specified and standard input is a terminal-like
 device), 0 otherwise.
-
 .SH "SCRIPT FILES"
 .PP
 If you create a Tcl script in a file whose first line is
@@ -152,8 +151,8 @@ If you create a Tcl script in a file whose first line is
 then you can invoke the script file directly from your shell if
 you mark it as executable.
 This assumes that \fBwish\fR has been installed in the default
-location in /usr/local/bin;  if it's installed somewhere else
-then you'll have to modify the above line to match.
+location in /usr/local/bin;  if it is installed somewhere else
+then you will have to modify the above line to match.
 Many UNIX systems do not allow the \fB#!\fR line to exceed about
 30 characters in length, so be sure that the \fBwish\fR executable
 can be accessed with a short file name.
@@ -166,7 +165,7 @@ following three lines:
 exec wish "$0" "$@"\fR
 .CE
 This approach has three advantages over the approach in the previous
-paragraph.  First, the location of the \fBwish\fR binary doesn't have
+paragraph.  First, the location of the \fBwish\fR binary does not have
 to be hard-wired into the script:  it can be anywhere in your shell
 search path.  Second, it gets around the 30-character file name limit
 in the previous approach.
@@ -185,24 +184,30 @@ since the backslash at the end of the second line causes the third
 line to be treated as part of the comment on the second line.
 .PP
 The end of a script file may be marked either by the physical end of
-the medium, or by the character, '\\032' ('\\u001a', control-Z).
+the medium, or by the character,
+.QW \e032
+.PQ \eu001a ", control-Z" .
 If this character is present in the file, the \fBwish\fR application
 will read text up to but not including the character.  An application
 that requires this character in the file may encode it as
-``\\032'', ``\\x1a'', or ``\\u001a''; or may generate it by use of commands 
-such as \fBformat\fR or \fBbinary\fR.
+.QW \e032 ,
+.QW \ex1a ,
+or
+.QW \eu001a ;
+or may generate it by use of commands such as \fBformat\fR or \fBbinary\fR.
 .SH PROMPTS
 .PP
 When \fBwish\fR is invoked interactively it normally prompts for each
-command with ``\fB% \fR''.  You can change the prompt by setting the
+command with
+.QW "\fB% \fR" .
+You can change the prompt by setting the
 variables \fBtcl_prompt1\fR and \fBtcl_prompt2\fR.  If variable
 \fBtcl_prompt1\fR exists then it must consist of a Tcl script
 to output a prompt;  instead of outputting a prompt \fBwish\fR
 will evaluate the script in \fBtcl_prompt1\fR.
 The variable \fBtcl_prompt2\fR is used in a similar way when
-a newline is typed but the current command isn't yet complete;
-if \fBtcl_prompt2\fR isn't set then no prompt is output for
+a newline is typed but the current command is not yet complete;
+if \fBtcl_prompt2\fR is not set then no prompt is output for
 incomplete commands.
-
 .SH KEYWORDS
 shell, toolkit