Summary: | An encoding menu in message window | ||
---|---|---|---|
Product: | [Unmaintained] kmail | Reporter: | Noam Raphael <noamraph> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | wishlist | CC: | bensberg |
Priority: | NOR | ||
Version: | 1.6.2 | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Noam Raphael
2004-12-13 16:46:38 UTC
Could this wish be applied to choosing between quoted-printable and base64 as well as the different charsets - I know that in most cases this is a choice that should be made automatically, but it would be a good idea to have a manual override in case of faulty mail clients at the other end. I view the fact that the encoding can only be set globally, rather than per message, as a usability bug. A "Normal" bug, not a "Wishlist" bug. It is my biggest annoyance with KMail, which I like more than any other mail client I've tried. Hasn't this bug long since been fixed? When hitting Enter on a message (in KMail 1.9.6), there's a Set Encoding submenu in the View menu. If this is not what's meant, then please explain what you mean with "open a message in a new window". I seem to remember that in earlier versions of KMail, the message window did not have File, View etc menus, only the "print, reply, delete" icon toolbar, and so the Set Encoding submenu was not accessible. However, this is now fixed in my version of KMail (1.9.5) In response to comment #3: Indeed, the bug as presented is mostly gone (and I'm with KMail 1.9.5). I would like the encoding set per message to be persistent (i.e. once I set the encoding for a message manually, I want it to always open with the encoding I specified), then I would consider it completely gone. Or do you think I should open a new bug for this? Yes, please file a new bug -- it keeps things clean. And close this one as fixed, since you now do have an encoding menu in the message window. :) *** Bug has been marked as fixed ***. |