GNU bug report logs - #73363
30.0.91; CJK Font Rendering Behavior Changed

Previous Next

Full log

Message #65 received at 73363 <at> debbugs.gnu.org (full text, mbox):

From: Po Lu <luangruo <at> yahoo.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: Robert Pluim <rpluim <at> gmail.com>, tomohisa.kuranari <at> gmail.com,
 73363 <at> debbugs.gnu.org
Subject: Re: bug#73363: 30.0.91; CJK Font Rendering Behavior Changed
Date: Fri, 20 Sep 2024 22:24:34 +0800

Eli Zaretskii <eliz <at> gnu.org> writes:

> Po Lu, why does it make sense to reject iso10646-1 in these cases?  I
> could perhaps understand why reject gb2312.1980-0 when we request
> something like jisx0208*-*, but iso10646-1 is supposed to support all
> the characters, so I don't understand the rationale for rejecting
> that.  And the same for unicode-bmp and unicode-sip, I think (although
> those are rarely used).

Because such font objects that are cached are subsequently rejected,
once Emacs detects that their registries do not agree with the font
specs'.  I don't recall where this rejection is implemented,
unfortunately.

> And what if the requested registry is ascii-0?  That one should match
> any registry, IMO.  If not, why not?

See above.

> More generally, what were the examples where you saw problems in
> accepting registries different from the requested one?  Also, if those
> problems are specific to certain platforms, how about making this test
> only on those platforms?  Font selection machinery in Emacs is
> delicate enough to try to "do no harm" first and foremost.

I tested my original reproducer, and it appears that the problem has
resolved of itself, probably because the performance of the sfnt font
driver has since improved.  Therefore I will disable this change
elsewhere than Android on the release branch, and remove it entirely on
master.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.