-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Japanese input doesn't work well in composer #7630
Comments
I think this might be the same issue as #7535 just with a different language. |
Hello @bwindels, I was just talking to Rick (@rxl881) over on matrix/riot.im and he asked me to point out what I had found. I can corroborate that I'm seeing input anomalies entering Japanese on latest macOS Safari. Using either the ever-popular ATOK IME or, the built-in macOS IME, when I try entering Japanese what I expect does not get entered at all. Depending on what I type, I can sometimes see the list that you usually see but, the characters just look jumbled in most cases. If I do get an entry that actually looks correct, and use arrow keys and Enter to "fix" it to the textarea, I get nothing. It just returns spaces. In the below screenshot, taken while entering Nihon in here, you can see after I switch to ATOK and type nihon, it gives me the most typical solution 日本 ready to be entered. I can use the arrows to select others, even unicode emoji. ATOK has a nice dictionary function as well, where the definition pops out to the right. This is great because there are a lot of homonyms in Japanese. But in riot.im, when I enter nihon, it kind of appears backwards and selecting it does nothing. Hopefully it's visible here: |
Yeah, it's entering right to left. n |
Today I tested again in riot.im, and now I can enter Japanese correctly. Something got fixed? |
Oops, I spoke too soon. This does not work in latest macOS Safari (Version 12.0.1 (14606.2.104.1.1)) but, does work in latest macOS Firefox (Quantum 63.0.1 (64-bit)). The other day, I must have tested in Safari... Sorry for the confusion. |
Also works ok in Chrome Version 70.0.3538.102 (Official Build) (64-bit) |
very much still having this issue. Windows 10 recent Build Issue happens with all team members only on Windows Client |
craigmyster reported the issue on #riot:
I verified, after setting up a japanese keyboard (I used kana kanji variant/hiragana input method) under Gnome 3.28, typing "hello" on https://www.slatejs.org/#/rich-text yields ”へぉ", while in the riot.im/develop composer I see things appearing and disappearing but after having typed "hello" completely, the composer is empty. I don't know any japanese but that doesn't seem right.
The text was updated successfully, but these errors were encountered: