JDK1.1.*'s java.awt.event.KeyEvent does not have
VK_COLON(0xBA) for ':', VK_AT(0xC0) for '@', and VK_CIRCUMFLEX(0xDE) for '^'.
These keys are inputed with Japanese PC106 keyboard or
Japanese Sun Keyboard without modifier keys.
So VK_ value for these keys are nessesaly.
JDK1.1.3 implementations are
Win32: store correct values (Windows VK value)
into keyCode variable for these key's KEY_PRESS/KEY_RELEASE event
Solaris: store 0 (VK_UNDEFINED) into keyCode variable for
these key's KEY_PRESS/KEY_RELEASE event.
So the first bug is java.awt.event.KeyEvent has no constant variable for
':', '@' nor '^'.
The second bug is Solaris/AWT implementation stores VK_UNDEFINED value into
KEY_PRESS/KEY_RELEASE KeyEvent's keyCode for ':', '@' and '&'.
I'm not sure about other countries keyboard, but basically any key has
possibility to be inputed without modifier keys considering l10n keyboard, so
every key code which appear in popular keyboard should be pre-defined
in KeyEvent class, I believe.
This bug report states only about Japanese keyboard.
Here is the input from Ginger Ward about European keyboard.
----- Begin Included Message -----
Date: Thu, 7 Aug 97 10:31:49 JST
From: ###@###.### (Ginger Ward (Ferguson))
Subject: [LUNA-IM:121] Virtual-Key Keysym definitions missing
To: ###@###.### (luna-im)
I've been noticing that as I write more keysym-
to-Virtual-Key tables, for use in my localized
keyboard classes, I find that I need additional
Virtual Key keysyms that aren't in the
java.awt.event.KeyEvent class. This is annoying
in the sense that it seems that for each keyboard
I write, I find more VK keysyms that aren't present.
I'm concerned, as I would like to be able to add
new keyboard classes rather seemlessly, I mean without
having to add stuff to the base JDK to support them.
Here I list the additional Virtual Key keysyms needed for
the scancode-VK keysym (few) tables I've done so far.
These are needed to support the following keyboards:
danish, french, italian, spanish, uk
(I used the Xlib keysym names as advised by Tom Ball.)
Perhaps there's a better way for me to do this. It seems
that as I add keyboards I'll keep asking you all to add
VK keysyms. There must be a better way. If anyone has
any good ideas, please email.
However, for now, can these please be added to the
----- End Included Message -----
IBM and other licensees have also requested additional VK constants to fully support localized keyboards, for example:
Kanji code input