From: Robert Pluim <rpluim@gmail.com>
To: Tassilo Horn <tsdh@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Emacs 28: Specific TTF font gets loaded with font-backend x instead of ftcrhb
Date: Tue, 04 Feb 2020 21:11:57 +0100 [thread overview]
Message-ID: <m2mu9yjenm.fsf@gmail.com> (raw)
In-Reply-To: <87mu9yi4pj.fsf@gnu.org> (Tassilo Horn's message of "Tue, 04 Feb 2020 19:32:08 +0100")
>>>>> On Tue, 04 Feb 2020 19:32:08 +0100, Tassilo Horn <tsdh@gnu.org> said:
Tassilo> Robert Pluim <rpluim@gmail.com> writes:
Tassilo> Hi Robert,
Tassilo> I've now tried at home with my own computer (also running Arch) and got
Tassilo> the same issue so it is at least not machine specific.
I spun up an Arch VM, and the system jetbrains mono package works fine
there.
Tassilo> I did that, and now it works just fine. Is there something different
Tassilo> (except for the location) when installing a font by just copying the ttf
Tassilo> files to /usr/share/fonts/TTF/ and installing them with the Fonts tool?
Tassilo> I mean, now it works with the very same ttf files I've previously copied
Tassilo> to /usr/share/fonts/TTF/ (replacing the files installed by the Arch
Tassilo> package).
Not that I know of, as far as I know it just does the moral equivalent of
'fc-cache' somewhere.
Tassilo> Hm, another minor thing: when I compare the rendering of the above
Tassilo> paragraph in gedit and emacs, there are slight differences for some
Tassilo> glyphs. For example, the F in TTF is slightly higher than the Ts, and
Tassilo> the y is slightly lower than, e.g., an a or o. In gedit, their height
Tassilo> is equal.
That sounds like there are hinting differences. Cairo doesnʼt always
obey the Gnome Tweaks hinting settings. The following might help:
<https://www.kilobitspersecond.com/2009/04/17/ubuntu-font-hinting-you-a-cautionary-tale/>
Robert
next prev parent reply other threads:[~2020-02-04 20:11 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-04 11:12 Emacs 28: Specific TTF font gets loaded with font-backend x instead of ftcrhb Tassilo Horn
2020-02-04 12:15 ` Robert Pluim
2020-02-04 12:25 ` Robert Pluim
2020-02-04 12:58 ` Tassilo Horn
2020-02-04 13:54 ` Robert Pluim
2020-02-04 14:21 ` Tassilo Horn
2020-02-04 16:26 ` Robert Pluim
2020-02-04 18:32 ` Tassilo Horn
2020-02-04 20:11 ` Robert Pluim [this message]
2020-02-05 16:51 ` Tassilo Horn
2020-02-04 15:31 ` Eli Zaretskii
2020-02-04 18:43 ` Tassilo Horn
2020-02-04 19:08 ` Eli Zaretskii
2020-02-05 16:44 ` Tassilo Horn
2020-02-05 17:04 ` Eli Zaretskii
2020-02-06 7:12 ` Tassilo Horn
2020-02-06 18:15 ` Eli Zaretskii
2020-02-07 9:21 ` Tassilo Horn
[not found] ` <b271f1084b17a53ee1583d1f8cd92e9ed21cf360.camel@gnu.org>
2020-02-07 9:48 ` Eli Zaretskii
2020-02-07 10:41 ` Tassilo Horn
2020-02-07 13:28 ` Eli Zaretskii
2020-02-08 9:39 ` Tassilo Horn
2020-02-08 9:52 ` Tassilo Horn
2020-02-08 10:16 ` Eli Zaretskii
2020-02-08 10:36 ` Eli Zaretskii
2020-02-08 12:29 ` Tassilo Horn
2020-02-08 13:50 ` Eli Zaretskii
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=m2mu9yjenm.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=tsdh@gnu.org \
/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.
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).