From: Alex Kost <alezost@gmail.com>
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 2/2] gnu: Add 'ttf-liberation'.
Date: Thu, 30 Oct 2014 15:52:50 +0300 [thread overview]
Message-ID: <8738a5g1nh.fsf@gmail.com> (raw)
In-Reply-To: <20141030075640.GB27584@debian> (Andreas Enge's message of "Thu, 30 Oct 2014 08:56:40 +0100")
Andreas Enge (2014-10-30 10:56 +0300) wrote:
> On Thu, Oct 30, 2014 at 10:27:49AM +0300, Alex Kost wrote:
>> Why should? What about “ttf-dejavu”? Should it be called
>> “dejavu-fonts-ttf” then?
>
> Yes, that was a mistake, maybe inspired from the debian package name.
> We should rename it.
I don't understand why you call it a mistake. It's just a package name
used by some distributions (and I think it's a good name). Is there a
convention to use “…-fonts-ttf” in Guix?
>> Then it shouldn't be prefixed with "ttf". I suggest to use "ttf-…" name
>> only for packages that provide truetype fonts only. As for the other
>> font packages, I think they should have "font"/"fonts" in their names,
>> no matter would it be in the beginning (font-misc-ethiopic) or in the
>> end (terminus-font).
>
> Then what if it contains other types of fonts? Texlive-data/texfm-dist/fonts
> contains the following 20 subdirectories:
> afm cmap fea map ofm ovf pfm sfd tfm type1
> cid enc lig misc opentype ovp pk source truetype vf
> (not all of them are fonts, some are just metrics and some I do not know).
> Would you suggest to use prefixes type1-, opentype-, pk- also?
> Only if the package contains exactly one format? I think modifying our
> package name rules for fonts will open a can of worms.
I think they should be called “texlive-…”.
What I see in "Arch Linux" is a lot of “ttf-…” packages (including
“ttf-liberation” and “ttf-dejavu”). IIUC Debian uses the same names for
TrueType fonts. And I like it. But anyway, if “liberation-fonts-ttf”
is the prefered variant, I'll fix my patch. But I think “ttf-dejavu”
should be renamed into “dejavu-fonts-ttf” at first. And what about
“freefont-ttf” and “ttf-bitstream-vera”?
next prev parent reply other threads:[~2014-10-31 15:49 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 [this message]
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
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=8738a5g1nh.fsf@gmail.com \
--to=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.