Re: Intent to unship: ISO-2022-JP-2 support in the ISO-2022-JP decoder

2017-06-15 Thread Henri Sivonen
On Mon, Nov 30, 2015 at 5:38 PM, Henri Sivonen 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

Re: Intent to unship: ISO-2022-JP-2 support in the ISO-2022-JP decoder

2015-12-02 Thread Henri Sivonen
On Mon, Nov 30, 2015 at 7:09 PM, Jörg Knobloch wrote: > As far as I see, there are no objections to removing the ISO-2022-JP-2 > variant as long as the ISO-2022-JP is maintained. Cool. This intent is indeed scoped to the -2 stuff only. On Mon, Nov 30, 2015 at 7:21 PM, Jonas

Re: Intent to unship: ISO-2022-JP-2 support in the ISO-2022-JP decoder

2015-11-30 Thread Jonas Sicking
On Mon, Nov 30, 2015 at 7:38 AM, Henri Sivonen wrote: > Other browsers don't support this extension, so it clearly can't be a > requirement for the Web Platform Generally speaking, I don't think this reasoning is entirely accurate. We know that there's lots of

Re: Intent to unship: ISO-2022-JP-2 support in the ISO-2022-JP decoder

2015-11-30 Thread Jörg Knobloch
On 30/11/2015 16:38, Henri Sivonen wrote: Are there any objections to removing the ISO-2022-JP-2 functionality from mozilla-central? Hello, I am currently in the process of repairing long-standing issues with CJK e-mail in general and Japanese e-mail using ISO-2022-JP in particularm see

Intent to unship: ISO-2022-JP-2 support in the ISO-2022-JP decoder

2015-11-30 Thread Henri Sivonen
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

Re: Intent to unship: ISO-2022-JP-2 support in the ISO-2022-JP decoder

2015-11-30 Thread Andrew Sutherland
On Mon, Nov 30, 2015, at 01:24 PM, Adam Roach wrote: > Does this mean it might interact with webmail services as well? Or do > they tend to do server-side transcoding from the received encoding to > something like UTF8? They do server-side decoding. It would take a tremendous amount of effort

Re: Intent to unship: ISO-2022-JP-2 support in the ISO-2022-JP decoder

2015-11-30 Thread Adam Roach
On 11/30/15 09:38, Henri Sivonen wrote: 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. Does this mean it might interact with webmail services as well? Or do they tend to do server-side

Re: Intent to unship: ISO-2022-JP-2 support in the ISO-2022-JP decoder

2015-11-30 Thread Joshua Cranmer 
On 11/30/2015 1:02 PM, Andrew Sutherland wrote: On Mon, Nov 30, 2015, at 01:24 PM, Adam Roach wrote: Does this mean it might interact with webmail services as well? Or do they tend to do server-side transcoding from the received encoding to something like UTF8? They do server-side decoding.