[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

01/01: doc: Add a section on naming conventions for font packages.

From: Andreas Enge
Subject: 01/01: doc: Add a section on naming conventions for font packages.
Date: Sun, 23 Nov 2014 20:38:06 +0000

andreas pushed a commit to branch master
in repository guix.

commit 7fec52b78b1b5f762a82ef900e0b871da40e7f92
Author: Andreas Enge <address@hidden>
Date:   Sun Nov 23 18:23:35 2014 +0100

    doc: Add a section on naming conventions for font packages.
    * doc/guix.texi (Fonts): New section.
      (Package naming): Reference the new section.
 doc/guix.texi |   40 ++++++++++++++++++++++++++++++++++++++++
 1 files changed, 40 insertions(+), 0 deletions(-)

diff --git a/doc/guix.texi b/doc/guix.texi
index c0b9668..b5aefc0 100644
--- a/doc/guix.texi
+++ b/doc/guix.texi
@@ -4745,6 +4745,7 @@ needed is to review and apply the patch.
 * Version Numbers::      When the name is not enough.
 * Python Modules::       Taming the snake.
 * Perl Modules::         Little pearls.
+* Fonts::                Fond of fonts.
 @end menu
 @node Software Freedom
@@ -4796,6 +4797,8 @@ already part of the official project name.  But 
 Modules} and @ref{Perl Modules} for special rules concerning modules for
 the Python and Perl languages.
+Font package names are handled differently, @pxref {Fonts}.
 @node Version Numbers
 @subsection Version Numbers
@@ -4871,6 +4874,43 @@ are also prepended by @code{perl-}.  Such modules tend 
to have the word
 prefix.  For instance, @code{libwww-perl} becomes @code{perl-libwww}.
address@hidden Fonts
address@hidden Fonts
+For fonts that are in general not installed by a user for typesetting
+purposes, or that are distributed as part of a larger software package,
+we rely on the general packaging rules for software; for instance, this
+applies to the fonts delivered as part of the X.Org system or fonts that
+are part of TeX Live.
+To make it easier for a user to search for fonts, names for other packages
+containing only fonts are constructed as follows, independently of the
+upstream package name.
+The name of a package containing only one font family starts with
address@hidden; it is followed by the foundry name and a dash @code{-}
+if the foundry is known, and the font family name, in which spaces are
+replaced by dashes (and as usual, all upper case letters are transformed
+to lower case).
+For example, the Gentium font family by SIL is packaged under the name
+For a package containing several font families, the name of the collection
+is used in the place of the font family name.
+For instance, the Liberation fonts consist of three families,
+Liberation Sans, Liberation Serif and Liberation Mono.
+These could be packaged separately under the names
address@hidden and so on; but as they are distributed together
+under a common name, we prefer to package them together as
+In the case where several formats of the same font family or font collection
+are packaged separately, a short form of the format, prepended by a dash,
+is added to the package name.  We use @code{-ttf} for TrueType fonts,
address@hidden {-otf} for OpenType fonts and @code{-type1} for PostScript Type 1
 @node Bootstrapping
 @section Bootstrapping

reply via email to

[Prev in Thread] Current Thread [Next in Thread]