Open ElonPark opened 1 year ago
Thanks for bringing this to our attention, @ElonPark. We appreciate your feedback, and we'll make sure to post any updates regarding this issue on this thread.
If you're experiencing the same issue, please add a 👍 to the original post at the top or comment with your details. This will help us track the number of users facing the same problem.
Additionally, if you'd like to receive notifications about any developments or resolutions related to this issue, please hit the subscribe button.
Thank you for your understanding, and we'll do our best to address this as soon as possible.
@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.
Thanks for the headsup @p-iknow I'll let the team know this is affecting many devs.
Hi! @dannyneira, has this issue been resolved?
My wrap terminal still doesn't display Korean folders and Korean filenames correctly like the issue above.
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.
ᐩ 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.
@dannyneira ping
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
Operating system
MacOS
Operating system and version
13.1.0
Shell Version
zsh 5.8.1 (x86_64-apple-darwin22.0)
Current Warp version
v0.2023.05.23.08.05.stable_00
Regression
No, this bug or issue has existed throughout my experience using Warp
Recent working Warp date
always
Additional context
No response
Does this block you from using Warp daily?
Yes, this issue prevents me from using Warp daily.
Is this a Warp specific issue? (i.e. does it happen in Terminal, iTerm, Kitty, etc.)
Yes, this I confirmed this only happens in Warp, not other terminals.
Warp Internal (ignore): linear-label:b8107fdf-ba31-488d-b103-d271c89cac3e
None