Re: [encoding] Big5 encoder treats a code point as error when both an HKSCS and non-HKSCS pointer exists for the code point (#9)

On a tangent, it'd be nice if we were adding regression tests for changes like this to web-platform-tests/encoding.

Since thinking is hard but I'm versed on the process and tests, I'll happily add tests/cases if we can encourage reporters to include example string/byte arrays pairs as comments on bugs like this.


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