From: Julien Lepiller <julien@lepiller.eu>
To: guix-devel@gnu.org, Leo Prikler <leo.prikler@student.tugraz.at>,
Yasuaki Kudo <yasu@yasuaki.com>
Subject: Re: Add Microsoft Cascadia Code font?
Date: Sun, 10 Jan 2021 07:28:55 -0500 [thread overview]
Message-ID: <9897CE46-E860-4BB2-BA5D-B262709FF112@lepiller.eu> (raw)
In-Reply-To: <5a04e459a00f1f8e6051d4ad7e77d4fd090fca7a.camel@student.tugraz.at>
[-- Attachment #1: Type: text/plain, Size: 1924 bytes --]
I might be wrong, but I thought fonts were considered non-functional data. If that's the case, isn't cc-by-nc-nd acceptable?
Le 10 janvier 2021 05:38:16 GMT-05:00, Leo Prikler <leo.prikler@student.tugraz.at> a écrit :
>Hi Yasu,
>
>I don't think it'll be so simple. It appears, that nerd-fonts already
>includes – or at least has the potential to include – some non-free
>glyphs, which would in turn then be part of Cascadia. An instance
>would be pomicons [1], which are licensed as CC BY-NC-ND. A reviewer
>would first have to verify, that Cascadia is indeed wholly covered
>under the OFL or at least under a set of free licenses.
>
>Yes, it sucks having to put that much effort into packaging a font, but
>if you just want to have a workable font for programming, there are
>probably better solutions than Cascadia, some of which are already
>packaged in Guix – e.g. font-fira-code.
>
>Regards,
>Leo
>
>[1] https://github.com/gabrielelana/pomicons
>
>Am Sonntag, den 10.01.2021, 19:11 +0900 schrieb Yasuaki Kudo:
>> Thank you for your comments!
>>
>> Because I don't have a lot of time, is it ok to just re-format the
>> original submission, get it committed with the comment that the
>> package needs to be compiled rather than copied, when someone (or I)
>> wants to so properly?
>>
>> Cheers,
>> Yasu
>>
>>
>> > On Jan 10, 2021, at 18:16, Leo Prikler <
>> > leo.prikler@student.tugraz.at> wrote:
>> >
>> > Hello Vincent,
>> >
>> > there is no .tar of the fonts however, that's a source tarball
>> > generated by github. To be fair, one should probably build this
>> > font
>> > (and other fonts) from source instead. In particular, we might
>> > want to
>> > package nerd-fonts[1] first, since Cascadia appears to be an
>> > iteration
>> > of it.
>> >
>> > Regards,
>> > Leo
>> >
>> > [1] https://github.com/ryanoasis/nerd-fonts
>> >
>> >
[-- Attachment #2: Type: text/html, Size: 2506 bytes --]
next prev parent reply other threads:[~2021-01-10 12:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-10 9:16 Add Microsoft Cascadia Code font? Leo Prikler
2021-01-10 9:39 ` Vincent Legoll
2021-01-10 10:11 ` Yasuaki Kudo
2021-01-10 10:38 ` Leo Prikler
2021-01-10 10:56 ` Yasuaki Kudo
2021-01-10 12:28 ` yasu
2021-01-10 12:28 ` Julien Lepiller [this message]
2021-01-10 12:55 ` yasu
2021-01-10 13:09 ` Leo Prikler
2021-01-10 14:28 ` Julien Lepiller
2021-01-10 23:37 ` Mark H Weaver
-- strict thread matches above, loose matches on Subject: below --
2021-01-10 8:04 yasu
2021-01-10 8:46 ` Vincent Legoll
2021-01-10 8:51 ` Vincent Legoll
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=9897CE46-E860-4BB2-BA5D-B262709FF112@lepiller.eu \
--to=julien@lepiller.eu \
--cc=guix-devel@gnu.org \
--cc=leo.prikler@student.tugraz.at \
--cc=yasu@yasuaki.com \
/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).