User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:22.214.171.124) Gecko/2008071615 Fedora/3.0.1-1.fc9 Firefox/3.0.1 Build Identifier: Since Thunderbird can handle more than one account, it is not desirable that "For messages that contain 8-bit characters, use 'qouted printable' MIME encoding" is the same for all accounts. It would make more sense to have per account. I therefore propose it is moved to Edit->"Composition & Addressing". See mock up. Reproducible: Always
IMO, zero point having that as an per account setting. In fact, it's questionable to have UI for it at all. (Only needed for testing, for real use it should die die die.)
I'm wondering how many SMTP servers are still out there which are unable to process 8-bit content transfer encoding. Thus, I agree with comment #2 that the relevance of this option for justifying a checkbox in the UI is somewhat questionable, especially given that the description and the implications of this option are probably not understood by a typical user. If you want to retain and move it, the Outgoing Server (SMTP) settings would be more appropriate than the settings of an individual account, as this is a limitation of the SMTP server connected to. But again, I don't really see the need for this effort for an option that likely may retire in the future...
Maybe we should make WONTFIX?
I would like to see the option gone as well. So I open a bug 'Remove "For messages that contain 8-bit..."' and close this one, or should this be changed to getting rid of the setting?
I will change it to Remove.
Confirming based on several supporting statements, no objections about changing the subject, no duplicate found.
OK, we can work on removing this from the prefs. Who wants it?
You can also ask this question the opposite way: Is there any good reason to keep the checkbox for this option? And if yes, does it have to be in the General tab of the Composition preferences?
(In reply to comment #9) I can not think of a good reason for keeping it. See Comment #2, Comment #3, and Comment #5
Tyler, I realize that the comments presented here are all in favor of removing the quoted-printable checkbox (and so am I). However, the fact that neither of us can't think of any reason to keep it doesn't imply that there is none, thus my comment #9 was intended to make sure that we don't miss anything. I'm working on a patch, should be straightforward.
Created attachment 333180 [details] [diff] [review] Proposed patch to remove the checkbox I can add a screen shot if desired, but the change is rather obvious.
Comment on attachment 333180 [details] [diff] [review] Proposed patch to remove the checkbox excellent! looks good to me
(In reply to comment #11) > Tyler, I realize that the comments presented here are all in favor of removing > the quoted-printable checkbox (and so am I). However, the fact that neither of > us can't think of any reason to keep it doesn't imply that there is none, thus > my comment #9 was intended to make sure that we don't miss anything. > > I'm working on a patch, should be straightforward. > I was just confirming that I could think of no reason to keep.
Thanks for the reviews, check-in/push for comm-central please.
Checked in, changeset id: 80:027edc78f0da
I see the fix.