2000120420 trunk NT4 Sp6a I have the default character encoding set in the prefs to ISO-8859-1 and Auto-detect set Japanese. Whenever I get a news message with no encoding set in the headers, it's rendered using one of the Japanese encoding.
I am confirming this bug since the phenomenon described by Gilles does occur. But I wonder if we should really fix this problem. In the current spec for this, we honor "Auto-detection" above the fallback encoding set in the Pref | Message Display. If you want to have correct display, you can check the "Apply the default to all messages..." in the Pref for Message Display. If this does not work, it would be a bug. One possibility we can think of is to place the default encoding higher than Auto-detection, however. CC'ing nhotta and others. Let's think about this a bit before deciding what to do.
Status: UNCONFIRMED → NEW
Ever confirmed: true
QA Contact: esther → momoi
>One possibility we can think of is to place the default >encoding higher than Auto-detection, however. No, it makes auto-detection useless. For better newsgroup support, it is planned to be targeted by folder level charset (bug 32714) feature. It will allow the user to set a particular charset per newsgroup instead of a global default.
And then you can force that encoding for that folder only -- in which case, auto-detection will be ignored. Yes, that's a better solution. Then, let's make this a duplicate of that bug. Marking this a duplicate of Bug 32714. *** This bug has been marked as a duplicate of 32714 ***
Status: NEW → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → DUPLICATE
We are going to verify this bug as a duplicate of Bug 32714. Being able to "force" the per folder encoding onto all the msgs in a given folder will solve the reported problem.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.