[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#394080: marked as done (Kopete does not display non-ascii characters)



Your message dated Sun, 30 Mar 2008 10:09:58 -0400
with message-id <9f694b820803300709k4472f1aapcc5a7cc64cee22e1@mail.gmail.com>
and subject line Closing Debian bug 394080
has caused the Debian Bug report #394080,
regarding Kopete does not display non-ascii characters
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
394080: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=394080
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: kopete
Version: 3.5.5-1
Tags: l10n

Similar to the older bug #267749, my kopete has a problem with non-ascii
characters (at least) in ICQ messages, especially the german umlauts.
They are not displayed as a chinese sign but just as a white space.
Sometimes however the following (probably ascii) character was also
omitted, which looks again as what Sebastian reported in #267749.

The bug does not occur with everyone of my contacts. At first I thought
that only Trillian users were affected, but later I also found Miranda
and even Kopete users which couldn't send umlauts to me.

As the problem first occured a couple of weeks ago, I decided to try an
older version of Kopete. Right now I run 3.5.4-2 from testing which does
not have that problem.

Maybe the following information will help tracking the problem down:
When displaying old chats (recorded with the buggy version 3.5.5-1) with
the working 3.5.4-2, I get the following message in the chat window:

"Kopete encountered the following error while parsing a message:
Message could not be parsed. This is likely due to an encoding problem.
Please ensure you have selected the correct encoding for this contact."

Meanwhile the following errors are displayed in the system console:

Entity: line 14: parser error : Input is not proper UTF-8, indicate
encoding !
Bytes: 0xE4 0x74 0x74 0x65
#aaaa7f" ><![CDATA[<span style="color:#aaaa7f" title="19.10.2006
11:30:40">was h

       ^
Entity: line 14: parser error : Input is not proper UTF-8, indicate
encoding !
Bytes: 0xC4 0xD6 0xDC 0x20
lor="#aaaa7f" ><![CDATA[<span style="color:#aaaa7f" title="19.10.2006
11:30:53">

       ^
Entity: line 14: parser error : Input is not proper UTF-8, indicate
encoding !
Bytes: 0xA7 0x24 0x25 0x26
="#aaaa7f" ><![CDATA[<span style="color:#aaaa7f" title="19.10.2006
11:31:01">?!"

QDom: saving invalid character &#xdedc;, the document will not be
well-formed
QDom: saving invalid character &#xdbff;, the document will not be
well-formed
QDom: saving invalid character &#xdee4;, the document will not be
well-formed
QDom: saving invalid character &#xdefc;, the document will not be
well-formed
QDom: saving invalid character &#xdef6;, the document will not be
well-formed
QDom: saving invalid character &#xdea7;, the document will not be
well-formed




Before I downgraded kopete I tried a few other things for resolving this
issue, but I did not get anywhere:
- Setting /etc/locale.gen -> /usr/share/i18n/SUPPORTED and building
  a whole bunch of forreign locales
- Selecting a few different encodings for the users which I had problems
  with (did not make any difference).


To give you an idea about my system (Debian unstable):
Linux ulf 2.6.18-ulf15 #1 PREEMPT Sun Oct 8 11:08:55 CEST 2006 i686
libc Version: 2.3.6.ds1-6
The other KDE stuff is either 3.5.5a-2 or 3.5.5-1 (would a whole list of
packages versions of kopetes dependency tree be helpful?).

Locale: LANG=de_DE@euro, LC_CTYPE=de_DE@euro (charmap=ISO-8859-15)
(ignored: LC_ALL set to de_DE@euro)



Best wishes and Thank you in advance!

Ulf


--- End Message ---
--- Begin Message ---
Thanks,
I'm closing this bug report

Olivier


--- End Message ---

Reply to: