From: Eli Zaretskii <eliz@gnu.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: greselin.andrea@gmail.com, 39082@debbugs.gnu.org
Subject: bug#39082: Inconsolata v3.000 has too wide spacing
Date: Mon, 13 Jan 2020 19:26:41 +0200 [thread overview]
Message-ID: <83r2035ktq.fsf@gnu.org> (raw)
In-Reply-To: <m2k15vthjq.fsf@gmail.com> (message from Robert Pluim on Mon, 13 Jan 2020 18:03:37 +0100)
> From: Robert Pluim <rpluim@gmail.com>
> Cc: greselin.andrea@gmail.com, 39082@debbugs.gnu.org
> Date: Mon, 13 Jan 2020 18:03:37 +0100
>
> ** Under X, some characters are unexpectedly wide.
>
> e.g. recent versions of Inconsolata show this issue for almost all of
> its characters. Due to either a limitation in the Xft interface used
> by Emacs, or an Xft bug, the determination of the width of some
> characters is incorrect. Emacs built with Cairo enabled ("configure
> --with-cairo") and the appropriate cairo development packages
> installed does not have this issue. See
> <https://github.com/googlefonts/Inconsolata/issues/42> and
> <https://lists.gnu.org/archive/html/bug-gnu-emacs/2020-01/msg00456.html>
> for more discussion.
OK, but please inject something like "a workaround is to ..." into
this text. Like "A workaround is to build Emacs with Cairo enabled,
as this configuration doesn't have such problems."
next prev parent reply other threads:[~2020-01-13 17:26 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
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 [this message]
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=83r2035ktq.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=39082@debbugs.gnu.org \
--cc=greselin.andrea@gmail.com \
--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).