From: "Štěpán Němec" <stepnem@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 3179@debbugs.gnu.org, jidanni@jidanni.org
Subject: bug#3179: Entering Chinese "zero": add U+3007
Date: Mon, 14 Oct 2019 18:55:07 +0200 [thread overview]
Message-ID: <87y2xnb72s.fsf@gmail.com> (raw)
In-Reply-To: <87eezga3oy.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sun, 13 Oct 2019 20:41:17 +0200")
On Sun, 13 Oct 2019 20:41:17 +0200
Lars Ingebrigtsen wrote:
> jidanni@jidanni.org writes:
>
>> With locale zh_TW.UTF-8 and toggle-input-method, we can type
>> Possible completion and corresponding characters are:
>> ling2:(1/6) 1.零 2.玲 3.靈 4.鈴 5.齡 6.陵 7.凌 8.菱 9.聆 0.羚...
>> (6/6) 1.駖 2.蕶 3.爧 4.堎 5.○
>>
>> Useful when one wants to type the year 2003:
>> 公文都有「二○○三年」,非「二零零三年」。
>>
>> But in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=427519
>> MH> You probably want "〇" (U+3007) instead of "○" (U+25CB)
>> So maybe add that in addition (not instead).
>>
>> (And 0, 0...? nah.)
>
> I know nothing about this, but the suggestion is to use
>
> name: IDEOGRAPHIC NUMBER ZERO
>
> instead of
>
> name: WHITE CIRCLE
>
> I have no idea what that means. But there's:
>
> (eval-after-load "quail/PY-b5"
> '(quail-defrule "ling2" ?○ nil t))
>
> which has apparently been in Emacs ever since leim-ext.el was added.
Checking the commit history, the file was originally encoded in iso-2022
and I have no idea what "0!r" in that encoding amounts to, but in any
case, U+3007 is the standard way to write ideographic zero. Various
other similar-looking glyphs (in various encodings) can be found in its
place occasionally[1], but in this day and age I see no reason to
encourage that practice (so I suggest "instead", not "in addition" is
the way to go above).
[1] Cf. e.g. here (in Japanese):
https://hp.vector.co.jp/authors/VA000964/html/zero.htm
--
Štěpán (reading, writing and speaking Chinese (also as professional
translator and interpreter) and Japanese)
next prev parent reply other threads:[~2019-10-14 16:55 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 [this message]
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
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=87y2xnb72s.fsf@gmail.com \
--to=stepnem@gmail.com \
--cc=3179@debbugs.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).