From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 3179@debbugs.gnu.org, stepnem@gmail.com, jidanni@jidanni.org
Subject: bug#3179: Entering Chinese "zero": add U+3007
Date: Tue, 15 Oct 2019 12:51:35 +0300 [thread overview]
Message-ID: <837e56gwuw.fsf@gnu.org> (raw)
In-Reply-To: <87wod6pg6n.fsf@gnus.org> (message from Lars Ingebrigtsen on Tue, 15 Oct 2019 10:26:56 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: stepnem@gmail.com, 3179@debbugs.gnu.org, jidanni@jidanni.org
> Date: Tue, 15 Oct 2019 10:26:56 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > I don't understand this decision. None of us knows enough about these
> > particular characters to tell U+25CB was a mistake (it was there since
> > day one of leim-ext.el), and the OP asked for _addition_ of U+3007.
> > So why did we replace instead of adding?
>
> We had the opinions of two people (Ming Hua <minghua@rice.edu> over at
> the Debian debbugs and Štěpán here) that IDEOGRAPHIC NUMBER ZERO made
> sense while WHITE CIRCLE didn't, so it didn't seem controversial.
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? (And the original file had U+25CB
there, in ISO-2022 encoding, that's definitely correct.)
next prev parent reply other threads:[~2019-10-15 9:51 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 [this message]
2019-10-15 12:00 ` Štěpán Němec
2019-10-15 13:00 ` Eli Zaretskii
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=837e56gwuw.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=3179@debbugs.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).