High bit characters in Tcl & eggdrop

stere0 · Post by **stere0** » Fri Sep 28, 2001 4:39 pm

i get and recompile my eggdrop with 1.6-current and everything is run perfectly with this case. thanks

stdragon · Post by **stdragon** » Fri Sep 28, 2001 9:33 pm

Maybe the problem is with the script. It sounds like your bot is able to join the channel with the weird letter in it, so it must be handling the utf correctly.

Sendron · Post by **Sendron** » Sat Sep 29, 2001 9:48 am

Yeah.. the bot has no trouble with joining the channel, but when its supposed to run tcl scripts in this channel, it goes bananas..

|^Raven^| · Post by **|^Raven^|** » Sun Sep 30, 2001 10:12 pm

Well, I don't know about problems with the character in the #channel, but I use this quite often in 1.6.5:

if {[info commands realputserv] == ""} {
rename putserv realputserv
proc putserv { thestring } {
realputserv [encoding convertfrom identity $thestring]
}
}
if {[info commands realputdcc] == ""} {
rename putdcc realputdcc
proc putdcc { idx thestring } {
realputdcc $idx [encoding convertfrom identity $thestring]
}
}

- does anyone know if stdarg's patch will fix my need to have to use this snippet of code anymore?

Thanks,

Raven.

Baerchen · Post by **Baerchen** » Thu Nov 08, 2001 12:49 pm

Hi,
being the author of CHATstats, I'm interested in knowing where exactly the problem can be within the script, from a theoretical point of view.

There's no encoding transformation/converting in the script. For channel names or nick names, whatever strange characters they contain, the script just takes the characters, does some list and/or string processing and outputs them. Where could be the point where the script messes up?
The problem is, even a simple one-line-script (bound to join or whatever) like

if {[onchan $channel $nick]} {do_this}

would mess up if the nick contained strange characters.

So I'd like to know what I can include as a workaround. Any ideas ?

Thnx in advance,

Baerchen