| Summary: | UTF-8 being mangled in outgoing messages | ||
|---|---|---|---|
| Product: | [Unmaintained] kopete | Reporter: | Dotan Cohen <kde-2011.08> |
| Component: | ICQ and AIM Plugins | Assignee: | Kopete Developers <kopete-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | kde |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Dotan Cohen
2008-01-02 19:54:37 UTC
I can reproduce this, will try to fix it. Btw. you should request authorization for that user and probably grant it if the user doesn't have your authorization already and when the user grants you the authorization then this problem should go away. This is also a problem for the AIM protocol in Kopete. I can receive messages with Unicode characters in them, but in messages I try to send, any characters outside of iso-8859-1 are replaced by question marks by the time the recipient receives them. Oddly, those characters appear correctly in my copy of my message. I know OSCAR supports UTF-8, so what's the trouble here, guys? Come on! Roman, authorizing did not solve the problem. The latest version of Pidgin won't even accept AIM messages from Kopete because Kopete doesn't set the message encoding properly. Pidgin says: "There was an error receiving this message. Either you and XXXXXX have different encodings selected, or XXXXXX has a buggy client." Matt this is bug in pidgin 2.4.0, it will be fixed in 2.4.1. We can't do anything about it. Dotan can you tell me which ICQ version the other user is using? Yes, he is using ICQ 6.1 in a Russiah Windows environment. His ICQ install is in English. He has no problem communicating in English, Hebrew, or Russian with any of his other contacts. He has about 20-30 other contacts, and communicates in those three languages on a regular basis. He does not know what encoding or codepage is, and he is certain that he never touched an encoding or codepage-related setting. It 'just works' for him, with the exception of communicating with me when I use Kopete. When I use Pidgin we communicate fine. SVN commit 789284 by rjarosz: Make text encoding more robust by using optimal encoding. Allow offline messages and all AIM messages (AIM doesn't sets the CAP_UTF8 anymore) to be UNICODE. Fix max size of a message. BUG: 159652 BUG: 154983 M +3 -4 aimcontactbase.cpp M +4 -8 icqcontactbase.cpp M +32 -0 liboscar/oscarmessage.cpp M +5 -0 liboscar/oscarmessage.h M +11 -3 liboscar/tasks/messagereceivertask.cpp M +1 -1 liboscar/tasks/profiletask.cpp M +14 -8 liboscar/tasks/sendmessagetask.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=789284 SVN commit 789289 by rjarosz: Backport commit 789284. Make text encoding more robust by using optimal encoding. Allow offline messages and all AIM messages (AIM doesn't sets the CAP_UTF8 anymore) to be UNICODE. Fix max size of a message. CCBUG: 159652 CCBUG: 154983 M +3 -4 aimcontactbase.cpp M +4 -8 icqcontactbase.cpp M +32 -0 liboscar/oscarmessage.cpp M +5 -0 liboscar/oscarmessage.h M +11 -3 liboscar/tasks/messagereceivertask.cpp M +1 -1 liboscar/tasks/profiletask.cpp M +14 -8 liboscar/tasks/sendmessagetask.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=789289 |