Tracker issue: Work on UTF-8 support.

Question

Tracker issue: Work on UTF-8 support.

shymega opened this issue 4 years ago · comments

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 · Answer 1 · Sat Sep 12 2020 04:34:09 GMT+0800 (China Standard Time)

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

Dom Rodriguez · Answer 2 · Sun Sep 13 2020 02:18:05 GMT+0800 (China Standard Time)

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.

Ian C · Answer 3 · Tue Mar 09 2021 03:33:24 GMT+0800 (China Standard Time)

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.

Oleksandr Natalenko · Answer 4 · Wed Apr 21 2021 14:14:33 GMT+0800 (China Standard Time)

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.

Dom Rodriguez · Answer 5 · Mon May 31 2021 05:16:14 GMT+0800 (China Standard Time)

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 <#860 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAKF2QBW4Y7FIJ5G5BGYFYDTJZUNTANCNFSM4QQAHDZA>.

-- Kind regards, dom rodriguez (shymega)

Oleksandr Natalenko · Answer 6 · Mon May 31 2021 14:04:38 GMT+0800 (China Standard Time)

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

Stéphane Grienenberger · Answer 7 · Wed Aug 18 2021 00:07:11 GMT+0800 (China Standard Time)

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

Dom Rodriguez · Answer 8 · Wed Aug 18 2021 00:49:43 GMT+0800 (China Standard Time)

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

Unknown-Guy · Answer 9 · Thu Sep 16 2021 19:35:35 GMT+0800 (China Standard Time)

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 · Answer 10 · Tue Jan 18 2022 03:42:59 GMT+0800 (China Standard Time)

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

Mark Simon · Answer 11 · Wed Nov 16 2022 09:33:38 GMT+0800 (China Standard Time)

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?

Dom Rodriguez · Answer 12 · Sun Nov 27 2022 05:28:23 GMT+0800 (China Standard Time)

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