GNU bug report logs -
#64270
30.0.50; Font update for no toolkit menu
Previous Next
Reported by: Manuel Giraud <manuel <at> ledu-giraud.fr>
Date: Sat, 24 Jun 2023 17:01:02 UTC
Severity: normal
Found in version 30.0.50
Fixed in version 30.1
Done: Manuel Giraud <manuel <at> ledu-giraud.fr>
Bug is archived. No further changes may be made.
Full log
Message #20 received at 64270 <at> debbugs.gnu.org (full text, mbox):
Manuel Giraud <manuel <at> ledu-giraud.fr> writes:
> Po Lu <luangruo <at> yahoo.com> writes:
>
>> Manuel Giraud <manuel <at> ledu-giraud.fr> writes:
>>
>>> I thought that the font's XLFD string would be a good candidate to pass
>>> this information since it should be understood by XLoadQueryFont. But
>>> unfortunately, the XLFD returned by font_unparse_xlfd are not.
>>>
>>> For instance, XLoadQueryFont can understand
>>> "-misc-fixed-medium-r-normal-*-22-*-*-*-*-*-*-*" but not
>>> "-misc-fixed-regular-r-normal-*-22-*-*-*-*-*-*-*". Do you think I need
>>> a function to « normalize » the XLFD returned by font_unparse_xlfd? Or
>>> maybe I'm missing something?
>>
>> I don't understand why you're trying to ``normalize'' the second invalid
>> XLFD: RELATIVE_SETWIDTH can't be `regular'.
>
> 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)
``XLFD'' strings generated by Emacs aren't guaranteed to be
X11-compatible; Emacs is only designed to read them. I don't remember
whether or not this is intentional, so you will have to ask Kenichi
Handa, but I have a sinking suspicion that he is not around anymore...
This bug report was last modified 1 year and 323 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.