-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Some Turkish characters are transferred incorrectly #527
Comments
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] |
Same Problem. on Windows 10 Turkish Q Keyboard (both side) |
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 |
Yes, it is still a problem. Client Server |
Yes, it is still a problem. Both client and server: |
I’m sure that it is the same problem that was solved in pull request #910 |
@eugenegff I've built your branch to try it. All keys type correct letters now. |
This issue has been fixed in #910. |
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.
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.
The text was updated successfully, but these errors were encountered: