[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:       Iori Yagami <yagami () netcabo ! pt>
Date:       2004-01-23 16:44:35
Message-ID: 20040123164435.28803.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 yagami@netcabo.pt  2004-01-23 17:44 -------
Subject: Re: [Kopete-devel]  UTF8 and other cause XML parsing errors, only in IRC conversations

Em Sexta, 23 de Janeiro de 2004 16:25, o Martijn Klingens escreveu:
> ------- Additional Comments From klingens@kde.org  2004-01-23 17:25 -------
> Subject: Re: [Kopete-devel]  UTF8 and other cause XML parsing errors, only
> in IRC conversations
>
> On Friday 23 January 2004 17:18, Jason Keirstead wrote:
> > We can display:
> >
> > WARNING: Kopete could not properly determine the encoding of the
> > following message:
> > Foobar message ?? foo.
>
> Ah, seems like a reasonable workaround.
>
> As for the encoding DETECTION, would using KStringHandler::isUtf8() before
> using QString::fromUtf8() help?
> _______________________________________________

if you can do that , than you probably can make a iso8859-15 to utf8 
conversion and then try to put it on xml right ?!

even if this isnt 100 % full proof , it it would fix 25 % of cases would be 
already good.

also , could the :
" WARNING: Kopete could not properly determine the encoding of the following 
message:
 Foobar message ?? foo." 

be like : WARNING ?? : "message" 

as to not take too much space on the screen ( i see this going to happen 
alot )
_______________________________________________
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]