From kmail-devel  Mon Mar 27 11:58:29 2000
From: Sven Radej <sven () lisa ! exp ! univie ! ac ! at>
Date: Mon, 27 Mar 2000 11:58:29 +0000
To: kmail-devel
Subject: Re: new "kmail with PGP" error
X-MARC-Message: https://marc.info/?l=kmail-devel&m=95415978106245

On Mon, 27 Mar 2000, Stefan Taferner wrote:
(...)
>It's ported, by does not use QString yet. I am stuck at the point that I 
>would like to keep encodings out of kmail if possible, but I was not able
>to decide in which format the mails should be kept.

Hmm... do I get it right?
If someone uses special charsets (Latin 2, cyrilics, or two byte, Chinese,
whatever) it is encoded and mail always travels encoded. Shouldnīt KMMessage
class handle only technical stuff, like setting/getting headers,
adding/getting parts, etc? If so, it is only QCString job (or am I very wrong?).
Decoding should be done at very end, when displaying text, images, whatever,
right?

So we need "just" QCString  <-> (QString | Image | whatever) codec for sending
stuff to KHTML to display it. We donīt have it now - DwString isnīt capable of
anything like QString. So there is nothing to lose.

Please excuse me if all above is just a nonsense :-)

>The kmail2 (kdenonbeta) also does parsing a lot better and displays
>all the nested message parts (attachment in attachment) right.
>
>Even supports some variations of multipart/alternative, multipart/digest,
>email that is an attachment, etc.
(...)
>The said message class of libkmsg takes the good ideas of mimelib but uses
>Qt mechanisms, plus some extras.
>
>I don't comment on the parsing algorithm below. It is IMO nearly correct, some
>minor issues are there. But I think we should first replace the message 
>classes with something that does not make so much troubles.
Yes, this is a major issue.
-- 
Sven Radej      radej@kde.org
KDE developer   Visit http://www.kde.org