From: Eli Zaretskii <eliz@gnu.org>
To: Jean Louis <bugs@gnu.support>
Cc: yuri.v.khan@gmail.com, paaguti@gmail.com, emacs-devel@gnu.org,
luangruo@yahoo.com, rms@gnu.org
Subject: Re: svg library ideas
Date: Sat, 04 Feb 2023 10:49:56 +0200 [thread overview]
Message-ID: <83wn4xu85n.fsf@gnu.org> (raw)
In-Reply-To: <Y94D+8fA5tmQcw2N@protected.localdomain> (message from Jean Louis on Sat, 4 Feb 2023 10:06:35 +0300)
> Date: Sat, 4 Feb 2023 10:06:35 +0300
> From: Jean Louis <bugs@gnu.support>
> Cc: Eli Zaretskii <eliz@gnu.org>,
> Pedro Andres Aranda Gutierrez <paaguti@gmail.com>,
> emacs-devel@gnu.org, luangruo@yahoo.com, rms@gnu.org
>
> Can you use this one?
>
> AmanithSVG, a software library for reading and rendering SVG files:
> https://www.amanithsvg.com/
That site says:
Source Code
In order to satisfy all the needs to have total control over the
software, the complete AmanithSVG (along with AmanithVG) engine
source code is always available as a licensing option.
How can we use a library that is not Free Software and whose source
code is only available "as a licensing option"? The SDK they tell to
download includes only binaries and header files, the sources of the
library itself are indeed not available.
next prev parent reply other threads:[~2023-02-04 8:49 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-03 6:39 Re: svg library ideas Pedro Andres Aranda Gutierrez
2023-02-03 8:00 ` Eli Zaretskii
2023-02-03 11:25 ` Jean Louis
2023-02-03 12:31 ` Po Lu
2023-02-03 13:37 ` Jean Louis
2023-02-03 12:42 ` Eli Zaretskii
2023-02-03 13:56 ` Yuri Khan
2023-02-04 7:06 ` Jean Louis
2023-02-04 8:49 ` Eli Zaretskii [this message]
2023-02-04 18:38 ` Jean Louis
2023-02-05 4:29 ` Richard Stallman
2023-02-04 7:07 ` Jean Louis
[not found] <87lelo15vw.fsf.ref@yahoo.com>
2023-01-27 13:09 ` Po Lu
2023-01-27 16:36 ` Jean Louis
2023-01-29 5:18 ` Richard Stallman
2023-01-29 5:29 ` Po Lu
2023-01-29 6:44 ` Jim Porter
2023-01-29 6:51 ` Eli Zaretskii
2023-01-31 4:19 ` Richard Stallman
2023-01-31 5:16 ` Po Lu
2023-02-02 5:03 ` Richard Stallman
2023-02-02 5:18 ` Po Lu
2023-02-03 0:19 ` Gregory Heytings
2023-01-29 6:43 ` Eli Zaretskii
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=83wn4xu85n.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=bugs@gnu.support \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.com \
--cc=paaguti@gmail.com \
--cc=rms@gnu.org \
--cc=yuri.v.khan@gmail.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/emacs.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).