From: ludo@gnu.org (Ludovic Courtès)
To: Alex Griffin <a@ajgrf.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 0/3] Various new fonts
Date: Fri, 10 Feb 2017 13:48:04 +0100 [thread overview]
Message-ID: <87vasidxff.fsf@gnu.org> (raw)
In-Reply-To: <1486675748.2110684.876127416.10FBD981@webmail.messagingengine.com> (Alex Griffin's message of "Thu, 09 Feb 2017 15:29:08 -0600")
Hi Alex,
Alex Griffin <a@ajgrf.com> skribis:
> I've been holding off on submitting them because they just copy TTF
> files instead of building from source, which I think may be against the
> FSDG.
I think copying TTFs is not perfect, but I don’t think it contradicts
the GNU FSDG. What part of the FSDG did you have in mind?
> I brought up this point a few months back and nothing really came of
> it. I'm submitting them now because nobody else seems concerned, and
> I've been happy enough with these packages to use them myself. Many
> free fonts make it very difficult or impossible to build from source
> anyway.
So far I see only two of our font packages that depend on Fontforge; I
think the others simply copy TTF/OTF files around.
I’m not sure which discussion you’re referring to, but I think
long-term, we should encourage font packages that build from source.
However, I would not refuse packages that copy TTF/OTF files today
because the other packages are not up to that standard yet.
WDYT?
Thanks,
Ludo’.
next prev parent reply other threads:[~2017-02-10 12:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-09 21:29 [PATCH 0/3] Various new fonts Alex Griffin
2017-02-10 12:48 ` Ludovic Courtès [this message]
2017-02-10 15:27 ` Alex Griffin
2017-02-10 15:56 ` Ludovic Courtès
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87vasidxff.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=a@ajgrf.com \
--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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).