commit - a7f37cebdc300b3b87bb8d6b558769cf11441f61
commit + 79731a57f3f35744236407f128cdd09c32b700fa
blob - c7fd7826b85539d6e6615362b9693897a2e7fa27
blob + d0f0780f549a18b00f7f439d2336f7dcbcd147c7
--- doc/Protocol.txt
+++ doc/Protocol.txt
@@ -186,9 +186,21 @@ II.5 Client character encoding conversion
      Command: CHARCONV
   Parameters: <client-charset>
      Used by: registered clients
-     Replies: RPL_IP_CHARCONV_MSG, ERR_IP_CHARCONV_MSG
+     Replies: RPL_IP_CHARCONV, ERR_IP_CHARCONV
 
+A client can set its character set encoding using the CHARCONV command:
+after receiving such a command, the server translates all message data
+received from the client using the set <client-charset> to the server
+encoding (UTF-8), and all message data which is to be sent to the client
+from the server encoding (UTF-8) to <client-charset>.
 
+The list of supported <client-charset>'s is implementation dependent.
+
+If a client sets its <client-charset> to the server encoding (UTF-8),
+it disables all conversions; the connection behaves as if no CHARCONV
+command has been sent at all in this session.
+
+
 III. Numerics used by IRC+ Protocol
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
@@ -201,7 +213,7 @@ Numerics 800-849 are used for status and success messa
 
 III.1 IRC+ status and success numerics
 
-800 - RPL_IP_CHARCONV_MSG
+801 - RPL_IP_CHARCONV
 	%1 :Client encoding set"
 
 		%1	client character set
@@ -209,5 +221,5 @@ III.1 IRC+ status and success numerics
 
 III.2 IRC+ failure and error numerics
 
-850 - ERR_IP_CHARCONV_MSG
+851 - ERR_IP_CHARCONV
 	:Can't initialize client encoding