1 files changed, 9 insertions, 21 deletions
diff --git a/doc/tclvars.n b/doc/tclvars.n
index 16f684e..4a4a16e 100644
--- a/doc/tclvars.n
+++ b/doc/tclvars.n
@@ -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: tclvars.n,v 1.28 2007/10/24 14:29:39 dkf Exp $
+'\" RCS: @(#) $Id: tclvars.n,v 1.29 2007/10/26 20:11:53 dgp Exp $
 '\" 
 .so man.macros
 .TH tclvars n 8.0 Tcl "Tcl Built-In Commands"
@@ -39,11 +39,8 @@ variables.
 .RS
 Under Windows, the environment variables PATH and COMSPEC in any
 capitalization are converted automatically to upper case.  For instance, the
-PATH variable could be exported by the operating system as
-.QW path ,
-.QW Path ,
-.QW PaTh ,
-etc., causing otherwise simple Tcl code to have to
+PATH variable could be exported by the operating system as ``path'',
+``Path'', ``PaTh'', etc., causing otherwise simple Tcl code to have to
 support many special cases.  All other environment variables inherited by
 Tcl are left unmodified.  Setting an env array variable to blank is the
 same as unsetting it as this is the behavior of the underlying Windows OS.
@@ -81,8 +78,7 @@ The \fIsigName\fR element will be the symbolic name of the signal that caused
 the process to terminate; it will be one of the names from the
 include file signal.h, such as \fBSIGPIPE\fR.
 The \fImsg\fR element will be a short human-readable message
-describing the signal, such as
-.QW "write on pipe with no readers"
+describing the signal, such as ``write on pipe with no readers''
 for \fBSIGPIPE\fR.
 .TP
 \fBCHILDSTATUS\fI pid code\fR
@@ -99,8 +95,7 @@ The \fIsigName\fR element will be the symbolic name of the signal that caused
 the process to suspend; this will be one of the names from the
 include file signal.h, such as \fBSIGTTIN\fR.
 The \fImsg\fR element will be a short human-readable message
-describing the signal, such as
-.QW "background tty read"
+describing the signal, such as ``background tty read''
 for \fBSIGTTIN\fR.
 .TP
 \fBNONE\fR
@@ -118,8 +113,7 @@ of the error that occurred, such as \fBENOENT\fR; this will
 be one of the values defined in the include file errno.h.
 The \fImsg\fR element will be a human-readable
 message corresponding to \fIerrName\fR, such as
-.QW "no such file or directory"
-for the \fBENOENT\fR case.
+``no such file or directory'' for the \fBENOENT\fR case.
 .PP
 To set the \fB-errorcode\fR return option, applications should use library
 procedures such as \fBTcl_SetObjErrorCode\fR, \fBTcl_SetReturnOptions\fR,
@@ -269,9 +263,7 @@ binary number.
 .VE 8.5
 .PP
 .RS
-17 digits is
-.QW perfect
-for IEEE floating-point in that it allows
+17 digits is ``perfect'' for IEEE floating-point in that it allows
 double-precision values to be converted to strings and back to
 binary with no loss of information.  However, using 17 digits prevents
 any rounding, which produces longer, less intuitive results.  For example,
@@ -342,9 +334,7 @@ This variable and functionality only exist if
 .TP
 \fBtcl_wordchars\fR
 The value of this variable is a regular expression that can be set to
-control what are considered
-.QW word
-characters, for instances like
+control what are considered ``word'' characters, for instances like
 selecting a word by double-clicking in text in Tk.  It is platform
 dependent.  On Windows, it defaults to \fB\\S\fR, meaning anything
 but a Unicode space character.  Otherwise it defaults to \fB\\w\fR,
@@ -352,9 +342,7 @@ which is any Unicode word character (number, letter, or underscore).
 .TP
 \fBtcl_nonwordchars\fR
 The value of this variable is a regular expression that can be set to
-control what are considered
-.QW non-word
-characters, for instances like
+control what are considered ``non-word'' characters, for instances like
 selecting a word by double-clicking in text in Tk.  It is platform
 dependent.  On Windows, it defaults to \fB\\s\fR, meaning any Unicode space
 character.  Otherwise it defaults to \fB\\W\fR, which is anything but a