github-starred/barrier

Fork 0

mirror of https://github.com/debauchee/barrier.git synced 2026-05-15 14:16:02 -06:00

[GH-ISSUE #860] Tracker issue: Work on UTF-8 support. #682

New issue

Open

opened 2026-05-05 06:55:43 -06:00 by gitea-mirror · 12 comments

gitea-mirror commented

2026-05-05 06:55:43 -06:00

Owner

Originally created by @shymega on GitHub (Aug 31, 2020).
Original GitHub issue: https://github.com/debauchee/barrier/issues/860

Currently, Barrier has limited UTF-8 support, and that has led to issues being reported with various languages being processed wrongly.

We need to work on this. I would like to get it in for the v2.4 release, or earlier.

Originally created by @shymega on GitHub (Aug 31, 2020). Original GitHub issue: https://github.com/debauchee/barrier/issues/860 Currently, Barrier has limited UTF-8 support, and that has led to issues being reported with various languages being processed wrongly. We need to work on this. I would like to get it in for the v2.4 release, or earlier.

gitea-mirror added the

labels 2026-05-05 06:55:43 -06:00

gitea-mirror commented

2026-05-05 06:55:46 -06:00

Author

Owner

@jsantosdias commented on GitHub (Sep 11, 2020):

So, I am Portuguese and My name is João. I installed Barrier and it never worked because user folder as an ~. I am trying to change user folder name, but it's too dificult... Please change so that barrier can work with those characters...

@jsantosdias commented on GitHub (Sep 11, 2020): So, I am Portuguese and My name is João. I installed Barrier and it never worked because user folder as an ~. I am trying to change user folder name, but it's too dificult... Please change so that barrier can work with those characters...

gitea-mirror commented

2026-05-05 06:55:49 -06:00

Author

Owner

@shymega commented on GitHub (Sep 12, 2020):

Hi, thanks for your comment. You can react to the original post with :+1:, rather than commenting, as that does not add constructive information to the issue.

Thank you.

@shymega commented on GitHub (Sep 12, 2020): Hi, thanks for your comment. You can react to the original post with `:+1:`, rather than commenting, as that does not add constructive information to the issue. Thank you.

gitea-mirror commented

2026-05-05 06:55:51 -06:00

Author

Owner

@coquizen commented on GitHub (Mar 8, 2021):

Just wanted to further add that this behavior also occurs when pasting from a linux host to a mac osx client (consistently in some apps but not all. Textedit, Firefox, Paste.app seems to process the paste correctly, iMessage however does not.

@coquizen commented on GitHub (Mar 8, 2021): Just wanted to further add that this behavior also occurs when pasting from a linux host to a mac osx client (consistently in some apps but not all. Textedit, Firefox, Paste.app seems to process the paste correctly, iMessage however does not.

gitea-mirror commented

2026-05-05 06:55:53 -06:00

Author

Owner

@pfactum commented on GitHub (Apr 21, 2021):

Will this address the fact that I cannot type Ǐǐ (i with caron) and ȷ (dotless j) through barrier, or I should create another issue for this?

I get can't map keycode to key id message in the debug log.

Thanks.

@pfactum commented on GitHub (Apr 21, 2021): Will this address the fact that I cannot type Ǐǐ (i with caron) and ȷ (dotless j) through barrier, or I should create another issue for this? I get `can't map keycode to key id` message in the debug log. Thanks.

gitea-mirror commented

2026-05-05 06:55:55 -06:00

Author

Owner

@shymega commented on GitHub (May 30, 2021):

Presumably that's Unicode? if so, yes, it should resolve that.

On Wed, Apr 21, 2021, at 7:14 AM, Oleksandr Natalenko wrote:

Will this address the fact that I cannot type Ǐǐ (i with caron) and ȷ
(dotless j) through barrier, or I should create another issue for this?
Thanks.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/debauchee/barrier/issues/860#issuecomment-823805810, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAKF2QBW4Y7FIJ5G5BGYFYDTJZUNTANCNFSM4QQAHDZA.

--
Kind regards,
dom rodriguez (shymega)

@shymega commented on GitHub (May 30, 2021): Presumably that's Unicode? if so, yes, it should resolve that. On Wed, Apr 21, 2021, at 7:14 AM, Oleksandr Natalenko wrote: > > > Will this address the fact that I cannot type Ǐǐ (i with caron) and ȷ > (dotless j) through barrier, or I should create another issue for this? > Thanks. > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <https://github.com/debauchee/barrier/issues/860#issuecomment-823805810>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAKF2QBW4Y7FIJ5G5BGYFYDTJZUNTANCNFSM4QQAHDZA>. > -- Kind regards, dom rodriguez (shymega)

gitea-mirror commented

2026-05-05 06:55:56 -06:00

Author

Owner

@pfactum commented on GitHub (May 31, 2021):

Well, yes, those symbols are from the Unicode table. Thanks for the answer.

@pfactum commented on GitHub (May 31, 2021): Well, yes, those symbols are from the Unicode table. Thanks for the answer.

gitea-mirror commented

2026-05-05 06:55:59 -06:00

Author

Owner

@sgrienen commented on GitHub (Aug 17, 2021):

"Le dollar n√©o-z√©landais ("kiwi") recule de 1,40% √† 0,6923 dollar am√©ricain mardi en fin d‚Äôapr√®s-midi, alors que le gouvernement a d√©cr√©t√© un confinement de 3 jours dans tout le pays."

"(AOF) - Le dollar néo-zélandais ("kiwi") recule de 1,40% à 0,6923 dollar américain mardi en fin d’après-midi, alors que le gouvernement a décrété un confinement de 3 jours dans tout le pays."

this is how it looks like when I copy paste from MacOS Big Sur 11.5.1 to Win10 20H2 via Barrier 2.3.3 (PC is server, Mac is client). Don't know if this helps tracking this issue down...

@sgrienen commented on GitHub (Aug 17, 2021): "Le dollar n√©o-z√©landais ("kiwi") recule de 1,40% √† 0,6923 dollar am√©ricain mardi en fin d‚Äôapr√®s-midi, alors que le gouvernement a d√©cr√©t√© un confinement de 3 jours dans tout le pays." vs "(AOF) - Le dollar néo-zélandais ("kiwi") recule de 1,40% à 0,6923 dollar américain mardi en fin d’après-midi, alors que le gouvernement a décrété un confinement de 3 jours dans tout le pays." this is how it looks like when I copy paste from MacOS Big Sur 11.5.1 to Win10 20H2 via Barrier 2.3.3 (PC is server, Mac is client). Don't know if this helps tracking this issue down...

gitea-mirror commented

2026-05-05 06:56:00 -06:00

Author

Owner

@shymega commented on GitHub (Aug 17, 2021):

This does help, as it gives an example of UTF-8 behaviour. Thank you! 🙌🏻

@shymega commented on GitHub (Aug 17, 2021): This does help, as it gives an example of UTF-8 behaviour. Thank you! 🙌🏻

gitea-mirror commented

2026-05-05 06:56:03 -06:00

Author

Owner

@Unknown-Guy commented on GitHub (Sep 16, 2021):

Maybe I am missing something, but suspect after #910 got merged, basically all my UTF-8 issues with dead key went away. My guess is most of the people does not use the builds from master, so maybe it is time for proper release?

@Unknown-Guy commented on GitHub (Sep 16, 2021): Maybe I am missing something, but suspect after #910 got merged, basically all my UTF-8 issues with dead key went away. My guess is most of the people does not use the builds from master, so maybe it is time for proper release?

gitea-mirror commented

2026-05-05 06:56:05 -06:00

Author

Owner

@perroboc commented on GitHub (Jan 17, 2022):

Just adding my 2 cents: I'm trying to run this, but by default it looks for info in my user folder (which has an Á):

PS C:\Program Files\Barrier> .\barriers.exe --help
Start the barrier server component.
[...]
If no configuration file pathname is provided then the first of the
following to load successfully sets the configuration:
  C:\Users\├ülvaro\AppData\Local\Barrier\barrier.sgc
  C:\ProgramData\Barrier\barrier.sgc

As you can see, it prints ├ü instead of Á, because:
Á is the same as c3 81 in HEX (https://www.utf8-chartable.de/)
which in DEC is 195 129
which in Extended ASCII is ├ ü (https://www.asciitable.com/)

So, it seems it's not taking every UTF-8 byte into account, diving every 2 byte UTF-8 character into 2 ASCII characters, so maybe the reading of the path is correct, but the saving is wrong? I'll look, but I'm no cpp dev :(

@perroboc commented on GitHub (Jan 17, 2022): Just adding my 2 cents: I'm trying to run this, but by default it looks for info in my user folder (which has an Á): ``` PS C:\Program Files\Barrier> .\barriers.exe --help Start the barrier server component. [...] If no configuration file pathname is provided then the first of the following to load successfully sets the configuration: C:\Users\├ülvaro\AppData\Local\Barrier\barrier.sgc C:\ProgramData\Barrier\barrier.sgc ``` As you can see, it prints `├ü` instead of `Á`, because: `Á` is the same as `c3 81` in HEX (https://www.utf8-chartable.de/) which in DEC is `195 129` which in Extended ASCII is `├ ü` (https://www.asciitable.com/) So, it seems it's not taking every UTF-8 byte into account, diving every 2 byte UTF-8 character into 2 ASCII characters, so maybe the reading of the path is correct, but the saving is wrong? I'll look, but I'm no cpp dev :(

gitea-mirror commented

2026-05-05 06:56:06 -06:00

Author

Owner

@manngo commented on GitHub (Nov 16, 2022):

I have just installed 2.4.0-release-3e0d758b. Running between macOS Montery (server) and macOS Catalina (client). Copy & Paste work well enough (though not always on the first attempt). However Emojis such as 🦧👀🐵🙈 do not copy across. Other unicode characters such as 茶 are OK.

Is this the same issue as above?

@manngo commented on GitHub (Nov 16, 2022): I have just installed 2.4.0-release-3e0d758b. Running between macOS Montery (server) and macOS Catalina (client). Copy & Paste work well enough (though not always on the first attempt). However Emojis such as 🦧👀🐵🙈 do not copy across. Other unicode characters such as 茶 are OK. Is this the same issue as above?

gitea-mirror commented

2026-05-05 06:56:10 -06:00

Author

Owner

@shymega commented on GitHub (Nov 26, 2022):

I don't know, I work on Input Leap now - Barrier I'm not aware of UTF-8 being resolved yet.

@shymega commented on GitHub (Nov 26, 2022): I don't know, I work on Input Leap now - Barrier I'm not aware of UTF-8 being resolved yet.

No labels

Rows
Columns