Bug 70639

Summary:	Messages written in another character set are not shown / shown correctly
Product:	[Unmaintained] kopete	Reporter:	timo.jyrinki
Component:	general	Assignee:	Kopete Developers <kopete-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	normal
Priority:	NOR
Version First Reported In:	0.7.3
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description timo.jyrinki 2003-12-16 21:28:56 UTC

Version:           0.7.3 (using KDE KDE 3.1.4)
Installed from:    SuSE RPMs

I'm running my system wholely in UTF-8 (file system, LANG-settings etc.). When a friend of mine sends me a ISO-LATIN-1 -coded message to my Kopete (via ICQ), which contains non-ascii characters, the message is not shown at all in the chat. It's shown only in the history dialog, but of course if some of the messages come through (those that are purely ascii) one doesn't go looking into history.

Also, the non-ascii characters are shown incorrectly, ie. there's no conversion done. I have to manually set LANG to some latin character set before starting Kopete to be able to communicate with him properly.

Comment 1 Matt Rogers 2003-12-17 00:53:22 UTC

Could you please test with the 0.8 Beta and report back? There have been some encoding fixes made in that release.

Comment 2 timo.jyrinki 2003-12-17 10:52:10 UTC

Doesn't work with 0.8 Beta, either. This time, instead of nothing, I get "An internal Kopete error occurred while parsing a message: XML document could not be parsed!", when receiving a message with non-ascii chars. And as before, the entry does show in history (with wrong letters but shown anyway). We're Finnish so we have just a with dots and o with dots that cause this, so the messages are still understandable in the history as the garbled letters are either ä or ö.

Comment 3 Rui Malheiro 2003-12-17 15:06:34 UTC

Isn't this another instance of [Bug 67727]? http://bugs.kde.org/show_bug.cgi?id=67727

Anyway, as a workaround, you can try specifying your friend's encoding on his ICQ Contact Information (eg: set to "ISO-8859-1" instead of "Automatic").

Comment 4 Matt Rogers 2003-12-19 18:34:44 UTC


*** This bug has been marked as a duplicate of 67727 ***