118 files changed, 1622 insertions, 1299 deletions

diff --git a/doc/3DBorder.3 b/doc/3DBorder.3
index d0fb7f6..8b9a810 100644
--- a/doc/3DBorder.3
+++ b/doc/3DBorder.3
@@ -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: 3DBorder.3,v 1.9 2007/10/26 20:13:22 dgp Exp $
+'\" RCS: @(#) $Id: 3DBorder.3,v 1.10 2007/10/29 16:04:12 dkf Exp $
 '\" 
 .so man.macros
 .TH Tk_Alloc3DBorderFromObj 3 8.1 Tk "Tk Library Procedures"
@@ -100,7 +100,7 @@ for \fBTk_Fill3DRectangle\fR).
 .AP XPoint *pointPtr in
 Pointer to array of points describing the set of vertices in a polygon.
 The polygon need not be closed (it will be closed automatically if it
-isn't).
+is not).
 .AP int numPoints in
 Number of points at \fI*pointPtr\fR.
 .AP int polyBorderWidth in
@@ -168,7 +168,7 @@ prevents \fBTk_Get3DBorder\fR from caching the return value, so
 .PP
 \fBTk_Get3DBorderFromObj\fR returns the token for an existing border, given
 the window and color name used to create the border.
-\fBTk_Get3DBorderFromObj\fR doesn't actually create the border; it must
+\fBTk_Get3DBorderFromObj\fR does not actually create the border; it must
 already have been created with a previous call to
 \fBTk_Alloc3DBorderFromObj\fR or \fBTk_Get3DBorder\fR.  The return
 value is cached in \fIobjPtr\fR, which speeds up
@@ -238,7 +238,9 @@ Each procedure takes \fIx\fR, \fIy\fR, \fIwidth\fR, and \fIheight\fR
 arguments that describe the rectangular area of the beveled edge
 (e.g., \fIwidth\fR is the border width for \fBTk_3DVerticalBevel\fR).
 The \fIleftBorder\fR and \fItopBorder\fR arguments indicate the
-position of the border relative to the ``inside'' of the object, and
+position of the border relative to the
+.QW inside
+of the object, and
 \fIrelief\fR indicates the relief of the inside of the object relative
 to the outside.
 \fBTk_3DVerticalBevel\fR just draws a rectangular region.
diff --git a/doc/CanvTkwin.3 b/doc/CanvTkwin.3
index efa9125..167abff 100644
--- a/doc/CanvTkwin.3
+++ b/doc/CanvTkwin.3
@@ -4,7 +4,7 @@
 '\" See the file "license.terms" for information on usage and redistribution
 '\" of this file, and for a DISCLAIMER OF ALL WARRANTIES.
 '\" 
-'\" RCS: @(#) $Id: CanvTkwin.3,v 1.5 2007/01/05 00:00:48 nijtmans Exp $
+'\" RCS: @(#) $Id: CanvTkwin.3,v 1.6 2007/10/29 16:04:12 dkf Exp $
 '\" 
 .so man.macros
 .TH Tk_CanvasTkwin 3 4.1 Tk "Tk Library Procedures"
@@ -140,7 +140,7 @@ modified using image commands.
 .PP
 \fBTk_CanvasTagsParseProc\fR and \fBTk_CanvasTagsPrintProc\fR are
 procedures that handle the \fB\-tags\fR option for canvas items.
-The code of a canvas type manager won't call these procedures
+The code of a canvas type manager will not call these procedures
 directly, but will use their addresses to create a \fBTk_CustomOption\fR
 structure for the \fB\-tags\fR option.   The code typically looks
 like this:
diff --git a/doc/CanvTxtInfo.3 b/doc/CanvTxtInfo.3
index 10fee39..bd4879c 100644
--- a/doc/CanvTxtInfo.3
+++ b/doc/CanvTxtInfo.3
@@ -4,7 +4,7 @@
 '\" See the file "license.terms" for information on usage and redistribution
 '\" of this file, and for a DISCLAIMER OF ALL WARRANTIES.
 '\" 
-'\" RCS: @(#) $Id: CanvTxtInfo.3,v 1.3 2004/09/19 16:05:36 dkf Exp $
+'\" RCS: @(#) $Id: CanvTxtInfo.3,v 1.4 2007/10/29 16:04:12 dkf Exp $
 '\" 
 .so man.macros
 .TH Tk_CanvasTextInfo 3 4.0 Tk "Tk Library Procedures"
@@ -58,7 +58,7 @@ selected text, in pixels.
 \fIselFgColorPtr\fR points to an XColor that describes the foreground
 color to be used when drawing selected text.
 \fIselItemPtr\fR points to the item that is currently selected, or
