[Webkit-unassigned] [Bug 159891] [encoding] Support for GB18030

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=159891

--- Comment #8 from r12a <ishida at w3.org> ---
For me, interoperability means that users get identical results when they perform identical steps regardless of the platform or browser they are using.

This particular issue is about what happens when a Unicode code point is converted to a GB18030 sequence of bytes. For example, U+FA5C 臭 is converted by Firefox, Chrome and Edge to the GB18030 byte sequence %84%30%A1%38.  Safari, however, converts that Unicode character to the byte sequence %B3%F4 (which is the GB18030 character that corresponds to U+81ED 臭.

In other words, suppose i'm writing the following: 
"There are two similar han ideographs which represent the sound xiù, 臭 and 臭. In Unicode these are compatilibity equivalents."

If that document gets converted to the GB18030 encoding by any of the other major browser engines it will look the same, since GB18030 has code points for both forms.  If however the conversion happens in Webkit the sentence will be changed from the original and become rather confusing for the reader, since both ideographs shown are now the same.  The text no longer says what the writer intended.

"There are two similar han ideographs which represent the sound xiù, 臭 and 臭. In Unicode these are compatilibity equivalents."

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20161021/657f5240/attachment.html>