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

Since most browsers emit an error, it seems safer to just do that. Especially since WebKit ["fixed" this](https://bugs.webkit.org/show_bug.cgi?id=17014) in 2008, six years after Gecko did. Seems likely it might still be problematic.

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