[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
www/licenses why-gfdl.html
From: |
Yavor Doganov |
Subject: |
www/licenses why-gfdl.html |
Date: |
Mon, 01 Sep 2008 14:16:11 +0000 |
CVSROOT: /web/www
Module name: www
Changes by: Yavor Doganov <yavor> 08/09/01 14:16:11
Modified files:
licenses : why-gfdl.html
Log message:
Boilerplate compliance fixes.
CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/why-gfdl.html?cvsroot=www&r1=1.17&r2=1.18
Patches:
Index: why-gfdl.html
===================================================================
RCS file: /web/www/www/licenses/why-gfdl.html,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -b -r1.17 -r1.18
--- why-gfdl.html 19 Jun 2007 00:03:29 -0000 1.17
+++ why-gfdl.html 1 Sep 2008 14:16:09 -0000 1.18
@@ -12,7 +12,7 @@
<h2>Why publishers should use the GNU FDL</h2>
-<h3>by <a href="http://www.stallman.org/">Richard Stallman</a></h3>
+<p>by <a href="http://www.stallman.org/">Richard Stallman</a></p>
<p>
Can technical writers earn money by writing free documentation for
@@ -20,13 +20,14 @@
the GNU Free Documentation License.</p>
<p>
The GFDL is meant as a way to enlist commercial publishers in funding
-free documentation without surrendering any vital liberty. The "cover
-text" feature, and certain other aspects of the license that deal with
-covers, title page, history, and endorsements, are included to make
-the license appealing to commercial publishers for books whose authors
-are paid. To improve the appeal, I consulted specifically with staff
-of publishing companies, as well as lawyers, free documentation
-writers, and the community at large, in writing the GFDL.</p>
+free documentation without surrendering any vital liberty. The
+“cover text” feature, and certain other aspects of the
+license that deal with covers, title page, history, and endorsements,
+are included to make the license appealing to commercial publishers
+for books whose authors are paid. To improve the appeal, I consulted
+specifically with staff of publishing companies, as well as lawyers,
+free documentation writers, and the community at large, in writing the
+GFDL.</p>
<p>
At least two commercial publishers of software manuals have told me
they are interested in using this license. The future is never a sure
@@ -51,7 +52,7 @@
There are also <a href="/contact/">other ways to contact</a>
the FSF.
<br />
-Please send broken links and other corrections (or suggestions) to
+Please send broken links and other corrections or suggestions to
<a href="mailto:address@hidden"><em>address@hidden</em></a>.
</p>
@@ -63,7 +64,7 @@
</p>
<p>
-Copyright © 2000, 2007 Free Software Foundation, Inc.,
+Copyright © 2000, 2007, 2008 Free Software Foundation, Inc.,
</p>
<address>51 Franklin St, Fifth Floor, Boston, MA 02110, USA</address>
<p>Verbatim copying and distribution of this entire article are
@@ -74,7 +75,7 @@
<p>
Updated:
<!-- timestamp start -->
-$Date: 2007/06/19 00:03:29 $
+$Date: 2008/09/01 14:16:09 $
<!-- timestamp end -->
</p>
</div>
@@ -82,27 +83,36 @@
<div id="translations">
<h4>Translations of this page</h4>
-<!-- Please keep this list alphabetical. -->
-<!-- Comment what the language is for each type, i.e. de is Deutsch.-->
+<!-- Please keep this list alphabetical by language code. -->
+<!-- Comment what the language is for each type, i.e. de is German. -->
+<!-- Write the language name in its own language (Deutsch) in the text. -->
<!-- If you add a new language here, please -->
<!-- advise address@hidden and add it to -->
-<!-- - /home/www/bin/nightly-vars either TAGSLANG or WEBLANG -->
<!-- - /home/www/html/server/standards/README.translations.html -->
<!-- - one of the lists under the section "Translations Underway" -->
<!-- - if there is a translation team, you also have to add an alias -->
<!-- to mail.gnu.org:/com/mailer/aliases -->
-<!-- Please also check you have the 2 letter language code right versus -->
-<!-- <URL:http://www.w3.org/WAI/ER/IG/ert/iso639.htm> -->
-<!-- Please use W3C normative character entities -->
+<!-- Please also check you have the language code right; see: -->
+<!-- http://www.loc.gov/standards/iso639-2/php/code_list.php -->
+<!-- If the 2-letter ISO 639-1 code is not available, -->
+<!-- use the 3-letter ISO 639-2. -->
+<!-- Please use W3C normative character entities. -->
<ul class="translations-list">
- <li><a href="why-gfdl.zh-cn.html">简体中文</a></li>
<!-- Chinese(Simplified) -->
- <li><a href="why-gfdl.zh-tw.html">繁體中文</a></li>
<!-- Chinese(Traditional) -->
- <li><a href="why-gfdl.html">English</a></li>
- <li><a href="why-gfdl.fr.html">Français</a></li> <!-- French -->
- <li><a href="why-gfdl.ja.html">日本語</a></li> <!--
Japanese -->
- <li><a href="why-gfdl.ko.html">한국어</a></li> <!--
Korean -->
- <li><a href="why-gfdl.pl.html">Polski</a></li> <!-- Polish -->
+<!-- English -->
+<li><a href="/licenses/why-gfdl.html">English</a> [en]</li>
+<!-- French -->
+<li><a href="/licenses/why-gfdl.fr.html">Français</a> [fr]</li>
+<!-- Japanese -->
+<li><a
href="/licenses/why-gfdl.ja.html">日本語</a> [ja]</li>
+<!-- Korean -->
+<li><a
href="/licenses/why-gfdl.ko.html">한국어</a> [ko]</li>
+<!-- Polish -->
+<li><a href="/licenses/why-gfdl.pl.html">Polski</a> [pl]</li>
+<!-- Chinese (Simplified) -->
+<li><a
href="/licenses/why-gfdl.zh-cn.html">简体中文</a> [zh-cn]</li>
+<!-- Chinese (Traditional) -->
+<li><a
href="/licenses/why-gfdl.zh-tw.html">繁體中文</a> [zh-tw]</li>
</ul>
</div>
</div>
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- www/licenses why-gfdl.html,
Yavor Doganov <=