Re: Tests for Encoding spec

I was surprised to see > 200 failures for EUC-KR encoding in Chrome because
Chrome's copy of ICU has EUC-KR table automatically generated from the
encoding spec's index file for EUC-KR.

Virtually all of them are due to an NFC performed by Chrome at some point.
For instance, U+2126 is normalized to U+03A9 before being encoded to
EUC-KR. Most others failures are due to CJK Compatibility characters being
mapped to their corresponding canonical characters. (Chrome bug : )

The same is true of Shift_JIS failures (23 out of 24).

The first one (U+2022) : Chrome's table was not updated to cover the
following new change in the spec:

   If code point is U+2022, set it to U+FF0D.

I'll update our SJIS table.

BTW, the following summary is incorrect:

   1. sjis-encode: Total characters tested 7,326. Firefox fails for 1, *Opera
   and Safari *for 24. Edge fails because the test doesn't work in that
   browser. (Characters are not converted to percent-escapes in the href

'Opera and Safari for 24' should be 'Chrome and Opera for 24'.


On Fri, Oct 16, 2015 at 8:32 AM, Richard Ishida <> wrote:

> fyi, i just published two pages pointing to Encoding spec tests:
> 1.
> moves pre-existing tests to our new i18n test framework, but also adds
> some changes to koi8-u and a new test for koi8-ru, to conform to the latest
> Encoding spec text.  I also drafted the results for the major desktop
> browsers.  Apart from support for koi8-u, there have been many improvements
> since the last time the test results were recorded.
> 2.
> these are tests for some double-byte encodings.  In some cases the test
> needs some attention still, so the results are so far tentative.
> we are working on producing more tests, and would welcome any offers to
> help.  There are a few tests provided by Anne & co for which we don't yet
> display results, but we will try to do so. However, we also need to develop
> more.
> ri

Received on Friday, 16 October 2015 19:30:44 UTC