From: David Pirotte <david@altosw.be>
To: Neil Jerram <neil@ossau.homelinux.net>
Cc: guile-user@gnu.org
Subject: Re: Imagemagick and Guile
Date: Sun, 11 Jan 2015 14:12:38 -0200 [thread overview]
Message-ID: <20150111141238.77b0ccd2@capac> (raw)
In-Reply-To: <a62144d1f27e7336ef184de060b54428@ossau.homelinux.net>
[-- Attachment #1: Type: text/plain, Size: 1096 bytes --]
Hello,
> ...
> Personally, I find using the FFI much more fun than writing a 'proper'
> Guile binding
> ...
I would consider GraphicsMagick instead http://www.graphicsmagick.org/index.html
There has been a fork in 2002, due to license problems,
... ImageMagick from ImageMagick Studio LLC abandoned the MIT X11 style
license it had been using since 1992, and switched between several different
licenses until it ended up with one based on the Apache license, which is
intended to penalize projects which borrow some of its source code, or fork
from it. Since that time, GraphicsMagick has not incorporated any
ImageMagick source code
... On November 27, 2003 ImageMagick Studio LLC applied to register
"ImageMagick" as its trademark, and it was awarded this registered trademark
(serial number 78333969) on August 30, 2005. Those who re-distribute
modified versions of "ImageMagick" (e.g. patched or improved) under license
as "ImageMagick" now face the risk of arbitrary trademark infringement
claims by ImageMagick Studio LLC ...
Cheers,
David
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-01-11 16:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-11 9:09 Imagemagick and Guile A0
2015-01-11 11:07 ` Nala Ginrut
2015-01-11 12:02 ` John Darrington
2015-01-11 12:56 ` A0
2015-01-11 12:11 ` Neil Jerram
2015-01-11 12:53 ` A0
2015-01-11 16:12 ` David Pirotte [this message]
2015-01-11 12:46 ` 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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150111141238.77b0ccd2@capac \
--to=david@altosw.be \
--cc=guile-user@gnu.org \
--cc=neil@ossau.homelinux.net \
/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).