Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Changed "binary data" to "binary string". Thanks to Nathan for the rationale.
pyk: Except that my intent was that the term "binary string" should be avoided so that people don't think there are different types of strings in Tcl. It would be better to say that "binary data is represented by a string that is comprised only of characters 0 to 255." |
|---|---|
| Downloads: | Tarball | ZIP archive |
| Timelines: | family | ancestors | encoding-for-review-alt |
| Files: | files | file ages | folders |
| SHA3-256: |
96781584b92cafa72efe37398af8ea0c |
| User & Date: | oehhar 2024-06-17 06:26:30.883 |
| Original Comment: | Changed "binary data" to "binary string". Thanks to Nathan for the rationale |
Context
|
2024-06-17
| ||
| 06:26 |
Changed "binary data" to "binary string". Thanks to Nathan for the rationale.
pyk: Except that my... Closed-Leaf check-in: 96781584b9 user: oehhar tags: encoding-for-review-alt | |
|
2024-06-14
| ||
| 15:09 | Import selections of [4d6aa33b2f] (branch: encoding-for-review) and alternate wording. check-in: f5243d7263 user: oehhar tags: encoding-for-review-alt | |
Changes
Changes to doc/encoding.n.
| ︙ | ︙ | |||
14 15 16 17 18 19 20 | .BE .SH INTRODUCTION .PP Strings in Tcl are a sequence of Unicode codepoints. If strings are imported or exported from Tcl, they should be transfered to an encoding like cp1252, iso8859-1, Shift\-JIS, utf-8, utf-16, etc. .PP | | > > | > | | < > > | | 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 | .BE .SH INTRODUCTION .PP Strings in Tcl are a sequence of Unicode codepoints. If strings are imported or exported from Tcl, they should be transfered to an encoding like cp1252, iso8859-1, Shift\-JIS, utf-8, utf-16, etc. .PP Tcl Strings which are transfered to an encoding are represented within Tcl as binary strings, where each byte is represented by a codepoint with a value in the range of 0 to 255. Binary strings are typically handled using the \fBbinary\fR command. The command \fBstring length\fR returns the required byte count which may be different to the original character count. .PP As an illustrative example, the Tcl string consisting of one character "\N'196'" (Unicode codepoint 0xC4) may be transfered to utf-8 encoding like this: .CS % set e [encoding convertto utf-8 \N'196'] % string length $e 2 % binary scan $e cucu b1 b2 %set b1 195 % set b2 132 .CE The resulting utf-8 data is stored as a binary string consisting of the two bytes 195 and 132. .SH DESCRIPTION .PP Performs one of several encoding related operations, depending on \fIoption\fR. The legal \fIoption\fRs are: .\" METHOD: convertfrom .TP \fBencoding convertfrom\fR ?\fIencoding\fR? \fIdata\fR |
| ︙ | ︙ |