all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: luangruo@yahoo.com, 57962@debbugs.gnu.org
Subject: bug#57962: 29.0.50; Odd font choices
Date: Sun, 16 Oct 2022 14:17:55 +0300	[thread overview]
Message-ID: <83tu443tlo.fsf@gnu.org> (raw)
In-Reply-To: <874jw4jar9.fsf@gnus.org> (message from Lars Ingebrigtsen on Sun,  16 Oct 2022 12:58:18 +0200)

> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: luangruo@yahoo.com,  57962@debbugs.gnu.org
> Date: Sun, 16 Oct 2022 12:58:18 +0200
> 
> I've poked around some more here, experimenting with different fonts
> with -fn, and the thing is that everything works as expected with most
> fonts (i.e., the height of `fixed-pitch' and `default' fonts are the
> same, which is the problem, really) -- but with the default font in
> Ubuntu, "Ubuntu Mono", that's not the case.
> 
> So Emacs has chosen these two fonts for `default' and `fixed-pitch',
> respectively:
> 
>     ftcrhb:-DAMA-Ubuntu Mono-regular-normal-normal-*-48-*-*-*-m-0-iso10646-1 (#x2C)
>     ftcrhb:-PfEd-DejaVu Sans Mono-regular-normal-normal-*-48-*-*-*-m-0-iso10646-1 (#x26)
> 
> Is there something more Emacs could be doing to try to ensure that it
> picks equal-sized fonts?  By somehow looking at actual font metrics?

When we select a suitable font, we generally avoid opening a font,
because that's expensive.  So looking at the metrics is not possible,
unless we actually open each font.

But I don't think I understand what is going on here: these two fonts
are of the same size -- 48 -- so how come the glyphs have different
sizes?  And how different are they?  Can you look at the character
metrics inside gui_produce_glyphs and tell what we get from each font?

> (I guess we're currently just saying "give me this font in size 48"?

I think so, yes.  But if the font spec doesn't specify a size, maybe
we get different sizes?  Although the fact that both are "48" seems to
say we do get the same size?

> And that the actual size of the glyphs may vary between fonts?)

Not sure how this can happen, but I'm not enough of an expert on
fonts, sorry.





  reply	other threads:[~2022-10-16 11:17 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-20 22:16 bug#57962: 29.0.50; Odd font choices Lars Ingebrigtsen
2022-09-21  2:19 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-21 10:43   ` Lars Ingebrigtsen
2022-10-14 11:41     ` Lars Ingebrigtsen
2022-10-14 11:53       ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-14 12:02         ` Lars Ingebrigtsen
2022-10-14 12:05           ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-14 12:13             ` Lars Ingebrigtsen
2022-10-14 12:20               ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-14 12:07       ` Eli Zaretskii
2022-10-14 12:18         ` Lars Ingebrigtsen
2022-10-14 12:37           ` Eli Zaretskii
2022-10-14 12:48             ` Lars Ingebrigtsen
2022-10-14 13:00               ` Eli Zaretskii
2022-10-14 13:06                 ` Lars Ingebrigtsen
2022-10-14 13:09                   ` Eli Zaretskii
2022-10-16 10:58                     ` Lars Ingebrigtsen
2022-10-16 11:17                       ` Eli Zaretskii [this message]
2022-10-16 12:19                         ` Lars Ingebrigtsen
2022-10-16 13:53                           ` Eli Zaretskii
2022-10-17  9:57                             ` Lars Ingebrigtsen
2022-10-17 10:22                               ` Eli Zaretskii
2022-10-17 11:35                                 ` Lars Ingebrigtsen
2022-10-17 12:58                                   ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-17 14:26                                   ` Eli Zaretskii
2022-10-17 14:20                               ` Stefan Kangas
2022-10-17 14:34                                 ` Eli Zaretskii
2022-10-17 15:40                                   ` Stefan Kangas
2022-10-18  0:38                                 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=83tu443tlo.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=57962@debbugs.gnu.org \
    --cc=larsi@gnus.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.