Difference between revisions of "Read Me"

From Wiki
Jump to navigation Jump to search
(Text of mreadme.pdf)
 
(New mreadme.pdf in wiki markup)
Line 3: Line 3:
 
adapted to wiki markup.   
 
adapted to wiki markup.   
  
This page is generated from mreadme.pdf on 2005.05.31.
+
This page is generated from mreadme.pdf on 2005.11.24.
  
[[User:Taco|Taco]] 14:26, 31 May 2005 (CEST)
 
 
----
 
----
  
 
== Read Me ==
 
== Read Me ==
  
=== Preamble ===  
+
=== Introduction ===
  
This document presents licence information on ConTeXt, a macro package
+
What licence suits best for a TeX like system is a matter of
written in the typographical programming language TeX. This document
+
taste. Personally we dislike any licence that needs more than a
is ''not'' an installation manual. For installation of ConTeXt and its
+
few pages of dense legal code to get the message accross. A TeX
accompanying programs we refer to the following documents:
+
related system like ConTeXt is a hybrid of programs, scripts and/
 +
or macro code as well as documentation and sample code, including
 +
graphics. TeX related systems also have a long standing tradition
 +
of providing support structures for users. In order to make
 +
support feasable, a TeX based system like ConTeXt assumes a
 +
certain logic and structure in the way the related files are
 +
named and organized in a tree structure. Even a small change in
 +
one of the elements may let such a system behave differently than
 +
manuals suggest. Swap a font, change some style defaults, leave
 +
out some pieces, and users may end up in confusion. A licence
 +
does not give a user any guarantees!
  
