From: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>
To: 35781@debbugs.gnu.org
Subject: bug#35781: Discrepancies between xftfont.c and ftcrfont.c
Date: Sat, 18 May 2019 22:43:28 +0200 [thread overview]
Message-ID: <87pnofze6n.fsf@gmail.com> (raw)
In-Reply-To: <878sv5ou9r.fsf@gmail.com>
retitle 35781 Make Cairo build obey hint-style font setting
thanks
I am nowhere close to a proper fix, but at least I think I am starting
to get a clearer picture of the situation.
The distribution installed on my laptop sets the "hint-style" font
setting to "slight" in both ~/.config/fontconfig/fonts.conf and
~/.Xresources. AFAICU fontconfig and X resources are two (competing?)
mechanisms that tell graphical applications what fonts and font
settings they should use. OK.
I am still studying the lay of the land; I see that xftfont_open in
xftfont.c calls xftfont_add_rendering_parameters, which has a bunch of
hint-style-related code calling fontconfig functions, while
ftcrfont_open in ftcrfont.c seems blissfully unaware of fontconfig.
At this point I am assuming that only ftcrfont.c is used in Cairo
builds, since config.h does not define HAVE_XFT, but my knowledge of
font management in Emacs is pretty lacking so I will have to check this
assumption.
As I said, I am far from being able to cook up any sort of patch at
this point; I still intend to keep digging Soonish™, but since that
may take a while, I figured I would update this report with whatever
information I gathered this far for posterity.
next prev parent reply other threads:[~2019-05-18 20:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-17 17:39 bug#35781: 27.0.50; [PATCH] Improve font display on Cairo builds Kévin Le Gouguec
2019-05-17 17:54 ` Dmitry Gutov
2019-05-17 18:14 ` Kévin Le Gouguec
2019-05-17 18:23 ` Kévin Le Gouguec
2019-05-17 18:24 ` Dmitry Gutov
2019-05-18 20:43 ` Kévin Le Gouguec [this message]
2019-05-19 19:48 ` bug#35781: Discrepancies between xftfont.c and ftcrfont.c Alex Gramiak
2019-05-21 10:59 ` mituharu
2019-05-21 19:03 ` Kévin Le Gouguec
2019-05-22 9:24 ` YAMAMOTO Mitsuharu
2019-05-23 2:00 ` YAMAMOTO Mitsuharu
2019-05-23 17:53 ` Kévin Le Gouguec
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=87pnofze6n.fsf@gmail.com \
--to=kevin.legouguec@gmail.com \
--cc=35781@debbugs.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.
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).