Each value typically matches a string in the designer key of info.pb files in the library repo /catalog/designers tree. Once pushed to production, updating it is generally not allowed, although exceptions can be made in limited cases.įull name of the type designers or foundries who designed the fonts. If you set the date added into the future, then the family will stay at the top of the ‘trending’ sort until that date passes and it trails off like normal.

It is used to order the front page of the GF catalog, both obviously the “date added” sort mode, and also the default “trending mode.” nameįamily name used to call the family’s fonts from the Google Fonts API, and shown in the catalog .ĭate in YYYY-MM-DD format that the font was first published by Google Fonts. The order of the keys does not strictly matter, but the order in this example is typical and is maintained when possible to avoid noisy diff comparisons. Each top-level field can only occur once in the file. Most top-level keys provide unique information which is generally not derived from or matching with data inside the font files themselves.

Post_script_name: 'ExampleSerif-LightItalic' Example Static Fonts Family name: 'Example Sans'ĭesigner: 'Firstname Lastname, Person Two, Person Three'Ĭopyright: 'Copyright 2021 The Example Sans Project Authors (/username/example-sans)'Ĭommit: 'd9098c0a72125d411dbb225a2e5a61dc15265ffc'Įxample Variable Fonts Family name: 'Example Serif'Ĭopyright: 'Copyright 2021 The Example Sans Project Authors (/username/example-serif)'įilename: 'ExampleSerif-Italic.ttf' The file can be partially generated by the gftools add-font script and gftools packager : gftools add-font path/to/google/fonts/ofl/fontdirnameīelow are 2 example METADATA.pb files, first for a family of static font files, and then for a family with variable font files, followed by a brief description of each key and possible values. It may be useful for others to be able to make sense of the metadata files.

This metadata is used specifically by Google Fonts for organization and display on the Google Fonts website. It is provided so that other font distributors (webfonts providers or font package maintainers) can better use the library repo repository structure. This documentation was initiated by Adam Twardoch as a community contributor in 2015, and updated by Dave Crossland as a member of the Google Fonts team in 2020. Nerd google/fonts repository explained Table of contents

Google fonts chinese style