cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Minying Bao (JIRA)" <>
Subject [jira] [Created] (CLOUDSTACK-1964) Simplified Chinese -- Some combination keys used to switch IME cannot work well
Date Mon, 08 Apr 2013 09:53:15 GMT
Minying Bao created CLOUDSTACK-1964:

             Summary: Simplified Chinese -- Some combination keys used to switch IME cannot
work well
                 Key: CLOUDSTACK-1964
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: VNC Proxy
    Affects Versions: 4.2.0
         Environment: Build No.#133 (CloudStack-non-OSS-MASTER-133-rhel6.3.tar.gz)
XenServer6.1 for Host Server, CentOS6.3 for NFS server and CloudStack-Mgr Server, Win7Entx64SP1
for Client machine. 
            Reporter: Minying Bao

Setup the CloudStack environments with build 4.2#133.
Add SC-Win7 template and then create as an instance.
Open Firefox, launch the SC-Win7 via ConsoleProxy in client machine.
Hit all the keys with Simplified Chinese Keyboard (the same as US-101 standard keyboard).

Expected Result
All the keys should remap as same as the Simplified Chinese Keyboard layout behavior.

Actual Result
Simplified Chinese follows "US-101 keyboard" style, so most of the keys are working fine for
Simplified Chinese apart from few combination keys used to switch IME.
1. "Ctrl+Shift"
Repro frequency is 30%. As the key combinations are accepted correctly, we may not able to
fix using keytranslation.
Ctrl+Shift is used to switch of "Microsoft Pinyin New Experience Input Style", "Microsoft
Pinyin ABC Input Style" and "SouGou Pingyin input Style"
2. "Ctrl+Space"
Not working.
Ctrl + Space to switch keyboard layout between SC-US keyboard and SC-IME are not working at
3. "Ctrl+Dot"
Not working in IE browser, but works fine in Firefox.
Ctrl + Dot to switch Half/Full shape punctuation are not working at all.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message