Re: [encoding] "gb18030 ranges" have problematic definitions (#17) from Anne van Kesteren on 2016-01-05 (public-webapps-github@w3.org from January 2016)

From: Anne van Kesteren <notifications@github.com>
Date: Tue, 05 Jan 2016 05:57:00 -0800
To: whatwg/encoding <encoding@noreply.github.com>
Message-ID: <whatwg/encoding/issues/17/169007991@github.com>

@r12a I'm confused by the outcome of your tests since it suggests browsers simply do not encode U+E5E5 at all despite gb18030 supposedly being a UTF (both Chrome and Firefox emit an "HTML entity").

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

Received on Tuesday, 5 January 2016 13:57:56 UTC