Alex313031 / Thorium-Win

Chromium fork for Windows named after radioactive element No. 90; Windows builds of https://github.com/Alex313031/Thorium
https://thorium.rocks/
BSD 3-Clause "New" or "Revised" License
1.28k stars 33 forks source link

Vietnamese keyboard support #133

Open quan1232004 opened 7 months ago

quan1232004 commented 7 months ago

Problem Normally when you type Vietnamese in any app, the keyboard app will put a diacritic character in and delete the character that has no diacritic. But Thorium doesn't. I tried changing the settings but nothing helps (any browser works that way but Thorium doesn't)

Screenshots

image As you can see the non-diacritic character "a" is not automatically deleted

phucho0237 commented 5 months ago

Problem Normally when you type Vietnamese in any app, the keyboard app will put a diacritic character in and delete the character that has no diacritic. But Thorium doesn't. I tried changing the settings but nothing helps (any browser works that way but Thorium doesn't)

Screenshots

image As you can see the non-diacritic character "a" is not automatically deleted

Don't use the Windows default Vietnamese keyboard. Use Unikey or EVKey instead.

MinhBui2002 commented 3 months ago

I encoutered this problem, too. I have tried using both Unikey and EVKey but the problem still happens. I tried on Chrome and everything seem to be working.

phucho0237 commented 3 months ago

As you can see, it worked for me when I used Evkey.

https://github.com/Alex313031/Thorium-Win/assets/88989555/3e856aec-0581-4b34-abf9-91c3c658372a

MinhBui2002 commented 3 months ago

Here I also use EVKey and when I tried to type "mã", it always appears 2a. It also doesn't work when i tried "mâ", it shows "maâ" instead.

https://github.com/Alex313031/Thorium-Win/assets/88824973/7c47cede-2456-4781-8be2-2c4521bab270

phucho0237 commented 3 months ago

I don't have that issue.

https://github.com/Alex313031/Thorium-Win/assets/88989555/a1539718-23fe-4796-af9b-763a0b1ef4bf

MinhBui2002 commented 3 months ago

Well, I have found a workaround is installing OpenKey. Not sure when the problem will happen again.