From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 44316@debbugs.gnu.org, stefankangas@gmail.com
Subject: bug#44316: 26.3; Faces `fixed-pitch' and `fixed-pitch-serif' are opposite what they should be
Date: Sun, 01 Nov 2020 17:27:19 +0200 [thread overview]
Message-ID: <83r1pdf67c.fsf@gnu.org> (raw)
In-Reply-To: <87blghdzb9.fsf@gnus.org> (message from Lars Ingebrigtsen on Sun, 01 Nov 2020 13:41:30 +0100)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: stefankangas@gmail.com, 44316@debbugs.gnu.org
> Date: Sun, 01 Nov 2020 13:41:30 +0100
>
> > The other part of the problem, which could be Windows-specific, is
> > that the MS-Windows font back-ends don't know about "Mono Serif"
> > family. Do you always get a font with serifs when the family is "Mono
> > Serif"? If so, we could perhaps teach MS-Windows do the same. But
> > the result might be that both faces get the same font -- are we okay
> > with that? One place where that could matter is in Info.
>
> It looks like DejaVu Mono only has one variation, and it's... with
> serifs?
No, it's without serifs, AFAICS.
But that's not what I was asking: the "Mono Serif" family could
include more than just DejaVu Mono. I'm asking whether asking for
that family always brings fonts with serifs, or sometimes you get
fonts without serifs? If you get DejaVu Mono, I guess the answer is
"the latter"?
next prev parent reply other threads:[~2020-11-01 15:27 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-29 21:00 bug#44316: 26.3; Faces `fixed-pitch' and `fixed-pitch-serif' are opposite what they should be Drew Adams
2020-10-29 21:27 ` Drew Adams
2020-10-31 8:52 ` Eli Zaretskii
2020-10-29 22:10 ` Stefan Kangas
2020-10-29 22:22 ` Drew Adams
2020-10-29 22:31 ` Stefan Kangas
2020-10-29 22:50 ` Drew Adams
2020-10-30 0:45 ` Stefan Kangas
2020-10-30 12:55 ` Lars Ingebrigtsen
2020-10-30 13:26 ` Eli Zaretskii
2020-10-30 13:45 ` Stefan Kangas
2020-10-30 13:48 ` Lars Ingebrigtsen
2020-10-31 8:51 ` Eli Zaretskii
2020-11-01 12:41 ` Lars Ingebrigtsen
2020-11-01 15:27 ` Eli Zaretskii [this message]
2020-11-02 15:09 ` Lars Ingebrigtsen
2020-11-02 16:03 ` Eli Zaretskii
2020-11-03 14:36 ` Lars Ingebrigtsen
2020-11-03 15:53 ` Eli Zaretskii
2020-11-05 14:57 ` Lars Ingebrigtsen
2020-11-05 15:39 ` Eli Zaretskii
2020-11-03 15:32 ` Stefan Kangas
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=83r1pdf67c.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=44316@debbugs.gnu.org \
--cc=larsi@gnus.org \
--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).