Comment #2 on issue 1724 by [email protected]: Please update keycode for
jp
http://code.google.com/p/ibus/issues/detail?id=1724
In short, I agree. I wish you to move Execute and Katakana to the bottom
with comment.
Here is the long answer:
I hope there is no interference for having unused keycode values.
* The 'execute' being 84, there is no corresponding MACRO value in
<linux/input.h>.
* The 'Katakana' being 112 which corresponds to KEY_MACRO in
<linux/input.h>.
So neither keycodes overwrite used kernel keycode points.
These are clearly the Nicola (Oyayubi-shift) Fujitsuu Oasis keyboard key
names. So moving them to the bottom with comments noting these to be
verified by the hardware owner. It is still sold with PS/2 and USB
interfaces.
* http://access-fs.com/oasys/kblist.html
* http://access-fs.com/shop/product.php?P=FMV-KB613 (See Jikkou-key)
As for Caps_Lock/Eisuu, what you proposed is the same as current XKB jp
assignment. (Somehow ./keycode.py reports differently. I have no idea
which is right.)
I hope Daiki to check this too.
Regards,
Osamu
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
You received this message because you are subscribed to the Google
Groups "ibus-devel" group.
iBus project web page: http://code.google.com/p/ibus/
iBus dev group: http://groups.google.com/group/ibus-devel?hl=en
---
You received this message because you are subscribed to the Google Groups "ibus-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
