Re: [whatwg/encoding] gb18030 encoding/decoding support (#57)

Some time ago, the Encoding Standard starting mapping the two bytes "0xA3 0xA0" to "U+3000" rather than U+E5E5 "to be compatible with deployed content".

Do the benefits of this mapping still outweigh the disadvantages even today?  They depend largely on—

- how commonly GB18030 (as opposed to other encodings) is used in Web sites today compared to when the mapping was made,
- whether, today compared to when the mapping was made, the GB18030 bytes "0xA3 0xA0" are still commonly used instead of the proper mapping for U+3000 to represent a space character in Web sites,
- how frequently Web sites that use "0xA3 0xA0" instead of the proper mapping for U+3000 are seen today compared to when the mapping was made,
- whether GB18030 encoders/decoders that convert "0xA3 0xA0" to or from U+3000 (besides implementations of the Encoding Standard) are still widely deployed today,
- the effort required for Encoding Standard implementations to update their GB18030 mapping tables, 
- the need and desirability to comply strictly with GB18030-2005, and
- other factors weighing for or against this mapping.




-- 
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/57#issuecomment-403296620