Internationalization is the process of designing and developing a software product to function in multiple locales. This process involves identifying the locales that must be supported, designing features which support those locales, and writing the code needed.

Thanks for repoting this.
Just an observation - if this is a regression starting at version 31.0 (I'm not saying it is), it's hard to understand why this is only now being reported 5 months after release.

I could confirm this issue with attaching message.
But on my linux box, the issue also exists on thunderbird 24.6.0.
Note that this message does not contain any characters being included only in ms932.

(In reply to Wayne Mery (:wsmwk) from comment #1)
> Just an observation - if this is a regression starting at version 31.0 (I'm
> not saying it is), it's hard to understand why this is only now being
> reported 5 months after release.
Because it requires a message charset whose value is not anything we recognize.

I am guessing the problematic message in attachment 8547985[details] was sent by a JAVA system.
mizota san, does the messsage surely contain extended characters specified for ms932 (IBM extended)?
If not, windows-31j should be used instead there.

> Could you please attach a message which is GOOD on 24.6 but NG on 31.3?
ikezoe san ,I'm sorry this message is a "trade secret" so I can't attach.
I ask the person who send the email to
send a sample mail but they could not send the mail.
I download other version from this site.
http://ftp.mozilla.org/pub/mozilla.org/thunderbird/releases/
29.0b1 is GOOD and 30.0b1 is NG

> mizota san, does the messsage surely contain extended characters specified
> for ms932 (IBM extended)?
> If not, windows-31j should be used instead there.
ikezoe san , how can I check the message is
extended characters specified for ms932.

Anne, did you go for the intersection rather than the union when including labels in the Encoding Standard? Based on the research you posted, it seems that Presto-Opera recognized ms932 as a label of Shift_JIS.
(In reply to Hiroyuki Ikezoe (:hiro) from comment #13)
> mizota san, the charset of your system can not be changed to windows-31j?
Do you mean in whatever Java program that generated emails labeled as ms932?

(In reply to Henri Sivonen (:hsivonen) from comment #15)
> Anne, did you go for the intersection rather than the union when including
> labels in the Encoding Standard? Based on the research you posted, it seems
> that Presto-Opera recognized ms932 as a label of Shift_JIS.
>
> (In reply to Hiroyuki Ikezoe (:hiro) from comment #13)
> > mizota san, the charset of your system can not be changed to windows-31j?
>
> Do you mean in whatever Java program that generated emails labeled as ms932?
I am guessing programs built on Java-1.4 and prior versions use ms932 in Japan.

(In reply to Henri Sivonen (:hsivonen) from comment #15)
> Anne, did you go for the intersection rather than the union when including
> labels in the Encoding Standard? Based on the research you posted, it seems
> that Presto-Opera recognized ms932 as a label of Shift_JIS.
Mostly based on what the majority of user agents recognized. We had to be conservative to some extent as e.g. recognizing "shift-jis" as "shift_jis" causes compatibility issues.
Adding "ms932" seems like it might be worth it.

(In reply to Kent James (:rkent) from comment #19)
> I'm trying to understand what Thunderbird should do with this. Looking at
> the discussions in https://www.w3.org/Bugs/Public/show_bug.cgi?id=27851 it
> looks like this is leaning toward WONTFIX. Is that correct?
The W3 argues that adding new labels is probably not a net win, and I would WONTFIX adding ms932.
However, we appear to have a problem that giving an illegal charset as a label causes the charset selector to be disabled... which, if true, is a bug that really ought to be fixed.

(In reply to Joshua Cranmer [:jcranmer] from comment #20)
...
>
> The W3 argues that adding new labels is probably not a net win, and I would
> WONTFIX adding ms932.
>
> However, we appear to have a problem that giving an illegal charset as a
> label causes the charset selector to be disabled... which, if true, is a bug
> that really ought to be fixed.
If the problem of "the charset selector to be disabled" is fixed, is the message with
charset as ms932 somehow be rendered correctly?
I just noticed a posting in a large Japanese BBS in which one user describes
an issue of receiving such e-mails with ms932 chartype
from automated warehouse management system. It looks that the old Java system used to build the inventory and delivery management system used ms932 instead of
proper label (Windows-31J ???) to send out e-mails in Japanese,
and there is no way the user (the mere recipient of the automatic e-mail from the warehouse) could do.
He was forced to switch to livemail or something, but was not heard from again so far.
TIA