#253 Font hinting it set by default to "slight", but sub-pixel anti-aliasing is set to "none"
Closed: Deferred to upstream 2 years ago by ngraham. Opened 2 years ago by ngraham.

In Plasma, the Fonts page is being fixed so that the default sub-pixel anti-aliasing and hinting settings reflect the true system defaults; see https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/2140.

While testing this, I found that the defaults in Fedora aren't ideal: hinting is set to "slight", which is fine, but sub-pixel anti-aliasing is set to "none", which isn't.

It appears that the hinting setting is enforced by /etc/fonts/conf.d/10-hinting-slight.conf, but there isn't any such file to set default sub-pixel anti-aliasing style to something.


We can probably do something to set this...

Metadata Update from @ngompa:
- Issue tagged with: experience

2 years ago

We'll talk to the fontconfig maintainers about setting this by default.

I'll take this action.

Metadata Update from @ngompa:
- Assignee reset

2 years ago

Metadata Update from @ngompa:
- Issue assigned to ngompa

2 years ago

Metadata Update from @ngompa:
- Issue assigned to ngompa

2 years ago

Sent an email to @tagoh and @rstrode. Awaiting response.

Metadata Update from @ngompa:
- Issue tagged with: pending-action

2 years ago

Well, basically we expect "antialias" is true by default. it isn't the case in KDE? I could enable it in fontconfig though.

It appears that the hinting setting is enforced by /etc/fonts/conf.d/10-hinting-slight.conf

This isn't exactly true. default config in fontconfig such as them are only enabled if it isn't set. Given that some desktop has "hintfull" for example, fontconfig adds "hintslight" to hintstyle. most toolkits reads a first item only so "hintfull" is used for them. that is the trick.

We could do the same for antialias but I'm wondering why KDE doesn't enable it by default?

In general, Plasma respects distro defaults rather than overriding them. It's just a difference of design philosophy compared to other more opinionated DEs. This bites us a lot, but we feel like it's good to help distros improve their own defaults by exposing gaps like this.

I appreciate your getting involved to help fix this, thanks!

I added config files to disable/enable antialiasing in fontconfig upstream git: https://gitlab.freedesktop.org/fontconfig/fontconfig/-/commit/0825a178e82c58ae97e908d49e5ad7abe88ed7f5

will backport this to Fedora soon.

Thanks, but this issue is actually about sub-pixel hinting being set to None by default rather than RGB. I think we'll still need that even with your changes.

Oh cool, thanks!

So this should be enabled upstream by default now?

Yes, that would be 2.14.1.

Awesome, thanks a lot. So I guess there's nothing to do on the Fedora side, and we'll inherit that change automatically, right?

Once 2.14.1 is coming into Fedora, yes.

Great, so I guess there's nothing for Fedora to do here. Closing. Thanks again!

Metadata Update from @ngraham:
- Issue close_status updated to: Deferred to upstream
- Issue status updated to: Closed (was: Open)

2 years ago

I have pushed 2.14.1 to rawhide. please test it if you like. If that looks good, I can backport it for f37 if you want. just FYI.

I applied your package on top of Fedora 36 and it's working perfectly. I'd support a backport to 37, and even 36 too.

I just did a clean install of Fedora 37 on a new machine, and can verify that it has fontconfig-2.14.1. However we still don't get slight RGB sub-pixel rendering by default. In System Settings, the Fonts KCM says "None" in that combobox. However if I click on the "Defaults" button, it changes to RGB, inheriting the system's actual default value. And then after applying and restarting apps, we actually do get slight RGB sub-pixel rendering.

So the Fonts KCM thinks that RGB is the system's default value, but it's not set to that by default. Do we have a Fedora-sprcific override here or something?

Metadata Update from @ngraham:
- Issue status updated to: Open (was: Closed)

2 years ago

Ok, I will investigate and see if this is a KDE bug.

Metadata Update from @ngraham:
- Issue close_status updated to: Deferred to upstream
- Issue status updated to: Closed (was: Open)

2 years ago

Log in to comment on this ticket.

Metadata