- From: jungshik <notifications@github.com>
- Date: Sat, 06 May 2017 15:10:26 -0700
- To: whatwg/encoding <encoding@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Saturday, 6 May 2017 22:11:05 UTC
@aphillips @annevk I wouldn't call it a bug. On the Internet/Web, only [the original ISO-2022-JP defined in RFC 1468](https://tools.ietf.org/html/rfc1468) was "widely" (relative to subsequent versions) used as defined in RFC 1468, but subsequent versions of [ISO-2022-JP-[123]](https://en.wikipedia.org/wiki/ISO/IEC_2022#ISO.2FIEC_2022_character_sets) never got much traction. Why would anybody use ISO-2022-JP-* to encode Chinese, Korean, Latin beyond ASCII, and Greek? And, JIS X 0212 (supported in ISO-2022-JP-1 or later) is not critical enough to Japanese users (Shift_JIS does not support it, either). The original ISO-2022-JP does not support Halfwidth Katakana. That's why ICU has a fallback encoding for Halfwidth Katakana for the original ISO-2022-JP. It's only ISO-2022-JP-3 that supports Halfwidth Katakana. ICU supports ISO-2022-JP-3 as defined and does not have fallback encoding for Halfwidth Katakana for ISO-2022-JP-3. Note that [ISO-2022-JP-2 defined in RFC 1554](https://tools.ietf.org/html/rfc1554) does not support them either. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/whatwg/encoding/issues/105#issuecomment-299668933
Received on Saturday, 6 May 2017 22:11:05 UTC