egghelp/eggheads community

Problems with Eggdrop and extended characters. (utf-8)

2004-11-28T20:40:38-04:00

anyway

try export LANG=no, nn_NO, nb_NO, or whatever norvegian locales you happen to have on your system

Statistics: Posted by demond — Sun Nov 28, 2004 8:40 pm

Problems with Eggdrop and extended characters. (utf-8)

2004-11-28T19:07:23-04:00

if it works for your bot wouldn't it be full-good or am I missing something here?

Statistics: Posted by demond — Sun Nov 28, 2004 7:07 pm

Problems with Eggdrop and extended characters. (utf-8)

2004-11-28T18:19:48-04:00

No. I'd like this problem fixed, instead of making a half-good TCL workaround.

Statistics: Posted by Alpha — Sun Nov 28, 2004 6:19 pm

Problems with Eggdrop and extended characters. (utf-8)

2004-11-28T11:22:02-04:00

did you try that u2a proc?

Statistics: Posted by demond — Sun Nov 28, 2004 11:22 am

Problems with Eggdrop and extended characters. (utf-8)

2004-11-28T11:11:01-04:00

Yes! Encoding is a step in the right direction.. If I remember correctly, this was resolved using a few simple commands, probably SET & EXPORT? However, I can't remember what it was. I've compared to another Fedora box and can't find out what I need to change from what I read off the "set" command. Any further input?

Statistics: Posted by Alpha — Sun Nov 28, 2004 11:11 am

Problems with Eggdrop and extended characters. (utf-8)

2004-11-28T10:08:01-04:00

or you could just fix the encoding on the box your bot is running from.

I don't believe that would help... but I may be wrong

Statistics: Posted by demond — Sun Nov 28, 2004 10:08 am

Problems with Eggdrop and extended characters. (utf-8)

2004-11-27T17:52:17-04:00

or you could just fix the encoding on the box your bot is running from.

Statistics: Posted by greenbear — Sat Nov 27, 2004 5:52 pm

Problems with Eggdrop and extended characters. (utf-8)

2004-11-27T17:20:31-04:00

include this in your config before loading module channels:

Code:

proc u2a {s} {    set res ""    foreach i [split $s ""] {        scan $i %c c        if {$c<128} {append res $i} else {append res \\u[format %04.4X $c]}    }    set res } ;#RS

it converts norvegian chars in strings to \u-escaped ASCII

then specify your channel names (in the config or .chan file) as [u2a #yournorgechannel]

Statistics: Posted by demond — Sat Nov 27, 2004 5:20 pm

Problems with Eggdrop and extended characters. (utf-8)

2004-11-27T15:44:11-04:00

The bot does everything it's supposed to do. It joins the correct channel, but with an "Ã" instead of the "ø" in the channelname.

Statistics: Posted by Alpha — Sat Nov 27, 2004 3:44 pm

Problems with Eggdrop and extended characters. (utf-8)

2004-11-27T12:06:01-04:00

set your console +v and inspect the content of bot's JOIN msg; this might give some hint of what's happening - whether your bot tries to join that channel at all

Statistics: Posted by demond — Sat Nov 27, 2004 12:06 pm

Problems with Eggdrop and extended characters. (utf-8)

2004-11-27T00:35:03-04:00

Hi!

One of my linux-boxes was recently upgraded from Fedora Core 1 to Core 2. I had to build a new eggdrop from source, and installed eggdrop1.6.17. I copied the eggdrop-executeable and modules to my old directory, overwriting the old files. The bot started up as normal, but failed to join my channel. The channelname has the norwegian character "ø" in it's name, but this was replaced by an "Ã". This is an old problem, one I've come across before. But I've forgotten how it was solved...

The TCL version is 8.4.5-7, on a Fedora Core 2 box.

Any input is appreciated, thanx!

Statistics: Posted by Alpha — Sat Nov 27, 2004 12:35 am