From: Eli Zaretskii <eliz@gnu.org>
To: Corwin Brust <corwin@bru.st>
Cc: 54685-done@debbugs.gnu.org
Subject: bug#54685: 28.0.92; incorrect font on new frame after menu-set-font (Win32)
Date: Sun, 03 Apr 2022 19:34:15 +0300 [thread overview]
Message-ID: <838rsmf7nc.fsf@gnu.org> (raw)
In-Reply-To: <CAJf-WoTG8mtmixXRr3gw+NXz4jmtSuHeZV3Yqfhv2bE=YCefhw@mail.gmail.com> (message from Corwin Brust on Sun, 3 Apr 2022 11:23:25 -0500)
> From: Corwin Brust <corwin@bru.st>
> Date: Sun, 3 Apr 2022 11:23:25 -0500
> Cc: 54685@debbugs.gnu.org
>
> > If so, then this is expected. The APIs we use on MS-Windows to
> > enumerate fonts in a font family consider only 4 font varieties to
> > belong to the same family: Regular, Italic, Bold, and Bold-Italic.
> > All the other varieties aren't returned by those APIs when we request
> > to list all the fonts in a family. (I don't know if this is just the
> > deficiency of the APIs we use, or a general issue with how fonts are
> > managed on Windows.) So any font variety that is not one of those 4
> > will cause trouble sooner or later. (Medium is special, because we
> > have an extra-special kludge to allow Medium when Regular is being
> > sought.)
> >
> > So I think what you see is expected: on Windows one cannot select a
> > Light (or Thin, or UltraLight, or SemiBold, or ...) font for the
> > default face and hope that it will work as expected.
>
> In which case I think this bug report can be closed. Thank you.
Done. I will at some time add a PROBLEMS entry about this.
next prev parent reply other threads:[~2022-04-03 16:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-02 23:48 bug#54685: 28.0.92; incorrect font on new frame after menu-set-font (Win32) Corwin Brust
2022-04-03 5:20 ` Eli Zaretskii
2022-04-03 14:49 ` Corwin Brust
2022-04-03 15:03 ` Eli Zaretskii
2022-04-03 15:53 ` Corwin Brust
2022-04-03 16:12 ` Eli Zaretskii
2022-04-03 16:23 ` Corwin Brust
2022-04-03 16:34 ` Eli Zaretskii [this message]
2022-04-15 12:39 ` 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=838rsmf7nc.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=54685-done@debbugs.gnu.org \
--cc=corwin@bru.st \
/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.