-NULL if there is no item selected or if the canvas doesn't have the
+NULL if there is no item selected or if the canvas does not have the
 selection.
 \fIselectFirst\fR and \fIselectLast\fR give the indices of the first
 and last selected characters in \fIselItemPtr\fR, as returned by the
diff --git a/doc/ConfigWidg.3 b/doc/ConfigWidg.3
index 102394f..c4426a7 100644
--- a/doc/ConfigWidg.3
+++ b/doc/ConfigWidg.3
@@ -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: ConfigWidg.3,v 1.18 2007/10/26 20:13:22 dgp Exp $
+'\" RCS: @(#) $Id: ConfigWidg.3,v 1.19 2007/10/29 16:04:12 dkf Exp $
 '\" 
 .so man.macros
 .TH Tk_ConfigureWidget 3 4.1 Tk "Tk Library Procedures"
@@ -118,9 +118,12 @@ The \fItype\fR field indicates what type of configuration option this is
 (e.g. \fBTK_CONFIG_COLOR\fR for a color value, or \fBTK_CONFIG_INT\fR for
 an integer value).  The \fItype\fR field indicates how to use the
 value of the option (more on this below).
-The \fIargvName\fR field is a string such as ``\-font'' or ``\-bg'',
+The \fIargvName\fR field is a string such as
+.QW \-font
+or
+.QW \-bg ,
 which is compared with the values in \fIargv\fR (if \fIargvName\fR is
-NULL it means this is a grouped entry;  see GROUPED ENTRIES below).  The
+NULL it means this is a grouped entry;  see \fBGROUPED ENTRIES\fR below).  The
 \fIdbName\fR and \fIdbClass\fR fields are used to look up a value
 for this option in the option database.  The \fIdefValue\fR field
 specifies a default value for this configuration option if no
@@ -162,7 +165,8 @@ of each \fIspecs\fR entry indicates where in \fIwidgRec\fR to store
 the information about this configuration option.  You should use the
 \fBTk_Offset\fR macro to generate \fIoffset\fR values (see below for
 a description of \fBTk_Offset\fR).  The location indicated by
-\fIwidgRec\fR and \fIoffset\fR will be referred to as the ``target''
+\fIwidgRec\fR and \fIoffset\fR will be referred to as the
+.QW target
 in the descriptions below.
 .PP
 The \fItype\fR field of each entry in \fIspecs\fR determines what
@@ -181,7 +185,7 @@ If \fBTK_CONFIG_NULL_OK\fR is specified in \fIspecFlags\fR then the value
 may be an empty string, in which case the target and \fItkwin\fR's
 active cursor will be set to \fBNone\fR.
 If the previous value of the target
-wasn't \fBNone\fR, then it is freed by passing it to \fBTk_FreeCursor\fR.
+was not \fBNone\fR, then it is freed by passing it to \fBTk_FreeCursor\fR.
 .TP
 \fBTK_CONFIG_ANCHOR\fR
 The value must be an ASCII string identifying an anchor point in one of the ways
@@ -197,14 +201,24 @@ is stored in the target.
 If \fBTK_CONFIG_NULL_OK\fR is specified in \fIspecFlags\fR then the value
 may be an empty string, in which case the target is set to \fBNone\fR.
 If the previous value of the target
-wasn't \fBNone\fR, then it is freed by passing it to \fBTk_FreeBitmap\fR.
+was not \fBNone\fR, then it is freed by passing it to \fBTk_FreeBitmap\fR.
 .TP
 \fBTK_CONFIG_BOOLEAN\fR
 The value must be an ASCII string specifying a boolean value.  Any
-of the values ``true'', ``yes'', ``on'', or ``1'',
+of the values
+.QW true ,
+.QW yes ,
+.QW on ,
+or
+.QW 1 ,
 or an abbreviation of one of these values, means true;
-any of the values ``false'', ``no'', ``off'', or ``0'', or an abbreviation of
-one of these values, means false.
+any of the values
+.QW false ,
+.QW no ,
+.QW off ,
+or
+.QW 0 ,
+or an abbreviation of one of these values, means false.
 The target is expected to be an integer;  for true values it will
 be set to 1 and for false values it will be set to 0.
 .TP
@@ -216,7 +230,7 @@ is stored in the target.
 If \fBTK_CONFIG_NULL_OK\fR is specified in \fIspecFlags\fR then the value
 may be an empty string, in which case the target will be set to NULL.
 If the previous value of the target
