More GOOBE quoting

1 files changed, 14 insertions, 11 deletions

diff --git a/doc/fcopy.n b/doc/fcopy.n
index 69e6016..d59ddf8 100644
--- a/doc/fcopy.n
+++ b/doc/fcopy.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: fcopy.n,v 1.12 2007/10/24 14:29:38 dkf Exp $
+'\" RCS: @(#) $Id: fcopy.n,v 1.13 2007/10/25 14:07:32 dkf Exp $
 '\" 
 .so man.macros
 .TH fcopy n 8.0 Tcl "Tcl Built-In Commands"
@@ -59,7 +59,9 @@ then all data already queued for \fIoutchan\fR is written out.
 Note that \fIinchan\fR can become readable during a background copy.
 You should turn off any \fBfileevent\fR handlers during a background
 copy so those handlers do not interfere with the copy.
-Any I/O attempted by a \fBfileevent\fR handler will get a "channel busy" error.
+Any I/O attempted by a \fBfileevent\fR handler will get a
+.QW "channel busy"
+error.
 .PP
 \fBFcopy\fR translates end-of-line sequences in \fIinchan\fR and \fIoutchan\fR
 according to the \fB\-translation\fR option
@@ -78,15 +80,16 @@ means that the incoming characters are converted internally first
 UTF-8 and then into the encoding of the channel \fBfcopy\fR writes
 to. See the manual entry for \fBfconfigure\fR for details on the
 \fB\-encoding\fR and \fB\-translation\fR options. No conversion is
-done if both channels are
-set to encoding "binary" and have matching translations. If only the
-output channel is set to
-encoding "binary" the system will write the internal UTF-8
-representation of the incoming characters. If only the input channel
-is set to encoding "binary" the system will assume that the incoming
-bytes are valid UTF-8 characters and convert them according to the
-output encoding. The behaviour of the system for bytes which are not
-valid UTF-8 characters is undefined in this case.
+done if both channels are set to encoding
+.QW "binary"
+and have matching translations. If only the output channel is set to encoding
+.QW "binary"
+the system will write the internal UTF-8 representation of the incoming
+characters. If only the input channel is set to encoding
+.QW "binary"
+the system will assume that the incoming bytes are valid UTF-8 characters and
+convert them according to the output encoding. The behaviour of the system for
+bytes which are not valid UTF-8 characters is undefined in this case.
 .SH EXAMPLES
 .PP
 The first example transfers the contents of one channel exactly to