unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Robert Pluim <rpluim@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Andrea Greselin <greselin.andrea@gmail.com>, 39082@debbugs.gnu.org
Subject: bug#39082: Inconsolata v3.000 has too wide spacing
Date: Mon, 13 Jan 2020 10:27:32 +0100	[thread overview]
Message-ID: <m2eew3vh8b.fsf@gmail.com> (raw)
In-Reply-To: <838smc7bwn.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 12 Jan 2020 20:44:08 +0200")

>>>>> On Sun, 12 Jan 2020 20:44:08 +0200, Eli Zaretskii <eliz@gnu.org> said:

    Eli> The 4th value is unimportant: it's the font's glyph index for that
    Eli> character's glyph.  The 5th element is the problem: it's what we use
    Eli> for the glyph.  29 is way too large, about 2.5 times too large.

    Eli> So the question now becomes how come we get such a large value.  Looks
    Eli> like we somehow use the space-width value instead of the character
    Eli> glyph's width, not sure why.  I guess stepping through the code I've
    Eli> shown from xdisp.c is still necessary to understand this.

I can reproduce this, but I donʼt know how much effort we should spend
getting to the bottom of it: a Cairo-enabled build (ie !XFT) does not
have this problem.

Robert





  reply	other threads:[~2020-01-13  9:27 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
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 [this message]
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

  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=m2eew3vh8b.fsf@gmail.com \
    --to=rpluim@gmail.com \
    --cc=39082@debbugs.gnu.org \
    --cc=eliz@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 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).