✅ Korean characters disassembly issue

[Canorus]

👉 #1368

---

Before beginning I am aware that Apple's input methods have a TON of issues, so I just wish it's not their fault which makes it unapproachable for inidividual developers.

When typing Korean characters in WebSSH the result is different from other terminal: the characters won't assemble to create full character. It just remains consonant and vowels.

Please refer to the screencapture attached below. First line is typed in macbook with terminal application named Hyper and second on iPad with WebSSH

[isontheline]

Hi @Canorus 👋

Thanks for your detailed report and the screenshot, that helps a lot!

I agree—Apple’s input methods can be tricky, and I understand how frustrating it is when things work in one terminal but not another. I thought that #642 would have fixed these kind of composition issues, but it looks like WebSSH still lacks proper support for advanced character input (especially for languages like Korean, Japanese, and Chinese).

To be honest, I’m not a regular writer of Korean/Chinese/Japanese, so it’s sometimes difficult for me to reproduce and fully understand these problems. But your example is very clear! I’m opening a new issue from your discussion so I can track the progress, and I’ll continue looking for a solution. I can’t promise a quick fix, but I want WebSSH to work for everyone, regardless of language.

If you have any other insights, tools, or test cases that help narrow this down, please share them! Your help makes WebSSH better for everyone.

Have a nice day ☀️

Arnaud (WebSSH dev)

[Canorus]

That's great! Honestly I didn't expect such quick reply from you. As a Korean I do understand this kind of issue can take really long time and a lot of effort to fully addressed.

Just to make it sure it's not configuration issue serverside, I checked both on macOS and Ubuntu showing same issue. And I tried Apple's default keyboard to make it sure it's not external bluetooth keyboard that's acting up.

One way to check really quick if it's working as expected is : input keys in left red box and then right read box consecutively(that key in the middle belongs to left red box, sorry). It should combine keys rather than just aligning them horizontally like alphabets do.

One scenario I found online was when onChanged event triggered before IME finishes combination(Flutter). But I'm not sure if this has anything to do with WebSSH. I'll add here if anything comes up.

Thank you for making WebSSH. It's such a great app.

[isontheline]

Hi @Canorus 👋

Thank you so much for your kind words and for testing all these scenarios—that really helps! And thanks for clarifying it’s not a server-side or keyboard config issue. Your test cases and the screenshot are gold for tracking down this kind of tricky bug. 🙏

I’ll try reproducing the exact input sequence you shared (thanks for the visual, super helpful!). The tip about IME event timing is also interesting—I’ll look into whether Xterm.js (which WebSSH uses for rendering) is getting the correct composition events, or if something’s getting interrupted before the characters can fully combine.

I’ll keep digging, and if I find anything, I’ll update the GitHub issue. And of course, if you discover any more clues, feel free to add them!

Thanks again for your patience and for making WebSSH better.
Have a nice day ☀️

Arnaud