you mean you are able to see thai characters when you connect to your server with an IRC client, but the bot isnt't? what is your server's ircd and what IRC client do you use? (ircd version can be obtained with /quote version)
eggdrop doesn't alter server's output in any way, to see or not to see the correct characters is up to your IRC client and its interpretation of the character set
I don't actaully mean by that but you said "eggdrop doesn't alter server's output" so i think it may be tcl encoding setting and I don't think that tcl script will change this.
At first point I think that it need some patch for server module.
why don't you simply describe your situation in details? i.e. how and where exactly have you observed that issue - in the bot's log, on party-line, in some script's output, or whatever; also provide details about your configuration - eggdrop version, Tcl version, loaded scripts etc.
assuming that you don't use a script for that, it sounds puzzling to me... but I'll take a look at the source, although I'm pretty sure eggdrop doesn't convert PRIVMSGs
Things that are broken, but aren't getting fixed anytime soon:
* High-bit characters are being filtered from channel names. This is a
fault of the Tcl interpreter, and not Eggdrop. The Tcl interpreter
filters the characters when it reads a file for interpreting. Update
your Tcl to version 8.1 or higher.
* Version 8.1 of Tcl doesn't support unicode characters, for example, è.
If those characters are handled in a script as text, you run into errors.
Eggdrop can't handle these errors at the moment.
·awyeah·
==================================
Facebook: jawad@idsia.ch (Jay Dee) PS: Guys, I don't accept script helps or requests personally anymore.
==================================