Bug 327416 - Subject isn't correctly shown in messageviewer cause to encoding
Summary: Subject isn't correctly shown in messageviewer cause to encoding
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: 4.11.2
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-11-10 15:46 UTC by Sandro Knauß
Modified: 2017-01-07 22:33 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Mail with a sebuject, that isn't displayed correctly everytime. (695 bytes, application/mbox)
2013-11-10 15:46 UTC, Sandro Knauß 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Sandro Knauß 2013-11-10 15:46:39 UTC 
Created attachment 83477 [details]
Mail with a sebuject, that isn't displayed correctly everytime.

I got a mail with a subject:
=?iso-8859-1?q?Erinnerung=3A_=3D=3Fiso-8859-1=3F?=
 =?iso-8859-1?q?Q=3F=3D22Syrien=5Fzwischen=5FAufstand=3D2C=5FB=3DFCrgerkri?=
 =?iso-8859-1?q?eg=5Fund=5FV=3DF6lkerm=3F=3Dord=3D=3Fiso-8859-1=3FQ=3F=3D2?=
 =?iso-8859-1?q?2=5F-=5FDonnerstag=5F=7C=5F14=2ENovember=5F2013=5F=7C=5F19?=
 =?iso-8859-1?q?=2E30=5F=7C=5FBuchladen=5F=3F=3D=22Rote_Stra=DFe=22?=

In messageview is is wrong decoded:
Erinnerung: =?iso-8859-1?Q?=22Syrien_zwischen_Aufstand=2C_B=FCrgerkrieg_und_V=F6lkerm?=ord=?iso-8859-1?Q?=22_-_Donnerstag_|_14.November_2013_|_19.30_|_Buchladen_?="Rote Straße"

In message list the Subject is correctly shown as:
Erinnerung: "Syrien zwischen Aufstand, Bürgerkrieg und Völkermord" - Donnerstag | 14.November 2013 | 19.30 | Buchladen "Rote Straße"

replying: the subject is correct decoded.
forward: the subject is NOT correctly decoded.
Comment 1 Laurent Montel 2013-11-10 17:59:06 UTC 
Will investigate it soon.
Comment 2 Denis Kurz 2016-09-24 18:12:33 UTC 
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.
Comment 3 Denis Kurz 2017-01-07 22:33:17 UTC 
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.