all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Andreas Enge <andreas@enge.fr>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org, Nils Gillmann <niasterisk@grrlz.net>
Subject: Re: [PATCH] Add un-fonts (new patch, closes old thread)
Date: Sun, 6 Mar 2016 16:20:40 +0100	[thread overview]
Message-ID: <20160306152040.GA16110@solar> (raw)
In-Reply-To: <87io0zsomg.fsf@gnu.org>

On Sun, Mar 06, 2016 at 02:49:11PM +0100, Ludovic Courtès wrote:
> > +    (name "font-un-fonts")
> Shouldn’t it be “font-un-fonts-core” since that’s what the tarball is
> called?

I just read up on our font naming guidelines in the manual:
"The name of a package containing only one font family starts with font-; it is followed by the foundry name and a dash - 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 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. (...) we prefer to package them together as font-liberation"

Given that, I wonder if the name should not simply be "font-un". There is no
foundry, and "un" seems to be the collection name, given that all individual
fonts are named "UnSomething". A bit unusual as a name, but why not?

Andreas

  reply	other threads:[~2016-03-06 15:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-04 22:11 [PATCH] Add un-fonts (new patch, closes old thread) Nils Gillmann
2016-03-06 13:49 ` Ludovic Courtès
2016-03-06 15:20   ` Andreas Enge [this message]
2016-03-06 16:17     ` Nils Gillmann
2016-03-06 16:43       ` Andreas Enge
2016-03-06 16:55         ` Nils Gillmann
2016-03-06 15:25   ` Nils Gillmann
2016-03-06 16:43 ` Nils Gillmann
2016-03-06 16:50   ` Nils Gillmann
2016-03-06 17:23     ` Nils Gillmann
2016-03-13 22:39       ` Ludovic Courtès

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160306152040.GA16110@solar \
    --to=andreas@enge.fr \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.org \
    --cc=niasterisk@grrlz.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.