[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kmail-devel
Subject:    [Bug 84702] feature: fallback functionality,
From:       "S.Burmeister" <sven.burmeister () gmx ! net>
Date:       2004-10-24 13:06:13
Message-ID: 20041024130613.28475.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
        
http://bugs.kde.org/show_bug.cgi?id=84702        




------- Additional Comments From sven.burmeister gmx net  2004-10-24 15:06 -------
> Sven, can you please send me an mbox of such a message to adam kde org
> (File -> save as), I have a patch for this I would like to test. It falls

Sure I can.

> back to the first of the list of preferred charsets as specified in
> Configure KMail -> Composer -> Charsets. I think we can reasonably assume
> this to be the users preferred encoding.

But the user's favorite character encoding is not the favorite encoding of the 
author one gets the email from.
I like utf-8, thus utf-8 is first in my encoding list. Windows users hardly 
use utf-8, so the emails I get are not in the encoding I like, hence, if I 
understood you correctly, your patch would fail for me.

First I assumed that Windows always uses the same encoding, i.e. windows-1252, 
which I think is not the case?
However, the reason for me thinking this would be the case was, that everytime 
I got an email that did not display correctly, the reason lay in the lack of 
an encoding-header and all I had to do was to switch to windows-1252. Hence I 
thought it would be very convenient for people like me to be able to tell 
kmail that it should switch automatically to e.g. windows-1252 in case there 
is no encoding-header, yet obey the header if it exists.
This way I get all those windows emails right, plus all emails that have an 
encoding-header, which amounts to almost 100% of correctly displayed emails, 
at least in my case.

The setting could be placed in the misc. section, next to a drop-down menu 
containing all available encodings. Maybe even default to windows-1252 if 
that really includes 90% of emails with no encoding-header.

With your patch all people who want to use the functionality would have to 
write their emails in windows-1252 (being top of the list), which I do not 
think is a good solution?

Thanks for considering the feature request!
_______________________________________________
KMail developers mailing list
KMail-devel@kde.org
https://mail.kde.org/mailman/listinfo/kmail-devel
[prev in list] [next in list] [prev in thread] [next in thread]