[PATCH] doc: Add a section on naming conventions for font packages.

[PATCH] doc: Add a section on naming conventions for font packages.

[Andreas Enge]

I finally got around to word Ludovic's suggestion on names for font packages,
which I think we agreed upon. Corrections are welcome.

Andreas


* doc/guix.texi (Fonts): New section.
  (Package naming): Reference the new section.
---
 doc/guix.texi | 40 ++++++++++++++++++++++++++++++++++++++++
 1 file changed, 40 insertions(+)

diff --git a/doc/guix.texi b/doc/guix.texi
index c0b9668..11ae2e9 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 @pxref{Python
 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}.
 
 
+@node Fonts
+@subsection 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
+@code{font-}; 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
+@code{font-sil-gentium}.
+
+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
+@code{font-liberation-sans} and so on; but as they are distributed together
+under a common name, we prefer to package them together as
+@code{font-liberation}.
+
+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,
+@code {-otf} for OpenType fonts and @code{-type1} for PostScript Type 1
+fonts.
+
+
 
 @node Bootstrapping
 @section Bootstrapping
-- 
2.1.2

Re: [PATCH] doc: Add a section on naming conventions for font packages.

[Alex Kost]

Thanks!

Andreas Enge (2014-11-23 20:27 +0300) wrote:

> I finally got around to word Ludovic's suggestion on names for font packages,
> which I think we agreed upon. Corrections are welcome.

[...]
> +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,
There should double space here  ↑ I think.

-- 
Alex

Re: [PATCH] doc: Add a section on naming conventions for font packages.

[Andreas Enge]

On Sun, Nov 23, 2014 at 11:12:21PM +0300, Alex Kost wrote:
> > +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,
> There should double space here  ↑ I think.

Thanks, added.

Periods at the end of a line are okay without extra spaces?

Andreas

Re: [PATCH] doc: Add a section on naming conventions for font packages.

[Ludovic Courtès]

Andreas Enge <andreas@enge.fr> skribis:

> I finally got around to word Ludovic's suggestion on names for font packages,
> which I think we agreed upon. Corrections are welcome.

This looks good to me.

Thanks for taking the time to write it down!

Ludo’.