diff options
author | jan.nijtmans <nijtmans@users.sourceforge.net> | 2023-07-14 06:31:41 (GMT) |
---|---|---|
committer | jan.nijtmans <nijtmans@users.sourceforge.net> | 2023-07-14 06:31:41 (GMT) |
commit | 2d5f7e8dd76dd8207be4946a14992e3b96c8e2a2 (patch) | |
tree | 47a857cd341f086c3cd8b063abc39ef3245a3799 /doc/chan.n | |
parent | d08eb4bc7df247a0d4975869959c02aaf123ae4d (diff) | |
parent | ab5eabd5a4842c5a3cb009214eb7dea5f0ebdb6d (diff) | |
download | tcl-2d5f7e8dd76dd8207be4946a14992e3b96c8e2a2.zip tcl-2d5f7e8dd76dd8207be4946a14992e3b96c8e2a2.tar.gz tcl-2d5f7e8dd76dd8207be4946a14992e3b96c8e2a2.tar.bz2 |
Rebase to 9.0
Diffstat (limited to 'doc/chan.n')
-rw-r--r-- | doc/chan.n | 7 |
1 files changed, 3 insertions, 4 deletions
@@ -200,16 +200,15 @@ platforms it is \fBcrlf\fR for both input and output. \fBbinary\fR . Like \fBlf\fR, no end-of-line translation is performed, but in addition, sets -\fB\-eofchar\fR to the empty string to disable it, sets \fB\-encoding\fR to -\fBiso8859-1\fR, and sets \fB-profile\fR to \fBstrict\fR so the the channel is -fully configured for binary input and output: Each byte read from the channel +\fB\-eofchar\fR to the empty string to disable it, and sets \fB\-encoding\fR +to \fBiso8859-1\fR. With this one setting, a channel is fully configured +for binary input and output: Each byte read from the channel becomes the Unicode character having the same value as that byte, and each character written to the channel becomes a single byte in the output. This makes it possible to work seamlessly with binary data as long as each character in the data remains in the range of 0 to 255 so that there is no distinction between binary data and text. For example, A JPEG image can be read from a such a channel, manipulated, and then written back to such a channel. - .TP \fBcr\fR . |