VirtualBox

Ticket #2847 (closed defect: fixed)

Opened 5 years ago

Last modified 5 years ago

<Henkan_Mode> Key on Japanese keyboard is not recognized on Solaris host => fixed in SVN

Reported by: yukie Owned by:
Priority: major Component: other
Version: VirtualBox 2.1.0 Keywords:
Cc: Guest type: Solaris
Host type: Solaris

Description

<Henkan_Mode> key on Japanese keyboard is not worked correctly on Solaris.
Because the meaning of key code is different.

  • <Henkan_Mode> Key is recognized as <kanji(0xff21)> on Solaris host.
  • <Henkan_Mode> key is recognized as <Henkan_Mode(0xff23)> on Ubuntu host.

This was fixed in VirtualBox 2.06 by ticket 2263.
But it is not fixed in VirtualBox 2.10.
I opened a new ticket as a follow to #2263.

Attachments

VBoxKeyboard-2.1.0-jp106-sun.patch Download (1.4 KB) - added by sayama 5 years ago.

Change History

Changed 5 years ago by sayama

comment:1 Changed 5 years ago by sayama

I investigated this issue and found that X11DRV_KeyEvent() uses nonchar_key_scan table instead of main_keyboard_type_scans table on 2.1. Howeven even if using keysym, this problem cannot be fixed because the meaning the keysym is bit different between Solaris and Linux as the historical reason. Here is the difference.

Xorg on SolarisXorg on Linux
Zenkaku-Hankaku key (AT scan=29)Henkan_Mode(0xff23)Zenkaku_Hankaku(0xff2a)
Katakana/Hiragana key (AT scan=70)Kana_Lock(0xff2d)Hiragana_Katakana(0xff27)
Henkan key (AT scan=79)Kanji(0xff21)Henkan_Mode(0xff23)
Muhenkan key (AT scan=7B)Execute(0xff62)Muhenkan(0xff22)

Could you please review attached patch and merge it if it's OK? Yes, this is MIT-licenced.

comment:2 Changed 5 years ago by michael

  • Status changed from new to closed
  • Resolution set to fixed
  • Summary changed from <Henkan_Mode> Key on Japanese keyboard is not recognized on Solaris host to <Henkan_Mode> Key on Japanese keyboard is not recognized on Solaris host => fixed in SVN

Patch merged. Sorry that you had to redo this (I applied your last patch to the 2.0 branch, but I thought that it would not be needed on 2.1). Thanks again.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use