W3C home > Mailing lists > Public > public-i18n-core@w3.org > January to March 2015

I18N-ISSUE-443 (BUG27256): revamp iso-2022-jp decoder/encoder [encoding]

From: Internationalization Working Group Issue Tracker <sysbot+tracker@w3.org>
Date: Mon, 30 Mar 2015 14:02:44 +0000
To: public-i18n-core@w3.org
Message-Id: <E1YcaH6-000GDE-HV@deneb.w3.org>
I18N-ISSUE-443 (BUG27256): revamp iso-2022-jp decoder/encoder [encoding]


Raised by: Richard Ishida
On product: encoding


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


Reporter: annevk@annevk.nl

Per Jungshik Chromium and WebKit follow ICU, which follows


whereas Gecko has its own implementation which is quite a bit different. I
forgot what Opera did, but it no longer seems relevant. Internet Explorer is
quite special as well, allowing nested shift_jis.

Given this, I'm inclined to align the decoder with the aforementioned RFC,
though keeping error and EOF handling of course. Note that by fixing bug 26885
we already took one step in this direction.
Received on Monday, 30 March 2015 14:02:45 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:02:05 UTC