[Kde-pim] decodeRFC2047String
Thomas McGuire
mcguire at kde.org
Sun Aug 23 14:40:26 BST 2009
Hi,
On Sunday 23 August 2009 00:03:30 you wrote:
> On Saturday 22 August 2009 5:26:25 pm Martin Koller wrote:
> > tying to fix a drag'n drop bug from a mail URL into a AddresseeLineEdit
> > (e.g. drop a mailto url with an umlaut to the identity dialog in
> > kmail/advanced tab/reply to or BCC field - same problem as bug 138725)
> > I wanted to use a decodeRFC2047String method.
> > But there are some of them ... :-(
> >
> > There is one in KMime, and one in KIMAP.
> > Which is the preferred one ? Why are there 2 at all ?
> > (kmail uses the one from KMime)
> >
> > Also, the latter in KIMAP seems to have a bug: when I drag/drop a mailto
> > url with an umlaut in it, e.g. "Götz" <goetz at gmail.com>
> > KIMAP's decode function snippes the Götz and returns "" <goetz at gmail.com>
> >
> > I want to apply the attached patch.
>
> You should also read bug
> [Bug 189139] New: decodeRFC2047String() doesn't parse stuff correctly
>
> Which indicates yet-another RFC2047 decoder in kdelibs.
>
> We should make sure the version in kdelibs works and use that one.
The kdelibs one says "Note: a more rubust[sic!] version of this function is
included in kdepimlibs/libkmime[sic!]", so I guess it is not ready for the
job.
If the kdepimlibs version doesn't have dependencies, it could be moved to
kdelibs, and KMime should use the kdelibs version then.
In any case, KIMAP should use the KMime one.
Regards,
Thomas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-pim/attachments/20090823/0aa3db17/attachment.sig>
-------------- next part --------------
_______________________________________________
KDE PIM mailing list kde-pim at kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/
More information about the kde-pim
mailing list