From: Po Lu <luangruo@yahoo.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: master 15afa72460b: Fix 'script-representative-chars' for the 'han' script
Date: Tue, 06 Aug 2024 07:58:54 +0800 [thread overview]
Message-ID: <87sevio729.fsf@yahoo.com> (raw)
In-Reply-To: <86y15bos1w.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 05 Aug 2024 19:25:31 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> If you remove U+2E90, U+2F00, U+3300 and U+3400 from the list and
> rebuild Emacs, what happens if you insert U+2F75? Does Emacs succeed
> to find another font which support that codepoint or does it appear as
> tofu? If the latter, what happens if you in install some additional
> font which does support U+2F75?
I'll ask, but my intuition is that no font will be discovered, since a
font must support all of any characters defined as lists in
script-representative-chars to be eligible.
> IOW, I'm interested to know what happens on GNU/Linux if more than one
> font is available that together cover both the "usual" han characters
> and those additional ones which you think we should remove from
> script-representative-chars, but neither of these fonts supports all
> of those characters. Can Emacs solve this by itself on GNU/Linux, or
> does it need "help" from the user's customization of the fontset?
Probably the latter, unless `han' is divided into scripts for
characters, obsolete characters, radicals, and the like.
next prev parent reply other threads:[~2024-08-05 23:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <172267024373.1752.11669700725951474437@vcs2.savannah.gnu.org>
[not found] ` <20240803073044.42052C1CAF7@vcs2.savannah.gnu.org>
2024-08-03 9:27 ` master 15afa72460b: Fix 'script-representative-chars' for the 'han' script Po Lu
2024-08-03 15:23 ` Eli Zaretskii
2024-08-04 0:16 ` Po Lu
2024-08-04 4:57 ` Eli Zaretskii
2024-08-04 7:58 ` Po Lu
2024-08-05 16:25 ` Eli Zaretskii
2024-08-05 23:58 ` Po Lu [this message]
2024-08-06 11:35 ` Eli Zaretskii
2024-08-07 0:17 ` Po Lu
2024-08-07 11:47 ` Eli Zaretskii
2024-08-07 12:12 ` Po Lu
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sevio729.fsf@yahoo.com \
--to=luangruo@yahoo.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.