Thanks for the test suite. I'm updating Blink's converters now to the latest spec. While doing so, I found a bug in the spec. See https://github.com/whatwg/encoding/issues/21. Anne will take care of it quickly, I guess. After that, you have to run the test again for Japanese encodings :-) Jungshik On Wed, Dec 9, 2015 at 3:20 AM, <ishida@w3.org> wrote: > the page > > http://www.w3.org/International/tests/repo/results/encoding-dbl-byte > > now points to a lot more tests, with results for major browsers, for the > double-byte encodings in the Encoding spec. > > the tests are grouped as follows: > > 1 does the browser encode characters as expected per the Encoding spec > when sending data with a form? > > 2 are characters that cannot be encoded using the Encoding spec algorithms > handled as expected? > > > 3 same as 1 for values constructed for an href attribute > > 4 same as 2 for href values > > > 5 are the characters that can be encoded decoded per the spec? (in the > case of euc-jp and big5, the characters tested include more than just those > that can be encoded) > > 6 are non-conformant byte sequences encountered during decoding dealt with > per the Encoding spec algorithms? > > > there is another page at > > > http://www.w3.org/International/tests/repo/results/encoding-dbl-byte-nightly > > which shows the results for the latest nightlies (although a small number > of tests in the other page haven't made it to this one yet) > > > > next step is to analyse why the failures are occuring. > > (The following app can be useful to diagnose the underlying issues > http://r12a.github.io/apps/encodings/ ) > > ri > >Received on Thursday, 10 December 2015 19:49:34 UTC
This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:41:09 UTC