ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Pontus Lurcock <pont@talvi.net>
Subject: Re: Metapost/Metafun Q: using variables and "building blocks"?
Date: Sun, 06 May 2012 14:30:47 +0200	[thread overview]
Message-ID: <4FA66EF7.9080605@wxs.nl> (raw)
In-Reply-To: <20120506113350.GU31075@rae.vm.bytemark.co.uk>

On 6-5-2012 13:33, Pontus Lurcock wrote:
> On Sun 06 May 2012, Wolfgang Schuster wrote:
>
>>
>> Am 06.05.2012 um 11:16 schrieb luigi scarso:
>>
>>> On Sun, May 6, 2012 at 10:53 AM, Mari Voipio<mari.voipio@iki.fi>  wrote:
>>>> http://www.lucet.fi/textiles/
>>> """
>>> ConTeXt, developed by the Dutch company Pragma Advanced Document
>>> Engineering, is not open source software,
>>> """
>>> Hm, I'm not sure that it's correct.
>>
>> ConTeXt is licensed under the GPL, you can find the information in this document: http://pragma-ade.com/general/manuals/mreadme.pdf
>
> There was previous discussion and clarification on this at
> http://tex.stackexchange.com/questions/12431/using-context-commercially
> and
> http://archive.contextgarden.net/message/20110301.213750.c7a55835.en.html .

In the past (previous century, first releases) there hqad been some 
restrictions (i've forgotten which) that had to do with the fact that a 
third party was using context for a project and that we got notice that 
lawyers of that company would claimed copyright of context because it 
had become part of their workflow ... so, we had to make sure that by 
making context public it could not be used against us (like: we take 
context, add a few lines, and now it's ours). Then someone convinced us 
that people who 'd do such things would probably get themselves outcast 
from any community anyway, i.e. that there is some protection is being 
part of the tex community.

I think that there are still some recomendations with respect to not 
using the same filenames for patched files (simply because tex is always 
a large file infrastructure and we don't want to be bothered with 
support for such patched). AFAIK that is not much different than with latex.

Anyhow, license discussions are mostly wasted on me.

Hans


-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
                                              | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  reply	other threads:[~2012-05-06 12:30 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-23 17:34 Mari Voipio
2012-04-23 18:04 ` Hans Hagen
2012-05-06  8:53   ` Mari Voipio
2012-05-06  9:05     ` Mari Voipio
2012-05-06  9:16     ` luigi scarso
2012-05-06  9:56       ` Wolfgang Schuster
2012-05-06 10:17         ` luigi scarso
2012-05-06 11:33         ` Pontus Lurcock
2012-05-06 12:30           ` Hans Hagen [this message]
2012-05-06 12:47     ` Hans Hagen
2012-05-06 12:53       ` Martin Schröder
2012-05-06 12:59         ` Hans Hagen
2012-05-06 13:39       ` Mari Voipio
     [not found]         ` <4FA6822A.6070400@wxs.nl>
2012-05-08  5:53           ` Mari Voipio
2012-04-30 21:40 ` Mari Voipio
2012-05-01 17:09   ` Peter Rolf

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4FA66EF7.9080605@wxs.nl \
    --to=pragma@wxs.nl \
    --cc=ntg-context@ntg.nl \
    --cc=pont@talvi.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 NNTP newsgroup(s).