No edit summary |
No edit summary |
||
| Line 32: | Line 32: | ||
{{:Fonts spec template comments/description}} | {{:Fonts spec template comments/description}} | ||
== Building == | |||
{{:Fonts spec template comments/build}} | |||
Notes: | Notes: | ||
<references/> | <references/> | ||
{{:Fonts_SIG_signature}} [[Category:Fonts packaging|Spec template, comments]] [[Category:Documentation|Spec template, fonts, comments]][[Category:Template|Spec template, fonts, comments]] | {{:Fonts_SIG_signature}} [[Category:Fonts packaging|Spec template, comments]] [[Category:Documentation|Spec template, fonts, comments]][[Category:Template|Spec template, fonts, comments]] | ||
Revision as of 12:30, 20 December 2008
The following notes are intended to help new packagers understand the Fedora official fonts spec templates:
- our simple template, intended for source packages that ship a single font family,
- our multi template, intended for source packages that ship several different font families
Naming
Replace <FONTNAME> with something appropriate such as foundryname-fontname. For Fedora purposes a “foundry” is an entity that publishes a set of fonts with consistent QA rules[1].
If fontname already includes the font or fonts affix, drop it.
Fontconfig ruleset(s)
fontconf is the optional fontconfig ruleset for the fonts being packaged. For more information on choosing the right fontconfig priorities, see this page.
Font versions
Do not trust font metadata versionning[2], unless you've checked upstream does update versions on file changes. When in doubt use the timestamp of the most recent font file as version, for example 20081231.
Licensing
Make sure you've read and understand our legal page.
BuildRoot
Any approved buildroot choice.
Summary
Font summaries need to be short and to the point. Usual informations are font style and Unicode coverage. Only repeat the font name(s) if you don't have anything else to write.
Description
Font descriptions must detail information on the font style, Unicode coverage, and intended use[3] to help users choose the right packages to install. Also, it is considered good form to credit the original font designer and sum up the font history.
Incidentally, this is a good way to check if the licensing information declared by upstream is correct and if some fontconfig substitution rules can be added to the package.
Examples of terrific font descriptions are found on the Greek Font Society web site. This is what other font packages should strive to emulate.
Building
Building fonts from sources is always preferred. For GPLed or LGPLed fonts this is required by the license.
Notes:
- ↑ Thus Sourceforge is not a foundry
- ↑ The metadata embedded in TTF or OTF files.
- ↑ Print, screen, headings, code…
The Fonts SIG takes loving care of Fedora fonts. Please join this special interest group if you are interested in creating, improving, packaging, or just suggesting a font. Any help will be appreciated.