commit - 18ecc2fd811d3419c597fc31663f3f4a0e14824b
commit + b7690a0add0d46f952cc44ce522bb0e2e802b24c
blob - ac77c6503b73774e694364f91a70f89a1bd6ccfe
blob + 431a410affaa4d9c92cd0d1ff0d7e5e8f936cbe0
--- doc/Commands.txt
+++ doc/Commands.txt
@@ -83,7 +83,22 @@ Connection Handling Commands
 	 - doc/Capabilities.txt
 
 - CHARCONV
-	See doc/Protocol.txt
+	CHARCONV <client-charset>
+	.
+	Set client character set encoding to <client-charset>.
+	.
+	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>.
+	.
+	This enables older clients and clients using "strange" character sets
+	to transparently participate in channels and direct messages to
+	clients using UTF-8, which should be the default today.
+
+	References:
+	 - <http://ngircd.barton.de/doc/Protocol.txt>
+	 - doc/Protocol.txt
 
 - NICK
 	NICK <nick>