From: chad <yandros@gmail.com>
To: Richard Stallman <rms@gnu.org>
Cc: emacs-tangents@gnu.org
Subject: Re: Ligature support
Date: Sat, 20 Nov 2021 13:29:19 -0800 [thread overview]
Message-ID: <CAO2hHWbHmfuiiaS+=+26YMbfRpcJP6rrUQYyur75kFNyEofF+A@mail.gmail.com> (raw)
In-Reply-To: <E1moKxz-0007Fl-FU@fencepost.gnu.org>
[-- Attachment #1: Type: text/plain, Size: 834 bytes --]
On Fri, Nov 19, 2021 at 11:39 PM Richard Stallman <rms@gnu.org> wrote:
> Is all the material available in a way that avoids the SIL font license?
> It is better to avoid that if possible.
Out of curiosity, what makes the SIL licence something to be avoided? The
GNU project licenses list (https://www.gnu.org/licenses/license-list.en.html)
doesn't mention anything that makes me think it should be avoided, and in
fact it suggests to me that the SIL license is one of the better choices.
(This is largely academic to me at this point, but in my other work-life,
we almost released some content-specific icons as part of a font, so I
looked a bit to make sure that there was reasonable libre license, and SIL
seemed to be a reasonable choice. If something changed or I missed
something, I'm interested.)
Thanks in advance,
~Chad
[-- Attachment #2: Type: text/html, Size: 1305 bytes --]
next prev parent reply other threads:[~2021-11-20 21:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87cznths5j.fsf@gnus.org>
[not found] ` <87wnlwyox9.fsf@gnus.org>
[not found] ` <83lf2cq7n5.fsf@gnu.org>
[not found] ` <87wnlnkxbo.fsf@gnus.org>
[not found] ` <83cznfdohr.fsf@gnu.org>
[not found] ` <87zgqik9bk.fsf@gnus.org>
[not found] ` <83v916d64z.fsf@gnu.org>
[not found] ` <878ry2k6qz.fsf@gnus.org>
[not found] ` <83tugqd488.fsf@gnu.org>
[not found] ` <87zgqiiq8c.fsf@gnus.org>
[not found] ` <83r1bud3or.fsf@gnu.org>
[not found] ` <87r1buipf5.fsf@gnus.org>
[not found] ` <83o86yd0ig.fsf@gnu.org>
[not found] ` <87a6iiimay.fsf@gnus.org>
[not found] ` <83fssact8i.fsf@gnu.org>
[not found] ` <87k0hmgre3.fsf@gnus.org>
[not found] ` <87pmrdamcw.fsf@gnus.org>
[not found] ` <CAO2hHWZAUZsNkZ51p1ANO8BtLcXxrdE9gDmj5_vkJ_sqtYViUg@mail.gmail.com>
[not found] ` <E1mmTyA-0004E9-3k@fencepost.gnu.org>
[not found] ` <CADwFkmmPpmNWDcESMO6p9kgRnW6oMjb4hfoZ0d03eLQB0oMsdw@mail.gmail.com>
[not found] ` <E1mnYRl-00074V-I1@fencepost.gnu.org>
2021-11-18 12:32 ` Ligature support Stefan Kangas
2021-11-20 7:39 ` Richard Stallman
2021-11-20 11:32 ` Stefan Kangas
2021-11-21 5:17 ` Richard Stallman
2021-11-20 21:29 ` chad [this message]
2021-11-22 4:29 ` Richard Stallman
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAO2hHWbHmfuiiaS+=+26YMbfRpcJP6rrUQYyur75kFNyEofF+A@mail.gmail.com' \
--to=yandros@gmail.com \
--cc=emacs-tangents@gnu.org \
--cc=rms@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.
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).