linux/cros: Supports XKeyEvent to Unicode conversion independent from user's locale.

ui/events/keycodes/keysym_to_unicode_x.h

Index: ui/events/keycodes/keysym_to_unicode_x.h
diff --git a/ui/events/keycodes/keysym_to_unicode_x.h b/ui/events/keycodes/keysym_to_unicode_x.h
new file mode 100644
index 0000000000000000000000000000000000000000..cfb8ff4a7ee9bf2c5ce148d03903d3bfd49ec375
--- /dev/null
+++ b/ui/events/keycodes/keysym_to_unicode_x.h
@@ -0,0 +1,18 @@
+// Copyright 2014 The Chromium Authors. All rights reserved.
+// Use of this source code is governed by a BSD-style license that can be
+// found in the LICENSE file.
+
+#ifndef UI_EVENTS_KEYCODES_KEYSYM_TO_UNICODE_X_H_
+#define UI_EVENTS_KEYCODES_KEYSYM_TO_UNICODE_X_H_
+
+#include <cstdint>
+
+namespace ui {
+
+// Returns a unicode character corresponding to the given |keysym|.  If the

[Wez, 2014/08/07 23:37:12]

s/unicode/Unicode

[Yuki, 2014/08/08 14:22:09]

Done.

+// |keysym| doesn't represent a printable character, returns zero.
+uint16_t GetUnicodeCharacterFromXKeySym(unsigned long keysym);

[Wez, 2014/08/07 23:37:12]

You're only returning a 16-bit value, so you can only return Unicode characters
from the Basic Plane, surely?

[Yuki, 2014/08/08 14:22:09]

Yes, it's intentional.  No one uses a keyboard whose key is assigned to a
character outside the Basic Plane.  Should be no problem.

Note that ui::KeyEvent::GetCharacter() returns base::char16, so it's meaningless
to support such a character for now.

+
+}  // namespace ui
+
+#endif  // UI_EVENTS_KEYCODES_KEYSYM_TO_UNICODE_X_H_