From: Eli Zaretskii <eliz@gnu.org>
To: "Štěpán Němec" <stepnem@gmail.com>, "Kenichi Handa" <handa@gnu.org>
Cc: larsi@gnus.org, 3179@debbugs.gnu.org, jidanni@jidanni.org
Subject: bug#3179: Entering Chinese "zero": add U+3007
Date: Tue, 15 Oct 2019 16:00:19 +0300 [thread overview]
Message-ID: <8336fugo4c.fsf@gnu.org> (raw)
In-Reply-To: <87k196b4m4.fsf@gmail.com> (message from Štěpán Němec on Tue, 15 Oct 2019 14:00:35 +0200)
> From: Štěpán Němec <stepnem@gmail.com>
> Cc: 3179@debbugs.gnu.org, jidanni@jidanni.org
> Date: Tue, 15 Oct 2019 14:00:35 +0200
>
> On Tue, 15 Oct 2019 12:51:35 +0300
> Eli Zaretskii wrote:
>
> > Ming Hua gave no reasoning, and Štěpán said U+3007 is the standard way
> > to write ideographic zero. But why should we assume the intent here
> > was to use the ideographic zero?
>
> The intent (to write ideographic zero, not white circle) is quite clear,
> because that's what the key "ling2" means in Mandarin. As is usually the
> case in Chinese, ling2 can also mean a lot of other things, but white
> circle is not one of them.
>
> You can check with any Chinese or Japanese input method what suggestion
> you get for that key (in Japanese that'd be れい/rei). I, for example,
> use fcitx with mozc for Japanese and sunpinyin for Chinese, both of
> which do the right thing. (I don't normally use Emacs input methods for
> CJK languages, I find quail too limited for those and I suspect the same
> will be the case for other serious users, which might also be the reason
> for the lack of previous feedback.)
>
> That said, by all means, do check with Handa-san, I'm kind of curious
> myself.
Thanks, I've CC'ed him.
next prev parent reply other threads:[~2019-10-15 13:00 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87r5z8vgp1.fsf_-_@jidanni.org>
2009-05-01 18:10 ` bug#3179: Entering Chinese "zero": add U+3007 jidanni
2019-10-13 18:41 ` Lars Ingebrigtsen
2019-10-14 16:55 ` Štěpán Němec
2019-10-14 19:49 ` Lars Ingebrigtsen
2019-10-14 20:44 ` Štěpán Němec
2019-10-14 20:56 ` Lars Ingebrigtsen
2019-10-14 21:09 ` Štěpán Němec
2019-10-14 21:13 ` Lars Ingebrigtsen
2019-10-15 8:15 ` Eli Zaretskii
2019-10-15 8:26 ` Lars Ingebrigtsen
2019-10-15 9:51 ` Eli Zaretskii
2019-10-15 12:00 ` Štěpán Němec
2019-10-15 13:00 ` Eli Zaretskii [this message]
2019-10-26 10:12 ` Eli Zaretskii
2019-11-16 12:45 ` Eli Zaretskii
2019-11-28 13:18 ` handa
2019-11-28 15:44 ` Eli Zaretskii
2019-11-28 16:32 ` Štěpán Němec
2019-12-05 14:31 ` handa
2019-12-05 15:02 ` Štěpán Němec
2019-12-06 1:10 ` 積丹尼 Dan Jacobson
2019-12-06 2:55 ` 積丹尼 Dan Jacobson
2019-12-06 8:23 ` Štěpán Němec
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=8336fugo4c.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=3179@debbugs.gnu.org \
--cc=handa@gnu.org \
--cc=jidanni@jidanni.org \
--cc=larsi@gnus.org \
--cc=stepnem@gmail.com \
/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).