#9 Wish: Support for /CODEPAGE

[Szymon Stefanek]

:irc.wenet.ru 001 Pragma :Welcome to the WeNet IRC Network
Pragma!~pragma@xxx
:irc.wenet.ru 002 Pragma :Your host is irc.wenet.ru, running
version ircd-RU!(Bahamut-1.4.35)-1.0(07)-02
...
:irc.wenet.ru 005 Pragma ... CODEPAGES ... :are available on
this server
...
:irc.wenet.ru 700 Pragma CP1251 :is now your translation
scheme
>>> CODEPAGE UTF8
:irc.wenet.ru 700 Pragma UTF8 :is now your translation scheme
>>> JOIN #tokyo,#ny,#siena,#ukraina
:)

[Entrope]

Logged In: YES
user_id=10120

What would this do? That seems to be something that should
be negotiated between clients or on a per-channel basis. It
would not affect suggested numeric message texts. It could
not affect things like channel names, nicknames or message
text, since arbitrary character set pairs do not have
bijective mappings.

[Szymon Stefanek]

Logged In: YES
user_id=1150052

You simply assume that the network handles only UTF8
charset. Users are allowed to issue a /CODEPAGE
<charset> command to specify that they're using a specific
charset and that the server should remap the messages from
their charset to utf8 (and back from utf8 to their charset).
irc.wenet.ru supports only cyrillic codepages but having a
standard codebase that supports all (read: many) of them
would allow an easy transition to the UTF8 standard while
still leaving people use their own charset (old clients/scripts).
/charset utf8 would set a no-op mapping obviously. Servers
could have also a default charset that would be set on login
(RPL_YOURCHARSET) for the transition period.