From: travankor <travankor@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: subpixel rendering is broken in GTK programs
Date: Sat, 09 May 2020 14:06:39 +0200 [thread overview]
Message-ID: <20200509120639.Xxiuyaj9ms3aq2-Ddfoy57L01Wx7_R_iZv6cBJ-dmVY@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: 850 bytes --]
New comment by travankor on void-packages repository
https://github.com/void-linux/void-packages/issues/21429#issuecomment-626165884
Comment:
The problem that @bsduck experiences is that you need to specify lcdfilter with the Microsoft ClearType patch, otherwise you get color fringing. Most other distro's don't use ClearType because upstream recommends their non-patented solution ("Harmony") instead (they even claim their solution is as good).
@ericonr I haven't done any scientific testing or anything, but I would be ok to `rm` the ClearType patch from the freetype build. The other option might be document this under Font Configuration.
Refs:
-
1. https://www.freetype.org/freetype2/docs/reference/ft2-lcd_rendering.html
2. https://www.freetype.org/freetype2/docs/subpixel-hinting.html
3. https://bugs.archlinux.org/task/60658
next prev parent reply other threads:[~2020-05-09 12:06 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 [this message]
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
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=20200509120639.Xxiuyaj9ms3aq2-Ddfoy57L01Wx7_R_iZv6cBJ-dmVY@z \
--to=travankor@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).