Skip to content
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

Tracker issue: Work on UTF-8 support. #860

Open
shymega opened this issue Aug 31, 2020 · 12 comments
Open

Tracker issue: Work on UTF-8 support. #860

shymega opened this issue Aug 31, 2020 · 12 comments
Labels
bsd/freebsd Related to FreeBSD bsd/openbsd Related to OpenBSD enhancement New feature or request help wanted Extra attention is needed linux Related to Linux macOS Related to macOS meta A collection of smaller related issues windows Related to Microsoft Windows

Comments

@shymega
Copy link

shymega commented Aug 31, 2020

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.

@jsantosdias
Copy link

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...

@shymega
Copy link
Author

shymega commented 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 shymega added the meta A collection of smaller related issues label Sep 15, 2020
@coquizen
Copy link

coquizen commented 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.

@pfactum
Copy link

pfactum commented 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.

@shymega
Copy link
Author

shymega commented May 30, 2021 via email

@pfactum
Copy link

pfactum commented May 31, 2021

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

@sgrienen
Copy link

"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...

@shymega
Copy link
Author

shymega commented Aug 17, 2021

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

@Unknown-Guy
Copy link

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?

@perroboc
Copy link

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 :(

@manngo
Copy link

manngo commented 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?

@shymega
Copy link
Author

shymega commented Nov 26, 2022

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bsd/freebsd Related to FreeBSD bsd/openbsd Related to OpenBSD enhancement New feature or request help wanted Extra attention is needed linux Related to Linux macOS Related to macOS meta A collection of smaller related issues windows Related to Microsoft Windows
Projects
None yet
Development

No branches or pull requests

8 participants