Bug 64326 - Kopete can't deal with different charsets in AIM and ICQ
Summary: Kopete can't deal with different charsets in AIM and ICQ
Status: RESOLVED FIXED
Alias: None
Product: kopete
Classification: Applications
Component: ICQ and AIM Plugins (show other bugs)
Version: 0.7
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-09-15 18:54 UTC by Matias Fernandez
Modified: 2003-10-24 21:39 UTC (History)
1 user (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 Matias Fernandez 2003-09-15 18:54:22 UTC
Version:           0.7 (using KDE KDE 3.1.3)
Installed from:    Debian testing/unstable Packages
Compiler:          gcc 3.3 
OS:          Linux

There appears to be a bug in kopete 0.7 all versions.
A system running locale de_DE.UTF8. that system got a message from a guy running koptete under de_DE.ISO8859-1 with german umlauts in it.
I'm used to incorrect characters due to the different locale but in kopete I simply get nothing. The whole text is listed in the log file and I also get that popup message, but the chat windows just shows nothing.
Comment 1 Matias Fernandez 2003-09-15 18:56:24 UTC
This is the original report:
 (12:24:51) Michael says: 
    There appears to be a bug in kopete 0.7 all versions. My systems runs under
locale de_DE.UTF8. Now I just got a message from a guy running koptete under
de_DE.ISO8859-1 with german umlauts in it. I'm used to incorrect characters due
to the different locale but in kopete I simply get nothing. The whole text is
listed in the log file and I also get that popup message, but the chat windows
just shows nothing.
 (12:25:18) radix says: 
    ohh damn!
 (12:25:32) radix says: 
    ok, I'll report it to kopete's bts
 (12:28:33) Michael says: 
    thx
Comment 2 Stefan Gehn 2003-09-15 19:16:57 UTC
Could you be a bit more precise, the protocol used matters A LOT! 
Also the bug summary is really undescriptive. 
Comment 3 Martijn Klingens 2003-09-15 23:52:05 UTC
Subject: Re: [Kopete-devel]   possible bug in all 0.7 versions

On Monday 15 September 2003 19:16, Stefan Gehn wrote:
> Could you be a bit more precise, the protocol used matters A LOT!
> Also the bug summary is really undescriptive.

Not only that, but KDE (and as such Kopete) ignores the LANG, LC_... and other 
locale environment variables anyway.

Comment 4 Matias Fernandez 2003-09-16 00:06:54 UTC
Subject: Re:  possible bug in all 0.7 versions

El lun, 15-09-2003 a las 17:52, Martijn Klingens escribi
Comment 5 Michael Meskes 2003-09-16 07:28:17 UTC
I tried with AIM and ICQ, both show the same behaviour. I have no idea which 
locale information is used by KDE but everything on my system runs in unicode, 
set in /etc/environment. This seems to be the only difference. 
Comment 6 Martijn Klingens 2003-09-16 11:35:50 UTC
Subject: Re: [Kopete-devel]   possible bug in all 0.7 versions

On Tuesday 16 September 2003 07:28, Michael Meskes wrote:
> I tried with AIM and ICQ, both show the same behaviour. I have no
> idea which locale information is used by KDE but everything on my system
> runs in unicode, set in /etc/environment. This seems to be the only
> difference.

The QString class used for display has been in unicode since KDE 2.0. It's not 
even configurable to something else than unicode...

Obviously when communicating with the 'outside world' (opening files, starting 
apps through a pipe, socket i/o) we need some conversion, so if things go 
wrong the ONLY possible cause is some conversion missing somewhere.

Depending on the code that can be hard to find though. We'd need an exact 
description of which incoming messages (type, protocol, ...) are wrongly 
interpreted. Even then we're at the mercy of the remote end or the protocol 
specification to make it clear what encoding the data actually is on, or we 
end up with unreliable guesswork.

Comment 7 Stefan Gehn 2003-10-19 18:31:38 UTC
handling of different charsets was added to Kopete CVS some time ago, it'll appear in Kopete 0.8, maybe not 100% perfect but a lot better than now and fixing things like that.
In case of special cases where it still fails I need precise information about the client(s) involved, please open a new bug in this case instead of reopening this rather general bugreport.
Comment 8 Matt Rogers 2003-10-24 21:39:14 UTC
*** Bug 66517 has been marked as a duplicate of this bug. ***