https://bugzilla.redhat.com/show_bug.cgi?id=2257137
--- Comment #18 from Rajeesh rajeeshknambiar@gmail.com --- (In reply to Benson Muite from comment #17)
Source0: %{url}/-/jobs/artifacts/%{version}/download?job=build-tag#/download
Only, it doesn't result in a %{name}-%{version}.zip file. curl, which rpmbuild uses, generates a file named 'download'. If only that can be worked around...
Fedora does not seem to use the metainfo.xml file, but maybe this is still useful in applications. It is not mentioned in the font packaging guidelines. It does not block the review to install it, but am curious how it is used.
The metainfo.xml contains AppStream data, consumed by GUI 'app stores' like GNOME Software and Discover to show the font previews.
The font configuration file https://gitlab.com/rit-fonts/MeeraNew/-/blob/main/meta/65-meera-new-fonts. conf is very good. Can something similar be used for rit-keraleeyam ? As the number 75 for keraleeyam is higher than 65 for meera, if both are installed meera will be chosen as the default, but if only keraleeyam is installed it will be used instead. It is sufficient to apply a patch rather than make a new release.
So, MeeraNew is the default sans-serif font, intended for general use. Keraleeyam, on the other hand is a display typeface (no regular style, only bold) intended for specific typesetting use cases. It shouldn't be used as a general fallback font.