-
Notifications
You must be signed in to change notification settings - Fork 305
Description
This issue has been migrated from old Barrier Github repository debauchee/barrier#527
Issue created on: 2019-12-20 by @fthdgn
Issue last updated on: 2021-01-10
Operating Systems
Server: Windows 10 Pro 1909 18363.535
Client: macOS Catalina 10.15.1
Barrier Version
Server: 2.3.2-snapshot-210c2b70
Client: 2.3.2-Release-210c2b70
Steps to reproduce bug
My server and server keyboard is Turkish-Q. These keyboards work without problem on their own devices.
However, my server keyboard cannot type some Turkish characters on on my client.
I put the problematic buttons on the table below.
Server versions are correct, expected characters.
Client versions are current wrong behavior.
"Location on the keyboard" is the location of the button on the keyboard according to English layout.
Server upper-case | Server lower-case | Client upper-case | Client lower-case | Location on the keyboard |
---|---|---|---|---|
I (U+0049) | ı (U+0131) | I (U+0049) | i (U+0069) | Same place of I |
İ (U+0130) | i (U+0069) | I (U+0049) | i (U+0069) | Two button right of L |
Ş (U+015E) | ş (U+015F) | S (U+0053) | s (U+0073) | One button right of L |
Ğ (U+011E) | ğ (U+011F) | G (U+0047) | g (U+0067) | One button right of P |
Other Turkish characters like Üü, Öö, Çç work correctly.
Other information
When I use Mac as server and Windows as client, there is no problem. Turkish-Q keyboard of Mac can type every Turkish characters on Windows.
Commented on: 2020-01-07 by @AdrianVerde
On spanish keyboard, any dieresis character doesn't work (like Ü or ü), these are not a key on the keyboard, they are the normal letter (like U or u), preceded by shift + [The key just at the right of the Ñ key of the QWERTY spanish keyboard]
Commented on: 2020-03-31 by @farukcan
Same Problem. on Windows 10 Turkish Q Keyboard (both side)
Commented on: 2020-10-01 by @github-actions[bot]
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
Commented on: 2020-10-01 by @fthdgn
Yes, it is still a problem.
Client
macOS 10.15.6
Barrier 2.3.3-release-3395cca9
Server
Windows 10 Pro 2004 19041.508
Barrier 2.3.3-release-3395cca9
Commented on: 2020-10-02 by @AdrianVerde
Yes, it is still a problem.
Both client and server:
Windows 10 Pro 2004 19041.508
Barrier 2.3.3-release-3395cca9
Commented on: 2020-10-14 by @eugenegff
I’m sure that it is the same problem that was solved in pull request debauchee/barrier#910
Commented on: 2020-10-15 by @fthdgn
@eugenegff I've built your branch to try it. All keys type correct letters now.
Thank you.
Commented on: 2021-01-10 by @p12tic
This issue has been fixed in #910.
Closed on: 2021-01-10 by @p12tic