Bug 105300 - KMAIL doesn't decode properly a UTF-8 subject
Summary: KMAIL doesn't decode properly a UTF-8 subject
Status: RESOLVED WORKSFORME
Alias: None
Product: kmail
Classification: Unmaintained
Component: mime (show other bugs)
Version: unspecified
Platform: Mandrake RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-05-08 18:36 UTC by Moshe Caspi
Modified: 2009-08-24 22:15 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Moshe Caspi 2005-05-08 18:36:01 UTC 
Version:            (using KDE KDE 3.3.2)
Installed from:    Mandrake RPMs
OS:                Linux

KMAIL doesn't decode properly this UTF-8 subject. All the other fields are fine but not the subject. What I see in the subject field is exactly what is written in the subject bellow.

From: =?UTF-8?Q?=73=68=61=68=61=66=20=70=69=6C=6F=76=69=63=68?=
 
Subject:
 =?UTF-8?Q?=52=65=3A=20=52=45=3A=20=D7=9E=D7=94=20=D7=99=D7=A9=D7=A8=D7=90=D7=9C=20=D7=9B=D7=A1=D7=A4=D7=99=20=28=D7=A2=D7=99=D7=98=D7=95=D7=A8=20=D7=94=D7=9E=D7=95=D7=A4=D7=AA=29=20=D7=90=D7=95=D7=9E=D7=A8=20=D7=A9=D7=A9=D7=9E=D7=A2=20=D7=9E=D7=91=D7=A0=D7=A6=D7=99=20=28=D7=A6=D7=9C=22=D7=A9=20=D7=A8=D7=9E=D7=98=D7=9B=22=D7=9C=29=20=D7=9C=D7=9C=D7=90=20=D7=90=D7=A1=D7=9E=D7=9B=D7=AA=D7=90=D7=95=D7=AA=20=21?=
Comment 1 Moshe Caspi 2005-05-08 18:39:00 UTC 
Subject:
 =?UTF-8?Q?=52=65=3A=20=52=45=3A=20=D7=9E=D7=94=20=D7=

To: =?UTF-8?Q?=59=6F=73=73=69=20=42=6C=75=6D=20=48=61=6C=65=76=69?=
 ,
 =?UTF-8?Q?=42=65=6E=7A=69=65?= ,
 =?UTF-8?Q?=48=65=7A=79=44=20=47=6C=6F=62=61=6C=2D=52=65=70=6F=72=74?=
Comment 2 Thiago Macieira 2005-05-08 18:41:51 UTC 
Confirmed for KMail 1.8.
Comment 3 Moshe Caspi 2005-05-20 15:37:37 UTC 
It looks like the problem depends on the length of subject. If I get this subject I can read it.

=?UTF-8?Q?=52=65=3A=20=D7=9C=D7=A0=D7=A1=D7=97=20=D7=90=D7=AA=20=D7=94=D7=9E=D7
=94=D7=A4=D7=9B=D7=94?=

But if a get a subject which is very long (and I don't understand why) like this from the same provider and user, all I see is the code itself.

 =?UTF-8?Q?=52=65=3A=20=D7=93=22=D7=A8=20=D7=9E=D7=99=D7=9C=D7=A9=D7=98=D7=99=D7=99=D7=9F=3A=20=D7=A2=D7=95=
D7=A4=D7=A8=20=D7=A9=D7=9C=D7=95=D7=9D=2C=20=D7=90=D7=A0=D7=99=20=D7=99=D7=9B=
D7=95=D7=9C=20=D7=9C=D7=94=D7=AA=D7=99=D7=97=D7=A1=20=D7=A8=D7=A7=20=D7=9C=D7=
9E=D7=94=20=D7=A9=D7=90=D7=91=D7=99=D7=9A=20=D7=90=D7=9E=D7=A8=20=D7=91=D7=93=
D7=99=D7=95=D7=9F=20=D7=91=D7=98=D7=9C=D7=95=D7=95=D7=99=D7=96=D7=99=D7=94=2C?=
Comment 4 Moshe Caspi 2005-05-20 16:22:13 UTC 
Small change:

It looks like the problem depends on the length of subject. If I get this subject I can read it.

=?UTF-8?Q?=52=65=3A=20=D7=9C=D7=A0=D7=A1=D7=97=20=D7=90=D7=AA=20=D7=94=D7=9E=D7
=94=D7=A4=D7=9B=D7=94?=

But if a get a subject which is very long (and I don't understand why) like this from the same provider and user, all I see is the code itself.

=?UTF-8?Q?=52=65=3A=20=D7=93=22=D7=A8=20=D7=9E=D7=99=D7=9C=D7=A9=D7=98=D7=99=
D7=99=D7=9F=3A=20=D7=A2=D7=95=
D7=A4=D7=A8=20=D7=A9=D7=9C=D7=95=D7=9D=2C=20=D7=90=D7=A0=D7=99=20=D7=99=D7=9B=
D7=95=D7=9C=20=D7=9C=D7=94=D7=AA=D7=99=D7=97=D7=A1=20=D7=A8=D7=A7=20=D7=9C=D7=
9E=D7=94=20=D7=A9=D7=90=D7=91=D7=99=D7=9A=20=D7=90=D7=9E=D7=A8=20=D7=91=D7=93=
D7=99=D7=95=D7=9F=20=D7=91=D7=98=D7=9C=D7=95=D7=95=D7=99=D7=96=D7=99=D7=94=2C?=
Comment 5 Moshe Caspi 2005-06-10 08:11:10 UTC 
Same problem here:


From: XXXXXX@gmail.com>
Subject: Updates June10 עדכוני
 המטה המשותף
To: XXXXXXX
Message-id: <6900851bf64a228c646a724b2a1cd3e2@winnetou.ymlpnet.com>
MIME-version: 1.0
Content-type: text/html;
  charset=iso-8859-1
Content-transfer-encoding: 8BIT
X-YMLPcode: matelist+68+1363


<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">

<meta http-equiv="Content-Type" content="text/html; charset=windows-1255">
Comment 6 Marc Mutz 2005-06-10 08:47:12 UTC 
That very long subject, is it in one line, or more than one?
Can you maybe attach the mail for which the decoding doesn't work properly (not the last one youposted, that's just HTML in the subject and that's nothing we can do about, but one of the =?UTF-8?Q?... ones) to the bug report?

Thanks.
Comment 7 Martin Koller 2009-08-24 22:15:09 UTC 
The original report works with KDE 4.3.0.