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: 67269@debbugs.gnu.org
Subject: bug#67269: 30.0.50; italic face fallback does not assume italic properties
Date: Mon, 20 Nov 2023 08:22:35 +0800 [thread overview]
Message-ID: <s0dil5xnuic.fsf@yahoo.com> (raw)
In-Reply-To: <83wmudkihf.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 19 Nov 2023 14:58:20 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
> Then maybe we should change the default fontset's definition on
> Android (if those are the systems you have in mind). We already do
> that for w32, see w32-standard-fontset-spec as opposed to
> standard-fontset-spec.
The systems I have in mind aren't only Android: Noto Sand Mono is the
default (or only) Monospace font on many GNU/Linux systems as well, and
I've also witnessed DejaVu Sans Mono being installed without an Italic
variant.
> I don't understand how shr-tag-i is relevant. I'm probably missing
> something.
It combines a variable pitch face with italic, and so loses when the
italic face doesn't support slant properties, even if the variable pitch
one does.
next prev parent reply other threads:[~2023-11-20 0:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87jzqejn8f.fsf.ref@yahoo.com>
2023-11-19 6:01 ` bug#67269: 30.0.50; italic face fallback does not assume italic properties Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-19 6:37 ` Eli Zaretskii
2023-11-19 7:05 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-19 8:18 ` Eli Zaretskii
2023-11-19 12:37 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-19 12:58 ` Eli Zaretskii
2023-11-20 0:22 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-11-20 11:55 ` Eli Zaretskii
2023-11-20 12:00 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-25 10:31 ` Eli Zaretskii
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=s0dil5xnuic.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=67269@debbugs.gnu.org \
--cc=eliz@gnu.org \
--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.