Choosing the right font format to package

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(New page: {{CompactHeader|fonts-sig}} ''Navigating the multi font format hell'' {{Admon/note | Public discussion conclusions | This article summarises the conclusions of the debate initiated [htt...)
 
 
Line 31: Line 31:
 
# Do not package new Type1 fonts. If someone cares about a Type1 font, he should get it converted to OpenType CFF before we consider packaging it.
 
# Do not package new Type1 fonts. If someone cares about a Type1 font, he should get it converted to OpenType CFF before we consider packaging it.
  
{{:Fonts_SIG_signature}} [[Category:Fonts packaging]]
+
{{:Fonts_SIG_signature}} [[Category:Fonts packaging|Format choice for fonts]]

Latest revision as of 16:40, 25 July 2008

A page of the Fonts Special Interest Group

Navigating the multi font format hell


Note.png
Public discussion conclusions
This article summarises the conclusions of the debate initiated there.


In this page:

  • OTF is used as an abbreviation for the OpenType CFF format,
  • TTF is used as an abbreviation for the OpenType TT format.


The following decision tree is used to choose the font format to package in Fedora:

  1. If upstream works with one preferred OpenType format (TTF or OTF), use this format.
  2. If a font is available in both TTF and OTF versions, package the most recent (timestamp) and complete (size) version.
  3. If both formats are generated from the same source upstream, package the OTF version.
    • Most font editors work with cubic splines natively, and we don't ignore CFF hinting the way we do TT hinting (different legal context), so the OTF version may be slightly better for us.
  4. For already packaged fonts, continue to package the TTF format till OpenOffice.org is fixed.
    • The rationale is to avoid upsetting users that already created documents using the TTF version.
    • After OpenOffice.org is fixed apply the same policy as for new packages.
  5. As an exception, a package maintainer is authorized to use his best judgement and package both versions in a single rpm, if a user manages to convince him it's not a terribly bad idea.
    • Never do it by default.
    • That will double the package size so livecd and bandwidth-constrained users won't be happy about it.
    • Also we have little control on the version fontconfig will serve to applications.
    • But at least the packaging will be simple.
  6. Since it seems several projects use different font names for the OTF and TTF variants, systematically package a fontconfig ruleset that maps the font name we do not package to the one we do.

And lastly :

  1. Do not package new Type1 fonts. If someone cares about a Type1 font, he should get it converted to OpenType CFF before we consider packaging it.


Idea.png
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.