Skip to content

Commit 1e0a60e

Browse files
committed
doc/protocol: remove UTF-8 explanation
These days, this is common knowledge, and doesn't need a lengthy explanation.
1 parent e9c99e0 commit 1e0a60e

File tree

1 file changed

+1
-9
lines changed

1 file changed

+1
-9
lines changed

doc/protocol.xml

+1-9
Original file line numberDiff line numberDiff line change
@@ -59,15 +59,7 @@
5959

6060
<para>
6161
All data between the client and the server is encoded in
62-
UTF-8. (Note: In UTF-8 all standard ansi characters, 0-127 are
63-
the same as in standard ansi encoding. Also, no ansi character
64-
appears in any multi-byte characters. So, you can use
65-
standard C functions like <function>strlen</function>, and
66-
<function>strcpy</function> just fine with UTF-8 encoded
67-
strings. For example: <returnvalue>OK</returnvalue> encoded in
68-
UTF-8 is simply <returnvalue>OK</returnvalue>. For more
69-
information on UTF-8:
70-
<ulink url="http://www.cl.cam.ac.uk/~mgk25/unicode.html#utf-8"/>)
62+
UTF-8.
7163
</para>
7264
</section>
7365

0 commit comments

Comments
 (0)