[
https://issues.apache.org/jira/browse/GUACAMOLE-520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17074214#comment-17074214
]
Kazuhiko Tanaka edited comment on GUACAMOLE-520 at 4/3/20, 2:40 AM:
--------------------------------------------------------------------
In the discussion, I feel that keyboard recognition and key code
recognition are mixed. What I found was a keycode recognition problem, but no
keyboard recognition problem. Input of symbols etc. was done without problems.
I confirmed the problem of "Zenkaku_Hankaku" key in addition to "Caps Lock"
and "Hiragana". If enter the "Zenkaku_Hankaku" key in a Japanese browser,
"Zenkaku (keyup 243 and keydown 244)" and "Hankaku (keyup 244 and keydown 243)"
will be entered alternately (In each case, a keyup occurs first, followed by a
keydown). However, Guacamole does not seem to recognize these keys. Entering
these keys only switches the browser IME and does not affect the connection
destination.
I confirmed a strange phenomenon. If the focus is outside the canvas, it
may be recognized that a key has been pressed. Perhaps the keydown event is
not recognized on the canvas.
This problem has been observed in v1.0.0. Only confirmed that v1.1.0 does
not recognize "Zenkaku_Hankaku" too.
was (Author: tanakakz):
In the discussion, I feel that keyboard recognition and key code
recognition are mixed. What I found was a keycode recognition problem, but no
keyboard recognition problem. Input of symbols etc. was done without problems.
I confirmed the problem of "Zenkaku_Hankaku" key in addition to "Caps Lock"
and "Hiragana". If enter the "Zenkaku_Hankaku" key in a Japanese browser,
"Zenkaku (keyup 243 and keydown 244)" and "Hankaku (keyup 244 and keydown 243)"
will be entered alternately (In each case, a keyup occurs first, followed by a
keydown). However, Guacamole does not seem to recognize these keys. Entering
these keys only switches the browser IME and does not affect the connection
destination.
I confirmed a strange phenomenon. If the focus is outside the canvas, it
may be recognized that a key has been pressed. Perhaps the keydown event is
not recognized on the canvas.
> Japanese keyboard layout for RDP incorrect
> ------------------------------------------
>
> Key: GUACAMOLE-520
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-520
> Project: Guacamole
> Issue Type: Bug
> Components: RDP
> Reporter: Amarjeet Singh
> Priority: Minor
> Attachments: Keyboard_testing_report_Guacamole.xlsx
>
>
> [The Japanese keyboard layout definition used by Guacamole's RDP
> support|https://github.com/apache/guacamole-server/blob/e2feb416052b1a1ab33db6e79c5ea6e4f6f6eacf/src/protocols/rdp/keymaps/ja_jp_qwerty.keymap]
> currently contains the following:
> {code:none}
> #
> # Licensed to the Apache Software Foundation (ASF) under one
> # or more contributor license agreements. See the NOTICE file
> # distributed with this work for additional information
> # regarding copyright ownership. The ASF licenses this file
> # to you under the Apache License, Version 2.0 (the
> # "License"); you may not use this file except in compliance
> # with the License. You may obtain a copy of the License at
> #
> # http://www.apache.org/licenses/LICENSE-2.0
> #
> # Unless required by applicable law or agreed to in writing,
> # software distributed under the License is distributed on an
> # "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
> # KIND, either express or implied. See the License for the
> # specific language governing permissions and limitations
> # under the License.
> #
> parent "base"
> name "ja-jp-qwerty"
> freerdp "KBD_JAPANESE"
> map -shift 0x02..0x0D 0x7D ~ "1234567890-^\"
> map -shift 0x10..0x1B ~ "qwertyuiop@["
> map -shift 0x1E..0x28 0x2B ~ "asdfghjkl;:]"
> map -shift 0x2C..0x35 0x73 ~ "zxcvbnm,./\"
> map +shift 0x02..0x0A 0x0C 0x0D 0x7D ~ "!"#$%&'()=~|"
> map +shift 0x10..0x1B ~ "QWERTYUIOP`{"
> map +shift 0x1E..0x28 0x2B ~ "ASDFGHJKL+*}"
> map +shift 0x2C..0x35 0x73 ~ "ZXCVBNM<>?_"
> map -shift 0x29 ~ 0xFF28
> map -shift 0x29 ~ 0xFF2A
> map +shift 0x29 ~ 0xFF29
> {code}
> This is inherently incorrect, as the Japanese keyboard can type far more
> characters than those given here. Even if the missing characters are
> correctly mapped, several of these characters depend on additional,
> Japanese-specific modifier/lock keys which the keymap format does not
> currently define.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
