[
https://issues.apache.org/jira/browse/GUACAMOLE-520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16399982#comment-16399982
]
Amarjeet Singh edited comment on GUACAMOLE-520 at 3/15/18 6:48 AM:
-------------------------------------------------------------------
I agree with you. Thanks to highlight it. It will definitely not work if User
is typing from mobile or any other platform ( Shift will not be sent). I will
look into it that how we can handle CapsLock [ which is already there in JIRA ]
Below is the scancodes that I have added in* ja_jp_qwerty.keymap* file :-
{code:none}
map 0x3A ~ 0xFF30 // Japanese Alphanumeric
map 0x3A ~ 0xFF25 // Japanese Hirangana
map 0x7B ~ 0xFF22 // NonConvert
map 0x79 ~ 0xFF21 // Convert
{code}
*Link to get the scancodes of Japanese Keyboard* :-
https://msdn.microsoft.com/en-us/library/ms892472.aspx
*LINK to get the KEYSYM of NonConvert* :
https://www.cl.cam.ac.uk/~mgk25/ucs/keysymdef.h
Keysym added in Guacamole-Client
{code:none}
"Convert": [0xFF21],
"NonConvert": [0xFF22],
{code}
*JUST for INFO* : ( Not deviating from the above issue )
{quote}
I don't know why we cannot rely on keyup event as I have tested the
PrintScreen key which is working and I have handled it in keyup event. Please
provide more info. What could be the effect that will arise ?
I have tested PrintScreen key in Japanese keyboard and English Keyboard .
{quote}
Regards,
Amarjeet Singh
On Thu, Mar 15, 2018 at 11:51 AM, Michael Jumper (JIRA) <j...@apache.org>
wrote:
was (Author: amarjeetxc):
I agree with you. Thanks to highlight it. It will definitely not work if User
is typing from mobile or any other platform ( Shift will not be sent). I will
look into it that how we can handle CapsLock [ which is already there in JIRA ]
Below is the scancodes that I have added in* ja_jp_qwerty.keymap* file :-
{code:none}
map 0x3A ~ 0xFF30 // Japanese Alphanumeric
map 0x3A ~ 0xFF25 // Japanese Hirangana
map 0x7B ~ 0xFF22 // NonConvert
map 0x79 ~ 0xFF21 // Convert
{code}
*Link to get the scancodes of Japanese Keyboard* :-
https://msdn.microsoft.com/en-us/library/ms892472.aspx
*LINK to get the KEYSYM of NonConvert* : https://www.cl.cam.ac.uk/~
mgk25/ucs/keysymdef.h
Keysym added in Guacamole-Client
{code:none}
"Convert": [0xFF21],
"NonConvert": [0xFF22],
{code}
*JUST for INFO* : ( Not deviating from the above issue )
{quote}
I don't know why we cannot rely on keyup event as I have tested the
PrintScreen key which is working and I have handled it in keyup event. Please
provide more info. What could be the effect that will arise ?
I have tested PrintScreen key in Japanese keyboard and English Keyboard .
{quote}
Regards,
Amarjeet Singh
On Thu, Mar 15, 2018 at 11:51 AM, Michael Jumper (JIRA) <j...@apache.org>
wrote:
> Issues with Japanese Keys from Japanese Keyboard in Japanese OS
> ---------------------------------------------------------------
>
> Key: GUACAMOLE-520
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-520
> Project: Guacamole
> Issue Type: Bug
> Components: guacamole
> Affects Versions: 0.9.14
> Reporter: Amarjeet Singh
> Priority: Minor
> Attachments: ja_jp_qwerty.keymap
>
>
> Apache Guacamole Discussion Thread Link is as follows :-
> [http://apache-guacamole-general-user-mailing-list.2363388.n4.nabble.com/Fwd-ISSUES-with-Japanese-Keys-from-Japanese-Keyboard-in-Japanese-OS-td2924.html|http://example.com]
> Local Operating System : Windows 10 [ Japanese Keyboard layout ]
> Remote Operating System : Windows 10 [ Japanese Keyboard layout ]
> Browser : Chrome
> Guacamole-Client and Guacamole-Server [ Latest code from GIT ]
> *server-layout is : ja-jp-qwerty*
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
