kopete with meanwhile sametime protocol can't handle accents

Bug #206396 reported by aftertaf on 2008-03-25
4
Affects Status Importance Assigned to Milestone
Kopete
Unknown
Medium
kdenetwork (Ubuntu)
Low
Unassigned

Bug Description

Binary package hint: kopete

In all versions since feisty... I have the same behaviour.. in current kopete in hardy

I use kubuntu in english language, setup for use in France.
I have an azerty keyboard.

When I send messages to sametime contacts if i use an accent ( é, à, ç, è ) the whole message I sent is badly handled . . . the receiver only gets an empty line in his chat window.
And when someone sends me a message with an accent, i get @# type of characters instead of the letter with an accent...

Is it kopete, or the meanwhile wrapper for sametime?

how can I give you more information to help?

Version: 0.12.1 (using KDE KDE 3.5.2)
Installed from: Gentoo Packages
Compiler: 3.4.6 gcc version 3.4.6 (Gentoo 3.4.6-r1, ssp-3.4.5-1.0, pie-8.7.9)
OS: Linux

Problems sending and receiving messages with accents and other characters used in Spanish lenguage. When sending to a client using Sametime, the Sametime shows only an blank line. When receiving from a Sametime, Kopete shows weird characters (1 or more) in place of every accented character.

Meanwhile package & version: meanwhile-1.0.2

Here 100% reproducible with Kopete 0.12.7 and of course with not only Spanish characters.

Yuriy Kozlov (yuriy-kozlov) wrote :

Confirmed according to upstream bug.

Changed in kopete:
status: New → Confirmed
Changed in kopete:
status: Unknown → New

I have the same problem here (kopete 0.12.7 meanwhile 1.0.2), can someone point me on what part of code to look to help solve this bug ?

Thanks,
Andrea

*** This bug has been confirmed by popular vote. ***

Changed in kopete:
status: New → Confirmed

I applied the following patch on kopete (kde 3.5.10) and the problem with accented characters has gone.
It consists in converting messages on utf8 before send or display. I'm not expert, may be this is a "dirty" patch, but anyway it works for me.... upstream developers will know better than me if side effects are triggered...

Regards.
Andrea.

--- kdenetwork/kopete/protocols/meanwhile/meanwhilesession.cpp 2009-01-19 12:17:30.000000000 +0100
+++ kdenetwork/kopete/protocols/meanwhile/meanwhilesession.cpp 2009-01-19 12:18:01.000000000 +0100
@@ -351,7 +351,7 @@
         mwConversation_open(conv);

     } else if (!mwConversation_send(conv, mwImSend_PLAIN,
- message.plainBody().ascii())) {
+ message.plainBody().utf8())) {
         convdata->chat->appendMessage(message);
         convdata->chat->messageSucceeded();
     }
@@ -808,7 +808,7 @@
         for (it = convdata->queue->begin(); it != convdata->queue->end();
                 ++it) {
             mwConversation_send(conv, mwImSend_PLAIN,
- (*it).plainBody().ascii());
+ (*it).plainBody().utf8());
             convdata->chat->appendMessage(*it);
             convdata->chat->messageSucceeded();
         }
@@ -857,7 +857,7 @@
     case mwImSend_PLAIN:
         {
             Kopete::Message message(convdata->contact, account->myself(),
- QString((char *)msg), Kopete::Message::Inbound);
+ QString::fromUtf8((char *)msg), Kopete::Message::Inbound);
             convdata->chat->appendMessage(message);
         }
         break;

Changed in kdenetwork (Ubuntu):
status: Confirmed → Triaged
importance: Undecided → Low

*** Bug 146705 has been marked as a duplicate of this bug. ***

Did someone fix this problem?
I am using kopete 0.70.90 (KDE 4.3.1) with libmeanwhile1 1.0.2-3 and the problem does not seem to exist. The peer was using "sametime 8.1" client.

I don't seem to have this problem any more.
Please close the bug if it was really fixed.

Changed in kopete:
importance: Unknown → Medium

I have a similiar bug with german umlauts. I can receive messages containing umlauts (like ä, ö, ü...), but sent messages with one if these characters are not received by the Sametime client (not even a blank line). I think it might be a charset problem.

Changed in kopete:
status: Confirmed → Unknown
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.