[ 
https://issues.apache.org/jira/browse/GUACAMOLE-1936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17832246#comment-17832246
 ] 

Mike Jumper commented on GUACAMOLE-1936:
----------------------------------------

The keyboard layout for the connection and the keyboard layout within the 
remote desktop must match for Guacamole to be able to supply the RDP server 
with the correct events. If you connect to an RDP connection and then 
subsequently change the keyboard layout inside that RDP connection, Guacamole 
cannot know that you have done this and continues expecting that the remote 
keyboard layout is as originally set for the remote desktop session. It 
continues sending scancodes that would be correct for the original keyboard 
layout, but are no longer correct for the new layout.

See: https://guacamole.apache.org/faq/#does-guacamole-support-my-keyboard-layout

You don't typically need to set the keyboard layout within the RDP session, as 
Guacamole will automatically translate key presses that are missing from the 
RDP layout into Unicode events, allowing typing to work consistently regardless 
of the remote layout.

If you wish to use a Finnish keyboard to type in Guacamole, you need to:

# Set the Finnish keyboard _on the client machine only_.
# Change nothing on the RDP server.
# Change nothing in the RDP connection settings.

... and that's it. Guacamole will automatically translate the key events as 
long as you don't touch the _remote_ keyboard layout after connecting.

> Finnish keyboard input
> ----------------------
>
>                 Key: GUACAMOLE-1936
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-1936
>             Project: Guacamole
>          Issue Type: Bug
>            Reporter: zhenfa zhao
>            Priority: Major
>
> When the local computer uses the Finnish keyboard and the RDP is set to the 
> Finnish keyboard, the symbols cannot be entered accurately
> Corresponding keyboard keys:
> / ; ' [ ] \ 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to