Quoting Gunnar Hjalmarsson (2023-09-10 21:25:12) > On 2023-09-10 13:53, Adam Borowski wrote: > > On Sat, Sep 09, 2023 at 11:24:04PM +0200, Gunnar Hjalmarsson wrote: > >>> Alas, noto has the downside of making font pickers next to useless, > >>> as it declares every single of languages it supports as a separate > >>> font family. So instead off just "Noto Sans" "Noto Mono" "Noto > >>> Slightly Serifed", you have "Noto Western Klingon" "Noto Eastern > >>> Klingon" and so on, making the list of available fonts one big noto > >>> fest. [...] > > Besides, Noto can be said to be a metapackage by itself, providing a large > > set of fonts -- even if it claims to be a single font, it presents hundreds > > of them to the system and UI interfaces. > > That's entirely a result of the way the Noto fonts are packaged in > Debian, and not something that should be attributed to Noto itself. > Discussed at https://bugs.debian.org/983291 . You are potentially talking past each other here: Noto (the upstream project) is marketed as a font but technically appears in an installed operating system not as a single font family but as multiple similarly named but independent font families, each with a set of weights and each covering a subset of scripts and glyphs. fonts-noto (the Debian binary package) is a metapackage pulling in all upstream Noto fonts available in Debian. So yes, a Debian metapackage exists that is big, but the existence of that metapackage is not what "mak[es] font pickers next to useless", nor what "claims to be a single font". - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ * Sponsorship: https://ko-fi.com/drjones [x] quote me freely [ ] ask before reusing [ ] keep private
Attachment:
signature.asc
Description: signature