Support for Korean language

[ElonPark]

Discord username (optional)

No response

Describe the bug

First of all, thank you for making a great terminal app. I use it every day and always appreciate it.

But unfortunately, there is a bug that causes severe lag when typing in Korean and the input is lost in the input itself.
This bug has been around since the earliest versions of warp, but has yet to be fixed.

To reproduce

Occurs when entering Korean

Expected behavior

Lag-free input, just like English input

Screenshots

2023-05-26.1.35.32.mov

[dannyneira]

To anyone else interested in this feature, please add a 👍 to the original post at the top to signal that you want this feature, and subscribe if you'd like to be notified.

[p-iknow]

@dannyneira

Recently, many developers in Korea have been switching from iTerm2 to Warp. However, a significant hurdle they face is the issue of proper Korean character rendering. This issue has been reported for a long time but still needs to be solved, which is disappointing. Many people say they would immediately switch to Warp if it had proper support for Korean characters. Even though it's not indicated with emojis, the popularity of Warp is evident through various blog posts written in Korean.

I hope the Korean rendering issue is resolved soon.

[dannyneira]

Thanks for the headsup @p-iknow I'll let the team know this is affecting many devs.

[Nzoth9]

Hi! @dannyneira, has this issue been resolved?

My wrap terminal still doesn't display Korean folders and Korean filenames correctly like the issue above.

[Zeta611]

I believe the word "significant delay" doesn't exactly describe the issue. It seems that Warp kinds of buffers jamos(자모, Korean characters) and then "flushes" them only if a full set of jamos to create a single letter and a following jamo is entered.

For instance, when I type ㄱ, ㅡ, ㄹ, nothing appears on the prompt. It is only after when I type ㅈ to see 글 on the prompt. But "ㅈ" is still not seen.

For context, a single Korean letter consists of two or three jamos, e.g., ㅇ+ㅣ to yield 이, ㄱ+l+ㅅ to yield 깃.
While typing, Warp should show every intermediate steps, i.e., ㄱ->기->깃. This is what Warp should do. iTerm, Apple Terminal, etc. all behave well in this manner.

[Zeta611]

ᐩ While the situation is not ideal, it technically is usable when Korean characters are used occasionally. However, when trying to use a text editor (like Vim) inside Warp to write documents mainly in Korean characters, Warp is barely usable. I'm resorting to iTerm; this is the only thing that prevents me from fully transitioning to Warp.

I recall there was a similar (but not identical) issue in a new web browser Arc which was resolved (video note here) recently.

I believe this issue affects all Korean developers out there, and really hope this gets fixed soon. I wouldn't hesitate to recommend this product to my colleagues when this issue gets resolved.

[ElonPark]

@dannyneira ping

[rei-h-kakaoent]

I'm also experiencing the same issue. As @Zeta611 mentioned, Korean characters only appear after typing the next jamo, making it difficult to use. Like others here, this is the only thing preventing me from fully switching to Warp. Looking forward to seeing this resolved!

[K-Diger]

When will this be fixed?

Is this an issue you've forgotten about?

I think this is a pretty critical bug for Korean users using the CLI Coding Agent.

[Zeta611]

Have been following this thread for 3yrs. Apparently they don't care for Korean users, too busy running the AI hype :)