From Fedora Project Wiki

(New page: {{CompactHeader|fonts-sig}} {{Admon/warning | Abandoned proposal | This proposal was reviewed by FPC on 2009-01-06. FPC felt it didn't try hard enough ...)
 
No edit summary
Line 1: Line 1:
{{CompactHeader|fonts-sig}}
{{CompactHeader|fonts-sig}}
{{Admon/warning | Abandoned proposal  |
This proposal was reviewed by [[FPC]] on [[Packaging:Minutes/20090106|2009-01-06]]. FPC felt it didn't try hard enough to achieve distribution-wide naming consistency. A [[PackagingDrafts/Font package naming (2009-01-13)|more ambitious and invasive proposal]] was therefore written that supersedes this page.
}}


== Foreword ==
== Foreword ==

Revision as of 23:10, 13 January 2009

A page of the Fonts Special Interest Group

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

It consists of the addition one section to our current font policy that should be referenced in Packaging/NamingGuidelines.

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:
    • for entities that never released more than one font family, or
    • when the font project and the publishing entity are one and the same.
  4. The projectname- prefix can optionally be skipped, when the project and the font family names are one and the same.
  5. The foundryname affix should not be repeated in fontfamilyname, even if it is present in the actual font family name.
  6. The use of the -fonts suffix is not dependant on the actual number of font files in the package.
  7. When foundryname, projectname or fontfamilyname contain the font or fonts affix, it should be skipped to avoid foofont-fonts packages.

When in doubt, ask the mailing list for clarification.

Examples

Font package naming examples
Source package (src.rpm) Binary (sub)package Description
Fonts Other Fonts Other
apanov-heuristica-fonts apanov-heuristica-fonts “Heuristica” font family published by Andrey Panov, “apanov”.
sil-abyssinica-fonts sil-abyssinica-fonts “Abyssinica SIL” font family published by the “SIL” foundry.
oflb-brett-fonts oflb-brett-fonts “BrettFont” font family published on the “Open Font Library”, “oflb” foundry.
dejavu-fonts
  • dejavu-sans-fonts
  • dejavu-sans-mono-fonts
  • dejavu-serif-fonts
The three “DejaVu” font families self-published by the “DejaVu” project.
dejavu-fonts-common Utility font subpackage with no font files inside.
google-droid-fonts
  • google-droid-sans-fonts
  • google-droid-sans-mono-fonts
  • google-droid-serif-fonts
The three “Droid” font families published by “Google”, as part of its “Droid” release.
google-droid-fonts-common Utility font subpackage with no font files inside.
un-core-fonts
  • un-core-pilgi-fonts
  • un-core-dinaru-fonts
  • un-core-batang-fonts…
“UN Core” fonts published by the “UN” project.
un-core-fonts-common Utility font subpackage with no font files inside.
openoffice.org openoffice.org-opensymbol-fonts The “OpenSymbol” font family published as part of “openoffice.org”.
  • openoffice.org-writer
  • openoffice.org-calc…
ctan-cm-lgc-fonts
  • ctan-cm-lgc-sans-fonts
  • ctan-cm-lgc-roman-fonts
  • ctan-cm-lgc-typewriter-fonts…
“CM LGC” font families published by the “CTAN” foundry.
ctan-cm-lgc-fonts-common Utility font subpackage with no font files inside.
ctan-cm-lgc-tex TEX overlay for ctan-cm-lgc fonts


Fonts in Fedora
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.