[GH-ISSUE #481] Problem with russian language #375

New issue

Open

opened 2026-05-05 06:11:26 -06:00 by gitea-mirror · 5 comments

gitea-mirror commented

2026-05-05 06:11:26 -06:00

Owner

Originally created by @Copyrght on GitHub (Oct 29, 2019).
Original GitHub issue: https://github.com/debauchee/barrier/issues/481

Hi. I have problem with russian input language on macOS catalina with barrier client. Not all letters are currect. Buttons l ; ' [ ] \ z x c n m , . / ` and all SHIFT + number are still in english when i tiping on russian. Input method is Russian PC. Barrier version 2.3.2

Originally created by @Copyrght on GitHub (Oct 29, 2019). Original GitHub issue: https://github.com/debauchee/barrier/issues/481 Hi. I have problem with russian input language on macOS catalina with barrier client. Not all letters are currect. Buttons l ; ' [ ] \ z x c n m , . / ` and all SHIFT + number are still in english when i tiping on russian. Input method is Russian PC. Barrier version 2.3.2

gitea-mirror commented

2026-05-05 06:11:29 -06:00

Author

Owner

@ctsrc commented on GitHub (Nov 8, 2019):

I tested to see if I could reproduce this and I could in part, though some of the letters that didn't work for you worked for me and some differed that you didn't mention.

I tested with server running on macOS High Sierra 10.13.6 and client running on macOS Catalina 10.15.1.

What happens depends on which combination of input methods is used.

U.S. input method on server. U.S. input method on client. (What I normally use.) Results in normal U.S. output on client of course.
Russian PC input method on server. U.S. input method on client. Alphabetical and numerical keys output the same as they do with U.S. input method on server. Some of the symbols like ^ and & are different, while others like *, ( and ) are the same.
U.S. input method on server. Russian PC input method on client. This results in the behavior that you reported. A lot of the letters are Cyrillic as they should be (й, ц, у, к, е, н, etc) but some of them are not (c, l, d, m, v, z). Most of the symbols are the same as they are with U.S. English and some are different. I am guessing that this configuration might be the one you tried; U.S. input method on server, Russian PC input method on client.
Russian PC input method on server. Russian PC input method on client. This one seems to produce the correct letters and symbols for all of the buttons that I tried.

Additionally, when I started testing, I added the input methods with both server and client already running and when I first did that, no input was showing up on the client at all.

@Copyrght did you try quitting both the server and the client first, and setting both the host and the client to use Russian PC input method and then starting the server and the client? If you haven't tried that I suggest trying so.

Subsequent to that, you should be able to switch back and forth between Russian PC and for example U.S., but you will need to change to the same input method on both computers each time you change input method. Restarting the server and the client was only necessary the first time after I added a new input method it looks like.

I think Barrier should be better at handling this if possible. But at least if doing as I suggested above works for you then you have a workaround for the problem.

@ctsrc commented on GitHub (Nov 8, 2019): I tested to see if I could reproduce this and I could in part, though some of the letters that didn't work for you worked for me and some differed that you didn't mention. I tested with server running on macOS High Sierra 10.13.6 and client running on macOS Catalina 10.15.1. What happens depends on which combination of input methods is used. - U.S. input method on server. U.S. input method on client. (What I normally use.) Results in normal U.S. output on client of course. - Russian PC input method on server. U.S. input method on client. Alphabetical and numerical keys output the same as they do with U.S. input method on server. Some of the symbols like `^` and `&` are different, while others like `*`, `(` and `)` are the same. - U.S. input method on server. Russian PC input method on client. This results in the behavior that you reported. A lot of the letters are Cyrillic as they should be (й, ц, у, к, е, н, etc) but some of them are not (c, l, d, m, v, z). Most of the symbols are the same as they are with U.S. English and some are different. I am guessing that this configuration might be the one you tried; U.S. input method on server, Russian PC input method on client. - Russian PC input method on server. Russian PC input method on client. This one seems to produce the correct letters and symbols for all of the buttons that I tried. Additionally, when I started testing, I added the input methods with both server and client already running and when I first did that, no input was showing up on the client at all. @Copyrght did you try quitting both the server and the client first, and setting both the host and the client to use Russian PC input method and then starting the server and the client? If you haven't tried that I suggest trying so. Subsequent to that, you should be able to switch back and forth between Russian PC and for example U.S., but you will need to change to the same input method on both computers each time you change input method. Restarting the server and the client was only necessary the first time after I added a new input method it looks like. I think Barrier should be better at handling this if possible. But at least if doing as I suggested above works for you then you have a workaround for the problem.

gitea-mirror commented

2026-05-05 06:11:32 -06:00

Author

Owner

@Copyrght commented on GitHub (Nov 8, 2019):

So. Seems like when i switch both pc's on russian inputs all is ok. Problem with simbols are only when server side is on english input and client (mac) is on russian

@Copyrght commented on GitHub (Nov 8, 2019): So. Seems like when i switch both pc's on russian inputs all is ok. Problem with simbols are only when server side is on english input and client (mac) is on russian

gitea-mirror commented

2026-05-05 06:11:35 -06:00

Author

Owner

@ctsrc commented on GitHub (Nov 9, 2019):

Seems like when i switch both pc's on russian inputs all is ok.

Great!

@ctsrc commented on GitHub (Nov 9, 2019): > Seems like when i switch both pc's on russian inputs all is ok. Great!

gitea-mirror commented

2026-05-05 06:11:38 -06:00

Author

Owner

@github-actions[bot] commented on GitHub (Oct 1, 2020):

Is this issue still an issue for you? Please do comment and let us know! Alternatively, you may close the issue yourself if it is no longer an problem

@github-actions[bot] commented on GitHub (Oct 1, 2020): Is this issue still an issue for you? Please do comment and let us know! Alternatively, you may close the issue yourself if it is no longer an problem

gitea-mirror commented

2026-05-05 06:11:41 -06:00

Author

Owner

@kirilan commented on GitHub (Oct 15, 2020):

similar issue with 2.3.3 and Bulgarian (Traditional Phonetic) and both client and server in windows 10

when both are using Eng US everytghing works as normal, when either Server or Client PC are using Bulgarian all non-letter keys are working normally but no characters get sent to client. non-char keys work just fine.

@kirilan commented on GitHub (Oct 15, 2020): similar issue with 2.3.3 and Bulgarian (Traditional Phonetic) and both client and server in windows 10 when both are using Eng US everytghing works as normal, when either Server or Client PC are using Bulgarian all non-letter keys are working normally but no characters get sent to client. non-char keys work just fine.