[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
www licenses/licenses.el.html licenses/licenses...
|
From: |
GNUN |
|
Subject: |
www licenses/licenses.el.html licenses/licenses... |
|
Date: |
Sun, 21 Oct 2012 00:28:28 +0000 |
CVSROOT: /web/www
Module name: www
Changes by: GNUN <gnun> 12/10/21 00:28:28
Modified files:
licenses : licenses.el.html licenses.nl.html
licenses.zh-cn.html
philosophy : categories.es.html words-to-avoid.es.html
philosophy/po : categories.es-en.html words-to-avoid.es-en.html
Added files:
licenses/po : licenses.el-diff.html licenses.nl-diff.html
licenses.zh-cn-diff.html
Log message:
Automatic update by GNUnited Nations.
CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/licenses.el.html?cvsroot=www&r1=1.19&r2=1.20
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/licenses.nl.html?cvsroot=www&r1=1.7&r2=1.8
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/licenses.zh-cn.html?cvsroot=www&r1=1.7&r2=1.8
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/licenses.el-diff.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/licenses.nl-diff.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/licenses.zh-cn-diff.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/categories.es.html?cvsroot=www&r1=1.19&r2=1.20
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/words-to-avoid.es.html?cvsroot=www&r1=1.45&r2=1.46
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/categories.es-en.html?cvsroot=www&r1=1.8&r2=1.9
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/words-to-avoid.es-en.html?cvsroot=www&r1=1.11&r2=1.12
Patches:
Index: licenses/licenses.el.html
===================================================================
RCS file: /web/www/www/licenses/licenses.el.html,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -b -r1.19 -r1.20
--- licenses/licenses.el.html 16 Sep 2012 05:25:41 -0000 1.19
+++ licenses/licenses.el.html 21 Oct 2012 00:28:26 -0000 1.20
@@ -5,6 +5,13 @@
<title>ÎÎ´ÎµÎ¹ÎµÏ - ÎÏγο GNU - ÎδÏÏ
μα ÎλεÏθεÏοÏ
ÎογιÏÎ¼Î¹ÎºÎ¿Ï (ÎÎÎ)</title>
<!--#include virtual="/server/banner.el.html" -->
+<!--#set var="PO_FILE"
+ value='<a href="http://www.gnu.org/licenses/po/licenses.el.po";>
+ http://www.gnu.org/licenses/po/licenses.el.po</a>' -->
+ <!--#set var="ORIGINAL_FILE" value="/licenses/licenses.html" -->
+ <!--#set var="DIFF_FILE" value="/licenses/po/licenses.el-diff.html" -->
+ <!--#set var="OUTDATED_SINCE" value="2012-08-21" -->
+ <!--#include virtual="/server/outdated.el.html" -->
<!--#include virtual="/licenses/po/licenses.translist" -->
<h2>ÎδειεÏ</h2>
@@ -474,7 +481,7 @@
<p><!-- timestamp start -->
ÎνημεÏÏθηκε:
-$Date: 2012/09/16 05:25:41 $
+$Date: 2012/10/21 00:28:26 $
<!-- timestamp end -->
</p>
Index: licenses/licenses.nl.html
===================================================================
RCS file: /web/www/www/licenses/licenses.nl.html,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -b -r1.7 -r1.8
--- licenses/licenses.nl.html 16 Sep 2012 05:25:41 -0000 1.7
+++ licenses/licenses.nl.html 21 Oct 2012 00:28:26 -0000 1.8
@@ -5,6 +5,13 @@
<title>Licenties - GNU Project - Free Software Foundation (FSF)</title>
<!--#include virtual="/server/banner.nl.html" -->
+<!--#set var="PO_FILE"
+ value='<a href="http://www.gnu.org/licenses/po/licenses.nl.po";>
+ http://www.gnu.org/licenses/po/licenses.nl.po</a>' -->
+ <!--#set var="ORIGINAL_FILE" value="/licenses/licenses.html" -->
+ <!--#set var="DIFF_FILE" value="/licenses/po/licenses.nl-diff.html" -->
+ <!--#set var="OUTDATED_SINCE" value="2012-08-21" -->
+ <!--#include virtual="/server/outdated.nl.html" -->
<!--#include virtual="/licenses/po/licenses.translist" -->
<h2>Licenties</h2>
@@ -444,7 +451,7 @@
<p><!-- timestamp start -->
Bijgewerkt:
-$Date: 2012/09/16 05:25:41 $
+$Date: 2012/10/21 00:28:26 $
<!-- timestamp end -->
</p>
Index: licenses/licenses.zh-cn.html
===================================================================
RCS file: /web/www/www/licenses/licenses.zh-cn.html,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -b -r1.7 -r1.8
--- licenses/licenses.zh-cn.html 16 Sep 2012 05:25:41 -0000 1.7
+++ licenses/licenses.zh-cn.html 21 Oct 2012 00:28:26 -0000 1.8
@@ -5,6 +5,13 @@
<title>许å¯è¯ - GNU å·¥ç¨ - èªç±è½¯ä»¶åºéä¼ (FSF)</title>
<!--#include virtual="/server/banner.zh-cn.html" -->
+<!--#set var="PO_FILE"
+ value='<a href="http://www.gnu.org/licenses/po/licenses.zh-cn.po";>
+ http://www.gnu.org/licenses/po/licenses.zh-cn.po</a>' -->
+ <!--#set var="ORIGINAL_FILE" value="/licenses/licenses.html" -->
+ <!--#set var="DIFF_FILE" value="/licenses/po/licenses.zh-cn-diff.html" -->
+ <!--#set var="OUTDATED_SINCE" value="2012-08-21" -->
+ <!--#include virtual="/server/outdated.zh-cn.html" -->
<!--#include virtual="/licenses/po/licenses.translist" -->
<h2>许å¯è¯</h2>
@@ -333,7 +340,7 @@
<p><!-- timestamp start -->
æåæ´æ°ï¼
-$Date: 2012/09/16 05:25:41 $
+$Date: 2012/10/21 00:28:26 $
<!-- timestamp end -->
</p>
Index: philosophy/categories.es.html
===================================================================
RCS file: /web/www/www/philosophy/categories.es.html,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -b -r1.19 -r1.20
--- philosophy/categories.es.html 4 Oct 2012 16:28:56 -0000 1.19
+++ philosophy/categories.es.html 21 Oct 2012 00:28:27 -0000 1.20
@@ -341,14 +341,17 @@
todos los derechos sobre el programa privado, el programa es libre. Sin
embargo, si el usuario distribuye copias sin otorgar las cuatro libertades
para las mismas, esas copias no son libres.</p>
+
<p>El software libre es una cuestión de libertad, no de
disponibilidad. En
general no creemos que sea un error desarrollar un programa y no
-publicarlo. Hay ocasiones en las que un programa es tan útil que acapararlo
-para sà constituye un perjuicio para la humanidad. Sin embargo, la mayorÃa
-de los programas no son tan importantes, por lo que no publicarlos no
-resulta particularmente dañino. Por lo tanto, no hay ningún conflicto entre
-el desarrollo de software privado o personalizado y los principios del
+publicarlo. Hay ocasiones en las que un programa es tan importante que
+—se podrÃa argumentar— no ponerlo a disposición del público
+constituye un perjuicio para la humanidad. Sin embargo, esos casos no son
+frecuentes. La mayorÃa de los programas no son tan importantes, por lo que
+negarse a publicarlos no está mal. Por lo tanto, no hay ningún conflicto
+entre el desarrollo de software privado o personalizado y los principios del
movimiento del software libre.</p>
+
<p>Casi todos los empleos para programadores tienen por objetivo el
desarrollo
de software personalizado; por lo tanto, la mayorÃa de los trabajos de
programación son, o podrÃan ser, hechos de un modo compatible con el
@@ -441,7 +444,7 @@
<!-- timestamp start -->
Ãltima actualización:
-$Date: 2012/10/04 16:28:56 $
+$Date: 2012/10/21 00:28:27 $
<!-- timestamp end -->
</p>
Index: philosophy/words-to-avoid.es.html
===================================================================
RCS file: /web/www/www/philosophy/words-to-avoid.es.html,v
retrieving revision 1.45
retrieving revision 1.46
diff -u -b -r1.45 -r1.46
--- philosophy/words-to-avoid.es.html 28 Sep 2012 08:29:12 -0000 1.45
+++ philosophy/words-to-avoid.es.html 21 Oct 2012 00:28:27 -0000 1.46
@@ -184,13 +184,16 @@
<h4 id="Consume">«Consumir»</h4>
<p>
-No es correcto hablar de «consumir» información digital, música, software,
-etc., pues con el uso no se consumen. Ver la siguiente entrada.</p>
+«Consumir» se refiere a lo que hacemos con los alimentos: los ingerimos y
+los usamos de modo que se extinguen. Por analogÃa usamos el término para
+referirnos a otras cosas cuyo uso provoca su extinción. Pero decir que se
+«consume» información digital, música, software, etc., es erróneo porque
el
+uso no provoca su extinción. Véase también el artÃculo que sigue.</p>
<h4 id="Consumer">«Consumidor»</h4>
<p>
-Cuando se usa para referirse a los usuarios de computadoras, el término
-«consumidor» está cargado de una serie de suposiciones que debemos
+El término «consumidor», cuando se usa para referirse a quienes realizan
+tareas de computación, está cargado de una serie de suposiciones que debemos
rechazar. Reproducir una grabación digital o ejecutar un programa
informático no es consumir.</p>
<p>
@@ -202,16 +205,17 @@
un papel limitado para ellos: se les considera como un rebaño que pasta de
forma pasiva lo que otros ponen a su disposición.</p>
<p>
-Este modo de pensar da lugar a contradicciones, como ocurre con la Consumer
-Broadband and Digital Television Promotion Act («Ley de promoción del ancho
-de banda y la televisión digital para consumidores, CBDTPA en sus siglas en
-inglés). Dicha ley pretende que sea obligatorio incluir mecanismos de
-restricción de copia en todo dispositivo digital. Si todo lo que hacen los
-usuarios es «consumir», entonces ¿por qué deberÃan preocuparse?</p>
+Este modo de pensar da lugar a contradicciones, como ocurre con la
+<cite>Consumer Broadband and Digital Television Promotion Act</cite> («Ley
+de promoción del ancho de banda y la televisión digital para consumidores,
+CBDTPA por sus siglas en inglés). Dicha ley propuso la obligatoriedad de
+incluir mecanismos de restricción de copia en todo dispositivo digital. Si
+todo lo que hacen los usuarios es «consumir», entonces ¿por qué se
+preocupan?</p>
<p>
La superficial visión económica que define a los usuarios como
«consumidores» tiende a ir de la mano con la idea de que los trabajos
-publicados son mero «contenido».</p>
+publicados son mero <a href="#Content">«contenido»</a>.</p>
<p>
Para describir a las personas que no se limitan al uso pasivo de estos
trabajos, sugerimos términos tales como «particulares» o «ciudadanos».</p>
@@ -258,23 +262,27 @@
<h4 id="Creator">«Creador»</h4>
<p>
-Si se utiliza el término «creador» aplicado a los autores, se los compara
-implÃcitamente con una deidad («el Creador»). Los editores utilizan este
-término para elevar la posición moral de los autores por encima de las
-personas corrientes. El fin que persiguen es justificar que se conceda a los
-autores un control desorbitado sobre el copyright, de forma que los editores
-puedan hacer uso de este derecho en su nombre. En su lugar recomendamos
-decir «autor», aunque en muchos casos lo que realmente se desea expresar es
-«titular de los derechos de autor».</p>
+Si se utiliza el término «creador» para referirse a los autores, se los
+compara implÃcitamente con una deidad («el Creador»). Los editores utilizan
+este término para elevar la posición moral de los autores por encima de las
+personas corrientes. El fin que persiguen es otorgar a los autores mayor
+poder sobre el copyright, de modo que los editores puedan ejercer ese poder
+en nombre de los autores. Recomendamos decir «autor», aunque en muchos casos
+lo que realmente se desea expresar es «titular del copyright». Estos dos
+términos no son equivalentes, a menudo el titular del copyright no es el
+autor.</p>
<h4 id="DigitalGoods">«Bienes digitales»</h4>
<p>
El término «bienes digitales», aplicado a las copias de obras con autorÃa,
los equipara con bienes fÃsicos que no pueden copiarse y, por consiguiente,
-tienen que ser fabricados y vendidos. Esta metáfora alienta a las personas a
-considerar las cuestiones del software y libre y otras obras digitales en
-base a sus puntos de vista e impresiones sobre los bienes fÃsicos.</p>
+tienen que ser fabricados en cantidad y vendidos. Esta metáfora alienta a
+las personas a considerar las cuestiones del software y libre y otras obras
+digitales en base a sus puntos de vista e impresiones sobre los bienes
+fÃsicos. Además, encuadra el tema en términos que pertenecen al área de la
+economÃa, cuyos valores superficiales y limitados no incluyen la libertad y
+la comunidad.</p>
<h4 id="DigitalLocks">«Candados digitales»</h4>
@@ -292,12 +300,13 @@
llave; en otras palabras, como esposas. Por tanto, los llamamos «esposas
digitales», no «candados digitales».</p>
<p>
-Se han lanzado varias campañas que usan el término desacertado «candados
-digitales»; para corregir el error, tenemos que rechazar firmemente ese
-término. A veces apoyamos alguna campaña que critica el uso de «candados
-digitales» (siempre y cuando estemos de acuerdo con los principios básicos),
-pero cuando lo hacemos, manifestamos que rechazamos ese término y decimos
-claramente «esposas digitales» para presentar un ejemplo mejor.</p>
+Varias campañas opositoras han optado por usar el término desacertado
+«candados digitales»; para regresar a la ruta correcta, tenemos que negarnos
+firmemente a seguirlas con respecto al uso de ese término. Podemos apoyar
+una campaña que se opone al uso de «candados digitales», siempre y cuando
+estemos de acuerdo con los principios básicos; sin embargo, cuando
+declaramos nuestro apoyo, reemplazamos notablemente ese término por «esposas
+digitales» y explicamos las razones.</p>
<h4 id="DigitalRightsManagement">«Gestión digital de derechos»</h4>
@@ -316,26 +325,28 @@
<h4 id="Ecosystem">«Ecosistema»</h4>
<p>
-Es un error describir la comunidad de software libre, o cualquier otra
-comunidad humana, como un «ecosistema», ya que este término implica la
+No es recomendable describir la comunidad de software libre, o cualquier
+otra comunidad humana, como un «ecosistema», ya que este término implica la
ausencia de juicio ético.</p>
<p>
El término «ecosistema» lleva el significado implÃcito de observar sin
-emitir un juicio: no preguntes qué <em>deberÃa</em> ocurrir, simplemente
-estudia y explica lo que <em>sucede</em>. En un ecosistema, algunos
-organismos devoran a otros organismos. No nos cuestionamos si es justo que
-un búho se coma a un ratón, o que un ratón se coma una planta. Solo
-observamos lo que ellos hacen. La población de las especies crece o
-disminuye según las condiciones que los rodean. No es bueno ni malo, es un
-mero fenómeno ecológico.</p>
-
-<p>
-En cambio, quienes adoptan una postura ética ante su entorno, tienen en su
-mano el conservar cosas que, sin apoyo, tenderÃan a desaparecer como, por
-ejemplo, la sociedad civil, la democracia, los derechos humanos, la paz, la
-salud pública, el aire y las aguas no contaminados, las especies en peligro
-de extinción, las tradiciones o la libertad de los usuarios de computadoras.
+emitir un juicio: no pregunte qué <em>deberÃa</em> ocurrir, simplemente
+estudie y comprenda lo que <em>sucede</em>. En un ecosistema, algunos
+organismos consumen otros organismos. En ecologÃa, no nos cuestionamos si es
+correcto que un búho se coma a un ratón, o que un ratón se coma una
+semilla. Nos limitamos a observar lo que hacen. La población de las especies
+crece o disminuye según las condiciones; esto no es ni bueno ni malo, es un
+mero fenómeno ecológico, inclusive cuando se llega a la extinción de una
+especie.</p>
+
+<p>
+En cambio quienes adoptan una postura ética ante su entorno pueden tomar
+decisiones para conservar cosas que, sin su intervención, podrÃan
+desaparecer, como por ejemplo la sociedad civil, la democracia, los derechos
+humanos, la paz, la salud pública, un cima estable, el aire y las aguas no
+contaminados, las especies en peligro de extinción, las artes
+tradicionales… y la libertad de los usuarios de computadoras.
</p>
@@ -663,24 +674,21 @@
<h4 id="Theft">«Robo»</h4>
<p>
-Los defensores del copyright usan frecuentemente palabras como «robado» y
-«hurto» como metáfora de la violación de los derechos de autor. Al mismo
-tiempo, nos piden que tratemos el sistema legal como si fuera una autoridad
-en el campo de la ética: si copiar está prohibido, entonces debe de ser algo
-malo.</p>
-<p>
-Por este motivo, merece la pena mencionar que el sistema legal, «al menos en
-los EE.UU.», rechaza la idea de que la infracción sobre el copyright sea un
-«robo». Los partidarios del copyright están apelando a las autoridades y
+Los apologistas del copyright usan frecuentemente palabras como «robado» y
+«hurto» para referirse a la violación del copyright. Es una farsa, pero
+esperan que usted lo tome como una verdad objetiva.</p>
+<p>
+En el sistema legal estadounidense la violación del copyright no constituye
+robo. Las leyes sobre el robo no se aplican a las violaciones del
+copyright. Los apologistas del copyright están apelando a las autoridades y
malinterpretando lo que la misma autoridad dice.</p>
<p>
-Se ha generalizado la idea incorrecta de que las leyes deciden lo que está
-bien o lo que está mal. Las leyes son, en el mejor de los casos, un intento
-de hacer justicia. Decir que las leyes definen la justicia o las conductas
-éticas, es ponerlo todo patas arriba.</p>
-<p>
-Cuando se utiliza el nombre de un delito como metáfora para referirse a otra
-cosa, la ley que se refiere a ese delito es completamente irrelevante.</p>
+La copia no autorizada está prohibida bajo la ley de copyright en muchas
+circunstancias (¡no en todas!), pero el hecho de que esté prohibido no hace
+que sea una cosa mala. En general las leyes no definen lo que es bueno o lo
+que es malo. Las leyes, como máximo, intentan administrar justicia. Si las
+leyes (su implementación) no se ajustan a lo que para nosotros es bueno o
+malo (lo especÃfico), lo que se deberÃa cambiar son las leyes.</p>
<h4 id="TrustedComputing">«Computación confiable»</h4>
<p>
@@ -771,7 +779,7 @@
<!-- timestamp start -->
Ãltima actualización:
-$Date: 2012/09/28 08:29:12 $
+$Date: 2012/10/21 00:28:27 $
<!-- timestamp end -->
</p>
Index: philosophy/po/categories.es-en.html
===================================================================
RCS file: /web/www/www/philosophy/po/categories.es-en.html,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -b -r1.8 -r1.9
--- philosophy/po/categories.es-en.html 4 Oct 2012 16:28:56 -0000 1.8
+++ philosophy/po/categories.es-en.html 21 Oct 2012 00:28:28 -0000 1.9
@@ -350,14 +350,17 @@
free. However, if the user distributes copies to others and does
not provide the four freedoms with those copies, those copies
are not free software.</p>
- <p>Free software is a matter of freedom, not access.
- In general we do not believe it is wrong to develop a program
- and not release it. There are occasions when a program is so useful
- that withholding it from release is doing wrong to humanity.
- However, most programs are not that important, so not releasing them
- is not particularly harmful. Thus, there is no conflict between the
- development of private or custom software and the principles of the
- free software movement.</p>
+
+ <p>Free software is a matter of freedom, not access. In
+ general we do not believe it is wrong to develop a program and
+ not release it. There are occasions when a program is so
+ important that one might argue that withholding it from the
+ public is doing wrong to humanity. However, such cases are
+ rare. Most programs are not that important, and declining to
+ release them is not particularly wrong. Thus, there is no
+ conflict between the development of private or custom software
+ and the principles of the free software movement.</p>
+
<p>Nearly all employment for programmers is in development of
custom software; therefore most programming jobs are, or could be,
done in a way compatible with the free software movement.</p>
@@ -427,7 +430,7 @@
<p>
Updated:
<!-- timestamp start -->
-$Date: 2012/10/04 16:28:56 $
+$Date: 2012/10/21 00:28:28 $
<!-- timestamp end -->
</p>
</div>
Index: philosophy/po/words-to-avoid.es-en.html
===================================================================
RCS file: /web/www/www/philosophy/po/words-to-avoid.es-en.html,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -b -r1.11 -r1.12
--- philosophy/po/words-to-avoid.es-en.html 28 Sep 2012 08:29:12 -0000
1.11
+++ philosophy/po/words-to-avoid.es-en.html 21 Oct 2012 00:28:28 -0000
1.12
@@ -225,13 +225,16 @@
<h4 id="Consume">“Consume”</h4>
<p>
-It is erroneous to speak of "consuming" digital information, music,
-software, etc., since using them does not consume them. See the
-following entry,</p>
+"Consume" refers to what we do with food: we ingest it, and use it in
+a way that uses it up. By analogy, we emply the same word to describe
+using other things in a way that uses them up. However, it is
+erroneous to speak of "consuming" digital information, music,
+software, etc., since using them does not consume them. See also the
+following entry.</p>
<h4 id="Consumer">“Consumer”</h4>
<p>
-The term “consumer,” when used to refer to computer users,
+The term “consumer,” when used to refer to the users of computing,
is loaded with assumptions we should reject. Playing a digital
recording, or running a program, does not consume it.</p>
<p>
@@ -243,15 +246,15 @@
presumes a narrow role for them: it regards them as sheep that
passively graze on what others make available to them.</p>
<p>
-This kind of thinking leads to travesties like the CBDTPA
-“Consumer Broadband and Digital Television Promotion Act”
-which would require copying restriction facilities in every digital
+This kind of thinking leads to travesties such as the CBDTPA
+(“Consumer Broadband and Digital Television Promotion Act”)
+which proposed to require copying restriction facilities in every digital
device. If all the users do is “consume,” then why should
they mind?</p>
<p>
The shallow economic conception of users as “consumers” tends
to go hand in hand with the idea that published works are mere
-“content.”</p>
+<a href="#content">“content.”</a></p>
<p>
To describe people who are not limited to passive use of works, we
suggest terms such as “individuals” and
@@ -300,20 +303,22 @@
compares them to a deity (“the creator”). The term is
used by publishers to elevate authors' moral standing above that of
ordinary people in order to justify giving them increased copyright
-power, which the publishers can then exercise in their name.
-We recommend saying “author” instead. However,
-in many cases “copyright holder” is what you really
-mean.</p>
+power, which the publishers can then exercise in their name. We
+recommend saying “author” instead. However, in many cases
+“copyright holder” is what you really mean. These two
+terms are not equivalent: often the copyright holder is not the
+author.</p>
<h4 id="DigitalGoods">“Digital Goods”</h4>
<p>
The term “digital goods,” as applied to copies of works of
authorship, identifies them with physical goods—which cannot be
-copied, and which therefore have to be manufactured and sold. This
-metaphor encourages people to judge issues about software or other
-digital works based on their views and intuitions about physical
-goods.</p>
+copied, and which therefore have to be manufactured in quantity and
+sold. This metaphor encourages people to judge issues about software
+or other digital works based on their views and intuitions about
+physical goods. It also frames issues in terms of economics, whose
+shallow and limited values don't include freedom and community.</p>
<h4 id="DigitalLocks">“Digital Locks”</h4>
@@ -328,16 +333,16 @@
open and close them.</p>
<p>
DRM is like a lock placed on you by someone else, who refuses to
-give you the key — in other words, like handcuffs. Therefore,
+give you the key—in other words, like handcuffs. Therefore,
we call them “digital handcuffs”, not “digital
locks”.</p>
<p>
-A number of campaigns have chosen the unwise term “digital
-locks”; therefore, to correct the mistake, we must firmly reject
-the term. We sometimes support a campaign that criticizes
-“digital locks”, if we agree with the substance; but when
-we do, we state our rejection of that term, and conspicuously say
-“digital handcuffs” so as to set a better example.</p>
+A number of opposition campaigns have chosen the unwise term
+“digital locks”; to get things back on the right track, we
+must firmly decline to follow them in using that term. We can support
+a campaign that opposes “digital locks” if we agree on the
+substance; however, when we state our support, we conspicuously
+replace the term with “digital handcuffs” and say why.</p>
<h4 id="DigitalRightsManagement">“Digital Rights Management”</h4>
@@ -355,26 +360,28 @@
<h4 id="Ecosystem">“Ecosystem”</h4>
<p>
-It is a mistake to describe the free software community, or any human
+It is inadvisable to describe the free software community, or any human
community, as an “ecosystem,” because that word implies
the absence of ethical judgment.</p>
<p>
The term “ecosystem” implicitly suggests an attitude of
nonjudgmental observation: don't ask how what <em>should</em> happen,
-just study and explain what <em>does</em> happen. In an ecosystem,
-some organisms consume other organisms. We do not ask whether it is
-fair for an owl to eat a mouse or for a mouse to eat a plant, we only
-observe that they do so. Species' populations grow or shrink
-according to the conditions; this is neither right nor wrong, merely
-an ecological phenomenon.</p>
+just study and understand what <em>does</em> happen. In an ecosystem,
+some organisms consume other organisms. In ecology, we do not ask
+whether it is right for an owl to eat a mouse or for a mouse to eat a
+seed, we only observe that they do so. Species' populations grow or
+shrink according to the conditions; this is neither right nor wrong,
+merely an ecological phenomenon, even if it goes so far as the
+extinction of a species.</p>
<p>
By contrast, beings that adopt an ethical stance towards their
-surroundings can decide to preserve things that, on their own, might
-vanish—such as civil society, democracy, human rights, peace,
-public health, clean air and water, endangered species, traditional
-arts…and computer users' freedom.
+surroundings can decide to preserve things that, without their
+intervention, might vanish—such as civil society, democracy,
+human rights, peace, public health, a stable climate, clean air and
+water, endangered species, traditional arts…and computer users'
+freedom.
</p>
@@ -708,22 +715,20 @@
<h4 id="Theft">“Theft”</h4>
<p>
Copyright apologists often use words like “stolen” and
-“theft” as a metaphor for copyright infringement. At the same
-time, they ask us to treat the legal system as an authority on ethics:
-if copying is forbidden, it must be wrong.</p>
-<p>
-So it is pertinent to mention that the legal system—at least in
-the US—rejects the idea that copyright infringement is
-“theft.” Copyright apologists are making an appeal to
-authority…and misrepresenting what authority says.</p>
-<p>
-The idea that laws decide what is right or wrong is mistaken in
-general. Laws are, at their best, an attempt to achieve justice; to
-say that laws define justice or ethical conduct is turning things
-upside down.</p>
+“theft” to refer to copyright infringement. This is spin,
+but they would like you to take it for objective truth.</p>
<p>
-Meanwhile, when the name of a legal offense is used as a metaphor
-for something else, that particular law is not relevant at all.</p>
+Under the US legal system, copyright infringement is not theft. Laws
+about theft are not applicable to copyright infringement. The
+copyright apologists are making an appeal to authority—and
+misrepresenting what authority says.</p>
+<p>
+Unauthorized copying is forbidden by copyright law in many
+circumstances (not all!), but being forbidden doesn't make it wrong.
+In general, laws don't define right and wrong. Laws, at their best,
+attempt to implement justice. If the laws (the implementation) don't
+fit our ideas of right and wrong (the spec), the laws are what should
+change.</p>
<h4 id="TrustedComputing">“Trusted Computing”</h4>
<p>
@@ -790,7 +795,7 @@
<p>
Updated:
<!-- timestamp start -->
-$Date: 2012/09/28 08:29:12 $
+$Date: 2012/10/21 00:28:28 $
<!-- timestamp end -->
</p>
</div>
Index: licenses/po/licenses.el-diff.html
===================================================================
RCS file: licenses/po/licenses.el-diff.html
diff -N licenses/po/licenses.el-diff.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ licenses/po/licenses.el-diff.html 21 Oct 2012 00:28:27 -0000 1.1
@@ -0,0 +1,456 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";>
+<!-- Generated by GNUN -->
+<html xmlns="http://www.w3.org/1999/xhtml"; xml:lang="en" lang="en">
+<head>
+<meta http-equiv="content-type" content="text/html; charset=utf-8" />
+<title>/licenses/licenses.html-diff</title>
+<style type="text/css">
+span.removed { background-color: #f22; color: #000; }
+span.inserted { background-color: #2f2; color: #000; }
+</style></head>
+<body><pre>
+<!--#include virtual="/server/header.html" -->
+<title>Licenses - GNU Project - Free Software Foundation
(FSF)</title>
+<!--#include virtual="/server/banner.html" -->
+<!--#include virtual="/licenses/po/licenses.translist" -->
+<h2>Licenses</h2>
+
+<p>
+Published software should be <a href="/philosophy/free-sw.html">free
+software</a>. To make it free software, you need to release it
+under a free software license. We normally use the <a
+href="#GPL">GNU General Public License</a> (GNU GPL),
+but occasionally we use <a
href="/licenses/license-list.html#SoftwareLicenses">other
+free software licenses</a>. We use only licenses that are compatible
+with the GNU GPL for GNU software.
+</p>
+
+<p>
+Documentation for free software should be
+<a href="/philosophy/free-doc.html">free documentation</a>, so that
+people can redistribute it and improve it along with the software
+it describes. To make it free documentation, you need to release
+it under a free documentation license. We normally use the
+<a href="#FDL">GNU Free Documentation License</a> (GNU
+FDL), but occasionally we use
+<a href="/licenses/license-list.html#DocumentationLicenses">other free
+documentation licenses</a>.
+</p>
+
+<p>If you've started a new project and you're not sure what license to
+use, <a href="/licenses/license-recommendations.html">“How to
+choose a license for your own work”</a> details our
+recommendations in an easy-to-follow guide. If you just want a quick
+list reference, we have a page that names
+our <a href="/licenses/recommended-copylefts.html">recommended
+copyleft licenses</a>.</p>
+
+<p>
+Our documentation licenses are currently being revised, and we welcome
+your comments on the proposed texts. Please
+visit <a href="http://gplv3.fsf.org">our license update site</a> to
+read the current drafts and participate in the process.
+</p>
+
+<h3>Common Resources for our Software Licenses</h3>
+
+<p>We have a number of resources to help people understand and use our
+various licenses:</p>
+
+<ul>
+
+ <li><a href="/licenses/gpl-faq.html">Frequently Asked
+ Questions about the GNU licenses</a></li>
+ <li><a href="/licenses/gpl-howto.html">How to use GNU licenses
for your
+ own software</a></li>
+ <li><a href="/licenses/gpl-violation.html">What to do if you see
a
+ violation of a GNU license</a></li>
+ <li><a href="/philosophy/university.html">Releasing Free
Software if
+ you work at a university</a></li>
+ <li><a href="/licenses/why-assign.html">Why the FSF gets
copyright
+ assignments from contributors</a></li>
+ <li><a href="/graphics/license-logos.html">GNU license
logos</a> to use
+ with your project</li>
+ <li><a
+<span
class="removed"><del><strong>href="/licenses/license-list.html#LicensingMailingList"><address@hidden>
+mailing list</a></strong></del></span> <span
class="inserted"><ins><em>href="http://www.fsf.org/licensing">The FSF
Licensing & Compliance Lab</a></li>
+ <li><a
+href="/licenses/license-list.html#LicensingEmailAddress"><address@hidden></a></em></ins></span>
for general licensing help
+ </li>
+
+</ul>
+
+<h3 id="GPL">The GNU General Public License</h3>
+
+<p>
+The GNU General Public License is often called the GNU GPL for short;
+it is used by most GNU programs, and by more than half of all free
+software packages. The latest version is version 3.
+</p>
+
+<ul>
+ <li>The GNU General Public License is available in these formats:
+ <a href="/licenses/gpl.html">HTML</a>,
+ <a href="/licenses/gpl.txt">plain text</a>,
+ <a href="/licenses/gpl.odt">ODF</a>,
+ <a href="/licenses/gpl.dbk">Docbook</a>,
+ <a href="/licenses/gpl.texi">Texinfo</a>, and
+ <a href="/licenses/gpl.tex">LaTeX</a>.
+These documents are not formatted for standalone publishing, and
+are intended to be included in another document.</li>
+ <li><a href="/licenses/quick-guide-gplv3.html">A Quick Guide to
+ GPLv3</a></li>
+ <li><a href="/licenses/old-licenses/old-licenses.html#GPL">Older
+ versions of the GNU GPL</a></li>
+</ul>
+
+<h3 id="LGPL">The GNU Lesser General Public License</h3>
+
+<p>
+The GNU Lesser General Public License is used by a few (not by any means
+all) GNU libraries. The latest version is version 3.
+</p>
+
+<ul>
+ <li>The GNU Lesser General Public License text is available in
+ these formats:
+ <a href="/licenses/lgpl.html">HTML</a>,
+ <a href="/licenses/lgpl.txt">plain text</a>,
+ <a href="/licenses/lgpl.dbk">Docbook</a>, and
+ <a href="/licenses/lgpl.texi">Texinfo</a>.
+These documents are not formatted for standalone publishing, and
+are intended to be included in another document.</li>
+ <li><a href="/licenses/why-not-lgpl.html">Why you shouldn't use
+ the Lesser GPL for your next library</a></li>
+ <li><a href="/licenses/old-licenses/old-licenses.html#LGPL">Older
+ versions of the GNU LGPL</a></li>
+</ul>
+
+<h3 id="AGPL">The GNU Affero General Public License</h3>
+
+<p>
+The GNU Affero General Public License is based on the GNU GPL, but has an
+additional term to allow users who interact with the licensed software over
+a network to receive the source for that program. We recommend that people
+consider using the GNU AGPL for any software which will commonly be run
+over a network. The latest version is version 3.
+</p>
+
+<ul>
+ <li>The GNU Affero General Public License text is available in
+ these formats:
+ <a href="/licenses/agpl.html">HTML</a>,
+ <a href="/licenses/agpl.txt">plain text</a>,
+ <a href="/licenses/agpl.dbk">Docbook</a>,
+ <a href="/licenses/agpl.texi">Texinfo</a>, and
+ <a href="/licenses/agpl.tex">LaTeX</a>.
+These documents are not formatted for standalone publishing, and
+are intended to be included in another document.</li>
+ <li><a href="/licenses/why-affero-gpl.html">Why the Affero
GPL</a></li>
+</ul>
+
+<h3 id="FDL">The GNU Free Documentation License</h3>
+
+<p>
+The GNU Free Documentation License is a form of copyleft intended
+for use on a manual, textbook or other document to assure everyone
+the effective freedom to copy and redistribute it, with or without
+modifications, either commercially or non-commercially. The latest version
+is 1.3.
+</p>
+
+<ul>
+ <li>The GNU Free Documentation License text is available in these
formats:
+ <a href="/licenses/fdl.html">HTML</a>,
+ <a href="/licenses/fdl.txt">plain text</a>,
+ <a href="/licenses/fdl.xml">Docbook</a>,
+ <a href="/licenses/fdl.texi">Texinfo</a>, and
+ <a href="/licenses/fdl.tex">LaTeX</a>.
+These documents are not formatted for standalone publishing, and
+are intended to be included in another document.</li>
+ <li><a href="/licenses/why-gfdl.html">Why publishers should use
+ the GNU FDL</a></li>
+ <li><a href="/licenses/fdl.html#addendum">How to use
+ the GNU FDL for your documentation</a></li>
+ <li><a href="/licenses/fdl-howto.html">Tips on using the GNU
FDL</a></li>
+ <li><a href="/licenses/fdl-howto-opt.html">How to use the
optional
+ features of the GNU FDL</a></li>
+ <li><a href="/licenses/old-licenses/old-licenses.html#FDL">
+ Older versions of the GNU FDL</a></li>
+</ul>
+
+<h3 id="Exceptions">Exceptions to GNU Licenses</h3>
+
+<p>Some GNU programs have additional permissions or special exceptions
+ to specific terms in one of the main licenses. Since some of those
+ are commonly used or inspire a lot of questions on their own, we've
+ started collecting them on
+ our <a href="/licenses/exceptions.html">exceptions
page</a>.</p>
+
+<h3 id="LicenseURLs">License URLs</h3>
+
+<p>When linking to our licenses, it's usually best to link to the latest
+version; hence the standard URLs such as
+<tt>http://www.gnu.org/licenses/gpl.html</tt> have no version
number.
+Occasionally, however, you may want to link to a specific version of a
+given license. In those situations, you can use the following links
+[<a href="#urlskip">skip links</a>]:</p>
+
+<dl>
+<dt>GNU General Public License (GPL)</dt>
+<!-- Please keep these links absolute. I'm depending on that for the
+ XSLT to generate pages on fsf.org. Thanks. -brett -->
+<dd><a
href="http://www.gnu.org/licenses/gpl-3.0.html">GPLv3</a>,
+<a href="http://www.gnu.org/licenses/gpl-2.0.html">GPLv2</a>,
+<a
href="http://www.gnu.org/licenses/gpl-1.0.html">GPLv1</a></dd>
+
+<dt>GNU Lesser General Public License (LGPL)</dt>
+<dd><a
href="http://www.gnu.org/licenses/lgpl-3.0.html">LGPLv3</a>,
+<a
href="http://www.gnu.org/licenses/lgpl-2.1.html">LGPLv2.1</a></dd>
+
+<dt>GNU Affero General Public License (AGPL)</dt>
+<dd><a href="http://www.gnu.org/licenses/agpl-3.0.html">GNU
+ AGPLv3</a> (The <a
+ href="http://www.affero.org/oagpl.html">Affero General
+ Public License version 1</a> is not a GNU license, but it was
+ designed to serve a purpose much like the GNU AGPL's.)</dd>
+
+<dt>GNU Free Documentation License (FDL)</dt>
+<dd><a
href="http://www.gnu.org/licenses/fdl-1.3.html">FDLv1.3</a>,
+<a href="http://www.gnu.org/licenses/fdl-1.2.html">FDLv1.2</a>,
+<a
href="http://www.gnu.org/licenses/fdl-1.1.html">FDLv1.1</a></dd>
+</dl>
+
+<p><a name="urlskip"></a>Stable links to each license's
alternative
+ formats are available on its respective page. Not every version of
+ every license is available in every format. If you need one that is
+ missing, please <a href="mailto:address@hidden">email
us</a>.</p>
+
+<p>See also the <a href="old-licenses/">old licenses
page</a>.</p>
+
+
+<h3>Unofficial Translations</h3>
+
+<p>
+Legally speaking, the original (English) version of the licenses is what
+specifies the actual distribution terms for GNU programs and others that
+use them. But to help people better understand the licenses, we give
+permission to publish translations into other languages provided that
+they follow our regulations for unofficial translations:
+</p>
+
+<ul>
+ <li>
+ <a href="/licenses/translations.html">List of unofficial
translations</a>
+ </li>
+ <li><a href="/licenses/translations.html#rules">How to create an
unofficial
+ translation</a></li>
+</ul>
+
+<h3 id="VerbatimCopying">Verbatim Copying and Distribution</h3>
+
+<p>The standard copyright terms for GNU web pages is now the <a
+href="http://creativecommons.org/licenses/by-nd/3.0/us/">Creative
+Commons Attribution-NoDerivs 3.0 United States License</a>. It used to
+be (and for a few pages still is): <em><span
class="highlight">Verbatim
+copying and distribution of this entire article are permitted worldwide,
+without royalty, in any medium, provided this notice is
+preserved</span>.</em> Please note the following commentary about
this
+“verbatim license” by Eben Moglen:</p>
+
+<p>
+“Our intention in using the phrase ‘verbatim copying in
+any medium’ is not to require retention of page headings and
+footers or other formatting features. Retention of weblinks in both
+hyperlinked and non-hyperlinked media (as notes or some other form of
+printed URL in non-HTML media) is required”.
+</p>
+
+<h3>List of Free Software Licenses</h3>
+
+<ul>
+ <li>
+ <a href="/licenses/license-list.html">List of Free Software
Licenses</a>
+
+<p> If you are contemplating writing a new license, please contact the
+FSF by writing to <a
+href="mailto:address@hidden"><address@hidden></a>. The
+proliferation of different free software licenses means increased work
+for users in understanding the licenses; we may be able to help you
+find an existing Free Software license that meets your needs.
+</p>
+
+<p>
+If that isn't possible, if you really need a new license, with our
+help you can ensure that the license really is a Free Software license
+and avoid various practical problems.
+</p>
+
+ </li>
+ </ul>
+
+
+<h3 id="WhatIsCopyleft">What Is Copyleft?</h3>
+
+<p>
+<a
href="/copyleft/copyleft.html"><em>Copyleft</em></a> is a
general
+method for making a program free
+software and requiring all modified and extended versions of the
+program to be free software as well.
+</p>
+
+<p>
+The simplest way to make a program free is to put it in the
+<a href="/philosophy/categories.html#PublicDomainSoftware">public
+domain</a>, uncopyrighted. This allows people to share the program
+and their improvements, if they are so minded. But it also allows
+uncooperative people to convert the program into
+<a href="/philosophy/categories.html#ProprietarySoftware">proprietary
+software</a>. They can make changes, many or few, and distribute the
+result as a proprietary product. People who receive the program in
+that modified form do not have the freedom that the original author
+gave them; the middleman has stripped it away.
+</p>
+
+<p>
+In the <a href="/gnu/thegnuproject.html">GNU project</a>, our aim
is
+to give <em>all</em> users the freedom to redistribute and change
GNU
+software. If middlemen could strip off the freedom, we might have
+many users, but those users would not have freedom. So instead of
+putting GNU software in the public domain, we “copyleft”
+it. Copyleft says that anyone who redistributes the software, with or
+without changes, must pass along the freedom to further copy and
+change it. Copyleft guarantees that every user has freedom.
+</p>
+
+<p>
+Copyleft also provides an
+<a href="/philosophy/pragmatic.html">incentive</a>
+for other programmers to add to free software.
+Important free programs such as the GNU C++ compiler exist
+only because of this.
+</p>
+
+<p>
+Copyleft also helps programmers who want to contribute
+<a
href="/software/software.html#HelpWriteSoftware">improvements</a> to
+<a href="/philosophy/free-sw.html">free software</a> get
permission to
+do that. These programmers often work for companies or universities
+that would do almost anything to get more money. A programmer may
+want to contribute her changes to the community, but her employer may
+want to turn the changes into a proprietary software product.
+</p>
+
+<p>
+When we explain to the employer that it is illegal to distribute the
+improved version except as free software, the employer usually decides
+to release it as free software rather than throw it away.
+</p>
+
+<p>
+To copyleft a program, we first state that it is copyrighted; then
+we add distribution terms, which are a legal instrument that gives
+everyone the rights to use, modify, and redistribute the program's
+code <em>or any program derived from it</em> but only if the
+distribution terms are unchanged. Thus, the code and the freedoms
+become legally inseparable.
+</p>
+
+<p>
+Proprietary software developers use copyright to take away the users'
+freedom; we use copyright to guarantee their freedom. That's why we
+reverse the name, changing “copyright” into
+“copyleft”.
+</p>
+
+<p>
+Copyleft is a general concept; there are many ways to fill in the
+details. In the GNU Project, the specific distribution terms that we
+use are contained in the GNU General Public License, the GNU Lesser
+General Public License and the GNU Free Documentation License.
+</p>
+
+<p>
+The appropriate license is included in many manuals and in each GNU
+source code distribution.
+</p>
+
+<p>
+The GNU GPL is designed so that you can easily apply it to your own
+program if you are the copyright holder. You don't have to modify the
+GNU GPL to do this, just add notices to your program which refer
+properly to the GNU GPL. Please note that you must use the
+entire text of the GPL, if you use it. It is an integral whole, and
+partial copies are not permitted. (Likewise for the LGPL, AGPL, and FDL.)
+</p>
+
+<p>
+Using the same distribution terms for many different programs makes it
+easy to copy code between various different programs. Since they all
+have the same distribution terms, there is no need to think about
+whether the terms are compatible. The Lesser GPL includes a
+provision that lets you alter the distribution terms to the ordinary
+GPL, so that you can copy code into another program covered by the GPL.
+</p>
+
+<h3>Licenses for Other Types of Works</h3>
+
+<p>
+We believe that published software and documentation should be
+<a href="/philosophy/free-doc.html">free software and free
documentation</a>.
+We recommend making all sorts of educational and reference works free
+also, using free documentation licenses such as the
+<a href="#FDL">GNU Free Documentation License</a> (GNU FDL).
+</p>
+
+<p>For essays of opinion and scientific papers, we recommend
+either the <a
+href="http://creativecommons.org/licenses/by-nd/3.0/us/">Creative
+Commons Attribution-NoDerivs 3.0 United States License</a>, or the
+simple “verbatim copying only” license stated above.</p>
+
+<p>
+We don't take the position that artistic or entertainment works must
+be free, but if you want to make one free, we recommend
+the <a href="http://artlibre.org/licence/lalgb.html">Free Art
+License</a>.</p>
+
+<!-- If needed, change the copyright block at the bottom. In general,
+ pages on the GNU web server should be under CC BY-ND 3.0 US.
+ Please do NOT change or remove this without talking
+ with the webmasters or licensing team first.
+ Please make sure the copyright date is consistent with the document
+ and that it is like this: "2001, 2002", not this: "2001-2002". -->
+</div><!-- for id="content", starts in the include above -->
+<!--#include virtual="/server/footer.html" -->
+<div id="footer">
+
+<p>Please send general FSF & GNU inquiries to
+<a href="mailto:address@hidden"><address@hidden></a>.
+There are also <a href="/contact/">other ways to contact</a>
+the FSF.<br />
+Please send broken links and other corrections or suggestions to
+<a
href="mailto:address@hidden"><em>address@hidden</em></a>.</p>
+
+<p>Please see the
+<a href="/server/standards/README.translations.html">Translations
+README</a> for information on coordinating and submitting
+translations of this article.</p>
+
+<p>Copyright © 2011 Free Software Foundation, Inc.</p>
+
+<p>This page is licensed under a <a rel="license"
+href="http://creativecommons.org/licenses/by-nd/3.0/us/">Creative
+Commons Attribution-NoDerivs 3.0 United States License</a>.</p>
+
+<p>Updated:
+<!-- timestamp start -->
+$Date: 2012/10/21 00:28:27 $
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>
+</pre></body></html>
Index: licenses/po/licenses.nl-diff.html
===================================================================
RCS file: licenses/po/licenses.nl-diff.html
diff -N licenses/po/licenses.nl-diff.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ licenses/po/licenses.nl-diff.html 21 Oct 2012 00:28:27 -0000 1.1
@@ -0,0 +1,456 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";>
+<!-- Generated by GNUN -->
+<html xmlns="http://www.w3.org/1999/xhtml"; xml:lang="en" lang="en">
+<head>
+<meta http-equiv="content-type" content="text/html; charset=utf-8" />
+<title>/licenses/licenses.html-diff</title>
+<style type="text/css">
+span.removed { background-color: #f22; color: #000; }
+span.inserted { background-color: #2f2; color: #000; }
+</style></head>
+<body><pre>
+<!--#include virtual="/server/header.html" -->
+<title>Licenses - GNU Project - Free Software Foundation
(FSF)</title>
+<!--#include virtual="/server/banner.html" -->
+<!--#include virtual="/licenses/po/licenses.translist" -->
+<h2>Licenses</h2>
+
+<p>
+Published software should be <a href="/philosophy/free-sw.html">free
+software</a>. To make it free software, you need to release it
+under a free software license. We normally use the <a
+href="#GPL">GNU General Public License</a> (GNU GPL),
+but occasionally we use <a
href="/licenses/license-list.html#SoftwareLicenses">other
+free software licenses</a>. We use only licenses that are compatible
+with the GNU GPL for GNU software.
+</p>
+
+<p>
+Documentation for free software should be
+<a href="/philosophy/free-doc.html">free documentation</a>, so that
+people can redistribute it and improve it along with the software
+it describes. To make it free documentation, you need to release
+it under a free documentation license. We normally use the
+<a href="#FDL">GNU Free Documentation License</a> (GNU
+FDL), but occasionally we use
+<a href="/licenses/license-list.html#DocumentationLicenses">other free
+documentation licenses</a>.
+</p>
+
+<p>If you've started a new project and you're not sure what license to
+use, <a href="/licenses/license-recommendations.html">“How to
+choose a license for your own work”</a> details our
+recommendations in an easy-to-follow guide. If you just want a quick
+list reference, we have a page that names
+our <a href="/licenses/recommended-copylefts.html">recommended
+copyleft licenses</a>.</p>
+
+<p>
+Our documentation licenses are currently being revised, and we welcome
+your comments on the proposed texts. Please
+visit <a href="http://gplv3.fsf.org">our license update site</a> to
+read the current drafts and participate in the process.
+</p>
+
+<h3>Common Resources for our Software Licenses</h3>
+
+<p>We have a number of resources to help people understand and use our
+various licenses:</p>
+
+<ul>
+
+ <li><a href="/licenses/gpl-faq.html">Frequently Asked
+ Questions about the GNU licenses</a></li>
+ <li><a href="/licenses/gpl-howto.html">How to use GNU licenses
for your
+ own software</a></li>
+ <li><a href="/licenses/gpl-violation.html">What to do if you see
a
+ violation of a GNU license</a></li>
+ <li><a href="/philosophy/university.html">Releasing Free
Software if
+ you work at a university</a></li>
+ <li><a href="/licenses/why-assign.html">Why the FSF gets
copyright
+ assignments from contributors</a></li>
+ <li><a href="/graphics/license-logos.html">GNU license
logos</a> to use
+ with your project</li>
+ <li><a
+<span
class="removed"><del><strong>href="/licenses/license-list.html#LicensingMailingList"><address@hidden>
+mailing list</a></strong></del></span> <span
class="inserted"><ins><em>href="http://www.fsf.org/licensing">The FSF
Licensing & Compliance Lab</a></li>
+ <li><a
+href="/licenses/license-list.html#LicensingEmailAddress"><address@hidden></a></em></ins></span>
for general licensing help
+ </li>
+
+</ul>
+
+<h3 id="GPL">The GNU General Public License</h3>
+
+<p>
+The GNU General Public License is often called the GNU GPL for short;
+it is used by most GNU programs, and by more than half of all free
+software packages. The latest version is version 3.
+</p>
+
+<ul>
+ <li>The GNU General Public License is available in these formats:
+ <a href="/licenses/gpl.html">HTML</a>,
+ <a href="/licenses/gpl.txt">plain text</a>,
+ <a href="/licenses/gpl.odt">ODF</a>,
+ <a href="/licenses/gpl.dbk">Docbook</a>,
+ <a href="/licenses/gpl.texi">Texinfo</a>, and
+ <a href="/licenses/gpl.tex">LaTeX</a>.
+These documents are not formatted for standalone publishing, and
+are intended to be included in another document.</li>
+ <li><a href="/licenses/quick-guide-gplv3.html">A Quick Guide to
+ GPLv3</a></li>
+ <li><a href="/licenses/old-licenses/old-licenses.html#GPL">Older
+ versions of the GNU GPL</a></li>
+</ul>
+
+<h3 id="LGPL">The GNU Lesser General Public License</h3>
+
+<p>
+The GNU Lesser General Public License is used by a few (not by any means
+all) GNU libraries. The latest version is version 3.
+</p>
+
+<ul>
+ <li>The GNU Lesser General Public License text is available in
+ these formats:
+ <a href="/licenses/lgpl.html">HTML</a>,
+ <a href="/licenses/lgpl.txt">plain text</a>,
+ <a href="/licenses/lgpl.dbk">Docbook</a>, and
+ <a href="/licenses/lgpl.texi">Texinfo</a>.
+These documents are not formatted for standalone publishing, and
+are intended to be included in another document.</li>
+ <li><a href="/licenses/why-not-lgpl.html">Why you shouldn't use
+ the Lesser GPL for your next library</a></li>
+ <li><a href="/licenses/old-licenses/old-licenses.html#LGPL">Older
+ versions of the GNU LGPL</a></li>
+</ul>
+
+<h3 id="AGPL">The GNU Affero General Public License</h3>
+
+<p>
+The GNU Affero General Public License is based on the GNU GPL, but has an
+additional term to allow users who interact with the licensed software over
+a network to receive the source for that program. We recommend that people
+consider using the GNU AGPL for any software which will commonly be run
+over a network. The latest version is version 3.
+</p>
+
+<ul>
+ <li>The GNU Affero General Public License text is available in
+ these formats:
+ <a href="/licenses/agpl.html">HTML</a>,
+ <a href="/licenses/agpl.txt">plain text</a>,
+ <a href="/licenses/agpl.dbk">Docbook</a>,
+ <a href="/licenses/agpl.texi">Texinfo</a>, and
+ <a href="/licenses/agpl.tex">LaTeX</a>.
+These documents are not formatted for standalone publishing, and
+are intended to be included in another document.</li>
+ <li><a href="/licenses/why-affero-gpl.html">Why the Affero
GPL</a></li>
+</ul>
+
+<h3 id="FDL">The GNU Free Documentation License</h3>
+
+<p>
+The GNU Free Documentation License is a form of copyleft intended
+for use on a manual, textbook or other document to assure everyone
+the effective freedom to copy and redistribute it, with or without
+modifications, either commercially or non-commercially. The latest version
+is 1.3.
+</p>
+
+<ul>
+ <li>The GNU Free Documentation License text is available in these
formats:
+ <a href="/licenses/fdl.html">HTML</a>,
+ <a href="/licenses/fdl.txt">plain text</a>,
+ <a href="/licenses/fdl.xml">Docbook</a>,
+ <a href="/licenses/fdl.texi">Texinfo</a>, and
+ <a href="/licenses/fdl.tex">LaTeX</a>.
+These documents are not formatted for standalone publishing, and
+are intended to be included in another document.</li>
+ <li><a href="/licenses/why-gfdl.html">Why publishers should use
+ the GNU FDL</a></li>
+ <li><a href="/licenses/fdl.html#addendum">How to use
+ the GNU FDL for your documentation</a></li>
+ <li><a href="/licenses/fdl-howto.html">Tips on using the GNU
FDL</a></li>
+ <li><a href="/licenses/fdl-howto-opt.html">How to use the
optional
+ features of the GNU FDL</a></li>
+ <li><a href="/licenses/old-licenses/old-licenses.html#FDL">
+ Older versions of the GNU FDL</a></li>
+</ul>
+
+<h3 id="Exceptions">Exceptions to GNU Licenses</h3>
+
+<p>Some GNU programs have additional permissions or special exceptions
+ to specific terms in one of the main licenses. Since some of those
+ are commonly used or inspire a lot of questions on their own, we've
+ started collecting them on
+ our <a href="/licenses/exceptions.html">exceptions
page</a>.</p>
+
+<h3 id="LicenseURLs">License URLs</h3>
+
+<p>When linking to our licenses, it's usually best to link to the latest
+version; hence the standard URLs such as
+<tt>http://www.gnu.org/licenses/gpl.html</tt> have no version
number.
+Occasionally, however, you may want to link to a specific version of a
+given license. In those situations, you can use the following links
+[<a href="#urlskip">skip links</a>]:</p>
+
+<dl>
+<dt>GNU General Public License (GPL)</dt>
+<!-- Please keep these links absolute. I'm depending on that for the
+ XSLT to generate pages on fsf.org. Thanks. -brett -->
+<dd><a
href="http://www.gnu.org/licenses/gpl-3.0.html">GPLv3</a>,
+<a href="http://www.gnu.org/licenses/gpl-2.0.html">GPLv2</a>,
+<a
href="http://www.gnu.org/licenses/gpl-1.0.html">GPLv1</a></dd>
+
+<dt>GNU Lesser General Public License (LGPL)</dt>
+<dd><a
href="http://www.gnu.org/licenses/lgpl-3.0.html">LGPLv3</a>,
+<a
href="http://www.gnu.org/licenses/lgpl-2.1.html">LGPLv2.1</a></dd>
+
+<dt>GNU Affero General Public License (AGPL)</dt>
+<dd><a href="http://www.gnu.org/licenses/agpl-3.0.html">GNU
+ AGPLv3</a> (The <a
+ href="http://www.affero.org/oagpl.html">Affero General
+ Public License version 1</a> is not a GNU license, but it was
+ designed to serve a purpose much like the GNU AGPL's.)</dd>
+
+<dt>GNU Free Documentation License (FDL)</dt>
+<dd><a
href="http://www.gnu.org/licenses/fdl-1.3.html">FDLv1.3</a>,
+<a href="http://www.gnu.org/licenses/fdl-1.2.html">FDLv1.2</a>,
+<a
href="http://www.gnu.org/licenses/fdl-1.1.html">FDLv1.1</a></dd>
+</dl>
+
+<p><a name="urlskip"></a>Stable links to each license's
alternative
+ formats are available on its respective page. Not every version of
+ every license is available in every format. If you need one that is
+ missing, please <a href="mailto:address@hidden">email
us</a>.</p>
+
+<p>See also the <a href="old-licenses/">old licenses
page</a>.</p>
+
+
+<h3>Unofficial Translations</h3>
+
+<p>
+Legally speaking, the original (English) version of the licenses is what
+specifies the actual distribution terms for GNU programs and others that
+use them. But to help people better understand the licenses, we give
+permission to publish translations into other languages provided that
+they follow our regulations for unofficial translations:
+</p>
+
+<ul>
+ <li>
+ <a href="/licenses/translations.html">List of unofficial
translations</a>
+ </li>
+ <li><a href="/licenses/translations.html#rules">How to create an
unofficial
+ translation</a></li>
+</ul>
+
+<h3 id="VerbatimCopying">Verbatim Copying and Distribution</h3>
+
+<p>The standard copyright terms for GNU web pages is now the <a
+href="http://creativecommons.org/licenses/by-nd/3.0/us/">Creative
+Commons Attribution-NoDerivs 3.0 United States License</a>. It used to
+be (and for a few pages still is): <em><span
class="highlight">Verbatim
+copying and distribution of this entire article are permitted worldwide,
+without royalty, in any medium, provided this notice is
+preserved</span>.</em> Please note the following commentary about
this
+“verbatim license” by Eben Moglen:</p>
+
+<p>
+“Our intention in using the phrase ‘verbatim copying in
+any medium’ is not to require retention of page headings and
+footers or other formatting features. Retention of weblinks in both
+hyperlinked and non-hyperlinked media (as notes or some other form of
+printed URL in non-HTML media) is required”.
+</p>
+
+<h3>List of Free Software Licenses</h3>
+
+<ul>
+ <li>
+ <a href="/licenses/license-list.html">List of Free Software
Licenses</a>
+
+<p> If you are contemplating writing a new license, please contact the
+FSF by writing to <a
+href="mailto:address@hidden"><address@hidden></a>. The
+proliferation of different free software licenses means increased work
+for users in understanding the licenses; we may be able to help you
+find an existing Free Software license that meets your needs.
+</p>
+
+<p>
+If that isn't possible, if you really need a new license, with our
+help you can ensure that the license really is a Free Software license
+and avoid various practical problems.
+</p>
+
+ </li>
+ </ul>
+
+
+<h3 id="WhatIsCopyleft">What Is Copyleft?</h3>
+
+<p>
+<a
href="/copyleft/copyleft.html"><em>Copyleft</em></a> is a
general
+method for making a program free
+software and requiring all modified and extended versions of the
+program to be free software as well.
+</p>
+
+<p>
+The simplest way to make a program free is to put it in the
+<a href="/philosophy/categories.html#PublicDomainSoftware">public
+domain</a>, uncopyrighted. This allows people to share the program
+and their improvements, if they are so minded. But it also allows
+uncooperative people to convert the program into
+<a href="/philosophy/categories.html#ProprietarySoftware">proprietary
+software</a>. They can make changes, many or few, and distribute the
+result as a proprietary product. People who receive the program in
+that modified form do not have the freedom that the original author
+gave them; the middleman has stripped it away.
+</p>
+
+<p>
+In the <a href="/gnu/thegnuproject.html">GNU project</a>, our aim
is
+to give <em>all</em> users the freedom to redistribute and change
GNU
+software. If middlemen could strip off the freedom, we might have
+many users, but those users would not have freedom. So instead of
+putting GNU software in the public domain, we “copyleft”
+it. Copyleft says that anyone who redistributes the software, with or
+without changes, must pass along the freedom to further copy and
+change it. Copyleft guarantees that every user has freedom.
+</p>
+
+<p>
+Copyleft also provides an
+<a href="/philosophy/pragmatic.html">incentive</a>
+for other programmers to add to free software.
+Important free programs such as the GNU C++ compiler exist
+only because of this.
+</p>
+
+<p>
+Copyleft also helps programmers who want to contribute
+<a
href="/software/software.html#HelpWriteSoftware">improvements</a> to
+<a href="/philosophy/free-sw.html">free software</a> get
permission to
+do that. These programmers often work for companies or universities
+that would do almost anything to get more money. A programmer may
+want to contribute her changes to the community, but her employer may
+want to turn the changes into a proprietary software product.
+</p>
+
+<p>
+When we explain to the employer that it is illegal to distribute the
+improved version except as free software, the employer usually decides
+to release it as free software rather than throw it away.
+</p>
+
+<p>
+To copyleft a program, we first state that it is copyrighted; then
+we add distribution terms, which are a legal instrument that gives
+everyone the rights to use, modify, and redistribute the program's
+code <em>or any program derived from it</em> but only if the
+distribution terms are unchanged. Thus, the code and the freedoms
+become legally inseparable.
+</p>
+
+<p>
+Proprietary software developers use copyright to take away the users'
+freedom; we use copyright to guarantee their freedom. That's why we
+reverse the name, changing “copyright” into
+“copyleft”.
+</p>
+
+<p>
+Copyleft is a general concept; there are many ways to fill in the
+details. In the GNU Project, the specific distribution terms that we
+use are contained in the GNU General Public License, the GNU Lesser
+General Public License and the GNU Free Documentation License.
+</p>
+
+<p>
+The appropriate license is included in many manuals and in each GNU
+source code distribution.
+</p>
+
+<p>
+The GNU GPL is designed so that you can easily apply it to your own
+program if you are the copyright holder. You don't have to modify the
+GNU GPL to do this, just add notices to your program which refer
+properly to the GNU GPL. Please note that you must use the
+entire text of the GPL, if you use it. It is an integral whole, and
+partial copies are not permitted. (Likewise for the LGPL, AGPL, and FDL.)
+</p>
+
+<p>
+Using the same distribution terms for many different programs makes it
+easy to copy code between various different programs. Since they all
+have the same distribution terms, there is no need to think about
+whether the terms are compatible. The Lesser GPL includes a
+provision that lets you alter the distribution terms to the ordinary
+GPL, so that you can copy code into another program covered by the GPL.
+</p>
+
+<h3>Licenses for Other Types of Works</h3>
+
+<p>
+We believe that published software and documentation should be
+<a href="/philosophy/free-doc.html">free software and free
documentation</a>.
+We recommend making all sorts of educational and reference works free
+also, using free documentation licenses such as the
+<a href="#FDL">GNU Free Documentation License</a> (GNU FDL).
+</p>
+
+<p>For essays of opinion and scientific papers, we recommend
+either the <a
+href="http://creativecommons.org/licenses/by-nd/3.0/us/">Creative
+Commons Attribution-NoDerivs 3.0 United States License</a>, or the
+simple “verbatim copying only” license stated above.</p>
+
+<p>
+We don't take the position that artistic or entertainment works must
+be free, but if you want to make one free, we recommend
+the <a href="http://artlibre.org/licence/lalgb.html">Free Art
+License</a>.</p>
+
+<!-- If needed, change the copyright block at the bottom. In general,
+ pages on the GNU web server should be under CC BY-ND 3.0 US.
+ Please do NOT change or remove this without talking
+ with the webmasters or licensing team first.
+ Please make sure the copyright date is consistent with the document
+ and that it is like this: "2001, 2002", not this: "2001-2002". -->
+</div><!-- for id="content", starts in the include above -->
+<!--#include virtual="/server/footer.html" -->
+<div id="footer">
+
+<p>Please send general FSF & GNU inquiries to
+<a href="mailto:address@hidden"><address@hidden></a>.
+There are also <a href="/contact/">other ways to contact</a>
+the FSF.<br />
+Please send broken links and other corrections or suggestions to
+<a
href="mailto:address@hidden"><em>address@hidden</em></a>.</p>
+
+<p>Please see the
+<a href="/server/standards/README.translations.html">Translations
+README</a> for information on coordinating and submitting
+translations of this article.</p>
+
+<p>Copyright © 2011 Free Software Foundation, Inc.</p>
+
+<p>This page is licensed under a <a rel="license"
+href="http://creativecommons.org/licenses/by-nd/3.0/us/">Creative
+Commons Attribution-NoDerivs 3.0 United States License</a>.</p>
+
+<p>Updated:
+<!-- timestamp start -->
+$Date: 2012/10/21 00:28:27 $
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>
+</pre></body></html>
Index: licenses/po/licenses.zh-cn-diff.html
===================================================================
RCS file: licenses/po/licenses.zh-cn-diff.html
diff -N licenses/po/licenses.zh-cn-diff.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ licenses/po/licenses.zh-cn-diff.html 21 Oct 2012 00:28:27 -0000
1.1
@@ -0,0 +1,456 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";>
+<!-- Generated by GNUN -->
+<html xmlns="http://www.w3.org/1999/xhtml"; xml:lang="en" lang="en">
+<head>
+<meta http-equiv="content-type" content="text/html; charset=utf-8" />
+<title>/licenses/licenses.html-diff</title>
+<style type="text/css">
+span.removed { background-color: #f22; color: #000; }
+span.inserted { background-color: #2f2; color: #000; }
+</style></head>
+<body><pre>
+<!--#include virtual="/server/header.html" -->
+<title>Licenses - GNU Project - Free Software Foundation
(FSF)</title>
+<!--#include virtual="/server/banner.html" -->
+<!--#include virtual="/licenses/po/licenses.translist" -->
+<h2>Licenses</h2>
+
+<p>
+Published software should be <a href="/philosophy/free-sw.html">free
+software</a>. To make it free software, you need to release it
+under a free software license. We normally use the <a
+href="#GPL">GNU General Public License</a> (GNU GPL),
+but occasionally we use <a
href="/licenses/license-list.html#SoftwareLicenses">other
+free software licenses</a>. We use only licenses that are compatible
+with the GNU GPL for GNU software.
+</p>
+
+<p>
+Documentation for free software should be
+<a href="/philosophy/free-doc.html">free documentation</a>, so that
+people can redistribute it and improve it along with the software
+it describes. To make it free documentation, you need to release
+it under a free documentation license. We normally use the
+<a href="#FDL">GNU Free Documentation License</a> (GNU
+FDL), but occasionally we use
+<a href="/licenses/license-list.html#DocumentationLicenses">other free
+documentation licenses</a>.
+</p>
+
+<p>If you've started a new project and you're not sure what license to
+use, <a href="/licenses/license-recommendations.html">“How to
+choose a license for your own work”</a> details our
+recommendations in an easy-to-follow guide. If you just want a quick
+list reference, we have a page that names
+our <a href="/licenses/recommended-copylefts.html">recommended
+copyleft licenses</a>.</p>
+
+<p>
+Our documentation licenses are currently being revised, and we welcome
+your comments on the proposed texts. Please
+visit <a href="http://gplv3.fsf.org">our license update site</a> to
+read the current drafts and participate in the process.
+</p>
+
+<h3>Common Resources for our Software Licenses</h3>
+
+<p>We have a number of resources to help people understand and use our
+various licenses:</p>
+
+<ul>
+
+ <li><a href="/licenses/gpl-faq.html">Frequently Asked
+ Questions about the GNU licenses</a></li>
+ <li><a href="/licenses/gpl-howto.html">How to use GNU licenses
for your
+ own software</a></li>
+ <li><a href="/licenses/gpl-violation.html">What to do if you see
a
+ violation of a GNU license</a></li>
+ <li><a href="/philosophy/university.html">Releasing Free
Software if
+ you work at a university</a></li>
+ <li><a href="/licenses/why-assign.html">Why the FSF gets
copyright
+ assignments from contributors</a></li>
+ <li><a href="/graphics/license-logos.html">GNU license
logos</a> to use
+ with your project</li>
+ <li><a
+<span
class="removed"><del><strong>href="/licenses/license-list.html#LicensingMailingList"><address@hidden>
+mailing list</a></strong></del></span> <span
class="inserted"><ins><em>href="http://www.fsf.org/licensing">The FSF
Licensing & Compliance Lab</a></li>
+ <li><a
+href="/licenses/license-list.html#LicensingEmailAddress"><address@hidden></a></em></ins></span>
for general licensing help
+ </li>
+
+</ul>
+
+<h3 id="GPL">The GNU General Public License</h3>
+
+<p>
+The GNU General Public License is often called the GNU GPL for short;
+it is used by most GNU programs, and by more than half of all free
+software packages. The latest version is version 3.
+</p>
+
+<ul>
+ <li>The GNU General Public License is available in these formats:
+ <a href="/licenses/gpl.html">HTML</a>,
+ <a href="/licenses/gpl.txt">plain text</a>,
+ <a href="/licenses/gpl.odt">ODF</a>,
+ <a href="/licenses/gpl.dbk">Docbook</a>,
+ <a href="/licenses/gpl.texi">Texinfo</a>, and
+ <a href="/licenses/gpl.tex">LaTeX</a>.
+These documents are not formatted for standalone publishing, and
+are intended to be included in another document.</li>
+ <li><a href="/licenses/quick-guide-gplv3.html">A Quick Guide to
+ GPLv3</a></li>
+ <li><a href="/licenses/old-licenses/old-licenses.html#GPL">Older
+ versions of the GNU GPL</a></li>
+</ul>
+
+<h3 id="LGPL">The GNU Lesser General Public License</h3>
+
+<p>
+The GNU Lesser General Public License is used by a few (not by any means
+all) GNU libraries. The latest version is version 3.
+</p>
+
+<ul>
+ <li>The GNU Lesser General Public License text is available in
+ these formats:
+ <a href="/licenses/lgpl.html">HTML</a>,
+ <a href="/licenses/lgpl.txt">plain text</a>,
+ <a href="/licenses/lgpl.dbk">Docbook</a>, and
+ <a href="/licenses/lgpl.texi">Texinfo</a>.
+These documents are not formatted for standalone publishing, and
+are intended to be included in another document.</li>
+ <li><a href="/licenses/why-not-lgpl.html">Why you shouldn't use
+ the Lesser GPL for your next library</a></li>
+ <li><a href="/licenses/old-licenses/old-licenses.html#LGPL">Older
+ versions of the GNU LGPL</a></li>
+</ul>
+
+<h3 id="AGPL">The GNU Affero General Public License</h3>
+
+<p>
+The GNU Affero General Public License is based on the GNU GPL, but has an
+additional term to allow users who interact with the licensed software over
+a network to receive the source for that program. We recommend that people
+consider using the GNU AGPL for any software which will commonly be run
+over a network. The latest version is version 3.
+</p>
+
+<ul>
+ <li>The GNU Affero General Public License text is available in
+ these formats:
+ <a href="/licenses/agpl.html">HTML</a>,
+ <a href="/licenses/agpl.txt">plain text</a>,
+ <a href="/licenses/agpl.dbk">Docbook</a>,
+ <a href="/licenses/agpl.texi">Texinfo</a>, and
+ <a href="/licenses/agpl.tex">LaTeX</a>.
+These documents are not formatted for standalone publishing, and
+are intended to be included in another document.</li>
+ <li><a href="/licenses/why-affero-gpl.html">Why the Affero
GPL</a></li>
+</ul>
+
+<h3 id="FDL">The GNU Free Documentation License</h3>
+
+<p>
+The GNU Free Documentation License is a form of copyleft intended
+for use on a manual, textbook or other document to assure everyone
+the effective freedom to copy and redistribute it, with or without
+modifications, either commercially or non-commercially. The latest version
+is 1.3.
+</p>
+
+<ul>
+ <li>The GNU Free Documentation License text is available in these
formats:
+ <a href="/licenses/fdl.html">HTML</a>,
+ <a href="/licenses/fdl.txt">plain text</a>,
+ <a href="/licenses/fdl.xml">Docbook</a>,
+ <a href="/licenses/fdl.texi">Texinfo</a>, and
+ <a href="/licenses/fdl.tex">LaTeX</a>.
+These documents are not formatted for standalone publishing, and
+are intended to be included in another document.</li>
+ <li><a href="/licenses/why-gfdl.html">Why publishers should use
+ the GNU FDL</a></li>
+ <li><a href="/licenses/fdl.html#addendum">How to use
+ the GNU FDL for your documentation</a></li>
+ <li><a href="/licenses/fdl-howto.html">Tips on using the GNU
FDL</a></li>
+ <li><a href="/licenses/fdl-howto-opt.html">How to use the
optional
+ features of the GNU FDL</a></li>
+ <li><a href="/licenses/old-licenses/old-licenses.html#FDL">
+ Older versions of the GNU FDL</a></li>
+</ul>
+
+<h3 id="Exceptions">Exceptions to GNU Licenses</h3>
+
+<p>Some GNU programs have additional permissions or special exceptions
+ to specific terms in one of the main licenses. Since some of those
+ are commonly used or inspire a lot of questions on their own, we've
+ started collecting them on
+ our <a href="/licenses/exceptions.html">exceptions
page</a>.</p>
+
+<h3 id="LicenseURLs">License URLs</h3>
+
+<p>When linking to our licenses, it's usually best to link to the latest
+version; hence the standard URLs such as
+<tt>http://www.gnu.org/licenses/gpl.html</tt> have no version
number.
+Occasionally, however, you may want to link to a specific version of a
+given license. In those situations, you can use the following links
+[<a href="#urlskip">skip links</a>]:</p>
+
+<dl>
+<dt>GNU General Public License (GPL)</dt>
+<!-- Please keep these links absolute. I'm depending on that for the
+ XSLT to generate pages on fsf.org. Thanks. -brett -->
+<dd><a
href="http://www.gnu.org/licenses/gpl-3.0.html">GPLv3</a>,
+<a href="http://www.gnu.org/licenses/gpl-2.0.html">GPLv2</a>,
+<a
href="http://www.gnu.org/licenses/gpl-1.0.html">GPLv1</a></dd>
+
+<dt>GNU Lesser General Public License (LGPL)</dt>
+<dd><a
href="http://www.gnu.org/licenses/lgpl-3.0.html">LGPLv3</a>,
+<a
href="http://www.gnu.org/licenses/lgpl-2.1.html">LGPLv2.1</a></dd>
+
+<dt>GNU Affero General Public License (AGPL)</dt>
+<dd><a href="http://www.gnu.org/licenses/agpl-3.0.html">GNU
+ AGPLv3</a> (The <a
+ href="http://www.affero.org/oagpl.html">Affero General
+ Public License version 1</a> is not a GNU license, but it was
+ designed to serve a purpose much like the GNU AGPL's.)</dd>
+
+<dt>GNU Free Documentation License (FDL)</dt>
+<dd><a
href="http://www.gnu.org/licenses/fdl-1.3.html">FDLv1.3</a>,
+<a href="http://www.gnu.org/licenses/fdl-1.2.html">FDLv1.2</a>,
+<a
href="http://www.gnu.org/licenses/fdl-1.1.html">FDLv1.1</a></dd>
+</dl>
+
+<p><a name="urlskip"></a>Stable links to each license's
alternative
+ formats are available on its respective page. Not every version of
+ every license is available in every format. If you need one that is
+ missing, please <a href="mailto:address@hidden">email
us</a>.</p>
+
+<p>See also the <a href="old-licenses/">old licenses
page</a>.</p>
+
+
+<h3>Unofficial Translations</h3>
+
+<p>
+Legally speaking, the original (English) version of the licenses is what
+specifies the actual distribution terms for GNU programs and others that
+use them. But to help people better understand the licenses, we give
+permission to publish translations into other languages provided that
+they follow our regulations for unofficial translations:
+</p>
+
+<ul>
+ <li>
+ <a href="/licenses/translations.html">List of unofficial
translations</a>
+ </li>
+ <li><a href="/licenses/translations.html#rules">How to create an
unofficial
+ translation</a></li>
+</ul>
+
+<h3 id="VerbatimCopying">Verbatim Copying and Distribution</h3>
+
+<p>The standard copyright terms for GNU web pages is now the <a
+href="http://creativecommons.org/licenses/by-nd/3.0/us/">Creative
+Commons Attribution-NoDerivs 3.0 United States License</a>. It used to
+be (and for a few pages still is): <em><span
class="highlight">Verbatim
+copying and distribution of this entire article are permitted worldwide,
+without royalty, in any medium, provided this notice is
+preserved</span>.</em> Please note the following commentary about
this
+“verbatim license” by Eben Moglen:</p>
+
+<p>
+“Our intention in using the phrase ‘verbatim copying in
+any medium’ is not to require retention of page headings and
+footers or other formatting features. Retention of weblinks in both
+hyperlinked and non-hyperlinked media (as notes or some other form of
+printed URL in non-HTML media) is required”.
+</p>
+
+<h3>List of Free Software Licenses</h3>
+
+<ul>
+ <li>
+ <a href="/licenses/license-list.html">List of Free Software
Licenses</a>
+
+<p> If you are contemplating writing a new license, please contact the
+FSF by writing to <a
+href="mailto:address@hidden"><address@hidden></a>. The
+proliferation of different free software licenses means increased work
+for users in understanding the licenses; we may be able to help you
+find an existing Free Software license that meets your needs.
+</p>
+
+<p>
+If that isn't possible, if you really need a new license, with our
+help you can ensure that the license really is a Free Software license
+and avoid various practical problems.
+</p>
+
+ </li>
+ </ul>
+
+
+<h3 id="WhatIsCopyleft">What Is Copyleft?</h3>
+
+<p>
+<a
href="/copyleft/copyleft.html"><em>Copyleft</em></a> is a
general
+method for making a program free
+software and requiring all modified and extended versions of the
+program to be free software as well.
+</p>
+
+<p>
+The simplest way to make a program free is to put it in the
+<a href="/philosophy/categories.html#PublicDomainSoftware">public
+domain</a>, uncopyrighted. This allows people to share the program
+and their improvements, if they are so minded. But it also allows
+uncooperative people to convert the program into
+<a href="/philosophy/categories.html#ProprietarySoftware">proprietary
+software</a>. They can make changes, many or few, and distribute the
+result as a proprietary product. People who receive the program in
+that modified form do not have the freedom that the original author
+gave them; the middleman has stripped it away.
+</p>
+
+<p>
+In the <a href="/gnu/thegnuproject.html">GNU project</a>, our aim
is
+to give <em>all</em> users the freedom to redistribute and change
GNU
+software. If middlemen could strip off the freedom, we might have
+many users, but those users would not have freedom. So instead of
+putting GNU software in the public domain, we “copyleft”
+it. Copyleft says that anyone who redistributes the software, with or
+without changes, must pass along the freedom to further copy and
+change it. Copyleft guarantees that every user has freedom.
+</p>
+
+<p>
+Copyleft also provides an
+<a href="/philosophy/pragmatic.html">incentive</a>
+for other programmers to add to free software.
+Important free programs such as the GNU C++ compiler exist
+only because of this.
+</p>
+
+<p>
+Copyleft also helps programmers who want to contribute
+<a
href="/software/software.html#HelpWriteSoftware">improvements</a> to
+<a href="/philosophy/free-sw.html">free software</a> get
permission to
+do that. These programmers often work for companies or universities
+that would do almost anything to get more money. A programmer may
+want to contribute her changes to the community, but her employer may
+want to turn the changes into a proprietary software product.
+</p>
+
+<p>
+When we explain to the employer that it is illegal to distribute the
+improved version except as free software, the employer usually decides
+to release it as free software rather than throw it away.
+</p>
+
+<p>
+To copyleft a program, we first state that it is copyrighted; then
+we add distribution terms, which are a legal instrument that gives
+everyone the rights to use, modify, and redistribute the program's
+code <em>or any program derived from it</em> but only if the
+distribution terms are unchanged. Thus, the code and the freedoms
+become legally inseparable.
+</p>
+
+<p>
+Proprietary software developers use copyright to take away the users'
+freedom; we use copyright to guarantee their freedom. That's why we
+reverse the name, changing “copyright” into
+“copyleft”.
+</p>
+
+<p>
+Copyleft is a general concept; there are many ways to fill in the
+details. In the GNU Project, the specific distribution terms that we
+use are contained in the GNU General Public License, the GNU Lesser
+General Public License and the GNU Free Documentation License.
+</p>
+
+<p>
+The appropriate license is included in many manuals and in each GNU
+source code distribution.
+</p>
+
+<p>
+The GNU GPL is designed so that you can easily apply it to your own
+program if you are the copyright holder. You don't have to modify the
+GNU GPL to do this, just add notices to your program which refer
+properly to the GNU GPL. Please note that you must use the
+entire text of the GPL, if you use it. It is an integral whole, and
+partial copies are not permitted. (Likewise for the LGPL, AGPL, and FDL.)
+</p>
+
+<p>
+Using the same distribution terms for many different programs makes it
+easy to copy code between various different programs. Since they all
+have the same distribution terms, there is no need to think about
+whether the terms are compatible. The Lesser GPL includes a
+provision that lets you alter the distribution terms to the ordinary
+GPL, so that you can copy code into another program covered by the GPL.
+</p>
+
+<h3>Licenses for Other Types of Works</h3>
+
+<p>
+We believe that published software and documentation should be
+<a href="/philosophy/free-doc.html">free software and free
documentation</a>.
+We recommend making all sorts of educational and reference works free
+also, using free documentation licenses such as the
+<a href="#FDL">GNU Free Documentation License</a> (GNU FDL).
+</p>
+
+<p>For essays of opinion and scientific papers, we recommend
+either the <a
+href="http://creativecommons.org/licenses/by-nd/3.0/us/">Creative
+Commons Attribution-NoDerivs 3.0 United States License</a>, or the
+simple “verbatim copying only” license stated above.</p>
+
+<p>
+We don't take the position that artistic or entertainment works must
+be free, but if you want to make one free, we recommend
+the <a href="http://artlibre.org/licence/lalgb.html">Free Art
+License</a>.</p>
+
+<!-- If needed, change the copyright block at the bottom. In general,
+ pages on the GNU web server should be under CC BY-ND 3.0 US.
+ Please do NOT change or remove this without talking
+ with the webmasters or licensing team first.
+ Please make sure the copyright date is consistent with the document
+ and that it is like this: "2001, 2002", not this: "2001-2002". -->
+</div><!-- for id="content", starts in the include above -->
+<!--#include virtual="/server/footer.html" -->
+<div id="footer">
+
+<p>Please send general FSF & GNU inquiries to
+<a href="mailto:address@hidden"><address@hidden></a>.
+There are also <a href="/contact/">other ways to contact</a>
+the FSF.<br />
+Please send broken links and other corrections or suggestions to
+<a
href="mailto:address@hidden"><em>address@hidden</em></a>.</p>
+
+<p>Please see the
+<a href="/server/standards/README.translations.html">Translations
+README</a> for information on coordinating and submitting
+translations of this article.</p>
+
+<p>Copyright © 2011 Free Software Foundation, Inc.</p>
+
+<p>This page is licensed under a <a rel="license"
+href="http://creativecommons.org/licenses/by-nd/3.0/us/">Creative
+Commons Attribution-NoDerivs 3.0 United States License</a>.</p>
+
+<p>Updated:
+<!-- timestamp start -->
+$Date: 2012/10/21 00:28:27 $
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>
+</pre></body></html>
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- www licenses/licenses.el.html licenses/licenses...,
GNUN <=