On Mon, Nov 30, 2015 at 5:38 PM, Henri Sivonen <hsivo...@hsivonen.fi> wrote: > Japanese *email* is often encoded as ISO-2022-JP, and Web browsers > also support ISO-2022-JP even though Shift_JIS and EUC-JP are the more > common Japanese legacy encodings on the *Web*. The two UTF-16 variants > and ISO-2022-JP are the only remaining encodings in the Web Platform > that encode non-Basic Latin characters to bytes that represent Basic > Latin characters in ASCII. > > There exists an extension of ISO-2022-JP called ISO-2022-JP-2. The > ISO-2022-JP decoder (not encoder) in Gecko supports ISO-2022-JP-2 > features, which include the use of characters from JIS X 0212, KS X > 1001 (better known as the repertoire for EUC-KR), GB 2312, ISO-8859-1 > and ISO-8859-7. The reason originally given for adding ISO-2022-JP-2 > support to Gecko was: "I want to add a ISO-2022-JP-2 charset decoder > to Mozilla."[1] > > Other browsers don't support this extension, so it clearly can't be a > requirement for the Web Platform, and the Encoding Standard doesn't > include the ISO-2022-JP-2 extension in its definition for the > ISO-2022-JP decoder. Bringing our ISO-2022-JP decoder to compliance[2] > would, therefore, involve removing ISO-2022-JP-2 support. > > The only known realistic source of ISO-2022-JP-2 data is Apple's Mail > application under some circumstances, which may impact Thunderbird and > SeaMonkey. > > Are there any objections to removing the ISO-2022-JP-2 functionality > from mozilla-central? > > [1] https://bugzilla.mozilla.org/show_bug.cgi?id=72468 > [2] https://bugzilla.mozilla.org/show_bug.cgi?id=715833 > -- > Henri Sivonen > hsivo...@hsivonen.fi > https://hsivonen.fi/
Code implementing the above-quoted intent has landed. -- Henri Sivonen hsivo...@hsivonen.fi https://hsivonen.fi/ _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
