[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-bugs-dist
Subject: [Bug 72917] UTF8 and other cause XML parsing errors,
From: Robin Rosenberg <robin.rosenberg () dewire ! com>
Date: 2004-01-23 21:19:48
Message-ID: 20040123211948.24026.qmail () ktown ! kde ! org
[Download RAW message or body]
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
http://bugs.kde.org/show_bug.cgi?id=72917
------- Additional Comments From robin.rosenberg@dewire.com 2004-01-23 22:19 -------
Subject: Re: UTF8 and other cause XML parsing errors, only in IRC conversations
fredagen den 23 januari 2004 17.18 skrev Jason Keirstead:
> ------- Additional Comments From jason@keirstead.org 2004-01-23 17:18 -------
> Since these errors are infrequent, a little inefficientcy on them is OK. ...
They are AFAIC not uncommon. 80% of the messages I see are affeeted. A further 10% are
not because I have set the character set to isolatin1 for these users. Thus the chat looks like
kopete has flipped. It is better to say nothing than littering the chat log with warnings. This risk
of misinterpretations of the message due to the wrong charset is very small. Alternatve the
warning could be show the first time a user's message causes a problem, or it could be the
same line as the "message from".
Although I suggested it, I thiink "smart" heuristics here can outsmart itself.. On the other hand
a "per" topic or per server setting is the best approach. People tend to use the same character
set in IRC chats and they will get it right after one or two tries.
-- robin
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic