From: mvf <mvf@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: subpixel rendering is broken in GTK programs
Date: Thu, 30 Jul 2020 07:55:05 +0200 [thread overview]
Message-ID: <20200730055505.eEnan7zMYebNgNpflqeqaFGuZtvEdu2AX2FJocE4pzM@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: 1349 bytes --]
New comment by mvf on void-packages repository
https://github.com/void-linux/void-packages/issues/21429#issuecomment-666137216
Comment:
IMHO we should keep the patch. The largest distros have it enabled (Debian/Ubuntu, Fedora, openSUSE). Arch seems to be an outlier here, and some users don't seem too happy about it.
This is a configuration issue. The fix is to let `fontconfig` ship a file that lets `lcdfilter` default to `lcddefault`. Here's `/etc/fonts/conf.d/11-lcdfilter-default.conf` as found on Ubuntu 20.04 and Debian buster:
```xml
<?xml version="1.0"?>
<!DOCTYPE fontconfig SYSTEM "fonts.dtd">
<fontconfig>
<its:rules xmlns:its="http://www.w3.org/2005/11/its" version="1.0">
<its:translateRule translate="no" selector="/fontconfig/*[not(self::description)]"/>
</its:rules>
<description>Use lcddefault as default for LCD filter</description>
<!-- Use lcddefault as default for LCD filter -->
<match target="pattern">
<!--
This configuration is available on the major desktop environments.
We shouldn't overwrite it with "assign" unconditionally.
Most clients may picks up the first value only. so using "append"
may simply works to avoid it.
-->
<edit mode="append" name="lcdfilter">
<const>lcddefault</const>
</edit>
</match>
</fontconfig>
```
next prev parent reply other threads:[~2020-07-30 5:55 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 [this message]
2020-07-30 10:00 ` andry-dev
2020-07-30 10:01 ` andry-dev
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=20200730055505.eEnan7zMYebNgNpflqeqaFGuZtvEdu2AX2FJocE4pzM@z \
--to=mvf@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).