From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
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 21:12:40 +0800 [thread overview]
Message-ID: <871qam3dbr.fsf@yahoo.com> (raw)
In-Reply-To: <831qamka3m.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 12 Jan 2024 14:30:21 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
> 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.
I thought the OP's difficulties related to the rendering of icon fonts
without bold variants displayed in contexts where the bold attribute is
generally applied, which if true it can be removed, after which the
world's your lobster. Though if disabling the bold attribute for the
default face is indeed what OP wanted, providing this option exclusively
for fonts without bold variants (that is, subject to overstriking) would
create a fairly glaring deficiency.
next prev parent reply other threads:[~2024-01-12 13:12 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
2024-01-12 13:12 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
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=871qam3dbr.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=67810@debbugs.gnu.org \
--cc=crypto@timruffing.de \
--cc=eliz@gnu.org \
--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).