My eggdrop cant join channel with special ascii characters

[Mouse]

My eggdrop wont join this channel in my conf.
what i should do ?

channel add #†å£ {
chanmode "+k TAAA"
idle-kick 0
stopnethack-mode 0
revenge-mode 0
aop-delay 5:30
need-key { putserv "JOIN #†å£ TAAA" }
flood-chan 0:0
flood-deop 0:0
flood-kick 0:0
flood-join 0:0
flood-ctcp 0:0
flood-nick 0:0
}

[awyeah]

Maybe it's because of the non-aplhanumeric characters in the channels name. In DCC (partyline) type:

Code: Select all

.+chan #†å£
.chanset #†å£ chanmode +k TAAA
.save

[Mouse]

dont work..

in telnet

the ascii char will change to . or ?

stupid telnet

[awyeah]

Maybe the transfer type is in binary and not ASCII. Which text editor do you use on your shell? Modify the file in windows wordpad then directly upload it to the shell and then restart your bot.

[Alchera]

With a channel name like #†å£ no wonder there's a problem. Having the character set on the shell set correctly may or may not fix it. Those characters simply cannot be translated by the bot.

[awyeah]

But there are many arabic channels which utilize these non-aplhanumeric characters. I know pico sucks, it doesn't recognize them and weird characters form if you paste them on it.

The eggdrop does have support for these characters I guess, but some unix text editors don't.

[evildude]

One thing you can try is while you're on the partyline invite the bot to the channel and see how your eggdrop interprets those characters and then do a .+chan with the name of the channel that came accross the invite.

[greenbear]

encoding is your friend.

[YooHoo]

ok, I'll bite why is everyone so damn worked up about this? To have a special character or non-alphanumberic symbol in tcl, all that's required is a backslash ( \ ) before the character that is to processed as plain text, as described in the Suninet tcl guide... or did I miss something?

Code: Select all

channel add #\†\å\£ { 
+blah -blah
}

[]Kami[]

Or try Evangeline - www.averse.piasta.pl ...It's based on Eggdrop, if im not wrong it aswell support special characters in channel names...

[user]

To have a special character or non-alphanumberic symbol in tcl, all that's required is a backslash ( \ ) before the character that is to processed as plain text, as described in the Suninet tcl guide... or did I miss something?

You missed the point of escaping. Escaping a char is only needed if that char has a special meaning to the tcl interpreter that you wish to avoid. Escaping those chars doesn't make a difference. It's the way he encoded his config vs the encoding used when reading it in that's the problem. (I think)

Mouse: what happens if you add the channel from the partyline? (if that doesn't work, you need to fix your locale settings and/or upgrade/downgrade tcl/eggdrop

[awyeah]

user is right YooHoo, well atleast that's what I've learned from the past 6 months. These non-aplhanumeric characters are not special scripting characters as }, {, ], [, ", \ etc.

So by adding a "\" infront of them will not work and it is pointless. I think he will have to use them in the HEX format. Encode them using the encoding function or manually add the hex ascii codes.

Examples:
\x80
\x98
\xA9
\xFF

[YooHoo]

hehehe errr, yea, kinda backwards, isn't it? oh poop... /me makes mental note... no more answering threads while half asleep....

[KrzychuG]

Or try Evangeline - www.averse.piasta.pl ...It's based on Eggdrop, if im not wrong it aswell support special characters in channel names...

Not quite. It works quite good with our iso8859-2/iso8859-1 encoding, but not fully yet. Generally he will have same problem as in eggdrop.