Problem with some characters

tnd · Post by **tnd** » Fri Dec 17, 2004 7:12 am

I notice that raw text that bot get from channel public messages or server message bot some characters is not correct.

I would like to know how to fix it by modify code or using tcl script but I don't have any idea.

Some characters of thai text can display correct but some has been change to other characters.

I am not sure if I need to add some config to make it work correct.

I try both LANG=th_TH or add encode cp874, tis-620 to tclegg.h but it still have problem

eggdrop v1.6.17
Tcl version: 8.3.3
OS: Linux 2.4.20

demond · Post by **demond** » Fri Dec 17, 2004 10:49 am

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)

tnd · Post by **tnd** » Fri Dec 17, 2004 11:03 am

Server running version Unreal3.2.1

Bot can see thai font but some characters is not correct.

Example: นึกว่าที่เดียวกัน -> นกว่ที่เดียแy

I have no problem with thai font on mIRC client

but I wonders message in echo bot DCC chat can show text correctly

demond · Post by **demond** » Fri Dec 17, 2004 12:01 pm

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

tnd · Post by **tnd** » Fri Dec 17, 2004 10:31 pm

Anyone has the solution or suggestion?

It is the problem of tcl encoding?

demond · Post by **demond** » Fri Dec 17, 2004 11:15 pm

what tcl?

you didn't say anything about a tcl script

did you mean that characters become garbled after processing by a script?

tnd · Post by **tnd** » Fri Dec 17, 2004 11:19 pm

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.

demond · Post by **demond** » Sat Dec 18, 2004 3:15 am

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.

demond · Post by **demond** » Sat Dec 18, 2004 3:18 am

oops you've already given version details...

I actually wonder if this is a script output or not; and if not, where exactly did you notice it

tnd · Post by **tnd** » Sat Dec 18, 2004 3:32 am

I found the channel message in party line that some charactors was altered.

But the messages that type in party line show correctly.

demond · Post by **demond** » Sat Dec 18, 2004 3:49 am

you mean you have console +p? or do you use some script that relays channel messages to party-line (effectively the same as console +p)?

tnd · Post by **tnd** » Sat Dec 18, 2004 4:05 am

Yes I set +p and turn on everything msgs, public, joins, kicks/modes, cmds, misc, bots, files, server, debug, wallops

Public message (also server message, NickServ reply) was altered but message when user talking in party-line not altered.

demond · Post by **demond** » Sat Dec 18, 2004 5:10 am

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

tnd · Post by **tnd** » Sat Dec 18, 2004 6:09 am

I try to remove all scripts and load the follow modules

Module loaded: dns
Module loaded: channels
Module loaded: irc
Module loaded: server
Module loaded: ctcp
Module loaded: notes (with lang support)
Module loaded: console (with lang support)
Module loaded: blowfish
Module loaded: assoc

The problem still exists

awyeah · Post by **awyeah** » Sun Dec 19, 2004 9:13 pm

Taken from: eggdrop1.6.xx/doc/known-problems.txt

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.