all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel@gnu.org, Alex Kost <alezost@gmail.com>
Subject: Re: Font package naming convention
Date: Mon, 03 Nov 2014 09:53:21 +0100	[thread overview]
Message-ID: <87d294u0la.fsf@gnu.org> (raw)
In-Reply-To: <20141102174935.GF6865@debian> (Andreas Enge's message of "Sun, 2 Nov 2014 18:49:35 +0100")

Andreas Enge <andreas@enge.fr> skribis:

> On Sun, Nov 02, 2014 at 06:18:19PM +0100, Ludovic Courtès wrote:
>> Some of the fonts created by foundries are often referred to it using
>> the foundry’s name, such as “Bitstream Vera”; there are also
>> counter-examples, like Gentium, Charis, etc. (by SIL.)
>> 
>> So, again very informally, I would suggest to use the foundry name in
>> cases where people expect to see it, and in cases where it removes
>> ambiguity with similarly-named fonts.
>> 
>> What do people think?
>
> I think it would be nice to add the foundry when it is know, such as
> sil-gentium etc.; personally I find it an interesting information to have
> (we would get a complete list of all packages sil fonts, for instance).

OK, it makes sense to me.

If there’s rough consensus on this, the next step would be to write this
informal rule in the manual, and to update package names.

Any volunteer?  Alex?  :-)

Thanks,
Ludo’.

  reply	other threads:[~2014-11-03  8:53 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-28  6:53 [PATCH 2/2] gnu: Add 'ttf-liberation' Alex Kost
2014-10-28  8:10 ` Ludovic Courtès
2014-10-29 22:16   ` Andreas Enge
2014-10-30  7:27     ` Alex Kost
2014-10-30  7:56       ` Andreas Enge
2014-10-30 12:52         ` Alex Kost
2014-10-30 13:36           ` Andreas Enge
2014-10-30 18:55             ` Alex Kost
2014-10-30 17:20           ` Font package naming convention Ludovic Courtès
2014-10-30 17:32             ` Andreas Enge
2014-10-30 22:54               ` Ludovic Courtès
2014-10-30 18:55             ` Alex Kost
     [not found]               ` <20141030191743.GB19999@debian.eduroam.u-bordeaux.fr>
2014-10-30 22:02                 ` Alex Kost
2014-10-31 17:58                   ` Andreas Enge
2014-10-31 18:00                     ` Andreas Enge
2014-10-31 21:30                     ` Ludovic Courtès
2014-11-01  9:52                       ` Andreas Enge
2014-11-02 17:18                         ` Ludovic Courtès
2014-11-02 17:49                           ` Andreas Enge
2014-11-03  8:53                             ` Ludovic Courtès [this message]
2014-11-03  9:30                               ` Andreas Enge
2014-11-03 13:36                                 ` Alex Kost
2014-11-03 20:28                                 ` Ludovic Courtès
2014-11-19  9:01                                 ` Ludovic Courtès
2014-11-19 10:22                                   ` Andreas Enge
2014-11-20  7:09                                   ` Alex Kost
2014-11-23 20:13                                     ` [PATCH] gnu: Add 'font-liberation' Alex Kost
2014-11-24 14:12                                       ` Ludovic Courtès
2014-11-01  9:36                     ` Font package naming convention Alex Kost
2014-11-01  9:45                       ` Andreas Enge
2014-11-01 10:55                         ` Alex Kost

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=87d294u0la.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=alezost@gmail.com \
    --cc=andreas@enge.fr \
    --cc=guix-devel@gnu.org \
    /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.