You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So the metadata file in the fontpackage is important. I really like the package.json in npm as the base instead of the current METADATA.yaml standard used in UFR. This way we can define a set of standard fields and also have fontman specific data as well.
Fonts itself has metadata and we have to always build the package file from the fontfiles and other files such as CONTRIBUTORS and AUTHORS and other metadata.
The text was updated successfully, but these errors were encountered:
So the metadata file in the fontpackage is important. I really like the
package.json
in npm as the base instead of the current METADATA.yaml standard used in UFR. This way we can define a set of standard fields and also have fontman specific data as well.Fonts itself has metadata and we have to always build the package file from the fontfiles and other files such as CONTRIBUTORS and AUTHORS and other metadata.
The text was updated successfully, but these errors were encountered: