Bug 93057

Summary:	kopete icq message display problem with Russian messages
Product:	[Unmaintained] kopete	Reporter:	Max Belushkin <m.belushkin>
Component:	ICQ and AIM Plugins	Assignee:	Kopete Developers <kopete-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	billy
Priority:	NOR
Version First Reported In:	0.9.0
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Max Belushkin 2004-11-10 22:06:59 UTC

Version:           0.9.0 (using KDE KDE 3.3.0)
Installed from:    SuSE RPMs
Compiler:          gcc version 3.3.4 (pre 3.3.5 20040809) 
OS:                Linux

Migrated from 0.8 to 0.9 today (configs untouched), and realized that messages sent in Russian no longer get displayed correctly. Played around with Message encoding (in user properties) to no avail - messages are displayed in "Latin" charset with all those tildes above the letters, and not in Cyrillic.
Jabber is fine, ICQ isn't, but was fine with 0.8 before the migration.
P.S.: At some point a message displayed in Chinese hieoroglyphs, but that's as close as I got to getting Cyrillic :P

Comment 1 Max Belushkin 2004-11-11 10:53:30 UTC

Strangely enough, when I copy the incorrectly displayed text, paste it into the message window and send it back, the original sender receives normal text as he sent it. So I'm assuming this is some kind of a display problem. Messages originally typed by me in Russian and sent get shown correctly (and transferred correctly).

Comment 2 Richard Smith 2004-11-12 13:48:24 UTC

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

Comment 3 Max Belushkin 2004-11-13 10:22:19 UTC

Apparently, when the other side is also using Kopete (though, a 0.8.x version, haven't had a chance to test with a 0.9), encoding is fine. With GAIM (1.0.0, on Windows) on the other side, things also work out fine. When it's Miranda or ICQ, it doesn't work :(

Comment 4 Max Belushkin 2004-11-13 13:59:51 UTC

After a bit of digging around, I'm assuming this is the drawback of the protocol which doesn't allow to determine precisely whether the other side is using unicode or not.
Why isn't there a "UTF-8" option in User information->Encoding? Is there any big reason not to add it there, and force it to override any guessing?
I'm not sure this is the correct solution, if not - please correct me...

Comment 5 Max Belushkin 2004-11-26 14:06:46 UTC

Putting the CP-1251 encoding on Licq works with those people Kopete refuses to. Can anyone tell me why? Is Kopete ignoring the encoding I set or something?

Comment 6 Matt Rogers 2004-12-17 06:27:06 UTC


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

Comment 7 Artemio 2005-08-17 23:09:01 UTC

I am using Kopete 0.10.3 and this bug is there. I cannot read anything from my friends who "still use this crappy Microsith OS" ;-) My locale is UTF-8, and they send in CP-1251, and yes in Licq I can set what encoding to use. How can this be done in Kopete?