[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 13:17:10
Message-ID: 20040123131710.16022.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 14:17 -------
> I ran etherape on the connection (see attached file). It contains not XML \
> >whatsoever. The conclusion is that kopete internally creates invalid XML \
> > >documents that were not there to start with. 

As I said above. Etherrape and these other things don't use XML. They don't have to \
care. When you have an XML document, you *have* to specify the encoding it is in. \
It's a simple fact. If you  don't specify the right encoding a parsing error occurs.

We used to be able to somewhat reliably auto-detect the encoding, however QT releases \
since 3.1 have made this not possible any longer.

> I did that first, so I expeted the channel topic to be visible. Not! 

Yes, if what you are referring to is things like channel topics etc, these will be \
unreadable until we have an encoding setting for the server itself. I hope to have \
the code to do this done by next week, and it will be in CVS as soon as it's opened. \
_______________________________________________ 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]