Support for /CODEPAGE

Szymon Stefanek pragma at kvirc.net
Mon Nov 1 11:31:25 EST 2004


Now that I'm thinking better of it, a more conservative approach would be
to have default encodings for each daemon port (instead of setting utf8 as 
default as suggested before).
In the worst case one could set the default encoding to iso8859-1 on port 6667 
and all the clients connected to that port would have their native encodings 
completly preserved between each other: no visible change on the network. 
Smarter clients, users or scripts could just issue the appropriate /CODEPAGE 
command in order to partially enter the "unicode world". The smartest clients  
at all (mapping on client side required) would issue /CODEPAGE utf8 to become 
completly unicode aware.

-- 

Szymon Stefanek

------------------------------------------------------------------------------
-
- Solitary trees, if they grow at all, grow strong.
-
------------------------------------------------------------------------------
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://lists.ircd-hybrid.org/pipermail/hybrid/attachments/20041101/d070dc9a/attachment.pgp>


More information about the hybrid mailing list