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

Vietnamese keyboard support #133

Open
quan1232004 opened this issue Nov 30, 2023 · 6 comments
Open

Vietnamese keyboard support #133

quan1232004 opened this issue Nov 30, 2023 · 6 comments

Comments

@quan1232004
Copy link

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
Copy link

phucho0237 commented Jan 8, 2024

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
Copy link

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
Copy link

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

Recording.2024-04-03.094044.mp4

@MinhBui2002
Copy link

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.

New.Tab.-.Thorium.2024-04-03.09-44-51.mp4

@phucho0237
Copy link

I don't have that issue.

Recording.2024-04-03.121209.mp4

@MinhBui2002
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants