* Re: gsettings-desktop-schemas: missing font dependency
2024-01-26 16:27 [PR PATCH] gsettings-desktop-schemas: missing font dependency c0m4r
@ 2024-01-31 16:09 ` ahesford
2024-01-31 17:11 ` c0m4r
` (4 subsequent siblings)
5 siblings, 0 replies; 7+ messages in thread
From: ahesford @ 2024-01-31 16:09 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 389 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/pull/48382#issuecomment-1919424702
Comment:
The schema also references Cantarell, but GTK applications with client-side decorations still seem to function with an alternative font.
It would seem better to have the default schema reference generic font aliases rather than specific fonts.
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: gsettings-desktop-schemas: missing font dependency
2024-01-26 16:27 [PR PATCH] gsettings-desktop-schemas: missing font dependency c0m4r
2024-01-31 16:09 ` ahesford
@ 2024-01-31 17:11 ` c0m4r
2024-01-31 17:14 ` c0m4r
` (3 subsequent siblings)
5 siblings, 0 replies; 7+ messages in thread
From: c0m4r @ 2024-01-31 17:11 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 1260 bytes --]
New comment by c0m4r on void-packages repository
https://github.com/void-linux/void-packages/pull/48382#issuecomment-1919545113
Comment:
> The schema also references Cantarell, but GTK applications with client-side decorations still seem to function with an alternative font.
That's correct, however that's not the case in terminal emulators. You either need to provide the correct font or change the configuration pointing to the generic Monospace font (Debian does that). The idea is so it just works by default, without such changes.
> It would seem better to have the default schema reference generic font aliases rather than specific fonts.
It depends. I compared solutions used by other distros and I found this font as a dep less invasive and problematic. It's widely used and you don't need to modify schemas, nor configuration. By changing the default schemas there's no guarantee that it's not already overwritten by the local or user configuration, still pointing to the missing font. Moreover, this way we use native, consistent fonts. So in terms of user experience I'd vote for adding missing font the way that [Arch](https://archlinux.org/packages/extra/any/gsettings-desktop-schemas/) does that, rather that the overwriting schemas.
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: gsettings-desktop-schemas: missing font dependency
2024-01-26 16:27 [PR PATCH] gsettings-desktop-schemas: missing font dependency c0m4r
2024-01-31 16:09 ` ahesford
2024-01-31 17:11 ` c0m4r
@ 2024-01-31 17:14 ` c0m4r
2024-01-31 18:20 ` ahesford
` (2 subsequent siblings)
5 siblings, 0 replies; 7+ messages in thread
From: c0m4r @ 2024-01-31 17:14 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 1603 bytes --]
New comment by c0m4r on void-packages repository
https://github.com/void-linux/void-packages/pull/48382#issuecomment-1919545113
Comment:
> The schema also references Cantarell, but GTK applications with client-side decorations still seem to function with an alternative font.
That's correct, however that's not the case in terminal emulators. You either need to provide the correct font or change the configuration pointing to the generic Monospace font (Debian does that). The idea is so it just works by default, without such changes.
> It would seem better to have the default schema reference generic font aliases rather than specific fonts.
It depends. I compared solutions used by other distros and I found this font as a dep less invasive and problematic. It's widely used and you don't need to modify schemas, nor configuration. By changing the default schemas there's no guarantee that it's not already overwritten by the local or user configuration, still pointing to the missing font. Moreover, this way we use native, consistent fonts. So in terms of user experience I'd vote for adding missing font the way that [Arch](https://archlinux.org/packages/extra/any/gsettings-desktop-schemas/) does that, rather that the overwriting schemas.
And even Debian's gsettings-desktop-schemas.gsettings-override mentions:
```
# Adobe Source Code Pro is not in Debian yet
# See https://bugs.debian.org/736681 and https://bugs.debian.org/762252
[org.gnome.desktop.interface]
monospace-font-name = 'Monospace 11'
```
so if we have the font in the repo, I think it's worth using it
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: gsettings-desktop-schemas: missing font dependency
2024-01-26 16:27 [PR PATCH] gsettings-desktop-schemas: missing font dependency c0m4r
` (2 preceding siblings ...)
2024-01-31 17:14 ` c0m4r
@ 2024-01-31 18:20 ` ahesford
2024-01-31 19:39 ` c0m4r
2024-02-02 7:38 ` [PR PATCH] [Closed]: " c0m4r
5 siblings, 0 replies; 7+ messages in thread
From: ahesford @ 2024-01-31 18:20 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 521 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/pull/48382#issuecomment-1919672433
Comment:
My argument is that upstream should use a generic label, not necessarily that we should patch the schema. The reference to Cantarell may be considered a special case because the font is maintained by the GNOME project as the official UI font, whereas Source Code Pro is an external font whose associated use in terminal emulators is likely to incite a lot of passionate opinion.
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: gsettings-desktop-schemas: missing font dependency
2024-01-26 16:27 [PR PATCH] gsettings-desktop-schemas: missing font dependency c0m4r
` (3 preceding siblings ...)
2024-01-31 18:20 ` ahesford
@ 2024-01-31 19:39 ` c0m4r
2024-02-02 7:38 ` [PR PATCH] [Closed]: " c0m4r
5 siblings, 0 replies; 7+ messages in thread
From: c0m4r @ 2024-01-31 19:39 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 765 bytes --]
New comment by c0m4r on void-packages repository
https://github.com/void-linux/void-packages/pull/48382#issuecomment-1919805915
Comment:
> My argument is that upstream should use a generic label, not necessarily that we should patch the schema.
Agreed. Yet, I don't believe we're gonna influence such change.
> whereas Source Code Pro is an external font whose associated use in terminal emulators is likely to incite a lot of passionate opinion.
We'd better not get into THESE discussions ;) Though it's only a font, not the init system :)
But if it were to turn into such a big deal, the compromise solution is to make a schema patch or an override.
Just let me know, if there's no go for a font dep I'm gonna try to prepare an alternative solution.
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [PR PATCH] [Closed]: gsettings-desktop-schemas: missing font dependency
2024-01-26 16:27 [PR PATCH] gsettings-desktop-schemas: missing font dependency c0m4r
` (4 preceding siblings ...)
2024-01-31 19:39 ` c0m4r
@ 2024-02-02 7:38 ` c0m4r
5 siblings, 0 replies; 7+ messages in thread
From: c0m4r @ 2024-02-02 7:38 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 477 bytes --]
There's a closed pull request on the void-packages repository
gsettings-desktop-schemas: missing font dependency
https://github.com/void-linux/void-packages/pull/48382
Description:
org.gnome.desktop.interface monospace-font-name default is 'Source Code Pro 10', which is missing
adding this dependency will fix default configuration with dependent packages like tilix, terminator and probably others
#### Testing the changes
- I tested the changes in this PR: **YES**
^ permalink raw reply [flat|nested] 7+ messages in thread