all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: greselin.andrea@gmail.com
Cc: 39082@debbugs.gnu.org
Subject: bug#39082: Inconsolata v3.000 has too wide spacing
Date: Sun, 12 Jan 2020 18:56:08 +0200	[thread overview]
Message-ID: <83d0bo7gwn.fsf@gnu.org> (raw)
In-Reply-To: <83eew47kix.fsf@gnu.org> (message from Eli Zaretskii on Sun, 12 Jan 2020 17:37:58 +0200)

> Date: Sun, 12 Jan 2020 17:37:58 +0200
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: 39082@debbugs.gnu.org
> 
> Sadly, I have no idea how to go about investigating this problem
> further, maybe someone else does?

One idea is to look at the character glyph metric we get from the font
here:

  if (it->what == IT_CHARACTER)
    {
      unsigned char2b;
      struct face *face = FACE_FROM_ID (it->f, it->face_id);
      struct font *font = face->font;
      struct font_metrics *pcm = NULL;
      int boff;			/* Baseline offset.  */
    [...]
	  if (get_char_glyph_code (it->char_to_display, font, &char2b))
	    {
	      pcm = get_per_char_metric (font, &char2b);
	      if (pcm->width == 0
		  && pcm->rbearing == 0 && pcm->lbearing == 0)
		pcm = NULL;
	    }

(this is from xdisp.c), and then find the culprit, probably
pcm->width, and go back to where we get these values from the font
back-end.

I cannot myself do this, as I don't have access to a system where this
problem happens.





  reply	other threads:[~2020-01-12 16:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-11 10:03 bug#39082: Inconsolata v3.000 has too wide spacing Andrea Greselin
2020-01-12 15:37 ` Eli Zaretskii
2020-01-12 16:56   ` Eli Zaretskii [this message]
2020-01-12 17:52     ` Eli Zaretskii
2020-01-12 18:17       ` Andrea Greselin
2020-01-12 18:44         ` Eli Zaretskii
2020-01-13  9:27           ` Robert Pluim
2020-01-13 16:18             ` Eli Zaretskii
2020-01-13 16:43               ` Robert Pluim
2020-01-13 16:56                 ` Andrea Greselin
2020-01-13 17:03                 ` Robert Pluim
2020-01-13 17:26                   ` Eli Zaretskii
2020-01-14  9:52                     ` Robert Pluim

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=83d0bo7gwn.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=39082@debbugs.gnu.org \
    --cc=greselin.andrea@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 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.