From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: crypto@timruffing.de, 67810@debbugs.gnu.org, stefankangas@gmail.com
Subject: bug#67810: 29.1; fonts use synthetic bold on Linux / pgtk
Date: Fri, 12 Jan 2024 14:30:21 +0200 [thread overview]
Message-ID: <831qamka3m.fsf@gnu.org> (raw)
In-Reply-To: <875xzy3frj.fsf@yahoo.com> (message from Po Lu on Fri, 12 Jan 2024 20:20:00 +0800)
> From: Po Lu <luangruo@yahoo.com>
> Cc: crypto@timruffing.de, stefankangas@gmail.com, 67810@debbugs.gnu.org
> Date: Fri, 12 Jan 2024 20:20:00 +0800
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > If we do introduce such a variable, wouldn't it prevent Emacs from
> > generating the missing variants?
>
> On the contrary: if the generation of such variants by the font backend
> is inhibited, Emacs will display bold text with overstriking, when these
> variants are absent from the font itself.
>
> I should clarify that "generation" refers to the automatic generation of
> oblique or bold fonts undertaken by a handful of our font backends, not
> the overstriking implemented in xfaces.c.
Then we are mis-communicating, I think: I was talking about the code
in xfaces.c to which you pointed up-thread:
> > Can you point me at the place in the code where we do this?
>
> Yes, see lines 6192 and 6045 in xfaces.c, viz.:
>
> if (face->font
> && FONT_WEIGHT_NAME_NUMERIC (attrs[LFACE_WEIGHT_INDEX]) > 100
> && FONT_WEIGHT_NUMERIC (attrs[LFACE_FONT_INDEX]) <= 100)
> face->overstrike = true;
>
> and
>
> face->overstrike
> = (! NILP (font_object)
> && FONT_WEIGHT_NAME_NUMERIC (face->lface[LFACE_WEIGHT_INDEX]) > 100
> && FONT_WEIGHT_NUMERIC (font_object) <= 100);
I ws suggesting to introduce a variable that would inhibit this.
> > And wouldn't avoiding to generate them do what the OP wanted,
> > i.e. have a default face's font where bold looks like regular?
>
> No, see above. However, the matter at hand is that I can't understand
> the deficiency OPs request is supposed to address. Surely, if the
> author of a package which inserts icons wishes that they not be bold,
> the package should set the face by which they are displayed to one that
> isn't?
AFAIU, the OP's request was to allow to have a default font that lacks
the bold variant, so that the bold face attribute could be displayed
in some other way, or maybe not at all.
next prev parent reply other threads:[~2024-01-12 12:30 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-13 12:03 bug#67810: 29.1; fonts use synthetic bold on Linux / pgtk Tim Ruffing
2023-12-13 12:39 ` Eli Zaretskii
2023-12-13 13:28 ` Tim Ruffing
2023-12-13 13:39 ` Eli Zaretskii
2023-12-13 15:09 ` Tim Ruffing
2023-12-13 15:43 ` Tim Ruffing
2023-12-14 0:09 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-14 7:28 ` Eli Zaretskii
2023-12-14 9:32 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-14 9:54 ` Tim Ruffing
2023-12-14 10:04 ` Eli Zaretskii
2023-12-14 10:37 ` Tim Ruffing
2023-12-14 11:19 ` Eli Zaretskii
2023-12-14 11:26 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-14 15:06 ` Tim Ruffing
2023-12-14 22:55 ` Stefan Kangas
2024-01-11 15:50 ` Tim Ruffing
2024-01-12 1:46 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-12 8:37 ` Eli Zaretskii
2024-01-12 9:59 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-12 11:46 ` Eli Zaretskii
2024-01-12 12:20 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-12 12:30 ` Eli Zaretskii [this message]
2024-01-12 13:12 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-12 14:12 ` Eli Zaretskii
2024-01-13 0:46 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-13 6:59 ` Eli Zaretskii
2024-01-14 1:02 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-14 6:24 ` Eli Zaretskii
2024-01-14 8:09 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-14 9:33 ` Eli Zaretskii
2024-01-14 13:44 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-14 14:03 ` Eli Zaretskii
2024-01-14 14:19 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-14 14:55 ` Eli Zaretskii
2024-01-15 13:11 ` Tim Ruffing
2024-01-13 6:37 ` Stefan Kangas
2024-01-14 0:55 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-14 5:23 ` Stefan Kangas
2024-01-14 10:20 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-14 12:21 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-14 14:10 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-14 16:37 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-15 0:36 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-15 13:56 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-15 14:02 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=831qamka3m.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=67810@debbugs.gnu.org \
--cc=crypto@timruffing.de \
--cc=luangruo@yahoo.com \
--cc=stefankangas@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).