From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: crypto@timruffing.de, 67810@debbugs.gnu.org
Subject: bug#67810: 29.1; fonts use synthetic bold on Linux / pgtk
Date: Thu, 14 Dec 2023 09:28:09 +0200 [thread overview]
Message-ID: <83y1dxqm46.fsf@gnu.org> (raw)
In-Reply-To: <s0d5y11odaw.fsf@yahoo.com> (message from Po Lu on Thu, 14 Dec 2023 08:09:11 +0800)
> From: Po Lu <luangruo@yahoo.com>
> Cc: Eli Zaretskii <eliz@gnu.org>, 67810@debbugs.gnu.org
> Date: Thu, 14 Dec 2023 08:09:11 +0800
>
> Tim Ruffing <crypto@timruffing.de> writes:
>
> > 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.
>
> There's no bug here: when a bold face is displayed by a font which
> doesn't provide a bold variant, Emacs overstrikes text displayed in that
> font to create visual contrast between the bold text and its
> surroundings. This is implemented independently of font backend
> features such as FC_EMBOLDEN.
Can you point me at the place in the code where we do this?
> If this contrast is undesirable, remove the weight attribute from the
> face.
We could have a variable exposed to Lisp to inhibit this overstriking,
if some users want that.
next prev parent reply other threads:[~2023-12-14 7:28 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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83y1dxqm46.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=67810@debbugs.gnu.org \
--cc=crypto@timruffing.de \
--cc=luangruo@yahoo.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.