From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: emacs-devel@gnu.org
Subject: Re: master 15afa72460b: Fix 'script-representative-chars' for the 'han' script
Date: Mon, 05 Aug 2024 19:25:31 +0300 [thread overview]
Message-ID: <86y15bos1w.fsf@gnu.org> (raw)
In-Reply-To: <87le1dp2gb.fsf@yahoo.com> (message from Po Lu on Sun, 04 Aug 2024 08:16:20 +0800)
> From: Po Lu <luangruo@yahoo.com>
> Cc: emacs-devel@gnu.org
> Date: Sun, 04 Aug 2024 08:16:20 +0800
>
> >> > --- a/lisp/international/fontset.el
> >> > +++ b/lisp/international/fontset.el
> >> > @@ -208,8 +208,7 @@
> >> > (kana #x304B)
> >> > (bopomofo #x3105)
> >> > (kanbun #x319D)
> >> > - (han #x2e90 #x2f00 #x3010 #x3200 #x3300 #x3400 #x31c0 #x4e10
> >> > - #x5B57 #xfe30 #xf900)
> >> > + (han #x2e90 #x2f00 #x3200 #x3300 #x3400 #x4e10 #x5B57 #xfe30 #xf900)
> >>
> >> Someone reports that this set of characters still does not enable the
> >> detection of WenQuanYi Micro Hei, which is certainly complete enough to
> >> display all Han text that will be encountered in practice. U+2E90,
> >> U+2F00, U+3300 and U+3400 are absent from this font, and quite
> >> reasonably so, since they are freestanding radicals, Kana, which belong
> >> in the entry for kana rather than han, or obsolete.
> >
> > On what system did that happen?
>
> Not "what system", "which font": WenQuanYi Micro Hei, one of the better
> free Han fonts.
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?
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?
next prev parent reply other threads:[~2024-08-05 16:25 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 [this message]
2024-08-05 23:58 ` Po Lu
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
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=86y15bos1w.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@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).