Bug 235541 – net-im/pidgin cannot handle icq in different charsets anymore

• Product: Gentoo Linux
• Status: RESOLVED FIXED

[Description Stefan de Konink 2008-08-23 15:53:16 UTC]

People are not able to read or receive messages send from ICQ in another charset. It appears to be wrongly converted. I suggest to mask 2.5.0 until this critical problems are solved.

I'm seeing stranger things lately especially related to ICQ.

Reproducible: Always

Steps to Reproduce:
1. type a message (English) to a foreign user
2. foreign user sees strange characters

[Comment 1 Jeroen Roovers (RETIRED) 2008-08-23 16:01:46 UTC]

(In reply to comment #0)
> People are not able to read or receive messages send from ICQ in another
> charset. It appears to be wrongly converted. I suggest to mask 2.5.0 until this
> critical problems are solved.

It's masked by keywording already... use a stable version (currently 2.4.3) if you have to avoid certain problems that the testing version exhibits.

[Comment 2 Stefan de Konink 2008-08-23 16:07:37 UTC]

These problems also affects the previous versions. I suspect something changed in the protocol. If I am looking with Wireshark to one message that Pidgin 2.4.3 and 2.5.0 can't parse in pidgin I see just " ", in Wireshark I see that the message was encoded in the FEATURES area.

When I send messages in 2.4.3 in plain English it doesn't work. When I translate my message using Google Translate to Russian, paste it, it is received.

[Comment 3 Olivier Crete (RETIRED) 2008-08-23 16:32:31 UTC]

charsets in the ICQ protocol are an horrible mess... so don't be surprised it they start f*ing up regularly. If you use a non-ascii language, I recommend you use another system.

[Comment 4 Stefan de Konink 2008-08-23 16:36:56 UTC]

(In reply to comment #3)
> charsets in the ICQ protocol are an horrible mess... so don't be surprised it
> they start f*ing up regularly.

I see in #pidgin: We know about the AIM chat message problem
But the Trac of Pidgin is terribly slow :(

> If you use a non-ascii language, I recommend you use another system.

This is about ascii not arriving at non-ascii users... or worse mobile phone messages in ascii not being displayed in Pidgin at all (since last week). But you are right, I should brainwash my friends and make them use Jabber (I'm running a server anyway). I hope there is a telephone widget/java thing for Jabber already that makes my life more easy.

[Comment 5 Stefan de Konink 2009-02-20 00:27:08 UTC]

If the patch in the URL can be added to Pidgin. You can close this bug :)

[Comment 6 Olivier Crete (RETIRED) 2009-02-20 17:23:23 UTC]

added to cvs