An archive with all of the fonts

[Pi-Cla]

Is your feature request related to a problem? Please describe.
Where I can download an archive with all of the (non-CJK/Emoji) Noto fonts? Cause if the fonts are not all going to be hosted in this one repository, then would that mean I now have to click on every single font's link to download all of them?

Describe the solution you'd like
I would like it if Noto fonts could make monthly(or quarterly, or some other consistent period of time) archives of all of the fonts. So it would be like how Adobe Source Han/Noto CJK already has archives of all of the CJK fonts, and there are archives for Variable vs Non-Variable, TTF vs OTF, etc.

Describe alternatives you've considered
The way I had been downloading fonts is to run SVN on the folder within this repo that has all of the hinted ttf fonts, as waiting for the entire repo to download (even with sparse checkout turned on) takes forever. and there had not been a Github release in two years.

Additional context
I am packaging the Noto Fonts for openSUSE, and it would be nice if I did not have to click on 200+ urls just to download all of the fonts, or even do the hacky SVN thing I have been doing.
Also, this is the svn command I had been using:

svn checkout https://github.com/googlefonts/noto-fonts/trunk/hinted/ttf

[simoncozens]

Thanks for this. We're currently in transition at the moment, and in the future, all the fonts will be hosted via the notofonts.github.io repository. This will both be a GitHub Pages front-end to the release and also a repository containing the latest released versions of all fonts.

You can see this repo slowly filling up with families here as new releases happen. The priority at the moment is to get a new release of everything out so that notofonts.github.io picks them up. I'm hoping to do this over the course of this month and next but it's also an opportunity to get fonts onto Google Fonts and Google Docs and sometimes that requires additional fiddling with the sources to meet their standards.

I can certainly also do a quarterly or even monthly GitHub snapshot of the repo, if it would help, once we have it fully populated. You may also be interested in the JSON catalogue file which gives you information about each new release and the files contained in them.

[Pi-Cla]

Oh neat, I wasn't aware that the repository for the website already has an archive with all of the fonts. After perusing the repository, I think its already quite good and the json file with the version number and issues it quite helpful too.

Now I think that a periodic snapshot of the repo may be helpful if its possible for a font to be updated without a new tagged archive being created. But if that's not the case, then I think its unnecessary.

Thanks for the hard work so far

[Pi-Cla]

Oh, actually on second thought. I just remembered that having a consistent download url is useful for packaging (at least for rpm based distros since the url has to be included in the packaging specifications file). So an issue with naming the release tarballs after the last updated font is that then every time a packager needs to update Noto Fonts, they will have to change the url manually. Whereas, if the tarballs were instead named after the date they were released, that would be more helpful as there's a macro I can use to substitute part of the url for the version and openSUSE already versions Noto Fonts as a whole using a calendar date.

It would also be good if the tagged archive were to follow the format of YYYYMMDD as that is already the version format many Linux distros use to package Noto Fonts https://repology.org/project/fonts:noto/versions

[classabbyamp]

+1 for having a consistent, versioned download of all languages available (working on the package for void linux currently)

[simoncozens]

I'll add a GHA job to do a monthly tag.