On Fri, Sep 14, 2001 at 12:48:40AM +0700, Max wrote: > Hi again. > > Im going also to implement a translations for EPIC, > and want to ask USERS for suggestions and ideas. > > As for me, for russian language, > it will be enough to have charset parameter for each window, > default window charset and terminal charset.
[snip] > - Non-8bit encodings. > Japanese, Chinese and similar languages use either 2-byte encoding, > or some scripts to encode/decode text into ascii. > There exist several 2byte 'charsets' as well as several scripts, IIRC. > As for Japanese - i've seen different channels using different methods > even under the same OS. Did you ever take a look at UTF-8 or something? This way you don't have to specify a charset, since it can represent all characters. For just the privmsg, you won't even need support from the server to make it work, all clients on the channel should just agree to use UTF-8. I would really like to make channels and nicks UTF-8 too, but that would require a change in the server, since it really should make it case insensitive. I know that atleast japanse people use some non-8bit charset, it would really be nice if they switched too. > Here i'm completely giving up, having never seen how such languages > are used in console (are they used at all? :) Afaik, atleast Linux supports things like UTF-8 in console, but I never used it, and never tried it. I could be wrong here though. :) Kurt _______________________________________________ List mailing list [EMAIL PROTECTED] http://epicsol.org/mailman/listinfo/list
