-------- Ursprüngliche Nachricht -------- Von: fab...@greffrath.com An: Amr Ibrahim <amribrahim1...@hotmail.com> Kopie: 1041...@bugs.debian.org Betreff: Re: [Pkg-fonts-devel] Bug#1041312: fonts-noto: Migrate to new upstream sources, and split the fonts according to upstream Datum: 12.09.2023 14:23:19
Hi Fabian, > the fonts appear to be organized into different subdirectories with > varying content. True. If you go to https://notofonts.github.io/ and look at any font, you'll see that there is a "Source repository" selection, which opens the font's source on GitHub. For example, Noto Arabic <https://notofonts.github.io/#arabic> has its source at <https://github.com/notofonts/arabic>, and so on. > Do you know upstream's stance on this? Is hinted/ttf always preferable > over unhinted/* and what's the matter with the fonts in googlefonts/*? > And how about the unhinted/variable-ttf, unhinted/slim-variable-ttf and > unhinted/otf variants? Sorry, I don't have answers to that. > They offer a snapshow of the entire repository for download in the > Releases section: > > https://github.com/notofonts/notofonts.github.io/releases > > These could be downloaded, have the undesired fonts stripped off, get > repacked and split up into individual Debian packages. Or the individual fonts can be packaged from their own sources, which I mentioned above. Whichever the Debian maintainer finds more practical. Best, Amr