unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Tim Ruffing <crypto@timruffing.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 67810@debbugs.gnu.org
Subject: bug#67810: 29.1; fonts use synthetic bold on Linux / pgtk
Date: Wed, 13 Dec 2023 16:09:15 +0100	[thread overview]
Message-ID: <7ea3f7db448191f2b9886604084abe84d0caaf61.camel@timruffing.de> (raw)
In-Reply-To: <83h6kmrzkz.fsf@gnu.org>



On Wed, 2023-12-13 at 15:39 +0200, Eli Zaretskii wrote:
> 
> Maybe this is done by the calls to the font backend with FC_EMBOLDEN
> parameter?  I'm no expert on these font backends, but maybe you could
> play with those calls and see if disabling them gets you what you
> want?  You can find the relevant code by searching the C sources for
> FC_EMBOLDEN.

Thanks for the suggestion, but no luck unfortunately. What also didn't
help is going back to Xft by configuring like this:
./configure --without-pgtk --without-cairo 

I don't know what to try next, I guess it will be useful to have
someone more familiar with the font stuff look at this. 








  reply	other threads:[~2023-12-13 15:09 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 [this message]
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
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=7ea3f7db448191f2b9886604084abe84d0caaf61.camel@timruffing.de \
    --to=crypto@timruffing.de \
    --cc=67810@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    /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).