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: Sun, 02 Nov 2014 18:18:19 +0100 [thread overview]
Message-ID: <87ioixo71g.fsf@gnu.org> (raw)
In-Reply-To: <20141101095205.GB30939@debian> (Andreas Enge's message of "Sat, 1 Nov 2014 10:52:05 +0100")
Andreas Enge <andreas@enge.fr> skribis:
> On Fri, Oct 31, 2014 at 10:30:24PM +0100, Ludovic Courtès wrote:
>> Furthermore, unlike software packages, what matters here is the actual
>> name of the font or font collection, not the “system name” or “tarball
>> name.”
>> 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? :-)
>
> This sounds like quite an interesting solution - so we would completely drop
> the upstream package name and only go for the font name (which would normally
> be some part of the upstream package name, I suppose).
>
> What would be the role of FOUNDRY? Should we try to find it out for most
> fonts, or would it only be there to avoid confusions for fonts such as
> Garamond?
Some fonts are created by hobbyists rather than a foundry.
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?
>> 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.
>
> Maybe we could refine the rules once an ambiguity occurs and see if we can
> lift it.
Sure.
> One suggestion: I would like to keep the names of the x.org fonts as they
> are, following the software package guidelines. I think they are more software
> than fonts that actual users would employ to typeset their documents.
Yes, I agree.
Thanks,
Ludo’.
next prev parent reply other threads:[~2014-11-02 17:18 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 [this message]
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=87ioixo71g.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.