From: SUKBEOM KIM <sukbeom.kim@gmail.com>
To: 66970@debbugs.gnu.org
Subject: bug#66970: 29.1; Overwrite-mode is not working with Korean characters
Date: Tue, 7 Nov 2023 08:19:53 +0900 [thread overview]
Message-ID: <559fe1a8-a18e-4d8c-81c3-78fd3bbddbcc@gmail.com> (raw)
In-Reply-To: <83bkc63jbh.fsf@gnu.org>
Yes, it is the problem only with typing via an input method.
I checked that there is no issue if I type Korean characters with iBus
(I guess this is the 'LEIM' what you mentioned).
>> Date: Tue, 7 Nov 2023 01:37:43 +0900
>> From: SUKBEOM KIM <sukbeom.kim@gmail.com>
>>
>> I forgot to provide the test sequence to reproduce the issue:
>>
>> 1 type 'aeiou' and <C-a>
>>
>> 2 <M-x> set-input-method and set to korean-hangul (2-beoksik)
>>
>> 3 <M-x> overwrite-mode.
>> Replace 'ae' to '아' and 'oi' to '에'. You can type them with typing 'dk', 'dp'.
>>
>> 4 I expected '아에u', but the actual result is '아에aeiou'.
>> Replacing Korean characters with alphabets is working but not vice versa.
> What happens if you type the Korean characters using a Korean
> keyboard, not via a Leim input method? Does it also not work? Or is
> the problem only with typing via an input method?
next prev parent reply other threads:[~2023-11-06 23:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-06 16:07 bug#66970: 29.1; Overwrite-mode is not working with Korean characters SUKBEOM KIM
2023-11-06 16:37 ` bug#66970: (no subject) SUKBEOM KIM
2023-11-06 17:03 ` Eli Zaretskii
2023-11-06 23:19 ` SUKBEOM KIM [this message]
2023-11-08 13:18 ` bug#66970: 29.1; Overwrite-mode is not working with Korean characters Eli Zaretskii
2023-11-08 0:48 ` bug#66970: (no subject) Sukbeom Kim
2023-11-06 16:41 ` bug#66970: 29.1; Overwrite-mode is not working with Korean characters Eli Zaretskii
2023-11-09 16:37 ` João Távora
2023-11-09 16:50 ` Eli Zaretskii
2023-11-10 0:34 ` Sukbeom Kim
2023-11-10 7:13 ` Eli Zaretskii
2023-11-10 22:32 ` Sukbeom Kim
2023-11-13 12:41 ` João Távora
2023-11-13 14:31 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=559fe1a8-a18e-4d8c-81c3-78fd3bbddbcc@gmail.com \
--to=sukbeom.kim@gmail.com \
--cc=66970@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).