[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
www/licenses/old-licenses gcc-exception-transla...
|
From: |
Yavor Doganov |
|
Subject: |
www/licenses/old-licenses gcc-exception-transla... |
|
Date: |
Sat, 29 Oct 2011 16:36:05 +0000 |
CVSROOT: /web/www
Module name: www
Changes by: Yavor Doganov <yavor> 11/10/29 16:36:05
Modified files:
licenses/old-licenses: gcc-exception-translations.de.html
licenses/old-licenses/po: gcc-exception-translations.translist
gpl-1.0.translist gpl-2.0-faq.de.po
gpl-2.0-faq.translist
gpl-2.0-translations.translist
gpl-2.0.de.po gpl-2.0.translist
lgpl-2.0.de.po lgpl-2.0.translist
lgpl-2.1-translations.translist
lgpl-2.1.de.po lgpl-2.1.translist
old-licenses.translist
Added files:
licenses/old-licenses: gpl-1.0.de.html gpl-2.0-faq.de.html
gpl-2.0-translations.de.html
gpl-2.0.de.html lgpl-2.0.de.html
lgpl-2.1-translations.de.html
lgpl-2.1.de.html old-licenses.de.html
Log message:
Automatic update by GNUnited Nations.
CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/old-licenses/gcc-exception-translations.de.html?cvsroot=www&r1=1.3&r2=1.4
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/old-licenses/gpl-1.0.de.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/old-licenses/gpl-2.0-faq.de.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/old-licenses/gpl-2.0-translations.de.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/old-licenses/gpl-2.0.de.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/old-licenses/lgpl-2.0.de.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/old-licenses/lgpl-2.1-translations.de.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/old-licenses/lgpl-2.1.de.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/old-licenses/old-licenses.de.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/old-licenses/po/gcc-exception-translations.translist?cvsroot=www&r1=1.1&r2=1.2
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/old-licenses/po/gpl-1.0.translist?cvsroot=www&r1=1.1&r2=1.2
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/old-licenses/po/gpl-2.0-faq.de.po?cvsroot=www&r1=1.1&r2=1.2
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/old-licenses/po/gpl-2.0-faq.translist?cvsroot=www&r1=1.1&r2=1.2
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/old-licenses/po/gpl-2.0-translations.translist?cvsroot=www&r1=1.1&r2=1.2
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/old-licenses/po/gpl-2.0.de.po?cvsroot=www&r1=1.1&r2=1.2
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/old-licenses/po/gpl-2.0.translist?cvsroot=www&r1=1.1&r2=1.2
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/old-licenses/po/lgpl-2.0.de.po?cvsroot=www&r1=1.1&r2=1.2
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/old-licenses/po/lgpl-2.0.translist?cvsroot=www&r1=1.1&r2=1.2
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/old-licenses/po/lgpl-2.1-translations.translist?cvsroot=www&r1=1.1&r2=1.2
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/old-licenses/po/lgpl-2.1.de.po?cvsroot=www&r1=1.1&r2=1.2
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/old-licenses/po/lgpl-2.1.translist?cvsroot=www&r1=1.1&r2=1.2
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/old-licenses/po/old-licenses.translist?cvsroot=www&r1=1.1&r2=1.2
Patches:
Index: gcc-exception-translations.de.html
===================================================================
RCS file:
/web/www/www/licenses/old-licenses/gcc-exception-translations.de.html,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -b -r1.3 -r1.4
--- gcc-exception-translations.de.html 29 Oct 2011 08:27:53 -0000 1.3
+++ gcc-exception-translations.de.html 29 Oct 2011 16:35:40 -0000 1.4
@@ -14,16 +14,16 @@
<h3 id="UnofficialTranslations">Informationen über inoffizielle
Ãbersetzungen</h3>
<p>
-Der Grund, warum die FSF diese Ãbersetzungen als nicht offiziell gÃltig
-genehmigt, ist, dass deren ÃberprÃfung schwierig und teuer wäre (es wird die
+Der Grund, warum die FSF diese Ãbersetzungen als nicht offiziell gültig
+genehmigt, ist, dass deren Ãberprüfung schwierig und teuer wäre (es wird die
Hilfe zweisprachiger Juristen in anderen Ländern benötigt). Schlimmer noch,
wenn ein Fehler durchrutscht, könnten die Ergebnisse für die gesamte
Freie-Software-Gemeinschaft katastrophal sein. Solange die Ãbersetzungen
inoffiziell sind, können sie keinen Schaden anrichten.</p>
<p>Der Verweis auf Ãbersetzungen soll mehr Menschen helfen, die GNU FDL zu
-verstehen. Damit sie das tun, mÃssen Ãbersetzungen grundsätzlich genau sein,
-wenn auch nicht perfekt. FÃr eine gute Ãbersetzung ist es unerlässlich,
+verstehen. Damit sie das tun, müssen Ãbersetzungen grundsätzlich genau sein,
+wenn auch nicht perfekt. Für eine gute Ãbersetzung ist es unerlässlich,
grundlegende Konzepte wie <a href="/copyleft/copyleft">Copyleft</a> und die
<a href="/philosophy/free-sw">Definition von Freie Software</a> vollständig
verstanden zu haben. Aus diesem Grund sollten diejenigen, die Ãbersetzungen
@@ -69,11 +69,11 @@
dass es wahrscheinlich hauptsächlich richtig ist.</p>
<p>
-Um Ihre Ãbersetzungen als inoffiziell zu kennzeichnen, fÃgen Sie bitte
+Um Ihre Ãbersetzungen als inoffiziell zu kennzeichnen, fügen Sie bitte
folgenden Text am Anfang, sowohl in Englisch als auch in der Sprache der
Ãbersetzung, hinzu. Ersetzen Sie <em>language</em> durch den Namen dieser
Sprache und „GNU General Public License“ und „GPL“
-mit dem Namen und der AbkÃrzung der Lizenz, die Sie Ãbersetzen, wenn es sich
+mit dem Namen und der Abkürzung der Lizenz, die Sie Ãbersetzen, wenn es sich
<em>nicht</em> um die GPL handelt:</p>
<blockquote dir="ltr"><p>
@@ -85,34 +85,33 @@
not translated, so if your language is RTL, you *must* put your
translation within <span dir="rtl">.-->
<span xml:lang="en" lang="en">This is an unofficial translation of the GNU
-General Public License into <tt>language</tt>. It was not published by the
+General Public License into <em>language</em>. It was not published by the
Free Software Foundation, and does not legally state the distribution terms
for software that uses the GNU GPL—only the original English text of
the GNU GPL does that. However, we hope that this translation will help
-<tt>language</tt> speakers understand the GNU GPL better.</span><br /><br />
+<em>language</em> speakers understand the GNU GPL better.</span><br /><br />
<span class="translation">Dies ist eine inoffizielle Ãbersetzung der GNU
-General Public License in <tt>Deutsch</tt>. Sie wurde nicht von der Free
+General Public License in <em>Deutsch</em>. Sie wurde nicht von der Free
Software Foundation freigegeben und ist keine rechtsverbindliche
Vertriebsbedingung für Software, die GNU GPL lizenziert
ist ‑ dies kann nur der englische Originaltext der
GNU GPL. Dennoch hoffen wir, dass diese Ãbersetzung
-<tt>deutschsprachigen</tt> Personen helfen wird, die GNU GPL besser zu
+<em>deutschsprachigen</em> Personen helfen wird, die GNU GPL besser zu
verstehen.</span>
</p></blockquote>
<p>
-Möchten Sie eine Lizenz Ãbersetzen, informieren Sie bitte die <em>GNU
+MoÌchten Sie eine Lizenz übersetzen, informieren Sie bitte die <em>GNU
Translation Manager</em> <a
href="mailto:address@hidden";><address@hidden></a>.
-Sie ÃberprÃfen, ob die Ãbersetzung den oben genannten Richtlinien folgt und
+Sie überprüfen, ob die UÌbersetzung den oben genannten Richtlinien folgt und
legen einen Verweis darauf an.</p>
<p>Dies sind Ãbersetzungen von alten Versionen der GCC Runtime Library
Exception, die <em>nicht</em> der neuesten Version
entsprechen. Ãbersetzungen aktueller Lizenzen finden Sie unter <a
-href="/licenses/translations">
-http://www.gnu.org/licenses/translations.html</a>.</p>
+href="/licenses/translations">http://www.gnu.org/licenses/translations.html</a>.</p>
<h3 id="gcc-rle-3.0">GNU Runtime Library Exception (RLE), Version 3.0</h3>
@@ -175,7 +174,7 @@
<!-- timestamp start -->
Aktualisierung:
-$Date: 2011/10/29 08:27:53 $
+$Date: 2011/10/29 16:35:40 $
<!-- timestamp end -->
</p>
Index: po/gcc-exception-translations.translist
===================================================================
RCS file:
/web/www/www/licenses/old-licenses/po/gcc-exception-translations.translist,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- po/gcc-exception-translations.translist 19 Sep 2011 00:29:49 -0000
1.1
+++ po/gcc-exception-translations.translist 29 Oct 2011 16:35:50 -0000
1.2
@@ -1,6 +1,8 @@
<!-- begin translinks file -->
<div id="translations">
<ul class="translations-list">
+<!-- German -->
+<li><a
href="/licenses/old-licenses/gcc-exception-translations.de.html">Deutsch</a> [de]</li>
<!-- English -->
<li><a
href="/licenses/old-licenses/gcc-exception-translations.html">English</a> [en]</li>
</ul>
Index: po/gpl-1.0.translist
===================================================================
RCS file: /web/www/www/licenses/old-licenses/po/gpl-1.0.translist,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- po/gpl-1.0.translist 20 Sep 2011 07:35:28 -0000 1.1
+++ po/gpl-1.0.translist 29 Oct 2011 16:35:51 -0000 1.2
@@ -1,6 +1,8 @@
<!-- begin translinks file -->
<div id="translations">
<ul class="translations-list">
+<!-- German -->
+<li><a href="/licenses/old-licenses/gpl-1.0.de.html">Deutsch</a> [de]</li>
<!-- English -->
<li><a href="/licenses/old-licenses/gpl-1.0.html">English</a> [en]</li>
</ul>
Index: po/gpl-2.0-faq.de.po
===================================================================
RCS file: /web/www/www/licenses/old-licenses/po/gpl-2.0-faq.de.po,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- po/gpl-2.0-faq.de.po 28 Oct 2011 15:20:50 -0000 1.1
+++ po/gpl-2.0-faq.de.po 29 Oct 2011 16:35:51 -0000 1.2
@@ -13,6 +13,7 @@
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
+"Outdated-Since: 2011-09-20 12:28-0300\n"
#. type: Content of: <title>
msgid ""
Index: po/gpl-2.0-faq.translist
===================================================================
RCS file: /web/www/www/licenses/old-licenses/po/gpl-2.0-faq.translist,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- po/gpl-2.0-faq.translist 20 Sep 2011 07:35:31 -0000 1.1
+++ po/gpl-2.0-faq.translist 29 Oct 2011 16:35:51 -0000 1.2
@@ -3,6 +3,8 @@
<ul class="translations-list">
<!-- Czech -->
<li><a
href="/licenses/old-licenses/gpl-2.0-faq.cs.html">Česky</a> [cs]</li>
+<!-- German -->
+<li><a
href="/licenses/old-licenses/gpl-2.0-faq.de.html">Deutsch</a> [de]</li>
<!-- English -->
<li><a
href="/licenses/old-licenses/gpl-2.0-faq.html">English</a> [en]</li>
<!-- Spanish -->
Index: po/gpl-2.0-translations.translist
===================================================================
RCS file: /web/www/www/licenses/old-licenses/po/gpl-2.0-translations.translist,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- po/gpl-2.0-translations.translist 20 Sep 2011 07:35:28 -0000 1.1
+++ po/gpl-2.0-translations.translist 29 Oct 2011 16:35:51 -0000 1.2
@@ -3,6 +3,8 @@
<ul class="translations-list">
<!-- Catalan -->
<li><a
href="/licenses/old-licenses/gpl-2.0-translations.ca.html">català</a> [ca]</li>
+<!-- German -->
+<li><a
href="/licenses/old-licenses/gpl-2.0-translations.de.html">Deutsch</a> [de]</li>
<!-- English -->
<li><a
href="/licenses/old-licenses/gpl-2.0-translations.html">English</a> [en]</li>
<!-- French -->
Index: po/gpl-2.0.de.po
===================================================================
RCS file: /web/www/www/licenses/old-licenses/po/gpl-2.0.de.po,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- po/gpl-2.0.de.po 28 Oct 2011 15:20:50 -0000 1.1
+++ po/gpl-2.0.de.po 29 Oct 2011 16:35:51 -0000 1.2
@@ -13,6 +13,7 @@
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
+"Outdated-Since: 2011-09-20 12:28-0300\n"
#. type: Content of: <title>
msgid ""
Index: po/gpl-2.0.translist
===================================================================
RCS file: /web/www/www/licenses/old-licenses/po/gpl-2.0.translist,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- po/gpl-2.0.translist 20 Sep 2011 07:35:29 -0000 1.1
+++ po/gpl-2.0.translist 29 Oct 2011 16:35:51 -0000 1.2
@@ -3,6 +3,8 @@
<ul class="translations-list">
<!-- Czech -->
<li><a
href="/licenses/old-licenses/gpl-2.0.cs.html">Česky</a> [cs]</li>
+<!-- German -->
+<li><a href="/licenses/old-licenses/gpl-2.0.de.html">Deutsch</a> [de]</li>
<!-- English -->
<li><a href="/licenses/old-licenses/gpl-2.0.html">English</a> [en]</li>
<!-- Japanese -->
Index: po/lgpl-2.0.de.po
===================================================================
RCS file: /web/www/www/licenses/old-licenses/po/lgpl-2.0.de.po,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- po/lgpl-2.0.de.po 28 Oct 2011 15:20:49 -0000 1.1
+++ po/lgpl-2.0.de.po 29 Oct 2011 16:35:51 -0000 1.2
@@ -13,6 +13,7 @@
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
+"Outdated-Since: 2011-09-20 12:28-0300\n"
#. type: Content of: <title>
msgid ""
Index: po/lgpl-2.0.translist
===================================================================
RCS file: /web/www/www/licenses/old-licenses/po/lgpl-2.0.translist,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- po/lgpl-2.0.translist 20 Sep 2011 07:35:31 -0000 1.1
+++ po/lgpl-2.0.translist 29 Oct 2011 16:35:51 -0000 1.2
@@ -1,6 +1,8 @@
<!-- begin translinks file -->
<div id="translations">
<ul class="translations-list">
+<!-- German -->
+<li><a
href="/licenses/old-licenses/lgpl-2.0.de.html">Deutsch</a> [de]</li>
<!-- English -->
<li><a href="/licenses/old-licenses/lgpl-2.0.html">English</a> [en]</li>
<!-- Japanese -->
Index: po/lgpl-2.1-translations.translist
===================================================================
RCS file:
/web/www/www/licenses/old-licenses/po/lgpl-2.1-translations.translist,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- po/lgpl-2.1-translations.translist 20 Sep 2011 07:35:30 -0000 1.1
+++ po/lgpl-2.1-translations.translist 29 Oct 2011 16:35:51 -0000 1.2
@@ -3,6 +3,8 @@
<ul class="translations-list">
<!-- Catalan -->
<li><a
href="/licenses/old-licenses/lgpl-2.1-translations.ca.html">català</a> [ca]</li>
+<!-- German -->
+<li><a
href="/licenses/old-licenses/lgpl-2.1-translations.de.html">Deutsch</a> [de]</li>
<!-- English -->
<li><a
href="/licenses/old-licenses/lgpl-2.1-translations.html">English</a> [en]</li>
<!-- French -->
Index: po/lgpl-2.1.de.po
===================================================================
RCS file: /web/www/www/licenses/old-licenses/po/lgpl-2.1.de.po,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- po/lgpl-2.1.de.po 28 Oct 2011 15:20:49 -0000 1.1
+++ po/lgpl-2.1.de.po 29 Oct 2011 16:35:51 -0000 1.2
@@ -13,6 +13,7 @@
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
+"Outdated-Since: 2011-09-20 12:28-0300\n"
#. type: Content of: <title>
msgid ""
Index: po/lgpl-2.1.translist
===================================================================
RCS file: /web/www/www/licenses/old-licenses/po/lgpl-2.1.translist,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- po/lgpl-2.1.translist 20 Sep 2011 07:35:30 -0000 1.1
+++ po/lgpl-2.1.translist 29 Oct 2011 16:35:51 -0000 1.2
@@ -1,6 +1,8 @@
<!-- begin translinks file -->
<div id="translations">
<ul class="translations-list">
+<!-- German -->
+<li><a
href="/licenses/old-licenses/lgpl-2.1.de.html">Deutsch</a> [de]</li>
<!-- English -->
<li><a href="/licenses/old-licenses/lgpl-2.1.html">English</a> [en]</li>
<!-- Japanese -->
Index: po/old-licenses.translist
===================================================================
RCS file: /web/www/www/licenses/old-licenses/po/old-licenses.translist,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- po/old-licenses.translist 20 Sep 2011 07:35:31 -0000 1.1
+++ po/old-licenses.translist 29 Oct 2011 16:35:52 -0000 1.2
@@ -5,6 +5,8 @@
<li><a
href="/licenses/old-licenses/old-licenses.ar.html">العربية</a> [ar]</li>
<!-- Catalan -->
<li><a
href="/licenses/old-licenses/old-licenses.ca.html">català</a> [ca]</li>
+<!-- German -->
+<li><a
href="/licenses/old-licenses/old-licenses.de.html">Deutsch</a> [de]</li>
<!-- English -->
<li><a
href="/licenses/old-licenses/old-licenses.html">English</a> [en]</li>
<!-- French -->
Index: gpl-1.0.de.html
===================================================================
RCS file: gpl-1.0.de.html
diff -N gpl-1.0.de.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ gpl-1.0.de.html 29 Oct 2011 16:35:40 -0000 1.1
@@ -0,0 +1,371 @@
+
+<!--#include virtual="/server/header.de.html" -->
+
+<!-- This file is automatically generated by GNUnited Nations! -->
+<title>GNU General Public License (GPL) v1.0 - GNU Projekt - Free Software
+Foundation (FSF)</title>
+
+<!--#include virtual="/server/banner.de.html" -->
+<!--#include virtual="/licenses/old-licenses/po/gpl-1.0.translist" -->
+<h2>GNU General Public License, Version 1</h2>
+
+<ul>
+ <li><a href="/licenses/gpl-violation">GNU GPL: Was ist bei einer möglichen
+Verletzung zu tun</a></li>
+ <li>Die GNU GPLv1 ist in anderen Formaten abrufbar (engl.): <a
+href="gpl-1.0.txt">Nur Text</a>, <a href="gpl-1.0-standalone.html">Nur
+HTML</a>
+ </li>
+ <li><a href="/licenses/old-licenses/old-licenses.de.html#GPL">Alte Versionen
der
+GNU GPL</a></li>
+</ul>
+
+<pre><!--TRANSLATORS: Don't translate the license; copy msgid's
+verbatim!-->
+
+ GNU GENERAL PUBLIC LICENSE
+ Version 1, February 1989
+
+ Copyright (C) 1989 Free Software Foundation, Inc.
+ 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+ Preamble
+
+ The license agreements of most software companies try to keep users
+at the mercy of those companies. By contrast, our General Public
+License is intended to guarantee your freedom to share and change free
+software--to make sure the software is free for all its users. The
+General Public License applies to the Free Software Foundation's
+software and to any other program whose authors commit to using it.
+You can use it for your programs, too.
+
+ When we speak of free software, we are referring to freedom, not
+price. Specifically, the General Public License is designed to make
+sure that you have the freedom to give away or sell copies of free
+software, that you receive source code or can get it if you want it,
+that you can change the software or use pieces of it in new free
+programs; and that you know you can do these things.
+
+ To protect your rights, we need to make restrictions that forbid
+anyone to deny you these rights or to ask you to surrender the rights.
+These restrictions translate to certain responsibilities for you if you
+distribute copies of the software, or if you modify it.
+
+ For example, if you distribute copies of a such a program, whether
+gratis or for a fee, you must give the recipients all the rights that
+you have. You must make sure that they, too, receive or can get the
+source code. And you must tell them their rights.
+
+ We protect your rights with two steps: (1) copyright the software, and
+(2) offer you this license which gives you legal permission to copy,
+distribute and/or modify the software.
+
+ Also, for each author's protection and ours, we want to make certain
+that everyone understands that there is no warranty for this free
+software. If the software is modified by someone else and passed on, we
+want its recipients to know that what they have is not the original, so
+that any problems introduced by others will not reflect on the original
+authors‘ reputations.
+
+ The precise terms and conditions for copying, distribution and
+modification follow.
+
+ GNU GENERAL PUBLIC LICENSE
+ TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+ 0. This License Agreement applies to any program or other work which
+contains a notice placed by the copyright holder saying it may be
+distributed under the terms of this General Public License. The
+"Program", below, refers to any such program or work, and a "work based
+on the Program" means either the Program or any work containing the
+Program or a portion of it, either verbatim or with modifications. Each
+licensee is addressed as "you".
+
+ 1. You may copy and distribute verbatim copies of the Program's source
+code as you receive it, in any medium, provided that you conspicuously and
+appropriately publish on each copy an appropriate copyright notice and
+disclaimer of warranty; keep intact all the notices that refer to this
+General Public License and to the absence of any warranty; and give any
+other recipients of the Program a copy of this General Public License
+along with the Program. You may charge a fee for the physical act of
+transferring a copy.
+
+ 2. You may modify your copy or copies of the Program or any portion of
+it, and copy and distribute such modifications under the terms of Paragraph
+1 above, provided that you also do the following:
+
+ a) cause the modified files to carry prominent notices stating that
+ you changed the files and the date of any change; and
+
+ b) cause the whole of any work that you distribute or publish, that
+ in whole or in part contains the Program or any part thereof, either
+ with or without modifications, to be licensed at no charge to all
+ third parties under the terms of this General Public License (except
+ that you may choose to grant warranty protection to some or all
+ third parties, at your option).
+
+ c) If the modified program normally reads commands interactively when
+ run, you must cause it, when started running for such interactive use
+ in the simplest and most usual way, to print or display an
+ announcement including an appropriate copyright notice and a notice
+ that there is no warranty (or else, saying that you provide a
+ warranty) and that users may redistribute the program under these
+ conditions, and telling the user how to view a copy of this General
+ Public License.
+
+ d) You may charge a fee for the physical act of transferring a
+ copy, and you may at your option offer warranty protection in
+ exchange for a fee.
+
+Mere aggregation of another independent work with the Program (or its
+derivative) on a volume of a storage or distribution medium does not bring
+the other work under the scope of these terms.
+
+ 3. You may copy and distribute the Program (or a portion or derivative of
+it, under Paragraph 2) in object code or executable form under the terms of
+Paragraphs 1 and 2 above provided that you also do one of the following:
+
+ a) accompany it with the complete corresponding machine-readable
+ source code, which must be distributed under the terms of
+ Paragraphs 1 and 2 above; or,
+
+ b) accompany it with a written offer, valid for at least three
+ years, to give any third party free (except for a nominal charge
+ for the cost of distribution) a complete machine-readable copy of the
+ corresponding source code, to be distributed under the terms of
+ Paragraphs 1 and 2 above; or,
+
+ c) accompany it with the information you received as to where the
+ corresponding source code may be obtained. (This alternative is
+ allowed only for noncommercial distribution and only if you
+ received the program in object code or executable form alone.)
+
+Source code for a work means the preferred form of the work for making
+modifications to it. For an executable file, complete source code means
+all the source code for all modules it contains; but, as a special
+exception, it need not include source code for modules which are standard
+libraries that accompany the operating system on which the executable
+file runs, or for standard header files or definitions files that
+accompany that operating system.
+
+ 4. You may not copy, modify, sublicense, distribute or transfer the
+Program except as expressly provided under this General Public License.
+Any attempt otherwise to copy, modify, sublicense, distribute or transfer
+the Program is void, and will automatically terminate your rights to use
+the Program under this License. However, parties who have received
+copies, or rights to use copies, from you under this General Public
+License will not have their licenses terminated so long as such parties
+remain in full compliance.
+
+ 5. By copying, distributing or modifying the Program (or any work based
+on the Program) you indicate your acceptance of this license to do so,
+and all its terms and conditions.
+
+ 6. Each time you redistribute the Program (or any work based on the
+Program), the recipient automatically receives a license from the original
+licensor to copy, distribute or modify the Program subject to these
+terms and conditions. You may not impose any further restrictions on the
+recipients‘ exercise of the rights granted herein.
+
+ 7. The Free Software Foundation may publish revised and/or new versions
+of the General Public License from time to time. Such new versions will
+be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+Each version is given a distinguishing version number. If the Program
+specifies a version number of the license which applies to it and "any
+later version", you have the option of following the terms and conditions
+either of that version or of any later version published by the Free
+Software Foundation. If the Program does not specify a version number of
+the license, you may choose any version ever published by the Free Software
+Foundation.
+
+ 8. If you wish to incorporate parts of the Program into other free
+programs whose distribution conditions are different, write to the author
+to ask for permission. For software which is copyrighted by the Free
+Software Foundation, write to the Free Software Foundation; we sometimes
+make exceptions for this. Our decision will be guided by the two goals
+of preserving the free status of all derivatives of our free software and
+of promoting the sharing and reuse of software generally.
+
+ NO WARRANTY
+
+ 9. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
+FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
+OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
+PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
+OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
+MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. 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.
+
+ 10. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
+REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
+INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
+OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
+TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
+YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
+PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGES.
+
+ END OF TERMS AND CONDITIONS
+
+ Anhang: Bedingungen auf eigene neue Bibliotheken anwenden
+
+Wenn Sie ein neues Programm entwickeln und von gröÃtmöglichem Nutzen für
die
+Allgemeinheit sein soll, ist der beste Weg dies zu erreichen Freie Software,
+die jeder, unter diesen Bedingungen, weiterverbreiten und verändern kann.
+
+Dazu fügen Sie folgende Hinweise zum Programm hinzu. Am sichersten ist es, den
+Hinweis am Anfang jeder Quelldatei anzubringen, um den Ausschluss jeder
Gewähr-
+leistung am wirksamsten zu vermitteln; und jede Datei sollte mindestens eine
+<em>Copyright</em>-Zeile und einen Verweis auf den vollständigen Hinweis
enthalten.
+
+ <Eine Zeile mit dem Namen der Bibliothek und dem Zweck.>
+ Copyright (C) 19jj <Name des Autors>
+
+<span xml:lang="en"> This program is free software; you can redistribute it
and/or modify
+ it under the terms of the GNU General Public License as published by
+ the Free Software Foundation; either version 1, or (at your option)
+ any later version.
+
+ This program is distributed in the hope that it will be useful,
+ but WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+ GNU General Public License for more details.
+
+ You should have received a copy of the GNU General Public License
+ along with this program; if not, write to the Free Software
+ Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.</span>
+
+<span class="translation"> Dieses Programm ist Freie Software: Sie können
es unter den Bedingungen
+ der GNU General Public License, wie von der Free Software Foundation,
+ Version 1 der Lizenz oder (nach Ihrer Option) jeder neueren
+ veröffentlichten Version, weiterverbreiten und/oder modifizieren.
+
+ Dieses Programm wird in der Hoffnung, dass es nützlich sein wird, aber
+ OHNE JEDE GEWÃHRLEISTUNG, bereitgestellt; sogar ohne die implizite
+ Gewährleistung der MARKTFÃHIGKEIT oder EIGNUNG FÃR EINEN BESTIMMTEN
ZWECK.
+ Siehe die GNU General Public License für weitere Details.
+
+ Sie sollten eine Kopie der GNU General Public License zusammen mit diesem
+ Programm erhalten haben. Wenn nicht, schreiben Sie an die Free Software
+ Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.</span>
+
+Fügen Sie auÃerdem Informationen hinzu, wie man Sie per E-Mail und Brief
kontaktieren
+kann.
+
+Ist das Programm interaktiv, blenden Sie einen kurzen Hinweis ein, wenn es in
+diesem Modus ausgeführt wird:
+
+ Gnomovision, Version 69, Copyright (C) 19xx Name des Autors
+ <span xml:lang="en">Gnomovision comes with ABSOLUTELY NO WARRANTY; for
details
+ type ‚show w'. This is free software, and you are welcome
+ to redistribute it under certain conditions; type ‚show c‘
+ for details.</span>
+
+ Gnomovision wird OHNE JEDE GEWÃHRLEISTUNG angeboten; Details
+ unter ‚show w‘. Dies ist Freie Software und darf unter
+ bestimmten Bedingungen weitergeben werden; siehe ‚<span
xml:lang="en">show c</span>‘
+ für Details.
+
+Die hypothetischen Befehle ‚<span xml:lang="en">show w</span>‘ und
‚<span xml:lang="en">show c</span>‘ sollten die entsprechenden Teile
+der General Public License anzeigen. Natürlich können die verwendeten
Befehle anders
+als genannt werden; es sind auch Mausklicks oder
Menüpunkte ‑ was auch immer
+sinnvoll ist ‑ möglich.
+
+Sie sollten sich von Ihren Arbeitgeber (wenn Sie als ProgrammiererIn arbeiten)
oder
+ggf. von der Schule ein <em>Copyright-Verzicht</em> für das Programm
unterschreiben
+lassen. Ein Beispiel:
+
+ Yoyodyne, Inc. verzichtet hiermit auf alle
+ Copyright-Interessen an dem von
+ James Hacker
+ geschriebenen Programm ‚Gnomovision‘
+ (welches Compilerdurchläufe macht).
+
+ <var>1989-04-01, <Unterschrift von Ty Coon></var>
+ Ty Coon, stellv. Vizepräsident
+
+Das war schon alles, fertig!
+</pre>
+
+
+<div style="font-size: small;">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't have notes.-->
+ </div>
+</div>
+
+<!--#include virtual="/server/footer.de.html" -->
+<div id="footer">
+
+<p>
+Bitte senden Sie Fragen zur FSF & GNU an <a
+href="mailto:address@hidden";><address@hidden></a>. Sie können auch die
<a
+href="/contact/contact">Free Software Foundation kontaktieren</a>.
+<br />
+Bitte senden Sie ungültige Verweise und andere Korrekturen oder Vorschläge
+an <a
+href="mailto:address@hidden";><address@hidden></a>.
+</p>
+
+<p>
+Bitte beachten Sie die <a
+href="/server/standards/README.translations">LIESMICH für Ãbersetzungen</a>,
+um weitere Informationen über die Koordinierung und Einsendung von
+Ãbersetzungen zu erhalten.
+</p>
+
+<p>
+Copyright-Hinweis siehe oben.</p>
+<address><!-- --></address>
+
+<div class="translators-credits">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.-->
+<strong>Ãbersetzung:</strong> Joerg Kohne, 2011.</div>
+ <p>
+<!-- timestamp start -->
+Aktualisierung:
+
+$Date: 2011/10/29 16:35:40 $
+
+<!-- timestamp end -->
+</p>
+</div>
+
+<!-- <div id="translations">
+ -->
+<!-- <h4>
+Translations of this page</h4> -->
+<!-- -->
+<!-- Please keep this list alphabetical by language code. -->
+<!-- Comment what the language is for each type, i.e. de is German. -->
+<!-- Write the language name in its own language (Deutsch) in the text. -->
+<!-- If you add a new language here, please -->
+<!-- advise address@hidden and add it to -->
+<!-- - /home/www/html/server/standards/README.translations.html -->
+<!-- - one of the lists under the section "Translations Underway" -->
+<!-- - if there is a translation team, you also have to add an alias -->
+<!-- to mail.gnu.org:/com/mailer/aliases -->
+<!-- Please also check you have the language code right; see: -->
+<!-- http://www.loc.gov/standards/iso639-2/php/code_list.php -->
+<!-- If the 2-letter ISO 639-1 code is not available, -->
+<!-- use the 3-letter ISO 639-2. -->
+<!-- Please use W3C normative character entities. -->
+<!-- -->
+<!-- <gnun>
+<ul class="translations-list"> -->
+<!-- English -->
+<!-- <li><a
href="/licenses/old-licenses/gpl-1.0.html">English</a> [en]</li> -->
+<!-- </ul></gnun> -->
+<!-- </div>
+ -->
+</div>
+</body>
+</html>
Index: gpl-2.0-faq.de.html
===================================================================
RCS file: gpl-2.0-faq.de.html
diff -N gpl-2.0-faq.de.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ gpl-2.0-faq.de.html 29 Oct 2011 16:35:41 -0000 1.1
@@ -0,0 +1,2456 @@
+
+
+<!--#include virtual="/server/header.de.html" -->
+
+<!-- This file is automatically generated by GNUnited Nations! -->
+<title>GNU GPLv2.0: Häufig gestellte Fragen (FAQ) - GNU Projekt - Free
Software
+Foundation (FSF)</title>
+
+<!--#include virtual="/server/banner.de.html" -->
+<!--#include virtual="/licenses/old-licenses/po/gpl-2.0-faq.translist" -->
+<h2>GNU GPLv2.0: Häufig gestellte Fragen (FAQ)</h2>
+
+<p>
+Diese Seite enthält Antworten auf Häufig gestellte Fragen (FAQ) über die GNU
+General Public License (GPL), Version 2. Bitte beachten Sie auch die
+aktuellen <a href="/licenses/gpl-faq">Häufig gestellten Fragen (FAQ) über
+GNU Lizenzen</a> sowie weitere <a href="/licenses/licenses">Lizenzen</a> der
+Free Software Foundation.</p>
+
+<p>
+Nachdem Sie diese Häufig gestellte Fragen gelesen haben, können Sie Ihr <a
+href="/cgi-bin/license-quiz.cgi">Wissen über die Lizenzierung von Freie
+Software testen</a>.
+</p>
+
+<!-- Replace this list with the page's contents. -->
+<h4>Inhalt</h4>
+
+ <h4>Grundsätzliche Fragen über die <em>GNU GPL</em>, dem <em>GNU
Projekt</em>
+sowie der <span xml:lang="en" lang="en"><em>Free Software
+Foundation</em></span>.</h4>
+
+ <ul>
+ <li><a href="#WhatDoesGPLStandFor" name="TOCWhatDoesGPLStandFor">What does
+“GPL” stand for?</a></li>
+
+ <li><a href="#DoesFreeSoftwareMeanUsingTheGPL"
+name="TOCDoesFreeSoftwareMeanUsingTheGPL">Does free software mean using the
+GPL?</a></li>
+
+ <li><a href="#WhyUseGPL" name="TOCWhyUseGPL">Why should I use the GNU GPL
rather
+than other free software licenses?</a></li>
+
+ <li><a href="#DoesAllGNUSoftwareUseTheGNUGPLAsItsLicense"
+name="TOCDoesAllGNUSoftwareUseTheGNUGPLAsItsLicense">Does all GNU software
+use the GNU GPL as its license?</a></li>
+
+ <li><a href="#DoesUsingTheGPLForAProgramMakeItGNUSoftware"
+name="TOCDoesUsingTheGPLForAProgramMakeItGNUSoftware">Does using the GPL for
+a program make it GNU software?</a></li>
+
+ <li><a href="#GPLOtherThanSoftware" name="TOCGPLOtherThanSoftware">Can I
use the
+GPL for something other than software?</a></li>
+
+ <li><a href="#WhyNotGPLForManuals" name="TOCWhyNotGPLForManuals">Why don't
you
+use the GPL for manuals?</a></li>
+
+ <li><a href="#GPLTranslations" name="TOCGPLTranslations">Are there
translations
+of the GPL into other languages?</a></li>
+
+ <li><a href="#WhySomeGPLAndNotLGPL" name="TOCWhySomeGPLAndNotLGPL">Why are
some
+GNU libraries released under the ordinary GPL rather than the Lesser
+GPL?</a></li>
+
+ <li><a href="#WhoHasThePower" name="TOCWhoHasThePower">Who has the power to
+enforce the GPL?</a></li>
+
+ <li><a href="#AssignCopyright" name="TOCAssignCopyright">Why does the FSF
+require that contributors to FSF-copyrighted programs assign copyright to
+the FSF? If I hold copyright on a GPL'ed program, should I do this, too? If
+so, how?</a></li>
+
+ <li><a href="#ModifyGPL" name="TOCModifyGPL">Can I modify the GPL and make
a
+modified license?</a></li>
+
+ </ul>
+
+ <h4>Allgemeines Verständnis der GNU Lizenzen</h4>
+
+ <ul>
+ <li><a href="#WhyDoesTheGPLPermitUsersToPublishTheirModifiedVersions"
+name="TOCWhyDoesTheGPLPermitUsersToPublishTheirModifiedVersions">Why does
+the GPL permit users to publish their modified versions?</a></li>
+
+ <li><a href="#GPLRequireSourcePostedPublic"
+name="TOCGPLRequireSourcePostedPublic">Does the GPL require that source code
+of modified versions be posted to the public?</a></li>
+
+ <li><a href="#GPLAndNonfreeOnSameMachine"
name="TOCGPLAndNonfreeOnSameMachine">
+Can I have a GPL-covered program and an unrelated non-free program on the
+same computer?</a></li>
+
+ <li><a href="#CanIDemandACopy" name="TOCCanIDemandACopy">If I know someone
has a
+copy of a GPL-covered program, can I demand he give me a copy?</a></li>
+
+ <li><a href="#WhatDoesWrittenOfferValid"
+name="TOCWhatDoesWrittenOfferValid">What does this “written offer
+valid for any third party” mean? Does that mean everyone in the world
+can get the source to any GPL'ed program no matter what?</a></li>
+
+ <li><a href="#TheGPLSaysModifiedVersions"
+name="TOCTheGPLSaysModifiedVersions">The GPL says that modified versions, if
+released, must be “licensed … to all third parties.” Who
+are these third parties?</a></li>
+
+ <li><a href="#DoesTheGPLAllowMoney" name="TOCDoesTheGPLAllowMoney">Does
the GPL
+allow me to sell copies of the program for money?</a></li>
+
+ <li><a href="#DoesTheGPLAllowDownloadFee"
name="TOCDoesTheGPLAllowDownloadFee">
+Does the GPL allow me to charge a fee for downloading the program from my
+site?</a></li>
+
+ <li><a href="#DoesTheGPLAllowRequireFee"
name="TOCDoesTheGPLAllowRequireFee">
+Does the GPL allow me to require that anyone who receives the software must
+pay me a fee and/or notify me?</a></li>
+
+ <li><a href="#DoesTheGPLRequireAvailabilityToPublic"
+name="TOCDoesTheGPLRequireAvailabilityToPublic">If I distribute GPL'd
+software for a fee, am I required to also make it available to the public
+without a charge?</a></li>
+
+ <li><a href="#DoesTheGPLAllowNDA" name="TOCDoesTheGPLAllowNDA">Does the GPL
+allow me to distribute a copy under a nondisclosure agreement?</a></li>
+
+ <li><a href="#DoesTheGPLAllowModNDA" name="TOCDoesTheGPLAllowModNDA">Does
the
+GPL allow me to distribute a modified or beta version under a nondisclosure
+agreement?</a></li>
+
+ <li><a href="#DevelopChangesUnderNDA"
name="TOCDevelopChangesUnderNDA">Does the
+GPL allow me to develop a modified version under a nondisclosure
+agreement?</a></li>
+
+ <li><a href="#WhyMustIInclude" name="TOCWhyMustIInclude">Why does the GPL
+require including a copy of the GPL with every copy of the program?</a></li>
+
+ <li><a href="#WhatIfWorkIsShort" name="TOCWhatIfWorkIsShort">What if the
work is
+not much longer than the license itself?</a></li>
+
+ <li><a href="#RequiredToClaimCopyright"
name="TOCRequiredToClaimCopyright">Am I
+required to claim a copyright on my modifications to a GPL-covered
+program?</a></li>
+
+ <li><a href="#CombinePublicDomainWithGPL"
+name="TOCCombinePublicDomainWithGPL">If a program combines public-domain
+code with GPL-covered code, can I take the public-domain part and use it as
+public domain code?</a></li>
+
+ <li><a href="#IWantCredit" name="TOCIWantCredit">I want to get credit for
my
+work. I want people to know what I wrote. Can I still get credit if I use
+the GPL?</a></li>
+
+ <li><a href="#GPLOmitPreamble" name="TOCGPLOmitPreamble">Can I omit the
preamble
+of the GPL, or the instructions for how to use it on your own programs, to
+save space?</a></li>
+
+ <li><a href="#WhatIsCompatible" name="TOCWhatIsCompatible">What does it
mean to
+say that two licenses are “compatible”?</a></li>
+
+ <li><a href="#WhatDoesCompatMean" name="TOCWhatDoesCompatMean">What does
it mean
+to say a license is “compatible with the GPL”?</a></li>
+
+ <li><a href="#OrigBSD" name="TOCOrigBSD">Why is the original BSD license
+incompatible with the GPL?</a></li>
+
+ <li><a href="#MereAggregation" name="TOCMereAggregation">What is the
difference
+between “mere aggregation” and “combining two modules into
+one program”?</a></li>
+
+ <li><a href="#AssignCopyright" name="TOCAssignCopyright">Why does the FSF
+require that contributors to FSF-copyrighted programs assign copyright to
+the FSF? If I hold copyright on a GPL'ed program, should I do this, too? If
+so, how?</a></li>
+
+ <li><a href="#GPLCommercially" name="TOCGPLCommercially">If I use a piece
of
+software that has been obtained under the GNU GPL, am I allowed to modify
+the original code into a new program, then distribute and sell that new
+program commercially?</a></li>
+
+ <li><a href="#GPLOtherThanSoftware" name="TOCGPLOtherThanSoftware">Can I
use the
+GPL for something other than software?</a></li>
+
+ <li><a href="#LGPLJava" name="TOCLGPLJava">How does the LGPL work with
Java?</a></li>
+
+
+ </ul>
+
+ <h4>Verwendung von GNU Lizenzen für eigene Programme</h4>
+
+ <ul>
+
+ <li><a href="#CouldYouHelpApplyGPL" name="TOCCouldYouHelpApplyGPL">Could
you
+give me step by step instructions on how to apply the GPL to my
program?</a></li>
+
+ <li><a href="#WhyUseGPL" name="TOCWhyUseGPL">Why should I use the GNU GPL
rather
+than other free software licenses?</a></li>
+
+ <li><a href="#WhyMustIInclude" name="TOCWhyMustIInclude">Why does the GPL
+require including a copy of the GPL with every copy of the program?</a></li>
+
+ <li><a href="#WhatIfWorkIsShort" name="TOCWhatIfWorkIsShort">What if the
work is
+not much longer than the license itself?</a></li>
+
+ <li><a href="#GPLOmitPreamble" name="TOCGPLOmitPreamble">Can I omit the
preamble
+of the GPL, or the instructions for how to use it on your own programs, to
+save space?</a></li>
+
+ <li><a href="#HowIGetCopyright" name="TOCHowIGetCopyright">How do I get a
+copyright on my program in order to release it under the GPL?</a></li>
+
+ <li><a href="#WhatIfSchool" name="TOCWhatIfSchool">What if my school might
want
+to make my program into its own proprietary software product?</a></li>
+
+ <li><a href="#ReleaseUnderGPLAndNF" name="TOCReleaseUnderGPLAndNF">I would
like
+to release a program I wrote under the GNU GPL, but I would like to use the
+same code in non-free programs.</a></li>
+
+ <li><a href="#CanDeveloperThirdParty" name="TOCCanDeveloperThirdParty">Can
the
+developer of a program who distributed it under the GPL later license it to
+another party for exclusive use?</a></li>
+
+ <li><a href="#GPLUSGov" name="TOCGPLUSGov">Can the US Government release a
+program under the GNU GPL?</a></li>
+
+ <li><a href="#GPLUSGovAdd" name="TOCGPLUSGovAdd">Can the US Government
release
+improvements to a GPL-covered program?</a></li>
+
+ <li><a href="#VersionTwoOrLater" name="TOCVersionTwoOrLater">Why should
programs
+say “Version 2 of the GPL or any later version”?</a></li>
+
+ <li><a href="#GPLOutput" name="TOCGPLOutput">Is there some way that I can
GPL
+the output people get from use of my program? For example, if my program is
+used to develop hardware designs, can I require these these designs must be
+free?</a></li>
+
+ <li><a href="#WhyNotGPLForManuals" name="TOCWhyNotGPLForManuals">Why don't
you
+use the GPL for manuals?</a></li>
+
+ <li><a href="#FontException" name="TOCFontException">How does the GPL
apply to
+fonts?</a></li>
+
+ <li><a href="#WMS" name="TOCWMS">What license should I use for website
+maintenance system templates?</a></li>
+
+ <li><a href="#NonFreeTools" name="TOCNonFreeTools">Can I release a program
under
+the GPL which I developed using non-free tools?</a></li>
+ </ul>
+
+ <h4>Verbreitung von unter der GNU GPL freigegebener Programme</h4>
+
+ <ul>
+
+ <li><a href="#ModifiedJustBinary" name="TOCModifiedJustBinary">Can I
release a
+modified version of a GPL-covered program in binary form only?</a></li>
+
+ <li><a href="#UnchangedJustBinary" name="TOCUnchangedJustBinary">I
downloaded
+just the binary from the net. If I distribute copies, do I have to get the
+source and distribute that too?</a></li>
+
+ <li><a href="#DistributeWithSourceOnInternet"
+name="TOCDistributeWithSourceOnInternet">I want to distribute binaries via
+physical media without accompanying sources. Can I provide source code by
+FTP instead of by mail order?</a></li>
+
+ <li><a href="#RedistributedBinariesGetSource"
+name="TOCRedistributedBinariesGetSource">My friend got a GPL-covered binary
+with an offer to supply source, and made a copy for me. Can I use the offer
+to obtain the source?</a></li>
+
+ <li><a href="#SourceAndBinaryOnDifferentSites"
+name="TOCSourceAndBinaryOnDifferentSites">Can I put the binaries on my
+Internet server and put the source on a different Internet site?</a></li>
+
+ <li><a href="#DistributeExtendedBinary"
name="TOCDistributeExtendedBinary">I
+want to distribute an extended version of a GPL-covered program in binary
+form. Is it enough to distribute the source for the original version?</a></li>
+
+ <li><a href="#DistributingSourceIsInconvenient"
+name="TOCDistributingSourceIsInconvenient">I want to distribute binaries,
+but distributing complete source is inconvenient. Is it ok if I give users
+the diffs from the “standard” version along with the
+binaries?</a></li>
+
+ <li><a href="#AnonFTPAndSendSources" name="TOCAnonFTPAndSendSources">I
want to
+make binaries available for anonymous FTP, but send sources only to people
+who order them.</a></li>
+
+ <li><a href="#HowCanIMakeSureEachDownloadGetsSource"
+name="TOCHowCanIMakeSureEachDownloadGetsSource">How can I make sure each
+user who downloads the binaries also gets the source?</a></li>
+
+ <li><a href="#ReleaseNotOriginal" name="TOCReleaseNotOriginal"> Can I
release a
+program with a license which says that you can distribute modified versions
+of it under the GPL but you can't distribute the original itself under the
+GPL?</a></li>
+
+ <li><a href="#CompanyGPLCostsMoney" name="TOCCompanyGPLCostsMoney"> I just
found
+out that a company has a copy of a GPL'ed program, and it costs money to get
+it. Aren't they violating the GPL by not making it available on the
+Internet?</a></li>
+
+ <li><a href="#UnreleasedMods" name="TOCUnreleasedMods"> A company is
running a
+modified version of a GPL'ed program on a web site. Does the GPL say they
+must release their modified sources?</a></li>
+
+ <li><a href="#InternalDistribution" name="TOCInternalDistribution"> Is use
+within one organization or company “distribution”?</a></li>
+
+ <li><a href="#StolenCopy" name="TOCStolenCopy"> If someone steals a CD
+containing a version of a GPL-covered program, does the GPL give him the
+right to redistribute that version?</a></li>
+
+ <li><a href="#TradeSecretRelease" name="TOCTradeSecretRelease"> What if a
+company distributes a copy as a trade secret?</a></li>
+
+ <li><a href="#GPLFairUse" name="TOCGPLFairUse">Do I have “fair
use”
+rights in using the source code of a GPL-covered program?</a></li>
+
+ <li><a href="#DistributeSubsidiary" name="TOCDistributeSubsidiary"> Does
moving
+a copy to a majority-owned, and controlled, subsidiary constitute
+distribution?</a></li>
+
+ <li><a href="#ClickThrough" name="TOCClickThrough"> Can software
installers ask
+people to click to agree to the GPL? If I get some software under the GPL,
+do I have to agree to anything?</a></li>
+
+ <li><a href="#GPLCompatInstaller" name="TOCGPLCompatInstaller">I would
like to
+bundle GPLed software with some sort of installation software. Does that
+installer need to have a GPL-compatible license?</a></li>
+
+ </ul>
+
+ <h4>Using programs released under the GPL when writing other programs</h4>
+
+ <ul>
+
+ <li><a href="#GPLAndNonfreeOnSameMachine"
name="TOCGPLAndNonfreeOnSameMachine">
+Can I have a GPL-covered program and an unrelated non-free program on the
+same computer?</a></li>
+
+ <li><a href="#CanIUseGPLToolsForNF" name="TOCCanIUseGPLToolsForNF">Can I
use
+GPL-covered editors such as GNU Emacs to develop non-free programs? Can I
+use GPL-covered tools such as GCC to compile them?</a></li>
+
+ <li><a href="#GPLOutput" name="TOCGPLOutput">Is there some way that I can
GPL
+the output people get from use of my program? For example, if my program is
+used to develop hardware designs, can I require these these designs must be
+free?</a></li>
+
+ <li><a href="#WhatCaseIsOutputGPL" name="TOCWhatCaseIsOutputGPL">In what
cases
+is the output of a GPL program covered by the GPL too?</a></li>
+
+ <li><a href="#PortProgramToGL" name="TOCPortProgramToGL">If I port my
program to
+GNU/Linux, does that mean I have to release it as Free Software under the
+GPL or some other Free Software license?</a></li>
+
+ <li><a href="#GPLInProprietarySystem" name="TOCGPLInProprietarySystem">I'd
like
+to incorporate GPL-covered software in my proprietary system. Can I do
+this?</a></li>
+
+ <li><a href="#LibGCCException" name="TOCLibGCCException">Does the libstdc++
+exception permit dynamic linking?</a></li>
+
+ </ul>
+
+ <h4>Kombination von Werken mit unter der GNU GPL freigegeben Quellcode</h4>
+
+ <ul>
+
+ <li><a href="#MereAggregation" name="TOCMereAggregation">What is the
difference
+between “mere aggregation” and “combining two modules into
+one program”?</a></li>
+
+ <li><a href="#GPLFairUse" name="TOCGPLFairUse">Do I have “fair
use”
+rights in using the source code of a GPL-covered program?</a></li>
+
+ <li><a href="#GPLUSGovAdd" name="TOCGPLUSGovAdd">Can the US Government
release
+improvements to a GPL-covered program?</a></li>
+
+ <li><a href="#IfLibraryIsGPL" name="TOCIfLibraryIsGPL">If a library is
released
+under the GPL (not the LGPL), does that mean that any program which uses it
+has to be under the GPL?</a></li>
+
+ <li><a href="#LinkingWithGPL" name="TOCLinkingWithGPL">You have a GPL'ed
program
+that I'd like to link with my code to build a proprietary program. Does the
+fact that I link with your program mean I have to GPL my program?</a></li>
+
+ <li><a href="#SwitchToLGPL" name="TOCSwitchToLGPL">If so, is there any
chance I
+could get a license of your program under the Lesser GPL?</a></li>
+
+ <li><a href="#WillYouMakeAnException"
name="TOCWillYouMakeAnException">Using a
+certain GNU program under the GPL does not fit our project to make
+proprietary software. Will you make an exception for us? It would mean more
+users of that program.</a></li>
+
+ <li><a href="#IfInterpreterIsGPL" name="TOCIfInterpreterIsGPL">If a
programming
+language interpreter is released under the GPL, does that mean programs
+written to be interpreted by it must be under GPL-compatible licenses?</a></li>
+
+ <li><a href="#InterpreterIncompat" name="TOCInterpreterIncompat">If a
+programming language interpreter has a license that is incompatible with the
+GPL, can I run GPL-covered programs on it?</a></li>
+
+ <li><a href="#GPLModuleLicense" name="TOCGPLModuleLicense">If I add a
module to
+a GPL-covered program, do I have to use the GPL as the license for my
+module?</a></li>
+
+ <li><a href="#GPLAndPlugins" name="TOCGPLAndPlugins">If a program released
under
+the GPL uses plug-ins, what are the requirements for the licenses of a
+plug-in?</a></li>
+
+ <li><a href="#GPLPluginsInNF" name="TOCGPLPluginsInNF">Can I apply the GPL
when
+writing a plug-in for a non-free program?</a></li>
+
+ <li><a href="#NFUseGPLPlugins" name="TOCNFUseGPLPlugins">Can I release a
+non-free program that's designed to load a GPL-covered plug-in?</a></li>
+
+ <li><a href="#GPLInProprietarySystem" name="TOCGPLInProprietarySystem">I'd
like
+to incorporate GPL-covered software in my proprietary system. Can I do
+this?</a></li>
+
+ <li><a href="#GPLWrapper" name="TOCGPLWrapper">I'd like to incorporate
+GPL-covered software in my proprietary system. Can I do this by putting a
+“wrapper” module, under a GPL-compatible lax permissive license
+(such as the X11 license) in between the GPL-covered part and the
+proprietary part?</a></li>
+
+ <li><a href="#FSWithNFLibs" name="TOCFSWithNFLibs"> Can I write free
software
+that uses non-free libraries?</a></li>
+
+ <li><a href="#GPLIncompatibleLibs" name="TOCGPLIncompatibleLibs"> What
legal
+issues come up if I use GPL-incompatible libraries with GPL software?</a></li>
+
+ <li><a href="#WindowsRuntimeAndGPL" name="TOCWindowsRuntimeAndGPL">I'm
writing a
+Windows application with Microsoft Visual C++ and I will be releasing it
+under the GPL. Is dynamically linking my program with the Visual C++
+run-time library permitted under the GPL?</a></li>
+
+ <li><a href="#MoneyGuzzlerInc" name="TOCMoneyGuzzlerInc">I'd like to modify
+GPL-covered programs and link them with the portability libraries from Money
+Guzzler Inc. I cannot distribute the source code for these libraries, so
+any user who wanted to change these versions would have to obtain those
+libraries separately. Why doesn't the GPL permit this?</a></li>
+
+ <li><a href="#GPLIncompatibleAlone" name="TOCGPLIncompatibleAlone">If
license
+for a module Q has a requirement that's incompatible with the GPL, but the
+requirement applies only when Q is distributed by itself, not when Q is
+included in a larger program, does that make the license GPL-compatible? Can
+I combine or link Q with a GPL-covered program?</a></li>
+
+ <li><a href="#OOPLang" name="TOCOOPLANG"> In an object-oriented language
such as
+Java, if I use a class that is GPL'ed without modifying, and subclass it, in
+what way does the GPL affect the larger program?</a></li>
+
+ <li><a href="#LinkingOverControlledInterface"
+name="TOCLinkingOverControlledInterface">How can I allow linking of
+proprietary modules with my GPL-covered library under a controlled interface
+only?</a></li>
+
+ <li><a href="#Consider" name="TOCConsider">Consider this situation: 1. X
+releases V1 of a project under the GPL. 2. Y contributes to the development
+of V2 with changes and new code based on V1. 3. X wants to convert V2 to a
+non-GPL license. Does X need Y's permission?</a></li>
+
+ <li><a href="#ManyDifferentLicenses" name="TOCManyDifferentLicenses">I have
+written an application that links with many different components, that have
+different licenses. I am very confused as to what licensing requirements
+are placed on my program. Can you please tell me what licenses I may
+use?</a></li>
+
+ </ul>
+
+ <h4>Questions about violations of the GPL</h4>
+
+ <ul>
+
+ <li><a href="#ReportingViolation" name="TOCReportingViolation">What should
I do
+if I discover a possible violation of the GPL?</a></li>
+
+ <li><a href="#WhoHasThePower" name="TOCWhoHasThePower">Who has the power to
+enforce the GPL?</a></li>
+
+ <li><a href="#HeardOtherLicense" name="TOCHeardOtherLicense">I heard that
+someone got a copy of a GPL'ed program under another license. Is this
+possible?</a></li>
+
+ <li><a href="#DeveloperViolate" name="TOCDeveloperViolate">Is the
developer of a
+GPL-covered program bound by the GPL? Could the developer's actions ever be
+a violation of the GPL?</a></li>
+
+ <li><a href="#CompanyGPLCostsMoney" name="TOCCompanyGPLCostsMoney"> I just
found
+out that a company has a copy of a GPL'ed program, and it costs money to get
+it. Aren't they violating the GPL by not making it available on the
+Internet?</a></li>
+
+ </ul>
+
+<hr />
+
+<dl>
+
+<dt><b><a href="#TOCWhatDoesGPLStandFor" name="WhatDoesGPLStandFor">What does
+“GPL” stand for?</a></b></dt>
+
+<dd><em>GPL</em> steht für „General Public License“. Die am
+weitesten verbreitete Lizenz ist die <em>GNU General Public License</em>
+oder kurz <em>GNU GPL</em>. Dies kann weiter zu <em>GPL</em> abgekürzt
+werden, wenn unmissverständlich die GNU GPL gemeint ist.
+<p></p></dd>
+
+<dt><b><a href="#TOCDoesFreeSoftwareMeanUsingTheGPL"
+name="DoesFreeSoftwareMeanUsingTheGPL"> Does free software mean using the
+GPL?</a></b></dt>
+
+<dd>
+Not at all—there are many other free software licenses. We have an <a
+href="/licenses/license-list.html"> incomplete list</a>. Any license that
+provides the user <a href="/philosophy/free-sw.html">certain specific
+freedoms</a> is a free software license.
+<p></p></dd>
+
+<dt><b><a href="#TOCWhyUseGPL" name="WhyUseGPL"> Why should I use the GNU GPL
+rather than other free software licenses?</a></b></dt>
+
+<dd>
+Using the GNU GPL will require that all the <a
+href="/philosophy/pragmatic.html">released improved versions be free
+software</a>. This means you can avoid the risk of having to compete with a
+proprietary modified version of your own work. However, in some special
+situations it can be better to use a <a href="/licenses/why-not-lgpl.html">
+more permissive license</a>.
+<p></p></dd>
+
+<dt><b><a href="#TOCDoesAllGNUSoftwareUseTheGNUGPLAsItsLicense"
+name="DoesAllGNUSoftwareUseTheGNUGPLAsItsLicense"> Does all GNU software use
+the GNU GPL as its license?</a></b></dt>
+
+<dd>
+Most GNU software packages use the GNU GPL, but there are a few GNU programs
+(and parts of programs) that use looser licenses, such as the Lesser GPL.
+When we do this, it is a matter of <a href="/licenses/why-not-lgpl.html">
+strategy</a>.
+<p></p></dd>
+
+<dt><b><a href="#TOCDoesUsingTheGPLForAProgramMakeItGNUSoftware"
+name="DoesUsingTheGPLForAProgramMakeItGNUSoftware"> Does using the GPL for a
+program make it GNU software?</a></b></dt>
+
+<dd>
+Anyone can release a program under the GNU GPL but that does not make it a
+GNU package.
+<p>
+Making the program a GNU software package means explicitly contributing to
+the GNU Project. This happens when the program's developers and the GNU
+Project agree to do it. If you are interested in contributing a program to
+the GNU Project, please write to <a
+href="mailto:address@hidden";><address@hidden></a>.
+</p></dd>
+
+<dt><b><a href="#TOCReportingViolation" name="ReportingViolation"> What should
I
+do if I discover a possible violation of the GPL?</a></b></dt>
+
+<dd>
+You should <a href="/licenses/gpl-violation.html">report it</a>. First,
+check the facts as best you can. Then tell the publisher or copyright
+holder of the specific GPL-covered program. If that is the Free Software
+Foundation, write to <a
+href="mailto:address@hidden";><address@hidden></a>.
+Otherwise, the program's maintainer may be the copyright holder, or else
+could tell you how to contact the copyright holder, so report it to the
+maintainer.
+<p></p></dd>
+
+<dt><b><a href="#TOCWhyDoesTheGPLPermitUsersToPublishTheirModifiedVersions"
+name="WhyDoesTheGPLPermitUsersToPublishTheirModifiedVersions"> Why does the
+GPL permit users to publish their modified versions?</a></b></dt>
+
+<dd>
+A crucial aspect of free software is that users are free to cooperate. It
+is absolutely essential to permit users who wish to help each other to share
+their bug fixes and improvements with other users.
+<p>
+Some have proposed alternatives to the GPL that require modified versions to
+go through the original author. As long as the original author keeps up
+with the need for maintenance, this may work well in practice, but if the
+author stops (more or less) to do something else or does not attend to all
+the users' needs, this scheme falls down. Aside from the practical
+problems, this scheme does not allow users to help each other.</p>
+<p>
+Sometimes control over modified versions is proposed as a means of
+preventing confusion between various versions made by users. In our
+experience, this confusion is not a major problem. Many versions of Emacs
+have been made outside the GNU Project, but users can tell them apart. The
+GPL requires the maker of a version to place his or her name on it, to
+distinguish it from other versions and to protect the reputations of other
+maintainers.
+</p></dd>
+
+<dt><b><a href="#TOCGPLRequireSourcePostedPublic"
+name="GPLRequireSourcePostedPublic"> Does the GPL require that source code
+of modified versions be posted to the public?</a></b></dt>
+
+<dd>
+The GPL does not require you to release your modified version. You are free
+to make modifications and use them privately, without ever releasing them.
+This applies to organizations (including companies), too; an organization
+can make a modified version and use it internally without ever releasing it
+outside the organization.
+<p>
+But <em>if</em> you release the modified version to the public in some way,
+the GPL requires you to make the modified source code available to the
+program's users, under the GPL.</p>
+<p>
+Thus, the GPL gives permission to release the modified program in certain
+ways, and not in other ways; but the decision of whether to release it is up
+to you.
+</p></dd>
+
+<dt><b><a href="#TOCGPLAndNonfreeOnSameMachine"
+name="GPLAndNonfreeOnSameMachine"> Can I have a GPL-covered program and an
+unrelated non-free program on the same computer?</a></b></dt>
+<dd>
+Yes. The “mere aggregation” clause in the GPL makes this
+permission explicit, but that only reinforces what we believe would be true
+anyway.
+<p></p></dd>
+
+<dt><b><a href="#TOCCanIDemandACopy" name="CanIDemandACopy">If I know someone
+has a copy of a GPL-covered program, can I demand he give me a
copy?</a></b></dt>
+
+<dd>
+No. The GPL gives him permission to make and redistribute copies of the
+program <em>if he chooses to do so</em>. He also has the right not to
+redistribute the program, if that is what he chooses.
+<p></p></dd>
+
+<dt><b><a href="#TOCWhatDoesWrittenOfferValid"
name="WhatDoesWrittenOfferValid">
+What does this “written offer valid for any third party” mean?
+Does that mean everyone in the world can get the source to any GPL'ed
+program no matter what?</a></b></dt>
+
+<dd>
+<p>If you choose to provide source through a written offer, then anybody who
+requests the source from you is entitled to receive it.</p>
+<p>
+If you commercially distribute binaries not accompanied with source code,
+the GPL says you must provide a written offer to distribute the source code
+later. When users non-commercially redistribute the binaries they received
+from you, they must pass along a copy of this written offer. This means
+that people who did not get the binaries directly from you can still receive
+copies of the source code, along with the written offer.</p>
+<p>
+The reason we require the offer to be valid for any third party is so that
+people who receive the binaries indirectly in that way can order the source
+code from you.
+</p></dd>
+
+<dt><b><a href="#TOCTheGPLSaysModifiedVersions"
+name="TheGPLSaysModifiedVersions">The GPL says that modified versions, if
+released, must be “licensed … to all third parties.” Who
+are these third parties?</a></b></dt>
+
+<dd>
+Section 2 says that modified versions you distribute must be licensed to all
+third parties under the GPL. “All third parties” means
+absolutely everyone—but this does not require you to
+<strong>do</strong> anything physically for them. It only means they have a
+license from you, under the GPL, for your version.
+<p></p></dd>
+
+<dt><b><a href="#TOCRequiredToClaimCopyright"
name="RequiredToClaimCopyright">Am
+I required to claim a copyright on my modifications to a GPL-covered
+program?</a></b></dt>
+
+<dd>
+You are not required to claim a copyright on your changes. In most
+countries, however, that happens automatically by default, so you need to
+place your changes explicitly in the public domain if you do not want them
+to be copyrighted.
+<p>
+Whether you claim a copyright on your changes or not, either way you must
+release the modified version, as a whole, under the GPL. (<a
+href="#GPLRequireSourcePostedPublic">if you release your modified version at
+all</a>)
+</p></dd>
+
+
+<dt><b><a href="#TOCCombinePublicDomainWithGPL"
+name="CombinePublicDomainWithGPL">If a program combines public-domain code
+with GPL-covered code, can I take the public-domain part and use it as
+public domain code?</a></b></dt>
+
+<dd>
+You can do that, if you can figure out which part is the public domain part
+and separate it from the rest. If code was put in the public domain by its
+developer, it is in the public domain no matter where it has been.
+<p></p></dd>
+
+<dt><b><a href="#TOCDoesTheGPLAllowMoney" name="DoesTheGPLAllowMoney"> Does the
+GPL allow me to sell copies of the program for money?</a></b></dt>
+
+<dd>
+Yes, the GPL allows everyone to do this. The <a
+href="/philosophy/selling.html"> right to sell copies </a> is part of the
+definition of free software. Except in one special situation, there is no
+limit on what price you can charge. (The one exception is the required
+written offer to provide source code that must accompany binary-only
+release.)
+<p></p></dd>
+
+<dt><b><a href="#TOCDoesTheGPLAllowDownloadFee"
+name="DoesTheGPLAllowDownloadFee"> Does the GPL allow me to charge a fee for
+downloading the program from my site?</a></b></dt>
+
+<dd>
+Yes. You can charge any fee you wish for distributing a copy of the
+program. If you distribute binaries by download, you must provide
+“equivalent access” to download the source—therefore, the
+fee to download source may not be greater than the fee to download the
+binary.
+<p></p></dd>
+
+<dt><b><a href="#TOCDoesTheGPLAllowRequireFee"
name="DoesTheGPLAllowRequireFee">
+Does the GPL allow me to require that anyone who receives the software must
+pay me a fee and/or notify me?</a></b></dt>
+
+<dd>
+No. In fact, a requirement like that would make the program non-free. If
+people have to pay when they get a copy of a program, or if they have to
+notify anyone in particular, then the program is not free. See the <a
+href="/philosophy/free-sw.html"> definition of free software</a>.
+<p>
+The GPL is a free software license, and therefore it permits people to use
+and even redistribute the software without being required to pay anyone a
+fee for doing so.
+</p></dd>
+
+<dt><b><a href="#TOCDoesTheGPLRequireAvailabilityToPublic"
+name="DoesTheGPLRequireAvailabilityToPublic">If I distribute GPL'd software
+for a fee, am I required to also make it available to the public without a
+charge?</a></b></dt>
+
+<dd>
+No. However, if someone pays your fee and gets a copy, the GPL gives them
+the freedom to release it to the public, with or without a fee. For
+example, someone could pay your fee, and then put her copy on a web site for
+the general public.
+<p></p></dd>
+
+<dt><b><a href="#TOCDoesTheGPLAllowNDA" name="DoesTheGPLAllowNDA"> Does the GPL
+allow me to distribute copies under a nondisclosure agreement?</a></b></dt>
+
+<dd>
+No. The GPL says that anyone who receives a copy from you has the right to
+redistribute copies, modified or not. You are not allowed to distribute the
+work on any more restrictive basis.
+<p>If someone asks you to sign an NDA for receiving GPL-covered software
+copyrighted by the FSF, please inform us immediately by writing to <a
+href="mailto:address@hidden";>address@hidden</a>.</p>
+<p>
+If the violation involves GPL-covered code that has some other copyright
+holder, please inform that copyright holder, just as you would for any other
+kind of violation of the GPL.
+</p></dd>
+
+
+<dt><b><a href="#TOCDoesTheGPLAllowModNDA" name="DoesTheGPLAllowModNDA"> Does
+the GPL allow me to distribute a modified or beta version under a
+nondisclosure agreement?</a></b></dt>
+
+<dd>
+No. The GPL says that your modified versions must carry all the freedoms
+stated in the GPL. Thus, anyone who receives a copy of your version from
+you has the right to redistribute copies (modified or not) of that version.
+You may not distribute any version of the work on a more restrictive basis.
+<p></p></dd>
+
+<dt><b><a href="#TOCDevelopChangesUnderNDA" name="DevelopChangesUnderNDA"> Does
+the GPL allow me to develop a modified version under a nondisclosure
+agreement?</a></b></dt>
+
+<dd>
+Yes. For instance, you can accept a contract to develop changes and agree
+not to release <em>your changes</em> until the client says ok. This is
+permitted because in this case no GPL-covered code is being distributed
+under an NDA.
+<p>
+You can also release your changes to the client under the GPL, but agree not
+to release them to anyone else unless the client says ok. In this case,
+too, no GPL-covered code is being distributed under an NDA, or under any
+additional restrictions.</p>
+<p>
+The GPL would give the client the right to redistribute your version. In
+this scenario, the client will probably choose not to exercise that right,
+but does <em>have</em> the right.
+</p></dd>
+
+<dt><b><a href="#TOCIWantCredit" name="IWantCredit">I want to get credit for my
+work. I want people to know what I wrote. Can I still get credit if I use
+the GPL?</a></b></dt>
+
+<dd>
+You can certainly get credit for the work. Part of releasing a program
+under the GPL is writing a copyright notice in your own name (assuming you
+are the copyright holder). The GPL requires all copies to carry an
+appropriate copyright notice.
+<p></p></dd>
+
+<dt><b><a href="#TOCWhyMustIInclude" name="WhyMustIInclude">Why does the GPL
+require including a copy of the GPL with every copy of the
program?</a></b></dt>
+
+<dd>
+Including a copy of the license with the work is vital so that everyone who
+gets a copy of the program can know what his rights are.
+<p>
+It might be tempting to include a URL that refers to the license, instead of
+the license itself. But you cannot be sure that the URL will still be
+valid, five years or ten years from now. Twenty years from now, URLs as we
+know them today may no longer exist.</p>
+<p>
+The only way to make sure that people who have copies of the program will
+continue to be able to see the license, despite all the changes that will
+happen in the network, is to include a copy of the license in the program.
+</p></dd>
+
+<dt><b><a href="#TOCWhatIfWorkIsShort" name="WhatIfWorkIsShort">What if the
work
+is not much longer than the license itself?</a></b></dt>
+
+<dd>
+If a single program is that short, you may as well use a simple
+all-permissive license for it, rather than the GNU GPL.
+<p></p></dd>
+
+<dt><b><a href="#TOCGPLOmitPreamble" name="GPLOmitPreamble"> Can I omit the
+preamble of the GPL, or the instructions for how to use it on your own
+programs, to save space?</a></b></dt>
+<dd>
+The preamble and instructions are integral parts of the GNU GPL and may not
+be omitted. In fact, the GPL is copyrighted, and its license permits only
+verbatim copying of the entire GPL. (You can use the legal terms to make <a
+href="#ModifyGPL">another license</a> but it won't be the GNU GPL.)
+<p>
+The preamble and instructions add up to some 5000 characters, less than 1/3
+of the GPL's total size. They will not make a substantial fractional change
+in the size of a software package unless the package itself is quite small.
+In that case, you may as well use a simple all-permissive license rather
+than the GNU GPL.
+</p></dd>
+
+<dt><b><a href="#TOCWhatIsCompatible" name="WhatIsCompatible">What does it mean
+to say that two licenses are “compatible”?</a></b></dt>
+
+<dd>
+In order to combine two programs (or substantial parts of them) into a
+larger work, you need to have permission to use both programs in this way.
+If the two programs' licenses permit this, they are compatible. If there is
+no way to satisfy both licenses at once, they are incompatible.
+<p>
+For some licenses, the way in which the combination is made may affect
+whether they are compatible—for instance, they may allow linking two
+modules together, but not allow merging their code into one module.</p>
+<p>
+Just to install two separate programs in the same system, it is not
+necessary that their licenses be compatible, because this does not combine
+them into a larger work.</p>
+</dd>
+
+<dt><b><a href="#TOCWhatDoesCompatMean" name="WhatDoesCompatMean">What does it
+mean to say a license is “compatible with the GPL”.</a></b></dt>
+
+<dd>
+It means that the other license and the GNU GPL are compatible; you can
+combine code released under the other license with code released under the
+GNU GPL in one larger program.
+<p>
+The GPL permits such a combination provided it is released under the GNU
+GPL. The other license is compatible with the GPL if it permits this too.
+</p></dd>
+
+
+<dt><b><a href="#TOCFSWithNFLibs" name="FSWithNFLibs">Can I write free software
+that uses non-free libraries?</a></b></dt>
+
+<dd>
+If you do this, your program won't be fully usable in a free environment. If
+your program depends on a non-free library to do a certain job, it cannot do
+that job in the Free World. If it depends on a non-free library to run at
+all, it cannot be part of a free operating system such as GNU; it is
+entirely off limits to the Free World.
+<p>
+So please consider: can you find a way to get the job done without using
+this library? Can you write a free replacement for that library?</p>
+<p>
+If the program is already written using the non-free library, perhaps it is
+too late to change the decision. You may as well release the program as it
+stands, rather than not release it. But please mention in the README that
+the need for the non-free library is a drawback, and suggest the task of
+changing the program so that it does the same job without the non-free
+library. Please suggest that anyone who thinks of doing substantial further
+work on the program first free it from dependence on the non-free library.</p>
+<p>
+Note that there may also be legal issues with combining certain non-free
+libraries with GPL-covered Free Software. Please see <a
+href="#GPLIncompatibleLibs">the question on GPL software with
+GPL-incompatible libraries</a> for more information.
+</p></dd>
+
+
+<dt><b><a href="#TOCGPLIncompatibleLibs" name="GPLIncompatibleLibs">What legal
+issues come up if I use GPL-incompatible libraries with GPL
+software?</a></b></dt>
+
+<dd>
+If the libraries that you link with fall within the following exception in
+the GPL:
+<blockquote><p>
+ However, as a special exception, the source code distributed need not
+include anything that is normally distributed (in either source or binary
+form) with the major components (compiler, kernel, and so on) of the
+operating system on which the executable runs, unless that component itself
+accompanies the executable.
+</p></blockquote>
+<p>
+then you don't have to do anything special to use them; the requirement to
+distribute source code for the whole program does not include those
+libraries, even if you distribute a linked executable containing them.
+Thus, if the libraries you need come with major parts of a proprietary
+operating system, the GPL says people can link your program with them
+without any conditions.
+</p><p>
+If you want your program to link against a library not covered by that
+exception, you need to add your own exception, wholly outside of the
+GPL. This copyright notice and license notice give permission to link with
+the program FOO:</p>
+
+<blockquote><p>
+ Copyright (C) yyyy <name of copyright holder>
+</p><p>
+ This program is free software; you can redistribute it and/or modify it
+under the terms of the GNU General Public License as published by the Free
+Software Foundation; either version 2 of the License, or (at your option)
+any later version.
+</p><p>
+ This program is distributed in the hope that it will be useful, but WITHOUT
+ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
+FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for
+more details.
+</p><p>
+ You should have received a copy of the GNU General Public License along
with
+this program; if not, write to the Free Software Foundation, Inc., 51
+Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
+</p>
+
+<p>Linking ABC statically or dynamically with other modules is making a
+combined work based on ABC. Thus, the terms and conditions of the GNU
+General Public License cover the whole combination.</p>
+
+<p>In addition, as a special exception, the copyright holders of ABC give you
+permission to combine ABC program with free software programs or libraries
+that are released under the GNU LGPL and with code included in the standard
+release of DEF under the XYZ license (or modified versions of such code,
+with unchanged license). You may copy and distribute such a system
+following the terms of the GNU GPL for ABC and the licenses of the other
+code concerned, provided that you include the source code of that other code
+when and as the GNU GPL requires distribution of source code.</p>
+
+<p>Note that people who make modified versions of ABC are not obligated to
+grant this special exception for their modified versions; it is their choice
+whether to do so. The GNU General Public License gives permission to
+release a modified version without this exception; this exception also makes
+it possible to release a modified version which carries forward this
+exception.</p>
+
+</blockquote>
+<p>
+You should put this text in each file to which the exception applies.
+</p><p>
+Only the copyright holders for the program can legally authorize this
+exception. If you wrote the whole program yourself, then assuming your
+employer or school does not claim the copyright, you are the copyright
+holder—so you can authorize the exception. But if you want to use
+parts of other GPL-covered programs by other authors in your code, you
+cannot authorize the exception for them. You have to get the approval of the
+copyright holders of those programs.
+</p><p>
+When other people modify the program, they do not have to make the same
+exception for their code—it is their choice whether to do so.
+</p><p>
+If the libraries you intend to link with are non-free, please also see <a
+href="#FSWithNFLibs">the section on writing Free Software which uses
+non-free libraries</a>.
+</p></dd>
+
+<dt><b><a href="#TOCHowIGetCopyright" name="HowIGetCopyright">How do I get a
+copyright on my program in order to release it under the GPL?</a></b></dt>
+
+<dd>
+Under the Berne Convention, everything written is automatically copyrighted
+from whenever it is put in fixed form. So you don't have to do anything to
+“get” the copyright on what you write—as long as nobody
+else can claim to own your work.
+<p>
+However, registering the copyright in the US is a very good idea. It will
+give you more clout in dealing with an infringer in the US.</p>
+<p>
+The case when someone else might possibly claim the copyright is if you are
+an employee or student; then the employer or the school might claim you did
+the job for them and that the copyright belongs to them. Whether they would
+have a valid claim would depend on circumstances such as the laws of the
+place where you live, and on your employment contract and what sort of work
+you do. It is best to consult a lawyer if there is any possible doubt.</p>
+<p>
+If you think that the employer or school might have a claim, you can resolve
+the problem clearly by getting a copyright disclaimer signed by a suitably
+authorized officer of the company or school. (Your immediate boss or a
+professor is usually NOT authorized to sign such a disclaimer.)
+</p></dd>
+
+<dt><b><a href="#TOCWhatIfSchool" name="WhatIfSchool">What if my school might
+want to make my program into its own proprietary software product?</a></b></dt>
+
+<dd>
+Many universities nowadays try to raise funds by restricting the use of the
+knowledge and information they develop, in effect behaving little different
+from commercial businesses. (See “The Kept University”,
+Atlantic Monthly, March 2000, for a general discussion of this problem and
+its effects.)
+<p>
+If you see any chance that your school might refuse to allow your program to
+be released as free software, it is best to raise the issue at the earliest
+possible stage. The closer the program is to working usefully, the more
+temptation the administration might feel to take it from you and finish it
+without you. At an earlier stage, you have more leverage.</p>
+<p>
+So we recommend that you approach them when the program is only half-done,
+saying, “If you will agree to releasing this as free software, I will
+finish it.” Don't think of this as a bluff. To prevail, you must have
+the courage to say, “My program will have liberty, or never be
+born.”
+</p></dd>
+
+<dt><b><a href="#TOCCouldYouHelpApplyGPL" name="CouldYouHelpApplyGPL">Could you
+give me step by step instructions on how to apply the GPL to my
+program?</a></b></dt>
+
+<dd>
+See the page of <a href="/licenses/gpl-howto.html"> GPL instructions</a>.
+<p></p></dd>
+
+<dt><b><a href="#TOCHeardOtherLicense" name="HeardOtherLicense">I heard that
+someone got a copy of a GPL'ed program under another license. Is this
+possible?</a></b></dt>
+
+<dd>
+The GNU GPL does not give users permission to attach other licenses to the
+program. But the copyright holder for a program can release it under
+several different licenses in parallel. One of them may be the GNU GPL.
+<p>
+The license that comes in your copy, assuming it was put in by the copyright
+holder and that you got the copy legitimately, is the license that applies
+to your copy.
+</p></dd>
+
+<dt><b><a href="#TOCReleaseUnderGPLAndNF" name="ReleaseUnderGPLAndNF">I would
+like to release a program I wrote under the GNU GPL, but I would like to use
+the same code in non-free programs.</a></b></dt>
+
+<dd>
+To release a non-free program is always ethically tainted, but legally there
+is no obstacle to your doing this. If you are the copyright holder for the
+code, you can release it under various different non-exclusive licenses at
+various times.
+<p></p></dd>
+
+<dt><b><a href="#TOCDeveloperViolate" name="DeveloperViolate">Is the developer
+of a GPL-covered program bound by the GPL? Could the developer's actions
+ever be a violation of the GPL?</a></b></dt>
+
+<dd>
+Strictly speaking, the GPL is a license from the developer for others to
+use, distribute and change the program. The developer itself is not bound
+by it, so no matter what the developer does, this is not a
+“violation” of the GPL.
+<p>
+However, if the developer does something that would violate the GPL if done
+by someone else, the developer will surely lose moral standing in the
+community.
+</p></dd>
+
+<dt><b><a href="#TOCCanDeveloperThirdParty" name="CanDeveloperThirdParty">Can
+the developer of a program who distributed it under the GPL later license it
+to another party for exclusive use?</a></b></dt>
+
+<dd>
+No, because the public already has the right to use the program under the
+GPL, and this right cannot be withdrawn.
+<p></p></dd>
+
+<dt><b><a href="#TOCCanIUseGPLToolsForNF" name="CanIUseGPLToolsForNF">Can I use
+GPL-covered editors such as GNU Emacs to develop non-free programs? Can I
+use GPL-covered tools such as GCC to compile them?</a></b></dt>
+
+<dd>
+Yes, because the copyright on the editors and tools does not cover the code
+you write. Using them does not place any restrictions, legally, on the
+license you use for your code.
+<p>
+Some programs copy parts of themselves into the output for technical
+reasons—for example, Bison copies a standard parser program into its
+output file. In such cases, the copied text in the output is covered by the
+same license that covers it in the source code. Meanwhile, the part of the
+output which is derived from the program's input inherits the copyright
+status of the input.</p>
+<p>
+As it happens, Bison can also be used to develop non-free programs. This is
+because we decided to explicitly permit the use of the Bison standard parser
+program in Bison output files without restriction. We made the decision
+because there were other tools comparable to Bison which already permitted
+use for non-free programs.
+</p></dd>
+
+<dt><b><a href="#TOCGPLFairUse" name="GPLFairUse">Do I have “fair
+use” rights in using the source code of a GPL-covered
program?</a></b></dt>
+
+<dd>
+Yes, you do. “Fair use” is use that is allowed without any
+special permission. Since you don't need the developers' permission for
+such use, you can do it regardless of what the developers said about
+it—in the license or elsewhere, whether that license be the GNU GPL or
+any other free software license.
+<p>
+Note, however, that there is no world-wide principle of fair use; what kinds
+of use are considered “fair” varies from country to country.
+</p></dd>
+
+<dt><b><a href="#TOCGPLUSGov" name="GPLUSGov">Can the US Government release a
+program under the GNU GPL?</a></b></dt>
+<dd>
+If the program is written by US federal government employees in the course
+of their employment, it is in the public domain, which means it is not
+copyrighted. Since the GNU GPL is based on copyright, such a program cannot
+be released under the GNU GPL. (It can still be <a
+href="/philosophy/free-sw.html"> free software</a>, however; a public domain
+program is free.)
+<p>
+However, when a US federal government agency uses contractors to develop
+software, that is a different situation. The contract can require the
+contractor to release it under the GNU GPL. (GNU Ada was developed in this
+way.) Or the contract can assign the copyright to the government agency,
+which can then release the software under the GNU GPL. </p></dd>
+
+<dt><b><a href="#TOCGPLUSGovAdd" name="GPLUSGovAdd">Can the US Government
+release improvements to a GPL-covered program?</a></b></dt>
+<dd>
+Yes. If the improvements are written by US government employees in the
+course of their employment, then the improvements are in the public domain.
+However, the improved version, as a whole, is still covered by the GNU GPL.
+There is no problem in this situation.
+<p>
+If the US government uses contractors to do the job, then the improvements
+themselves can be GPL-covered.
+</p></dd>
+
+<dt><b><a href="#TOCGPLOutput" name="GPLOutput">Is there some way that I can
GPL
+the output people get from use of my program? For example, if my program is
+used to develop hardware designs, can I require that these designs must be
+free?</a></b></dt>
+
+<dd>
+In general this is legally impossible; copyright law does not give you any
+say in the use of the output people make from their data using your
+program. If the user uses your program to enter or convert his own data,
+the copyright on the output belongs to him, not you. More generally, when a
+program translates its input into some other form, the copyright status of
+the output inherits that of the input it was generated from.
+<p>
+So the only way you have a say in the use of the output is if substantial
+parts of the output are copied (more or less) from text in your program.
+For instance, part of the output of Bison (see above) would be covered by
+the GNU GPL, if we had not made an exception in this specific case.</p>
+<p>
+You could artificially make a program copy certain text into its output even
+if there is no technical reason to do so. But if that copied text serves no
+practical purpose, the user could simply delete that text from the output
+and use only the rest. Then he would not have to obey the conditions on
+redistribution of the copied text.
+</p></dd>
+
+<dt><b><a href="#TOCWhatCaseIsOutputGPL" name="WhatCaseIsOutputGPL">In what
+cases is the output of a GPL program covered by the GPL too?</a></b></dt>
+
+<dd>
+Only when the program copies part of itself into the output.
+<p></p></dd>
+
+<dt><b><a href="#TOCGPLModuleLicense" name="GPLModuleLicense">If I add a module
+to a GPL-covered program, do I have to use the GPL as the license for my
+module?</a></b></dt>
+
+<dd>
+The GPL says that the whole combined program has to be released under the
+GPL. So your module has to be available for use under the GPL.
+<p>
+But you can give additional permission for the use of your code. You can,
+if you wish, release your program under a license which is more lax than the
+GPL but compatible with the GPL. The <a
+href="/licenses/license-list.html">license list page</a> gives a partial
+list of GPL-compatible licenses.
+</p></dd>
+
+<dt><b><a href="#TOCIfLibraryIsGPL" name="IfLibraryIsGPL">If a library is
+released under the GPL (not the LGPL), does that mean that any program which
+uses it has to be under the GPL?</a></b></dt>
+
+<dd>
+Yes, because the program as it is actually run includes the library.
+<p></p></dd>
+
+<dt><b><a href="#TOCIfInterpreterIsGPL" name="IfInterpreterIsGPL">If a
+programming language interpreter is released under the GPL, does that mean
+programs written to be interpreted by it must be under GPL-compatible
+licenses?</a></b></dt>
+
+<dd>
+When the interpreter just interprets a language, the answer is no. The
+interpreted program, to the interpreter, is just data; a free software
+license like the GPL, based on copyright law, cannot limit what data you use
+the interpreter on. You can run it on any data (interpreted program), any
+way you like, and there are no requirements about licensing that data to
+anyone.
+<p>However, when the interpreter is extended to provide “bindings”
+to other facilities (often, but not necessarily, libraries), the interpreted
+program is effectively linked to the facilities it uses through these
+bindings. So if these facilities are released under the GPL, the interpreted
+program that uses them must be released in a GPL-compatible way. The JNI or
+Java Native Interface is an example of such a binding mechanism; libraries
+that are accessed in this way are linked dynamically with the Java programs
+that call them. These libraries are also linked with the interpreter. If
+the interpreter is linked statically with these libraries, or if it is
+designed to <a href="#GPLPluginsInNF"> link dynamically with these specific
+libraries</a>, then it too needs to be released in a GPL-compatible way.</p>
+<p>
+Another similar and very common case is to provide libraries with the
+interpreter which are themselves interpreted. For instance, Perl comes with
+many Perl modules, and a Java implementation comes with many Java classes.
+These libraries and the programs that call them are always dynamically
+linked together.</p>
+<p>
+A consequence is that if you choose to use GPL'd Perl modules or Java
+classes in your program, you must release the program in a GPL-compatible
+way, regardless of the license used in the Perl or Java interpreter that the
+combined Perl or Java program will run on.
+</p></dd>
+
+<dt><b><a href="#TOCWindowsRuntimeAndGPL" name="WindowsRuntimeAndGPL">I'm
+writing a Windows application with Microsoft Visual C++ (or Visual Basic)
+and I will be releasing it under the GPL. Is dynamically linking my program
+with the Visual C++ (or Visual Basic) run-time library permitted under the
+GPL?</a></b></dt>
+
+<dd>
+The GPL permits this because that run-time library normally accompanies the
+compiler or interpreter you are using. So it falls under the exception in
+GPL section 3.
+<p>
+That doesn't mean it is a good idea to write the program so that it only
+runs on Windows. Doing so results in a program that is free software but <a
+href="/philosophy/java-trap.html">“trapped”</a> (in this case,
+trapped by Windows instead of by Java, but the effect is the same).
+(Historical note: As of December 2006 Sun is in the middle of <a
+href="http://www.fsf.org/news/fsf-welcomes-gpl-java.html";>rereleasing its
+Java platform under GNU GPL</a>.)
+</p></dd>
+
+<dt><b><a href="#TOCOrigBSD" name="OrigBSD">Why is the original BSD license
+incompatible with the GPL?</a></b></dt>
+
+<dd>
+Because it imposes a specific requirement that is not in the GPL; namely,
+the requirement on advertisements of the program. The GPL states:
+<pre>
+ You may not impose any further restrictions on the recipients' exercise
+ of the rights granted herein.
+</pre>
+<p>
+The advertising clause provides just such a further restriction, and thus is
+GPL-incompatible.</p>
+<p>
+The revised BSD license does not have the advertising clause, which
+eliminates the problem.
+</p></dd>
+
+<dt><b><a href="#TOCGPLAndPlugins" name="GPLAndPlugins">If a program released
+under the GPL uses plug-ins, what are the requirements for the licenses of a
+plug-in?</a></b></dt>
+
+<dd>
+It depends on how the program invokes its plug-ins. If the program uses
+fork and exec to invoke plug-ins, then the plug-ins are separate programs,
+so the license for the main program makes no requirements for them.
+<p>
+If the program dynamically links plug-ins, and they make function calls to
+each other and share data structures, we believe they form a single program,
+which must be treated as an extension of both the main program and the
+plug-ins. This means the plug-ins must be released under the GPL or a
+GPL-compatible free software license, and that the terms of the GPL must be
+followed when those plug-ins are distributed.</p>
+<p>
+If the program dynamically links plug-ins, but the communication between
+them is limited to invoking the ‘main’ function of the plug-in
+with some options and waiting for it to return, that is a borderline case.
+</p></dd>
+
+<dt><b><a href="#TOCGPLPluginsInNF" name="GPLPluginsInNF">Can I apply the GPL
+when writing a plug-in for a non-free program?</a></b></dt>
+
+<dd>
+If the program uses fork and exec to invoke plug-ins, then the plug-ins are
+separate programs, so the license for the main program makes no requirements
+for them. So you can use the GPL for a plug-in, and there are no special
+requirements.
+<p>
+If the program dynamically links plug-ins, and they make function calls to
+each other and share data structures, we believe they form a single program,
+which must be treated as an extension of both the main program and the
+plug-ins. This means that combination of the GPL-covered plug-in with the
+non-free main program would violate the GPL. However, you can resolve that
+legal problem by adding an exception to your plug-in's license, giving
+permission to link it with the non-free main program.</p>
+<p>
+See also the question <a href="#FSWithNFLibs">I am writing free software
+that uses a non-free library.</a>
+</p></dd>
+
+<dt><b><a href="#TOCNFUseGPLPlugins" name="NFUseGPLPlugins">Can I release a
+non-free program that's designed to load a GPL-covered plug-in?</a></b></dt>
+
+<dd>
+It depends on how the program invokes its plug-ins. If the program uses
+fork and exec to invoke plug-ins, then the plug-ins are separate programs,
+so the license of the plug-in makes no requirements about the main program.
+<p>
+If the program dynamically links plug-ins, and they make function calls to
+each other and share data structures, we believe they form a single program,
+which must be treated as an extension of both the main program and the
+plug-ins. In order to use the GPL-covered plug-ins, the main program must
+be released under the GPL or a GPL-compatible free software license, and
+that the terms of the GPL must be followed when the main program is
+distributed for use with these plug-ins.</p>
+<p>
+If the program dynamically links plug-ins, but the communication between
+them is limited to invoking the ‘main’ function of the plug-in
+with some options and waiting for it to return, that is a borderline case.</p>
+<p>
+See also the question <a href="#FSWithNFLibs">I am writing free software
+that uses a non-free library.</a>
+</p></dd>
+
+<dt><b><a href="#TOCLinkingWithGPL" name="LinkingWithGPL">You have a GPL'ed
+program that I'd like to link with my code to build a proprietary program.
+Does the fact that I link with your program mean I have to GPL my
+program?</a></b></dt>
+
+<dd>
+Yes.
+<p></p></dd>
+
+<dt><b><a href="#TOCSwitchToLGPL" name="SwitchToLGPL">If so, is there any
chance
+I could get a license of your program under the Lesser GPL?</a></b></dt>
+
+<dd>
+You can ask, but most authors will stand firm and say no. The idea of the
+GPL is that if you want to include our code in your program, your program
+must also be free software. It is supposed to put pressure on you to
+release your program in a way that makes it part of our community.
+<p>
+You always have the legal alternative of not using our code.
+</p></dd>
+
+<dt><b><a href="#TOCLinkingOverControlledInterface"
+name="LinkingOverControlledInterface">How can I allow linking of proprietary
+modules with my GPL-covered library under a controlled interface
+only?</a></b></dt>
+
+<dd>
+Add this text to the license notice of each file in the package, at the end
+of the text that says the file is distributed under the GNU GPL:
+<pre>
+
+Linking ABC statically or dynamically with other modules is making
+a combined work based on ABC. Thus, the terms and conditions of
+the GNU General Public License cover the whole combination.
+
+In addition, as a special exception, the copyright holders of ABC give
+you permission to combine ABC program with free software programs or
+libraries that are released under the GNU LGPL and with independent
+modules that communicate with ABC solely through the ABCDEF interface.
+You may copy and distribute such a system following the terms of the
+GNU GPL for ABC and the licenses of the other code concerned, provided
+that you include the source code of that other code when and as the
+GNU GPL requires distribution of source code.
+
+Note that people who make modified versions of ABC are not obligated
+to grant this special exception for their modified versions; it is
+their choice whether to do so. The GNU General Public License gives
+permission to release a modified version without this exception; this
+exception also makes it possible to release a modified version which
+carries forward this exception.
+
+</pre>
+<p>
+Only the copyright holders for the program can legally authorize this
+exception. If you wrote the whole program yourself, then assuming your
+employer or school does not claim the copyright, you are the copyright
+holder—so you can authorize the exception. But if you want to use
+parts of other GPL-covered programs by other authors in your code, you
+cannot authorize the exception for them. You have to get the approval of the
+copyright holders of those programs.
+</p><p></p></dd>
+
+<dt><b><a href="#TOCManyDifferentLicenses" name="ManyDifferentLicenses">I have
+written an application that links with many different components, that have
+different licenses. I am very confused as to what licensing requirements
+are placed on my program. Can you please tell me what licenses I may
+use?</a></b></dt>
+
+<dd>
+To answer this question, we would need to see a list of each component that
+your program uses, the license of that component, and a brief (a few
+sentences for each should suffice) describing how your library uses that
+component. Two examples would be:
+<ul>
+<li>To make my software work, it must be linked to the FOO library, which is
+available under the Lesser GPL.</li>
+<li>My software makes a system call (with a command line that I built) to run
+the BAR program, which is licensed under “the GPL, with a special
+exception allowing for linking with QUUX”.</li>
+</ul>
+<p></p></dd>
+
+<dt><b><a href="#TOCMereAggregation" name="MereAggregation">What is the
+difference between “mere aggregation” and “combining two
+modules into one program”?</a></b></dt>
+
+<dd>
+Mere aggregation of two programs means putting them side by side on the same
+CD-ROM or hard disk. We use this term in the case where they are separate
+programs, not parts of a single program. In this case, if one of the
+programs is covered by the GPL, it has no effect on the other program.
+<p>
+Combining two modules means connecting them together so that they form a
+single larger program. If either part is covered by the GPL, the whole
+combination must also be released under the GPL—if you can't, or
+won't, do that, you may not combine them.</p>
+<p>
+What constitutes combining two parts into one program? This is a legal
+question, which ultimately judges will decide. We believe that a proper
+criterion depends both on the mechanism of communication (exec, pipes, rpc,
+function calls within a shared address space, etc.) and the semantics of
+the communication (what kinds of information are interchanged).</p>
+<p>
+If the modules are included in the same executable file, they are definitely
+combined in one program. If modules are designed to run linked together in
+a shared address space, that almost surely means combining them into one
+program.</p>
+<p>
+By contrast, pipes, sockets and command-line arguments are communication
+mechanisms normally used between two separate programs. So when they are
+used for communication, the modules normally are separate programs. But if
+the semantics of the communication are intimate enough, exchanging complex
+internal data structures, that too could be a basis to consider the two
+parts as combined into a larger program.
+</p></dd>
+
+<dt><b><a href="#TOCAssignCopyright" name="AssignCopyright">Why does the FSF
+require that contributors to FSF-copyrighted programs assign copyright to
+the FSF? If I hold copyright on a GPL'ed program, should I do this, too? If
+so, how?</a></b></dt>
+
+<dd>
+Our lawyers have told us that to be in the <a
+href="/licenses/why-assign.html">best position to enforce the GPL</a> in
+court against violators, we should keep the copyright status of the program
+as simple as possible. We do this by asking each contributor to either
+assign the copyright on his contribution to the FSF, or disclaim copyright
+on it and thus put it in the public domain.
+<p>
+We also ask individual contributors to get copyright disclaimers from their
+employers (if any) so that we can be sure those employers won't claim to own
+the contributions.</p>
+<p>
+Of course, if all the contributors put their code in the public domain,
+there is no copyright with which to enforce the GPL. So we encourage people
+to assign copyright on large code contributions, and only put small changes
+in the public domain.</p>
+<p>
+If you want to make an effort to enforce the GPL on your program, it is
+probably a good idea for you to follow a similar policy. Please contact <a
+href="mailto:address@hidden";><address@hidden></a> if you want
+more information.
+</p></dd>
+
+<dt><b><a href="#TOCModifyGPL" name="ModifyGPL">Can I modify the GPL and make a
+modified license?</a></b></dt>
+
+<dd>
+You can use the GPL terms (possibly modified) in another license provided
+that you call your license by another name and do not include the GPL
+preamble, and provided you modify the instructions-for-use at the end enough
+to make it clearly different in wording and not mention GNU (though the
+actual procedure you describe may be similar).
+<p>
+If you want to use our preamble in a modified license, please write to <a
+href="mailto:address@hidden";><address@hidden></a> for
+permission. For this purpose we would want to check the actual license
+requirements to see if we approve of them.</p>
+<p>
+Although we will not raise legal objections to your making a modified
+license in this way, we hope you will think twice and not do it. Such a
+modified license is almost certainly <a href="#WhatIsCompatible">
+incompatible with the GNU GPL</a>, and that incompatibility blocks useful
+combinations of modules. The mere proliferation of different free software
+licenses is a burden in and of itself.
+</p></dd>
+
+<dt><b><a href="#TOCGPLCommercially" name="GPLCommercially">If I use a piece of
+software that has been obtained under the GNU GPL, am I allowed to modify
+the original code into a new program, then distribute and sell that new
+program commercially?</a></b></dt>
+
+<dd>
+You are allowed to sell copies of the modified program commercially, but
+only under the terms of the GNU GPL. Thus, for instance, you must make the
+source code available to the users of the program as described in the GPL,
+and they must be allowed to redistribute and modify it as described in the
+GPL.
+<p>
+These requirements are the condition for including the GPL-covered code you
+received in a program of your own.
+</p></dd>
+
+
+<dt><b><a href="#TOCGPLOtherThanSoftware" name="GPLOtherThanSoftware">Can I use
+the GPL for something other than software?</a></b></dt>
+
+<dd>
+You can apply the GPL to any kind of work, as long as it is clear what
+constitutes the “source code” for the work. The GPL defines
+this as the preferred form of the work for making changes in it.
+<p>
+However, for manuals and textbooks, or more generally any sort of work that
+is meant to teach a subject, we recommend using the GFDL rather than the
+GPL.
+</p></dd>
+
+
+<dt><b><a href="#TOCLGPLJava" name="LGPLJava">How does the LGPL work with
+Java?</a></b></dt>
+
+<dd>
+
+<p><a href="/licenses/lgpl-java.html">See this article for details.</a> It
+works as designed, intended, and expected.
+</p></dd>
+
+<dt><b><a href="#TOCConsider" name="Consider">Consider this situation: 1. X
+releases V1 of a project under the GPL. 2. Y contributes to the development
+of V2 with changes and new code based on V1. 3. X wants to convert V2 to a
+non-GPL license. Does X need Y's permission?</a></b></dt>
+
+<dd>
+Yes. Y was required to release its version under the GNU GPL, as a
+consequence of basing it on X's version V1. Nothing required Y to agree to
+any other license for its code. Therefore, X must get Y's permission before
+releasing that code under another license.
+<p></p></dd>
+
+
+<dt><b><a href="#TOCGPLInProprietarySystem" name="GPLInProprietarySystem">I'd
+like to incorporate GPL-covered software in my proprietary system. Can I do
+this?</a></b></dt>
+
+<dd>
+You cannot incorporate GPL-covered software in a proprietary system. The
+goal of the GPL is to grant everyone the freedom to copy, redistribute,
+understand, and modify a program. If you could incorporate GPL-covered
+software into a non-free system, it would have the effect of making the
+GPL-covered software non-free too.
+<p>
+A system incorporating a GPL-covered program is an extended version of that
+program. The GPL says that any extended version of the program must be
+released under the GPL if it is released at all. This is for two reasons:
+to make sure that users who get the software get the freedom they should
+have, and to encourage people to give back improvements that they make.</p>
+<p>
+However, in many cases you can distribute the GPL-covered software alongside
+your proprietary system. To do this validly, you must make sure that the
+free and non-free programs communicate at arms length, that they are not
+combined in a way that would make them effectively a single program.</p>
+<p>
+The difference between this and “incorporating” the GPL-covered
+software is partly a matter of substance and partly form. The substantive
+part is this: if the two programs are combined so that they become
+effectively two parts of one program, then you can't treat them as two
+separate programs. So the GPL has to cover the whole thing.</p>
+<p>
+If the two programs remain well separated, like the compiler and the kernel,
+or like an editor and a shell, then you can treat them as two separate
+programs—but you have to do it properly. The issue is simply one of
+form: how you describe what you are doing. Why do we care about this?
+Because we want to make sure the users clearly understand the free status of
+the GPL-covered software in the collection.</p>
+<p>
+If people were to distribute GPL-covered software calling it “part
+of” a system that users know is partly proprietary, users might be
+uncertain of their rights regarding the GPL-covered software. But if they
+know that what they have received is a free program plus another program,
+side by side, their rights will be clear.
+</p></dd>
+
+<dt><b><a href="#TOCGPLWrapper" name="GPLWrapper"> I'd like to incorporate
+GPL-covered software in my proprietary system. Can I do this by putting a
+“wrapper” module, under a GPL-compatible lax permissive license
+(such as the X11 license) in between the GPL-covered part and the
+proprietary part?</a></b></dt>
+
+<dd><p>No. The X11 license is compatible with the GPL, so you can add a
module to
+the GPL-covered program and put it under the X11 license. But if you were
+to incorporate them both in a larger program, that whole would include the
+GPL-covered part, so it would have to be licensed <em> as a whole </em>
+under the GNU GPL.</p>
+
+<p>The fact that proprietary module A communicates with GPL-covered module C
+only through X11-licensed module B is legally irrelevant; what matters is
+the fact that module C is included in the whole.
+</p></dd>
+
+<dt><b><a href="#TOCLibGCCException" name="LibGCCException"> Does the libstdc++
+exception permit dynamic linking?</a></b></dt>
+
+<dd><p>Yes. The intent of the exception is to allow people to compile
proprietary
+software using gcc.</p></dd>
+
+<dt><b><a href="#TOCMoneyGuzzlerInc" name="MoneyGuzzlerInc">I'd like to modify
+GPL-covered programs and link them with the portability libraries from Money
+Guzzler Inc. I cannot distribute the source code for these libraries, so
+any user who wanted to change these versions would have to obtained those
+libraries separately. Why doesn't the GPL permit this?</a></b></dt>
+
+<dd>
+There are two reasons for this.
+<p>
+First, a general one. If we permitted company A to make a proprietary file,
+and company B to distribute GPL-covered software linked with that file, the
+effect would be to make a hole in the GPL big enough to drive a truck
+through. This would be carte blanche for withholding the source code for
+all sorts of modifications and extensions to GPL-covered software.</p>
+<p>
+Giving all users access to the source code is one of our main goals, so this
+consequence is definitely something we want to avoid.</p>
+<p>
+More concretely, the versions of the programs linked with the Money Guzzler
+libraries would not really be free software as we understand the
+term—they would not come with full source code that enables users to
+change and recompile the program.
+</p></dd>
+
+<dt><b><a href="#TOCGPLIncompatibleAlone" name="GPLIncompatibleAlone">If
license
+for a module Q has a requirement that's incompatible with the GPL, but the
+requirement applies only when Q is distributed by itself, not when Q is
+included in a larger program, does that make the license GPL-compatible? Can
+I combine or link Q with a GPL-covered program?</a></b></dt>
+
+<dd>
+If a program P is released under the GPL that means <strong>any and every
+part of it</strong> can be used under the GPL. If you integrate module Q,
+and release the combined program P+Q under the GPL, that means any part of
+P+Q can be used under the GPL. One part of P+Q is Q. So releasing P+Q
+under the GPL says that Q any part of it can be used under the GPL. Putting
+it in other words, a user who obtains P+Q under the GPL can delete P, so
+that just Q remains, still under the GPL.
+<p>
+If the license of module Q permits you to give permission for that, then it
+is GPL-compatible. Otherwise, it is not GPL-compatible.</p>
+<p>
+If the license for Q says in no uncertain terms that you must do certain
+things (not compatible with the GPL) when you redistribute Q on its own,
+then it does not permit you to distribute Q under the GPL. It follows that
+you can't release P+Q under the GPL either. So you cannot link or combine P
+with Q.
+</p></dd>
+
+<dt><b><a href="#TOCModifiedJustBinary" name="ModifiedJustBinary">Can I release
+a modified version of a GPL-covered program in binary form only?</a></b></dt>
+<dd>
+No. The whole point of the GPL is that all modified versions must be <a
+href="/philosophy/free-sw.html"> free software</a>—which means, in
+particular, that the source code of the modified version is available to the
+users.
+<p></p></dd>
+
+
+<dt><b><a href="#TOCUnchangedJustBinary" name="UnchangedJustBinary">I
downloaded
+just the binary from the net. If I distribute copies, do I have to get the
+source and distribute that too?</a></b></dt>
+<dd>
+Yes. The general rule is, if you distribute binaries, you must distribute
+the complete corresponding source code too. The exception for the case
+where you received a written offer for source code is quite limited.
+<p></p></dd>
+
+<dt><b><a href="#TOCDistributeWithSourceOnInternet"
+name="DistributeWithSourceOnInternet">I want to distribute binaries via
+physical media without accompanying sources. Can I provide source code by
+FTP instead of by mail order?</a></b></dt>
+
+<dd>
+You're supposed to provide the source code by mail-order on a physical
+medium, if someone orders it. You are welcome to offer people a way to copy
+the corresponding source code by FTP, in addition to the mail-order option,
+but FTP access to the source is not sufficient to satisfy section 3 of the
+GPL.
+<p>
+When a user orders the source, you have to make sure to get the source to
+that user. If a particular user can conveniently get the source from you by
+anonymous FTP, fine—that does the job. But not every user can do such
+a download. The rest of the users are just as entitled to get the source
+code from you, which means you must be prepared to send it to them by post.</p>
+<p>
+If the FTP access is convenient enough, perhaps no one will choose to
+mail-order a copy. If so, you will never have to ship one. But you cannot
+assume that.</p>
+<p>
+Of course, it's easiest to just send the source with the binary in the first
+place.
+</p>
+<p>If you distribute binaries via FTP, <a href="#AnonFTPAndSendSource">you
+should distribute source via FTP.</a></p>
+
+</dd>
+
+<dt><b><a href="#TOCRedistributedBinariesGetSource"
+name="RedistributedBinariesGetSource">My friend got a GPL-covered binary
+with an offer to supply source, and made a copy for me. Can I use the offer
+myself to obtain the source?</a></b></dt>
+
+<dd>
+Yes, you can. The offer must be open to everyone who has a copy of the
+binary that it accompanies. This is why the GPL says your friend must give
+you a copy of the offer along with a copy of the binary—so you can
+take advantage of it.
+<p></p></dd>
+
+<dt><b><a href="#TOCSourceAndBinaryOnDifferentSites"
+name="SourceAndBinaryOnDifferentSites">Can I put the binaries on my Internet
+server and put the source on a different Internet site?</a></b></dt>
+
+<dd>
+The GPL says you must offer access to copy the source code “from the
+same place”; that is, next to the binaries. However, if you make
+arrangements with another site to keep the necessary source code available,
+and put a link or cross-reference to the source code next to the binaries,
+we think that qualifies as “from the same place”.
+<p>
+Note, however, that it is not enough to find some site that happens to have
+the appropriate source code today, and tell people to look there. Tomorrow
+that site may have deleted that source code, or simply replaced it with a
+newer version of the same program. Then you would no longer be complying
+with the GPL requirements. To make a reasonable effort to comply, you need
+to make a positive arrangement with the other site, and thus ensure that the
+source will be available there for as long as you keep the binaries
+available.
+</p></dd>
+
+<dt><b><a href="#TOCDistributeExtendedBinary" name="DistributeExtendedBinary">I
+want to distribute an extended version of a GPL-covered program in binary
+form. Is it enough to distribute the source for the original
+version?</a></b></dt>
+
+<dd>
+No, you must supply the source code that corresponds to the binary.
+Corresponding source means the source from which users can rebuild the same
+binary.
+<p>
+Part of the idea of free software is that users should have access to the
+source code for <strong>the programs they use</strong>. Those using your
+version should have access to the source code for your version.</p>
+<p>
+A major goal of the GPL is to build up the Free World by making sure that
+improvement to a free program are themselves free. If you release an
+improved version of a GPL-covered program, you must release the improved
+source code under the GPL.
+</p></dd>
+
+<dt><b><a href="#TOCDistributingSourceIsInconvenient"
+name="DistributingSourceIsInconvenient">I want to distribute binaries, but
+distributing complete source is inconvenient. Is it ok if I give users the
+diffs from the “standard” version along with the
+binaries?</a></b></dt>
+
+<dd>
+This is a well-meaning request, but this method of providing the source
+doesn't really do the job.
+<p>
+A user that wants the source a year from now may be unable to get the proper
+version from another site at that time. The standard distribution site may
+have a newer version, but the same diffs probably won't work with that
+version.</p>
+<p>
+So you need to provide complete sources, not just diffs, with the binaries.
+</p></dd>
+
+<dt><b><a href="#TOCAnonFTPAndSendSource" name="AnonFTPAndSendSources">I want
to
+make binaries available for anonymous FTP, but send sources only to people
+who order them.</a></b></dt>
+
+<dd>
+<p>If you want to distribute binaries by anonymous FTP, you still have to
+provide source through one of the options listed in section 3. This should
+not be hard. You can provide a written offer for source if you want;
+section 3(b) allows this. But if you can find a site to distribute your
+program, you can surely find one that has room for the sources.
+</p><p>No matter how you distribute the source, the sources you provide must
+correspond exactly to the binaries. In particular, you must make sure they
+are for the same version of the program—not an older version and not a
+newer version.</p>
+<p>
+You can make the sources and binaries available on different machines,
+provided they are equally easy to get to, and provided that you have
+information next to the binaries saying where to find the sources.
+</p></dd>
+
+<dt><b><a href="#TOCHowCanIMakeSureEachDownloadGetsSource"
+name="HowCanIMakeSureEachDownloadGetsSource">How can I make sure each user
+who downloads the binaries also gets the source?</a></b></dt>
+
+<dd>
+You don't have to make sure of this. As long as you make the source and
+binaries available so that the users can see what's available and take what
+they want, you have done what is required of you. It is up to the user
+whether to download the source.
+<p>
+Our requirements for redistributors are intended to make sure the users can
+get the source code, not to force users to download the source code even if
+they don't want it.
+</p></dd>
+
+<dt><b><a href="#TOCUnreleasedMods" name="UnreleasedMods">A company is running
a
+modified version of a GPL'ed program on a web site. Does the GPL say they
+must release their modified sources?</a></b></dt>
+
+<dd>
+The GPL permits anyone to make a modified version and use it without ever
+distributing it to others. What this company is doing is a special case of
+that. Therefore, the company does not have to release the modified sources.
+<p>
+It is essential for people to have the freedom to make modifications and use
+them privately, without ever publishing those modifications. However,
+putting the program on a server machine for the public to talk to is hardly
+“private” use, so it would be legitimate to require release of
+the source code in that special case. We are thinking about doing something
+like this in GPL version 3, but we don't have precise wording in mind yet.</p>
+<p>
+In the mean time, you might want to use the <a
+href="http://www.affero.org/oagpl.html";>Affero GPL</a> for programs designed
+for network server use.
+</p></dd>
+
+<dt><b><a href="#TOCInternalDistribution" name="InternalDistribution">Is making
+and using multiple copies within one organization or company
+“distribution”?</a></b></dt>
+
+<dd>
+No, in that case the organization is just making the copies for itself. As
+a consequence, a company or other organization can develop a modified
+version and install that version through its own facilities, without giving
+the staff permission to release that modified version to outsiders.
+<p>
+However, when the organization transfers copies to other organizations or
+individuals, that is distribution. In particular, providing copies to
+contractors for use off-site is distribution.
+</p></dd>
+
+
+<dt><b><a href="#TOCStolenCopy" name="StolenCopy"> If someone steals a CD
+containing a version of a GPL-covered program, does the GPL give him the
+right to redistribute that version?</a></b></dt>
+
+<dd>
+If the version has been released elsewhere, then the thief probably does
+have the right to make copies and redistribute them under the GPL, but if he
+is imprisoned for stealing the CD he may have to wait until his release
+before doing so.
+<p>
+If the version in question is unpublished and considered by a company to be
+its trade secret, then publishing it may be a violation of trade secret law,
+depending on other circumstances. The GPL does not change that. If the
+company tried to release its version and still treat it as a trade secret,
+that would violate the GPL, but if the company hasn't released this version,
+no such violation has occurred.
+</p></dd>
+
+<dt><b><a href="#TOCTradeSecretRelease" name="TradeSecretRelease">What if a
+company distributes a copy as a trade secret?</a></b></dt>
+<dd>
+If a company distributes a copy to you and claims it is a trade secret, the
+company has violated the GPL and will have to cease distribution. Note how
+this differs from the theft case above; the company does not intentionally
+distribute a copy when a copy is stolen, so in that case the company has not
+violated the GPL.
+<p></p></dd>
+
+<dt><b><a href="#TOCWhySomeGPLAndNotLGPL" name="WhySomeGPLAndNotLGPL">Why are
+some GNU libraries released under the ordinary GPL rather than the Lesser
+GPL?</a></b></dt>
+
+<dd>
+Using the Lesser GPL for any particular library constitutes a retreat for
+free software. It means we partially abandon the attempt to defend the
+users' freedom, and some of the requirements to share what is built on top
+of GPL-covered software. In themselves, those are changes for the worse.
+<p>
+Sometimes a localized retreat is a good strategy. Sometimes, using the LGPL
+for a library might lead to wider use of that library, and thus to more
+improvement for it, wider support for free software, and so on. This could
+be good for free software if it happens to a large extent. But how much
+will this happen? We can only speculate.</p>
+<p>
+It would be nice to try out the LGPL on each library for a while, see
+whether it helps, and change back to the GPL if the LGPL didn't help. But
+this is not feasible. Once we use the LGPL for a particular library,
+changing back would be difficult.</p>
+<p>
+So we decide which license to use for each library on a case-by-case basis.
+There is a <a href="/licenses/why-not-lgpl.html"> long explanation</a> of
+how we judge the question.
+</p></dd>
+
+<dt><b><a href="#TOCWillYouMakeAnException" name="WillYouMakeAnException">Using
+a certain GNU program under the GPL does not fit our project to make
+proprietary software. Will you make an exception for us? It would mean more
+users of that program.</a></b></dt>
+
+<dd>
+Sorry, we don't make such exceptions. It would not be right.
+<p>
+Maximizing the number of users is not our aim. Rather, we are trying to
+give the crucial freedoms to as many users as possible. In general,
+proprietary software projects hinder rather than help the cause of freedom.</p>
+<p>
+We do occasionally make license exceptions to assist a project which is
+producing free software under a license other than the GPL. However, we
+have to see a good reason why this will advance the cause of free software.</p>
+<p>
+We also do sometimes change the distribution terms of a package, when that
+seems clearly the right way to serve the cause of free software; but we are
+very cautious about this, so you will have to show us very convincing
+reasons.
+</p></dd>
+
+<dt><b><a href="#TOCVersionTwoOrLater" name="VersionTwoOrLater">Why should
+programs say “Version 2 of the GPL or any later
+version”?</a></b></dt>
+
+<dd>
+From time to time, at intervals of years, we change the GPL—sometimes
+to clarify it, sometimes to permit certain kinds of use not previously
+permitted, and sometimes to tighten up a requirement. (The last change was
+in 1991.) Using this “indirect pointer” in each program makes
+it possible for us to change the distribution terms on the entire collection
+of GNU software, when we update the GPL.
+<p>
+If each program lacked the indirect pointer, we would be forced to discuss
+the change at length with numerous copyright holders, which would be a
+virtual impossibility. In practice, the chance of having uniform
+distribution terms for GNU software would be nil.</p>
+<p>
+Suppose a program says “Version 2 of the GPL or any later
+version” and a new version of the GPL is released. If the new GPL
+version gives additional permission, that permission will be available
+immediately to all the users of the program. But if the new GPL version has
+a tighter requirement, it will not restrict use of the current version of
+the program, because it can still be used under GPL version 2. When a
+program says “Version 2 of the GPL or any later version”, users
+will always be permitted to use it, and even change it, according to the
+terms of GPL version 2—even after later versions of the GPL are
+available.</p>
+<p>
+If a tighter requirement in a new version of the GPL need not be obeyed for
+existing software, how is it useful? Once GPL version 3 is available, the
+developers of most GPL-covered programs will release subsequent versions of
+their programs specifying “Version 3 of the GPL or any later
+version”. Then users will have to follow the tighter requirements in
+GPL version 3, for subsequent versions of the program.</p>
+<p>
+However, developers are not obligated to do this; developers can continue
+allowing use of the previous version of the GPL, if that is their
+preference.
+</p></dd>
+
+
+<dt><b><a href="#TOCWhyNotGPLForManuals" name="WhyNotGPLForManuals">Why don't
+you use the GPL for manuals?</a></b></dt>
+
+<dd>
+It is possible to use the GPL for a manual, but the GNU Free Documentation
+License (GFDL) is much better for manuals.
+<p>
+The GPL was designed for programs; it contains lots of complex clauses that
+are crucial for programs, but that would be cumbersome and unnecessary for a
+book or manual. For instance, anyone publishing the book on paper would
+have to either include machine-readable “source code” of the
+book along with each printed copy, or provide a written offer to send the
+“source code” later.</p>
+<p>
+Meanwhile, the GFDL has clauses that help publishers of free manuals make a
+profit from selling copies—cover texts, for instance. The special
+rules for Endorsements sections make it possible to use the GFDL for an
+official standard. This would permit modified versions, but they could not
+be labeled as “the standard”.</p>
+<p>
+Using the GFDL, we permit changes in the text of a manual that covers its
+technical topic. It is important to be able to change the technical parts,
+because people who change a program ought to change the documentation to
+correspond. The freedom to do this is an ethical imperative.</p>
+<p>
+Our manuals also include sections that state our political position about
+free software. We mark these as “invariant”, so that they
+cannot be changed or removed. The GFDL makes provisions for these
+“invariant sections”.
+</p></dd>
+
+
+<dt><b><a href="#TOCFontException" name="FontException">How does the GPL apply
+to fonts?</a></b></dt>
+
+<dd>
+Font licensing is a complex issue which needs serious consideration. The
+following license exception is experimental but approved for general use.
+We welcome suggestions on this subject—please see this <a
+href="http://www.fsf.org/blogs/licensing/20050425novalis";>explanatory
+essay</a> and write to <a
+href="mailto:address@hidden";><address@hidden></a>.
+
+<p>
+To use this exception, add this text to the license notice of each file in
+the package (to the extent possible), at the end of the text that says the
+file is distributed under the GNU GPL:</p>
+<p>
+<tt> As a special exception, if you create a document which uses this font,
+and embed this font or unaltered portions of this font into the document,
+this font does not by itself cause the resulting document to be covered by
+the GNU General Public License. This exception does not however invalidate
+any other reasons why the document might be covered by the GNU General
+Public License. If you modify this font, you may extend this exception to
+your version of the font, but you are not obligated to do so. If you do not
+wish to do so, delete this exception statement from your version. </tt>
+</p></dd>
+
+
+<dt><b><a href="#TOCWMS" name="WMS"> I am writing a website maintenance
+system</a> (called a “<a
+href="/philosophy/words-to-avoid.html">content management system</a>”
+by some), or some other application which generates web pages from
+templates. What license should I use for those templates?</b></dt>
+
+<dd>
+<p>Templates are minor enough that it is not worth using copyleft to protect
+them. It is normally harmless to use copyleft on minor works, but templates
+are a special case, because they are combined with data provided by users of
+the application and the combination is distributed. So, we recommend that
+you license your templates under simple permissive terms. </p>
+
+<p>Some templates make calls into Javascript functions. Since Javascript is
+often non-trivial, it is worth copylefting. Because the templates will be
+combined with user data, it's possible that template+user data+Javascript
+would be considered one work under copyright law. A line needs to be drawn
+between the Javascript (copylefted), and the user code (usually under
+incompatible terms). </p>
+
+<p><a href="/licenses/template-diagram.png"><img
src="/licenses/template-diagram.png" alt="A diagram of the above content"
/></a></p>
+
+<p>Here's an exception for Javascript code that does this:</p>
+
+<blockquote><p>As a special exception to GPL, any HTML file which merely makes
function
+calls to this code, and for that purpose includes it by reference shall be
+deemed a separate work for copyright law purposes. In addition, the
+copyright holders of this code give you permission to combine this code with
+free software libraries that are released under the GNU LGPL. You may copy
+and distribute such a system following the terms of the GNU GPL for this
+code and the LGPL for the libraries. If you modify this code, you may
+extend this exception to your version of the code, but you are not obligated
+to do so. If you do not wish to do so, delete this exception statement from
+your version.
+</p></blockquote>
+
+</dd>
+
+<dt><b><a href="#TOCNonFreeTools" name="NonFreeTools">Can I release a program
+under the GPL which I developed using non-free tools?</a></b></dt>
+
+<dd>
+Which programs you used to edit the source code, or to compile it, or study
+it, or record it, usually makes no difference for issues concerning the
+licensing of that source code.
+
+<p>
+However, if you link non-free libraries with the source code, that would be
+an issue you need to deal with. It does not preclude releasing the source
+code under the GPL, but if the libraries don't fit under the “system
+library” exception, you should affix an explicit notice giving
+permission to link your program with them. The FSF can give you advice on
+doing this.</p>
+</dd>
+
+
+<dt><b><a href="#TOCGPLTranslations" name="GPLTranslations">Are there
+translations of the GPL into other languages?</a></b></dt>
+
+<dd>
+It would be useful to have translations of the GPL into languages other than
+English. People have even written translations and sent them to us. But we
+have not dared to approve them as officially valid. That carries a risk so
+great we do not dare accept it.
+<p>
+A legal document is in some ways like a program. Translating it is like
+translating a program from one language and operating system to another.
+Only a lawyer skilled in both languages can do it—and even then, there
+is a risk of introducing a bug.</p>
+<p>
+If we were to approve, officially, a translation of the GPL, we would be
+giving everyone permission to do whatever the translation says they can do.
+If it is a completely accurate translation, that is fine. But if there is
+an error in the translation, the results could be a disaster which we could
+not fix.</p>
+<p>
+If a program has a bug, we can release a new version, and eventually the old
+version will more or less disappear. But once we have given everyone
+permission to act according to a particular translation, we have no way of
+taking back that permission if we find, later on, that it had a bug.</p>
+<p>
+Helpful people sometimes offer to do the work of translation for us. If the
+problem were a matter of finding someone to do the work, this would solve
+it. But the actual problem is the risk of error, and offering to do the
+work does not avoid the risk. We could not possibly authorize a translation
+written by a non-lawyer.</p>
+<p>
+Therefore, for the time being, we are not approving translations of the GPL
+as globally valid and binding. Instead, we are doing two things:</p>
+<ul>
+<li> Referring people to unofficial translations. This means that we permit
+people to write translations of the GPL, but we don't approve them as
+legally valid and binding.
+<p>
+An unapproved translation has no legal force, and it should say so
+explicitly. It should be marked as follows:</p>
+<pre>
+ This translation of the GPL is informal, and not officially approved
+ by the Free Software Foundation as valid. To be completely sure of
+ what is permitted, refer to the original GPL (in English).
+</pre>
+<p>
+But the unapproved translation can serve as a hint for how to understand the
+English GPL. For many users, that is sufficient.</p>
+<p>
+However, businesses using GNU software in commercial activity, and people
+doing public ftp distribution, should need to check the real English GPL to
+make sure of what it permits.</p>
+</li>
+<li>
+Publishing translations valid for a single country only.
+<p>
+We are considering the idea of publishing translations which are officially
+valid only for one country. This way, if there is a mistake, it will be
+limited to that country, and the damage will not be too great.</p>
+<p>
+It will still take considerable expertise and effort from a sympathetic and
+capable lawyer to make a translation, so we cannot promise any such
+translations soon.</p>
+</li>
+</ul>
+<p></p></dd>
+
+<dt><b><a href="#TOCInterpreterIncompat" name="InterpreterIncompat">If a
+programming language interpreter has a license that is incompatible with the
+GPL, can I run GPL-covered programs on it?</a></b></dt>
+
+<dd>
+When the interpreter just interprets a language, the answer is yes. The
+interpreted program, to the interpreter, is just data; the GPL doesn't
+restrict what tools you process the program with.
+<p>
+However, when the interpreter is extended to provide “bindings”
+to other facilities (often, but not necessarily, libraries), the interpreted
+program is effectively linked to the facilities it uses through these
+bindings. The JNI or Java Native Interface is an example of such a
+facility; libraries that are accessed in this way are linked dynamically
+with the Java programs that call them.</p>
+<p>
+So if these facilities are released under a GPL-incompatible license, the
+situation is like linking in any other way with a GPL-incompatible library.
+Which implies that:</p>
+<ol>
+ <li>If you are writing code and releasing it under the GPL, you can state an
+explicit exception giving permission to link it with those GPL-incompatible
+facilities.</li>
+
+ <li>If you wrote and released the program under the GPL, and you designed it
+specifically to work with those facilities, people can take that as an
+implicit exception permitting them to link it with those facilities. But if
+that is what you intend, it is better to say so explicitly.</li>
+
+ <li>You can't take someone else's GPL-covered code and use it that way, or
add
+such exceptions to it. Only the copyright holders of that code can add the
+exception.</li>
+</ol>
+<p></p></dd>
+
+<dt><b><a href="#TOCWhoHasThePower" name="WhoHasThePower">Who has the power to
+enforce the GPL?</a></b></dt>
+
+<dd>
+Since the GPL is a copyright license, the copyright holders of the software
+are the ones who have the power to enforce the GPL. If you see a violation
+of the GPL, you should inform the developers of the GPL-covered software
+involved. They either are the copyright holders, or are connected with the
+copyright holders. <a
+href="http://www.fsf.org/licenses/gpl-faq.html#ReportingViolation";>Learn
+more about reporting GPL violations.</a>
+<p></p></dd>
+
+
+<dt><b><a href="#TOCOOPLang" name="OOPLang"> In an object-oriented language
such
+as Java, if I use a class that is GPL'ed without modifying, and subclass it,
+in what way does the GPL affect the larger program?</a></b></dt>
+
+<dd>
+Subclassing is creating a derivative work. Therefore, the terms of the GPL
+affect the whole program where you create a subclass of a GPL'ed class.
+<p></p></dd>
+
+<dt><b><a href="#TOCPortProgramToGL" name="PortProgramToGL">If I port my
program
+to GNU/Linux, does that mean I have to release it as Free Software under the
+GPL or some other Free Software license?</a></b></dt>
+
+<dd>
+In general, the answer is no—this is not a legal requirement. In
+specific, the answer depends on which libraries you want to use and what
+their licenses are. Most system libraries either use the <a
+href="/copyleft/lesser.html">GNU Lesser GPL</a>, or use the GNU GPL plus an
+exception permitting linking the library with anything. These libraries can
+be used in non-free programs; but in the case of the Lesser GPL, it does
+have some requirements you must follow.
+<p>
+Some libraries are released under the GNU GPL alone; you must use a
+GPL-compatible license to use those libraries. But these are normally the
+more specialized libraries, and you would not have had anything much like
+them on another platform, so you probably won't find yourself wanting to use
+these libraries for simple porting.</p>
+<p>
+Of course, your software is not a contribution to our community if it is not
+free, and people who value their freedom will refuse to use it. Only people
+willing to give up their freedom will use your software, which means that it
+will effectively function as an inducement for people to lose their
freedom.</p>
+<p>
+If you hope some day to look back on your career and feel that it has
+contributed to the growth of a good and free society, you need to make your
+software free.
+</p></dd>
+
+<dt><b><a href="#TOCCompanyGPLCostsMoney" name="CompanyGPLCostsMoney"> I just
+found out that a company has a copy of a GPL'ed program, and it costs money
+to get it. Aren't they violating the GPL by not making it available on the
+Internet?</a></b></dt>
+
+<dd>
+No. The GPL does not require anyone to use the Internet for distribution.
+It also does not require anyone in particular to redistribute the program.
+And (outside of one special case), even if someone does decide to
+redistribute the program sometimes, the GPL doesn't say he has to distribute
+a copy to you in particular, or any other person in particular.
+<p>
+What the GPL requires is that he must have the freedom to distribute a copy
+to you <em>if he wishes to</em>. Once the copyright holder does distribute
+a copy program to someone, that someone can then redistribute the program to
+you, or to anyone else, as he sees fit.
+</p></dd>
+
+<dt><b><a href="#TOCReleaseNotOriginal" name="ReleaseNotOriginal"> Can I
release
+a program with a license which says that you can distribute modified
+versions of it under the GPL but you can't distribute the original itself
+under the GPL?</a></b></dt>
+
+<dd>
+No. Such a license would be self-contradictory. Let's look at its
+implications for me as a user.
+<p>
+Suppose I start with the original version (call it version A), add some code
+(let's imagine it is 1000 lines), and release that modified version (call it
+B) under the GPL. The GPL says anyone can change version B again and
+release the result under the GPL. So I (or someone else) can delete those
+1000 lines, producing version C which has the same code as version A but is
+under the GPL.</p>
+<p>
+If you try to block that path, by saying explicitly in the license that I'm
+not allowed to reproduce something identical to version A under the GPL by
+deleting those lines from version B, in effect the license now says that I
+can't fully use version B in all the ways that the GPL permits. In other
+words, the license does not in fact allow a user to release a modified
+version such as B under the GPL.
+</p>
+</dd>
+
+<dt><b><a href="#TOCDistributeSubsidiary" name="DistributeSubsidiary"> Does
+moving a copy to a majority-owned, and controlled, subsidiary constitute
+distribution?</a></b></dt>
+<dd>
+<p>
+Whether moving a copy to or from this subsidiary constitutes 'distribution'
+is a matter to be decided in each case under the copyright law of the
+appropriate jurisdiction. The GPL does not and cannot override local laws.
+US copyright law is not entirely clear on the point, but appears not to
+consider this distribution.
+</p><p>
+If, in some country, this is considered distribution, and the subsidiary
+must receive the right to redistribute the program, that will not make a
+practical difference. The subsidiary is controlled by the parent company;
+rights or no rights, it won't redistribute the program unless the parent
+company decides to do so.
+</p>
+</dd>
+
+<dt><b><a href="#TOCClickThrough" name="ClickThrough"> Can software installers
+ask people to click to agree to the GPL? If I get some software under the
+GPL, do I have to agree to anything?</a></b></dt>
+<dd>
+<p>
+Some software packaging systems have a place which requires you to click
+through or otherwise indicate assent to the terms of the GPL. This is
+neither required nor forbidden. With or without a click through, the GPL's
+rules remain the same. </p>
+
+<p>
+Merely agreeing to the GPL doesn't place any obligations on you. You are
+not required to agree to anything to merely use software which is licensed
+under the GPL. You only have obligations if you modify or distribute the
+software. If it really bothers you to click through the GPL, nothing stops
+you from hacking the GPLed software to bypass this.
+</p>
+</dd>
+
+<dt><b><a href="#TOCGPLCompatInstaller" name="GPLCompatInstaller">I would like
+to bundle GPLed software with some sort of installation software. Does that
+installer need to have a GPL-compatible license?</a></b></dt>
+<dd>
+<p>No. The installer and the files it installs are separate works. As a
+result, the terms of the GPL do not apply to the installation software.</p>
+</dd>
+
+</dl>
+
+
+<div style="font-size: small;">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't have notes.-->
+ </div>
+</div>
+
+<!--#include virtual="/server/footer.de.html" -->
+<div id="footer">
+<p>
+Bitte senden Sie Fragen zur FSF & GNU an <a
+href="mailto:address@hidden";><address@hidden></a>. Sie können auch die
<a
+href="/contact/contact">Free Software Foundation kontaktieren</a>.
+<br />
+Bitte senden Sie ungültige Verweise und andere Korrekturen oder Vorschläge
+an <a
+href="mailto:address@hidden";><address@hidden></a>.
+</p>
+
+<p>
+Bitte beachten Sie die <a
+href="/server/standards/README.translations">LIESMICH für Ãbersetzungen</a>,
+um weitere Informationen über die Koordinierung und Einsendung von
+Ãbersetzungen zu erhalten.
+</p>
+
+<p>
+Copyright © 2001, 2006, 2007, 2008 Free Software Foundation, Inc.</p>
+<address><!--51 Franklin Street, Fifth Floor, Boston, MA 02110-1301,
USA--></address>
+<p>Dieses Werk bzw. Inhalt steht unter einer <a rel="license"
+href="http://creativecommons.org/licenses/by-nd/3.0/us/deed.de";>Creative
+Commons Namensnennung-Keine Bearbeitung 3.0 Vereinigte Staaten von Amerika
+Lizenz</a>.
+</p>
+
+
+<div class="translators-credits">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.-->
+ </div>
+ <p>
+<!-- timestamp start -->
+Aktualisierung:
+
+$Date: 2011/10/29 16:35:41 $
+
+<!-- timestamp end -->
+</p>
+</div>
+
+<!-- <div id="translations">
+ -->
+<!-- <h4>
+Translations of this page</h4> -->
+<!-- -->
+<!-- Please keep this list alphabetical by language code. -->
+<!-- Comment what the language is for each type, i.e. de is German. -->
+<!-- Write the language name in its own language (Deutsch) in the text. -->
+<!-- If you add a new language here, please -->
+<!-- advise address@hidden and add it to -->
+<!-- - /home/www/html/server/standards/README.translations.html -->
+<!-- - one of the lists under the section "Translations Underway" -->
+<!-- - if there is a translation team, you also have to add an alias -->
+<!-- to mail.gnu.org:/com/mailer/aliases -->
+<!-- Please also check you have the language code right; see: -->
+<!-- http://www.loc.gov/standards/iso639-2/php/code_list.php -->
+<!-- If the 2-letter ISO 639-1 code is not available, -->
+<!-- use the 3-letter ISO 639-2. -->
+<!-- Please use W3C normative character entities. -->
+<!-- -->
+<!-- <gnun>
+<ul class="translations-list"> -->
+<!-- Czech -->
+<!-- <li><a
href="/licenses/old-licenses/gpl-2.0-faq.cs.html">Česky</a> [cs]</li>
-->
+<!-- English -->
+<!-- <li><a
href="/licenses/old-licenses/gpl-2.0-faq.html">English</a> [en]</li> -->
+<!-- Spanish -->
+<!-- <li><a
href="/licenses/old-licenses/gpl-2.0-faq.es.html">Español</a> [es]</li>
-->
+<!-- French -->
+<!-- <li><a
href="/licenses/old-licenses/gpl-2.0-faq.fr.html">Français</a> [fr]</li>
-->
+<!-- Italian -->
+<!-- <li><a
href="/licenses/old-licenses/gpl-2.0-faq.it.html">Italiano</a> [it]</li>
-->
+<!-- Japanese -->
+<!-- <li><a
href="/licenses/old-licenses/gpl-2.0-faq.ja.html">日本語</a> [ja]</li>
-->
+<!-- Korean -->
+<!-- <li><a
href="/licenses/old-licenses/gpl-2.0-faq.ko.html">한국어</a> [ko]</li>
-->
+<!-- Polish -->
+<!-- <li><a
href="/licenses/old-licenses/gpl-2.0-faq.pl.html">polski</a> [pl]</li> -->
+<!-- Brazilian Portuguese -->
+<!-- <li><a
href="/licenses/old-licenses/gpl-2.0-faq.pt-br.html">português do
Brasil</a> [pt-br]</li> -->
+<!-- </ul></gnun> -->
+<!-- </div>
+ -->
+</div>
+</body>
+</html>
Index: gpl-2.0-translations.de.html
===================================================================
RCS file: gpl-2.0-translations.de.html
diff -N gpl-2.0-translations.de.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ gpl-2.0-translations.de.html 29 Oct 2011 16:35:41 -0000 1.1
@@ -0,0 +1,399 @@
+
+
+<!--#include virtual="/server/header.de.html" -->
+
+<!-- This file is automatically generated by GNUnited Nations! -->
+<title>Inoffizielle Ãbersetzungen der GNU GPLv2.0 - GNU Projekt - Free
Software
+Foundation (FSF)</title>
+<meta http-equiv="keywords" content=" " />
+
+<!--#include virtual="/server/banner.de.html" -->
+<!--#include
virtual="/licenses/old-licenses/po/gpl-2.0-translations.translist" -->
+<h2>Inoffizielle Ãbersetzungen der GNU GPLv2.0</h2>
+
+<h3 id="UnofficialTranslations">Informationen über inoffizielle
Ãbersetzungen</h3>
+
+<p>
+Der Grund, warum die FSF diese Ãbersetzungen als nicht offiziell gültig
+genehmigt, ist, dass deren Ãberprüfung schwierig und teuer wäre (es wird die
+Hilfe zweisprachiger Juristen in anderen Ländern benötigt). Schlimmer noch,
+wenn ein Fehler durchrutscht, könnten die Ergebnisse für die gesamte
+Freie-Software-Gemeinschaft katastrophal sein. Solange die Ãbersetzungen
+inoffiziell sind, können sie keinen Schaden anrichten.</p>
+
+<p>Die Ãbersetzungen sollen mehr Menschen helfen, die GNU GPL zu verstehen.
+Ãbersetzungen müssen grundsätzlich genau sein, wenn auch nicht perfekt. Für
+eine gute Ãbersetzung ist es unerlässlich, grundlegende Konzepte wie <a
+href="/copyleft/copyleft">Copyleft</a> und die <a
+href="/philosophy/free-sw">Definition von Freie Software</a> vollständig
+verstanden zu haben. Aus diesem Grund sollten diejenigen, die Ãbersetzungen
+beitragen möchten, sich vergewissern, dass sie gut mit sowohl diesen
+Konzepten als auch anderen philosophischen Prinzipien, die im Dokument
+auftauchen können, vertraut sind.</p>
+
+<p>Wir erteilen die Berechtigung, Ãbersetzungen der GNU GPL, GNU LGPL, GNU
AGPL
+und GNU FDL in andere Sprachen zu veröffentlichen, unter folgendem
+Vorbehalt:</p>
+
+<ol>
+
+<li>Die Ãbersetzung wird als inoffiziell bezeichnet, um darüber zu
informieren,
+dass sie kein rechtlicher Ersatz für die verbindliche Fassung ist
+(Informationen hierzu siehe unten).</li>
+
+<li>AÌnderungen auf unseren Wunsch hin eingepflegt werden, wenn wir von GNUs
+Freunden erfahren, dass AÌnderungen notwendig sind, die Ãbersetzung
+verständlicher zu machen.</li>
+
+<li>Die Ãbersetzung wird nicht auf einem kommerziellen Webauftritt gehostet
und
+bezieht sich auf keine Unternehmen.</li>
+
+<li>Der Webauftritt, der die Ãbersetzung enthält, sollte keine Verweise mit
+Ausnahme zur fsf.org und gnu.org enthalten. Wir akzeptieren möglicherweise
+Verweise auf andere freie Softwarepakete, aber bevorzugen sie zu
vermeiden.</li>
+
+<li>Der Webauftritt sollte darauf hinweisen, dass sie unter irgendeiner Version
+der <em>Creative Commons Namensnennung-Keine Bearbeitung-Lizenz</em>
+freigegeben ist.</li>
+
+<li>Wir können auch kleinere Ausnahmen dieser Regel in älteren Fällen, die
+schwer zu beheben sind, akzeptieren.</li>
+
+</ol>
+
+<p>Wir verweisen nicht unbedingt auf alle inoffiziellen Ãbersetzungen, von der
+wir in jeder Sprache wissen. Wenn bspw. eine inoffizielle Ãbersetzung von
+einem freien Softwareunternehmen gemacht wurde, das wir kennen und dem wir
+vertrauen, verweisen wir eher auf diese Ãbersetzung anstatt einer
+anderen. Wir können sie zwar noch nicht offiziell machen, aber erwarten,
+dass es wahrscheinlich hauptsächlich richtig ist.</p>
+
+<p>
+Ãm die Ãbersetzungen als inoffiziell zu beschriften, fügen Sie folgenden
+Text am Anfang hinzu, sowohl in Englisch und in der Sprache der
+Ãbersetzung ‑ tauschen Sie <em>language</em> durch die
+verwendete Sprache aus:</p>
+<blockquote dir="ltr"><p>
+
+<!--TRANSLATORS: If you translate this paragraph, retain the English
+text and put your translation below. The entire <blockquote>
+ element
+has dir="ltr" to work by default with RTL languages when the notice is
+not translated, so if your language is RTL, you *must* put your
+translation within <span dir="rtl">.-->
+<span xml:lang="en" lang="en">This is an unofficial translation of the GNU
+General Public License into <tt>language</tt>. It was not published by the
+Free Software Foundation, and does not legally state the distribution terms
+for software that uses the GNU GPL—only the original English text of
+the GNU GPL does that. However, we hope that this translation will help
+<tt>language</tt> speakers understand the GNU GPL better.</span><br /><br />
+
+<span class="translation">Dies ist eine inoffizielle Ãbersetzung der GNU
+General Public License in <tt>Deutsch</tt>. Sie wurde nicht von der Free
+Software Foundation freigegeben und ist keine rechtsverbindliche
+Vertriebsbedingung für Software, die GNU GPL lizenziert
+ist ‑ dies kann nur der englische Originaltext der
+GNU GPL. Dennoch hoffen wir, dass diese Ãbersetzung
+<tt>deutschsprachigen</tt> Personen helfen wird, die GNU GPL besser zu
+verstehen.</span>
+</p></blockquote>
+<p>
+Möchten Sie eine Lizenz übersetzen, informieren Sie bitte die <em>GNU
+Translation Manager</em> <a
+href="mailto:address@hidden";><address@hidden></a>.
+Sie überprüfen, ob die Ãbersetzung den oben genannten Richtlinien folgt und
+legen einen Verweis darauf an.</p>
+
+<p>
+Um leicht nach Ãbersetzungen suchen zu können, verwenden Sie bitte den
+Sprachcode in eckigen Klammern.
+</p>
+
+<p>
+Dies sind Ãbersetzungen einer älteren Version der GNU GPL. Siehe auch die <a
+href="/licenses/translations">Ãbersetzungen aktueller Lizenzen</a>.
+</p>
+
+<!-- Please keep entries alphabetical by language name. -->
+<!-- The language is Portuguese, the dialect is Brazilian. -->
+<!-- To be kind to the user, we list it under both "B" and "P" -->
+<!-- this link is broken. I sent mail to Conectiva asking for -->
+<!-- the new location but got no replies. Fortunately I found -->
+<!-- another translation (fsl) LI A HREF= -->
+<!-- http://lie-br.conectiva.com.br/licenca_gnu.html Brazilian -->
+<ul>
+
+<!-- dead link as of 2011-06-26
+ <li>
+<code>[af]</code> <a
href="http://www.poespas.co.za/wiki/index.php/GNU_Algemene_Publieke_Lisensie";>Afrikaans</a>
translation of the GPL
+</li>
+-->
+<!-- these translations have links other than to www.fsf.org and www.gnu.org
+ <li>
+<code>[sq]</code> <a href="http://www.alblinux.net/dok/GPL.html";>Albanian</a>
translation of the GPL</li>
+ <li><code>[ar]</code> <a
href="http://www.linuxfuture.org/download/Arabic_GPL_2.0.htm";>Arabic</a>
+ translation of the GPL</li>
+-->
+<li><code>[pt-br]</code> Portugiesisch (Brasilien): <a
+href="http://www.magnux.org/doc/GPL-pt_BR.txt";>Nur Text</a></li>
+
+<!-- hosted on a commercial site
+ <li>
+<code>[cs]</code> Czech translations of the GPL
+ (<a href="http://staff.cesnet.cz/~lhotka/gnugpl-cz.html";>1</a>)
+-->
+<!-- dead link as of 2011-06-26
+ (<a href="http://gnu.cz/article.php?id_art=32";>
+2</a>)</li>
+-->
+<!-- these translations have links other than to www.fsf.org and www.gnu.org
+ <li>
+<code>[da]</code> <a href="http://www.fundanemt.com/gpl_da.html";>Danish</a>
+ translation of the GPL</li>
+-->
+<!-- hosted on a commercial site
+ <li>
+<code>[nl]</code> <a href="http://users.skynet.be/xterm/gpld.txt";>Dutch</a>
translation of the GPL</li>
+-->
+<!-- these translations have links other than to www.fsf.org and www.gnu.org
+ <li>
+<code>[eo]</code> <a
href="http://www.esperanto.mv.ru/Cetero/gpl.html";>Esperanto</a> translation of
the GPL</li>
+-->
+<li><code>[fa]</code> Persisch (Farsi): <a
+href="http://www.kaveh.org/gnu/gpl-fa.html";>HTML</a></li>
+
+ <!-- these translations have links other than to www.fsf.org and www.gnu.org
+ <li>
+<code>[fi]</code> <a
href="http://www.turre.com/licenses/gpl-2.0_fi.html";>Finnish</a>
+ translation of the GPL</li>
+ <li><code>[fr]</code> <a
href="http://fsffrance.org/gpl/gpl-fr.fr.html";>French</a>
+ translation of the GPL</li>
+-->
+<li><!-- these translations have links other than to www.fsf.org and
www.gnu.org
+ and <a href="http://members.tripod.com.br/RamonFlores/GNU/gpl.html";>
+
+ Galician minimo</a>
+-->
+<code>[gl]</code> Galizisch: <a
+href="http://www.mancomun.org/GPL2_GL/gpl2_gl.txt";>Nur Text</a></li>
+
+<!-- these translations have links other than to www.fsf.org and www.gnu.org
+ <li>
+<code>[ka]</code> <a
href="http://aiet.qartuli.net/projects/gnu-gpl_en.php";>Georgian</a>
+ translation of the GPL</li>
+ <li><code>[de]</code> <a
href="http://www.gnu.de/documents/gpl-2.0.de.html";>German</a>
+ translation of the GPL</li>
+ <li><code>[el]</code> Greek translation of the GPL
+ (<a href="http://stillmover.tripod.com/Adana/";>1</a>)
+ (<a href="http://www.eexi.gr/?q=node/16";>2</a>)</li>
+-->
+<!-- hosted on a commercial site
+ <li>
+<code>[he]</code> <a
href="http://www.law.co.il/media/computer-law/gpl-hebrew.html";>
+ Hebrew</a> translation of the GPL</li>
+-->
+<!-- these translations have links other than to www.fsf.org and www.gnu.org
+ <li>
+<code>[hu]</code> <a href="http://gnu.hu/gpl.html";>Hungarian</a>
+ translation of the GPL</li>
+ <li><code>[id]</code> <a
href="http://vlsm.org/etc/gpl-unofficial.id.html";>Indonesian</a>
+ translation of the GPL</li>
+-->
+<li><code>[it]</code> Italienisch: <a
+href="http://www.softwarelibero.it/gnudoc/gpl.it.txt";>Nur Text</a></li>
+
+<!-- lgpl.ja.html is NOT a translation of GPL -->
+<!-- these translations have links other than to www.fsf.org and www.gnu.org
+ <li>
+<code>[ja]</code> Japanese
+ translations of the GPL
+ (<a href="http://www.opensource.jp/gpl/gpl.ja.html.euc-jp";>1</a>)
+-->
+<!-- dead link as of 2011-06-26
+ (<a href="ftp://ftp.sra.co.jp/pub/gnu/local-fix/GPL2-j/";>
+2</a>)</li>
+-->
+<!-- hosted on gnu.org
+ <li>
+<code>[ko]</code> <a
href="http://korea.gnu.org/people/chsong/copyleft/gpl.ko.html";>Korean</a>
+ translation of the GPL</li>
+-->
+<!-- these translations have links other than to www.fsf.org and www.gnu.org
+ <li>
+<code>[lt]</code> <a
href="http://www.autopenhosting.org/gnu/gnu_gpl.html";>Lithuanian</a>
+ translation of the GPL</li>
+ <li><code>[mk]</code> <a
href="http://www.slobodensoftver.org.mk/dokumenti/gnu_gpl_mk.html";>Macedonian</a>
+ translation of the GPL</li>
+ <li><code>[nb]</code> <a
href="http://www.joomlainorge.no/norsk-gnu-general-public-licence-gpl-v2";>Norwegian
(Bokmål)</a>
+ translation of the GPL</li>
+-->
+<li><code>[pl]</code> Polnisch: <a
+href="http://gnu.org.pl/text/licencja-gnu.html";>HTML</a></li>
+ <li><code>[pt]</code> Portugiesisch: <a
+href="http://www.neoscopio.com/licenca_GPL_pt.txt";>Nur Text</a></li>
+
+<!-- The language is Portuguese, the dialect is Brazilian. -->
+<!-- To be kind to the user, we list it under both "B" and "P" -->
+<li><code>[pt-br]</code> Portugiesisch (Brasilien): <a
+href="http://www.magnux.org/doc/GPL-pt_BR.txt";>Nur Text</a></li>
+
+<!-- these translations have links other than to www.fsf.org and www.gnu.org
+ <li>
+<code>[ru]</code> Russian
+ translations of the GPL
+ (<a href="http://www.infolex.narod.ru/gpl_gnu/gplrus.html";>1</a>)
+ (<a href="http://law.bugtraq.ru/freesoft/gplrus3.html";>2</a>)</li>
+-->
+<!-- dead link as of 2011-06-26
+ <li>
+<code>[sr]</code> <a
href="http://alas.matf.bg.ac.yu/~mr99164/ojl.html";>Serbian</a>
+ translation of the GPL</li>
+-->
+<!-- these translations have links other than to www.fsf.org and www.gnu.org
+ <li>
+<code>[es]</code> Spanish translations of the GPL
+ (<a href="http://gugs.sindominio.net/licencias/";>1</a> - several
different translations)
+-->
+<!-- dead link as of 2011-06-26
+ (<a
href="http://www.fsl.org.mx/index.pl/fsl/artculos/articulosmb2/licencias/licencia-gpl-espaolmxico";>
+2</a> - Spanish Mexican)</li>
+-->
+<li><code>[sv]</code> Schwedisch: <a
+href="http://danielnylander.se/gpl/";>HTML</a></li>
+
+ <!-- dead link as of 2011-06-26
+ <li>
+<code>[th]</code> <a href="http://developer.thai.net/gpl/";>Thai</a>
+ translation of the GPL</li>
+-->
+<li><!-- these translations have links other than to www.fsf.org and
www.gnu.org
+ (<a href="http://www.belgeler.org/howto/gpl.html";>
+2</a>)-->
+<code>[tr]</code> Türkisch: <a
+href="http://www.arayan.com/da/gpl_tr.html";>HTML</a>
+</li>
+
+<!-- these translations have links other than to www.fsf.org and www.gnu.org
+ <li>
+<code>[uk]</code> <a
href="http://www.linux.kiev.ua/ua/devel/licenses/gnu-gpl2/";>Ukranian</a>
+ translation of the GPL</li>
+-->
+<!-- dead link as of 2011-06-26
+ <li>
+<code>[vi]</code> <a href="http://vi.wikisource.org/wiki/GPL";>Vietnamese</a>
+ translation of the GPL</li>
+-->
+<!-- dead link as of 2011-06-26
+ <li>
+<code>[cy]</code> <a href="http://www.hebffinia.com/gpl_cymraeg/";>Welsh</a>
+ translation of the GPL</li>
+-->
+<!-- these translations have links other than to www.fsf.org and www.gnu.org
+ <li>
+<code>[zh-cn]</code> <a href="http://gnu.freehostingguru.com/gpl/";>Chinese
(Simplified)</a>
+ translation of the GPL</li>
+-->
+<li><code>[zh-tw]</code> Chinesisch (traditionell): <a
+href="http://www.linux.org.tw/CLDP/OLD/doc/GPL.html";>HTML</a></li>
+</ul>
+
+
+<div style="font-size: small;">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't have notes.-->
+ </div>
+</div>
+
+<!--#include virtual="/server/footer.de.html" -->
+<div id="footer">
+
+<p>
+Bitte senden Sie Fragen zur FSF & GNU an <a
+href="mailto:address@hidden";><address@hidden></a>. Sie können auch die
<a
+href="/contact/contact">Free Software Foundation kontaktieren</a>.
+<br />
+Bitte senden Sie ungültige Verweise und andere Korrekturen oder Vorschläge
+an <a
+href="mailto:address@hidden";><address@hidden></a>.
+</p>
+
+<p>
+Bitte beachten Sie die <a
+href="/server/standards/README.translations">LIESMICH für Ãbersetzungen</a>,
+um weitere Informationen über die Koordinierung und Einsendung von
+Ãbersetzungen zu erhalten.
+</p>
+
+<p>
+Copyright © 1996, 1997, 1998, 1999, 2004, 2005, 2006, 2007, 2008, 2009,
+2011 Free Software Foundation, Inc.
+</p>
+<p>Dieses Werk bzw. Inhalt steht unter einer <a rel="license"
+href="http://creativecommons.org/licenses/by-nd/3.0/us/deed.de";>Creative
+Commons Namensnennung-Keine Bearbeitung 3.0 Vereinigte Staaten von Amerika
+Lizenz</a>.
+</p>
+
+
+<div class="translators-credits">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.-->
+<strong>Ãbersetzung:</strong> Joerg Kohne, 2011.</div>
+ <p>
+<!-- timestamp start -->
+Aktualisierung:
+
+$Date: 2011/10/29 16:35:41 $
+
+<!-- timestamp end -->
+</p>
+</div>
+
+<!-- <div id="translations">
+ -->
+<!-- <h4>
+Translations of this page</h4> -->
+<!-- -->
+<!-- Please keep this list alphabetical by language code. -->
+<!-- Comment what the language is for each type, i.e. de is German. -->
+<!-- Write the language name in its own language (Deutsch) in the text.
-->
+<!-- If you add a new language here, please -->
+<!-- advise address@hidden and add it to -->
+<!-- - /home/www/html/server/standards/README.translations.html -->
+<!-- - one of the lists under the section "Translations Underway" -->
+<!-- - if there is a translation team, you also have to add an alias -->
+<!-- to mail.gnu.org:/com/mailer/aliases -->
+<!-- Please also check you have the language code right; see: -->
+<!-- http://www.loc.gov/standards/iso639-2/php/code_list.php -->
+<!-- If the 2-letter ISO 639-1 code is not available, -->
+<!-- use the 3-letter ISO 639-2. -->
+<!-- Please use W3C normative character entities. -->
+<!-- -->
+<!-- See also '(web-trans)Capitalization': -->
+<!--
http://gnu.org/software/trans-coord/manual/web-trans/html_node/Capitalization.html
-->
+<!-- -->
+<!-- -->
+<!-- <gnun>
+<ul class="translations-list"> -->
+<!-- Catalan -->
+<!-- <li><a
href="/licenses/old-licenses/gpl-2.0-translations.ca.html">català</a> [ca]</li>
-->
+<!-- English -->
+<!-- <li><a
href="/licenses/old-licenses/gpl-2.0-translations.html">English</a> [en]</li>
-->
+<!-- French -->
+<!-- <li><a
href="/licenses/old-licenses/gpl-2.0-translations.fr.html">français</a> [fr]</li>
-->
+<!-- Japanese -->
+<!-- <li><a
href="/licenses/old-licenses/gpl-2.0-translations.ja.html">日本語</a> [ja]</li>
-->
+<!-- Korean -->
+<!-- <li><a
href="/licenses/old-licenses/gpl-2.0-translations.ko.html">한국어</a> [ko]</li>
-->
+<!-- Polish -->
+<!-- <li><a
href="/licenses/old-licenses/gpl-2.0-translations.pl.html">polski</a> [pl]</li>
-->
+<!-- Chinese (Simplified) -->
+<!-- <li><a
href="/licenses/old-licenses/gpl-2.0-translations.zh-cn.html">简体中文</a> [zh-cn]</li>
-->
+<!-- Chinese (Traditional) -->
+<!-- <li><a
href="/licenses/old-licenses/gpl-2.0-translations.zh-tw.html">繁體中文</a> [zh-tw]</li>
-->
+<!-- </ul></gnun> -->
+<!-- </div>
+ -->
+</div>
+</body>
+</html>
Index: gpl-2.0.de.html
===================================================================
RCS file: gpl-2.0.de.html
diff -N gpl-2.0.de.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ gpl-2.0.de.html 29 Oct 2011 16:35:41 -0000 1.1
@@ -0,0 +1,613 @@
+
+
+<!--#include virtual="/server/header.de.html" -->
+
+<!-- This file is automatically generated by GNUnited Nations! -->
+<title>GNU General Public License (GPL) v2.0 - GNU Projekt - Free Software
+Foundation (FSF)</title>
+<link rel="alternate" type="application/rdf+xml" href="gpl-2.0.rdf" />
+
+<!--#include virtual="/server/banner.de.html" -->
+<!--#include virtual="/licenses/old-licenses/po/gpl-2.0.translist" -->
+<h2>GNU General Public License, Version 2</h2>
+
+<!-- Please keep this list alphabetical -->
+<!-- tower, gpl.ja.html is Japanese translation of THIS PAGE, -->
+<!-- NOT translation of GPL itself(gpl.ja.html contains the original -->
+<!-- English version). So please do not remove the following. -->
+<!-- Thanks -mhatta -->
+<!-- The same for the Czech page. The entire text of GPL is not -->
+<!-- translated on this page. Thanks Sisao -->
+<ul>
+ <li><a href="/licenses/gpl-violation">GNU GPL: Was ist bei einer möglichen
+Verletzung zu tun</a></li>
+ <li><a href="/licenses/old-licenses/gpl-2.0-translations">Ãbersetzungen der
+GPLv2</a></li>
+ <li><a href="/licenses/old-licenses/gpl-2.0-faq">GPLv2: Häufig gestellte
Fragen
+(FAQ)</a></li>
+ <li>Die GNU GPLv2 ist in anderen Formaten abrufbar (engl.): <a
+href="gpl-2.0.txt">Nur Text</a>, <a href="gpl-2.0.texi">Texinfo</a>, <a
+href="gpl-2.0.tex">LaTeX</a>, <a href="gpl-2.0-standalone.html">Nur
+HTML</a>, <a href="gpl-2.0.dbk">Docbook</a>
+ </li>
+</ul>
+
+<hr />
+
+<h3>Inhalt</h3>
+<ul>
+
+ <li><!--TRANSLATORS: Don't translate the license; copy msgid's
+ verbatim!-->
+<a id="TOC1" href="#SEC1">GNU GENERAL PUBLIC LICENSE</a>
+ <ul>
+ <li><a id="TOC2" href="#SEC2">Präambel</a></li>
+ <li><a id="TOC3" href="#SEC3">BEDINGUNGEN FÃR DIE VERVIELFAÌLTIGUNG,
VERBREITUNG
+UND MODIFIZIERUNG</a></li>
+ <li><a id="TOC4" href="#SEC4">Bedingungen auf eigene neue Bibliotheken
+anwenden</a></li>
+ </ul></li>
+</ul>
+
+<hr />
+
+<h3><a id="SEC1" href="#TOC1">GNU GENERAL PUBLIC LICENSE</a></h3>
+<p>
+Version 2, June 1991
+</p>
+
+<pre>
+Copyright (C) 1989, 1991 Free Software Foundation, Inc.
+51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA
+
+Everyone is permitted to copy and distribute verbatim copies
+of this license document, but changing it is not allowed.
+</pre>
+
+<h3><a id="preamble"></a><a id="SEC2" href="#TOC2">Preamble</a></h3>
+
+<p>
+ The licenses for most software are designed to take away your freedom to
+share and change it. By contrast, the GNU General Public License is
+intended to guarantee your freedom to share and change free software--to
+make sure the software is free for all its users. This General Public
+License applies to most of the Free Software Foundation's software and to
+any other program whose authors commit to using it. (Some other Free
+Software Foundation software is covered by the GNU Lesser General Public
+License instead.) You can apply it to your programs, too.
+</p>
+
+<p>
+ When we speak of free software, we are referring to freedom, not price. Our
+General Public Licenses are designed to make sure that you have the freedom
+to distribute copies of free software (and charge for this service if you
+wish), that you receive source code or can get it if you want it, that you
+can change the software or use pieces of it in new free programs; and that
+you know you can do these things.
+</p>
+
+<p>
+ To protect your rights, we need to make restrictions that forbid anyone to
+deny you these rights or to ask you to surrender the rights. These
+restrictions translate to certain responsibilities for you if you distribute
+copies of the software, or if you modify it.
+</p>
+
+<p>
+ For example, if you distribute copies of such a program, whether gratis or
+for a fee, you must give the recipients all the rights that you have. You
+must make sure that they, too, receive or can get the source code. And you
+must show them these terms so they know their rights.
+</p>
+
+<p>
+ We protect your rights with two steps: (1) copyright the software, and (2)
+offer you this license which gives you legal permission to copy, distribute
+and/or modify the software.
+</p>
+
+<p>
+ Also, for each author's protection and ours, we want to make certain that
+everyone understands that there is no warranty for this free software. If
+the software is modified by someone else and passed on, we want its
+recipients to know that what they have is not the original, so that any
+problems introduced by others will not reflect on the original authors'
+reputations.
+</p>
+
+<p>
+ Finally, any free program is threatened constantly by software patents. We
+wish to avoid the danger that redistributors of a free program will
+individually obtain patent licenses, in effect making the program
+proprietary. To prevent this, we have made it clear that any patent must be
+licensed for everyone's free use or not licensed at all.
+</p>
+
+<p>
+ The precise terms and conditions for copying, distribution and modification
+follow.
+</p>
+
+
+<h3><a id="terms"></a><a id="SEC3" href="#TOC3">TERMS AND CONDITIONS FOR
+COPYING, DISTRIBUTION AND MODIFICATION</a></h3>
+
+
+<a id="section0"></a><p>
+<strong>0.</strong> This License applies to any program or other work which
+contains a notice placed by the copyright holder saying it may be
+distributed under the terms of this General Public License. The "Program",
+below, refers to any such program or work, and a "work based on the Program"
+means either the Program or any derivative work under copyright law: that is
+to say, a work containing the Program or a portion of it, either verbatim or
+with modifications and/or translated into another language. (Hereinafter,
+translation is included without limitation in the term "modification".)
+Each licensee is addressed as "you".
+</p>
+
+<p>
+Activities other than copying, distribution and modification are not covered
+by this License; they are outside its scope. The act of running the Program
+is not restricted, and the output from the Program is covered only if its
+contents constitute a work based on the Program (independent of having been
+made by running the Program). Whether that is true depends on what the
+Program does.
+</p>
+
+<a id="section1"></a><p>
+<strong>1.</strong> You may copy and distribute verbatim copies of the
+Program's source code as you receive it, in any medium, provided that you
+conspicuously and appropriately publish on each copy an appropriate
+copyright notice and disclaimer of warranty; 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 this License along with the
+Program.
+</p>
+
+<p>
+You may charge a fee for the physical act of transferring a copy, and you
+may at your option offer warranty protection in exchange for a fee.
+</p>
+
+<a id="section2"></a><p>
+<strong>2.</strong> You may modify your copy or copies of the Program or any
+portion of it, thus forming a work based on the Program, and copy and
+distribute such modifications or work under the terms of Section 1 above,
+provided that you also meet all of these conditions:
+</p>
+
+<dl>
+ <dt></dt>
+ <dd>
+ <strong>a)</strong> You must cause the modified files to carry prominent
+notices stating that you changed the files and the date of any change.
+ </dd>
+ <dt></dt>
+ <dd>
+ <strong>b)</strong> You must cause any work that you distribute or
publish,
+that in whole or in part contains or is derived from the Program or any part
+thereof, to be licensed as a whole at no charge to all third parties under
+the terms of this License.
+ </dd>
+ <dt></dt>
+ <dd>
+ <strong>c)</strong> If the modified program normally reads commands
+interactively when run, you must cause it, when started running for such
+interactive use in the most ordinary way, to print or display an
+announcement including an appropriate copyright notice and a notice that
+there is no warranty (or else, saying that you provide a warranty) and that
+users may redistribute the program under these conditions, and telling the
+user how to view a copy of this License. (Exception: if the Program itself
+is interactive but does not normally print such an announcement, your work
+based on the Program is not required to print an announcement.)
+ </dd>
+</dl>
+
+<p>
+These requirements apply to the modified work as a whole. If identifiable
+sections of that work are not derived from the Program, and can be
+reasonably considered independent and separate works in themselves, then
+this License, and its terms, do not apply to those sections when you
+distribute them as separate works. But when you distribute the same
+sections as part of a whole which is a work based on the Program, the
+distribution of the whole must be on the terms of this License, whose
+permissions for other licensees extend to the entire whole, and thus to each
+and every part regardless of who wrote it.
+</p>
+
+<p>
+Thus, it is not the intent of this section to claim rights or contest your
+rights to work written entirely by you; rather, the intent is to exercise
+the right to control the distribution of derivative or collective works
+based on the Program.
+</p>
+
+<p>
+In addition, mere aggregation of another work not based on the Program with
+the Program (or with a work based on the Program) on a volume of a storage
+or distribution medium does not bring the other work under the scope of this
+License.
+</p>
+
+<a id="section3"></a><p>
+<strong>3.</strong> You may copy and distribute the Program (or a work based
+on it, under Section 2) in object code or executable form under the terms of
+Sections 1 and 2 above provided that you also do one of the following:
+</p>
+
+<!-- we use this doubled UL to get the sub-sections indented, -->
+<!-- while making the bullets as unobvious as possible. -->
+<dl>
+ <dt></dt>
+ <dd>
+ <strong>a)</strong> Accompany it with the complete corresponding
+machine-readable source code, which must be distributed under the terms of
+Sections 1 and 2 above on a medium customarily used for software
+interchange; or,
+ </dd>
+ <dt></dt>
+ <dd>
+ <strong>b)</strong> Accompany it with a written offer, valid for at least
+three years, to give any third party, for a charge no more than your cost of
+physically performing source distribution, a complete machine-readable copy
+of the corresponding source code, to be distributed under the terms of
+Sections 1 and 2 above on a medium customarily used for software
+interchange; or,
+ </dd>
+ <dt></dt>
+ <dd>
+ <strong>c)</strong> Accompany it with the information you received as to
the
+offer to distribute corresponding source code. (This alternative is allowed
+only for noncommercial distribution and only if you received the program in
+object code or executable form with such an offer, in accord with Subsection
+b above.)
+ </dd>
+</dl>
+
+<p>
+The source code for a work means the preferred form of the work for making
+modifications to it. For an executable work, complete source code means all
+the source code for all modules it contains, plus any associated interface
+definition files, plus the scripts used to control compilation and
+installation of the executable. However, as a special exception, the source
+code distributed need not include anything that is normally distributed (in
+either source or binary form) with the major components (compiler, kernel,
+and so on) of the operating system on which the executable runs, unless that
+component itself accompanies the executable.
+</p>
+
+<p>
+If distribution of executable or object code is made by offering access to
+copy from a designated place, then offering equivalent access to copy the
+source code from the same place counts as distribution of the source code,
+even though third parties are not compelled to copy the source along with
+the object code.
+</p>
+
+<a id="section4"></a><p>
+<strong>4.</strong> You may not copy, modify, sublicense, or distribute the
+Program except as expressly provided under this License. Any attempt
+otherwise to copy, modify, sublicense or distribute the Program is void, and
+will automatically terminate your rights under this License. However,
+parties who have received copies, or rights, from you under this License
+will not have their licenses terminated so long as such parties remain in
+full compliance.
+</p>
+
+<a id="section5"></a><p>
+<strong>5.</strong> You are not required to accept this License, since you
+have not signed it. However, nothing else grants you permission to modify
+or distribute the Program or its derivative works. These actions are
+prohibited by law if you do not accept this License. Therefore, by
+modifying or distributing the Program (or any work based on 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.
+</p>
+
+<a id="section6"></a><p>
+<strong>6.</strong> Each time you redistribute the Program (or any work
+based on the Program), the recipient automatically receives a license from
+the original licensor to copy, distribute or modify the Program subject to
+these terms and conditions. You may not impose any further restrictions on
+the recipients' exercise of the rights granted herein. You are not
+responsible for enforcing compliance by third parties to this License.
+</p>
+
+<a id="section7"></a><p>
+<strong>7.</strong> If, as a consequence of a court judgment or allegation
+of patent infringement or for any other reason (not limited to patent
+issues), conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License. If you cannot distribute so
+as to satisfy simultaneously your obligations under this License and any
+other pertinent obligations, then as a consequence you may not distribute
+the Program at all. For example, if a patent license would not permit
+royalty-free redistribution of the Program by all those who receive copies
+directly or indirectly through you, then the only way you could satisfy both
+it and this License would be to refrain entirely from distribution of the
+Program.
+</p>
+
+<p>
+If any portion of this section is held invalid or unenforceable under any
+particular circumstance, the balance of the section is intended to apply and
+the section as a whole is intended to apply in other circumstances.
+</p>
+
+<p>
+It is not the purpose of this section to induce you to infringe any patents
+or other property right claims or to contest validity of any such claims;
+this section has the sole purpose of protecting the integrity of the free
+software distribution system, which is implemented by public license
+practices. Many people have made generous contributions to the wide range
+of software distributed through that system in reliance on consistent
+application of that system; it is up to the author/donor to decide if he or
+she is willing to distribute software through any other system and a
+licensee cannot impose that choice.
+</p>
+
+<p>
+This section is intended to make thoroughly clear what is believed to be a
+consequence of the rest of this License.
+</p>
+
+<a id="section8"></a><p>
+<strong>8.</strong> If the distribution and/or use of the Program is
+restricted in certain countries either by patents or by copyrighted
+interfaces, the original copyright holder who places the Program under this
+License may add an explicit geographical distribution limitation excluding
+those countries, so that distribution is permitted only in or among
+countries not thus excluded. In such case, this License incorporates the
+limitation as if written in the body of this License.
+</p>
+
+<a id="section9"></a><p>
+<strong>9.</strong> The Free Software Foundation may publish revised and/or
+new versions of the General Public License from time to time. Such new
+versions will be similar in spirit to the present version, but may differ in
+detail to address new problems or concerns.
+</p>
+
+<p>
+Each version is given a distinguishing version number. If the Program
+specifies a version number of this License which applies to it and "any
+later version", you have the option of following the terms and conditions
+either of that version or of any later version published by the Free
+Software Foundation. If the Program does not specify a version number of
+this License, you may choose any version ever published by the Free Software
+Foundation.
+</p>
+
+<a id="section10"></a><p>
+<strong>10.</strong> If you wish to incorporate parts of the Program into
+other free programs whose distribution conditions are different, write to
+the author to ask for permission. For software which is copyrighted by the
+Free Software Foundation, write to the Free Software Foundation; we
+sometimes make exceptions for this. Our decision will be guided by the two
+goals of preserving the free status of all derivatives of our free software
+and of promoting the sharing and reuse of software generally.
+</p>
+
+<a id="section11"></a><p><strong>NO WARRANTY</strong></p>
+
+<p>
+<strong>11.</strong> BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE
+IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.
+EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER
+PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER
+EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. 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.
+</p>
+
+<a id="section12"></a><p>
+<strong>12.</strong> IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED
+TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY
+AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR
+DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES
+ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT
+LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES
+SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE
+WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN
+ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
+</p>
+
+<h3>END OF TERMS AND CONDITIONS</h3>
+
+<h3><a id="howto"></a><a id="SEC4" href="#TOC4">Bedingungen auf eigene neue
+Bibliotheken anwenden</a></h3>
+
+<p>
+ Wenn Sie ein neues Programm entwickeln und von gröÃtmöglichem Nutzen für
die
+Allgemeinheit sein soll, ist der beste Weg dies zu erreichen Freie Software,
+die jeder, unter diesen Bedingungen, weiterverbreiten und verändern kann.
+</p>
+
+<p>
+ Dazu fügen Sie folgende Hinweise zum Programm hinzu. Am sichersten ist es,
+den Hinweis am Anfang jeder Quelldatei anzubringen, um den Ausschluss jeder
+Gewährleistung am wirksamsten zu vermitteln; und jede Datei sollte
+mindestens eine <em>Copyright</em>-Zeile und einen Verweis auf den
+vollständigen Hinweis enthalten.
+</p>
+
+<pre>
+ <var>Eine Zeile mit dem Namen der Bibliothek und dem Zweck.</var>
+ Copyright (C) <var>JJJJ</var> <var>Name des Autors</var>
+
+<span xml:lang="en"> This program is free software; you can redistribute it
and/or
+ modify it under the terms of the GNU General Public License
+ as published by the Free Software Foundation; either version 2
+ of the License, or (at your option) any later version.
+
+ This program is distributed in the hope that it will be useful,
+ but WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+ GNU General Public License for more details.
+
+ You should have received a copy of the GNU General Public License
+ along with this program; if not, write to the Free Software
+ Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301,
USA.</span>
+
+<span class="translation"> Dieses Programm ist Freie Software: Sie können
es unter den Bedingungen
+ der GNU General Public License, wie von der Free Software Foundation,
+ Version 2 der Lizenz oder (nach Ihrer Option) jeder neueren
+ veröffentlichten Version, weiterverbreiten und/oder modifizieren.
+
+ Dieses Programm wird in der Hoffnung, dass es nützlich sein wird, aber
+ OHNE JEDE GEWÃHRLEISTUNG, bereitgestellt; sogar ohne die implizite
+ Gewährleistung der MARKTFÃHIGKEIT oder EIGNUNG FÃR EINEN BESTIMMTEN
ZWECK.
+ Siehe die GNU General Public License für weitere Details.
+
+ Sie sollten eine Kopie der GNU General Public License zusammen mit diesem
+ Programm erhalten haben. Wenn nicht, schreiben Sie an die Free Software
+ Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301,
USA.</span>
+</pre>
+
+<p>
+Fügen Sie auÃerdem Informationen hinzu, wie man Sie per E-Mail und Brief
+kontaktieren kann.
+</p>
+
+<p>
+Ist das Programm interaktiv, blenden Sie einen kurzen Hinweis ein, wenn es
+in diesem Modus ausgeführt wird:
+</p>
+
+<pre>
+ <samp>Gnomovision, Version 69, Copyright (C) <var>JJJJ</var> <var>Name des
Autors</var>
+ <span xml:lang="en">Gnomovision comes with ABSOLUTELY NO WARRANTY; for
details
+ type show w. This is free software, and you are welcome
+ to redistribute it under certain conditions; type ‚show c‘
+ for details.</span>
+
+ Gnomovision wird OHNE JEDE GEWÃHRLEISTUNG angeboten; Details
+ unter ‚show w‘. Dies ist Freie Software und darf unter
+ bestimmten Bedingungen weitergeben werden; siehe ‚<span
xml:lang="en">show c</span>‘
+ für Details.</samp>
+</pre>
+
+<p>
+Die hypothetischen Befehle <samp>‚<span xml:lang="en">show
+w</span>‘</samp> und <samp xml:lang="en">‚show c‘</samp>
+sollten die entsprechenden Teile der General Public License
+anzeigen. Natürlich können die verwendeten Befehle anders als genannt
+werden; es sind auch Mausklicks oder Menüpunkte ‑ was auch
+immer sinnvoll ist ‑ möglich.
+</p>
+
+<p>
+Sie sollten sich von Ihren Arbeitgeber (wenn Sie als ProgrammiererIn
+arbeiten) oder ggf. von der Schule ein <em>Copyright-Verzicht</em> für das
+Programm unterschreiben lassen. Ein Beispiel:
+</p>
+
+
+<pre>
+ <samp>Yoyodyne, Inc. verzichtet hiermit auf alle
+ Copyright-Interessen an dem von
+ James Hacker
+ geschriebenen Programm ‚Gnomovision‘
+ (welches Compilerdurchläufe macht).
+
+ <var>1989-04-01, Unterschrift von Ty Coon</var>
+ Ty Coon, stellv. Vizepräsident</samp>
+</pre>
+
+<p>
+Diese General Public License gestattet nicht die Einbindung Ihres Programms
+in proprietäre Programme. Ist Ihr Programm eine Unterprogrammbibliothek,
+kann es sinnvoller sein, das Linken proprietärer Programme mit dieser
+Bibliothek zu erlauben. Sollte dies der Fall sein, verwenden Sie statt
+dieser die <a href="/licenses/lgpl-3.0">GNU Lesser General Public License
+(LGPL)</a>.
+</p>
+
+
+<div style="font-size: small;">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't have notes.-->
+ </div>
+</div>
+
+<!--#include virtual="/server/footer.de.html" -->
+<div id="footer">
+
+<p>
+Bitte senden Sie Fragen zur FSF & GNU an <a
+href="mailto:address@hidden";><address@hidden></a>. Sie können auch die
<a
+href="/contact/contact">Free Software Foundation kontaktieren</a>.
+<br />
+Bitte senden Sie ungültige Verweise und andere Korrekturen oder Vorschläge
+an <a
+href="mailto:address@hidden";><address@hidden></a>.
+</p>
+
+<p>
+Bitte beachten Sie die <a
+href="/server/standards/README.translations">LIESMICH für Ãbersetzungen</a>,
+um weitere Informationen Ãber die Koordinierung und Einsendung von
+Ãbersetzungen zu erhalten.
+</p>
+
+<p>
+Copyright-Hinweis siehe oben.</p>
+<address><!--51 Franklin Street, Fifth Floor, Boston, MA 02110-1301,
USA--></address>
+<p>
+Die unveränderte Vervielfältigung und Verbreitung dieses gesamten Textes
+<!--sind weltweit --> ist ohne Lizenzgebühren und mit jedem Medium, sofern
+dieser Hinweis<!-- und der Copyright-Hinweis--> angegeben ist, erlaubt.
+</p>
+
+
+<div class="translators-credits">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.-->
+<strong>Ãbersetzung:</strong> Joerg Kohne, 2011.</div>
+ <p>
+<!-- timestamp start -->
+Aktualisierung:
+
+$Date: 2011/10/29 16:35:41 $
+
+<!-- timestamp end -->
+</p>
+</div>
+
+<!-- <div id="translations">
+ -->
+<!-- <h4>
+Translations of this page</h4> -->
+<!-- -->
+<!-- Please keep this list alphabetical by language code. -->
+<!-- Comment what the language is for each type, i.e. de is German. -->
+<!-- Write the language name in its own language (Deutsch) in the text. -->
+<!-- If you add a new language here, please -->
+<!-- advise address@hidden and add it to -->
+<!-- - /home/www/html/server/standards/README.translations.html -->
+<!-- - one of the lists under the section "Translations Underway" -->
+<!-- - if there is a translation team, you also have to add an alias -->
+<!-- to mail.gnu.org:/com/mailer/aliases -->
+<!-- Please also check you have the language code right; see: -->
+<!-- http://www.loc.gov/standards/iso639-2/php/code_list.php -->
+<!-- If the 2-letter ISO 639-1 code is not available, -->
+<!-- use the 3-letter ISO 639-2. -->
+<!-- Please use W3C normative character entities. -->
+<!-- -->
+<!-- <gnun>
+<ul class="translations-list"> -->
+<!-- Czech -->
+<!-- <li><a
href="/licenses/old-licenses/gpl-2.0.cs.html">Česky</a> [cs]</li>
-->
+<!-- English -->
+<!-- <li><a
href="/licenses/old-licenses/gpl-2.0.html">English</a> [en]</li> -->
+<!-- Japanese -->
+<!-- <li><a
href="/licenses/old-licenses/gpl-2.0.ja.html">日本語</a> [ja]</li>
-->
+<!-- </ul></gnun> -->
+<!-- </div>
+ -->
+</div>
+</body>
+</html>
Index: lgpl-2.0.de.html
===================================================================
RCS file: lgpl-2.0.de.html
diff -N lgpl-2.0.de.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ lgpl-2.0.de.html 29 Oct 2011 16:35:41 -0000 1.1
@@ -0,0 +1,732 @@
+
+<!--#include virtual="/server/header.de.html" -->
+
+<!-- This file is automatically generated by GNUnited Nations! -->
+<title>GNU Library General Public License (LGPL) v2.0 - GNU Projekt - Free
Software
+Foundation (FSF)</title>
+
+<!--#include virtual="/server/banner.de.html" -->
+<!--#include virtual="/licenses/old-licenses/po/lgpl-2.0.translist" -->
+<h2>GNU Library General Public License, Version 2.0</h2>
+
+<div class="announcement">
+<blockquote><p>
+<strong>Hinweis: Die GNU Library General Public License wurde von der <a
+href="/licenses/lgpl-3.0">GNU Lesser General Public License (LGPL)</a>
+abgelöst.</strong>
+</p></blockquote>
+</div>
+
+<p>Wir bitten eindringlich, die <a href="/licenses/lgpl-3.0">GNU Lesser General
+Public License (LGPL)</a> anstelle dieser GNU Library GPL zu verwenden. Die
+Library GPL dient als historische Referenz.</p>
+
+<ul>
+ <li><a href="/licenses/why-not-lgpl">Warum man die GNU LGPL nicht für die
+nächste Bibliothek verwenden sollte</a></li>
+ <li><a href="/licenses/gpl-violation">GNU LGPL: Was ist bei einer möglichen
+Verletzung zu tun</a></li>
+ <li>Die GNU LGPLv2.0 in anderen Formaten (engl.): <a
+href="/licenses/old-licenses/lgpl-2.0.txt">Nur Text</a>, <a
+href="/licenses/old-licenses/lgpl-2.0-standalone.html">Nur HTML</a>
+ </li>
+ <li><a href="/licenses/old-licenses/old-licenses.de.html#LGPL">Alte Versionen
+der GNU LGPL</a></li>
+</ul>
+
+<hr />
+
+<h3>Inhalt</h3>
+<ul>
+<li><!--TRANSLATORS: Don't translate the license; copy msgid's
+verbatim!-->
+<a id="TOC1" href="#SEC1">GNU LIBRARY GENERAL PUBLIC LICENSE</a>
+<ul>
+<li><a id="TOC2" href="#SEC2">Präambel</a></li>
+<li><a id="TOC3" href="#SEC3">BEDINGUNGEN FÃR DIE VERVIELFÃLTIGUNG,
VERBREITUNG
+UND MODIFIZIERUNG</a></li>
+<li><a id="TOC4" href="#SEC4">Bedingungen auf eigene neue Bibliotheken
+anwenden</a></li>
+</ul></li>
+</ul>
+
+<hr />
+
+<h3><a id="SEC1" href="#TOC1">GNU LIBRARY GENERAL PUBLIC LICENSE</a></h3>
+<p>
+Version 2, June 1991
+</p>
+
+<pre>
+Copyright (C) 1991 Free Software Foundation, Inc.
+51 Franklin St, Fifth Floor, Boston, MA 02110-1301, USA
+Everyone is permitted to copy and distribute verbatim copies
+of this license document, but changing it is not allowed.
+
+[This is the first released version of the library GPL. It is
+ numbered 2 because it goes with version 2 of the ordinary GPL.]
+</pre>
+
+<h3><a id="SEC2" href="#TOC2">Preamble</a></h3>
+
+<p>
+ The licenses for most software are designed to take away your freedom to
+share and change it. By contrast, the GNU General Public Licenses are
+intended to guarantee your freedom to share and change free software--to
+make sure the software is free for all its users.
+</p>
+
+<p>
+ This license, the Library General Public License, applies to some specially
+designated Free Software Foundation software, and to any other libraries
+whose authors decide to use it. You can use it for your libraries, too.
+</p>
+
+<p>
+ When we speak of free software, we are referring to freedom, not price. Our
+General Public Licenses are designed to make sure that you have the freedom
+to distribute copies of free software (and charge for this service if you
+wish), that you receive source code or can get it if you want it, that you
+can change the software or use pieces of it in new free programs; and that
+you know you can do these things.
+</p>
+
+<p>
+ To protect your rights, we need to make restrictions that forbid anyone to
+deny you these rights or to ask you to surrender the rights. These
+restrictions translate to certain responsibilities for you if you distribute
+copies of the library, or if you modify it.
+</p>
+
+<p>
+ For example, if you distribute copies of the library, whether gratis or for
+a fee, you must give the recipients all the rights that we gave you. You
+must make sure that they, too, receive or can get the source code. If you
+link a program with the library, you must provide complete object files to
+the recipients so that they can relink them with the library, after making
+changes to the library and recompiling it. And you must show them these
+terms so they know their rights.
+</p>
+
+<p>
+ Our method of protecting your rights has two steps: (1) copyright the
+library, and (2) offer you this license which gives you legal permission to
+copy, distribute and/or modify the library.
+</p>
+
+<p>
+ Also, for each distributor's protection, we want to make certain that
+everyone understands that there is no warranty for this free library. If
+the library is modified by someone else and passed on, we want its
+recipients to know that what they have is not the original version, so that
+any problems introduced by others will not reflect on the original authors'
+reputations.
+</p>
+
+<p>
+ Finally, any free program is threatened constantly by software patents. We
+wish to avoid the danger that companies distributing free software will
+individually obtain patent licenses, thus in effect transforming the program
+into proprietary software. To prevent this, we have made it clear that any
+patent must be licensed for everyone's free use or not licensed at all.
+</p>
+
+<p>
+ Most GNU software, including some libraries, is covered by the ordinary GNU
+General Public License, which was designed for utility programs. This
+license, the GNU Library General Public License, applies to certain
+designated libraries. This license is quite different from the ordinary
+one; be sure to read it in full, and don't assume that anything in it is the
+same as in the ordinary license.
+</p>
+
+<p>
+ The reason we have a separate public license for some libraries is that they
+blur the distinction we usually make between modifying or adding to a
+program and simply using it. Linking a program with a library, without
+changing the library, is in some sense simply using the library, and is
+analogous to running a utility program or application program. However, in
+a textual and legal sense, the linked executable is a combined work, a
+derivative of the original library, and the ordinary General Public License
+treats it as such.
+</p>
+
+<p>
+ Because of this blurred distinction, using the ordinary General Public
+License for libraries did not effectively promote software sharing, because
+most developers did not use the libraries. We concluded that weaker
+conditions might promote sharing better.
+</p>
+
+<p>
+ However, unrestricted linking of non-free programs would deprive the users
+of those programs of all benefit from the free status of the libraries
+themselves. This Library General Public License is intended to permit
+developers of non-free programs to use free libraries, while preserving your
+freedom as a user of such programs to change the free libraries that are
+incorporated in them. (We have not seen how to achieve this as regards
+changes in header files, but we have achieved it as regards changes in the
+actual functions of the Library.) The hope is that this will lead to faster
+development of free libraries.
+</p>
+
+<p>
+ The precise terms and conditions for copying, distribution and modification
+follow. Pay close attention to the difference between a "work based on the
+library" and a "work that uses the library". The former contains code
+derived from the library, while the latter only works together with the
+library.
+</p>
+
+<p>
+ Note that it is possible for a library to be covered by the ordinary General
+Public License rather than by this special one.
+</p>
+
+<h3><a id="SEC3" href="#TOC3">TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION
AND
+MODIFICATION</a></h3>
+
+<p>
+<strong>0.</strong> This License Agreement applies to any software library
+which contains a notice placed by the copyright holder or other authorized
+party saying it may be distributed under the terms of this Library General
+Public License (also called "this License"). Each licensee is addressed as
+"you".
+</p>
+<p>
+ A "library" means a collection of software functions and/or data prepared so
+as to be conveniently linked with application programs (which use some of
+those functions and data) to form executables.
+</p>
+<p>
+ The "Library", below, refers to any such software library or work which has
+been distributed under these terms. A "work based on the Library" means
+either the Library or any derivative work under copyright law: that is to
+say, a work containing the Library or a portion of it, either verbatim or
+with modifications and/or translated straightforwardly into another
+language. (Hereinafter, translation is included without limitation in the
+term "modification".)
+</p>
+<p>
+ "Source code" for a work means the preferred form of the work for making
+modifications to it. For a library, complete source code means all the
+source code for all modules it contains, plus any associated interface
+definition files, plus the scripts used to control compilation and
+installation of the library.
+</p>
+<p>
+ Activities other than copying, distribution and modification are not covered
+by this License; they are outside its scope. The act of running a program
+using the Library is not restricted, and output from such a program is
+covered only if its contents constitute a work based on the Library
+(independent of the use of the Library in a tool for writing it). Whether
+that is true depends on what the Library does and what the program that uses
+the Library does.
+</p>
+<p>
+<strong>1.</strong> You may copy and distribute verbatim copies of the
+Library's complete source code as you receive it, in any medium, provided
+that you conspicuously and appropriately publish on each copy an appropriate
+copyright notice and disclaimer of warranty; keep intact all the notices
+that refer to this License and to the absence of any warranty; and
+distribute a copy of this License along with the Library.
+</p>
+<p>
+ You may charge a fee for the physical act of transferring a copy, and you
+may at your option offer warranty protection in exchange for a fee.
+</p>
+<p>
+<strong>2.</strong> You may modify your copy or copies of the Library or any
+portion of it, thus forming a work based on the Library, and copy and
+distribute such modifications or work under the terms of Section 1 above,
+provided that you also meet all of these conditions:
+</p>
+
+<!-- we use this doubled UL to get the sub-sections indented, -->
+<!-- while making the bullets as unobvious as possible. -->
+<ul>
+
+<li><strong>a)</strong> The modified work must itself be a software library.
+</li>
+
+<li><strong>b)</strong> You must cause the files modified to carry prominent
+notices stating that you changed the files and the date of any change.
+</li>
+
+<li><strong>c)</strong> You must cause the whole of the work to be licensed at
+no charge to all third parties under the terms of this License.
+</li>
+
+<li><strong>d)</strong> If a facility in the modified Library refers to a
+function or a table of data to be supplied by an application program that
+uses the facility, other than as an argument passed when the facility is
+invoked, then you must make a good faith effort to ensure that, in the event
+an application does not supply such function or table, the facility still
+operates, and performs whatever part of its purpose remains meaningful.
+ <p>
+ (For example, a function in a library to compute square roots has a
purpose
+that is entirely well-defined independent of the application. Therefore,
+Subsection 2d requires that any application-supplied function or table used
+by this function must be optional: if the application does not supply it,
+the square root function must still compute square roots.)</p>
+</li>
+</ul>
+
+<p>
+These requirements apply to the modified work as a whole. If identifiable
+sections of that work are not derived from the Library, and can be
+reasonably considered independent and separate works in themselves, then
+this License, and its terms, do not apply to those sections when you
+distribute them as separate works. But when you distribute the same
+sections as part of a whole which is a work based on the Library, the
+distribution of the whole must be on the terms of this License, whose
+permissions for other licensees extend to the entire whole, and thus to each
+and every part regardless of who wrote it.
+</p>
+<p>
+Thus, it is not the intent of this section to claim rights or contest your
+rights to work written entirely by you; rather, the intent is to exercise
+the right to control the distribution of derivative or collective works
+based on the Library.
+</p>
+<p>
+In addition, mere aggregation of another work not based on the Library with
+the Library (or with a work based on the Library) on a volume of a storage
+or distribution medium does not bring the other work under the scope of this
+License.
+</p>
+<p>
+<strong>3.</strong> You may opt to apply the terms of the ordinary GNU
+General Public License instead of this License to a given copy of the
+Library. To do this, you must alter all the notices that refer to this
+License, so that they refer to the ordinary GNU General Public License,
+version 2, instead of to this License. (If a newer version than version 2
+of the ordinary GNU General Public License has appeared, then you can
+specify that version instead if you wish.) Do not make any other change in
+these notices.
+</p>
+<p>
+ Once this change is made in a given copy, it is irreversible for that copy,
+so the ordinary GNU General Public License applies to all subsequent copies
+and derivative works made from that copy.
+</p>
+<p>
+ This option is useful when you wish to copy part of the code of the Library
+into a program that is not a library.
+</p>
+<p>
+<strong>4.</strong> You may copy and distribute the Library (or a portion or
+derivative of it, under Section 2) in object code or executable form under
+the terms of Sections 1 and 2 above provided that you accompany it with the
+complete corresponding machine-readable source code, which must be
+distributed under the terms of Sections 1 and 2 above on a medium
+customarily used for software interchange.
+</p>
+<p>
+ If distribution of object code is made by offering access to copy from a
+designated place, then offering equivalent access to copy the source code
+from the same place satisfies the requirement to distribute the source code,
+even though third parties are not compelled to copy the source along with
+the object code.
+</p>
+<p>
+<strong>5.</strong> A program that contains no derivative of any portion of
+the Library, but is designed to work with the Library by being compiled or
+linked with it, is called a "work that uses the Library". Such a work, in
+isolation, is not a derivative work of the Library, and therefore falls
+outside the scope of this License.
+</p>
+<p>
+ However, linking a "work that uses the Library" with the Library creates an
+executable that is a derivative of the Library (because it contains portions
+of the Library), rather than a "work that uses the library". The executable
+is therefore covered by this License. Section 6 states terms for
+distribution of such executables.
+</p>
+<p>
+ When a "work that uses the Library" uses material from a header file that is
+part of the Library, the object code for the work may be a derivative work
+of the Library even though the source code is not. Whether this is true is
+especially significant if the work can be linked without the Library, or if
+the work is itself a library. The threshold for this to be true is not
+precisely defined by law.
+</p>
+<p>
+ If such an object file uses only numerical parameters, data structure
+layouts and accessors, and small macros and small inline functions (ten
+lines or less in length), then the use of the object file is unrestricted,
+regardless of whether it is legally a derivative work. (Executables
+containing this object code plus portions of the Library will still fall
+under Section 6.)
+</p>
+<p>
+ Otherwise, if the work is a derivative of the Library, you may distribute
+the object code for the work under the terms of Section 6. Any executables
+containing that work also fall under Section 6, whether or not they are
+linked directly with the Library itself.
+</p>
+<p>
+<strong>6.</strong> As an exception to the Sections above, you may also
+compile or link a "work that uses the Library" with the Library to produce a
+work containing portions of the Library, and distribute that work under
+terms of your choice, provided that the terms permit modification of the
+work for the customer's own use and reverse engineering for debugging such
+modifications.
+</p>
+<p>
+ You must give prominent notice with each copy of the work that the Library
+is used in it and that the Library and its use are covered by this License.
+You must supply a copy of this License. If the work during execution
+displays copyright notices, you must include the copyright notice for the
+Library among them, as well as a reference directing the user to the copy of
+this License. Also, you must do one of these things:
+</p>
+
+<!-- we use this doubled UL to get the sub-sections indented, -->
+<!-- while making the bullets as unobvious as possible. -->
+<ul>
+<li><strong>a)</strong> Accompany the work with the complete corresponding
+machine-readable source code for the Library including whatever changes were
+used in the work (which must be distributed under Sections 1 and 2 above);
+and, if the work is an executable linked with the Library, with the complete
+machine-readable "work that uses the Library", as object code and/or source
+code, so that the user can modify the Library and then relink to produce a
+modified executable containing the modified Library. (It is understood that
+the user who changes the contents of definitions files in the Library will
+not necessarily be able to recompile the application to use the modified
+definitions.)
+</li>
+
+<li><strong>b)</strong> Accompany the work with a written offer, valid for at
+least three years, to give the same user the materials specified in
+Subsection 6a, above, for a charge no more than the cost of performing this
+distribution.
+</li>
+
+<li><strong>c)</strong> If distribution of the work is made by offering access
+to copy from a designated place, offer equivalent access to copy the above
+specified materials from the same place.
+</li>
+
+<li><strong>d)</strong> Verify that the user has already received a copy of
+these materials or that you have already sent this user a copy.
+</li>
+</ul>
+
+<p>
+ For an executable, the required form of the "work that uses the Library"
+must include any data and utility programs needed for reproducing the
+executable from it. However, as a special exception, the source code
+distributed need not include anything that is normally distributed (in
+either source or binary form) with the major components (compiler, kernel,
+and so on) of the operating system on which the executable runs, unless that
+component itself accompanies the executable.
+</p>
+<p>
+ It may happen that this requirement contradicts the license restrictions of
+other proprietary libraries that do not normally accompany the operating
+system. Such a contradiction means you cannot use both them and the Library
+together in an executable that you distribute.
+</p>
+<p>
+<strong>7.</strong> You may place library facilities that are a work based
+on the Library side-by-side in a single library together with other library
+facilities not covered by this License, and distribute such a combined
+library, provided that the separate distribution of the work based on the
+Library and of the other library facilities is otherwise permitted, and
+provided that you do these two things:
+</p>
+
+<!-- we use this doubled UL to get the sub-sections indented, -->
+<!-- while making the bullets as unobvious as possible. -->
+<ul>
+<li><strong>a)</strong> Accompany the combined library with a copy of the same
+work based on the Library, uncombined with any other library facilities.
+This must be distributed under the terms of the Sections above.
+</li>
+
+<li><strong>b)</strong> Give prominent notice with the combined library of the
+fact that part of it is a work based on the Library, and explaining where to
+find the accompanying uncombined form of the same work.
+</li>
+</ul>
+
+<p>
+<strong>8.</strong> You may not copy, modify, sublicense, link with, or
+distribute the Library except as expressly provided under this License. Any
+attempt otherwise to copy, modify, sublicense, link with, or distribute the
+Library is void, and will automatically terminate your rights under this
+License. However, parties who have received copies, or rights, from you
+under this License will not have their licenses terminated so long as such
+parties remain in full compliance.
+</p>
+<p>
+<strong>9.</strong> You are not required to accept this License, since you
+have not signed it. However, nothing else grants you permission to modify
+or distribute the Library or its derivative works. These actions are
+prohibited by law if you do not accept this License. Therefore, by
+modifying or distributing the Library (or any work based on the Library),
+you indicate your acceptance of this License to do so, and all its terms and
+conditions for copying, distributing or modifying the Library or works based
+on it.
+</p>
+<p>
+<strong>10.</strong> Each time you redistribute the Library (or any work
+based on the Library), the recipient automatically receives a license from
+the original licensor to copy, distribute, link with or modify the Library
+subject to these terms and conditions. You may not impose any further
+restrictions on the recipients' exercise of the rights granted herein. You
+are not responsible for enforcing compliance by third parties to this
+License.
+</p>
+<p>
+<strong>11.</strong> If, as a consequence of a court judgment or allegation
+of patent infringement or for any other reason (not limited to patent
+issues), conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License. If you cannot distribute so
+as to satisfy simultaneously your obligations under this License and any
+other pertinent obligations, then as a consequence you may not distribute
+the Library at all. For example, if a patent license would not permit
+royalty-free redistribution of the Library by all those who receive copies
+directly or indirectly through you, then the only way you could satisfy both
+it and this License would be to refrain entirely from distribution of the
+Library.
+</p>
+<p>
+If any portion of this section is held invalid or unenforceable under any
+particular circumstance, the balance of the section is intended to apply,
+and the section as a whole is intended to apply in other circumstances.
+</p>
+<p>
+It is not the purpose of this section to induce you to infringe any patents
+or other property right claims or to contest validity of any such claims;
+this section has the sole purpose of protecting the integrity of the free
+software distribution system which is implemented by public license
+practices. Many people have made generous contributions to the wide range
+of software distributed through that system in reliance on consistent
+application of that system; it is up to the author/donor to decide if he or
+she is willing to distribute software through any other system and a
+licensee cannot impose that choice.
+</p>
+<p>
+This section is intended to make thoroughly clear what is believed to be a
+consequence of the rest of this License.
+</p>
+<p>
+<strong>12.</strong> If the distribution and/or use of the Library is
+restricted in certain countries either by patents or by copyrighted
+interfaces, the original copyright holder who places the Library under this
+License may add an explicit geographical distribution limitation excluding
+those countries, so that distribution is permitted only in or among
+countries not thus excluded. In such case, this License incorporates the
+limitation as if written in the body of this License.
+</p>
+<p>
+<strong>13.</strong> The Free Software Foundation may publish revised and/or
+new versions of the Library General Public License from time to time. Such
+new versions will be similar in spirit to the present version, but may
+differ in detail to address new problems or concerns.
+</p>
+<p>
+Each version is given a distinguishing version number. If the Library
+specifies a version number of this License which applies to it and "any
+later version", you have the option of following the terms and conditions
+either of that version or of any later version published by the Free
+Software Foundation. If the Library does not specify a license version
+number, you may choose any version ever published by the Free Software
+Foundation.
+</p>
+<p>
+<strong>14.</strong> If you wish to incorporate parts of the Library into
+other free programs whose distribution conditions are incompatible with
+these, write to the author to ask for permission. For software which is
+copyrighted by the Free Software Foundation, write to the Free Software
+Foundation; we sometimes make exceptions for this. Our decision will be
+guided by the two goals of preserving the free status of all derivatives of
+our free software and of promoting the sharing and reuse of software
+generally.
+</p>
+
+<p><strong>NO WARRANTY</strong></p>
+
+<p>
+<strong>15.</strong> BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE
+IS NO WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW.
+EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER
+PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER
+EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
+TO THE QUALITY AND PERFORMANCE OF THE LIBRARY IS WITH YOU. SHOULD THE
+LIBRARY PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
+REPAIR OR CORRECTION.
+</p>
+<p>
+<strong>16.</strong> IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED
+TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY
+AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU FOR
+DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES
+ARISING OUT OF THE USE OR INABILITY TO USE THE LIBRARY (INCLUDING BUT NOT
+LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES
+SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE LIBRARY TO OPERATE
+WITH ANY OTHER SOFTWARE), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN
+ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
+</p>
+
+<h3>END OF TERMS AND CONDITIONS</h3>
+
+<h3><a id="SEC4" href="#TOC4">Bedingungen auf eigene neue Bibliotheken
+anwenden</a></h3>
+
+<p>
+ Wenn Sie eine neue Bibliothek entwickeln und diese von gröÃtmöglichen
Nutzen
+für die Allgemeinheit sein soll, empfehlen wir, sie als Freie Software
+anzubieten, die jeder weiterverbreiten und verändern kann. Dies können Sie
+durch die Möglichkeit der Weitergabe unter diesen Bedingungen (oder
+alternativ unter den Bedingungen der GNU General Public License) erlauben.
+</p>
+<p>
+ Um diese Bedingungen anzuwenden, fügen Sie folgende Hinweise der Bibliothek,
+am sichersten am Anfang jeder Quelldatei, hinzu, um den Ausschluss der
+Gewährleistung effektiv zu vermitteln; jede Datei sollte mindestens eine
+<em>Copyright</em>-Zeile und einen Verweis enthalten, wo die vollständigen
+Hinweise gefunden werden.
+</p>
+
+<pre>
+ <var>Eine Zeile mit dem Namen der Bibliothek und dem Zweck.</var>
+ Copyright (C) <var>Jahr</var> <var>Name des Autors</var>
+
+<span xml:lang="en"> This library is free software; you can redistribute it
and/or
+ modify it under the terms of the GNU Library General Public
+ License as published by the Free Software Foundation; either
+ version 2 of the License, or (at your option) any later version.
+
+ This library is distributed in the hope that it will be useful,
+ but WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
+ Library General Public License for more details.
+
+ You should have received a copy of the GNU Library General Public
+ License along with this library; if not, write to the
+ Free Software Foundation, Inc., 51 Franklin St, Fifth Floor,
+ Boston, MA 02110-1301, USA.</span>
+
+<span class="translation"> Diese Bibliothek ist Freie Software: Sie können
sie unter den
+ Bedingungen der GNU Library General Public, wie von der Free Software
+ Foundation, Version 2 der Lizenz oder (nach Ihrer Option) jeder späteren
+ veröffentlichten Version, weiterverbreiten und/oder modifizieren.
+
+ Diese Bibliothek wird in der Hoffnung, dass sie nützlich sein wird, aber
+ OHNE JEDE GEWÃHRLEISTUNG, bereitgestellt; sogar ohne die implizite
+ Gewährleistung der MARKTFÃHIGKEIT oder EIGNUNG FÃR EINEN BESTIMMTEN
+ ZWECK. Siehe die Library General Public License für weitere Details.
+
+ Sie sollten eine Kopie der GNU Library General Public zusammen mit
+ dieser Bibliothek erhalten haben. Wenn nicht, schreiben Sie an Free
+ Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston,
+ MA 02110-1301, USA.</span>
+</pre>
+
+<p>
+Fügen Sie auÃerdem Informationen hinzu, wie man Sie per E-Mail und Brief
+kontaktieren kann.
+</p>
+<p>
+Sie sollten sich von Ihren Arbeitgeber (wenn Sie als ProgrammiererIn
+arbeiten) oder ggf. von der Schule ein <em>Copyright-Verzicht</em> für die
+Bibliothek unterschreiben lassen. Ein Beispiel:
+</p>
+
+<pre>
+ <samp>Yoyodyne, Inc. verzichtet hiermit auf alle
+ Copyright-Interessen an der von
+ James Random Hacker
+ geschriebenen Bibliothek ‚Frob‘
+ (eine Bibliothek, um Knöpfe zu optimieren).
+
+ <var>1990-04-01, Unterschrift von Ty Coon</var>
+ Ty Coon, stellv. Vizepräsident</samp>
+</pre>
+
+<p>
+Das ist alles, fertig!</p>
+
+
+<div style="font-size: small;">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't have notes.-->
+ </div>
+</div>
+
+<!--#include virtual="/server/footer.de.html" -->
+<div id="footer">
+
+<p>
+Bitte senden Sie Fragen zur FSF & GNU an <a
+href="mailto:address@hidden";><address@hidden></a>. Sie können auch die
<a
+href="/contact/contact">Free Software Foundation kontaktieren</a>.
+<br />
+Bitte senden Sie ungültige Verweise und andere Korrekturen oder Vorschläge
+an <a
+href="mailto:address@hidden";><address@hidden></a>.
+</p>
+
+<p>
+Bitte beachten Sie die <a
+href="/server/standards/README.translations">LIESMICH für Ãbersetzungen</a>,
+um weitere Informationen über die Koordinierung und Einsendung von
+Ãbersetzungen zu erhalten.
+</p>
+
+<p>
+Copyright-Hinweis siehe oben.</p>
+<address><!-- --></address>
+
+
+<div class="translators-credits">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.-->
+<strong>Ãbersetzung:</strong> Joerg Kohne, 2011.</div>
+ <p>
+<!-- timestamp start -->
+Aktualisierung:
+
+$Date: 2011/10/29 16:35:41 $
+
+<!-- timestamp end -->
+</p>
+</div>
+
+<!-- <div id="translations">
+ -->
+<!-- <h4>
+Translations of this page</h4> -->
+<!-- -->
+<!-- Please keep this list alphabetical by language code. -->
+<!-- Comment what the language is for each type, i.e. de is German. -->
+<!-- Write the language name in its own language (Deutsch) in the text. -->
+<!-- If you add a new language here, please -->
+<!-- advise address@hidden and add it to -->
+<!-- - /home/www/html/server/standards/README.translations.html -->
+<!-- - one of the lists under the section "Translations Underway" -->
+<!-- - if there is a translation team, you also have to add an alias -->
+<!-- to mail.gnu.org:/com/mailer/aliases -->
+<!-- Please also check you have the language code right; see: -->
+<!-- http://www.loc.gov/standards/iso639-2/php/code_list.php -->
+<!-- If the 2-letter ISO 639-1 code is not available, -->
+<!-- use the 3-letter ISO 639-2. -->
+<!-- Please use W3C normative character entities. -->
+<!-- -->
+<!-- <gnun>
+<ul class="translations-list"> -->
+<!-- English -->
+<!-- <li><a
href="/licenses/old-licenses/lgpl-2.0.html">English</a> [en]</li> -->
+<!-- Japanese -->
+<!-- <li><a
href="/licenses/old-licenses/lgpl-2.0.ja.html">日本語</a> [ja]</li>
-->
+<!-- </ul></gnun> -->
+<!-- </div>
+ -->
+</div>
+</body>
+</html>
Index: lgpl-2.1-translations.de.html
===================================================================
RCS file: lgpl-2.1-translations.de.html
diff -N lgpl-2.1-translations.de.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ lgpl-2.1-translations.de.html 29 Oct 2011 16:35:41 -0000 1.1
@@ -0,0 +1,267 @@
+
+
+<!--#include virtual="/server/header.de.html" -->
+
+<!-- This file is automatically generated by GNUnited Nations! -->
+<title>Inoffizielle Ãbersetzungen der GNU LGPLv2.1 - GNU Projekt - Free
Software
+Foundation (FSF)</title>
+<meta http-equiv="keywords" content=" " />
+
+<!--#include virtual="/server/banner.de.html" -->
+<!--#include
virtual="/licenses/old-licenses/po/lgpl-2.1-translations.translist" -->
+<h2>Inoffizielle Ãbersetzungen der GNU LGPLv2.1</h2>
+
+<h3 id="UnofficialTranslations">Informationen über inoffizielle
Ãbersetzungen</h3>
+
+<p>
+Der Grund, warum die FSF diese Ãbersetzungen als nicht offiziell gültig
+genehmigt, ist, dass deren Ãberprüfung schwierig und teuer wäre (es wird die
+Hilfe zweisprachiger Juristen in anderen Ländern benötigt). Schlimmer noch,
+wenn ein Fehler durchrutscht, könnten die Ergebnisse für die gesamte
+Freie-Software-Gemeinschaft katastrophal sein. Solange die Ãbersetzungen
+inoffiziell sind, können sie keinen Schaden anrichten.</p>
+
+<p>Die Ãbersetzungen sollen mehr Menschen helfen, die GNU LGPL zu verstehen.
+Ãbersetzungen müssen grundsätzlich genau sein, wenn auch nicht perfekt. Für
+eine gute Ãbersetzung ist es unerlässlich, grundlegende Konzepte wie <a
+href="/copyleft/copyleft">Copyleft</a> und die <a
+href="/philosophy/free-sw">Definition von Freie Software</a> vollständig
+verstanden zu haben. Aus diesem Grund sollten diejenigen, die Ãbersetzungen
+beitragen möchten, sich vergewissern, dass sie gut mit sowohl diesen
+Konzepten als auch anderen philosophischen Prinzipien, die im Dokument
+auftauchen können, vertraut sind.</p>
+
+<p>Wir erteilen die Berechtigung, Ãbersetzungen der GNU GPL, GNU LGPL, GNU
AGPL
+und GNU FDL in andere Sprachen zu veröffentlichen, unter folgendem
+Vorbehalt:</p>
+
+<ol>
+
+<li>Die Ãbersetzung wird als inoffiziell bezeichnet, um darüber zu
informieren,
+dass sie kein rechtlicher Ersatz für die verbindliche Fassung ist
+(Informationen hierzu siehe unten).</li>
+
+<li>AÌnderungen auf unseren Wunsch hin eingepflegt werden, wenn wir von GNUs
+Freunden erfahren, dass AÌnderungen notwendig sind, die Ãbersetzung
+verständlicher zu machen.</li>
+
+<li>Die Ãbersetzung wird nicht auf einem kommerziellen Webauftritt gehostet
und
+bezieht sich auf keine Unternehmen.</li>
+
+<li>Der Webauftritt, der die Ãbersetzung enthält, sollte keine Verweise mit
+Ausnahme zur fsf.org und gnu.org enthalten. Wir akzeptieren möglicherweise
+Verweise auf andere freie Softwarepakete, aber bevorzugen sie zu
vermeiden.</li>
+
+<li>Der Webauftritt sollte darauf hinweisen, dass sie unter irgendeiner Version
+der <em>Creative Commons Namensnennung-Keine Bearbeitung-Lizenz</em>
+freigegeben ist.</li>
+
+<li>Wir können auch kleinere Ausnahmen dieser Regel in älteren Fällen, die
+schwer zu beheben sind, akzeptieren.</li>
+
+</ol>
+
+<p>Wir verweisen nicht unbedingt auf alle inoffiziellen Ãbersetzungen, von der
+wir in jeder Sprache wissen. Wenn bspw. eine inoffizielle Ãbersetzung von
+einem freien Softwareunternehmen gemacht wurde, das wir kennen und dem wir
+vertrauen, verweisen wir eher auf diese Ãbersetzung anstatt einer
+anderen. Wir können sie zwar noch nicht offiziell machen, aber erwarten,
+dass es wahrscheinlich hauptsächlich richtig ist.</p>
+
+<p>
+Ãm die Ãbersetzungen als inoffiziell zu beschriften, fügen Sie folgenden
+Text am Anfang hinzu, sowohl in Englisch und in der Sprache der
+Ãbersetzung ‑ tauschen Sie <em>language</em> durch die
+verwendete Sprache aus:</p>
+<blockquote dir="ltr"><p>
+
+<!--TRANSLATORS: If you translate this paragraph, retain the English
+text and put your translation below. The entire <blockquote>
+ element
+has dir="ltr" to work by default with RTL languages when the notice is
+not translated, so if your language is RTL, you *must* put your
+translation within <span dir="rtl">.-->
+<span xml:lang="en" lang="en">This is an unofficial translation of the GNU
+General Public License into <tt>language</tt>. It was not published by the
+Free Software Foundation, and does not legally state the distribution terms
+for software that uses the GNU GPL—only the original English text of
+the GNU GPL does that. However, we hope that this translation will help
+<tt>language</tt> speakers understand the GNU GPL better.</span><br /><br />
+
+<span class="translation">Dies ist eine inoffizielle Ãbersetzung der GNU
+General Public License in <tt>Deutsch</tt>. Sie wurde nicht von der Free
+Software Foundation freigegeben und ist keine rechtsverbindliche
+Vertriebsbedingung für Software, die GNU GPL lizenziert
+ist ‑ dies kann nur der englische Originaltext der
+GNU GPL. Dennoch hoffen wir, dass diese Ãbersetzung
+<tt>deutschsprachigen</tt> Personen helfen wird, die GNU GPL besser zu
+verstehen.</span>
+</p></blockquote>
+<p>
+Möchten Sie eine Lizenz übersetzen, informieren Sie bitte die <em>GNU
+Translation Manager</em> <a
+href="mailto:address@hidden";><address@hidden></a>.
+Sie überprüfen, ob die Ãbersetzung den oben genannten Richtlinien folgt und
+legen einen Verweis darauf an.</p>
+
+<p>
+Um leicht nach Ãbersetzungen suchen zu können, verwenden Sie bitte den
+Sprachcode in eckigen Klammern.
+</p>
+
+<!-- Please keep entries alphabetical by language name. -->
+<ul>
+
+ <!-- these translations have links other than to www.fsf.org and www.gnu.org
+ <li>
+<code>[cn]</code> <a href="http://gnu.freehostingguru.com/lgpl/";>Chinese
(Simplified)</a>
+ translation of the LGPL</li>
+-->
+<li><code>[zh-tw]</code> Chinesisch (traditionell): <a
+href="http://www.linux.org.tw/CLDP/OLD/doc/LGPL.html";>HTML</a></li>
+
+<!-- these translations have links other than to www.fsf.org and www.gnu.org
+ <li>
+<code>[de]</code> <a
href="http://www.gnu.de/documents/lgpl-2.1.de.html";>German</a>
+ translation of the LGPL</li>
+ <li><code>[el]</code> <a href="http://www.eexi.gr/?q=node/25";>Greek</a>
+ translation of the LGPL</li>
+ <li><code>[hu]</code> <a href="http://gnu.hu/lgpl.html";>Hungarian</a>
+ translation of the LGPL</li>
+ <li><code>[it]</code> <a
href="http://softwarelibero.it/gnudoc/lgpl.it.txt";>Italian</a>
+ translation of the LGPL</li>
+-->
+<!-- these translations have links other than to www.fsf.org and www.gnu.org
+ <li>
+<code>[ja]</code> <a
href="http://www.opensource.jp/lesser/lgpl.ja.html.euc-jp";>Japanese</a>
+ translation of the LGPL</li>
+-->
+<!-- hosted on gnu.org
+ <li>
+<code>[ko]</code> <a
href="http://korea.gnu.org/people/chsong/copyleft/lgpl.ko.html";>Korean</a>
+ translation of the LGPL</li>
+-->
+<li><code>[pl]</code> Polnisch: <a
+href="http://www.hyperjump4.republika.pl/gnu/konradgnulgpl.html";>HTML
+(1)</a>, <a
+href="http://www.hyperjump4.republika.pl/gnu/elizagnulgpl.html";>HTML
(2)</a></li>
+
+ <!-- these translations have links other than to www.fsf.org and www.gnu.org
+ <li>
+<code>[ru]</code> <a
href="http://www.infolex.narod.ru/gpl_gnu/lgplrus.html";>Russian</a>
+ translation of the LGPL</li>
+-->
+<li><code>[es]</code> Spanisch: <a
+href="http://gugs.sindominio.net/licencias/lgpl-es.html";>HTML</a></li>
+ <li><!-- these translations have links other than to www.fsf.org and
www.gnu.org
+(<a
+ href="http://www.belgeler.org/howto/lgpl.html";>
+2</a>)
+-->
+<code>[tr]</code> Türkisch: <a
+href="http://www.arayan.com/da/lgpl_tr.html";>HTML</a>
+</li>
+
+<!-- dead link as of 2011-06-26
+ <li>
+<code>[vi]</code> <a href="http://vi.wikisource.org/wiki/LGPL";>
+ Vietnamese</a> translation of the LGPL</li>
+-->
+</ul>
+
+
+<div style="font-size: small;">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't have notes.-->
+ </div>
+</div>
+
+<!--#include virtual="/server/footer.de.html" -->
+<div id="footer">
+
+<p>
+Bitte senden Sie Fragen zur FSF & GNU an <a
+href="mailto:address@hidden";><address@hidden></a>. Sie können auch die
<a
+href="/contact/contact">Free Software Foundation kontaktieren</a>.
+<br />
+Bitte senden Sie ungültige Verweise und andere Korrekturen oder Vorschläge
+an <a
+href="mailto:address@hidden";><address@hidden></a>.
+</p>
+
+<p>
+Bitte beachten Sie die <a
+href="/server/standards/README.translations">LIESMICH für Ãbersetzungen</a>,
+um weitere Informationen über die Koordinierung und Einsendung von
+Ãbersetzungen zu erhalten.
+</p>
+
+<p>
+Copyright © 1996, 1997, 1998, 1999, 2004, 2005, 2006, 2007, 2008, 2009
+Free Software Foundation, Inc.
+</p>
+<p>Dieses Werk bzw. Inhalt steht unter einer <a rel="license"
+href="http://creativecommons.org/licenses/by-nd/3.0/us/deed.de";>Creative
+Commons Namensnennung-Keine Bearbeitung 3.0 Vereinigte Staaten von Amerika
+Lizenz</a>.
+</p>
+
+
+<div class="translators-credits">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.-->
+<strong>Ãbersetzung:</strong> Joerg Kohne, 2011.</div>
+ <p>
+<!-- timestamp start -->
+Aktualisierung:
+
+$Date: 2011/10/29 16:35:41 $
+
+<!-- timestamp end -->
+</p>
+</div>
+
+<!-- <div id="translations">
+ -->
+<!-- <h4>
+Translations of this page</h4> -->
+<!-- -->
+<!-- Please keep this list alphabetical by language code. -->
+<!-- Comment what the language is for each type, i.e. de is German. -->
+<!-- Write the language name in its own language (Deutsch) in the text. -->
+<!-- If you add a new language here, please -->
+<!-- advise address@hidden and add it to -->
+<!-- - /home/www/html/server/standards/README.translations.html -->
+<!-- - one of the lists under the section "Translations Underway" -->
+<!-- - if there is a translation team, you also have to add an alias -->
+<!-- to mail.gnu.org:/com/mailer/aliases -->
+<!-- Please also check you have the language code right; see: -->
+<!-- http://www.loc.gov/standards/iso639-2/php/code_list.php -->
+<!-- If the 2-letter ISO 639-1 code is not available, -->
+<!-- use the 3-letter ISO 639-2. -->
+<!-- Please use W3C normative character entities. -->
+<!-- -->
+<!-- <gnun>
+<ul class="translations-list"> -->
+<!-- Catalan -->
+<!-- <li><a
href="/licenses/old-licenses/lgpl-2.1-translations.ca.html">català</a> [ca]</li>
-->
+<!-- English -->
+<!-- <li><a
href="/licenses/old-licenses/lgpl-2.1-translations.html">English</a> [en]</li>
-->
+<!-- French -->
+<!-- <li><a
href="/licenses/old-licenses/lgpl-2.1-translations.fr.html">français</a> [fr]</li>
-->
+<!-- Japanese -->
+<!-- <li><a
href="/licenses/old-licenses/lgpl-2.1-translations.ja.html">日本語</a> [ja]</li>
-->
+<!-- Korean -->
+<!-- <li><a
href="/licenses/old-licenses/lgpl-2.1-translations.ko.html">한국어</a> [ko]</li>
-->
+<!-- Polish -->
+<!-- <li><a
href="/licenses/old-licenses/lgpl-2.1-translations.pl.html">polski</a> [pl]</li>
-->
+<!-- Chinese (Simplified) -->
+<!-- <li><a
href="/licenses/old-licenses/lgpl-2.1-translations.zh-cn.html">简体中文</a> [zh-cn]</li>
-->
+<!-- Chinese( Traditional) -->
+<!-- <li><a
href="/licenses/old-licenses/lgpl-2.1-translations.zh-tw.html">繁體中文</a> [zh-tw]</li>
-->
+<!-- </ul></gnun> -->
+<!-- </div>
+ -->
+</div>
+</body>
+</html>
Index: lgpl-2.1.de.html
===================================================================
RCS file: lgpl-2.1.de.html
diff -N lgpl-2.1.de.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ lgpl-2.1.de.html 29 Oct 2011 16:35:41 -0000 1.1
@@ -0,0 +1,720 @@
+
+<!--#include virtual="/server/header.de.html" -->
+
+<!-- This file is automatically generated by GNUnited Nations! -->
+<title>GNU Library General Public License (LGPL) v2.1 - GNU Projekt - Free
Software
+Foundation (FSF)</title>
+<link rel="alternate" type="application/rdf+xml" href="lgpl-2.1.rdf" />
+
+<!--#include virtual="/server/banner.de.html" -->
+<!--#include virtual="/licenses/old-licenses/po/lgpl-2.1.translist" -->
+<h2>GNU Lesser General Public License, Version 2.1</h2>
+
+
+<ul>
+ <li><a href="/licenses/why-not-lgpl">Warum man die GNU LGPL nicht für die
+nächste Bibliothek verwenden sollte</a></li>
+ <li><a href="/licenses/gpl-violation">GNU LGPL: Was ist bei einer möglichen
+Verletzung zu tun</a></li>
+ <li><a href="/licenses/old-licenses/lgpl-2.1-translations">Ãbersetzungen der
+LGPLv2.1</a></li>
+ <li>Die GNU LGPLv2.1 in anderen Formaten (engl.): <a href="lgpl-2.1.txt">Nur
+Text</a>, <a href="lgpl-2.1.texi">Texinfo</a>, <a
+href="lgpl-2.1-standalone.html">Nur HTML</a>, <a
+href="lgpl-2.1.dbk">Docbook</a>
+ </li>
+ <li><a href="/licenses/old-licenses/old-licenses.de.html#LGPL">Alte Versionen
+der GNU LGPL</a></li>
+</ul>
+
+<hr />
+
+<p>
+Diese GNU Lesser General Public License gilt als der Nachfolger der GNU
+Library General Public License. Eine Erläuterung, warum diese Ãnderung
+notwendig war, finden Sie unter <a href="/licenses/why-not-lgpl">Warum man
+die GNU LGPL nicht für die nächste Bibliothek verwenden sollte</a>.</p>
+
+
+<h3>Inhalt</h3>
+<ul>
+<li><!--TRANSLATORS: Don't translate the license; copy msgid's verbatim!-->
+<a id="TOC1" href="#SEC1">GNU LESSER GENERAL PUBLIC LICENSE</a>
+<ul>
+<li><a id="TOC2" href="#SEC2">Präambel</a></li>
+<li><a id="TOC3" href="#SEC3">BEDINGUNGEN FÃR DIE VERVIELFÃLTIGUNG,
VERBREITUNG
+UND MODIFIZIERUNG</a></li>
+<li><a id="TOC4" href="#SEC4">Bedingungen auf eigene neue Bibliotheken
+anwenden</a></li>
+</ul></li>
+</ul>
+
+<hr />
+
+<h3><a id="SEC1" href="#TOC1">GNU LESSER GENERAL PUBLIC LICENSE</a></h3>
+<p>
+Version 2.1, February 1999
+</p>
+
+<pre>
+Copyright (C) 1991, 1999 Free Software Foundation, Inc.
+51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
+Everyone is permitted to copy and distribute verbatim copies
+of this license document, but changing it is not allowed.
+
+[This is the first released version of the Lesser GPL. It also counts
+ as the successor of the GNU Library Public License, version 2, hence
+ the version number 2.1.]
+</pre>
+
+
+<h3><a id="SEC2" href="#TOC2">Preamble</a></h3>
+
+<p>
+ The licenses for most software are designed to take away your freedom to
+share and change it. By contrast, the GNU General Public Licenses are
+intended to guarantee your freedom to share and change free software--to
+make sure the software is free for all its users.
+</p>
+<p>
+ This license, the Lesser General Public License, applies to some specially
+designated software packages--typically libraries--of the Free Software
+Foundation and other authors who decide to use it. You can use it too, but
+we suggest you first think carefully about whether this license or the
+ordinary General Public License is the better strategy to use in any
+particular case, based on the explanations below.
+</p>
+<p>
+ When we speak of free software, we are referring to freedom of use, not
+price. Our General Public Licenses are designed to make sure that you have
+the freedom to distribute copies of free software (and charge for this
+service if you wish); that you receive source code or can get it if you want
+it; that you can change the software and use pieces of it in new free
+programs; and that you are informed that you can do these things.
+</p>
+<p>
+ To protect your rights, we need to make restrictions that forbid
+distributors to deny you these rights or to ask you to surrender these
+rights. These restrictions translate to certain responsibilities for you if
+you distribute copies of the library or if you modify it.
+</p>
+<p>
+ For example, if you distribute copies of the library, whether gratis or for
+a fee, you must give the recipients all the rights that we gave you. You
+must make sure that they, too, receive or can get the source code. If you
+link other code with the library, you must provide complete object files to
+the recipients, so that they can relink them with the library after making
+changes to the library and recompiling it. And you must show them these
+terms so they know their rights.
+</p>
+<p>
+ We protect your rights with a two-step method: (1) we copyright the library,
+and (2) we offer you this license, which gives you legal permission to copy,
+distribute and/or modify the library.
+</p>
+<p>
+ To protect each distributor, we want to make it very clear that there is no
+warranty for the free library. Also, if the library is modified by someone
+else and passed on, the recipients should know that what they have is not
+the original version, so that the original author's reputation will not be
+affected by problems that might be introduced by others.
+</p>
+<p>
+ Finally, software patents pose a constant threat to the existence of any
+free program. We wish to make sure that a company cannot effectively
+restrict the users of a free program by obtaining a restrictive license from
+a patent holder. Therefore, we insist that any patent license obtained for
+a version of the library must be consistent with the full freedom of use
+specified in this license.
+</p>
+<p>
+ Most GNU software, including some libraries, is covered by the ordinary GNU
+General Public License. This license, the GNU Lesser General Public
+License, applies to certain designated libraries, and is quite different
+from the ordinary General Public License. We use this license for certain
+libraries in order to permit linking those libraries into non-free programs.
+</p>
+<p>
+ When a program is linked with a library, whether statically or using a
+shared library, the combination of the two is legally speaking a combined
+work, a derivative of the original library. The ordinary General Public
+License therefore permits such linking only if the entire combination fits
+its criteria of freedom. The Lesser General Public License permits more lax
+criteria for linking other code with the library.
+</p>
+<p>
+ We call this license the "Lesser" General Public License because it does
+Less to protect the user's freedom than the ordinary General Public
+License. It also provides other free software developers Less of an
+advantage over competing non-free programs. These disadvantages are the
+reason we use the ordinary General Public License for many libraries.
+However, the Lesser license provides advantages in certain special
+circumstances.
+</p>
+<p>
+ For example, on rare occasions, there may be a special need to encourage the
+widest possible use of a certain library, so that it becomes a de-facto
+standard. To achieve this, non-free programs must be allowed to use the
+library. A more frequent case is that a free library does the same job as
+widely used non-free libraries. In this case, there is little to gain by
+limiting the free library to free software only, so we use the Lesser
+General Public License.
+</p>
+<p>
+ In other cases, permission to use a particular library in non-free programs
+enables a greater number of people to use a large body of free software.
+For example, permission to use the GNU C Library in non-free programs
+enables many more people to use the whole GNU operating system, as well as
+its variant, the GNU/Linux operating system.
+</p>
+<p>
+ Although the Lesser General Public License is Less protective of the users'
+freedom, it does ensure that the user of a program that is linked with the
+Library has the freedom and the wherewithal to run that program using a
+modified version of the Library.
+</p>
+<p>
+ The precise terms and conditions for copying, distribution and modification
+follow. Pay close attention to the difference between a "work based on the
+library" and a "work that uses the library". The former contains code
+derived from the library, whereas the latter must be combined with the
+library in order to run.
+</p>
+
+<h3><a id="SEC3" href="#TOC3">TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION
AND
+MODIFICATION</a></h3>
+
+
+<p>
+<strong>0.</strong> This License Agreement applies to any software library
+or other program which contains a notice placed by the copyright holder or
+other authorized party saying it may be distributed under the terms of this
+Lesser General Public License (also called "this License"). Each licensee
+is addressed as "you".
+</p>
+<p>
+ A "library" means a collection of software functions and/or data prepared so
+as to be conveniently linked with application programs (which use some of
+those functions and data) to form executables.
+</p>
+<p>
+ The "Library", below, refers to any such software library or work which has
+been distributed under these terms. A "work based on the Library" means
+either the Library or any derivative work under copyright law: that is to
+say, a work containing the Library or a portion of it, either verbatim or
+with modifications and/or translated straightforwardly into another
+language. (Hereinafter, translation is included without limitation in the
+term "modification".)
+</p>
+<p>
+ "Source code" for a work means the preferred form of the work for making
+modifications to it. For a library, complete source code means all the
+source code for all modules it contains, plus any associated interface
+definition files, plus the scripts used to control compilation and
+installation of the library.
+</p>
+<p>
+ Activities other than copying, distribution and modification are not covered
+by this License; they are outside its scope. The act of running a program
+using the Library is not restricted, and output from such a program is
+covered only if its contents constitute a work based on the Library
+(independent of the use of the Library in a tool for writing it). Whether
+that is true depends on what the Library does and what the program that uses
+the Library does.
+</p>
+<p>
+<strong>1.</strong> You may copy and distribute verbatim copies of the
+Library's complete source code as you receive it, in any medium, provided
+that you conspicuously and appropriately publish on each copy an appropriate
+copyright notice and disclaimer of warranty; keep intact all the notices
+that refer to this License and to the absence of any warranty; and
+distribute a copy of this License along with the Library.
+</p>
+<p>
+ You may charge a fee for the physical act of transferring a copy, and you
+may at your option offer warranty protection in exchange for a fee.
+</p>
+<p>
+<strong>2.</strong> You may modify your copy or copies of the Library or any
+portion of it, thus forming a work based on the Library, and copy and
+distribute such modifications or work under the terms of Section 1 above,
+provided that you also meet all of these conditions:
+</p>
+
+<ul>
+ <li><strong>a)</strong> The modified work must itself be a software
library.</li>
+ <li><strong>b)</strong> You must cause the files modified to carry prominent
+notices stating that you changed the files and the date of any change.</li>
+
+ <li><strong>c)</strong> You must cause the whole of the work to be licensed
at
+no charge to all third parties under the terms of this License.</li>
+
+ <li><strong>d)</strong> If a facility in the modified Library refers to a
+function or a table of data to be supplied by an application program that
+uses the facility, other than as an argument passed when the facility is
+invoked, then you must make a good faith effort to ensure that, in the event
+an application does not supply such function or table, the facility still
+operates, and performs whatever part of its purpose remains meaningful.
+ <p>
+ (For example, a function in a library to compute square roots has a
purpose
+that is entirely well-defined independent of the application. Therefore,
+Subsection 2d requires that any application-supplied function or table used
+by this function must be optional: if the application does not supply it,
+the square root function must still compute square roots.)</p></li>
+</ul>
+
+<p>
+These requirements apply to the modified work as a whole. If identifiable
+sections of that work are not derived from the Library, and can be
+reasonably considered independent and separate works in themselves, then
+this License, and its terms, do not apply to those sections when you
+distribute them as separate works. But when you distribute the same
+sections as part of a whole which is a work based on the Library, the
+distribution of the whole must be on the terms of this License, whose
+permissions for other licensees extend to the entire whole, and thus to each
+and every part regardless of who wrote it.
+</p>
+<p>
+Thus, it is not the intent of this section to claim rights or contest your
+rights to work written entirely by you; rather, the intent is to exercise
+the right to control the distribution of derivative or collective works
+based on the Library.
+</p>
+<p>
+In addition, mere aggregation of another work not based on the Library with
+the Library (or with a work based on the Library) on a volume of a storage
+or distribution medium does not bring the other work under the scope of this
+License.
+</p>
+<p>
+<strong>3.</strong> You may opt to apply the terms of the ordinary GNU
+General Public License instead of this License to a given copy of the
+Library. To do this, you must alter all the notices that refer to this
+License, so that they refer to the ordinary GNU General Public License,
+version 2, instead of to this License. (If a newer version than version 2
+of the ordinary GNU General Public License has appeared, then you can
+specify that version instead if you wish.) Do not make any other change in
+these notices.
+</p>
+<p>
+ Once this change is made in a given copy, it is irreversible for that copy,
+so the ordinary GNU General Public License applies to all subsequent copies
+and derivative works made from that copy.
+</p>
+<p>
+ This option is useful when you wish to copy part of the code of the Library
+into a program that is not a library.
+</p>
+<p>
+<strong>4.</strong> You may copy and distribute the Library (or a portion or
+derivative of it, under Section 2) in object code or executable form under
+the terms of Sections 1 and 2 above provided that you accompany it with the
+complete corresponding machine-readable source code, which must be
+distributed under the terms of Sections 1 and 2 above on a medium
+customarily used for software interchange.
+</p>
+<p>
+ If distribution of object code is made by offering access to copy from a
+designated place, then offering equivalent access to copy the source code
+from the same place satisfies the requirement to distribute the source code,
+even though third parties are not compelled to copy the source along with
+the object code.
+</p>
+<p>
+<strong>5.</strong> A program that contains no derivative of any portion of
+the Library, but is designed to work with the Library by being compiled or
+linked with it, is called a "work that uses the Library". Such a work, in
+isolation, is not a derivative work of the Library, and therefore falls
+outside the scope of this License.
+</p>
+<p>
+ However, linking a "work that uses the Library" with the Library creates an
+executable that is a derivative of the Library (because it contains portions
+of the Library), rather than a "work that uses the library". The executable
+is therefore covered by this License. Section 6 states terms for
+distribution of such executables.
+</p>
+<p>
+ When a "work that uses the Library" uses material from a header file that is
+part of the Library, the object code for the work may be a derivative work
+of the Library even though the source code is not. Whether this is true is
+especially significant if the work can be linked without the Library, or if
+the work is itself a library. The threshold for this to be true is not
+precisely defined by law.
+</p>
+<p>
+ If such an object file uses only numerical parameters, data structure
+layouts and accessors, and small macros and small inline functions (ten
+lines or less in length), then the use of the object file is unrestricted,
+regardless of whether it is legally a derivative work. (Executables
+containing this object code plus portions of the Library will still fall
+under Section 6.)
+</p>
+<p>
+ Otherwise, if the work is a derivative of the Library, you may distribute
+the object code for the work under the terms of Section 6. Any executables
+containing that work also fall under Section 6, whether or not they are
+linked directly with the Library itself.
+</p>
+<p>
+<strong>6.</strong> As an exception to the Sections above, you may also
+combine or link a "work that uses the Library" with the Library to produce a
+work containing portions of the Library, and distribute that work under
+terms of your choice, provided that the terms permit modification of the
+work for the customer's own use and reverse engineering for debugging such
+modifications.
+</p>
+<p>
+ You must give prominent notice with each copy of the work that the Library
+is used in it and that the Library and its use are covered by this License.
+You must supply a copy of this License. If the work during execution
+displays copyright notices, you must include the copyright notice for the
+Library among them, as well as a reference directing the user to the copy of
+this License. Also, you must do one of these things:
+</p>
+
+<ul>
+ <li><strong>a)</strong> Accompany the work with the complete corresponding
+machine-readable source code for the Library including whatever changes were
+used in the work (which must be distributed under Sections 1 and 2 above);
+and, if the work is an executable linked with the Library, with the complete
+machine-readable "work that uses the Library", as object code and/or source
+code, so that the user can modify the Library and then relink to produce a
+modified executable containing the modified Library. (It is understood that
+the user who changes the contents of definitions files in the Library will
+not necessarily be able to recompile the application to use the modified
+definitions.)</li>
+
+ <li><strong>b)</strong> Use a suitable shared library mechanism for
linking with
+the Library. A suitable mechanism is one that (1) uses at run time a copy
+of the library already present on the user's computer system, rather than
+copying library functions into the executable, and (2) will operate properly
+with a modified version of the library, if the user installs one, as long as
+the modified version is interface-compatible with the version that the work
+was made with.</li>
+
+ <li><strong>c)</strong> Accompany the work with a written offer, valid for
at
+least three years, to give the same user the materials specified in
+Subsection 6a, above, for a charge no more than the cost of performing this
+distribution.</li>
+
+ <li><strong>d)</strong> If distribution of the work is made by offering
access
+to copy from a designated place, offer equivalent access to copy the above
+specified materials from the same place.</li>
+
+ <li><strong>e)</strong> Verify that the user has already received a copy of
+these materials or that you have already sent this user a copy.</li>
+</ul>
+
+<p>
+ For an executable, the required form of the "work that uses the Library"
+must include any data and utility programs needed for reproducing the
+executable from it. However, as a special exception, the materials to be
+distributed need not include anything that is normally distributed (in
+either source or binary form) with the major components (compiler, kernel,
+and so on) of the operating system on which the executable runs, unless that
+component itself accompanies the executable.
+</p>
+<p>
+ It may happen that this requirement contradicts the license restrictions of
+other proprietary libraries that do not normally accompany the operating
+system. Such a contradiction means you cannot use both them and the Library
+together in an executable that you distribute.
+</p>
+<p>
+<strong>7.</strong> You may place library facilities that are a work based
+on the Library side-by-side in a single library together with other library
+facilities not covered by this License, and distribute such a combined
+library, provided that the separate distribution of the work based on the
+Library and of the other library facilities is otherwise permitted, and
+provided that you do these two things:
+</p>
+
+<ul>
+ <li><strong>a)</strong> Accompany the combined library with a copy of the
same
+work based on the Library, uncombined with any other library facilities.
+This must be distributed under the terms of the Sections above.</li>
+
+ <li><strong>b)</strong> Give prominent notice with the combined library of
the
+fact that part of it is a work based on the Library, and explaining where to
+find the accompanying uncombined form of the same work.</li>
+</ul>
+
+<p>
+<strong>8.</strong> You may not copy, modify, sublicense, link with, or
+distribute the Library except as expressly provided under this License. Any
+attempt otherwise to copy, modify, sublicense, link with, or distribute the
+Library is void, and will automatically terminate your rights under this
+License. However, parties who have received copies, or rights, from you
+under this License will not have their licenses terminated so long as such
+parties remain in full compliance.
+</p>
+<p>
+<strong>9.</strong> You are not required to accept this License, since you
+have not signed it. However, nothing else grants you permission to modify
+or distribute the Library or its derivative works. These actions are
+prohibited by law if you do not accept this License. Therefore, by
+modifying or distributing the Library (or any work based on the Library),
+you indicate your acceptance of this License to do so, and all its terms and
+conditions for copying, distributing or modifying the Library or works based
+on it.
+</p>
+<p>
+<strong>10.</strong> Each time you redistribute the Library (or any work
+based on the Library), the recipient automatically receives a license from
+the original licensor to copy, distribute, link with or modify the Library
+subject to these terms and conditions. You may not impose any further
+restrictions on the recipients' exercise of the rights granted herein. You
+are not responsible for enforcing compliance by third parties with this
+License.
+</p>
+<p>
+<strong>11.</strong> If, as a consequence of a court judgment or allegation
+of patent infringement or for any other reason (not limited to patent
+issues), conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License. If you cannot distribute so
+as to satisfy simultaneously your obligations under this License and any
+other pertinent obligations, then as a consequence you may not distribute
+the Library at all. For example, if a patent license would not permit
+royalty-free redistribution of the Library by all those who receive copies
+directly or indirectly through you, then the only way you could satisfy both
+it and this License would be to refrain entirely from distribution of the
+Library.
+</p>
+<p>
+If any portion of this section is held invalid or unenforceable under any
+particular circumstance, the balance of the section is intended to apply,
+and the section as a whole is intended to apply in other circumstances.
+</p>
+<p>
+It is not the purpose of this section to induce you to infringe any patents
+or other property right claims or to contest validity of any such claims;
+this section has the sole purpose of protecting the integrity of the free
+software distribution system which is implemented by public license
+practices. Many people have made generous contributions to the wide range
+of software distributed through that system in reliance on consistent
+application of that system; it is up to the author/donor to decide if he or
+she is willing to distribute software through any other system and a
+licensee cannot impose that choice.
+</p>
+<p>
+This section is intended to make thoroughly clear what is believed to be a
+consequence of the rest of this License.
+</p>
+<p>
+<strong>12.</strong> If the distribution and/or use of the Library is
+restricted in certain countries either by patents or by copyrighted
+interfaces, the original copyright holder who places the Library under this
+License may add an explicit geographical distribution limitation excluding
+those countries, so that distribution is permitted only in or among
+countries not thus excluded. In such case, this License incorporates the
+limitation as if written in the body of this License.
+</p>
+<p>
+<strong>13.</strong> The Free Software Foundation may publish revised and/or
+new versions of the Lesser General Public License from time to time. Such
+new versions will be similar in spirit to the present version, but may
+differ in detail to address new problems or concerns.
+</p>
+<p>
+Each version is given a distinguishing version number. If the Library
+specifies a version number of this License which applies to it and "any
+later version", you have the option of following the terms and conditions
+either of that version or of any later version published by the Free
+Software Foundation. If the Library does not specify a license version
+number, you may choose any version ever published by the Free Software
+Foundation.
+</p>
+<p>
+<strong>14.</strong> If you wish to incorporate parts of the Library into
+other free programs whose distribution conditions are incompatible with
+these, write to the author to ask for permission. For software which is
+copyrighted by the Free Software Foundation, write to the Free Software
+Foundation; we sometimes make exceptions for this. Our decision will be
+guided by the two goals of preserving the free status of all derivatives of
+our free software and of promoting the sharing and reuse of software
+generally.
+</p>
+<p>
+<strong>NO WARRANTY</strong>
+</p>
+<p>
+<strong>15.</strong> BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE
+IS NO WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW.
+EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER
+PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER
+EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
+TO THE QUALITY AND PERFORMANCE OF THE LIBRARY IS WITH YOU. SHOULD THE
+LIBRARY PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
+REPAIR OR CORRECTION.
+</p>
+<p>
+<strong>16.</strong> IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED
+TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY
+AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU FOR
+DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES
+ARISING OUT OF THE USE OR INABILITY TO USE THE LIBRARY (INCLUDING BUT NOT
+LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES
+SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE LIBRARY TO OPERATE
+WITH ANY OTHER SOFTWARE), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN
+ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
+</p>
+
+<h3>END OF TERMS AND CONDITIONS</h3>
+
+<h3><a id="SEC4" href="#TOC4">Bedingungen auf eigene neue Bibliotheken
+anwenden</a></h3>
+<p>
+ Wenn Sie eine neue Bibliothek entwickeln und diese von gröÃtmöglichen
Nutzen
+für die Allgemeinheit sein soll, empfehlen wir, sie als Freie Software
+anzubieten, die jeder weiterverbreiten und verändern kann. Dies können Sie
+durch die Möglichkeit der Weitergabe unter diesen Bedingungen (oder
+alternativ unter den Bedingungen der GNU General Public License) erlauben.
+</p>
+<p>
+ Um diese Bedingungen anzuwenden, fügen Sie folgende Hinweise der Bibliothek,
+am sichersten am Anfang jeder Quelldatei, hinzu, um den Ausschluss der
+Gewährleistung effektiv zu vermitteln; jede Datei sollte mindestens eine
+<em>Copyright</em>-Zeile und einen Verweis enthalten, wo die vollständigen
+Hinweise gefunden werden.
+</p>
+
+<pre>
+ <var>Eine Zeile mit dem Namen der Bibliothek und dem Zweck.</var>
+ Copyright (C) <var>Jahr</var> <var>Name des Autors</var>
+
+<span xml:lang="en"> This library is free software; you can redistribute it
and/or
+ modify it under the terms of the GNU Library General Public
+ License as published by the Free Software Foundation; either
+ version 2.1 of the License, or (at your option) any later version.
+
+ This library is distributed in the hope that it will be useful,
+ but WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
+ Library General Public License for more details.
+
+ You should have received a copy of the GNU Library General Public
+ License along with this library; if not, write to the Free Software
+ Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston,
+ MA 02110-1301 USA.</span>
+
+<span class="translation"> Diese Bibliothek ist Freie Software: Sie können
sie unter den
+ Bedingungen der GNU Library General Public, wie von der Free Software
+ Foundation, Version 2.1 der Lizenz oder (nach Ihrer Option) jeder späteren
+ veröffentlichten Version, weiterverbreiten und/oder modifizieren.
+
+ Diese Bibliothek wird in der Hoffnung, dass sie nützlich sein wird,
+ aber OHNE JEDE GEWÃHRLEISTUNG, bereitgestellt; sogar ohne die implizite
+ Gewährleistung der MARKTFÃHIGKEIT oder EIGNUNG FÃR EINEN BESTIMMTEN
+ ZWECK. Siehe die Library General Public License für weitere Details.
+
+ Sie sollten eine Kopie der GNU Library General Public zusammen mit
+ dieser Bibliothek erhalten haben. Wenn nicht, schreiben Sie an Free
+ Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston,
+ MA 02110-1301, USA.</span>
+</pre>
+
+<p>
+Fügen Sie auÃerdem Informationen hinzu, wie man Sie per E-Mail und Brief
+kontaktieren kann.
+</p>
+<p>
+Sie sollten sich von Ihren Arbeitgeber (wenn Sie als ProgrammiererIn
+arbeiten) oder ggf. von der Schule ein <em>Copyright-Verzicht</em> für die
+Bibliothek unterschreiben lassen. Ein Beispiel:
+</p>
+
+<pre>
+ <samp>Yoyodyne, Inc. verzichtet hiermit auf alle
+ Copyright-Interessen an der von
+ James Random Hacker
+ geschriebenen Bibliothek ‚Frob‘
+ (eine Bibliothek, um Knöpfe zu optimieren).
+
+ <var>1990-04-01, Unterschrift von Ty Coon</var>
+ Ty Coon, stellv. Vizepräsident</samp>
+</pre>
+
+<p>
+Das ist alles, fertig!</p>
+
+
+<div style="font-size: small;">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't have notes.-->
+ </div>
+</div>
+
+<!--#include virtual="/server/footer.de.html" -->
+<div id="footer">
+
+<p>
+Bitte senden Sie Fragen zur FSF & GNU an <a
+href="mailto:address@hidden";><address@hidden></a>. Sie können auch die
<a
+href="/contact/contact">Free Software Foundation kontaktieren</a>.
+<br />
+Bitte senden Sie ungültige Verweise und andere Korrekturen oder Vorschläge
+an <a
+href="mailto:address@hidden";><address@hidden></a>.
+</p>
+
+<p>
+Bitte beachten Sie die <a
+href="/server/standards/README.translations">LIESMICH für Ãbersetzungen</a>,
+um weitere Informationen über die Koordinierung und Einsendung von
+Ãbersetzungen zu erhalten.
+</p>
+
+<p>
+Copyright-Hinweis siehe oben.</p>
+<address><!-- --></address>
+
+
+<div class="translators-credits">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.-->
+<strong>Ãbersetzung:</strong> Joerg Kohne, 2011.</div>
+ <p>
+<!-- timestamp start -->
+Aktualisierung:
+
+$Date: 2011/10/29 16:35:41 $
+
+<!-- timestamp end -->
+</p>
+</div>
+
+<!-- <div id="translations">
+ -->
+<!-- <h4>
+Translations of this page</h4> -->
+<!-- -->
+<!-- Please keep this list alphabetical by language code. -->
+<!-- Comment what the language is for each type, i.e. de is German. -->
+<!-- Write the language name in its own language (Deutsch) in the text. -->
+<!-- If you add a new language here, please -->
+<!-- advise address@hidden and add it to -->
+<!-- - /home/www/html/server/standards/README.translations.html -->
+<!-- - one of the lists under the section "Translations Underway" -->
+<!-- - if there is a translation team, you also have to add an alias -->
+<!-- to mail.gnu.org:/com/mailer/aliases -->
+<!-- Please also check you have the language code right; see: -->
+<!-- http://www.loc.gov/standards/iso639-2/php/code_list.php -->
+<!-- If the 2-letter ISO 639-1 code is not available, -->
+<!-- use the 3-letter ISO 639-2. -->
+<!-- Please use W3C normative character entities. -->
+<!-- -->
+<!-- <gnun>
+<ul class="translations-list"> -->
+<!-- English -->
+<!-- <li><a
href="/licenses/old-licenses/lgpl-2.1.html">English</a> [en]</li> -->
+<!-- Japanese -->
+<!-- <li><a
href="/licenses/old-licenses/lgpl-2.1.ja.html">日本語</a> [ja]</li>
-->
+<!-- </ul></gnun> -->
+<!-- </div>
+ -->
+</div>
+</body>
+</html>
Index: old-licenses.de.html
===================================================================
RCS file: old-licenses.de.html
diff -N old-licenses.de.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ old-licenses.de.html 29 Oct 2011 16:35:42 -0000 1.1
@@ -0,0 +1,151 @@
+
+<!--#include virtual="/server/header.de.html" -->
+
+<!-- This file is automatically generated by GNUnited Nations! -->
+<title>
+ Alte Lizenzen - GNU Projekt - Free Software Foundation (FSF)
+</title>
+<meta http-equiv="Keywords" content=" " />
+
+<!--#include virtual="/server/banner.de.html" -->
+<!--#include virtual="/licenses/old-licenses/po/old-licenses.translist" -->
+<h2>Alte Lizenzen</h2>
+
+<p>
+Diese Seite enthält alte Versionen der von der Free Software Foundation
+veröffentlichten Lizenzen als Referenz. Die aktuellen Lizenzen finden Sie
+unter <a href="/licenses/licenses">Lizenzen</a>.
+</p>
+
+<hr />
+
+<a id="GPL"></a>
+<h4>Alte Versionen der GNU General Public License (GPL)</h4>
+
+<ul>
+ <li><a href="/licenses/old-licenses/gpl-2.0">GNU General Public License
(GPL),
+Version 2</a></li>
+ <li><a href="/licenses/old-licenses/gpl-1.0">GNU General Public License
(GPL),
+Version 1</a></li>
+</ul>
+
+<a id="LGPL"></a>
+<h4>Alte Versionen der GNU Lesser General Public License (LGPL)</h4>
+
+<ul>
+ <li><a href="/licenses/old-licenses/lgpl-2.1">GNU Lesser General Public
License
+(LGPL), Version 2.1</a></li>
+</ul>
+
+<p>
+Diese Lizenz wurde früher als GNU Library General Public License bezeichnet:
+</p>
+
+<ul>
+ <li><a href="/licenses/old-licenses/lgpl-2.0">GNU Library General Public
+License, Version 2.0</a></li>
+</ul>
+
+
+<a id="FDL"></a>
+<h4>Alte Versionen der GNU Free Documentation License (FDL)</h4>
+
+<ul>
+ <li><a href="/licenses/old-licenses/fdl-1.2">GNU Free Documentation License
+(FDL), Version 1.2</a></li>
+ <li><a href="/licenses/old-licenses/fdl-1.1">GNU Free Documentation License
+(FDL), Version 1.1</a></li>
+</ul>
+
+<p>Weitere Informationen sowie Verweise zu alten Lizenzen finden Sie unter <a
+href="/licenses/licenses.de.html#LicenseURLs">Lizenz-Internetadressen</a>.</p>
+
+
+<div style="font-size: small;">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't have notes.-->
+ </div>
+</div>
+
+<!--#include virtual="/server/footer.de.html" -->
+<div id="footer">
+
+<p>
+Bitte senden Sie Fragen zur FSF & GNU an <a
+href="mailto:address@hidden";><address@hidden></a>. Sie können auch die
<a
+href="/contact/contact">Free Software Foundation kontaktieren</a>.
+<br />
+Bitte senden Sie ungültige Verweise und andere Korrekturen oder Vorschläge
+an <a
+href="mailto:address@hidden";><address@hidden></a>.
+</p>
+
+<p>
+Bitte beachten Sie die <a
+href="/server/standards/README.translations">LIESMICH für Ãbersetzungen</a>,
+um weitere Informationen über die Koordinierung und Einsendung von
+Ãbersetzungen zu erhalten.
+</p>
+
+<p>
+Copyright © 1996, 1997, 1998, 1999, 2006, 2007, 2008, 2009 Free
+Software Foundation, Inc.
+</p>
+<p>
+Dieses Werk bzw. Inhalt steht unter einer <a rel="license"
+href="http://creativecommons.org/licenses/by-nd/3.0/us/deed.de";>Creative
+Commons Namensnennung-Keine Bearbeitung 3.0 Vereinigte Staaten von Amerika
+Lizenz</a>.
+</p>
+
+
+<div class="translators-credits">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.-->
+<strong>Ãbersetzung:</strong> Joerg Kohne, 2011.</div>
+ <p>
+<!-- timestamp start -->
+Aktualisierung:
+
+$Date: 2011/10/29 16:35:42 $
+
+<!-- timestamp end -->
+</p>
+</div>
+
+<!-- <div id="translations">
+ -->
+<!-- <h4>
+Translations of this page</h4> -->
+<!-- -->
+<!-- Please keep this list alphabetical by language code. -->
+<!-- Comment what the language is for each type, i.e. de is German. -->
+<!-- Write the language name in its own language (Deutsch) in the text. -->
+<!-- If you add a new language here, please -->
+<!-- advise address@hidden and add it to -->
+<!-- - /home/www/html/server/standards/README.translations.html -->
+<!-- - one of the lists under the section "Translations Underway" -->
+<!-- - if there is a translation team, you also have to add an alias -->
+<!-- to mail.gnu.org:/com/mailer/aliases -->
+<!-- Please also check you have the language code right; see: -->
+<!-- http://www.loc.gov/standards/iso639-2/php/code_list.php -->
+<!-- If the 2-letter ISO 639-1 code is not available, -->
+<!-- use the 3-letter ISO 639-2. -->
+<!-- Please use W3C normative character entities. -->
+<!-- -->
+<!-- <gnun>
+<ul class="translations-list"> -->
+<!-- Arabic -->
+<!-- <li><a
href="/licenses/old-licenses/old-licenses.ar.html">العربية</a> [ar]</li>
-->
+<!-- Catalan -->
+<!-- <li><a
href="/licenses/old-licenses/old-licenses.ca.html">català</a> [ca]</li>
-->
+<!-- English -->
+<!-- <li><a
href="/licenses/old-licenses/old-licenses.html">English</a> [en]</li> -->
+<!-- French -->
+<!-- <li><a
href="/licenses/old-licenses/old-licenses.fr.html">français</a> [fr]</li>
-->
+<!-- </ul></gnun> -->
+<!-- </div>
+ -->
+</div>
+</body>
+</html>