unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Štěpán Němec" <stepnem@gmail.com>
To: 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: Thu, 05 Dec 2019 16:02:44 +0100	[thread overview]
Message-ID: <87zhg6stm3.fsf@gmail.com> (raw)
In-Reply-To: <875ziuzvx0.fsf@gnu.org>

On Thu, 05 Dec 2019 23:31:07 +0900
handa wrote:

> In article <87wobkotbq.fsf@gmail.com>, Štěpán Němec <stepnem@gmail.com> writes:
>
>> > Thanks, I added U+25CB to "wan2".
>
>> Please don't, that is a Japanism.
>
>> While one of the meanings of 丸 (when read "maru") in _Japanese_ is
>> "circle", the same is not true for Chinese.
>
> Oops, sorry.  As some site showed me one of the Chinese translations of
> 丸 is ball, I thought it was ok.  I tried Google translatetion, and
> CIRCLE was translated to 圈 (Quān).  So, perhaps adding to "quan1" is
> correct, right?

Adding ○ (U+25CB) to quan1 would be less surprising I suppose, but I
really don't see any reason to have it anywhere. While not having
IDEOGRAPHIC NUMBER ZERO could be considered an omission or even bug, as
it is quite ubiquitous and a common way to write ling2 (in the meaning
"zero") in Chinese numerals, adding U+25CB is more similar to adding
various emoji or heart symbols to xin1 or a flower to hua1 or what have
you, i.e. definitely not necessary and AFAICT the py-b5 input method
doesn't do that for other symbols, either.

-- 
Štěpán





  reply	other threads:[~2019-12-05 15:02 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
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 [this message]
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=87zhg6stm3.fsf@gmail.com \
    --to=stepnem@gmail.com \
    --cc=3179@debbugs.gnu.org \
    --cc=handa@gnu.org \
    --cc=jidanni@jidanni.org \
    --cc=larsi@gnus.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).