-wasn't NULL, then it is freed by passing it to \fBTk_Free3DBorder\fR.
+was not NULL, then it is freed by passing it to \fBTk_Free3DBorder\fR.
 .TP
 \fBTK_CONFIG_CAP_STYLE\fR
 The value must be
@@ -234,7 +248,7 @@ is stored in the target.
 If \fBTK_CONFIG_NULL_OK\fR is specified in \fIspecFlags\fR then the value
 may be an empty string, in which case the target will be set to \fBNone\fR.
 If the previous value of the target
-wasn't NULL, then it is freed by passing it to \fBTk_FreeColor\fR.
+was not NULL, then it is freed by passing it to \fBTk_FreeColor\fR.
 .TP
 \fBTK_CONFIG_CURSOR\fR
 This option is identical to \fBTK_CONFIG_ACTIVE_CURSOR\fR except
@@ -265,12 +279,15 @@ is stored in the target.
 If \fBTK_CONFIG_NULL_OK\fR is specified in \fIspecFlags\fR then the value
 may be an empty string, in which case the target will be set to NULL.
 If the previous value of the target
-wasn't NULL, then it is freed by passing it to \fBTk_FreeFont\fR.
+was not NULL, then it is freed by passing it to \fBTk_FreeFont\fR.
 .TP
 \fBTK_CONFIG_INT\fR
 The value must be an ASCII integer string
