From: Eli Zaretskii <eliz@gnu.org>
To: Dan Jacobson <jidanni@jidanni.org>
Cc: 71822@debbugs.gnu.org
Subject: bug#71822: Feature request: fullwidth to halfwidth
Date: Sun, 30 Jun 2024 08:24:59 +0300 [thread overview]
Message-ID: <86wmm7gfys.fsf@gnu.org> (raw)
In-Reply-To: <87y16nvzvo.7.fsf@jidanni.org> (message from Dan Jacobson on Sun, 30 Jun 2024 12:04:07 +0800)
> From: Dan Jacobson <jidanni@jidanni.org>
> Cc: 71822@debbugs.gnu.org
> Date: Sun, 30 Jun 2024 12:04:07 +0800
>
> >>>>> "EZ" == Eli Zaretskii <eliz@gnu.org> writes:
> >> Have commands that can change wide to narrow,
> >> with the same ease as M-l.
> >> E.g., change 209M into 209M.
> >> and another command to do the opposite.
> >> OK, I guess they are called fullwidth and halfwidth.
>
> EZ> When would such commands be useful?
>
> We use them all the time in Chinese,
> 請由209M號門 Ugly
> 請由209M號門 Pretty
That's about use of the characters, not about the use cases for the
commands you proposed. Or maybe I don't understand the example, in
which case please elaborate.
> EZ> These characters are deliberately
> EZ> not the same, and not just different shapes of the same letters
> EZ> (unlike upper-case and lower-case letters).
>
> $ unicode 209M|grep Deco
> Decomposition: <wide> 0032
> Decomposition: <wide> 0030
> Decomposition: <wide> 0039
> Decomposition: <wide> 004D
Yes, and..?
I didn't ask whether Emacs has the requisite information, I asked
about the use cases for these commands. You presented none; instead,
you are lecturing me on basic Unicode attributes of characters and on
the reasons for having the wide ones. That is not helpful; I already
know all that. It definitely doesn't provide any rationale for having
such commands in Emacs.
next prev parent reply other threads:[~2024-06-30 5:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-28 9:06 bug#71822: Feature request: fullwidth to halfwidth Dan Jacobson
2024-06-28 13:45 ` Eli Zaretskii
2024-06-30 4:04 ` Dan Jacobson
2024-06-30 5:24 ` Eli Zaretskii [this message]
2024-06-30 8:23 ` Dan Jacobson
2024-06-30 8:30 ` Eli Zaretskii
2024-06-30 13:45 ` Dan Jacobson
2024-06-30 9:43 ` Kazuhiro Ito
2024-06-30 13:55 ` Dan Jacobson
2024-07-01 2:13 ` Stefan Kangas
2024-07-01 9:58 ` Dan Jacobson
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=86wmm7gfys.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=71822@debbugs.gnu.org \
--cc=jidanni@jidanni.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).