Re: [whatwg/encoding] If gb18030 is revised, consider aligning the Encoding Standard (#27) from Henri Sivonen on 2017-03-21 (public-webapps-github@w3.org from March 2017)

From: Henri Sivonen <notifications@github.com>
Date: Tue, 21 Mar 2017 00:32:06 -0700
To: whatwg/encoding <encoding@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <whatwg/encoding/issues/27/287997960@github.com>

> 0x84318236 → U+E78D
...
> 0x95329031 → U+E816

It seems harmful, and against the goal of avoiding the PUA, to change byte sequences that previously decoded to non-PUA code points to decode to PUA code points. This means that data out there that previously decoded to (assigned in Unicode) non-PUA code points would start mapping to the PUA.

I don't see how that could be a good thing for any practical interop purpose. (I can see how that could seem appealing to the theory that the GB18030 encoding is a bijective UTF, but that's already not the case as far as the Web is concerned due to U+3000 being double-mapped and U+E5E5 being unmappable.)

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/encoding/issues/27#issuecomment-287997960

Received on Tuesday, 21 March 2017 07:32:41 UTC