From: Van Ly <van.ly@sdf.org>
To: Po Lu <luangruo@yahoo.com>
Cc: 53896@debbugs.gnu.org
Subject: bug#53896: 28.0.91; Icomplete Vertical Mode fails to preview "C-x 8 RET 8072"
Date: Sun, 13 Feb 2022 13:06:17 +0000 (UTC) [thread overview]
Message-ID: <65cccf59-6569-886a-76cb-1609f7e376@SDF.ORG> (raw)
In-Reply-To: <87pmnssgiq.fsf@yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 887 bytes --]
On Sat, 12 Feb 2022, Po Lu wrote:
> Eli Zaretskii <eliz@gnu.org> writes:
>
>> Sorry, I don't understand the relevance. Do you see any names in
>> those URLs, and if so, are those names in any way derived from the
>> Unicode character DB?
>
> I couldn't find any, FWIW.
>
=> https://humanum.arts.cuhk.edu.hk/Lexis/lexi-mf/search.php?word=聲
The above link shows two handfuls of I suppose address schemes for
that sign, U+8072 in unicode.
For me, the name
* <CJK Ideograph>
* CJK IDEOGRAPH-8072
is better than "No match" and I get the majority of people who never
process any CJK will suffer performance-wise were the horde of CJK
characters to match in part on insert-char. So, an opt-in toggle and
filter improves on the situation of a blank drop.
Maybe the relevant U+8072 slab from Unihan_Readings.txt can be
included in describe-char under "Unicode data".
--
vl
next prev parent reply other threads:[~2022-02-13 13:06 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 10:38 bug#53896: 28.0.91; Icomplete Vertical Mode fails to preview "C-x 8 RET 8072" Van Ly
2022-02-09 14:36 ` Eli Zaretskii
2022-02-10 1:58 ` Van Ly
2022-02-10 4:54 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-11 23:11 ` Van Ly
2022-02-12 0:48 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-12 7:13 ` Eli Zaretskii
2022-02-12 7:14 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-13 13:06 ` Van Ly [this message]
2022-02-13 13:14 ` Eli Zaretskii
2022-02-13 13:18 ` Van Ly
2022-02-13 13:52 ` Eli Zaretskii
2022-02-13 14:18 ` Van Ly
2022-02-13 16:36 ` Eli Zaretskii
2022-02-14 14:55 ` Van Ly
2022-02-15 1:04 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-15 11:28 ` Van Ly
2022-02-13 14:34 ` Van Ly
2022-02-13 14:54 ` Andreas Schwab
2022-02-14 14:47 ` Van Ly
2022-02-14 14:57 ` Andreas Schwab
2022-02-14 15:01 ` Van Ly
2022-02-14 15:17 ` Andreas Schwab
2022-02-15 11:13 ` Van Ly
2022-02-15 11:33 ` Andreas Schwab
2022-02-15 21:25 ` Van Ly
2022-02-13 16:38 ` Eli Zaretskii
2022-02-14 14:57 ` Van Ly
2022-02-14 17:02 ` Eli Zaretskii
2022-02-15 11:21 ` Van Ly
2022-02-15 11:40 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-15 21:30 ` Van Ly
2022-02-22 1:38 ` Lars Ingebrigtsen
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=65cccf59-6569-886a-76cb-1609f7e376@SDF.ORG \
--to=van.ly@sdf.org \
--cc=53896@debbugs.gnu.org \
--cc=luangruo@yahoo.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).