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

[bugzilla-daemon at webkit.org]

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

--- Comment #14 from Myles C. Maxfield <mmaxfield at apple.com> ---
It sounds like we are discussing two different things here:

Alexey says:
> when a user types a character with an accent

Richard says:
> Unicode code point is converted

As I understand it, the chain of events is:

1. User presses some keys on their keyboard
2. IME stuff happens
3. A sequence of Unicode code points exists somewhere in memory which has some relation with the keys the user pressed
4. Something somewhere triggers form submission
5. This sequence of code points gets to converted to a sequence of bytes for the wire
6. Sockets are written to

The form encoding tests start this process at step number 3.

It's also relevant that the code points in memory in step 3 are visible to Javascript, and are therefore important for interoperability.

It sounds to me that, because step #3 is visible to Javascript, and step #6 is visible to Javascript (by way of the GET url), that a conceptual function from one to the other should be interoperable between all browsers on all platforms.

When the user types a character with an accent on Windows, perhaps the problem lies with the processing which converts the keystroke into a sequence of Unicode code points. Conceptually, this would seem to occur during step number 2.

Richard, Alexey: what are your thoughts?

-- 
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/20161025/7019f23c/attachment.html>