* [[http://www.pragma-ade.com/general/manuals/minstall.pdf How to install ConTeXt]]
 
* [[http://www.pragma-ade.com/general/manuals/mtexexec.pdf TeXexec explained]]
 
* [[http://www.pragma-ade.com/general/manuals/mtexutil.pdf TeXutil explained]]
 
  
In addition you may need the introduction and/or reference
+
In order to satisfy those responsible for distributing ConTeXt,
manual. There are more documents, but you need only these to get
+
we need to choose a licence that makes them feel comfortable.
started. Unless you are going to change and redistribute ConTeXt, you
+
Unfortunately we don't feel that comfortable with a licence that
can quit reading now.
+
does not provide the guarantees that a system will not be adapted
 +
in such ways that the advertised behaviour changes. On the other
 +
hand, it is the responsibility of those distributing and
 +
extending the system to make sure that this does not happen.
 +
However, users should not automatically assume that what they get
 +
shipped is the same as the original, which is why we stress that
 +
support (from our side) will only be given on unaltered systems.
  
=== Introduction ===
+
First of all, what is ConTeXt? It's just a bunch of macros,
 +
written in TeX and METAPOST, meant for typesetting documents. The
 +
macros are accompanied by some scripts, written in Perl (mainly
 +
the older scripts) Ruby (the official ones) and Lua (for embedded
 +
usage). The ConTeXt distribution comes with a few fonts, files
 +
that help manage resources (e.g. map files), as well as
 +
patterns (based on official ones, so this is a derived work).
 +
 
 +
The ConTeXt distribution is packaged in a zip file organized in the tds structure.
 +
 
 +
cont-tmf.zip The main distribution.
 +
cont-img.zip A few extra resources.
 +
cont-ext.zip Third party modules.
 +
 
 +
When we talk about ConTeXt we also mean its graphical companion
 +
MetaFun and foXet, an xml related product. All these are included
 +
in the main distribution archive. The documentation can be
 +
downloaded from our website, one of its mirrors, the TeX
 +
collection as distributed by TeX user groups. For some manuals,
 +
source code is available in a subversion repository. The
 +
archives are also kept on ctan.
  
'''[1.1]'''  The name ConTeXt is reserved for the distribution as
+
That said, what licence does apply? We need to distinguish
provided by Pragma ADE. This distribution is copyrighted and licensed in the
+
between things that resemble a program on the one hand and
spirit of the gnu general public licence. To prevent inconsistency in
+
documentation on the other hand. We (currently) use a different
distributions and to ease support, we will stress some details of
+
licence for either of them.
adapting sources and distributions.  
 
  
'''[1.2]'''  The ConTeXt distribution includes TeX macro files as well as
 
some utility programs written in Perl, Perl/Tk, and Ruby as well as
 
graphic macros written in the METAPOST language. The same conditions
 
apply to all files.
 
  
'''[1.3]'''  The logos associated to Pragma ADE, ConTeXt, TeXutil and related
+
=== The Code ===
programs are copyrighted by Pragma ADE and may not be used for other
 
purposes than their intended usage without permission.
 
  
'''[1.4]'''  Whenever one of the source files of ConTeXt mentions the file
 
being copyrighted by Pragma ADE, the conditions mentioned in this
 
document apply.
 
  
=== Principles ===
+
The program code (i.e. anything not under the <tt>/doc</tt> subtree)
 +
is distributed under the
  
'''[2.1]'''  Pragma ADE originally developed ConTeXt for producing highly
+
<div style="color:gray;">
structured documents as used in educational settings and process
+
: [http://creativecommons.org/licenses/GPL/2.0/ Creative Commons GNU GPL]
industry. Currently ConTeXt is used by publishers and in education, in
+
</div>
profit and non profit organizations. There are also numerous private
 
users. These all depend on ConTeXt being stable system.
 
  
'''[2.2]'''  One of the objectives of ConTeXt is the low entry level, that
+
For practical purposes distributers may also choose the LaTeX project
is, for day-to-day use no special technical (and no in-depth TeX)
+
licence, which is considered to be a bit more TeX friendly. (BSD alike
knowledge is needed. This is reflected in the user interface. We don't
+
licences, the Ruby Licence and the Apache are all licences that apply
expect users to be experts on installing TeX and adapting macros for
+
well for ConTeXt.)
local use.  
 
  
'''[2.3]'''  We try to keep ConTeXt in sync with developments in
+
In practice, users may forget about the legal part, if only because I
publishing. So far this has lead to support for output formats like
+
haven't even read  (and understood) it completely myself, so let's
pdf and alternative coding standards like xml. It has also resulted in
+
stick to what Creative Commons makes of it:
a couple of user interfaces and tools.
 
  
'''[2.4]'''  Further development of ConTeXt takes place at Pragma ADE with
+
<div style="color:gray;">
the help and input from some active users. All kinds of comment from
+
The GNU General Public License is a Free Software license. Like any Free Software
users is welcomed and will be taken seriously. When we talk about
+
license, it grants to you the four following freedoms:
ConTeXt, we refer to the version as distributed by Pragma ADE and
 
described in the official reference manual.
 
  
'''[2.5]'''  ConTeXt consists of several series of modules, that can be
+
* The freedom to run the program for any purpose.  
recognized by the fact that the filename starts with four characters
+
* The freedom to study how the program works and adapt it to your needs.  
and a dash. These core modules take care of languages, fonts, general
+
* The freedom to redistribute copies so you can help your neighbour.  
typography, data abstraction, and manipulations. On top of this core,
+
* The freedom to improve the program and release your improvements to the public, so that the whole community benefits.  
domain and task specific modules and styles are (and will become)
 
available. These can be recognized by their filename that start with a
 
character followed by a dash.  
 
  
'''[2.6]'''  For special purposes, not covered by existing functionality,
 
users can write their own extensions. ConTeXt provides hooks into the
 
core routines. These are documented in the source code.
 
  
'''[2.7]'''  ConTeXt is available for free for everyone who want to use
+
You may exercise the freedoms specified here provided that you comply
it. Distributors are free to choose between the latest official
+
with the express conditions of this license. The principal conditions
release and the (in most cases stable) beta version.  
+
are:
  
'''[2.8]'''  Experimental, and thereby potentially non-stable, versions as
+
You must conspicuously and appropriately publish on each copy
well as certain dedicated modules, will be distributed under different
+
distributed an appropriate copyright notice and disclaimer of warranty
conditions.  
+
and keep intact all the notices that refer to this License and to the
 +
absence of any warranty; and give any other recipients of the Program
 +
a copy of the GNU General Public License along with the Program. Any
 +
translation of the GNU General Public License must be accompanied by
 +
the GNU General Public License.
  
'''[2.9]'''  Modules to ConTeXt or adapted source code written by Pragma ADE
+
If you modify your copy or copies of the program or any portion of it,
for third parties as part of a project may not be distributed outside
+
or develop a program based upon it, you may distribute the resulting
that organization. They may become part of the public distribution,
+
work provided you do so under the GNU General Public License. Any
upon mutual agreement.
+
translation of the GNU General Public License must be accompanied by
 +
the GNU General Public License.
  
=== Public version ===
+
If you copy or distribute the program, you must accompany it with the
 +
complete corresponding machine-readable source code or with a written
 +
offer, valid for at least three years, to furnish the complete
 +
corresponding machine-readable source code.
  
'''[3.1]'''  ConTeXt is available as free software in the spirit of the gnu
+
Any of these conditions can be waived if you get permission from the
general public licence.
+
copyright holder.
  
'''[3.2]'''  This public version is the "official public ConTeXt
+
Your fair use and other rights are in no way affected by the above.
distribution". However, ConTeXt as part of one of the TeX
+
</div>
distributions supported by user groups can also be classified as
 
official.
 
  
'''[3.3]'''  The official version (i.e. the original zipped archive
+
=== Recommendations ===
recognized by the prefix cont-) may only be redistributed as a whole
 
and under this licence.
 
  
'''[3.4]'''  This licence does not automatically apply to third party
+
Here are a few recommendations in case you want to distribute, extend
extensions.
+
of embed ConTeXt in applications:
  
=== Third party developments ===
+
* You can best leave the code base untouched. Most of ConTeXt provides hooks and it's relatively easy to overload code. Leave the lower level system code untouched: changes may backfire when you update. Asking for more hooks is the best way to go.
  
'''[4.1]'''  This sections will not introduce limitations in use that
+
* Put your own code in the right subpaths, i.e. modules approved by the development team under <tt>.../third</tt>, and styles and whatever else under <tt>.../user</tt>. This way your code will not interfere with existing code and updating will give less problems. Keep in mind that TeX systems have their own way and order in locating files, and the load order often matters.  
conflict with the gnu general public licence. We only want to make
 
sure that the average user will get the ConTeXt they expect and that
 
we can continue to support users efficiently.  
 
  
'''[4.2]'''  Users are encouraged to develop modules cq. layout definition
+
* Don't copy styles and change a few lines, but load the base one and built/patch on top of that. In the end you may benefit from improvements to the base style.  
files for ConTeXt. However, the interface of such modules should fit
 
the general scheme philosophy.  
 
  
'''[4.3]'''  Keywords and command names should conform to the already defined
+
* Be original. The whole idea behind ConTeXt is that you can write your own styles. On the ConTeXt mailing list as well as on the Wiki there are enough advanced users to help you make a start.  
ones and therefore not clash with existing functionality. An example
 
of extending the user interface can be seen in the ppchTeX
 
module.  
 
  
'''[4.4]'''  On request, additional keywords and command names can be
+
* Don't hesitate to submit bugs reports and ask for extensions. It may even be that what you want is already present but yet undocumented.  
approved and/or assigned by the ConTeXt Task Force and, when accepted,
 
will be added to the validated definition files. The same applies to
 
the names of files and auxiliary variables. These should conform to
 
the naming scheme laid down in the documentation.  
 
  
'''[4.5]'''  Third party modules (and layout files) will not automatically
+
* If things don't work as expected, check to what extend your system matches the (more or less) standard. We provide so called minimal ConTeXt trees that can serve as a reference. Because ConTeXt evolves, make sure your system is up to date.
become part of the ConTeXt distribution, but will be collected and
 
distributed separately. One reason for this is that they fall outside
 
the maintainance responsibility of Pragma ADE. This also means that
 
for instance in the texmf directory structure, the context/base,
 
context/extra and context/sample locations are reserved for the
 
official distribution. Additions should go into context/third and user
 
specific things into context/user.  
 
  
'''[4.6]'''  We strongly advice users who write their own macros for ConTeXt,
+
* The scripts can best be called using texmfstart. This lessens dependencies on the location in the tree and ensures upward compatibility. It also prevents clashes with similary named scripts.  
to package them in document specific environments or third party
 
modules (prefixed by t-).  
 
  
'''[4.7]'''  Users may not change the official distribution and redistribute
+
* Some scripts depend on each other. Don't mess around with the existing functionality and names of the scripts and then feed them back into the standard distributions.  
that changed version as official. This will ensure the integrity of
 
ConTeXt. Local settings cq. bug fixes can be added in the files
 
cont-sys and cont-new. Distributers may add configuration settings to
 
cont-usr and cont-sys.
 
  
'''[4.8]'''  When adapted versions of ConTeXt are distributed, these versions
+
=== Documents ===
must contain the original distribution as a separate item. The runtime
 
versions (format files) must have different names and changed files
 
must have an additional \writestatus message, expressing that
 
something is changed. The rationale behind this is that some modules
 
are generic, and are sometimes distributed on request separately. When
 
distributing self contained modules and styles, a full distribution of
 
originals is not required.
 
  
'''[4.9]'''  Because many TeX systems support recursive directory search,
+
The documentation is provided under another Creative Commons licence
those who write extensions or change files, must make sure that the
 
original ConTeXt does not suffer from loading the wrong files. We
 
realize that this is not always easy, but please keep in mind that
 
there are many users who cannot sort out these problems. Together we
 
must guarantee that when users want to run original ConTeXt, nothing
 
unexpected is loaded, because it makes support nearly
 
impossible.
 
  
'''[4.10]'''  Because ConTeXt is a monolithic system, and because programming
+
<div style="color:gray;">
hooks are provided, adaptations and extensions should be put and/or
+
:Attribution NonCommercial ShareAlike
loaded in the file cont-new which itself is loaded at run time. That
+
</div>
way, users can still benefit from official updates.
+
This one says:
  
'''[4.11]'''  The auxiliary programs may be adapted to local conditions, such
+
<div style="color:gray;">
as operating systems specifics. The functionality however must not be
+
You are free:
changed.
+
* to copy, distribute, display, and perform the work
 +
* to make derivative works
  
'''[4.12]'''  The same rules apply for the METAPOST macro files as for the
+
ATTRIBUTION: You must attribute the work in the manner specified by the author or licensor.  
TeX macro files.  
 
  
'''[4.13]'''  Support of the official public version of ConTeXt is available
+
NONCOMMERCIAL: You may not use this work for commercial purposes.  
from the ConTeXt mailing list hosted by the ntg.
 
  
=== Manuals ===
+
SHARE ALIKE: If you alter, transform, or build upon this work, you may distribute the resulting work only under a license identical to this one.
  
'''[5.1]'''  User manuals, reference documentation, module related manuals,
+
* For any reuse or distribution, you must make clear to others the license terms of this work.  
quick reference guides, up-to-date documents, faqs, documented
+
* Any of these conditions can be waived if you get permission from the copyright holder.  
sources, are available in printable and/or electronic form at the
 
Pragma ADE site and its mirrors. These documents are copyrighted by
 
Pragma ADE and serve as reference to the official version. You may
 
print them and give away copies.  
 
  
'''[5.2]'''  Users are invited to provide
+
Your fair use and other rights are in no way affected by the above.  
additional documentation to users. The official documentation provided
+
</div>
by Pragma ADE is maintained by and generated at Pragma ADE and
 
available at its website. Pointers to third party contributions can be
 
found at the Pragma ADE website.
 
  
'''[5.3]''' Because the manuals provided by Pragma ADE are also examples of
+
The non-commercial part is mostly a safeguard. We don't mind if user
what can be done with ConTeXt, their layout is bound to these
+
groups distribute printed copies, publish (parts of) manuals and/or if
documents. This also applies to the ConTeXt demonstration
+
authors use example code in manuals and books about ConTeXt.
suite. Therefore, in order to avoid confusion, we strongly advice
 
authors of third party documentation and demos not to use the same
 
layout characteristics, graphics and special tricks. Examples of
 
coding and tricks can be found in the style files that come with
 
ConTeXt.
 
  
=== Guarantees ===
+
Keep in mind that logos and cover designs are not meant to be copied.
 +
We provide the source code for some manuals, but we don't always
 +
provide all graphics and other resources. For instance, in some
 +
manuals we use commercial fonts and you have to buy those yourself.
  
'''[6.1]'''  Pragma ADE cannot guarantee the typographic quality and the
+
We provide the typeset manuals at our website. Those are the official
functionality of the ConTeXt output.  
+
ones. We appreciate it if you do not to distribute manuals compiled on
 +
your own system as substitutes. The manuals are a showcase for what
 +
ConTeXt provides. Help us to assure the quality.
  
'''[6.2]'''  Typographic optimizations will be implemented and wishes
+
=== More information ===
cq. suggestions of users will be be honoured when possible. The best
 
way to communicate this is the ConTeXt mailing list.
 
  
'''[6.3]'''  When additional functionality is provided, downward
+
We're not going to fill ''n'' pages with legal stuff, so if you
compatibility will be guarded as good as possible.  
+
want to know more, you have to consult the web for the legalities
 +
mentioned. Here are a few starting points:
  
'''[6.4]'''  Users of experimental modules should be aware of the fact that
+
http://creativecommons.org/licenses/GPL/2.0/ <br>
due to further optimization and consistency, the functionality will
+
http://creativecommons.org/licenses/GPL/2.0/legalcode
only be stable when explicitly stated. The common user will hardly
 
notice this limitation.  
 
  
'''[6.5]'''  Some core modules can be classified as generic, that is, they
+
http://creativecommons.org/licenses/by-nc-sa/2.5/ <br>
work with other macro packages as well (for instance supp-pdf). You may
+
http://creativecommons.org/licenses/by-nc-sa/2.5/legalcode
install them separately on your system, but in order to prevent
 
conflicts in versions, we strongly advice separating them from the
 
distributions.  
 
  
'''[6.6]'''  Undocumented macros and functionality are subjected to
+
ConTeXt itself can be fetched from the main site or its primary mirror:
optimizations and relying on their presence can be "dangerous".
 
  
=== Distribution ===
+
http://www.pragma-ade.com <br>
 +
http://context.aanhet.net
  
'''[7.1]'''  The official ConTeXt archive is available at the Pragma ADE www
+
A starting point for support can be found at:
site, as well as on mirrors of this site, provided by the ntg, ctan,
 
and others. The free TeX distributions teTeX and fpTeX can be
 
considered as a references to integrating ConTeXt into other TeX
 
systems.
 
  
'''[7.2]'''  We hereby grant permission to the de facto official TeX
+
http://www.ntg.nl/mailman/listinfo/ntg-context <br>
distributors teTeX, fpTeX and TeXlive to replace this licence with
+
http://contextgarden.net
their own, i.e. their licence may supersede or enhance this one.
 
  
 +
Bugs and feature requests can be registered at the collector:
  
'''[7.3]'''  ConTeXt may be distributed as part of a public distribution in
+
http://context.literatesolutions.com
the spirit of free distributions. The authors of ConTeXt appreciate
 
being notified on this.  
 
  
'''[7.4]'''  Each distribution of ConTeXt should include a copy of this text.
+
Releases are announced at:
  
=== Additional disclaimers ===
+
http://www.ntg.nl/mailman/listinfo/ann-context
  
Because we don't want to be confronted with funny claims as a side
+
The developers can be met at:
effect of providing free software, we add a few disclaimers.
 
  
'''[8.1]'''  By modifying or distributing the program (or any work based on
+
http://www.ntg.nl/mailman/listinfo/dev-context
the program), you indicate your acceptance of this license to do so,
 
and all its terms and conditions for copying, distributing or
 
modifying the program or works based on it. Nothing other than this
 
license grants you permission to modify or distribute the program or
 
its derivative works. These actions are prohibited by law. If you do
 
not accept these terms and conditions, do not modify or distribute the
 
program.  
 
  
'''[8.2]'''  The program is provided to you "as is", without warranty. There
+
=== Disclaimer ===
is no warranty for the program, either expressed or implied,
+
To play safe we include a disclaimer here, taken from the
including, but not limited to, the implied warranties of
+
BSD style licence. For some reason such a text is in capitals, so ...
merchantability and fitness for a particular purpose and
 
noninfringement of third party rights. The entire risk as to the
 
quality and performance of the program is with you. should the program
 
prove defective, you assume the cost of all necessary servicing,
 
repair or correction.  
 
  
'''[8.3]'''  In no event unless required by applicable law or agreed to in
+
<div style="color:gray;">
writing will licensor, or any other party who may modify and/or
+
THIS SOFTWARE IS PROVIDED BY THE AUTHOR “AS IS” AND ANY EXPRESS OR
redistribute the program as permitted above, be liable to you for
+
IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
damages, including any general, special, incidental or consequential
+
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
damages arising out of the use or inability to use the program
+
DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT,
(including but not limited to loss of data or data being rendered
+
INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
inaccurate or losses sustained by you or third parties or a failure of
+
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
the program to operate with any other programs), even if such holder
+
SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
or other party has been advised of the possibility of such damages.
+
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
 +
STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
 +
IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
 +
POSSIBILITY OF SUCH DAMAGE.
 +
</div>
 +
... and don't bother discussing licence issues and related things with
 +
us for the mere sake of discussing licence stuff.
  
  

Revision as of 19:34, 7 December 2005

What follows is the text from [mreadme.pdf], adapted to wiki markup.

This page is generated from mreadme.pdf on 2005.11.24.


Read Me

Introduction

What licence suits best for a TeX like system is a matter of taste. Personally we dislike any licence that needs more than a few pages of dense legal code to get the message accross. A TeX related system like ConTeXt is a hybrid of programs, scripts and/ or macro code as well as documentation and sample code, including graphics. TeX related systems also have a long standing tradition of providing support structures for users. In order to make support feasable, a TeX based system like ConTeXt assumes a certain logic and structure in the way the related files are named and organized in a tree structure. Even a small change in one of the elements may let such a system behave differently than manuals suggest. Swap a font, change some style defaults, leave out some pieces, and users may end up in confusion. A licence does not give a user any guarantees!


In order to satisfy those responsible for distributing ConTeXt, we need to choose a licence that makes them feel comfortable. Unfortunately we don't feel that comfortable with a licence that does not provide the guarantees that a system will not be adapted in such ways that the advertised behaviour changes. On the other hand, it is the responsibility of those distributing and extending the system to make sure that this does not happen. However, users should not automatically assume that what they get shipped is the same as the original, which is why we stress that support (from our side) will only be given on unaltered systems.

First of all, what is ConTeXt? It's just a bunch of macros, written in TeX and METAPOST, meant for typesetting documents. The macros are accompanied by some scripts, written in Perl (mainly the older scripts) Ruby (the official ones) and Lua (for embedded usage). The ConTeXt distribution comes with a few fonts, files that help manage resources (e.g. map files), as well as patterns (based on official ones, so this is a derived work).

The ConTeXt distribution is packaged in a zip file organized in the tds structure.

cont-tmf.zip The main distribution. cont-img.zip A few extra resources. cont-ext.zip Third party modules.

When we talk about ConTeXt we also mean its graphical companion MetaFun and foXet, an xml related product. All these are included in the main distribution archive. The documentation can be downloaded from our website, one of its mirrors, the TeX collection as distributed by TeX user groups. For some manuals, source code is available in a subversion repository. The archives are also kept on ctan.

That said, what licence does apply? We need to distinguish between things that resemble a program on the one hand and documentation on the other hand. We (currently) use a different licence for either of them.


The Code

The program code (i.e. anything not under the /doc subtree) is distributed under the

Creative Commons GNU GPL

For practical purposes distributers may also choose the LaTeX project licence, which is considered to be a bit more TeX friendly. (BSD alike licences, the Ruby Licence and the Apache are all licences that apply well for ConTeXt.)

In practice, users may forget about the legal part, if only because I haven't even read (and understood) it completely myself, so let's stick to what Creative Commons makes of it:

The GNU General Public License is a Free Software license. Like any Free Software license, it grants to you the four following freedoms:

  • The freedom to run the program for any purpose.
  • The freedom to study how the program works and adapt it to your needs.
  • The freedom to redistribute copies so you can help your neighbour.
  • The freedom to improve the program and release your improvements to the public, so that the whole community benefits.


You may exercise the freedoms specified here provided that you comply with the express conditions of this license. The principal conditions are:

You must conspicuously and appropriately publish on each copy distributed an appropriate copyright notice and disclaimer of warranty and keep intact all the notices that refer to this License and to the absence of any warranty; and give any other recipients of the Program a copy of the GNU General Public License along with the Program. Any translation of the GNU General Public License must be accompanied by the GNU General Public License.

If you modify your copy or copies of the program or any portion of it, or develop a program based upon it, you may distribute the resulting work provided you do so under the GNU General Public License. Any translation of the GNU General Public License must be accompanied by the GNU General Public License.

If you copy or distribute the program, you must accompany it with the complete corresponding machine-readable source code or with a written offer, valid for at least three years, to furnish the complete corresponding machine-readable source code.

Any of these conditions can be waived if you get permission from the copyright holder.

Your fair use and other rights are in no way affected by the above.

Recommendations

Here are a few recommendations in case you want to distribute, extend of embed ConTeXt in applications:

  • You can best leave the code base untouched. Most of ConTeXt provides hooks and it's relatively easy to overload code. Leave the lower level system code untouched: changes may backfire when you update. Asking for more hooks is the best way to go.
  • Put your own code in the right subpaths, i.e. modules approved by the development team under .../third, and styles and whatever else under .../user. This way your code will not interfere with existing code and updating will give less problems. Keep in mind that TeX systems have their own way and order in locating files, and the load order often matters.
  • Don't copy styles and change a few lines, but load the base one and built/patch on top of that. In the end you may benefit from improvements to the base style.
  • Be original. The whole idea behind ConTeXt is that you can write your own styles. On the ConTeXt mailing list as well as on the Wiki there are enough advanced users to help you make a start.
  • Don't hesitate to submit bugs reports and ask for extensions. It may even be that what you want is already present but yet undocumented.
  • If things don't work as expected, check to what extend your system matches the (more or less) standard. We provide so called minimal ConTeXt trees that can serve as a reference. Because ConTeXt evolves, make sure your system is up to date.
  • The scripts can best be called using texmfstart. This lessens dependencies on the location in the tree and ensures upward compatibility. It also prevents clashes with similary named scripts.
  • Some scripts depend on each other. Don't mess around with the existing functionality and names of the scripts and then feed them back into the standard distributions.

Documents

The documentation is provided under another Creative Commons licence

Attribution NonCommercial ShareAlike

This one says:

You are free:

  • to copy, distribute, display, and perform the work
  • to make derivative works

ATTRIBUTION: You must attribute the work in the manner specified by the author or licensor.

NONCOMMERCIAL: You may not use this work for commercial purposes.

SHARE ALIKE: If you alter, transform, or build upon this work, you may distribute the resulting work only under a license identical to this one.

  • For any reuse or distribution, you must make clear to others the license terms of this work.
  • Any of these conditions can be waived if you get permission from the copyright holder.

Your fair use and other rights are in no way affected by the above.

The non-commercial part is mostly a safeguard. We don't mind if user groups distribute printed copies, publish (parts of) manuals and/or if authors use example code in manuals and books about ConTeXt.

Keep in mind that logos and cover designs are not meant to be copied. We provide the source code for some manuals, but we don't always provide all graphics and other resources. For instance, in some manuals we use commercial fonts and you have to buy those yourself.

We provide the typeset manuals at our website. Those are the official ones. We appreciate it if you do not to distribute manuals compiled on your own system as substitutes. The manuals are a showcase for what ConTeXt provides. Help us to assure the quality.

More information

We're not going to fill n pages with legal stuff, so if you want to know more, you have to consult the web for the legalities mentioned. Here are a few starting points:

http://creativecommons.org/licenses/GPL/2.0/
http://creativecommons.org/licenses/GPL/2.0/legalcode

http://creativecommons.org/licenses/by-nc-sa/2.5/
http://creativecommons.org/licenses/by-nc-sa/2.5/legalcode

ConTeXt itself can be fetched from the main site or its primary mirror:

http://www.pragma-ade.com
http://context.aanhet.net

A starting point for support can be found at:

http://www.ntg.nl/mailman/listinfo/ntg-context
http://contextgarden.net

Bugs and feature requests can be registered at the collector:

http://context.literatesolutions.com

Releases are announced at:

http://www.ntg.nl/mailman/listinfo/ann-context

The developers can be met at:

http://www.ntg.nl/mailman/listinfo/dev-context

Disclaimer

To play safe we include a disclaimer here, taken from the BSD style licence. For some reason such a text is in capitals, so ...

THIS SOFTWARE IS PROVIDED BY THE AUTHOR “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

... and don't bother discussing licence issues and related things with us for the mere sake of discussing licence stuff.


PRAGMA
Advanced Document Engineering
Ridderstraat 27
8061GH Hasselt NL
tel: +31 (0)38 477 53 69
email: pragma@wxs.nl
internet: www.pragma-ade.com