Hello!

Nicolas Mailhot nicolas.mailhot at laposte.net
Mon Mar 26 08:52:29 UTC 2012


Le Sam 24 mars 2012 21:52, Corey Richardson a écrit :

> "Nowadays Fedora converges on OpenType (TTF/OTF) fonts in Unicode
> encoding, and no efforts should be wasted on legacy formats. "
>
> Does this mean bitmap fonts should be converted (possibly by hand), or
> are BDF/PCF fine? (I ask this because some of my favorite fonts are
> bitmap)

You don't have to convert them, but I'm quite certain that packaging anything
not in OpenType format will be an exercise in frustration. If you rally want
bitmap fonts there are Opentype bitmap containers IIRC.

> 2. What are the most common pitfalls / What should I be aware of as I
> depart on this journey?

The technical part itself will be simple. For clean opentype fonts you only
need to get the current font package template, write a description, and insert
the font file names.

A special case if fonts built from sources which may be a bit harder depending
on the robustness of upstream's build process.

For most fonts, the bulk of the work will be in identifying the font sources
and licensing, and getting the naming right (a lot of old fonts are a legal
tangle, their metadata lies about licensing, their naming is atrocious). No
script will do that for you.

It's a lot easier if you start from an already curated font library with clean
licensing (SIL was nice but I think we've almost full coverage, I started
http://arkandis.tuxfamily.org/adffonts.html but I don't have the time to
finish it, and there are probably many nice fonts in the google font library
that need packaging.

Some high profile fonts that need packaging are Google's new roboto font and
the ubuntu font (have its license oked by spot but I don't think it would be a
problem)

When in doubt about a font license (if it's not oked on the wiki) always ask
spot.

-- 
Nicolas Mailhot



More information about the fonts mailing list