[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH] Add un-fonts (new patch, closes old thread)
From: |
Andreas Enge |
Subject: |
Re: [PATCH] Add un-fonts (new patch, closes old thread) |
Date: |
Sun, 6 Mar 2016 16:20:40 +0100 |
User-agent: |
Mutt/1.5.24 (2015-08-30) |
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
Re: [PATCH] Add un-fonts (new patch, closes old thread), Nils Gillmann, 2016/03/06