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

List:       kde-bugs-dist
Subject:    [Bug 84702] feature: fallback functionality,
From:       "S.Burmeister" <sven.burmeister () gmx ! net>
Date:       2004-10-21 21:16:07
Message-ID: 20041021211607.31128.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
        
http://bugs.kde.org/show_bug.cgi?id=84702        




------- Additional Comments From sven.burmeister gmx net  2004-10-21 23:16 -------
How do you define best we can do?

The better of two solutions, at least from my point of view, is the one that solves \
more issues. As you can see in my case and in most others the current functionality \
does not solve more problems than a two level fall back functionality.

Encoding set to Auto -> if charset header exists: use charset header -> if user set \
"fall back charset" exists, use it -> if not fall back to charset set by the system.

This definitely solves more issues than the current way and is hence better. Although \
I am not too familiar with C++ I think that another if-statement, checking whether \
the user has set a "fall back charset" should not be too hard to implement.

Can you point me to the the place in the code where kmail checks which charset to use \
for the email?


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