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

List:       kde-commits
Subject:    Re: make_it_cool: kdenetwork/kmail
From:       Ingo =?utf-8?q?Kl=C3=B6cker?= <kloecker () kde ! org>
Date:       2003-01-21 23:08:28
[Download RAW message or body]


On Tuesday 21 January 2003 06:45, Don Sanders wrote:
> Changed QString to QCString in some places. (Mail is 7/8 bit and
> non-ascii is encoded, so it makes sense to encode the string being
> search for rather than decoding all the mails searched)

Non-ascii is encoded in many different ways. First there is the charset 
and then there is the content-transfer-encoding. Is the search string 
encoded with all possible charsets and ctes? How can this possibly work 
with base64 encoded messages (where always three characters are encoded 
together)? What about for example "=46rom" which is a valid 
quoted-printable encoded "From"? It's perfectly legal to encoded any 
ascii character as =XX. IMO at least the cte has be decoded for every 
message. Of course in this case still QCStrings can be used. But there 
is still the problem with the charsets.

I didn't have a look at the code. So my questions might not apply.

Regards,
Ingo


[Attachment #3 (application/pgp-signature)]

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