FS#69082 - [telegram-desktop] No longer obeys fontconfig settings in 2.4.7-5 and later
Attached to Project:
Community Packages
Opened by Timon Walshe-Grey (redtimon) - Wednesday, 23 December 2020, 16:12 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Monday, 28 December 2020, 01:02 GMT
Opened by Timon Walshe-Grey (redtimon) - Wednesday, 23 December 2020, 16:12 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Monday, 28 December 2020, 01:02 GMT
|
Details
Description:
Telegram always used to obey my system font settings, but since updating it just now (from 2.4.7-4 to 2.5.1-1), it seems to have reverted to using some prepackaged font I don't recognise. I realise this is a perennial problem with Electron applications, since CSS all but encourages people to specify unique fonts wherever possible instead of deferring to the OS, but in this case upstream insists it is not the result of anything they changed. Additional info: * package version: first introduced & reported upstream in 2.4.7-5; still present in 2.5.1-1 * upstream bug report (not filed by me): https://github.com/telegramdesktop/tdesktop/issues/9965 Steps to reproduce: * set the default sans-serif font in fontconfig to something easily identifiable * open telegram-desktop * some other font is used. Relevant portion of my fonts.conf: <?xml version='1.0'?> <!DOCTYPE fontconfig SYSTEM 'fonts.dtd'> <fontconfig> <alias> <family>sans-serif</family> <prefer> <family>Source Sans Pro</family> <family>Source Han Sans JP</family> </prefer> </alias> </fontconfig> |
This task depends upon
Closed by Sven-Hendrik Haase (Svenstaro)
Monday, 28 December 2020, 01:02 GMT
Reason for closing: Won't fix
Monday, 28 December 2020, 01:02 GMT
Reason for closing: Won't fix
Anyway, that's that and I'm closing this one.