Archive:PackagingDrafts/Font package naming (2009-01-13)

Foreword
This proposal is a follow-up and replacement for the naming rules rejected by FPC on 2009-01-06. It is more invasive and will require more changes, but should produce more pleasant font package names.

Renaming of existing packages that fail this new rule will wait for the corresponding policy to be finalised, or for a specific FPC exception.

The change consists of the addition one section to our current font policy that should be referenced in Packaging/NamingGuidelines (alternatively it could be transcluded in both pages).

Naming
Fedora font packages are named [foundryname-]projectname[-fontfamilyname]-fonts, in lowercase.

Clarifications

 * 1) For Fedora purposes a “foundry” is an entity that publishes a set of fonts with consistent font QA rules. Thus a generic hosting service such as Sourceforge is not a foundry, but the Open Font Library is.
 * 2) It is good practice to contract foundryname- in a short prefix.
 * 3) The foundryname- prefix can optionally be skipped:
 * 4) * for entities that never released more than one font family, or
 * 5) * when the font project and the publishing entity are one and the same.
 * 6) If projectname or foundryname are repeated in fontfamilyname, they can be dropped from fontfamilyname.
 * 7) When foundryname, projectname or fontfamilyname contain the font or fonts affix, this affix should be dropped from them.
 * 8) -fontfamilyname should not be included in the srpm name of a package that includes several different font families.
 * 9) If any element of the naming contains spaces, they should be replaced by “-”.
 * 10) The use of the -fonts suffix is not dependant on the actual number of font files in the package.

When in doubt, ask the mailing list for clarification.

Examples
Notes: