From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: 64270@debbugs.gnu.org, Manuel Giraud <manuel@ledu-giraud.fr>
Subject: bug#64270: 30.0.50; Font update for no toolkit menu
Date: Tue, 27 Jun 2023 16:55:39 +0800 [thread overview]
Message-ID: <87352d8et0.fsf@yahoo.com> (raw)
In-Reply-To: <871qhxe1h7.fsf@gmail.com> (Robert Pluim's message of "Tue, 27 Jun 2023 10:47:00 +0200")
Robert Pluim <rpluim@gmail.com> writes:
>>>>>> On Tue, 27 Jun 2023 10:37:30 +0200, Robert Pluim <rpluim@gmail.com> said:
>
>>>>>> On Tue, 27 Jun 2023 15:48:29 +0800, Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org> said:
> >>> Ah then I have a bug in Emacs' XLFD generation on my system. Here is
> >>> what I get with 'C-u C-x =':
> >>>
> >>> ftcrhb:-Misc-Fixed-regular-normal-normal-*-18-*-*-*-c-90-iso10646-1 (#x59)
>
> Robert> Po Lu> ``XLFD'' strings generated by Emacs aren't guaranteed to be
> Robert> Po Lu> X11-compatible; Emacs is only designed to read them. I don't remember
> Robert> Po Lu> whether or not this is intentional, so you will have to ask Kenichi
> Robert> Po Lu> Handa, but I have a sinking suspicion that he is not around anymore...
>
> Robert> For at least 15 years prior to Larsʼ changes to support 'medium'
> Robert> fonts, that would have returned
>
> Robert> ftcrhb:-Misc-Fixed-medium-normal-normal-*-18-*-*-*-c-90-iso10646-1 (#x59)
>
> I mean:
>
> ftcrhb:-Misc-Fixed-normal-normal-normal-*-18-*-*-*-c-90-iso10646-1 (#x59)
>
> Robert
Right, but the problem is different: X doesn't support medium at all,
but calls Emacs's `normal' `medium'. Here are all the valid values for
an XLFD:
0 Undefined
10 UltraLight
20 ExtraLight
30 Light
40 SemiLight
50 Medium
60 SemiBold
70 Bold
80 ExtraBold
90 UltraBold
next prev parent reply other threads:[~2023-06-27 8:55 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-24 17:00 bug#64270: 30.0.50; Font update for no toolkit menu Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-24 17:16 ` Eli Zaretskii
2023-06-27 7:04 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-27 11:26 ` Eli Zaretskii
2023-06-27 14:13 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-27 15:54 ` Eli Zaretskii
2023-06-27 16:07 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-27 18:18 ` Eli Zaretskii
2023-06-28 0:28 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-28 7:50 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-28 9:20 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-28 7:38 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-25 0:36 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-27 7:08 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-27 7:48 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-27 8:25 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-27 8:37 ` Robert Pluim
2023-06-27 8:47 ` Robert Pluim
2023-06-27 8:55 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-06-27 9:42 ` Robert Pluim
2023-06-27 9:49 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-27 9:53 ` Robert Pluim
2023-06-27 12:06 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-27 9:59 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-27 12:10 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-27 14:02 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-27 11:30 ` 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
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=87352d8et0.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=64270@debbugs.gnu.org \
--cc=luangruo@yahoo.com \
--cc=manuel@ledu-giraud.fr \
--cc=rpluim@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).