Bug 131425 - Meanwhile & Accents and other spanish used characters
Summary: Meanwhile & Accents and other spanish used characters
Status: CONFIRMED
Alias: None
Product: kopete
Classification: Applications
Component: Meanwhile plugin (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
: 146705 (view as bug list)
Depends on:
Blocks:
 
Reported: 2006-07-27 02:50 UTC by Martin Salgueiro
Modified: 2021-03-09 22:40 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Salgueiro 2006-07-27 02:50:46 UTC
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.
Comment 1 Martin Salgueiro 2006-07-27 02:52:15 UTC
Meanwhile package & version: meanwhile-1.0.2
Comment 2 Andras Georgy Bekes 2008-03-12 12:24:33 UTC
Here 100% reproducible with Kopete 0.12.7 and of course with not only Spanish characters.
Comment 3 Andrea Iacovitti 2008-11-17 10:04:51 UTC
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
Comment 4 kt 2008-12-26 18:56:08 UTC
*** This bug has been confirmed by popular vote. ***
Comment 5 Andrea Iacovitti 2009-01-19 13:53:14 UTC
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;
Comment 6 Rex Dieter 2009-08-14 18:05:50 UTC
*** Bug 146705 has been marked as a duplicate of this bug. ***
Comment 7 Andras Georgy Bekes 2009-10-26 17:43:13 UTC
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.
Comment 8 Andras Georgy Bekes 2010-02-15 10:58:17 UTC
I don't seem to have this problem any more.
Please close the bug if it was really fixed.
Comment 9 Roland Tapken 2014-12-10 15:47:50 UTC
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.
Comment 10 Justin Zobel 2021-03-09 22:40:47 UTC
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.