Bug 101273

Summary: German umlauts not displayed correctly with ICQ (and possibly others?)
Product: [Unmaintained] kopete Reporter: Sebastian Ley <ley>
Component: ICQ and AIM PluginsAssignee: Kopete Developers <kopete-bugs-null>
Status: RESOLVED WORKSFORME    
Severity: normal    
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Debian testing   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Sebastian Ley 2005-03-10 23:52:17 UTC
Version:            (using KDE KDE 3.3.2)
Installed from:    Debian testing/unstable Packages
OS:                Linux

After switching to a UTF8 locale (de_DE.UTF-8) german umlauts in messages I receive over ICQ appear as chinese characters. This does not happen with all my contacts though.
Additionally the character after the umlaut is not dispalyed as well, so it seems the umlaut and the following chatacter are interpreted as two-byte unicode character.

The contacts I tested that with used miranda and licq.
Comment 1 Thiago Macieira 2005-03-11 03:23:56 UTC
Sorry, the protocol has been rewritten for Kopete 0.10. There's no plan on releasing bugfixes for 0.9.

Can you retest with Kopete 0.10 (from KDE 3.4.0) and report if you still have this issue?

I am using an UTF-8 locale and Kopete 0.10 works fine for me.
Comment 2 Sebastian Ley 2005-03-11 05:18:08 UTC
Ah yes. Well I am too lazy to compile myself now, and since 3.4 is pretty near, I will wait for that. Thanks!
Comment 3 Gandalf Sievers 2007-02-14 21:35:22 UTC
I expierence the same problem, I use Kopete 0.12.3 from KDE 3.5.5.
Comment 4 Oleg Girko 2007-02-15 00:49:03 UTC
Please ensure that you've selected correct default encoding for your account and encoding for your contact (if you communicate with this particular user using encoding different from default encoding for your account). These settings affect only offline messages and other stuff (like user info), which is encoded using user-specific 8-bit encoding in ICQ protocol. Official ICQ5 Windows client uses "Encoding for legacy non-Unicode applications" Windows setting for this, so don't select UTF-8 as encoding. For example, for Western European languages use Windows-1252 encoding.