Re: [encoding] "gb18030 ranges" have problematic definitions (#17)

i didn't test all the BMP for gb18030, just selected ranges, so i missed that particular character.  However, there are now two new tests that do test it, and find it (and only that one in the PUA) to be problematic on Firefox and Chrome (didn't try any others).

http://www.w3.org/International/tests/repo/encoding/legacy-mb-schinese/gb18030/gb18030-encode-form-other-pua.html

http://www.w3.org/International/tests/repo/encoding/legacy-mb-schinese/gb18030/gb18030-decode-other-pua.html

i won't integrate these tests into the i18n test suite fully until we decide what needs to be done about this.

i don't have any clear idea about why this fails, although peter's suggestion seems plausible (note the that problem character is the first one in the PUA (that isn't in the index)).

(http://r12a.github.io/apps/encodings/ also shows the behaviour @peteroupc describes)






---
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/encoding/issues/17#issuecomment-165206634