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

Nick Couchman commented on GUACAMOLE-925:
-----------------------------------------

[~nickstep]: Thanks for the information this. In regard to your feedback:
* The transmission of Unicde in absence of the proper scancodes is an intended 
feature - as you mention, the solution is to make sure the scancodes are being 
sent, which means having a correct, up-to-date keymap.
* Thank you for providing the updated keymap - it would be great if you could 
open a pull request on Github with this information and we can get it merged 
into the code.

> Add Russian keyboard support for RDP
> ------------------------------------
>
>                 Key: GUACAMOLE-925
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-925
>             Project: Guacamole
>          Issue Type: Improvement
>          Components: RDP
>    Affects Versions: 1.0.0
>            Reporter: Roman Adyev
>            Priority: Minor
>         Attachments: SCREEN.jpg, apache_guacamole_Russian_layouts.txt, 
> image-2021-01-04-14-42-50-393.png, ru_ru_qwerty-2.keymap, ru_ru_qwerty.keymap
>
>
> Hello, dear support team!
> I'm using Unicode layout because Russian layout isn't presented there, but 
> with Unicode layout I can't send keyboard shortcuts to remote RDP machine 
> (CTRL + C for example).
> If I switch Unicode to English layout in connection settings, I can do 
> keyboard shortcuts but unfortunately some signs doesn't match when I use RU 
> layout, for example instead of period sign I got Russian letter "ю". 
> The keyboard layouts on remote and local machine are identical, that's 100%, 
> tested many times on different clean windows 10 installs, on work, on VMs, on 
> friend's PCs, etc. The issue always the same.
> As I can see Russian layout isn't presented in Guacamole connection settings 
> by itself so it would be highly appreciated if you can suggest any workaround 
> for Russian users.



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

Reply via email to