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

List:       kde-core-devel
Subject:    Re: [Kde-pim] Fwd: Re: KDE 4.4.98 (4.4 RC3)
From:       argonel <argonel () gmail ! com>
Date:       2010-02-07 15:33:34
Message-ID: 28d9390d1002070733w574f647bn208c4d09100a1f30 () mail ! gmail ! com
[Download RAW message or body]

On Sun, Feb 7, 2010 at 3:58 AM, Thiago Macieira <thiago@kde.org> wrote:

>
> The protection has to happen somewhere. Technically, it's Konversation's
> fault
> for passing unfiltered network data into an API.
>
> But it could also be a QString issue, for allowing those invalid UTF-8
> strings
> to be converted to UTF-16 in the first place.
>
> Note that changing the D-Bus behaviour may likely introduce bugs in
> Glib-based
> applications, where conversions from UTF-8 do implement this check. (Which,
> in
> my opinion, is incomplete)
>
>
If you're referring to dbus's lack of checks for 0x1FFFE and so on, I found
that I was unable to create a QChar > 0xFFFF, so perhaps not checking those
is reasonable.

Regards, Eli

[Attachment #3 (text/html)]

<br><br><div class="gmail_quote">On Sun, Feb 7, 2010 at 3:58 AM, Thiago Macieira \
<span dir="ltr">&lt;<a href="mailto:thiago@kde.org">thiago@kde.org</a>&gt;</span> \
wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px \
#ccc solid;padding-left:1ex;"> <div class="im"><br>
</div>The protection has to happen somewhere. Technically, it&#39;s \
Konversation&#39;s fault<br> for passing unfiltered network data into an API.<br>
<br>
But it could also be a QString issue, for allowing those invalid UTF-8 strings<br>
to be converted to UTF-16 in the first place.<br>
<br>
Note that changing the D-Bus behaviour may likely introduce bugs in Glib-based<br>
applications, where conversions from UTF-8 do implement this check. (Which, in<br>
my opinion, is incomplete)<br>
<div><div></div><div class="h5"><br></div></div></blockquote><div><br></div><div>If \
you&#39;re referring to dbus&#39;s lack of checks for 0x1FFFE and so on, I found that \
I was unable to create a QChar &gt; 0xFFFF, so perhaps not checking those is \
reasonable.</div> <div><br></div><div>Regards, Eli</div></div>



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