DonationCoder.com Software > Mircryption

[XCHAT] Can't receive messages containing umlauts or special character

(1/2) > >>

bamboo123:
Hello ppl,

I found some issue with latest official version (v1.19.01) as well as with the pre release version (v0.4.0-alpha) from gjehle. Both version do not print/receive messages containing umlauts or special characters like äöüßéá etc (tested with xchat 2.8.6 on an ubuntu 8.10 32bit system).

PS: Other users receive my (send) messages containing umlauts without problems, as well as i see them on my screen. the problem is only with receiving such messages.
PSS: I forgot to mention, that i use "ISO-8859-15 (Western Europe)" as character set in xchat.

gjehle:
Hi Bamboo,

thanks for reporting this (also thanks for the mail you sent pointing me here).
This problem never occurred to me (I'm usually using UTF-8) but I'll look into it as soon as I find some spare time, hopefully next weekend, but no promises :x

Can you give me some background?
Are you on Windows or Linux and which version is it?
What version of XChat are you running?
Did you compile it yourself or are you running a binary version?

bamboo123:
(...) (tested with xchat 2.8.6 on an ubuntu 8.10 32bit system).-bamboo123 (February 25, 2009, 07:37 PM)
--- End quote ---
The xchat version is a pre compiled package from the ubuntu (linux) backports (Version: 2.8.6-2ubuntu1).

gjehle:
(...) (tested with xchat 2.8.6 on an ubuntu 8.10 32bit system).-bamboo123 (February 25, 2009, 07:37 PM)
--- End quote ---
The xchat version is a pre compiled package from the ubuntu (linux) backports (Version: 2.8.6-2ubuntu1).
-bamboo123 (February 26, 2009, 07:33 AM)
--- End quote ---

gee, stupid me.
I should open my eyes a bit more ;-)

bamboo123:
I also noticed, that it's impossible to set a crypted Topic, when the channel name contains a special char on iso-15: #abendeßen :No such channel.

EDIT: I tried some things and found out, that the error only occurs, when the channel name contains special characters. On querries and normal channels messages containing special characters work fine. Hope that helps to fix the bug.

Navigation

[0] Message Index

[#] Next page