mirror of
https://github.com/debauchee/barrier.git
synced 2026-05-15 14:16:02 -06:00
[GH-ISSUE #1307] Some symbols (i.e. Umlauts and '°') don't work on client #1038
Labels
No labels
HiDPI
bounty
bsd/freebsd
bsd/openbsd
bug
bug
build-infra
cantfix
critical
doc
duplicate
enhancement
fix-available
from git
from release
good first issue
help wanted
installer/package
invalid
linux
macOS
meta
needs testing
pull-request
query
question
regression
regression
v2.4.0
windows
wontfix
work-in-progress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/barrier#1038
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Thomseeen on GitHub (Oct 5, 2021).
Original GitHub issue: https://github.com/debauchee/barrier/issues/1307
What happened?
Some symbols don't work on the client, specifically, as far as I tested, äöüß°.
The log is on client side, when those symbols/characters are typed in the given order.
Version
v2.3.3
Git commit hash (if applicable)
No response
If applicable, where did you install Barrier from?
Installer from GitHub page.
What OSes are you seeing the problem on? (Check all that apply)
Windows
What OS versions are you using?
Client and Server are Win10
Relevant log output
Any other information
Both Windows machines use english installations and english display language with german region settings and german keyboard layout. Some other issue mentioned changing the "Beta: Use Unicode UTF-8 for worldwide language support" setting in windows, which didn't help in either combination (on on both machine, off on both, on on one, off on one...)
@Thomseeen commented on GitHub (Oct 6, 2021):
Probably related to some reports in #1181
@Thomseeen commented on GitHub (Nov 15, 2021):
This seems to be fixed for me since v2.4.0.