Bug 257954

Summary:	Wrong character set to display message content
Product:	[Applications] kmail2	Reporter:	Gael Beaudoin <gaboo>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	adrian, aspotashev
Priority:	NOR
Version:	2.0.90
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	wrongly displayed message other screenshot

Description Gael Beaudoin 2010-11-26 11:18:49 UTC

Created attachment 53753 [details]
wrongly displayed message

Version:           2.0 beta1 (using KDE 4.5.80) 
OS:                Linux

A message is displayed using the wrong character set and so some of them are not correctly displayed. See attached screeshot.

Reproducible: Always



Expected Results:  
Correctly displayed characters

Some headers and content :

Subject: =?UTF-8?Q?[FrAndroid_-_Android]_Nouveau_commentaire_pour:_Le_HTC_Desire_Z?=  =?UTF-8?Q?_disponible_=C3=A0_la_vente?=
Date: Fri, 26 Nov 2010 10:03:37 +0000
From: =?UTF-8?Q?FrAndroid_-_LA_communaut=C3=A9_francophone_Android=2C_Nexus_One?= <noreply@frandroid.com>
Message-ID: <9353e448ecd783ef23f7dd951c3fd571@www.frandroid.com>
X-Priority: 3
X-Mailer: PHPMailer (phpmailer.sourceforge.net) [version 2.0.4]
MIME-Version: 1.0
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset="UTF-8"

Un nouveau commentaire a été posté "Le HTC Desire Z disponible Ã  la vente". 
http://www.frandroid.com/49381/le-htc-desire-z-disponible-a-la-vente/

Comment 1 Gael Beaudoin 2010-11-26 11:19:16 UTC

Note : those were ok on kmail 1.x

Comment 2 Andrei Nistor 2010-12-01 17:49:31 UTC

Created attachment 53945 [details]
other screenshot

This might be the same bug, some characters look odd on that email too, but it is readable.

Comment 3 Adrián Chaves (Gallaecio) 2012-11-25 18:00:40 UTC

I have no problem reading UTF-8 characters. Isn’t it possible that the error is in the email sent, that has headers indicating the text is UTF-8 when it is actually using a different encoding?

Anyway, any steps to reproduce the issue?

Comment 4 Denis Kurz 2016-09-24 18:21:00 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 5 Denis Kurz 2017-01-07 22:40:34 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.