-in the format accepted by \fBstrtol\fR (e.g. ``0''
-and ``0x'' prefixes may be used to specify octal or hexadecimal
+in the format accepted by \fBstrtol\fR (e.g.
+.QW 0
+and
+.QW 0x
+prefixes may be used to specify octal or hexadecimal
 numbers, respectively).  The string is converted to an integer
 value and the integer is stored in the target.
 .TP
@@ -314,19 +331,22 @@ of the value is made by allocating memory space with
 space.  A pointer to the new string is stored in the target.
 If \fBTK_CONFIG_NULL_OK\fR is specified in \fIspecFlags\fR then the value
 may be an empty string, in which case the target will be set to NULL.
-If the previous value of the target wasn't NULL, then it is
+If the previous value of the target was not NULL, then it is
 freed by passing it to \fBTcl_Free\fR.
 .TP
 \fBTK_CONFIG_SYNONYM\fR
 This \fItype\fR value identifies special entries in \fIspecs\fR that
 are synonyms for other entries.  If an \fIargv\fR value matches the
-\fIargvName\fR of a \fBTK_CONFIG_SYNONYM\fR entry, the entry isn't used
+\fIargvName\fR of a \fBTK_CONFIG_SYNONYM\fR entry, the entry is not used
 directly. Instead, \fBTk_ConfigureWidget\fR searches \fIspecs\fR
 for another entry whose \fIargvName\fR is the same as the \fIdbName\fR
 field in the \fBTK_CONFIG_SYNONYM\fR entry;  this new entry is used just
 as if its \fIargvName\fR had matched the \fIargv\fR value.  The
 synonym mechanism allows multiple \fIargv\fR values to be used for
-a single configuration option, such as ``\-background'' and ``\-bg''.
+a single configuration option, such as
+.QW \-background
+and
+.QW \-bg .
 .TP
 \fBTK_CONFIG_UID\fR
 The value is translated to a \fBTk_Uid\fR
@@ -369,8 +389,8 @@ First, if the \fIflags\fR argument to \fBTk_ConfigureWidget\fR has
 the \fBTK_CONFIG_ARGV_ONLY\fR bit set (i.e., \fIflags\fR | \fBTK_CONFIG_ARGV_ONLY\fR != 0),
 then the option database and
 \fIdefValue\fR fields are not used.  In this case, if an entry in
-\fIspecs\fR doesn't match a field in \fIargv\fR then nothing happens:
-the corresponding target isn't modified.  This feature is useful
+\fIspecs\fR does not match a field in \fIargv\fR then nothing happens:
+the corresponding target is not modified.  This feature is useful
 when the goal is to modify certain configuration options while
 leaving others in their current state, such as when a \fBconfigure\fR
 widget command is being processed.
@@ -399,7 +419,7 @@ on the type of the target.
 This flag is typically used to allow a
 feature to be turned off entirely, e.g. set a cursor value to
 \fBNone\fR so that a window simply inherits its parent's cursor.
-If this bit isn't set then empty strings are processed as strings,
+If this bit is not set then empty strings are processed as strings,
 which generally results in an error.
 .TP
 \fBTK_CONFIG_DONT_SET_DEFAULT\fR
@@ -520,7 +540,7 @@ to release all of the resources associated with configuration options.
 It scans through \fIspecs\fR and for each entry corresponding to a
 resource that must be explicitly freed (e.g. those with
 type \fBTK_CONFIG_COLOR\fR), it frees the resource in the widget record.
-If the field in the widget record doesn't refer to a resource (e.g.
+If the field in the widget record does not refer to a resource (e.g.
 it contains a null pointer) then no resource is freed for that
 entry.
 After freeing a resource, \fBTk_FreeOptions\fR sets the
diff --git a/doc/ConfigWind.3 b/doc/ConfigWind.3
index c9f0089..ec00323 100644
--- a/doc/ConfigWind.3
+++ b/doc/ConfigWind.3
@@ -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: ConfigWind.3,v 1.2 1998/09/14 18:22:46 stanton Exp $
+'\" RCS: @(#) $Id: ConfigWind.3,v 1.3 2007/10/29 16:04:12 dkf Exp $
 '\" 
 .so man.macros
 .TH Tk_ConfigureWindow 3 4.0 Tk "Tk Library Procedures"
@@ -81,7 +81,6 @@ New cursor to use for \fItkwin\fR.  If \fBNone\fR is specified, then
 \fItkwin\fR will not have its own cursor;  it will use the cursor
 of its parent.
 .BE
-
 .SH DESCRIPTION
 .PP
 These procedures are analogous to the X library procedures
@@ -127,9 +126,8 @@ To change the stacking order, use the procedure \fBTk_RestackWindow\fR.
 The procedure \fBTk_SetWindowColormap\fR will automatically add
 \fItkwin\fR to the \fBTK_COLORMAP_WINDOWS\fR property of its
 nearest top-level ancestor if the new colormap is different from
-that of \fItkwin\fR's parent and \fItkwin\fR isn't already in
+that of \fItkwin\fR's parent and \fItkwin\fR is not already in
 the \fBTK_COLORMAP_WINDOWS\fR property.
-
 .SH BUGS
 .PP
 \fBTk_SetWindowBackgroundPixmap\fR and \fBTk_SetWindowBorderPixmap\fR
@@ -145,9 +143,7 @@ and \fIpixmap\fR has been passed to the X server.
 A similar problem occurs for the \fIcursor\fR argument passed to
 \fBTk_DefineCursor\fR.  The solution is the same as for pixmaps above:
 call \fBTk_MakeWindowExist\fR before freeing the cursor.
-
 .SH "SEE ALSO"
 Tk_MoveToplevelWindow, Tk_RestackWindow
-
 .SH KEYWORDS
 attributes, border, color, configure, height, pixel, pixmap, width, window, x, y
diff --git a/doc/CrtCmHdlr.3 b/doc/CrtCmHdlr.3
index 7c050ec..a146447 100644
--- a/doc/CrtCmHdlr.3
+++ b/doc/CrtCmHdlr.3
@@ -4,7 +4,7 @@
 '\" See the file "license.terms" for information on usage and redistribution
 '\" of this file, and for a DISCLAIMER OF ALL WARRANTIES.
 '\" 
-'\" RCS: @(#) $Id: CrtCmHdlr.3,v 1.2 2004/09/19 16:05:36 dkf Exp $
+'\" RCS: @(#) $Id: CrtCmHdlr.3,v 1.3 2007/10/29 16:04:12 dkf Exp $
 '\" 
 .so man.macros
 .TH Tk_CreateClientMessageHandler 3 "8.4" Tk "Tk Library Procedures"
@@ -27,7 +27,7 @@ Procedure to invoke whenever a ClientMessage X event occurs on any display.
 .PP
 
 \fBTk_CreateClientMessageHandler\fR arranges for \fIproc\fR to be invoked
-in the future whenever a ClientMessage X event occurs that isn't handled by
+in the future whenever a ClientMessage X event occurs that is not handled by
 \fBWM_PROTOCOL\fR.  \fBTk_CreateClientMessageHandler\fR is intended for use
 by applications which need to watch X ClientMessage events, such as drag and
 drop applications.
@@ -49,7 +49,7 @@ The \fItkwin\fR parameter to \fIproc\fR is the Tk window which is
 associated with this event.  \fIEventPtr\fR is a pointer to the X event.
 .PP
 Whenever an X ClientMessage event is processed by \fBTk_HandleEvent\fR,
-the \fIproc\fR is called if it wasn't handled as a \fBWM_PROTOCOL\fR.
+the \fIproc\fR is called if it was not handled as a \fBWM_PROTOCOL\fR.
 The return value from \fIproc\fR is normally 0.
 A non-zero return value indicates that the event is not to be handled
 further; that is, \fIproc\fR has done all processing that is to be
diff --git a/doc/CrtErrHdlr.3 b/doc/CrtErrHdlr.3
index 0bfeae8..713e3a5 100644
--- a/doc/CrtErrHdlr.3
+++ b/doc/CrtErrHdlr.3
@@ -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: CrtErrHdlr.3,v 1.5 2007/10/26 20:13:22 dgp Exp $
+'\" RCS: @(#) $Id: CrtErrHdlr.3,v 1.6 2007/10/29 16:04:12 dkf Exp $
 '\" 
 .so man.macros
 .TH Tk_CreateErrorHandler 3 "" Tk "Tk Library Procedures"
@@ -26,13 +26,13 @@ Tk_ErrorHandler
 Display whose errors are to be handled.
 .AP int error in
 Match only error events with this value in the \fIerror_code\fR
-field.  If -1, then match any \fIerror_code\fR value.
+field.  If \-1, then match any \fIerror_code\fR value.
 .AP int request in
 Match only error events with this value in the \fIrequest_code\fR
-field.  If -1, then match any \fIrequest_code\fR value.
+field.  If \-1, then match any \fIrequest_code\fR value.
 .AP int minor in
 Match only error events with this value in the \fIminor_code\fR
-field.  If -1, then match any \fIminor_code\fR value.
+field.  If \-1, then match any \fIminor_code\fR value.
 .AP Tk_ErrorProc *proc in
 Procedure to invoke whenever an error event is received for
 \fIdisplay\fR and matches \fIerror\fR, \fIrequest\fR, and \fIminor\fR.
@@ -43,14 +43,13 @@ Arbitrary one-word value to pass to \fIproc\fR.
 Token for error handler to delete (return value from a previous
 call to \fBTk_CreateErrorHandler\fR).
 .BE
-
 .SH DESCRIPTION
 .PP
 \fBTk_CreateErrorHandler\fR arranges for a particular procedure
 (\fIproc\fR) to be called whenever certain protocol errors occur on a
 particular display (\fIdisplay\fR).  Protocol errors occur when
 the X protocol is used incorrectly, such as attempting to map a window
-that doesn't exist.  See the Xlib documentation for \fBXSetErrorHandler\fR
+that does not exist.  See the Xlib documentation for \fBXSetErrorHandler\fR
 for more information on the kinds of errors that can occur.
 For \fIproc\fR to be invoked
 to handle a particular error, five things must occur:
@@ -58,15 +57,15 @@ to handle a particular error, five things must occur:
 The error must pertain to \fIdisplay\fR.
 .IP [2]
 Either the \fIerror\fR argument to \fBTk_CreateErrorHandler\fR
-must have been -1, or the \fIerror\fR argument must match
+must have been \-1, or the \fIerror\fR argument must match
 the \fIerror_code\fR field from the error event.
 .IP [3]
 Either the \fIrequest\fR argument to \fBTk_CreateErrorHandler\fR
-must have been -1, or the \fIrequest\fR argument must match
+must have been \-1, or the \fIrequest\fR argument must match
 the \fIrequest_code\fR field from the error event.
 .IP [4]
 Either the \fIminor\fR argument to \fBTk_CreateErrorHandler\fR
-must have been -1, or the \fIminor\fR argument must match
+must have been \-1, or the \fIminor\fR argument must match
 the \fIminor_code\fR field from the error event.
 .IP [5]
 The protocol request to which the error pertains must have been
@@ -98,14 +97,13 @@ If more than more than one handler matches a particular error, then
 they are invoked in turn.  The handlers will be invoked in reverse
 order of creation:  most recently declared handler first.
 If any handler returns 0, then subsequent (older) handlers will
-not be invoked.  If no handler returns 0, then Tk invokes X'es
+not be invoked.  If no handler returns 0, then Tk invokes X's
 default error handler, which prints an error message and aborts the
 program.  If you wish to have a default handler that deals with errors
 that no other handler can deal with, then declare it first.
 .PP
-The X documentation states that ``the error handler should not call
-any functions (directly or indirectly) on the display that will
-generate protocol requests or that will look for input events.''
+The X documentation states that
+.QW "the error handler should not call any functions (directly or indirectly) on the display that will generate protocol requests or that will look for input events."
 This restriction applies to handlers declared by \fBTk_CreateErrorHandler\fR;
 disobey it at your own risk.
 .PP
diff --git a/doc/CrtItemType.3 b/doc/CrtItemType.3
index 0922e5a..fbaa410 100644
--- a/doc/CrtItemType.3
+++ b/doc/CrtItemType.3