unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stephen Berman <stephen.berman@gmx.net>
Cc: luangruo@yahoo.com, rpluim@gmail.com,
	tomohisa.kuranari@gmail.com, 73363@debbugs.gnu.org
Subject: bug#73363: 30.0.91; CJK Font Rendering Behavior Changed
Date: Fri, 20 Sep 2024 09:12:02 +0300	[thread overview]
Message-ID: <86zfo27t1p.fsf@gnu.org> (raw)
In-Reply-To: <87setv76bp.fsf@gmx.net> (message from Stephen Berman on Thu, 19 Sep 2024 22:10:34 +0200)

> From: Stephen Berman <stephen.berman@gmx.net>
> Cc: Eli Zaretskii <eliz@gnu.org>,  Po Lu <luangruo@yahoo.com>,  Tomohisa
>  Kuranari <tomohisa.kuranari@gmail.com>,  73363@debbugs.gnu.org
> Date: Thu, 19 Sep 2024 22:10:34 +0200
> 
> On my GNU/Linux system:
> 
> emacs-29 -Q:
> "-WenQ-WenQuanYi Zen Hei-medium-normal-normal-*-13-*-*-*-*-0-iso10646-1"

For all 3 characters?  That is, Emacs selects the same font for han
and hangul characters?

> emacs-30 -Q and emacs-master -Q:
> "-GOOG-Noto Sans JP-regular-normal-normal-*-13-*-*-*-*-0-iso10646-1"
> 
> The WenQuanYi Zen Hei font is in /usr/share/fonts and the Noto Sans JP
> font is in ~/.local/share/fonts.

What happens in Emacs 30 if you prevent Emacs from using the font in
~/.local/share/fonts in some way?





  reply	other threads:[~2024-09-20  6:12 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-19 14:50 bug#73363: 30.0.91; CJK Font Rendering Behavior Changed Tomohisa Kuranari
2024-09-19 16:33 ` Eli Zaretskii
2024-09-19 17:02   ` Robert Pluim
2024-09-19 17:59     ` Eli Zaretskii
2024-09-19 20:10     ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-20  6:12       ` Eli Zaretskii [this message]
2024-09-20  8:21         ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-19 23:51     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-20  6:27       ` Eli Zaretskii
2024-09-20  8:44         ` Robert Pluim
2024-09-20 10:29           ` Eli Zaretskii
2024-09-20 11:07             ` Robert Pluim
2024-09-20 13:24               ` Eli Zaretskii
2024-09-20 13:42                 ` Robert Pluim
2024-09-20 13:53                   ` Eli Zaretskii
2024-09-20 14:03                     ` Robert Pluim
2024-09-20 11:59         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-20 12:08           ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-20 12:24             ` Robert Pluim
2024-09-20 13:50               ` Eli Zaretskii
2024-09-20 14:24                 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-20 15:41                   ` Eli Zaretskii

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=86zfo27t1p.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=73363@debbugs.gnu.org \
    --cc=luangruo@yahoo.com \
    --cc=rpluim@gmail.com \
    --cc=stephen.berman@gmx.net \
    --cc=tomohisa.kuranari@gmail.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).