[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kopete-devel
Subject:    [Kopete-devel] [Bug 72917] UTF8 and other cause XML parsing errors,
From:       Jason Keirstead <jason () keirstead ! org>
Date:       2004-01-23 12:36:41
Message-ID: 20040123123641.26079.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
      
http://bugs.kde.org/show_bug.cgi?id=72917      




------- Additional Comments From jason@keirstead.org  2004-01-23 13:36 -------
A few points:

> Furthermore the user should be given a hint. Especially since XML is used in >the \
> IRC protocol.m The error message says "internal error", a phrase typically >meaning \
> "oops, programmer forgot to check something"

Kopete uses XML for all messages, on all protocols. A string can either be parsed as \
UTF 8, or it can't. If the string is not parseable (because there is no way to figure \
out the right codec), it can't be displayed in the XML document at all.

You can see themin network debug and stull like that because they don't have this \
restriction.

> It is not reasonable to have to change the character set for every contact in >IRC \
> in forum with 200 connected users, especially since I cannot see who wrote >what I \
> couldn't see. I've just tried in a chat with 30 users, and got >exhausted after \
> setting the character set for 10 users. The only hint with

Heh, this might be your largest problem. Setting the character set for all these \
people won't do anything anyways.

You need to sett he character set for the CHANNEL you are in. Right click on the \
CHANNEL. Or use the IRC menu in the window.

You only need to set the character set for a user if you are in a one on one chat \
with them and they are not using UTF-8.

> Well, right now I'm switching to History mode to see the "error-giving" 
> messages. It seems that the logs are already parsed, but somehow distorted.

This is the same problem. The history plugin will store messages correctly only if \
the codec was set correctly originally.

-------------

The biggest probelm you are having is that *all* communications on this server is not \
in UTF-8. You need an "account default" codec that applies to all contacts on the \
server, and communication with the server itself.

This was a requested feature, and it will be in the next release. It did not go into \
this release due to string and fearure freeze. \
_______________________________________________ Kopete-devel mailing list
Kopete-devel@kde.org
https://mail.kde.org/mailman/listinfo/kopete-devel


[prev in list] [next in list] [prev in thread] [next in thread]