Sub-pixel anti-aliasing is not being applied to snaps

[soredake]

In my ~/.config/fontconfig/fonts.conf i have this:
```
  <edit name="rgba" mode="assign">
   <const>rgb</const>
  </edit>
```
It is not applied to snaps, making fonts in snaps look bad.

[Ian Johnson (anonymouse67)]

This is a per-snap feature, snapd doesn't specifically modify any font features, and we are working towards having as many snaps as possible use snapcraft's configure hook which sets up a private font cache that is per-snap and not shared. So if you find this is happening for a snap which uses that configure hook, then we can add a snapcraft task here to look into updating the configure hook there to support your config.

An example snap that uses that configure hook would be the chromium snap on the stable channel, can you try installing that snap with

snap install chromium --stable

and then check if your fonts are configured the way you expect?

[soredake (soredake)]

>and then check if your fonts are configured the way you expect?

Yes, rgb works with chromium snap.

Snap that i tested is telegram desktop (https://github.com/telegramdesktop/tdesktop/blob/dev/snap/snapcraft.yaml), so it's better for to report to them?

[Ian Johnson (anonymouse67)]

Yes, I would say that you should file bugs with individual snaps then, you can suggest to snaps to try upgrading to using the extensions from modern snapcraft such as kde-neon or gnome-* but it's possible that some snaps will not be able to switch to using those extensions.

[soredake (soredake)]

https://github.com/telegramdesktop/tdesktop/issues/10429