GNU bug report logs - #67810
29.1; fonts use synthetic bold on Linux / pgtk

Previous Next

Full log

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: Po Lu <luangruo <at> yahoo.com>
Cc: crypto <at> timruffing.de, 67810 <at> debbugs.gnu.org, stefankangas <at> gmail.com
Subject: Re: bug#67810: 29.1; fonts use synthetic bold on Linux / pgtk
Date: Fri, 12 Jan 2024 10:37:13 +0200

> From: Po Lu <luangruo <at> yahoo.com>
> Cc: Stefan Kangas <stefankangas <at> gmail.com>,  Eli Zaretskii <eliz <at> gnu.org>,
>   67810 <at> debbugs.gnu.org
> Date: Fri, 12 Jan 2024 09:46:21 +0800
> 
> Tim Ruffing <crypto <at> timruffing.de> writes:
> 
> > @Po Lu:
> > Independent of icons, I still think that overstriking is a bit
> > unexpected. (I mean, even Eli didn't know about it.) I see that a font
> > regex is too much, but do you think a simple boolean option would be a
> > good idea? Or do you think the current behavior should simply be
> > documented more prominently?
> 
> I think this is a mechanism users should not understand in this much
> technical detail, because font backends might synthesize their bold or
> oblique variants by other means when one is requested from a font that
> doesn't provide them.  Rather, users should understand that Emacs will
> seek to display bold text when they specify it should, and that text
> which isn't meant to be bold text should not receive text properties
> labeling it as such.

Would it make sense to introduce a variable that disables synthesizing
bold or oblique font variants?

Previous Next

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