Version: (using KDE 4.1.3) OS: Linux Installed from: Ubuntu Packages The problem is that most of ICQ users with windows (ICQ6, QIP, Miranda) and linux (Gajim, Pidgin) clients see russian letters, sent from pyicqt, normally. But Kopete receive russian letters from pyicqt jabber transport as latin-1 (ISO-8859-1) like this: Íà äàííûé ìîìåíò ó íàñ îòêðûòî äâà îôèñà â Ìîñêâå Original text is: На данный момент у нас открыто два офиса в Москве Changing the default and the user encoding force to "Windows-1251 Cyrillic" or "UTF-8" and other variants clients don't help. Messages from other ICQ users receives normally. Messages from kopete to pyicqt with russian letters shows normally in pyicqt clients. As the jabber client I use psi, but I try to change the clients, but this doesn't solve the problem.
Bug still here when I try to send message from Kopete to Kopete. Steps to reproduce: 1. Create an jabber account on Kopete 2. Add a pyicqt jabber transport with some icq number (for example 111) 3. Add a direct icq account with another icq number (for example 222) 4. Change the default encoding in icq account to "Windows-1251 Cyrillic" 5. Go online on both accounts 5. Send the message from icq 111 to icq 222 with russian letters (for example - "Тест"): the letters receives wrong (we see "Òåñò" instead of "Тест") Delivering a russian letters from icq 222 to icq 111 was good, without problems. To see that it is a kopete problem we can try to setup an icq 222 on Pidgin account. With default encoding it receives "Òåñò" from icq 111 on Kopete client, but if we change default encoding to windows-1251, the message receives normally, like "Тест".
I can confirm this. Though, for me Kopete managed to encode messages in right encoding _when my correspondent wasn't authorized_. I deleted him fro my Contac list, then he deleted me, then we added together and we had all the encodings work properly, but my friend asked me to grant him authorization, since i was in grey for him. And as soon as i granted one - Kopete lost it's ability to transcode messages. He uses LIcq v 1.3.6
Eduard IMHO Licq is broken, because I've tried Licq <-> ICQ 6 and it's broken too. Kopete <-> ICQ 6 works fine. Murz: could you sometime join the Kopete channel on freenode.net and ping kedge (me). I would like to reproduce this bug with you and hopefully fix it as I can't find how to add pyicqt.
Wrong encoding from Kopete fixed in lastest version of pyicqt (0.8.1) by forcing the UTF-8 encoding: Try send messages in UTF-8 (supported by PyICQt 0.8.1): Select value "Always when it's possible" in option "Settings > Message settings > utf-8 messages sending mode" (Ad-Hoc) More info here: http://code.google.com/p/pyicqt/issues/detail?id=144&can=1&sort=-id But I think that this problem is in Kopete because other ICQ clients receives messages with older pyicqt normally. Kopete must set the encoding of non-utf8 messages to setted in Kopete settings but i think it sets the ISO-8859-1 instead of windows-1251. Roman Jarosz, which server I need to join on freenode.net? there are more than one servers: http://freenode.net/irc_servers.shtml We can talk by Jabber, my Jabber id is murznn@gmail.com
SVN commit 901619 by rjarosz: Fix bug 175566 Wrong russian encoding (windows-1251) in incoming messages Looks like charset 0x0003 is system encoding. BUG: 175566 M +1 -5 messagereceivertask.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=901619
SVN commit 901622 by rjarosz: Backport fix for bug 175566 Wrong russian encoding (windows-1251) in incoming messages CCBUG: 175566 M +1 -5 messagereceivertask.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=901622