Korean input issue

[aca]

It seems korean input is broken in nightly.
Creating this issue in the hope that Korean users can gather, organize, and resolve related issues.

WIP

• fix: inconsistent behavior from legacy and kitty Key encoding #5728
• macos: requires two <esc> to exit insert mode in vim with korean ime. #1663

Fixed

• input: fix bs emitting sequence when it should not #1665
• input: do not emit sequence on <BS> when their's UTF-8 text #1659
• input: escape can be used to clear dead key state #1651
• apprt/gtk: commit buffer before "preeditchanged" resets #1594
• macos: handle preedit in AppKit, enables Korean input #856

cc @exploitJ @leokang94

[aca]

띄어쓰기시 글자가 지워지는 현상, linux/nixos/wayland/fcitx5

'한글<space>' // got: '한<space>', expect: '한글<space>'

[mitchellh]

#6772

[mitchellh]

I don't speak, read, or write Korean. Can you please help me by telling me what keys to press on a US keyboard layout with fcitx5? I can use that to debug this more easily. Thank you.

[leokang94]

Oh, to make it easier for you to understand, you can probably look at the dubeolsik as 2-set Korean and the sebeolsik as 3-set Korean. 😅

[mitchellh]

Inputting "dkssud" with 2-set and pressing "space" results in 안녕 for me.

[leokang94]

in nivm, could you type “dkssud” and BS BS BS right after?
expected is “안“, but it actually becomes “”.

This seems related to #5728 (more detailed report is #5312)

[mitchellh]

Yeah that's a separate known bug due to Kitty encoding.

[leokang94]

Ah, I misunderstood a little bit, you were referring to the <space> above, thanks for the clarification!