ISSUE-441: Drop JIS X 212 from ISO-2022-JP

Drop JIS X 212 from ISO-2022-JP

State:

CLOSED

Product:

encoding

Raised by:

Richard Ishida

Opened on:

2015-03-30

Description:

https://www.w3.org/Bugs/Public/show_bug.cgi?id=26885

This issue tracks the bug listed above and was created as part of the WG CR process.

---

Reporter: jshin@chromium.org

EUC-JP in the encoding spec does not support JIS X 212 even though the formal
definition of EUC-JP does include it.

OTOH, ISO-2022-JP in the encoding spec does support JIS X 212 to my surprise.

Is there a reason to support JIS X 212 in ISO-2022-JP? It's not a part of the
original ISO-2022-JP (RFC 1468 : https://www.ietf.org/rfc/rfc1468.txt). It's
added later in RFC 1554, but I don't think it's widely used.

Blink has never supported ISO-2022-JP-2 with JIS X 212. It only supports the
original ISO-2022-JP. Supporting JIS X 212 adds ~ 50kB to our build and I'd
rather avoid it.

Related Actions Items:

No related actions

Related emails:

1. I18N-ISSUE-441 (BUG26885): Drop JIS X 212 from ISO-2022-JP [encoding] (from sysbot+tracker@w3.org on 2015-03-30)

Related notes:

Display change log