[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH] python-kivy and Adobe source-code-pro font
From: |
Alex Griffin |
Subject: |
Re: [PATCH] python-kivy and Adobe source-code-pro font |
Date: |
Wed, 10 Aug 2016 15:08:44 -0500 |
On Wed, Aug 10, 2016, at 01:42 PM, Mark H Weaver wrote:
> That said, this needn't be a blocker for including the built OTF files
> in Guix, as long as the license permits all users to copy and
> redistribute them for commercial and non-commercial purposes, as these
> fonts are considered non-functional data. See:
>
>
> http://www.gnu.org/distros/free-system-distribution-guidelines.html#non-functional-data
Are you sure about that? By my reading, that document explicitly
categorizes fonts as functional works by that document:
> “Information for practical use” includes software, documentation, fonts,
> and other data that has direct functional applications. It does not include
> artistic works that have an aesthetic (rather than functional) purpose,
> or statements of opinion or judgment.
Personally, I have avoided submitting my font-iosevka [1] package for
months because it just downloads the ttf files instead of building them
from the JavaScript source code. (Maybe when we have better node
support, eh?)
[1]: https://be5invis.github.io/Iosevka/
--
Alex Griffin