[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
www/licenses gpl-howto.ca.html gpl-howto.de.htm...
|
From: |
GNUN |
|
Subject: |
www/licenses gpl-howto.ca.html gpl-howto.de.htm... |
|
Date: |
Mon, 16 Oct 2017 14:29:28 -0400 (EDT) |
CVSROOT: /web/www
Module name: www
Changes by: GNUN <gnun> 17/10/16 14:29:28
Modified files:
licenses : gpl-howto.ca.html gpl-howto.de.html
gpl-howto.it.html gpl-howto.ja.html
gpl-howto.pl.html gpl-howto.pt-br.html
licenses/po : gpl-howto.ca-diff.html
Added files:
licenses/po : gpl-howto.de-diff.html gpl-howto.it-diff.html
gpl-howto.ja-diff.html gpl-howto.pl-diff.html
gpl-howto.pt-br-diff.html
Log message:
Automatic update by GNUnited Nations.
CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/gpl-howto.ca.html?cvsroot=www&r1=1.34&r2=1.35
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/gpl-howto.de.html?cvsroot=www&r1=1.49&r2=1.50
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/gpl-howto.it.html?cvsroot=www&r1=1.24&r2=1.25
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/gpl-howto.ja.html?cvsroot=www&r1=1.12&r2=1.13
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/gpl-howto.pl.html?cvsroot=www&r1=1.16&r2=1.17
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/gpl-howto.pt-br.html?cvsroot=www&r1=1.10&r2=1.11
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/gpl-howto.ca-diff.html?cvsroot=www&r1=1.1&r2=1.2
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/gpl-howto.de-diff.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/gpl-howto.it-diff.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/gpl-howto.ja-diff.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/gpl-howto.pl-diff.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/gpl-howto.pt-br-diff.html?cvsroot=www&rev=1.1
Patches:
Index: gpl-howto.ca.html
===================================================================
RCS file: /web/www/www/licenses/gpl-howto.ca.html,v
retrieving revision 1.34
retrieving revision 1.35
diff -u -b -r1.34 -r1.35
--- gpl-howto.ca.html 11 Jul 2016 08:08:20 -0000 1.34
+++ gpl-howto.ca.html 16 Oct 2017 18:29:26 -0000 1.35
@@ -1,4 +1,9 @@
-<!--#set var="ENGLISH_PAGE" value="/licenses/gpl-howto.en.html" -->
+<!--#set var="PO_FILE"
+ value='<a href="/licenses/po/gpl-howto.ca.po">
+ https://www.gnu.org/licenses/po/gpl-howto.ca.po</a>'
+ --><!--#set var="ORIGINAL_FILE" value="/licenses/gpl-howto.html"
+ --><!--#set var="DIFF_FILE" value="/licenses/po/gpl-howto.ca-diff.html"
+ --><!--#set var="OUTDATED_SINCE" value="2017-08-17" --><!--#set
var="ENGLISH_PAGE" value="/licenses/gpl-howto.en.html" -->
<!--#include virtual="/server/header.ca.html" -->
<!-- Parent-Version: 1.77 -->
@@ -9,6 +14,7 @@
<!--#include virtual="/licenses/po/gpl-howto.translist" -->
<!--#include virtual="/server/banner.ca.html" -->
+<!--#include virtual="/server/outdated.ca.html" -->
<h2>Com utilitzar les llicències de GNU en els vostres programes</h2>
<p>Aquà trobareu una breu explicació sobre la manera de publicar un programa
@@ -257,7 +263,7 @@
<p class="unprintable"><!-- timestamp start -->
Updated:
-$Date: 2016/07/11 08:08:20 $
+$Date: 2017/10/16 18:29:26 $
<!-- timestamp end -->
</p>
Index: gpl-howto.de.html
===================================================================
RCS file: /web/www/www/licenses/gpl-howto.de.html,v
retrieving revision 1.49
retrieving revision 1.50
diff -u -b -r1.49 -r1.50
--- gpl-howto.de.html 3 Dec 2016 23:45:06 -0000 1.49
+++ gpl-howto.de.html 16 Oct 2017 18:29:27 -0000 1.50
@@ -1,4 +1,9 @@
-<!--#set var="ENGLISH_PAGE" value="/licenses/gpl-howto.en.html" -->
+<!--#set var="PO_FILE"
+ value='<a href="/licenses/po/gpl-howto.de.po">
+ https://www.gnu.org/licenses/po/gpl-howto.de.po</a>'
+ --><!--#set var="ORIGINAL_FILE" value="/licenses/gpl-howto.html"
+ --><!--#set var="DIFF_FILE" value="/licenses/po/gpl-howto.de-diff.html"
+ --><!--#set var="OUTDATED_SINCE" value="2017-08-17" --><!--#set
var="ENGLISH_PAGE" value="/licenses/gpl-howto.en.html" -->
<!--#include virtual="/server/header.de.html" -->
<!-- Parent-Version: 1.77 -->
@@ -8,6 +13,7 @@
<!--#include virtual="/licenses/po/gpl-howto.translist" -->
<!--#include virtual="/server/banner.de.html" -->
+<!--#include virtual="/server/outdated.de.html" -->
<h2>GNU-Lizenzen: Tipps zur Verwendung</h2>
<p>Dies ist eine kurze Erläuterung, wie man ein Programm unter der <cite><a
@@ -300,7 +306,7 @@
<p class="unprintable"><!-- timestamp start -->
Letzte Ãnderung:
-$Date: 2016/12/03 23:45:06 $
+$Date: 2017/10/16 18:29:27 $
<!-- timestamp end -->
</p>
Index: gpl-howto.it.html
===================================================================
RCS file: /web/www/www/licenses/gpl-howto.it.html,v
retrieving revision 1.24
retrieving revision 1.25
diff -u -b -r1.24 -r1.25
--- gpl-howto.it.html 18 Mar 2015 09:26:48 -0000 1.24
+++ gpl-howto.it.html 16 Oct 2017 18:29:27 -0000 1.25
@@ -1,4 +1,9 @@
-<!--#set var="ENGLISH_PAGE" value="/licenses/gpl-howto.en.html" -->
+<!--#set var="PO_FILE"
+ value='<a href="/licenses/po/gpl-howto.it.po">
+ https://www.gnu.org/licenses/po/gpl-howto.it.po</a>'
+ --><!--#set var="ORIGINAL_FILE" value="/licenses/gpl-howto.html"
+ --><!--#set var="DIFF_FILE" value="/licenses/po/gpl-howto.it-diff.html"
+ --><!--#set var="OUTDATED_SINCE" value="2017-08-17" --><!--#set
var="ENGLISH_PAGE" value="/licenses/gpl-howto.en.html" -->
<!--#include virtual="/server/header.it.html" -->
<!-- Parent-Version: 1.77 -->
@@ -9,6 +14,7 @@
<!--#include virtual="/licenses/po/gpl-howto.translist" -->
<!--#include virtual="/server/banner.it.html" -->
+<!--#include virtual="/server/outdated.it.html" -->
<h2>Come usare le licenze GNU per il vostro software</h2>
<p>Questa è una breve spiegazione su come mettere un programma sotto <a
@@ -257,7 +263,7 @@
<p class="unprintable"><!-- timestamp start -->
Ultimo aggiornamento:
-$Date: 2015/03/18 09:26:48 $
+$Date: 2017/10/16 18:29:27 $
<!-- timestamp end -->
</p>
Index: gpl-howto.ja.html
===================================================================
RCS file: /web/www/www/licenses/gpl-howto.ja.html,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -b -r1.12 -r1.13
--- gpl-howto.ja.html 3 Feb 2016 09:13:15 -0000 1.12
+++ gpl-howto.ja.html 16 Oct 2017 18:29:27 -0000 1.13
@@ -1,4 +1,9 @@
-<!--#set var="ENGLISH_PAGE" value="/licenses/gpl-howto.en.html" -->
+<!--#set var="PO_FILE"
+ value='<a href="/licenses/po/gpl-howto.ja.po">
+ https://www.gnu.org/licenses/po/gpl-howto.ja.po</a>'
+ --><!--#set var="ORIGINAL_FILE" value="/licenses/gpl-howto.html"
+ --><!--#set var="DIFF_FILE" value="/licenses/po/gpl-howto.ja-diff.html"
+ --><!--#set var="OUTDATED_SINCE" value="2017-08-17" --><!--#set
var="ENGLISH_PAGE" value="/licenses/gpl-howto.en.html" -->
<!--#include virtual="/server/header.ja.html" -->
<!-- Parent-Version: 1.77 -->
@@ -8,6 +13,7 @@
<!--#include virtual="/licenses/po/gpl-howto.translist" -->
<!--#include virtual="/server/banner.ja.html" -->
+<!--#include virtual="/server/outdated.ja.html" -->
<h2>ããªãèªèº«ã®ã½ããã¦ã§ã¢ã«GNUã©ã¤ã»ã³ã¹ã使ãæ¹æ³</h2>
<p>ããã¯ãããããã°ã©ã ãã<a
href="/licenses/gpl.html">GNUä¸è¬å
¬è¡ã©ã¤ã»ã³ã¹</a>ã<a
@@ -189,7 +195,7 @@
<p class="unprintable"><!-- timestamp start -->
æçµæ´æ°:
-$Date: 2016/02/03 09:13:15 $
+$Date: 2017/10/16 18:29:27 $
<!-- timestamp end -->
</p>
Index: gpl-howto.pl.html
===================================================================
RCS file: /web/www/www/licenses/gpl-howto.pl.html,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -b -r1.16 -r1.17
--- gpl-howto.pl.html 10 Aug 2017 17:59:19 -0000 1.16
+++ gpl-howto.pl.html 16 Oct 2017 18:29:27 -0000 1.17
@@ -1,4 +1,9 @@
-<!--#set var="ENGLISH_PAGE" value="/licenses/gpl-howto.en.html" -->
+<!--#set var="PO_FILE"
+ value='<a href="/licenses/po/gpl-howto.pl.po">
+ https://www.gnu.org/licenses/po/gpl-howto.pl.po</a>'
+ --><!--#set var="ORIGINAL_FILE" value="/licenses/gpl-howto.html"
+ --><!--#set var="DIFF_FILE" value="/licenses/po/gpl-howto.pl-diff.html"
+ --><!--#set var="OUTDATED_SINCE" value="2017-08-17" --><!--#set
var="ENGLISH_PAGE" value="/licenses/gpl-howto.en.html" -->
<!--#include virtual="/server/header.pl.html" -->
<!-- Parent-Version: 1.77 -->
@@ -9,6 +14,7 @@
<!--#include virtual="/licenses/po/gpl-howto.translist" -->
<!--#include virtual="/server/banner.pl.html" -->
+<!--#include virtual="/server/outdated.pl.html" -->
<h2>Jak stosowaÄ licencje GNU dla swojego oprogramowania</h2>
<p>To jest krótkie objasnienie jak wydaÄ program na warunkach <a
@@ -297,7 +303,7 @@
<p class="unprintable"><!-- timestamp start -->
Aktualizowane:
-$Date: 2017/08/10 17:59:19 $
+$Date: 2017/10/16 18:29:27 $
<!-- timestamp end -->
</p>
Index: gpl-howto.pt-br.html
===================================================================
RCS file: /web/www/www/licenses/gpl-howto.pt-br.html,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -b -r1.10 -r1.11
--- gpl-howto.pt-br.html 21 Jan 2017 15:58:24 -0000 1.10
+++ gpl-howto.pt-br.html 16 Oct 2017 18:29:27 -0000 1.11
@@ -1,4 +1,9 @@
-<!--#set var="ENGLISH_PAGE" value="/licenses/gpl-howto.en.html" -->
+<!--#set var="PO_FILE"
+ value='<a href="/licenses/po/gpl-howto.pt-br.po">
+ https://www.gnu.org/licenses/po/gpl-howto.pt-br.po</a>'
+ --><!--#set var="ORIGINAL_FILE" value="/licenses/gpl-howto.html"
+ --><!--#set var="DIFF_FILE" value="/licenses/po/gpl-howto.pt-br-diff.html"
+ --><!--#set var="OUTDATED_SINCE" value="2017-08-17" --><!--#set
var="ENGLISH_PAGE" value="/licenses/gpl-howto.en.html" -->
<!--#include virtual="/server/header.pt-br.html" -->
<!-- Parent-Version: 1.77 -->
@@ -9,6 +14,7 @@
<!--#include virtual="/licenses/po/gpl-howto.translist" -->
<!--#include virtual="/server/banner.pt-br.html" -->
+<!--#include virtual="/server/outdated.pt-br.html" -->
<h2>Como usar as licenças GNU para seu próprio software</h2>
<p>Esta é uma breve explicação de como colocar um programa sob a <a
@@ -286,7 +292,7 @@
<p class="unprintable"><!-- timestamp start -->
Ãltima atualização:
-$Date: 2017/01/21 15:58:24 $
+$Date: 2017/10/16 18:29:27 $
<!-- timestamp end -->
</p>
Index: po/gpl-howto.ca-diff.html
===================================================================
RCS file: /web/www/www/licenses/po/gpl-howto.ca-diff.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- po/gpl-howto.ca-diff.html 4 Jun 2014 00:29:29 -0000 1.1
+++ po/gpl-howto.ca-diff.html 16 Oct 2017 18:29:27 -0000 1.2
@@ -11,7 +11,7 @@
</style></head>
<body><pre>
<!--#include virtual="/server/header.html" -->
-<!-- Parent-Version: <span
class="removed"><del><strong>1.76</strong></del></span> <span
class="inserted"><ins><em>1.77</em></ins></span> -->
+<!-- Parent-Version: <span
class="removed"><del><strong>1.77</strong></del></span> <span
class="inserted"><ins><em>1.84</em></ins></span> -->
<title>How to use GNU licenses for your own software
- GNU Project - Free Software Foundation</title>
<!--#include virtual="/licenses/po/gpl-howto.translist" -->
@@ -20,14 +20,18 @@
<p>This is a brief explanation of how to place a program under the <a
href="/licenses/gpl.html">GNU General Public License</a>, <a
-href="/licenses/lgpl.html">Lesser General Public License</a>, or <a
-href="/licenses/agpl.html">Affero General Public License</a>. For the
+<span
class="removed"><del><strong>href="/licenses/lgpl.html">Lesser</strong></del></span>
+<span class="inserted"><ins><em>href="/licenses/lgpl.html">GNU
Lesser</em></ins></span> General Public License</a>, or <a
+<span
class="removed"><del><strong>href="/licenses/agpl.html">Affero</strong></del></span>
+<span class="inserted"><ins><em>href="/licenses/agpl.html">GNU
Affero</em></ins></span> General Public License</a>. For the
<a href="/licenses/fdl.html">GNU Free Documentation License</a>,
we have
a <a href="/licenses/fdl-howto.html">separate page</a>.</p>
-<p>If you are looking for more detailed information, consider perusing
-our list of <a href="/licenses/gpl-faq.html">frequently asked questions
-about our licenses</a>.</p>
+<span class="removed"><del><strong><p>If you are looking for more
detailed</strong></del></span>
+
+<span class="inserted"><ins><em><p>For further</em></ins></span>
information, <span class="removed"><del><strong>consider
perusing</strong></del></span> <span
class="inserted"><ins><em>see</em></ins></span> our list
+of <a href="/licenses/gpl-faq.html">frequently asked questions about
+our licenses</a>.</p>
<p>If you are considering using the GNU Lesser General Public License,
please read the article “<a href="/licenses/why-not-lgpl.html">Why
@@ -35,18 +39,69 @@
article explains why it may be better to use the ordinary GPL instead,
and how we would make the decision.</p>
-<p>Whichever license you plan to use, the process involves adding two
-elements to each source file of your program: a copyright notice (such
-as “Copyright 1999 Terry Jones”), and a statement of copying
-permission, saying that the program is distributed under the terms of
-the GNU General Public License (or the Lesser GPL).</p>
+<span class="removed"><del><strong><p>Whichever
license</strong></del></span>
+
+<span class="inserted"><ins><em><p>Here's a brief summary of
what</em></ins></span> you <span
class="removed"><del><strong>plan</strong></del></span> <span
class="inserted"><ins><em>need</em></ins></span> to <span
class="removed"><del><strong>use,</strong></del></span> <span
class="inserted"><ins><em>do to release a program
+under one of our licenses:</p>
+
+<ul>
+<li>Get a copyright disclaimer from your employer or school.</li>
+<li>Give each file the proper copyright notices.</li>
+<li>Add a COPYING file with a copy of the GNU GPL or GNU AGPL.</li>
+<li>Also add a COPYING.LESSER file with a copy of</em></ins></span> the
<span class="removed"><del><strong>process</strong></del></span> <span
class="inserted"><ins><em>GNU LGPL, if you
+use that.</li>
+<li>Put a license notice in each file.</li>
+<li>(Optionally) make the program display a startup notice.</li>
+<li>(If using the AGPL) make the program offer copies of its source
code.</li>
+</ul>
+
+<p>This</em></ins></span> involves adding two elements to each source
file of your
+program: a copyright notice (such as “Copyright 1999 Terry
+Jones”), and a statement of copying permission, saying that the
+program is distributed under the terms of the GNU General Public
+License (or the Lesser <span class="inserted"><ins><em>GPL, or the
Affero</em></ins></span> GPL).</p>
+
+<span class="inserted"><ins><em><h3>The copyright disclaimer</h3>
+
+<p>To avoid possible legal complications later, it's wise to ask your
+employer or school, if any, to sign a copyright disclaimer for your
+program, so it cannot later claim that the copyright belongs to it
+and that you had no right to release the program at all. This really
+has nothing to do with the GNU GPL—it applies no matter which
+free software license you use to release the program.</p>
+
+<p>Here is a sample copyright disclaimer; just alter the names, title,
+and program description as appropriate:</p>
+
+<blockquote>
+<p>Yoyodyne, Inc., hereby disclaims all copyright interest
+in the program “Woodpecker” (which deconstructs trees)
+written by James Hacker.</p>
+
+<p><em>signature of Moe Ghoul</em> 1 April 1989<br />
+ Moe Ghoul, President of Vice</p>
+</blockquote>
+
+<p>If you are a university student, we recommend you request the
+disclaimer <a href="/philosophy/university.html"> at an early stage in
+writing the program</a> to reduce resistance. If you are not a
+research assistant or teaching assistant, it could be that the university
+has no claim to copyright on your work, but ask a lawyer to make
+sure of that.</p>
+
+<p>If you work, the best time to negotiate permission to release free
+software is <em>when negotiating your employment
agreement</em>.</p>
+
+<h3>The copyright notice</h3></em></ins></span>
<p>The copyright notice should include the year in which you finished
-preparing the release (so if you finished it in 1998 but didn't post it
-until 1999, use 1998). You should add the proper year for each release;
-for example, “Copyright 1998, 1999 Terry Jones” if some
-versions were finished in 1998 and some were finished in 1999. If
-several people helped write the code, use all their names.</p>
+preparing the release (so if you finished it in 1998 but didn't post
+it until 1999, use 1998). You should add the proper year for each
+<span class="inserted"><ins><em>past</em></ins></span> release; for example,
“Copyright 1998, 1999 Terry
+Jones” if some
+<span class="removed"><del><strong>versions</strong></del></span> <span
class="inserted"><ins><em>releases</em></ins></span> were finished in 1998 and
some were
+finished in 1999. If several people helped write the code, use all
+their names.</p>
<p>For software with several releases over multiple years, it's okay
to use a range (“2008-2010”) instead of listing individual
@@ -60,22 +115,32 @@
languages. The copyright symbol “©” can be included if
you wish (and your character set supports it), but it's not necessary.
There is no legal significance to using the three-character sequence
-“(C)”, although it does no harm.</p>
+“(C)”, <span
class="removed"><del><strong>although</strong></del></span> <span
class="inserted"><ins><em>but</em></ins></span> it does no harm.</p>
+
+<span class="inserted"><ins><em><p>If you have copied code from other
programs covered by the same
+license, copy their copyright notices too. Put all the copyright
+notices for a file together, right near the top of the file.</p>
+
+<h3>The license files</h3></em></ins></span>
<p>You should also include a copy of the license itself somewhere in the
distribution of your program. All programs, whether they are released
under the GPL or LGPL, should include <a href="/licenses/gpl.txt">the
-text version of the GPL</a>. In GNU programs the license is usually in
-a file called COPYING.</p>
+text version of the GPL</a>. In GNU programs <span
class="inserted"><ins><em>we conventionally put</em></ins></span> the
+license <span class="removed"><del><strong>is usually</strong></del></span> in
a file called COPYING.</p>
+
+<p>If you are releasing your program under the <span
class="removed"><del><strong>LGPL,</strong></del></span> <span
class="inserted"><ins><em>GNU AGPL,
+use <a href="/licenses/agpl.txt">the text version of the GNU
AGPL</a>
+instead of the GNU GPL.</p>
-<p>If you are releasing your program under the LGPL, you should also
+<p>If you are releasing your program under the Lesser
GPL,</em></ins></span> you should also
include <a href="/licenses/lgpl.txt">the text version of the
LGPL</a>,
usually in a file called COPYING.LESSER. Please note that, since the
-LGPL is a set of additional permissions on top of the GPL, it's important
+LGPL is a set of additional permissions on top of the GPL, it's <span
class="removed"><del><strong>important</strong></del></span> <span
class="inserted"><ins><em>crucial</em></ins></span>
to include both licenses so users have all the materials they need to
understand their rights.</p>
-<p>If you are releasing your program under the GNU AGPL, you only need to
+<span class="removed"><del><strong><p>If you are releasing your program
under the GNU AGPL, you only need to
include <a href="/licenses/agpl.txt">the text version of the GNU
AGPL</a>.</p>
@@ -87,9 +152,14 @@
information for how to reach you, perhaps in the README file, but this
has nothing to do with the legal issues of applying the license.</p>
-<p>The copying permission statement should come right after the
-copyright notices. For a one-file program, the statement (for the GPL)
-should look like this:</p>
+<p>The</strong></del></span>
+
+<span class="inserted"><ins><em><h3>The license notices</h3>
+
+<p>Each file's</em></ins></span> copying permission statement <span
class="inserted"><ins><em>(also called the license notice)</em></ins></span>
+should come right after <span
class="removed"><del><strong>the</strong></del></span> <span
class="inserted"><ins><em>its</em></ins></span> copyright notices. For a
one-file
+program, the statement (for the GPL) should look like <span
class="removed"><del><strong>this:</p></strong></del></span> <span
class="inserted"><ins><em>this, to use
+GPL version 3 or later:</p></em></ins></span>
<pre>
This program is free software: you can redistribute it and/or modify
@@ -125,9 +195,14 @@
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
- along with Foobar. If not, see <http://www.gnu.org/licenses/>.
+ along with <span class="removed"><del><strong>Foobar. If not, see
<http://www.gnu.org/licenses/>.
+</pre></strong></del></span> <span class="inserted"><ins><em>Foobar. If
not, see <http://www.gnu.org/licenses/>.
</pre>
+<p>To use a different set of GPL versions, you would modify the end of
+the first long paragraph. For instance, to license under version 2 or
+later, you would replace “3” with
“2”.</p></em></ins></span>
+
<p>This statement should go near the beginning of every source file,
close to the copyright notices. When using the Lesser GPL, insert the
word “Lesser” before “General” in <em>all
@@ -135,11 +210,35 @@
word “Affero” before “General” in <em>all
three</em> places.</p>
+<span class="inserted"><ins><em><h3>Why license notices?</h3>
+
+<p>The purpose of a free software license is to give certain rights to
+all users of a program. If it is not clear what rights you have given
+them, that defeats the purpose. Our practices are designed to
+avoid any uncertainty.</p>
+
+<p>If a program has a copy of a license FOO alongside the source files,
+but doesn't have an explicit statement that “This program is
+released under license FOO,” that leaves room for uncertainty
+about whether the license FOO applies to the code of that program.</p>
+
+<p>If a release has one statement that “This program is released
+under license FOO,” in a central place such as the README file,
+that makes the situation clear <em>for that release</em>. However,
+programmers often copy source files from one free program into
+another. If a source file contains no statement about what its
+license is, then moving it into another context eliminates all trace
+of that point. This invites confusion and error.</p>
+
+<h3>The startup notice</h3></em></ins></span>
+
<p>For interactive programs, it is usually a good idea to make the
-program print out a brief notice about copyright and copying permission
+program <span class="removed"><del><strong>print out</strong></del></span>
<span class="inserted"><ins><em>display</em></ins></span> a brief notice about
copyright and copying permission
when it starts up. See <a href="/licenses/gpl-3.0.html#howto">the end
of the GNU GPL</a> for more information about this.</p>
+<span class="inserted"><ins><em><h3>The Affero
notice</h3></em></ins></span>
+
<p>If you are releasing your program under the GNU AGPL, and it can
interact with users over a network, the program should offer its source to
those users in some way. For example, if your program is a web
@@ -148,14 +247,21 @@
that you can choose a method that's suitable for your specific
program—see section 13 for details.</p>
+<span class="inserted"><ins><em><h3>Miscellaneous</h3>
+
+<p>It is very important for practical reasons to include contact
+information for how to reach you, perhaps in the README file, but this
+has nothing to do with the legal issues of applying the
license.</p></em></ins></span>
+
<p>There is no legal requirement to register your copyright with anyone;
-simply distributing the program makes it copyrighted. However, it is a
-very good idea to register the copyright with the US Registry of
+simply <span class="removed"><del><strong>distributing</strong></del></span>
<span class="inserted"><ins><em>writing</em></ins></span> the program makes it
copyrighted. However, <span class="inserted"><ins><em>for the
US,</em></ins></span>
+it is a
+<span class="removed"><del><strong>very</strong></del></span> good idea to
register the copyright with the US Registry of
Copyrights, because that puts you in a stronger position against anyone
who violates the license in the US. Most other countries have no system
of copyright registration.</p>
-<p>It's wise to ask your employer or school, if any, to sign a
+<span class="removed"><del><strong><p>It's wise to ask your employer or
school, if any, to sign a
copyright disclaimer for the work, so they cannot claim to hold it
later. Below is a sample copyright disclaimer; just alter the names
and program description as appropriate:</p>
@@ -165,21 +271,26 @@
compilers) written by James Hacker.</p>
<p><signature of Moe Ghoul>, 1 April 1989<br />
- Moe Ghoul, President of Vice</p></blockquote>
+ Moe Ghoul, President of
Vice</p></blockquote></strong></del></span>
-<p>We would like to list all free software programs in the Free Software
-Directory, including all programs licensed under the GPL (any version).
-Please see the <a href="http://directory.fsf.org/">Directory web
page</a>
-for information and an online submission form.</p>
+<p>We would like to list all free software programs in the Free
+Software Directory, including all programs licensed under the GPL (any
+version). <span class="inserted"><ins><em>So please submit an entry for your
program, when it has
+reached the point of being useful.</em></ins></span> Please see
+the <a href="http://directory.fsf.org/">Directory web page</a> for
+information and an online submission form.</p>
<p>It is also possible to make your program a GNU package, a part of the
-GNU Project. (That's if we like the program—we have to look at it
-first, and decide.) If you might be interested in joining up with the
+GNU Project. <span class="removed"><del><strong>(That's if we like the
program—we have to look at it
+first, and decide.)</strong></del></span> If you might be interested in
joining up with the
GNU Project in this way, please see our <a
href="/help/evaluation.html">GNU software evaluation page</a> for more
-information and a short questionnaire.</p>
+information and a short <span
class="removed"><del><strong>questionnaire.</p>
+
+<p>But you</strong></del></span> <span
class="inserted"><ins><em>questionnaire. We will respond and discuss the
+matter with you.</p>
-<p>But you are welcome to use any of our licenses even if your program
+<p>You</em></ins></span> are welcome to use any of our licenses even if
your program
is not a GNU package; indeed, we hope you will. They're available to
everyone. If you'd like to advertise your use of a particular license,
feel free to use <a href="/graphics/license-logos.html"
@@ -217,7 +328,7 @@
<!-- Regarding copyright, in general, standalone pages (as opposed to
files generated as part of manuals) on the GNU web server should
- be under CC BY-ND 3.0 US. Please do NOT change or remove this
+ be under CC BY-ND <span class="removed"><del><strong>3.0
US.</strong></del></span> <span
class="inserted"><ins><em>4.0.</em></ins></span> 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. For web pages, it is ok to list just the latest year the
@@ -232,20 +343,19 @@
There is more detail about copyright years in the GNU Maintainers
Information document, www.gnu.org/prep/maintain. -->
-<p>Copyright © 2001, 2007, 2008, 2009, <span
class="removed"><del><strong>2013</strong></del></span> <span
class="inserted"><ins><em>2013, 2014</em></ins></span>
+<p>Copyright © 2001, 2007, 2008, 2009, 2013, <span
class="removed"><del><strong>2014</strong></del></span> <span
class="inserted"><ins><em>2014, 2017</em></ins></span>
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>
+<span
class="removed"><del><strong>href="http://creativecommons.org/licenses/by-nd/3.0/us/">Creative</strong></del></span>
+<span
class="inserted"><ins><em>href="http://creativecommons.org/licenses/by-nd/4.0/">Creative</em></ins></span>
+Commons <span class="removed"><del><strong>Attribution-NoDerivs 3.0 United
States</strong></del></span> <span
class="inserted"><ins><em>Attribution-NoDerivatives 4.0
International</em></ins></span> License</a>.</p>
<!--#include virtual="/server/bottom-notes.html" -->
-<span
class="removed"><del><strong><p></p><p</strong></del></span>
-
-<span class="inserted"><ins><em><p</em></ins></span>
class="unprintable">Updated:
+<p class="unprintable">Updated:
<!-- timestamp start -->
-$Date: 2014/06/04 00:29:29 $
+$Date: 2017/10/16 18:29:27 $
<!-- timestamp end -->
</p>
</div>
Index: po/gpl-howto.de-diff.html
===================================================================
RCS file: po/gpl-howto.de-diff.html
diff -N po/gpl-howto.de-diff.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ po/gpl-howto.de-diff.html 16 Oct 2017 18:29:27 -0000 1.1
@@ -0,0 +1,365 @@
+<!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/gpl-howto.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" -->
+<!-- Parent-Version: <span
class="removed"><del><strong>1.77</strong></del></span> <span
class="inserted"><ins><em>1.84</em></ins></span> -->
+<title>How to use GNU licenses for your own software
+- GNU Project - Free Software Foundation</title>
+<!--#include virtual="/licenses/po/gpl-howto.translist" -->
+<!--#include virtual="/server/banner.html" -->
+<h2>How to use GNU licenses for your own software</h2>
+
+<p>This is a brief explanation of how to place a program under the <a
+href="/licenses/gpl.html">GNU General Public License</a>, <a
+<span
class="removed"><del><strong>href="/licenses/lgpl.html">Lesser</strong></del></span>
+<span class="inserted"><ins><em>href="/licenses/lgpl.html">GNU
Lesser</em></ins></span> General Public License</a>, or <a
+<span
class="removed"><del><strong>href="/licenses/agpl.html">Affero</strong></del></span>
+<span class="inserted"><ins><em>href="/licenses/agpl.html">GNU
Affero</em></ins></span> General Public License</a>. For the
+<a href="/licenses/fdl.html">GNU Free Documentation License</a>,
we have
+a <a href="/licenses/fdl-howto.html">separate page</a>.</p>
+
+<span class="removed"><del><strong><p>If you are looking for more
detailed</strong></del></span>
+
+<span class="inserted"><ins><em><p>For further</em></ins></span>
information, <span class="removed"><del><strong>consider
perusing</strong></del></span> <span
class="inserted"><ins><em>see</em></ins></span> our list
+of <a href="/licenses/gpl-faq.html">frequently asked questions about
+our licenses</a>.</p>
+
+<p>If you are considering using the GNU Lesser General Public License,
+please read the article “<a href="/licenses/why-not-lgpl.html">Why
+you shouldn't use the LGPL for your next library</a>” first. The
+article explains why it may be better to use the ordinary GPL instead,
+and how we would make the decision.</p>
+
+<span class="removed"><del><strong><p>Whichever
license</strong></del></span>
+
+<span class="inserted"><ins><em><p>Here's a brief summary of
what</em></ins></span> you <span
class="removed"><del><strong>plan</strong></del></span> <span
class="inserted"><ins><em>need</em></ins></span> to <span
class="removed"><del><strong>use,</strong></del></span> <span
class="inserted"><ins><em>do to release a program
+under one of our licenses:</p>
+
+<ul>
+<li>Get a copyright disclaimer from your employer or school.</li>
+<li>Give each file the proper copyright notices.</li>
+<li>Add a COPYING file with a copy of the GNU GPL or GNU AGPL.</li>
+<li>Also add a COPYING.LESSER file with a copy of</em></ins></span> the
<span class="removed"><del><strong>process</strong></del></span> <span
class="inserted"><ins><em>GNU LGPL, if you
+use that.</li>
+<li>Put a license notice in each file.</li>
+<li>(Optionally) make the program display a startup notice.</li>
+<li>(If using the AGPL) make the program offer copies of its source
code.</li>
+</ul>
+
+<p>This</em></ins></span> involves adding two elements to each source
file of your
+program: a copyright notice (such as “Copyright 1999 Terry
+Jones”), and a statement of copying permission, saying that the
+program is distributed under the terms of the GNU General Public
+License (or the Lesser <span class="inserted"><ins><em>GPL, or the
Affero</em></ins></span> GPL).</p>
+
+<span class="inserted"><ins><em><h3>The copyright disclaimer</h3>
+
+<p>To avoid possible legal complications later, it's wise to ask your
+employer or school, if any, to sign a copyright disclaimer for your
+program, so it cannot later claim that the copyright belongs to it
+and that you had no right to release the program at all. This really
+has nothing to do with the GNU GPL—it applies no matter which
+free software license you use to release the program.</p>
+
+<p>Here is a sample copyright disclaimer; just alter the names, title,
+and program description as appropriate:</p>
+
+<blockquote>
+<p>Yoyodyne, Inc., hereby disclaims all copyright interest
+in the program “Woodpecker” (which deconstructs trees)
+written by James Hacker.</p>
+
+<p><em>signature of Moe Ghoul</em> 1 April 1989<br />
+ Moe Ghoul, President of Vice</p>
+</blockquote>
+
+<p>If you are a university student, we recommend you request the
+disclaimer <a href="/philosophy/university.html"> at an early stage in
+writing the program</a> to reduce resistance. If you are not a
+research assistant or teaching assistant, it could be that the university
+has no claim to copyright on your work, but ask a lawyer to make
+sure of that.</p>
+
+<p>If you work, the best time to negotiate permission to release free
+software is <em>when negotiating your employment
agreement</em>.</p>
+
+<h3>The copyright notice</h3></em></ins></span>
+
+<p>The copyright notice should include the year in which you finished
+preparing the release (so if you finished it in 1998 but didn't post
+it until 1999, use 1998). You should add the proper year for each
+<span class="inserted"><ins><em>past</em></ins></span> release; for example,
“Copyright 1998, 1999 Terry
+Jones” if some
+<span class="removed"><del><strong>versions</strong></del></span> <span
class="inserted"><ins><em>releases</em></ins></span> were finished in 1998 and
some were
+finished in 1999. If several people helped write the code, use all
+their names.</p>
+
+<p>For software with several releases over multiple years, it's okay
+to use a range (“2008-2010”) instead of listing individual
+years (“2008, 2009, 2010”) if and only if every year in
+the range, inclusive, really is a “copyrightable” year
+that would be listed individually; <em>and</em> you make an
explicit
+statement in your documentation about this usage.</p>
+
+<p>Always use the English word “Copyright”; by international
+convention, this is used worldwide, even for material in other
+languages. The copyright symbol “©” can be included if
+you wish (and your character set supports it), but it's not necessary.
+There is no legal significance to using the three-character sequence
+“(C)”, <span
class="removed"><del><strong>although</strong></del></span> <span
class="inserted"><ins><em>but</em></ins></span> it does no harm.</p>
+
+<span class="inserted"><ins><em><p>If you have copied code from other
programs covered by the same
+license, copy their copyright notices too. Put all the copyright
+notices for a file together, right near the top of the file.</p>
+
+<h3>The license files</h3></em></ins></span>
+
+<p>You should also include a copy of the license itself somewhere in the
+distribution of your program. All programs, whether they are released
+under the GPL or LGPL, should include <a href="/licenses/gpl.txt">the
+text version of the GPL</a>. In GNU programs <span
class="inserted"><ins><em>we conventionally put</em></ins></span> the
+license <span class="removed"><del><strong>is usually</strong></del></span> in
a file called COPYING.</p>
+
+<p>If you are releasing your program under the <span
class="removed"><del><strong>LGPL,</strong></del></span> <span
class="inserted"><ins><em>GNU AGPL,
+use <a href="/licenses/agpl.txt">the text version of the GNU
AGPL</a>
+instead of the GNU GPL.</p>
+
+<p>If you are releasing your program under the Lesser
GPL,</em></ins></span> you should also
+include <a href="/licenses/lgpl.txt">the text version of the
LGPL</a>,
+usually in a file called COPYING.LESSER. Please note that, since the
+LGPL is a set of additional permissions on top of the GPL, it's <span
class="removed"><del><strong>important</strong></del></span> <span
class="inserted"><ins><em>crucial</em></ins></span>
+to include both licenses so users have all the materials they need to
+understand their rights.</p>
+
+<span class="removed"><del><strong><p>If you are releasing your program
under the GNU AGPL, you only need to
+include <a href="/licenses/agpl.txt">the text version of the GNU
+AGPL</a>.</p>
+
+<p>If you have copied code from other programs covered by the same
+license, copy their copyright notices too. Put all the copyright
+notices together, right near the top of each file.</p>
+
+<p>It is very important for practical reasons to include contact
+information for how to reach you, perhaps in the README file, but this
+has nothing to do with the legal issues of applying the license.</p>
+
+<p>The</strong></del></span>
+
+<span class="inserted"><ins><em><h3>The license notices</h3>
+
+<p>Each file's</em></ins></span> copying permission statement <span
class="inserted"><ins><em>(also called the license notice)</em></ins></span>
+should come right after <span
class="removed"><del><strong>the</strong></del></span> <span
class="inserted"><ins><em>its</em></ins></span> copyright notices. For a
one-file
+program, the statement (for the GPL) should look like <span
class="removed"><del><strong>this:</p></strong></del></span> <span
class="inserted"><ins><em>this, to use
+GPL version 3 or later:</p></em></ins></span>
+
+<pre>
+ 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 3 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, see <http://www.gnu.org/licenses/>.
+</pre>
+
+<p>For programs that are more than one file, it is better to replace
+“this program” with the name of the program, and begin the
+statement with a line saying “This file is part of NAME”.
+For instance,</p>
+
+<pre>
+ This file is part of Foobar.
+
+ Foobar 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 3 of the License, or
+ (at your option) any later version.
+
+ Foobar 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 <span class="removed"><del><strong>Foobar. If not, see
<http://www.gnu.org/licenses/>.
+</pre></strong></del></span> <span class="inserted"><ins><em>Foobar. If
not, see <http://www.gnu.org/licenses/>.
+</pre>
+
+<p>To use a different set of GPL versions, you would modify the end of
+the first long paragraph. For instance, to license under version 2 or
+later, you would replace “3” with
“2”.</p></em></ins></span>
+
+<p>This statement should go near the beginning of every source file,
+close to the copyright notices. When using the Lesser GPL, insert the
+word “Lesser” before “General” in <em>all
+three</em> places. When using the GNU AGPL, insert the
+word “Affero” before “General” in <em>all
+three</em> places.</p>
+
+<span class="inserted"><ins><em><h3>Why license notices?</h3>
+
+<p>The purpose of a free software license is to give certain rights to
+all users of a program. If it is not clear what rights you have given
+them, that defeats the purpose. Our practices are designed to
+avoid any uncertainty.</p>
+
+<p>If a program has a copy of a license FOO alongside the source files,
+but doesn't have an explicit statement that “This program is
+released under license FOO,” that leaves room for uncertainty
+about whether the license FOO applies to the code of that program.</p>
+
+<p>If a release has one statement that “This program is released
+under license FOO,” in a central place such as the README file,
+that makes the situation clear <em>for that release</em>. However,
+programmers often copy source files from one free program into
+another. If a source file contains no statement about what its
+license is, then moving it into another context eliminates all trace
+of that point. This invites confusion and error.</p>
+
+<h3>The startup notice</h3></em></ins></span>
+
+<p>For interactive programs, it is usually a good idea to make the
+program <span class="removed"><del><strong>print out</strong></del></span>
<span class="inserted"><ins><em>display</em></ins></span> a brief notice about
copyright and copying permission
+when it starts up. See <a href="/licenses/gpl-3.0.html#howto">the end
+of the GNU GPL</a> for more information about this.</p>
+
+<span class="inserted"><ins><em><h3>The Affero
notice</h3></em></ins></span>
+
+<p>If you are releasing your program under the GNU AGPL, and it can
+interact with users over a network, the program should offer its source to
+those users in some way. For example, if your program is a web
+application, its interface could display a “Source” link that
+leads users to an archive of the code. The GNU AGPL is flexible enough
+that you can choose a method that's suitable for your specific
+program—see section 13 for details.</p>
+
+<span class="inserted"><ins><em><h3>Miscellaneous</h3>
+
+<p>It is very important for practical reasons to include contact
+information for how to reach you, perhaps in the README file, but this
+has nothing to do with the legal issues of applying the
license.</p></em></ins></span>
+
+<p>There is no legal requirement to register your copyright with anyone;
+simply <span class="removed"><del><strong>distributing</strong></del></span>
<span class="inserted"><ins><em>writing</em></ins></span> the program makes it
copyrighted. However, <span class="inserted"><ins><em>for the
US,</em></ins></span>
+it is a
+<span class="removed"><del><strong>very</strong></del></span> good idea to
register the copyright with the US Registry of
+Copyrights, because that puts you in a stronger position against anyone
+who violates the license in the US. Most other countries have no system
+of copyright registration.</p>
+
+<span class="removed"><del><strong><p>It's wise to ask your employer or
school, if any, to sign a
+copyright disclaimer for the work, so they cannot claim to hold it
+later. Below is a sample copyright disclaimer; just alter the names
+and program description as appropriate:</p>
+
+<blockquote><p>Yoyodyne, Inc., hereby disclaims all copyright
interest
+in the program “Gnomovision” (which makes passes at
+compilers) written by James Hacker.</p>
+
+<p><signature of Moe Ghoul>, 1 April 1989<br />
+ Moe Ghoul, President of
Vice</p></blockquote></strong></del></span>
+
+<p>We would like to list all free software programs in the Free
+Software Directory, including all programs licensed under the GPL (any
+version). <span class="inserted"><ins><em>So please submit an entry for your
program, when it has
+reached the point of being useful.</em></ins></span> Please see
+the <a href="http://directory.fsf.org/">Directory web page</a> for
+information and an online submission form.</p>
+
+<p>It is also possible to make your program a GNU package, a part of the
+GNU Project. <span class="removed"><del><strong>(That's if we like the
program—we have to look at it
+first, and decide.)</strong></del></span> If you might be interested in
joining up with the
+GNU Project in this way, please see our <a
+href="/help/evaluation.html">GNU software evaluation page</a> for more
+information and a short <span
class="removed"><del><strong>questionnaire.</p>
+
+<p>But you</strong></del></span> <span
class="inserted"><ins><em>questionnaire. We will respond and discuss the
+matter with you.</p>
+
+<p>You</em></ins></span> are welcome to use any of our licenses even if
your program
+is not a GNU package; indeed, we hope you will. They're available to
+everyone. If you'd like to advertise your use of a particular license,
+feel free to use <a href="/graphics/license-logos.html"
+title="GNU License Logos">one of our logos</a>.</p>
+
+</div><!-- for id="content", starts in the include above -->
+<!--#include virtual="/server/footer.html" -->
+<div id="footer">
+<div class="unprintable">
+
+<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. Broken links and other corrections or suggestions can be sent
+to <a
href="mailto:address@hidden"><address@hidden></a>.</p>
+
+<p><!-- TRANSLATORS: Ignore the original text in this paragraph,
+ replace it with the translation of these two:
+
+ We work hard and do our best to provide accurate, good quality
+ translations. However, we are not exempt from imperfection.
+ Please send your comments and general suggestions in this regard
+ to <a href="mailto:address@hidden">
+ <address@hidden></a>.</p>
+
+ <p>For information on coordinating and submitting translations of
+ our web pages, see <a
+ href="/server/standards/README.translations.html">Translations
+ README</a>. -->
+Please see the <a
+href="/server/standards/README.translations.html">Translations
+README</a> for information on coordinating and submitting translations
+of this article.</p>
+</div>
+
+<!-- Regarding copyright, in general, standalone pages (as opposed to
+ files generated as part of manuals) on the GNU web server should
+ be under CC BY-ND <span class="removed"><del><strong>3.0
US.</strong></del></span> <span
class="inserted"><ins><em>4.0.</em></ins></span> 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. For web pages, it is ok to list just the latest year the
+ document was modified, or published.
+
+ If you wish to list earlier years, that is ok too.
+ Either "2001, 2002, 2003" or "2001-2003" are ok for specifying
+ years, as long as each year in the range is in fact a copyrightable
+ year, i.e., a year in which the document was published (including
+ being publicly visible on the web or in a revision control system).
+
+ There is more detail about copyright years in the GNU Maintainers
+ Information document, www.gnu.org/prep/maintain. -->
+
+<p>Copyright © 2001, 2007, 2008, 2009, 2013, <span
class="removed"><del><strong>2014</strong></del></span> <span
class="inserted"><ins><em>2014, 2017</em></ins></span>
+Free Software Foundation, Inc.</p>
+
+<p>This page is licensed under a <a rel="license"
+<span
class="removed"><del><strong>href="http://creativecommons.org/licenses/by-nd/3.0/us/">Creative</strong></del></span>
+<span
class="inserted"><ins><em>href="http://creativecommons.org/licenses/by-nd/4.0/">Creative</em></ins></span>
+Commons <span class="removed"><del><strong>Attribution-NoDerivs 3.0 United
States</strong></del></span> <span
class="inserted"><ins><em>Attribution-NoDerivatives 4.0
International</em></ins></span> License</a>.</p>
+
+<!--#include virtual="/server/bottom-notes.html" -->
+
+<p class="unprintable">Updated:
+<!-- timestamp start -->
+$Date: 2017/10/16 18:29:27 $
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>
+</pre></body></html>
Index: po/gpl-howto.it-diff.html
===================================================================
RCS file: po/gpl-howto.it-diff.html
diff -N po/gpl-howto.it-diff.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ po/gpl-howto.it-diff.html 16 Oct 2017 18:29:27 -0000 1.1
@@ -0,0 +1,365 @@
+<!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/gpl-howto.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" -->
+<!-- Parent-Version: <span
class="removed"><del><strong>1.77</strong></del></span> <span
class="inserted"><ins><em>1.84</em></ins></span> -->
+<title>How to use GNU licenses for your own software
+- GNU Project - Free Software Foundation</title>
+<!--#include virtual="/licenses/po/gpl-howto.translist" -->
+<!--#include virtual="/server/banner.html" -->
+<h2>How to use GNU licenses for your own software</h2>
+
+<p>This is a brief explanation of how to place a program under the <a
+href="/licenses/gpl.html">GNU General Public License</a>, <a
+<span
class="removed"><del><strong>href="/licenses/lgpl.html">Lesser</strong></del></span>
+<span class="inserted"><ins><em>href="/licenses/lgpl.html">GNU
Lesser</em></ins></span> General Public License</a>, or <a
+<span
class="removed"><del><strong>href="/licenses/agpl.html">Affero</strong></del></span>
+<span class="inserted"><ins><em>href="/licenses/agpl.html">GNU
Affero</em></ins></span> General Public License</a>. For the
+<a href="/licenses/fdl.html">GNU Free Documentation License</a>,
we have
+a <a href="/licenses/fdl-howto.html">separate page</a>.</p>
+
+<span class="removed"><del><strong><p>If you are looking for more
detailed</strong></del></span>
+
+<span class="inserted"><ins><em><p>For further</em></ins></span>
information, <span class="removed"><del><strong>consider
perusing</strong></del></span> <span
class="inserted"><ins><em>see</em></ins></span> our list
+of <a href="/licenses/gpl-faq.html">frequently asked questions about
+our licenses</a>.</p>
+
+<p>If you are considering using the GNU Lesser General Public License,
+please read the article “<a href="/licenses/why-not-lgpl.html">Why
+you shouldn't use the LGPL for your next library</a>” first. The
+article explains why it may be better to use the ordinary GPL instead,
+and how we would make the decision.</p>
+
+<span class="removed"><del><strong><p>Whichever
license</strong></del></span>
+
+<span class="inserted"><ins><em><p>Here's a brief summary of
what</em></ins></span> you <span
class="removed"><del><strong>plan</strong></del></span> <span
class="inserted"><ins><em>need</em></ins></span> to <span
class="removed"><del><strong>use,</strong></del></span> <span
class="inserted"><ins><em>do to release a program
+under one of our licenses:</p>
+
+<ul>
+<li>Get a copyright disclaimer from your employer or school.</li>
+<li>Give each file the proper copyright notices.</li>
+<li>Add a COPYING file with a copy of the GNU GPL or GNU AGPL.</li>
+<li>Also add a COPYING.LESSER file with a copy of</em></ins></span> the
<span class="removed"><del><strong>process</strong></del></span> <span
class="inserted"><ins><em>GNU LGPL, if you
+use that.</li>
+<li>Put a license notice in each file.</li>
+<li>(Optionally) make the program display a startup notice.</li>
+<li>(If using the AGPL) make the program offer copies of its source
code.</li>
+</ul>
+
+<p>This</em></ins></span> involves adding two elements to each source
file of your
+program: a copyright notice (such as “Copyright 1999 Terry
+Jones”), and a statement of copying permission, saying that the
+program is distributed under the terms of the GNU General Public
+License (or the Lesser <span class="inserted"><ins><em>GPL, or the
Affero</em></ins></span> GPL).</p>
+
+<span class="inserted"><ins><em><h3>The copyright disclaimer</h3>
+
+<p>To avoid possible legal complications later, it's wise to ask your
+employer or school, if any, to sign a copyright disclaimer for your
+program, so it cannot later claim that the copyright belongs to it
+and that you had no right to release the program at all. This really
+has nothing to do with the GNU GPL—it applies no matter which
+free software license you use to release the program.</p>
+
+<p>Here is a sample copyright disclaimer; just alter the names, title,
+and program description as appropriate:</p>
+
+<blockquote>
+<p>Yoyodyne, Inc., hereby disclaims all copyright interest
+in the program “Woodpecker” (which deconstructs trees)
+written by James Hacker.</p>
+
+<p><em>signature of Moe Ghoul</em> 1 April 1989<br />
+ Moe Ghoul, President of Vice</p>
+</blockquote>
+
+<p>If you are a university student, we recommend you request the
+disclaimer <a href="/philosophy/university.html"> at an early stage in
+writing the program</a> to reduce resistance. If you are not a
+research assistant or teaching assistant, it could be that the university
+has no claim to copyright on your work, but ask a lawyer to make
+sure of that.</p>
+
+<p>If you work, the best time to negotiate permission to release free
+software is <em>when negotiating your employment
agreement</em>.</p>
+
+<h3>The copyright notice</h3></em></ins></span>
+
+<p>The copyright notice should include the year in which you finished
+preparing the release (so if you finished it in 1998 but didn't post
+it until 1999, use 1998). You should add the proper year for each
+<span class="inserted"><ins><em>past</em></ins></span> release; for example,
“Copyright 1998, 1999 Terry
+Jones” if some
+<span class="removed"><del><strong>versions</strong></del></span> <span
class="inserted"><ins><em>releases</em></ins></span> were finished in 1998 and
some were
+finished in 1999. If several people helped write the code, use all
+their names.</p>
+
+<p>For software with several releases over multiple years, it's okay
+to use a range (“2008-2010”) instead of listing individual
+years (“2008, 2009, 2010”) if and only if every year in
+the range, inclusive, really is a “copyrightable” year
+that would be listed individually; <em>and</em> you make an
explicit
+statement in your documentation about this usage.</p>
+
+<p>Always use the English word “Copyright”; by international
+convention, this is used worldwide, even for material in other
+languages. The copyright symbol “©” can be included if
+you wish (and your character set supports it), but it's not necessary.
+There is no legal significance to using the three-character sequence
+“(C)”, <span
class="removed"><del><strong>although</strong></del></span> <span
class="inserted"><ins><em>but</em></ins></span> it does no harm.</p>
+
+<span class="inserted"><ins><em><p>If you have copied code from other
programs covered by the same
+license, copy their copyright notices too. Put all the copyright
+notices for a file together, right near the top of the file.</p>
+
+<h3>The license files</h3></em></ins></span>
+
+<p>You should also include a copy of the license itself somewhere in the
+distribution of your program. All programs, whether they are released
+under the GPL or LGPL, should include <a href="/licenses/gpl.txt">the
+text version of the GPL</a>. In GNU programs <span
class="inserted"><ins><em>we conventionally put</em></ins></span> the
+license <span class="removed"><del><strong>is usually</strong></del></span> in
a file called COPYING.</p>
+
+<p>If you are releasing your program under the <span
class="removed"><del><strong>LGPL,</strong></del></span> <span
class="inserted"><ins><em>GNU AGPL,
+use <a href="/licenses/agpl.txt">the text version of the GNU
AGPL</a>
+instead of the GNU GPL.</p>
+
+<p>If you are releasing your program under the Lesser
GPL,</em></ins></span> you should also
+include <a href="/licenses/lgpl.txt">the text version of the
LGPL</a>,
+usually in a file called COPYING.LESSER. Please note that, since the
+LGPL is a set of additional permissions on top of the GPL, it's <span
class="removed"><del><strong>important</strong></del></span> <span
class="inserted"><ins><em>crucial</em></ins></span>
+to include both licenses so users have all the materials they need to
+understand their rights.</p>
+
+<span class="removed"><del><strong><p>If you are releasing your program
under the GNU AGPL, you only need to
+include <a href="/licenses/agpl.txt">the text version of the GNU
+AGPL</a>.</p>
+
+<p>If you have copied code from other programs covered by the same
+license, copy their copyright notices too. Put all the copyright
+notices together, right near the top of each file.</p>
+
+<p>It is very important for practical reasons to include contact
+information for how to reach you, perhaps in the README file, but this
+has nothing to do with the legal issues of applying the license.</p>
+
+<p>The</strong></del></span>
+
+<span class="inserted"><ins><em><h3>The license notices</h3>
+
+<p>Each file's</em></ins></span> copying permission statement <span
class="inserted"><ins><em>(also called the license notice)</em></ins></span>
+should come right after <span
class="removed"><del><strong>the</strong></del></span> <span
class="inserted"><ins><em>its</em></ins></span> copyright notices. For a
one-file
+program, the statement (for the GPL) should look like <span
class="removed"><del><strong>this:</p></strong></del></span> <span
class="inserted"><ins><em>this, to use
+GPL version 3 or later:</p></em></ins></span>
+
+<pre>
+ 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 3 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, see <http://www.gnu.org/licenses/>.
+</pre>
+
+<p>For programs that are more than one file, it is better to replace
+“this program” with the name of the program, and begin the
+statement with a line saying “This file is part of NAME”.
+For instance,</p>
+
+<pre>
+ This file is part of Foobar.
+
+ Foobar 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 3 of the License, or
+ (at your option) any later version.
+
+ Foobar 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 <span class="removed"><del><strong>Foobar. If not, see
<http://www.gnu.org/licenses/>.
+</pre></strong></del></span> <span class="inserted"><ins><em>Foobar. If
not, see <http://www.gnu.org/licenses/>.
+</pre>
+
+<p>To use a different set of GPL versions, you would modify the end of
+the first long paragraph. For instance, to license under version 2 or
+later, you would replace “3” with
“2”.</p></em></ins></span>
+
+<p>This statement should go near the beginning of every source file,
+close to the copyright notices. When using the Lesser GPL, insert the
+word “Lesser” before “General” in <em>all
+three</em> places. When using the GNU AGPL, insert the
+word “Affero” before “General” in <em>all
+three</em> places.</p>
+
+<span class="inserted"><ins><em><h3>Why license notices?</h3>
+
+<p>The purpose of a free software license is to give certain rights to
+all users of a program. If it is not clear what rights you have given
+them, that defeats the purpose. Our practices are designed to
+avoid any uncertainty.</p>
+
+<p>If a program has a copy of a license FOO alongside the source files,
+but doesn't have an explicit statement that “This program is
+released under license FOO,” that leaves room for uncertainty
+about whether the license FOO applies to the code of that program.</p>
+
+<p>If a release has one statement that “This program is released
+under license FOO,” in a central place such as the README file,
+that makes the situation clear <em>for that release</em>. However,
+programmers often copy source files from one free program into
+another. If a source file contains no statement about what its
+license is, then moving it into another context eliminates all trace
+of that point. This invites confusion and error.</p>
+
+<h3>The startup notice</h3></em></ins></span>
+
+<p>For interactive programs, it is usually a good idea to make the
+program <span class="removed"><del><strong>print out</strong></del></span>
<span class="inserted"><ins><em>display</em></ins></span> a brief notice about
copyright and copying permission
+when it starts up. See <a href="/licenses/gpl-3.0.html#howto">the end
+of the GNU GPL</a> for more information about this.</p>
+
+<span class="inserted"><ins><em><h3>The Affero
notice</h3></em></ins></span>
+
+<p>If you are releasing your program under the GNU AGPL, and it can
+interact with users over a network, the program should offer its source to
+those users in some way. For example, if your program is a web
+application, its interface could display a “Source” link that
+leads users to an archive of the code. The GNU AGPL is flexible enough
+that you can choose a method that's suitable for your specific
+program—see section 13 for details.</p>
+
+<span class="inserted"><ins><em><h3>Miscellaneous</h3>
+
+<p>It is very important for practical reasons to include contact
+information for how to reach you, perhaps in the README file, but this
+has nothing to do with the legal issues of applying the
license.</p></em></ins></span>
+
+<p>There is no legal requirement to register your copyright with anyone;
+simply <span class="removed"><del><strong>distributing</strong></del></span>
<span class="inserted"><ins><em>writing</em></ins></span> the program makes it
copyrighted. However, <span class="inserted"><ins><em>for the
US,</em></ins></span>
+it is a
+<span class="removed"><del><strong>very</strong></del></span> good idea to
register the copyright with the US Registry of
+Copyrights, because that puts you in a stronger position against anyone
+who violates the license in the US. Most other countries have no system
+of copyright registration.</p>
+
+<span class="removed"><del><strong><p>It's wise to ask your employer or
school, if any, to sign a
+copyright disclaimer for the work, so they cannot claim to hold it
+later. Below is a sample copyright disclaimer; just alter the names
+and program description as appropriate:</p>
+
+<blockquote><p>Yoyodyne, Inc., hereby disclaims all copyright
interest
+in the program “Gnomovision” (which makes passes at
+compilers) written by James Hacker.</p>
+
+<p><signature of Moe Ghoul>, 1 April 1989<br />
+ Moe Ghoul, President of
Vice</p></blockquote></strong></del></span>
+
+<p>We would like to list all free software programs in the Free
+Software Directory, including all programs licensed under the GPL (any
+version). <span class="inserted"><ins><em>So please submit an entry for your
program, when it has
+reached the point of being useful.</em></ins></span> Please see
+the <a href="http://directory.fsf.org/">Directory web page</a> for
+information and an online submission form.</p>
+
+<p>It is also possible to make your program a GNU package, a part of the
+GNU Project. <span class="removed"><del><strong>(That's if we like the
program—we have to look at it
+first, and decide.)</strong></del></span> If you might be interested in
joining up with the
+GNU Project in this way, please see our <a
+href="/help/evaluation.html">GNU software evaluation page</a> for more
+information and a short <span
class="removed"><del><strong>questionnaire.</p>
+
+<p>But you</strong></del></span> <span
class="inserted"><ins><em>questionnaire. We will respond and discuss the
+matter with you.</p>
+
+<p>You</em></ins></span> are welcome to use any of our licenses even if
your program
+is not a GNU package; indeed, we hope you will. They're available to
+everyone. If you'd like to advertise your use of a particular license,
+feel free to use <a href="/graphics/license-logos.html"
+title="GNU License Logos">one of our logos</a>.</p>
+
+</div><!-- for id="content", starts in the include above -->
+<!--#include virtual="/server/footer.html" -->
+<div id="footer">
+<div class="unprintable">
+
+<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. Broken links and other corrections or suggestions can be sent
+to <a
href="mailto:address@hidden"><address@hidden></a>.</p>
+
+<p><!-- TRANSLATORS: Ignore the original text in this paragraph,
+ replace it with the translation of these two:
+
+ We work hard and do our best to provide accurate, good quality
+ translations. However, we are not exempt from imperfection.
+ Please send your comments and general suggestions in this regard
+ to <a href="mailto:address@hidden">
+ <address@hidden></a>.</p>
+
+ <p>For information on coordinating and submitting translations of
+ our web pages, see <a
+ href="/server/standards/README.translations.html">Translations
+ README</a>. -->
+Please see the <a
+href="/server/standards/README.translations.html">Translations
+README</a> for information on coordinating and submitting translations
+of this article.</p>
+</div>
+
+<!-- Regarding copyright, in general, standalone pages (as opposed to
+ files generated as part of manuals) on the GNU web server should
+ be under CC BY-ND <span class="removed"><del><strong>3.0
US.</strong></del></span> <span
class="inserted"><ins><em>4.0.</em></ins></span> 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. For web pages, it is ok to list just the latest year the
+ document was modified, or published.
+
+ If you wish to list earlier years, that is ok too.
+ Either "2001, 2002, 2003" or "2001-2003" are ok for specifying
+ years, as long as each year in the range is in fact a copyrightable
+ year, i.e., a year in which the document was published (including
+ being publicly visible on the web or in a revision control system).
+
+ There is more detail about copyright years in the GNU Maintainers
+ Information document, www.gnu.org/prep/maintain. -->
+
+<p>Copyright © 2001, 2007, 2008, 2009, 2013, <span
class="removed"><del><strong>2014</strong></del></span> <span
class="inserted"><ins><em>2014, 2017</em></ins></span>
+Free Software Foundation, Inc.</p>
+
+<p>This page is licensed under a <a rel="license"
+<span
class="removed"><del><strong>href="http://creativecommons.org/licenses/by-nd/3.0/us/">Creative</strong></del></span>
+<span
class="inserted"><ins><em>href="http://creativecommons.org/licenses/by-nd/4.0/">Creative</em></ins></span>
+Commons <span class="removed"><del><strong>Attribution-NoDerivs 3.0 United
States</strong></del></span> <span
class="inserted"><ins><em>Attribution-NoDerivatives 4.0
International</em></ins></span> License</a>.</p>
+
+<!--#include virtual="/server/bottom-notes.html" -->
+
+<p class="unprintable">Updated:
+<!-- timestamp start -->
+$Date: 2017/10/16 18:29:27 $
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>
+</pre></body></html>
Index: po/gpl-howto.ja-diff.html
===================================================================
RCS file: po/gpl-howto.ja-diff.html
diff -N po/gpl-howto.ja-diff.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ po/gpl-howto.ja-diff.html 16 Oct 2017 18:29:27 -0000 1.1
@@ -0,0 +1,365 @@
+<!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/gpl-howto.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" -->
+<!-- Parent-Version: <span
class="removed"><del><strong>1.77</strong></del></span> <span
class="inserted"><ins><em>1.84</em></ins></span> -->
+<title>How to use GNU licenses for your own software
+- GNU Project - Free Software Foundation</title>
+<!--#include virtual="/licenses/po/gpl-howto.translist" -->
+<!--#include virtual="/server/banner.html" -->
+<h2>How to use GNU licenses for your own software</h2>
+
+<p>This is a brief explanation of how to place a program under the <a
+href="/licenses/gpl.html">GNU General Public License</a>, <a
+<span
class="removed"><del><strong>href="/licenses/lgpl.html">Lesser</strong></del></span>
+<span class="inserted"><ins><em>href="/licenses/lgpl.html">GNU
Lesser</em></ins></span> General Public License</a>, or <a
+<span
class="removed"><del><strong>href="/licenses/agpl.html">Affero</strong></del></span>
+<span class="inserted"><ins><em>href="/licenses/agpl.html">GNU
Affero</em></ins></span> General Public License</a>. For the
+<a href="/licenses/fdl.html">GNU Free Documentation License</a>,
we have
+a <a href="/licenses/fdl-howto.html">separate page</a>.</p>
+
+<span class="removed"><del><strong><p>If you are looking for more
detailed</strong></del></span>
+
+<span class="inserted"><ins><em><p>For further</em></ins></span>
information, <span class="removed"><del><strong>consider
perusing</strong></del></span> <span
class="inserted"><ins><em>see</em></ins></span> our list
+of <a href="/licenses/gpl-faq.html">frequently asked questions about
+our licenses</a>.</p>
+
+<p>If you are considering using the GNU Lesser General Public License,
+please read the article “<a href="/licenses/why-not-lgpl.html">Why
+you shouldn't use the LGPL for your next library</a>” first. The
+article explains why it may be better to use the ordinary GPL instead,
+and how we would make the decision.</p>
+
+<span class="removed"><del><strong><p>Whichever
license</strong></del></span>
+
+<span class="inserted"><ins><em><p>Here's a brief summary of
what</em></ins></span> you <span
class="removed"><del><strong>plan</strong></del></span> <span
class="inserted"><ins><em>need</em></ins></span> to <span
class="removed"><del><strong>use,</strong></del></span> <span
class="inserted"><ins><em>do to release a program
+under one of our licenses:</p>
+
+<ul>
+<li>Get a copyright disclaimer from your employer or school.</li>
+<li>Give each file the proper copyright notices.</li>
+<li>Add a COPYING file with a copy of the GNU GPL or GNU AGPL.</li>
+<li>Also add a COPYING.LESSER file with a copy of</em></ins></span> the
<span class="removed"><del><strong>process</strong></del></span> <span
class="inserted"><ins><em>GNU LGPL, if you
+use that.</li>
+<li>Put a license notice in each file.</li>
+<li>(Optionally) make the program display a startup notice.</li>
+<li>(If using the AGPL) make the program offer copies of its source
code.</li>
+</ul>
+
+<p>This</em></ins></span> involves adding two elements to each source
file of your
+program: a copyright notice (such as “Copyright 1999 Terry
+Jones”), and a statement of copying permission, saying that the
+program is distributed under the terms of the GNU General Public
+License (or the Lesser <span class="inserted"><ins><em>GPL, or the
Affero</em></ins></span> GPL).</p>
+
+<span class="inserted"><ins><em><h3>The copyright disclaimer</h3>
+
+<p>To avoid possible legal complications later, it's wise to ask your
+employer or school, if any, to sign a copyright disclaimer for your
+program, so it cannot later claim that the copyright belongs to it
+and that you had no right to release the program at all. This really
+has nothing to do with the GNU GPL—it applies no matter which
+free software license you use to release the program.</p>
+
+<p>Here is a sample copyright disclaimer; just alter the names, title,
+and program description as appropriate:</p>
+
+<blockquote>
+<p>Yoyodyne, Inc., hereby disclaims all copyright interest
+in the program “Woodpecker” (which deconstructs trees)
+written by James Hacker.</p>
+
+<p><em>signature of Moe Ghoul</em> 1 April 1989<br />
+ Moe Ghoul, President of Vice</p>
+</blockquote>
+
+<p>If you are a university student, we recommend you request the
+disclaimer <a href="/philosophy/university.html"> at an early stage in
+writing the program</a> to reduce resistance. If you are not a
+research assistant or teaching assistant, it could be that the university
+has no claim to copyright on your work, but ask a lawyer to make
+sure of that.</p>
+
+<p>If you work, the best time to negotiate permission to release free
+software is <em>when negotiating your employment
agreement</em>.</p>
+
+<h3>The copyright notice</h3></em></ins></span>
+
+<p>The copyright notice should include the year in which you finished
+preparing the release (so if you finished it in 1998 but didn't post
+it until 1999, use 1998). You should add the proper year for each
+<span class="inserted"><ins><em>past</em></ins></span> release; for example,
“Copyright 1998, 1999 Terry
+Jones” if some
+<span class="removed"><del><strong>versions</strong></del></span> <span
class="inserted"><ins><em>releases</em></ins></span> were finished in 1998 and
some were
+finished in 1999. If several people helped write the code, use all
+their names.</p>
+
+<p>For software with several releases over multiple years, it's okay
+to use a range (“2008-2010”) instead of listing individual
+years (“2008, 2009, 2010”) if and only if every year in
+the range, inclusive, really is a “copyrightable” year
+that would be listed individually; <em>and</em> you make an
explicit
+statement in your documentation about this usage.</p>
+
+<p>Always use the English word “Copyright”; by international
+convention, this is used worldwide, even for material in other
+languages. The copyright symbol “©” can be included if
+you wish (and your character set supports it), but it's not necessary.
+There is no legal significance to using the three-character sequence
+“(C)”, <span
class="removed"><del><strong>although</strong></del></span> <span
class="inserted"><ins><em>but</em></ins></span> it does no harm.</p>
+
+<span class="inserted"><ins><em><p>If you have copied code from other
programs covered by the same
+license, copy their copyright notices too. Put all the copyright
+notices for a file together, right near the top of the file.</p>
+
+<h3>The license files</h3></em></ins></span>
+
+<p>You should also include a copy of the license itself somewhere in the
+distribution of your program. All programs, whether they are released
+under the GPL or LGPL, should include <a href="/licenses/gpl.txt">the
+text version of the GPL</a>. In GNU programs <span
class="inserted"><ins><em>we conventionally put</em></ins></span> the
+license <span class="removed"><del><strong>is usually</strong></del></span> in
a file called COPYING.</p>
+
+<p>If you are releasing your program under the <span
class="removed"><del><strong>LGPL,</strong></del></span> <span
class="inserted"><ins><em>GNU AGPL,
+use <a href="/licenses/agpl.txt">the text version of the GNU
AGPL</a>
+instead of the GNU GPL.</p>
+
+<p>If you are releasing your program under the Lesser
GPL,</em></ins></span> you should also
+include <a href="/licenses/lgpl.txt">the text version of the
LGPL</a>,
+usually in a file called COPYING.LESSER. Please note that, since the
+LGPL is a set of additional permissions on top of the GPL, it's <span
class="removed"><del><strong>important</strong></del></span> <span
class="inserted"><ins><em>crucial</em></ins></span>
+to include both licenses so users have all the materials they need to
+understand their rights.</p>
+
+<span class="removed"><del><strong><p>If you are releasing your program
under the GNU AGPL, you only need to
+include <a href="/licenses/agpl.txt">the text version of the GNU
+AGPL</a>.</p>
+
+<p>If you have copied code from other programs covered by the same
+license, copy their copyright notices too. Put all the copyright
+notices together, right near the top of each file.</p>
+
+<p>It is very important for practical reasons to include contact
+information for how to reach you, perhaps in the README file, but this
+has nothing to do with the legal issues of applying the license.</p>
+
+<p>The</strong></del></span>
+
+<span class="inserted"><ins><em><h3>The license notices</h3>
+
+<p>Each file's</em></ins></span> copying permission statement <span
class="inserted"><ins><em>(also called the license notice)</em></ins></span>
+should come right after <span
class="removed"><del><strong>the</strong></del></span> <span
class="inserted"><ins><em>its</em></ins></span> copyright notices. For a
one-file
+program, the statement (for the GPL) should look like <span
class="removed"><del><strong>this:</p></strong></del></span> <span
class="inserted"><ins><em>this, to use
+GPL version 3 or later:</p></em></ins></span>
+
+<pre>
+ 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 3 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, see <http://www.gnu.org/licenses/>.
+</pre>
+
+<p>For programs that are more than one file, it is better to replace
+“this program” with the name of the program, and begin the
+statement with a line saying “This file is part of NAME”.
+For instance,</p>
+
+<pre>
+ This file is part of Foobar.
+
+ Foobar 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 3 of the License, or
+ (at your option) any later version.
+
+ Foobar 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 <span class="removed"><del><strong>Foobar. If not, see
<http://www.gnu.org/licenses/>.
+</pre></strong></del></span> <span class="inserted"><ins><em>Foobar. If
not, see <http://www.gnu.org/licenses/>.
+</pre>
+
+<p>To use a different set of GPL versions, you would modify the end of
+the first long paragraph. For instance, to license under version 2 or
+later, you would replace “3” with
“2”.</p></em></ins></span>
+
+<p>This statement should go near the beginning of every source file,
+close to the copyright notices. When using the Lesser GPL, insert the
+word “Lesser” before “General” in <em>all
+three</em> places. When using the GNU AGPL, insert the
+word “Affero” before “General” in <em>all
+three</em> places.</p>
+
+<span class="inserted"><ins><em><h3>Why license notices?</h3>
+
+<p>The purpose of a free software license is to give certain rights to
+all users of a program. If it is not clear what rights you have given
+them, that defeats the purpose. Our practices are designed to
+avoid any uncertainty.</p>
+
+<p>If a program has a copy of a license FOO alongside the source files,
+but doesn't have an explicit statement that “This program is
+released under license FOO,” that leaves room for uncertainty
+about whether the license FOO applies to the code of that program.</p>
+
+<p>If a release has one statement that “This program is released
+under license FOO,” in a central place such as the README file,
+that makes the situation clear <em>for that release</em>. However,
+programmers often copy source files from one free program into
+another. If a source file contains no statement about what its
+license is, then moving it into another context eliminates all trace
+of that point. This invites confusion and error.</p>
+
+<h3>The startup notice</h3></em></ins></span>
+
+<p>For interactive programs, it is usually a good idea to make the
+program <span class="removed"><del><strong>print out</strong></del></span>
<span class="inserted"><ins><em>display</em></ins></span> a brief notice about
copyright and copying permission
+when it starts up. See <a href="/licenses/gpl-3.0.html#howto">the end
+of the GNU GPL</a> for more information about this.</p>
+
+<span class="inserted"><ins><em><h3>The Affero
notice</h3></em></ins></span>
+
+<p>If you are releasing your program under the GNU AGPL, and it can
+interact with users over a network, the program should offer its source to
+those users in some way. For example, if your program is a web
+application, its interface could display a “Source” link that
+leads users to an archive of the code. The GNU AGPL is flexible enough
+that you can choose a method that's suitable for your specific
+program—see section 13 for details.</p>
+
+<span class="inserted"><ins><em><h3>Miscellaneous</h3>
+
+<p>It is very important for practical reasons to include contact
+information for how to reach you, perhaps in the README file, but this
+has nothing to do with the legal issues of applying the
license.</p></em></ins></span>
+
+<p>There is no legal requirement to register your copyright with anyone;
+simply <span class="removed"><del><strong>distributing</strong></del></span>
<span class="inserted"><ins><em>writing</em></ins></span> the program makes it
copyrighted. However, <span class="inserted"><ins><em>for the
US,</em></ins></span>
+it is a
+<span class="removed"><del><strong>very</strong></del></span> good idea to
register the copyright with the US Registry of
+Copyrights, because that puts you in a stronger position against anyone
+who violates the license in the US. Most other countries have no system
+of copyright registration.</p>
+
+<span class="removed"><del><strong><p>It's wise to ask your employer or
school, if any, to sign a
+copyright disclaimer for the work, so they cannot claim to hold it
+later. Below is a sample copyright disclaimer; just alter the names
+and program description as appropriate:</p>
+
+<blockquote><p>Yoyodyne, Inc., hereby disclaims all copyright
interest
+in the program “Gnomovision” (which makes passes at
+compilers) written by James Hacker.</p>
+
+<p><signature of Moe Ghoul>, 1 April 1989<br />
+ Moe Ghoul, President of
Vice</p></blockquote></strong></del></span>
+
+<p>We would like to list all free software programs in the Free
+Software Directory, including all programs licensed under the GPL (any
+version). <span class="inserted"><ins><em>So please submit an entry for your
program, when it has
+reached the point of being useful.</em></ins></span> Please see
+the <a href="http://directory.fsf.org/">Directory web page</a> for
+information and an online submission form.</p>
+
+<p>It is also possible to make your program a GNU package, a part of the
+GNU Project. <span class="removed"><del><strong>(That's if we like the
program—we have to look at it
+first, and decide.)</strong></del></span> If you might be interested in
joining up with the
+GNU Project in this way, please see our <a
+href="/help/evaluation.html">GNU software evaluation page</a> for more
+information and a short <span
class="removed"><del><strong>questionnaire.</p>
+
+<p>But you</strong></del></span> <span
class="inserted"><ins><em>questionnaire. We will respond and discuss the
+matter with you.</p>
+
+<p>You</em></ins></span> are welcome to use any of our licenses even if
your program
+is not a GNU package; indeed, we hope you will. They're available to
+everyone. If you'd like to advertise your use of a particular license,
+feel free to use <a href="/graphics/license-logos.html"
+title="GNU License Logos">one of our logos</a>.</p>
+
+</div><!-- for id="content", starts in the include above -->
+<!--#include virtual="/server/footer.html" -->
+<div id="footer">
+<div class="unprintable">
+
+<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. Broken links and other corrections or suggestions can be sent
+to <a
href="mailto:address@hidden"><address@hidden></a>.</p>
+
+<p><!-- TRANSLATORS: Ignore the original text in this paragraph,
+ replace it with the translation of these two:
+
+ We work hard and do our best to provide accurate, good quality
+ translations. However, we are not exempt from imperfection.
+ Please send your comments and general suggestions in this regard
+ to <a href="mailto:address@hidden">
+ <address@hidden></a>.</p>
+
+ <p>For information on coordinating and submitting translations of
+ our web pages, see <a
+ href="/server/standards/README.translations.html">Translations
+ README</a>. -->
+Please see the <a
+href="/server/standards/README.translations.html">Translations
+README</a> for information on coordinating and submitting translations
+of this article.</p>
+</div>
+
+<!-- Regarding copyright, in general, standalone pages (as opposed to
+ files generated as part of manuals) on the GNU web server should
+ be under CC BY-ND <span class="removed"><del><strong>3.0
US.</strong></del></span> <span
class="inserted"><ins><em>4.0.</em></ins></span> 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. For web pages, it is ok to list just the latest year the
+ document was modified, or published.
+
+ If you wish to list earlier years, that is ok too.
+ Either "2001, 2002, 2003" or "2001-2003" are ok for specifying
+ years, as long as each year in the range is in fact a copyrightable
+ year, i.e., a year in which the document was published (including
+ being publicly visible on the web or in a revision control system).
+
+ There is more detail about copyright years in the GNU Maintainers
+ Information document, www.gnu.org/prep/maintain. -->
+
+<p>Copyright © 2001, 2007, 2008, 2009, 2013, <span
class="removed"><del><strong>2014</strong></del></span> <span
class="inserted"><ins><em>2014, 2017</em></ins></span>
+Free Software Foundation, Inc.</p>
+
+<p>This page is licensed under a <a rel="license"
+<span
class="removed"><del><strong>href="http://creativecommons.org/licenses/by-nd/3.0/us/">Creative</strong></del></span>
+<span
class="inserted"><ins><em>href="http://creativecommons.org/licenses/by-nd/4.0/">Creative</em></ins></span>
+Commons <span class="removed"><del><strong>Attribution-NoDerivs 3.0 United
States</strong></del></span> <span
class="inserted"><ins><em>Attribution-NoDerivatives 4.0
International</em></ins></span> License</a>.</p>
+
+<!--#include virtual="/server/bottom-notes.html" -->
+
+<p class="unprintable">Updated:
+<!-- timestamp start -->
+$Date: 2017/10/16 18:29:27 $
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>
+</pre></body></html>
Index: po/gpl-howto.pl-diff.html
===================================================================
RCS file: po/gpl-howto.pl-diff.html
diff -N po/gpl-howto.pl-diff.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ po/gpl-howto.pl-diff.html 16 Oct 2017 18:29:27 -0000 1.1
@@ -0,0 +1,365 @@
+<!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/gpl-howto.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" -->
+<!-- Parent-Version: <span
class="removed"><del><strong>1.77</strong></del></span> <span
class="inserted"><ins><em>1.84</em></ins></span> -->
+<title>How to use GNU licenses for your own software
+- GNU Project - Free Software Foundation</title>
+<!--#include virtual="/licenses/po/gpl-howto.translist" -->
+<!--#include virtual="/server/banner.html" -->
+<h2>How to use GNU licenses for your own software</h2>
+
+<p>This is a brief explanation of how to place a program under the <a
+href="/licenses/gpl.html">GNU General Public License</a>, <a
+<span
class="removed"><del><strong>href="/licenses/lgpl.html">Lesser</strong></del></span>
+<span class="inserted"><ins><em>href="/licenses/lgpl.html">GNU
Lesser</em></ins></span> General Public License</a>, or <a
+<span
class="removed"><del><strong>href="/licenses/agpl.html">Affero</strong></del></span>
+<span class="inserted"><ins><em>href="/licenses/agpl.html">GNU
Affero</em></ins></span> General Public License</a>. For the
+<a href="/licenses/fdl.html">GNU Free Documentation License</a>,
we have
+a <a href="/licenses/fdl-howto.html">separate page</a>.</p>
+
+<span class="removed"><del><strong><p>If you are looking for more
detailed</strong></del></span>
+
+<span class="inserted"><ins><em><p>For further</em></ins></span>
information, <span class="removed"><del><strong>consider
perusing</strong></del></span> <span
class="inserted"><ins><em>see</em></ins></span> our list
+of <a href="/licenses/gpl-faq.html">frequently asked questions about
+our licenses</a>.</p>
+
+<p>If you are considering using the GNU Lesser General Public License,
+please read the article “<a href="/licenses/why-not-lgpl.html">Why
+you shouldn't use the LGPL for your next library</a>” first. The
+article explains why it may be better to use the ordinary GPL instead,
+and how we would make the decision.</p>
+
+<span class="removed"><del><strong><p>Whichever
license</strong></del></span>
+
+<span class="inserted"><ins><em><p>Here's a brief summary of
what</em></ins></span> you <span
class="removed"><del><strong>plan</strong></del></span> <span
class="inserted"><ins><em>need</em></ins></span> to <span
class="removed"><del><strong>use,</strong></del></span> <span
class="inserted"><ins><em>do to release a program
+under one of our licenses:</p>
+
+<ul>
+<li>Get a copyright disclaimer from your employer or school.</li>
+<li>Give each file the proper copyright notices.</li>
+<li>Add a COPYING file with a copy of the GNU GPL or GNU AGPL.</li>
+<li>Also add a COPYING.LESSER file with a copy of</em></ins></span> the
<span class="removed"><del><strong>process</strong></del></span> <span
class="inserted"><ins><em>GNU LGPL, if you
+use that.</li>
+<li>Put a license notice in each file.</li>
+<li>(Optionally) make the program display a startup notice.</li>
+<li>(If using the AGPL) make the program offer copies of its source
code.</li>
+</ul>
+
+<p>This</em></ins></span> involves adding two elements to each source
file of your
+program: a copyright notice (such as “Copyright 1999 Terry
+Jones”), and a statement of copying permission, saying that the
+program is distributed under the terms of the GNU General Public
+License (or the Lesser <span class="inserted"><ins><em>GPL, or the
Affero</em></ins></span> GPL).</p>
+
+<span class="inserted"><ins><em><h3>The copyright disclaimer</h3>
+
+<p>To avoid possible legal complications later, it's wise to ask your
+employer or school, if any, to sign a copyright disclaimer for your
+program, so it cannot later claim that the copyright belongs to it
+and that you had no right to release the program at all. This really
+has nothing to do with the GNU GPL—it applies no matter which
+free software license you use to release the program.</p>
+
+<p>Here is a sample copyright disclaimer; just alter the names, title,
+and program description as appropriate:</p>
+
+<blockquote>
+<p>Yoyodyne, Inc., hereby disclaims all copyright interest
+in the program “Woodpecker” (which deconstructs trees)
+written by James Hacker.</p>
+
+<p><em>signature of Moe Ghoul</em> 1 April 1989<br />
+ Moe Ghoul, President of Vice</p>
+</blockquote>
+
+<p>If you are a university student, we recommend you request the
+disclaimer <a href="/philosophy/university.html"> at an early stage in
+writing the program</a> to reduce resistance. If you are not a
+research assistant or teaching assistant, it could be that the university
+has no claim to copyright on your work, but ask a lawyer to make
+sure of that.</p>
+
+<p>If you work, the best time to negotiate permission to release free
+software is <em>when negotiating your employment
agreement</em>.</p>
+
+<h3>The copyright notice</h3></em></ins></span>
+
+<p>The copyright notice should include the year in which you finished
+preparing the release (so if you finished it in 1998 but didn't post
+it until 1999, use 1998). You should add the proper year for each
+<span class="inserted"><ins><em>past</em></ins></span> release; for example,
“Copyright 1998, 1999 Terry
+Jones” if some
+<span class="removed"><del><strong>versions</strong></del></span> <span
class="inserted"><ins><em>releases</em></ins></span> were finished in 1998 and
some were
+finished in 1999. If several people helped write the code, use all
+their names.</p>
+
+<p>For software with several releases over multiple years, it's okay
+to use a range (“2008-2010”) instead of listing individual
+years (“2008, 2009, 2010”) if and only if every year in
+the range, inclusive, really is a “copyrightable” year
+that would be listed individually; <em>and</em> you make an
explicit
+statement in your documentation about this usage.</p>
+
+<p>Always use the English word “Copyright”; by international
+convention, this is used worldwide, even for material in other
+languages. The copyright symbol “©” can be included if
+you wish (and your character set supports it), but it's not necessary.
+There is no legal significance to using the three-character sequence
+“(C)”, <span
class="removed"><del><strong>although</strong></del></span> <span
class="inserted"><ins><em>but</em></ins></span> it does no harm.</p>
+
+<span class="inserted"><ins><em><p>If you have copied code from other
programs covered by the same
+license, copy their copyright notices too. Put all the copyright
+notices for a file together, right near the top of the file.</p>
+
+<h3>The license files</h3></em></ins></span>
+
+<p>You should also include a copy of the license itself somewhere in the
+distribution of your program. All programs, whether they are released
+under the GPL or LGPL, should include <a href="/licenses/gpl.txt">the
+text version of the GPL</a>. In GNU programs <span
class="inserted"><ins><em>we conventionally put</em></ins></span> the
+license <span class="removed"><del><strong>is usually</strong></del></span> in
a file called COPYING.</p>
+
+<p>If you are releasing your program under the <span
class="removed"><del><strong>LGPL,</strong></del></span> <span
class="inserted"><ins><em>GNU AGPL,
+use <a href="/licenses/agpl.txt">the text version of the GNU
AGPL</a>
+instead of the GNU GPL.</p>
+
+<p>If you are releasing your program under the Lesser
GPL,</em></ins></span> you should also
+include <a href="/licenses/lgpl.txt">the text version of the
LGPL</a>,
+usually in a file called COPYING.LESSER. Please note that, since the
+LGPL is a set of additional permissions on top of the GPL, it's <span
class="removed"><del><strong>important</strong></del></span> <span
class="inserted"><ins><em>crucial</em></ins></span>
+to include both licenses so users have all the materials they need to
+understand their rights.</p>
+
+<span class="removed"><del><strong><p>If you are releasing your program
under the GNU AGPL, you only need to
+include <a href="/licenses/agpl.txt">the text version of the GNU
+AGPL</a>.</p>
+
+<p>If you have copied code from other programs covered by the same
+license, copy their copyright notices too. Put all the copyright
+notices together, right near the top of each file.</p>
+
+<p>It is very important for practical reasons to include contact
+information for how to reach you, perhaps in the README file, but this
+has nothing to do with the legal issues of applying the license.</p>
+
+<p>The</strong></del></span>
+
+<span class="inserted"><ins><em><h3>The license notices</h3>
+
+<p>Each file's</em></ins></span> copying permission statement <span
class="inserted"><ins><em>(also called the license notice)</em></ins></span>
+should come right after <span
class="removed"><del><strong>the</strong></del></span> <span
class="inserted"><ins><em>its</em></ins></span> copyright notices. For a
one-file
+program, the statement (for the GPL) should look like <span
class="removed"><del><strong>this:</p></strong></del></span> <span
class="inserted"><ins><em>this, to use
+GPL version 3 or later:</p></em></ins></span>
+
+<pre>
+ 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 3 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, see <http://www.gnu.org/licenses/>.
+</pre>
+
+<p>For programs that are more than one file, it is better to replace
+“this program” with the name of the program, and begin the
+statement with a line saying “This file is part of NAME”.
+For instance,</p>
+
+<pre>
+ This file is part of Foobar.
+
+ Foobar 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 3 of the License, or
+ (at your option) any later version.
+
+ Foobar 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 <span class="removed"><del><strong>Foobar. If not, see
<http://www.gnu.org/licenses/>.
+</pre></strong></del></span> <span class="inserted"><ins><em>Foobar. If
not, see <http://www.gnu.org/licenses/>.
+</pre>
+
+<p>To use a different set of GPL versions, you would modify the end of
+the first long paragraph. For instance, to license under version 2 or
+later, you would replace “3” with
“2”.</p></em></ins></span>
+
+<p>This statement should go near the beginning of every source file,
+close to the copyright notices. When using the Lesser GPL, insert the
+word “Lesser” before “General” in <em>all
+three</em> places. When using the GNU AGPL, insert the
+word “Affero” before “General” in <em>all
+three</em> places.</p>
+
+<span class="inserted"><ins><em><h3>Why license notices?</h3>
+
+<p>The purpose of a free software license is to give certain rights to
+all users of a program. If it is not clear what rights you have given
+them, that defeats the purpose. Our practices are designed to
+avoid any uncertainty.</p>
+
+<p>If a program has a copy of a license FOO alongside the source files,
+but doesn't have an explicit statement that “This program is
+released under license FOO,” that leaves room for uncertainty
+about whether the license FOO applies to the code of that program.</p>
+
+<p>If a release has one statement that “This program is released
+under license FOO,” in a central place such as the README file,
+that makes the situation clear <em>for that release</em>. However,
+programmers often copy source files from one free program into
+another. If a source file contains no statement about what its
+license is, then moving it into another context eliminates all trace
+of that point. This invites confusion and error.</p>
+
+<h3>The startup notice</h3></em></ins></span>
+
+<p>For interactive programs, it is usually a good idea to make the
+program <span class="removed"><del><strong>print out</strong></del></span>
<span class="inserted"><ins><em>display</em></ins></span> a brief notice about
copyright and copying permission
+when it starts up. See <a href="/licenses/gpl-3.0.html#howto">the end
+of the GNU GPL</a> for more information about this.</p>
+
+<span class="inserted"><ins><em><h3>The Affero
notice</h3></em></ins></span>
+
+<p>If you are releasing your program under the GNU AGPL, and it can
+interact with users over a network, the program should offer its source to
+those users in some way. For example, if your program is a web
+application, its interface could display a “Source” link that
+leads users to an archive of the code. The GNU AGPL is flexible enough
+that you can choose a method that's suitable for your specific
+program—see section 13 for details.</p>
+
+<span class="inserted"><ins><em><h3>Miscellaneous</h3>
+
+<p>It is very important for practical reasons to include contact
+information for how to reach you, perhaps in the README file, but this
+has nothing to do with the legal issues of applying the
license.</p></em></ins></span>
+
+<p>There is no legal requirement to register your copyright with anyone;
+simply <span class="removed"><del><strong>distributing</strong></del></span>
<span class="inserted"><ins><em>writing</em></ins></span> the program makes it
copyrighted. However, <span class="inserted"><ins><em>for the
US,</em></ins></span>
+it is a
+<span class="removed"><del><strong>very</strong></del></span> good idea to
register the copyright with the US Registry of
+Copyrights, because that puts you in a stronger position against anyone
+who violates the license in the US. Most other countries have no system
+of copyright registration.</p>
+
+<span class="removed"><del><strong><p>It's wise to ask your employer or
school, if any, to sign a
+copyright disclaimer for the work, so they cannot claim to hold it
+later. Below is a sample copyright disclaimer; just alter the names
+and program description as appropriate:</p>
+
+<blockquote><p>Yoyodyne, Inc., hereby disclaims all copyright
interest
+in the program “Gnomovision” (which makes passes at
+compilers) written by James Hacker.</p>
+
+<p><signature of Moe Ghoul>, 1 April 1989<br />
+ Moe Ghoul, President of
Vice</p></blockquote></strong></del></span>
+
+<p>We would like to list all free software programs in the Free
+Software Directory, including all programs licensed under the GPL (any
+version). <span class="inserted"><ins><em>So please submit an entry for your
program, when it has
+reached the point of being useful.</em></ins></span> Please see
+the <a href="http://directory.fsf.org/">Directory web page</a> for
+information and an online submission form.</p>
+
+<p>It is also possible to make your program a GNU package, a part of the
+GNU Project. <span class="removed"><del><strong>(That's if we like the
program—we have to look at it
+first, and decide.)</strong></del></span> If you might be interested in
joining up with the
+GNU Project in this way, please see our <a
+href="/help/evaluation.html">GNU software evaluation page</a> for more
+information and a short <span
class="removed"><del><strong>questionnaire.</p>
+
+<p>But you</strong></del></span> <span
class="inserted"><ins><em>questionnaire. We will respond and discuss the
+matter with you.</p>
+
+<p>You</em></ins></span> are welcome to use any of our licenses even if
your program
+is not a GNU package; indeed, we hope you will. They're available to
+everyone. If you'd like to advertise your use of a particular license,
+feel free to use <a href="/graphics/license-logos.html"
+title="GNU License Logos">one of our logos</a>.</p>
+
+</div><!-- for id="content", starts in the include above -->
+<!--#include virtual="/server/footer.html" -->
+<div id="footer">
+<div class="unprintable">
+
+<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. Broken links and other corrections or suggestions can be sent
+to <a
href="mailto:address@hidden"><address@hidden></a>.</p>
+
+<p><!-- TRANSLATORS: Ignore the original text in this paragraph,
+ replace it with the translation of these two:
+
+ We work hard and do our best to provide accurate, good quality
+ translations. However, we are not exempt from imperfection.
+ Please send your comments and general suggestions in this regard
+ to <a href="mailto:address@hidden">
+ <address@hidden></a>.</p>
+
+ <p>For information on coordinating and submitting translations of
+ our web pages, see <a
+ href="/server/standards/README.translations.html">Translations
+ README</a>. -->
+Please see the <a
+href="/server/standards/README.translations.html">Translations
+README</a> for information on coordinating and submitting translations
+of this article.</p>
+</div>
+
+<!-- Regarding copyright, in general, standalone pages (as opposed to
+ files generated as part of manuals) on the GNU web server should
+ be under CC BY-ND <span class="removed"><del><strong>3.0
US.</strong></del></span> <span
class="inserted"><ins><em>4.0.</em></ins></span> 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. For web pages, it is ok to list just the latest year the
+ document was modified, or published.
+
+ If you wish to list earlier years, that is ok too.
+ Either "2001, 2002, 2003" or "2001-2003" are ok for specifying
+ years, as long as each year in the range is in fact a copyrightable
+ year, i.e., a year in which the document was published (including
+ being publicly visible on the web or in a revision control system).
+
+ There is more detail about copyright years in the GNU Maintainers
+ Information document, www.gnu.org/prep/maintain. -->
+
+<p>Copyright © 2001, 2007, 2008, 2009, 2013, <span
class="removed"><del><strong>2014</strong></del></span> <span
class="inserted"><ins><em>2014, 2017</em></ins></span>
+Free Software Foundation, Inc.</p>
+
+<p>This page is licensed under a <a rel="license"
+<span
class="removed"><del><strong>href="http://creativecommons.org/licenses/by-nd/3.0/us/">Creative</strong></del></span>
+<span
class="inserted"><ins><em>href="http://creativecommons.org/licenses/by-nd/4.0/">Creative</em></ins></span>
+Commons <span class="removed"><del><strong>Attribution-NoDerivs 3.0 United
States</strong></del></span> <span
class="inserted"><ins><em>Attribution-NoDerivatives 4.0
International</em></ins></span> License</a>.</p>
+
+<!--#include virtual="/server/bottom-notes.html" -->
+
+<p class="unprintable">Updated:
+<!-- timestamp start -->
+$Date: 2017/10/16 18:29:27 $
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>
+</pre></body></html>
Index: po/gpl-howto.pt-br-diff.html
===================================================================
RCS file: po/gpl-howto.pt-br-diff.html
diff -N po/gpl-howto.pt-br-diff.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ po/gpl-howto.pt-br-diff.html 16 Oct 2017 18:29:27 -0000 1.1
@@ -0,0 +1,365 @@
+<!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/gpl-howto.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" -->
+<!-- Parent-Version: <span
class="removed"><del><strong>1.77</strong></del></span> <span
class="inserted"><ins><em>1.84</em></ins></span> -->
+<title>How to use GNU licenses for your own software
+- GNU Project - Free Software Foundation</title>
+<!--#include virtual="/licenses/po/gpl-howto.translist" -->
+<!--#include virtual="/server/banner.html" -->
+<h2>How to use GNU licenses for your own software</h2>
+
+<p>This is a brief explanation of how to place a program under the <a
+href="/licenses/gpl.html">GNU General Public License</a>, <a
+<span
class="removed"><del><strong>href="/licenses/lgpl.html">Lesser</strong></del></span>
+<span class="inserted"><ins><em>href="/licenses/lgpl.html">GNU
Lesser</em></ins></span> General Public License</a>, or <a
+<span
class="removed"><del><strong>href="/licenses/agpl.html">Affero</strong></del></span>
+<span class="inserted"><ins><em>href="/licenses/agpl.html">GNU
Affero</em></ins></span> General Public License</a>. For the
+<a href="/licenses/fdl.html">GNU Free Documentation License</a>,
we have
+a <a href="/licenses/fdl-howto.html">separate page</a>.</p>
+
+<span class="removed"><del><strong><p>If you are looking for more
detailed</strong></del></span>
+
+<span class="inserted"><ins><em><p>For further</em></ins></span>
information, <span class="removed"><del><strong>consider
perusing</strong></del></span> <span
class="inserted"><ins><em>see</em></ins></span> our list
+of <a href="/licenses/gpl-faq.html">frequently asked questions about
+our licenses</a>.</p>
+
+<p>If you are considering using the GNU Lesser General Public License,
+please read the article “<a href="/licenses/why-not-lgpl.html">Why
+you shouldn't use the LGPL for your next library</a>” first. The
+article explains why it may be better to use the ordinary GPL instead,
+and how we would make the decision.</p>
+
+<span class="removed"><del><strong><p>Whichever
license</strong></del></span>
+
+<span class="inserted"><ins><em><p>Here's a brief summary of
what</em></ins></span> you <span
class="removed"><del><strong>plan</strong></del></span> <span
class="inserted"><ins><em>need</em></ins></span> to <span
class="removed"><del><strong>use,</strong></del></span> <span
class="inserted"><ins><em>do to release a program
+under one of our licenses:</p>
+
+<ul>
+<li>Get a copyright disclaimer from your employer or school.</li>
+<li>Give each file the proper copyright notices.</li>
+<li>Add a COPYING file with a copy of the GNU GPL or GNU AGPL.</li>
+<li>Also add a COPYING.LESSER file with a copy of</em></ins></span> the
<span class="removed"><del><strong>process</strong></del></span> <span
class="inserted"><ins><em>GNU LGPL, if you
+use that.</li>
+<li>Put a license notice in each file.</li>
+<li>(Optionally) make the program display a startup notice.</li>
+<li>(If using the AGPL) make the program offer copies of its source
code.</li>
+</ul>
+
+<p>This</em></ins></span> involves adding two elements to each source
file of your
+program: a copyright notice (such as “Copyright 1999 Terry
+Jones”), and a statement of copying permission, saying that the
+program is distributed under the terms of the GNU General Public
+License (or the Lesser <span class="inserted"><ins><em>GPL, or the
Affero</em></ins></span> GPL).</p>
+
+<span class="inserted"><ins><em><h3>The copyright disclaimer</h3>
+
+<p>To avoid possible legal complications later, it's wise to ask your
+employer or school, if any, to sign a copyright disclaimer for your
+program, so it cannot later claim that the copyright belongs to it
+and that you had no right to release the program at all. This really
+has nothing to do with the GNU GPL—it applies no matter which
+free software license you use to release the program.</p>
+
+<p>Here is a sample copyright disclaimer; just alter the names, title,
+and program description as appropriate:</p>
+
+<blockquote>
+<p>Yoyodyne, Inc., hereby disclaims all copyright interest
+in the program “Woodpecker” (which deconstructs trees)
+written by James Hacker.</p>
+
+<p><em>signature of Moe Ghoul</em> 1 April 1989<br />
+ Moe Ghoul, President of Vice</p>
+</blockquote>
+
+<p>If you are a university student, we recommend you request the
+disclaimer <a href="/philosophy/university.html"> at an early stage in
+writing the program</a> to reduce resistance. If you are not a
+research assistant or teaching assistant, it could be that the university
+has no claim to copyright on your work, but ask a lawyer to make
+sure of that.</p>
+
+<p>If you work, the best time to negotiate permission to release free
+software is <em>when negotiating your employment
agreement</em>.</p>
+
+<h3>The copyright notice</h3></em></ins></span>
+
+<p>The copyright notice should include the year in which you finished
+preparing the release (so if you finished it in 1998 but didn't post
+it until 1999, use 1998). You should add the proper year for each
+<span class="inserted"><ins><em>past</em></ins></span> release; for example,
“Copyright 1998, 1999 Terry
+Jones” if some
+<span class="removed"><del><strong>versions</strong></del></span> <span
class="inserted"><ins><em>releases</em></ins></span> were finished in 1998 and
some were
+finished in 1999. If several people helped write the code, use all
+their names.</p>
+
+<p>For software with several releases over multiple years, it's okay
+to use a range (“2008-2010”) instead of listing individual
+years (“2008, 2009, 2010”) if and only if every year in
+the range, inclusive, really is a “copyrightable” year
+that would be listed individually; <em>and</em> you make an
explicit
+statement in your documentation about this usage.</p>
+
+<p>Always use the English word “Copyright”; by international
+convention, this is used worldwide, even for material in other
+languages. The copyright symbol “©” can be included if
+you wish (and your character set supports it), but it's not necessary.
+There is no legal significance to using the three-character sequence
+“(C)”, <span
class="removed"><del><strong>although</strong></del></span> <span
class="inserted"><ins><em>but</em></ins></span> it does no harm.</p>
+
+<span class="inserted"><ins><em><p>If you have copied code from other
programs covered by the same
+license, copy their copyright notices too. Put all the copyright
+notices for a file together, right near the top of the file.</p>
+
+<h3>The license files</h3></em></ins></span>
+
+<p>You should also include a copy of the license itself somewhere in the
+distribution of your program. All programs, whether they are released
+under the GPL or LGPL, should include <a href="/licenses/gpl.txt">the
+text version of the GPL</a>. In GNU programs <span
class="inserted"><ins><em>we conventionally put</em></ins></span> the
+license <span class="removed"><del><strong>is usually</strong></del></span> in
a file called COPYING.</p>
+
+<p>If you are releasing your program under the <span
class="removed"><del><strong>LGPL,</strong></del></span> <span
class="inserted"><ins><em>GNU AGPL,
+use <a href="/licenses/agpl.txt">the text version of the GNU
AGPL</a>
+instead of the GNU GPL.</p>
+
+<p>If you are releasing your program under the Lesser
GPL,</em></ins></span> you should also
+include <a href="/licenses/lgpl.txt">the text version of the
LGPL</a>,
+usually in a file called COPYING.LESSER. Please note that, since the
+LGPL is a set of additional permissions on top of the GPL, it's <span
class="removed"><del><strong>important</strong></del></span> <span
class="inserted"><ins><em>crucial</em></ins></span>
+to include both licenses so users have all the materials they need to
+understand their rights.</p>
+
+<span class="removed"><del><strong><p>If you are releasing your program
under the GNU AGPL, you only need to
+include <a href="/licenses/agpl.txt">the text version of the GNU
+AGPL</a>.</p>
+
+<p>If you have copied code from other programs covered by the same
+license, copy their copyright notices too. Put all the copyright
+notices together, right near the top of each file.</p>
+
+<p>It is very important for practical reasons to include contact
+information for how to reach you, perhaps in the README file, but this
+has nothing to do with the legal issues of applying the license.</p>
+
+<p>The</strong></del></span>
+
+<span class="inserted"><ins><em><h3>The license notices</h3>
+
+<p>Each file's</em></ins></span> copying permission statement <span
class="inserted"><ins><em>(also called the license notice)</em></ins></span>
+should come right after <span
class="removed"><del><strong>the</strong></del></span> <span
class="inserted"><ins><em>its</em></ins></span> copyright notices. For a
one-file
+program, the statement (for the GPL) should look like <span
class="removed"><del><strong>this:</p></strong></del></span> <span
class="inserted"><ins><em>this, to use
+GPL version 3 or later:</p></em></ins></span>
+
+<pre>
+ 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 3 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, see <http://www.gnu.org/licenses/>.
+</pre>
+
+<p>For programs that are more than one file, it is better to replace
+“this program” with the name of the program, and begin the
+statement with a line saying “This file is part of NAME”.
+For instance,</p>
+
+<pre>
+ This file is part of Foobar.
+
+ Foobar 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 3 of the License, or
+ (at your option) any later version.
+
+ Foobar 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 <span class="removed"><del><strong>Foobar. If not, see
<http://www.gnu.org/licenses/>.
+</pre></strong></del></span> <span class="inserted"><ins><em>Foobar. If
not, see <http://www.gnu.org/licenses/>.
+</pre>
+
+<p>To use a different set of GPL versions, you would modify the end of
+the first long paragraph. For instance, to license under version 2 or
+later, you would replace “3” with
“2”.</p></em></ins></span>
+
+<p>This statement should go near the beginning of every source file,
+close to the copyright notices. When using the Lesser GPL, insert the
+word “Lesser” before “General” in <em>all
+three</em> places. When using the GNU AGPL, insert the
+word “Affero” before “General” in <em>all
+three</em> places.</p>
+
+<span class="inserted"><ins><em><h3>Why license notices?</h3>
+
+<p>The purpose of a free software license is to give certain rights to
+all users of a program. If it is not clear what rights you have given
+them, that defeats the purpose. Our practices are designed to
+avoid any uncertainty.</p>
+
+<p>If a program has a copy of a license FOO alongside the source files,
+but doesn't have an explicit statement that “This program is
+released under license FOO,” that leaves room for uncertainty
+about whether the license FOO applies to the code of that program.</p>
+
+<p>If a release has one statement that “This program is released
+under license FOO,” in a central place such as the README file,
+that makes the situation clear <em>for that release</em>. However,
+programmers often copy source files from one free program into
+another. If a source file contains no statement about what its
+license is, then moving it into another context eliminates all trace
+of that point. This invites confusion and error.</p>
+
+<h3>The startup notice</h3></em></ins></span>
+
+<p>For interactive programs, it is usually a good idea to make the
+program <span class="removed"><del><strong>print out</strong></del></span>
<span class="inserted"><ins><em>display</em></ins></span> a brief notice about
copyright and copying permission
+when it starts up. See <a href="/licenses/gpl-3.0.html#howto">the end
+of the GNU GPL</a> for more information about this.</p>
+
+<span class="inserted"><ins><em><h3>The Affero
notice</h3></em></ins></span>
+
+<p>If you are releasing your program under the GNU AGPL, and it can
+interact with users over a network, the program should offer its source to
+those users in some way. For example, if your program is a web
+application, its interface could display a “Source” link that
+leads users to an archive of the code. The GNU AGPL is flexible enough
+that you can choose a method that's suitable for your specific
+program—see section 13 for details.</p>
+
+<span class="inserted"><ins><em><h3>Miscellaneous</h3>
+
+<p>It is very important for practical reasons to include contact
+information for how to reach you, perhaps in the README file, but this
+has nothing to do with the legal issues of applying the
license.</p></em></ins></span>
+
+<p>There is no legal requirement to register your copyright with anyone;
+simply <span class="removed"><del><strong>distributing</strong></del></span>
<span class="inserted"><ins><em>writing</em></ins></span> the program makes it
copyrighted. However, <span class="inserted"><ins><em>for the
US,</em></ins></span>
+it is a
+<span class="removed"><del><strong>very</strong></del></span> good idea to
register the copyright with the US Registry of
+Copyrights, because that puts you in a stronger position against anyone
+who violates the license in the US. Most other countries have no system
+of copyright registration.</p>
+
+<span class="removed"><del><strong><p>It's wise to ask your employer or
school, if any, to sign a
+copyright disclaimer for the work, so they cannot claim to hold it
+later. Below is a sample copyright disclaimer; just alter the names
+and program description as appropriate:</p>
+
+<blockquote><p>Yoyodyne, Inc., hereby disclaims all copyright
interest
+in the program “Gnomovision” (which makes passes at
+compilers) written by James Hacker.</p>
+
+<p><signature of Moe Ghoul>, 1 April 1989<br />
+ Moe Ghoul, President of
Vice</p></blockquote></strong></del></span>
+
+<p>We would like to list all free software programs in the Free
+Software Directory, including all programs licensed under the GPL (any
+version). <span class="inserted"><ins><em>So please submit an entry for your
program, when it has
+reached the point of being useful.</em></ins></span> Please see
+the <a href="http://directory.fsf.org/">Directory web page</a> for
+information and an online submission form.</p>
+
+<p>It is also possible to make your program a GNU package, a part of the
+GNU Project. <span class="removed"><del><strong>(That's if we like the
program—we have to look at it
+first, and decide.)</strong></del></span> If you might be interested in
joining up with the
+GNU Project in this way, please see our <a
+href="/help/evaluation.html">GNU software evaluation page</a> for more
+information and a short <span
class="removed"><del><strong>questionnaire.</p>
+
+<p>But you</strong></del></span> <span
class="inserted"><ins><em>questionnaire. We will respond and discuss the
+matter with you.</p>
+
+<p>You</em></ins></span> are welcome to use any of our licenses even if
your program
+is not a GNU package; indeed, we hope you will. They're available to
+everyone. If you'd like to advertise your use of a particular license,
+feel free to use <a href="/graphics/license-logos.html"
+title="GNU License Logos">one of our logos</a>.</p>
+
+</div><!-- for id="content", starts in the include above -->
+<!--#include virtual="/server/footer.html" -->
+<div id="footer">
+<div class="unprintable">
+
+<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. Broken links and other corrections or suggestions can be sent
+to <a
href="mailto:address@hidden"><address@hidden></a>.</p>
+
+<p><!-- TRANSLATORS: Ignore the original text in this paragraph,
+ replace it with the translation of these two:
+
+ We work hard and do our best to provide accurate, good quality
+ translations. However, we are not exempt from imperfection.
+ Please send your comments and general suggestions in this regard
+ to <a href="mailto:address@hidden">
+ <address@hidden></a>.</p>
+
+ <p>For information on coordinating and submitting translations of
+ our web pages, see <a
+ href="/server/standards/README.translations.html">Translations
+ README</a>. -->
+Please see the <a
+href="/server/standards/README.translations.html">Translations
+README</a> for information on coordinating and submitting translations
+of this article.</p>
+</div>
+
+<!-- Regarding copyright, in general, standalone pages (as opposed to
+ files generated as part of manuals) on the GNU web server should
+ be under CC BY-ND <span class="removed"><del><strong>3.0
US.</strong></del></span> <span
class="inserted"><ins><em>4.0.</em></ins></span> 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. For web pages, it is ok to list just the latest year the
+ document was modified, or published.
+
+ If you wish to list earlier years, that is ok too.
+ Either "2001, 2002, 2003" or "2001-2003" are ok for specifying
+ years, as long as each year in the range is in fact a copyrightable
+ year, i.e., a year in which the document was published (including
+ being publicly visible on the web or in a revision control system).
+
+ There is more detail about copyright years in the GNU Maintainers
+ Information document, www.gnu.org/prep/maintain. -->
+
+<p>Copyright © 2001, 2007, 2008, 2009, 2013, <span
class="removed"><del><strong>2014</strong></del></span> <span
class="inserted"><ins><em>2014, 2017</em></ins></span>
+Free Software Foundation, Inc.</p>
+
+<p>This page is licensed under a <a rel="license"
+<span
class="removed"><del><strong>href="http://creativecommons.org/licenses/by-nd/3.0/us/">Creative</strong></del></span>
+<span
class="inserted"><ins><em>href="http://creativecommons.org/licenses/by-nd/4.0/">Creative</em></ins></span>
+Commons <span class="removed"><del><strong>Attribution-NoDerivs 3.0 United
States</strong></del></span> <span
class="inserted"><ins><em>Attribution-NoDerivatives 4.0
International</em></ins></span> License</a>.</p>
+
+<!--#include virtual="/server/bottom-notes.html" -->
+
+<p class="unprintable">Updated:
+<!-- timestamp start -->
+$Date: 2017/10/16 18:29:27 $
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>
+</pre></body></html>
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- www/licenses gpl-howto.ca.html gpl-howto.de.htm...,
GNUN <=