From: andry-dev <andry-dev@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: subpixel rendering is broken in GTK programs
Date: Thu, 30 Jul 2020 12:01:28 +0200 [thread overview]
Message-ID: <20200730100128.-hbB0pfNiDK96OlP7VoH0Pm4Wrf_uqicSKgKFbUQwcY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21429@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 803 bytes --]
New comment by andry-dev on void-packages repository
https://github.com/void-linux/void-packages/issues/21429#issuecomment-666272488
Comment:
I may be a bit biased (since I'm the author of the patch), but I agree with @mvf.
When I made the patch I had lcdfilter in my `~/.config/fontconfig/fonts.conf` so nothing looked weird for me; shipping a system-wide config file would fix it for everyone.
I noticed that lots of people on Arch install the patched `fontconfig-cleartype` package from the AUR.
Since major distros use it, nobody complains about their font rendering, the font rendering is (IMHO) actually better with it and the fix is just to ship a config file, I think this is a valuable patch that should be kept.
It's my fault for not noticing the need for a system-wide config at the time.
next prev parent reply other threads:[~2020-07-30 10:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-28 14:21 [ISSUE] " VoidDuck
2020-04-29 6:43 ` travankor
2020-05-01 12:45 ` bsduck
2020-05-06 4:27 ` ericonr
2020-05-09 12:05 ` travankor
2020-05-09 12:06 ` travankor
2020-05-09 12:06 ` travankor
2020-07-29 23:31 ` ericonr
2020-07-30 5:55 ` mvf
2020-07-30 10:00 ` andry-dev
2020-07-30 10:01 ` andry-dev [this message]
2020-07-30 15:26 ` ericonr
2022-04-16 2:02 ` github-actions
2022-07-18 2:13 ` github-actions
2022-08-01 2:14 ` [ISSUE] [CLOSED] " github-actions
2023-02-20 1:13 ` bsduck
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=20200730100128.-hbB0pfNiDK96OlP7VoH0Pm4Wrf_uqicSKgKFbUQwcY@z \
--to=andry-dev@users.noreply.github.com \
--cc=ml@inbox.vuxu.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 NNTP newsgroup(s).