| Summary: | Kopete can't deal with different charsets in AIM and ICQ | ||
|---|---|---|---|
| Product: | [Unmaintained] kopete | Reporter: | Matias Fernandez <radix> |
| Component: | ICQ and AIM Plugins | Assignee: | Kopete Developers <kopete-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | meskes |
| Priority: | NOR | ||
| Version First Reported In: | 0.7 | ||
| Target Milestone: | --- | ||
| Platform: | Debian testing | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Matias Fernandez
2003-09-15 18:54:22 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
Could you be a bit more precise, the protocol used matters A LOT! Also the bug summary is really undescriptive. 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.
Subject: Re: possible bug in all 0.7 versions El lun, 15-09-2003 a las 17:52, Martijn Klingens escribi 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. 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.
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. |