-
-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provide metadata for fonts #17
Comments
Here is a basic version of an appstream generator, https://sid.ethz.ch/appstream/ |
@tintou I don't think the metadata alone lets the application software manager to install the fonts, can you prove otherwise? what system do you use? distribution/release? |
The application software can't let install you the fonts unless they are distributed as a package for your distribution (for now). |
For instance, flatpak provides a standard location where it automatically downloads the "remote" AppStream data so that appcenters can then show the same data as if it would have come from the distribution repository. It is then up to the appcenter to give back the id to flatpak at installation time. |
I see like a snap, flatpak, apt backend but for fonts only using fnt... |
using equivs it is easy to create debian packages automatically for all fonts see an early test: https://sid.ethz.ch/debian/fonts-equivs/ |
all? google webfonts as rpm and deb packages at http://sid.ethz.ch/fonts/, see the example http://sid.ethz.ch/fonts/?fraunces |
The problem with AppStream is it is from freedesktop.org only for GNOME. And Linux. But the world (or Internet), is not only made of that. There is also macOS and that other OS (that you have to pay for)… AppStream by fd.o is made by someone who was at Red Hat in 2000. And it is 23 years later nowhere near useful. |
The AppStream specification is providing a metadata standard for fonts, this allow them to be available in Application Software Managers (like GNOME Shell, elementary AppCenter or KDE Discover).
It would be freat if fnt would create such metadata to easily be able to install them.
The text was updated successfully, but these errors were encountered: