[Interest] Configuring Qt's built-in freetype ?
jeanmichael.celerier at gmail.com
Fri Feb 11 20:08:50 CET 2022
Managed to get to the bottom of the issue: without fontconfig, the freetype
backend depends on QPlatformScreen::subpixelAntialiasingTypeHint(),
which will return QPlatformScreen::Subpixel_None unless the
QT_SUBPIXEL_AA_TYPE env var is set.
I've checked a bit and it seems that 99% of current LCD monitors are RGB
(the very few references I could find to recent BGR monitors were about
people complaining that nothing did work with them anyways and recommending
to not buy them because the industry seems to have standardized on RGB
so I'll set the env var to this by default, and will report here if I get
tons of complaints :)
*cto* ossia.io | *consulting inquiries* celtera.dev | *personal*
t: +336 81 31 53 08
On Sun, Jan 2, 2022 at 11:09 AM Jean-Michaël Celerier <
jeanmichael.celerier at gmail.com> wrote:
> Yes, this test was done on linux (but even on windows & mac I pass the
> correct options to the QPA).
> Thanks for the heads up and the link !
> On Sun, Jan 2, 2022 at 1:48 AM Marius Kittler <mkittler at suse.de> wrote:
>> Am Samstag, 1. Januar 2022, 17:23:22 CET schrieb Jean-Michaël Celerier:
>> > Yet I still get non-subpixel AA when rendering so there may be a bit
>> > to that issue...
>> Just to rule out a simple mistake: Be aware that Qt is *not* using
>> under Windows by default (also if Qt was compiled with FreeType2 support)
>> any changes to the FreeType2 config make no difference by default. This
>> especially notable when trying to use WOFF which thus doesn't work by
>> See https://github.com/Martchus/qtforkawesome#providing-the-font-file
>> also explains how to configure the Windows platform plugin to use
>> Best Regards
>> Interest mailing list
>> Interest at qt-project.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Interest