Bug 142548

Summary:	kmail3: encoding detection problems [testcase]
Product:	[openSUSE] openSUSE 10.3	Reporter:	Martin Mrazik <mmrazik>
Component:	KDE	Assignee:	Will Stephenson <wstephenson>
Status:	RESOLVED WONTFIX	QA Contact:	E-mail List <qa-bugs>
Severity:	Minor
Priority:	P4 - Low
Version:	unspecified
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Bug Depends on:
Bug Blocks:	140732
Attachments:	screenshot of broken kmail encoding problematic mail mail causing the problem on my system

Description Martin Mrazik 2006-01-11 13:05:58 UTC

It seems there are som problems with the "auto" encoding in kmail.

Although I have this in the header of the mail, the encoding is broken (see the attached screenshot, the mail is really utf-8...):
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable

I have the same problem if I have mail with the following encoding:
Content-Type: text/plain;
  charset=ISO-8859-2

However If I go to menu View->Set Encoding and change the encoding from auto (default) to anything else and than back to auto it works correctly! E.i. all  my mails with west-european encoding are rendered correctly.

Comment 1 Martin Mrazik 2006-01-11 13:06:38 UTC

Created attachment 62875 [details]
screenshot of broken kmail encoding

Comment 2 Martin Mrazik 2006-01-11 13:08:32 UTC

if I close kmail then after next start again the same encoding problem, which can be solved with the same workaround.

Comment 3 Will Stephenson 2006-01-13 14:24:21 UTC

Please forward a mail with the header/encoding problem to me at wstephenson@suse.de  (NOT my novel.com l address, I don't want it to go through groupwise).

Comment 4 Martin Mrazik 2006-03-28 08:13:49 UTC

any news here?

Comment 5 Will Stephenson 2006-03-28 09:21:37 UTC

I couldn't reproduce the problem with the mail you forwarded, since it's inline utf-8 and you forwarded it with charset="iso-8859-1" in the header, the auto encoding setting picks 8859-1, which looks bad, then manually setting to utf-8 decodes the inline joke correctly, and reverting to auto goes back to the incorrect 8859-1 decoding.

What I want to see is the original mail you took a screenshot of - right click on the mail, select Save As.. and then send me the resulting file as an attachment - then I will have a mail with charset=utf-8 in the header, utf-8 in the body and hopefully an encoding probelm I can get my teeth into.

Comment 6 Martin Mrazik 2006-03-28 09:31:42 UTC

sorry for that. Please feel to free to contact me if you don't have enough info. I have this problem with other e-mails too (not only jokes ;)). It's quite annoying.

The e-mail is attached (actually its another e-mail, but the same problem).

Comment 7 Martin Mrazik 2006-03-28 09:33:23 UTC

Created attachment 75279 [details]
problematic mail

Comment 8 Will Stephenson 2006-03-28 10:20:35 UTC

That one works for me too (beta8)

Is your login using a non-utf-8 locale?  

What are the values of 'Fallback character encoding' and 'Override character encoding' in Configure Kmail->Appearance->Message Window?

Comment 9 Martin Mrazik 2006-03-28 10:57:08 UTC

hm...:
king:~:$ locale
LANG=en_US.UTF-8
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=

Fallback character encoding: "Western European (iso-8859-15)"
(strange)

Override character encoding: "Auto"

Comment 10 Will Stephenson 2006-03-28 18:21:21 UTC

Created attachment 75389 [details]
mail causing the problem on my system

This mail (utf8/utf8) triggers the bug for me.

Comment 11 Harald Mueller-Ney 2006-04-21 16:52:25 UTC

Any news on this? we are close to SLES 10 RC1

Comment 12 Stephan Kulow 2006-05-24 07:20:03 UTC

for later

Comment 13 Will Stephenson 2006-11-24 14:44:45 UTC

bumped again

Comment 14 Will Stephenson 2007-12-14 15:02:22 UTC

Reported to Kolab maintaintainers: https://intevation.de/roundup/kolab/issue2345, maybe they can fix it.

Comment 15 Thorsten Kukuk 2009-07-02 08:27:39 UTC

No progress since over three years, closing.