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: Fri, 31 Oct 2014 22:30:24 +0100 [thread overview]
Message-ID: <87sii4q64v.fsf@gnu.org> (raw)
In-Reply-To: <20141031175840.GA16902@debian> (Andreas Enge's message of "Fri, 31 Oct 2014 18:58:40 +0100")
Andreas Enge <andreas@enge.fr> skribis:
> On Fri, Oct 31, 2014 at 01:02:44AM +0300, Alex Kost wrote:
[...]
>> I'm against any strict binding to an upstream name. Why should we stick
>> to a (potentially strange) upstream name if we know better how a package
>> should be called?
>
> This is what we have done so far and it is part of the packaging guidelines.
Yes, and I think we should stick to that for software packages, with the
already-documented exceptions of ‘perl-’ and ‘python-’.
Now, I think a good reason to add an exception for fonts is that it
would make it easier to search for them: a software package can be
searched by keyword quite reasonably (with ‘guix package --search’ &
co.), but this is not the case for a font. Being able to type ‘guix
package -A ^font’ (say) is convenient.
Furthermore, unlike software packages, what matters here is the actual
name of the font or font collection, not the “system name” or “tarball
name.”
> 1)
> Do we want to have the font format as part of the name?
> Not having it would make things easier for packages containing several
> formats; a user looking only for special types of fonts would then have to
> go through the package descriptions. We could then prepend "font" or "fonts"
> to the package name and drop it from inside (or keep it additionally inside,
> which would be somewhat strange, but would avoid strange names occurring for
> "unifont", for instance).
>
> 2)
> Do we distinguish between packages containing one font (possibly in several
> variants), prepending it with "font-", and packages containing several
> fonts, prepending it with "fonts-", or do we go with a common prefix?
>
> 3)
> If we want to add the font format to the package name, which font formats
> do we want to "support"? We need a complete list.
>
> 4)
> For the sake of argument, assume we decided on ttf and otf in 2).
> Then packages containing only ttf could be prepended with "ttf" or "ttf-font"
> or something like this, likewise for packages containing only otf.
> We could use the "file extension" such as "ttf", or any longer version
> such as "true-type-fonts".
All good points, indeed.
I’m not completely sure we can come up with a strict algorithm for the
naming scheme that we will not want to change two weeks later. ;-)
Here’s a possible answer to the above questions, informally:
• Use ‘font-FOUNDRY-FAMILY’ or ‘font-FAMILY’ or
‘font-FOUNDRY-COLLECTION’ or ‘font-COLLECTION’ as the name.
Examples: ‘font-bitstream-vera’, ‘font-liberation’, ‘font-unifont’.
• Use ‘font-.*-FORMAT’ only when there happens to be separate packages
for separate formats. FORMAT would be the format short name, like
‘ttf’, ‘otf’, ‘type1’.
WDYT, fellow nitpickers? :-)
IMO the goal should be to find something convenient for users.
Sometimes, maybe, there will be several valid choices for the package
name, but that’s fine, I think.
Ludo’.
next prev parent reply other threads:[~2014-10-31 21:30 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 [this message]
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
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=87sii4q64v.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.