[GH-ISSUE #527] Some Turkish characters are transferred incorrectly #413

Closed
opened 2026-05-05 06:19:08 -06:00 by gitea-mirror · 8 comments
Owner

Originally created by @fthdgn on GitHub (Dec 20, 2019).
Original GitHub issue: https://github.com/debauchee/barrier/issues/527

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.

Originally created by @fthdgn on GitHub (Dec 20, 2019). Original GitHub issue: https://github.com/debauchee/barrier/issues/527 ### 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.
gitea-mirror 2026-05-05 06:19:08 -06:00
Author
Owner

@AdrianVerde commented on GitHub (Jan 7, 2020):

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]

<!-- gh-comment-id:571553947 --> @AdrianVerde commented on GitHub (Jan 7, 2020): 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]
Author
Owner

@farukcan commented on GitHub (Mar 31, 2020):

Same Problem. on Windows 10 Turkish Q Keyboard (both side)

<!-- gh-comment-id:606667992 --> @farukcan commented on GitHub (Mar 31, 2020): Same Problem. on Windows 10 Turkish Q Keyboard (both side)
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

<!-- gh-comment-id:701709326 --> @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
Author
Owner

@fthdgn commented on GitHub (Oct 1, 2020):

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

<!-- gh-comment-id:701719251 --> @fthdgn commented on GitHub (Oct 1, 2020): 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
Author
Owner

@AdrianVerde commented on GitHub (Oct 2, 2020):

Yes, it is still a problem.

Both client and server:
Windows 10 Pro 2004 19041.508
Barrier 2.3.3-release-3395cca9

<!-- gh-comment-id:702542003 --> @AdrianVerde commented on GitHub (Oct 2, 2020): Yes, it is still a problem. Both client and server: Windows 10 Pro 2004 19041.508 Barrier 2.3.3-release-3395cca9
Author
Owner

@eugenegff commented on GitHub (Oct 14, 2020):

I’m sure that it is the same problem that was solved in pull request https://github.com/debauchee/barrier/pull/910

<!-- gh-comment-id:708594869 --> @eugenegff commented on GitHub (Oct 14, 2020): I’m sure that it is the same problem that was solved in pull request https://github.com/debauchee/barrier/pull/910
Author
Owner

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

@eugenegff I've built your branch to try it. All keys type correct letters now.
Thank you.

<!-- gh-comment-id:708784431 --> @fthdgn commented on GitHub (Oct 15, 2020): @eugenegff I've built your branch to try it. All keys type correct letters now. Thank you.
Author
Owner

@p12tic commented on GitHub (Jan 10, 2021):

This issue has been fixed in #910.

<!-- gh-comment-id:757504382 --> @p12tic commented on GitHub (Jan 10, 2021): This issue has been fixed in #910.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/barrier#413
No description provided.