Bug 79254 - kmail default encoding option
Summary: kmail default encoding option
Status: RESOLVED DUPLICATE of bug 84702
Alias: None
Product: kmail
Classification: Applications
Component: mime (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR wishlist
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-04-07 21:06 UTC by Gal Ben-Haim
Modified: 2007-09-14 12:17 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gal Ben-Haim 2004-04-07 21:06:22 UTC
Version:            (using KDE KDE 3.2.1)
Installed from:    Debian testing/unstable Packages
OS:          Linux

my system is on UTF-8, when a message with bad charset headers (usually happen alot with web mail), after changing to the right encoding from the menu kmail displays the message correctly except the subject which shows as rectangles, appearantly the encoding settings from the menu doesn't affect the subject line.

my temporary solution is to set the environment variable KDE_UTF8_FILENAMES=true and to run kmail with: env LANG=he_IL kmail
this runs kmail with the ISO8859-8 locale, thus making those subjects of the messages to display correctly..

I guess a pernament solution is to have a default encoding in kmail (like in mozilla-thunderbird) so messages with wrong headers or whatever will have their default..

I subitted this as a bugreport to debian BTS and I got some replies from more people who are experiencing this issue with dutch..
Comment 1 Achim Bohnet 2004-04-07 22:00:25 UTC
You'll find the debian bug report at:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=242520

After switching from en_US.ISO8859-1 to en_US.UTF-8 many msgs
contain boxes instead of glyphs.  I've checked some and all
had a missing charset entry in contents-type.  Handish fix
to set them to ISO8859-1 in encoding menu is possible but
cumbersome.

'We' at the institute use:

	LANG=en_US.UTF-8

And in kdesktopwizard:

	language: us english
	country:  Germany

Maybe??? a 'sensible' default for 'unknown/undefined' charset in incoming
mails may be the default encoding for current country would be a
good idea?   From the bug describtion it looks like this works also
for Gal Ben-Haim. 

Achim
Comment 2 Marcus Sundman 2004-04-14 15:13:44 UTC
"Configuration -> Composer -> Charset" has a nice charset system for outgoing mails. Why can't there be a similar thing for incoming mails?
Comment 3 Andreas Gungl 2004-04-14 16:42:37 UTC
On Wednesday 14 April 2004 15:13, Marcus Sundman wrote:
> "Configuration -> Composer -> Charset" has a nice charset system for
> outgoing mails. Why can't there be a similar thing for incoming mails?

View -> Set Encoding ?

Comment 4 Gal Ben-Haim 2004-04-14 16:47:38 UTC
as said before some message contain 'broken' charset headers, and their subject is displayed in the system's locale (UTF-8).. changing view/encodings affect the message body and not the subject..

there should be a 'default encoding' option for incoming emails, so those broken messages and actually any other message will be displayed in the right locale in the default.
Comment 5 Marcus Sundman 2004-04-15 13:42:12 UTC
> > "Configuration -> Composer -> Charset" has a nice charset system for 
> > outgoing mails. Why can't there be a similar thing for incoming mails? 
>
> View -> Set Encoding ?

Argh! NO! "View -> Set Encoding" overrides the encoding specified in the email header, instead of being a fallback. Of course there are those borderline cases where there is an encoding specified in the email header but it is wrong. For such messages it would probably be best to have a per-message override. However, in NO case is it OK to have a global override!

> there should be a 'default encoding' option for incoming emails, so those
> broken messages and actually any other message will be displayed in the
> right locale in the default.

Having just one fallback encoding/charset is clearly not good enough when you receive mails from more than one region. Instead KMail should auto-detect it as best it can (preferably while taking the LC_* and LANG values into account), and only as a very last resort fall back to a user-specified charset.
Comment 6 Ismail Donmez 2004-07-20 20:53:49 UTC
*** Bug 79639 has been marked as a duplicate of this bug. ***
Comment 7 S. Burmeister 2004-11-05 18:19:52 UTC
Maybe you want to have a look at bug 84702, which already had a patch that did not really solve the problem but at least was a start towards solving these issues.
Comment 8 Ingo Klöcker 2005-05-16 15:11:55 UTC
This wish is a duplicate of wish #84702 which has been implemented in the meantime (KMail 1.8).

*** This bug has been marked as a duplicate of 84702 ***
Comment 9 Aivaras 2005-08-31 12:20:25 UTC
I have same problems. In message view panel encoding are incorrect, but in ViewSource same messages encoding are correct!