Version: 0.60.3 (using KDE 4.1.3) OS: Linux Installed from: Gentoo Packages I experiment this problem with the MSNProtocol, I haven't tested on other protocols. Sometimes, I receive messages but they are not displayed in the chat window (it only shows an empty line). These messages appear in the xml log file, but even in the history window, a blank line is displayed instead... They correctly appear in the notification popup. I suspect a strange character inside these kind of messages, perhaps related to custom emoticons. Attached is a xml log file with a message not displayed in the history window. If you open it with okteta you will see a strange sequence between "lanceurs" and "tout". This is a really annoying bug, I experiment it very often, so I have to switch to amsn... so any workaround is welcome.
Created attachment 28547 [details] a message not displayed by kopete
We have an all new plugin for MSN which might fix this issue. Please try KDE 4.2 Beta 1 and reopen this bug if you can reproduce it with the newer version.
Hello, This bug still occurs with kde 4.2.0!
Do you use OTR plugin?
Here is a message which contains some strange chars and are not displayed, even by the history window. I extracted it using python to show up special characters : <msgnick="luna" in="1" from="XXXX" time="31 21:56:15" >ouais mais il risque pas de rester des\xef\xbf\xbc</msg> So the sequence "\xef\xbf\xbc" seems responsible from the non-display of this message. It seems that it was originally a custom emoticon from the sender... And there is no way to disable them in the new version of kopete.
#4> the otr is installed, but I wasn't using it in this chat session.
If it's enabled in plugin configuration dialog than disable it and you should be ok
yes you are right the \xef\xbf\xbc is OBJECT REPLACEMENT CHARACTER it's the character which is put into text when img tag is converted to plain text.
it worked, thanks! Should I keep this bug open ? Or is this an intended behavior?
No it's bug, will be fixed soon. *** This bug has been marked as a duplicate of bug 182114 ***