www-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

www/licenses gpl-howto.html


From: Karl Berry
Subject: www/licenses gpl-howto.html
Date: Sat, 10 Feb 2007 16:21:34 +0000

CVSROOT:        /web/www
Module name:    www
Changes by:     Karl Berry <karl>       07/02/10 16:21:34

Modified files:
        licenses       : gpl-howto.html 

Log message:
        copyright symbol not needed, etc.

CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/gpl-howto.html?cvsroot=www&r1=1.11&r2=1.12

Patches:
Index: gpl-howto.html
===================================================================
RCS file: /web/www/www/licenses/gpl-howto.html,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -b -r1.11 -r1.12
--- gpl-howto.html      10 Feb 2007 00:20:40 -0000      1.11
+++ gpl-howto.html      10 Feb 2007 16:21:30 -0000      1.12
@@ -37,21 +37,34 @@
 <a href="/licenses/gpl-faq.html">frequently-asked questions about the GNU
 General Public License</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 Library GPL 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>
+<p>If you are considering using the GNU Lesser General Public License,
+please read the article &ldquo; <a
+href="/licenses/why-not-lgpl.html">Why you shouldn't use the Library GPL
+for your next library</a>&rdquo; first.  The 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&copy; 1999 Linda Jones"), and a statement of copying
+as &ldquo;Copyright 1999 Terry Jones&rdquo;), 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>
 
+<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 have
+helped write the code, use all their names.</p>
+
+<p>Always use the English word &ldquo;Copyright&rdquo;; by international
+convention, this is used worldwide, even for material in other
+languages. The copyright symbol &ldquo;&copy;&rdquo; 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
+&ldquo;(C)&rdquo;, although it does no harm.<p>
+
 <p>
 You should also include a copy of the license itself somewhere in the
 distribution of your program.  In GNU programs the license is usually
@@ -62,15 +75,6 @@
 version Lesser GPL</a>.</p>
 
 <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&copy; 1998, 1999 Linda Jones" if some versions were finished 
-in 1998
-and some were finished in 1999.  If several people have helped write the
-code, use all their names.</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>
@@ -103,8 +107,8 @@
 
 <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>
+&ldquot;this program&rdquo; with the name of the program, and begin the 
statement
+with a line saying &ldquo;This file is part of NAME&rdquo;.  For instance,</p>
 
 <pre>
     This file is part of Foobar.
@@ -124,11 +128,11 @@
     Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA  02110-1301  USA
 </pre>
 
-<p>
-This statement should go near the beginning of every source file, close to
-the copyright notices.  For using the Lesser GPL, insert the word "Lesser"
-before "General" in <em>all three</em> places, and change "version 2" to
-"version 2.1".</p>
+<p> This statement should go near the beginning of every source file,
+close to the copyright notices.  For using the Lesser GPL, insert the
+word &ldquo;Lesser&rdquo; before &ldquo;General&rdquo; in <em>all
+three</em> places, and change &ldquo;version 2&rdquo; to &ldquo;version
+2.1&rdquo;.</p>
 
 <p>
 For interactive programs, it is usually a good idea to make the
@@ -225,7 +229,7 @@
 </p>
 
 <p>
-Copyright (C) 2001 Free Software Foundation, Inc.,
+Copyright &copy; 2001, 2007 Free Software Foundation, Inc.,
 51 Franklin St, Fifth Floor, Boston, MA  02110,  USA
 <br />
 Verbatim copying and distribution of this entire article is
@@ -236,7 +240,7 @@
 <p>
 Updated:
 <!-- timestamp start -->
-$Date: 2007/02/10 00:20:40 $ $Author: exal $
+$Date: 2007/02/10 16:21:30 $
 <!-- timestamp end -->
 </p>
 </div>




reply via email to

[Prev in Thread] Current Thread [Next in Thread]