www-commits
[Top][All Lists]
Advanced

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

www/prep/maintain index.html maintain.dvi.gz ma...


From: Karl Berry
Subject: www/prep/maintain index.html maintain.dvi.gz ma...
Date: Wed, 07 Sep 2011 15:01:17 +0000

CVSROOT:        /web/www
Module name:    www
Changes by:     Karl Berry <karl>       11/09/07 15:01:17

Modified files:
        prep/maintain  : index.html maintain.dvi.gz maintain.html 
                         maintain.html.gz maintain.html_node.tar.gz 
                         maintain.info.tar.gz maintain.pdf 
                         maintain.ps.gz maintain.texi.tar.gz 
                         maintain.txt maintain.txt.gz 
        prep/maintain/html_node: Announcements.html 
                                 Automated-FTP-Uploads.html 
                                 Automated-Upload-Procedure.html 
                                 Automated-Upload-Registration.html 
                                 CVS-Keywords-in-Web-Pages.html 
                                 Canonical-License-Sources.html 
                                 Clean-Ups.html 
                                 Copying-from-Other-Packages.html 
                                 Copyright-Notices.html 
                                 Copyright-Papers.html 
                                 Creating-Mailing-Lists.html 
                                 Distribution-Patches.html 
                                 Distribution-on-ftp_002egnu_002eorg.html 
                                 Distribution-tar-Files.html 
                                 Distributions.html Donations.html 
                                 Ethical-and-Philosophical-Consideration.html 
                                 External-Libraries.html 
                                 FTP-Upload-Directive-File-_002d-v1_002e0.html 
                                 FTP-Upload-Directive-File-_002d-v1_002e1.html 
                                 Free-Software-Directory.html 
                                 Free-Software-and-Open-Source.html 
                                 Freedom-for-Web-Pages.html 
                                 GNU-Free-Documentation-License.html 
                                 GNU-and-Linux.html Getting-Help.html 
                                 Getting-a-GNU-Account.html 
                                 Hosting-for-Web-Pages.html Hosting.html 
                                 Index.html Invoking-gendocs_002esh.html 
                                 Legal-Matters.html 
                                 Legally-Significant.html 
                                 License-Notices-for-Code.html 
                                 License-Notices-for-Documentation.html 
                                 License-Notices-for-Other-Files.html 
                                 License-Notices.html 
                                 Licensing-of-GNU-Packages.html 
                                 Mail.html Manuals-on-Web-Pages.html 
                                 Old-Versions.html Platforms.html 
                                 Preface.html 
                                 Recording-Contributors.html 
                                 Recruiting-Developers.html 
                                 Replying-to-Mail.html 
                                 Standard-Mailing-Lists.html 
                                 Stepping-Down.html Terminology.html 
                                 Test-Releases.html 
                                 Using-the-Proofreaders-List.html 
                                 Web-Pages.html index.html 

Log message:
        regenerate with new makeinfo

CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/index.html?cvsroot=www&r1=1.76&r2=1.77
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/maintain.dvi.gz?cvsroot=www&rev=1.69
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/maintain.html?cvsroot=www&r1=1.71&r2=1.72
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/maintain.html.gz?cvsroot=www&rev=1.70
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/maintain.html_node.tar.gz?cvsroot=www&rev=1.70
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/maintain.info.tar.gz?cvsroot=www&rev=1.69
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/maintain.pdf?cvsroot=www&rev=1.70
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/maintain.ps.gz?cvsroot=www&rev=1.69
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/maintain.texi.tar.gz?cvsroot=www&rev=1.69
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/maintain.txt?cvsroot=www&r1=1.71&r2=1.72
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/maintain.txt.gz?cvsroot=www&rev=1.69
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Announcements.html?cvsroot=www&r1=1.66&r2=1.67
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Automated-FTP-Uploads.html?cvsroot=www&r1=1.66&r2=1.67
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Automated-Upload-Procedure.html?cvsroot=www&r1=1.66&r2=1.67
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Automated-Upload-Registration.html?cvsroot=www&r1=1.66&r2=1.67
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/CVS-Keywords-in-Web-Pages.html?cvsroot=www&r1=1.65&r2=1.66
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Canonical-License-Sources.html?cvsroot=www&r1=1.50&r2=1.51
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Clean-Ups.html?cvsroot=www&r1=1.66&r2=1.67
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Copying-from-Other-Packages.html?cvsroot=www&r1=1.54&r2=1.55
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Copyright-Notices.html?cvsroot=www&r1=1.66&r2=1.67
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Copyright-Papers.html?cvsroot=www&r1=1.68&r2=1.69
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Creating-Mailing-Lists.html?cvsroot=www&r1=1.17&r2=1.18
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Distribution-Patches.html?cvsroot=www&r1=1.66&r2=1.67
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Distribution-on-ftp_002egnu_002eorg.html?cvsroot=www&r1=1.66&r2=1.67
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Distribution-tar-Files.html?cvsroot=www&r1=1.66&r2=1.67
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Distributions.html?cvsroot=www&r1=1.66&r2=1.67
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Donations.html?cvsroot=www&r1=1.9&r2=1.10
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Ethical-and-Philosophical-Consideration.html?cvsroot=www&r1=1.67&r2=1.68
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/External-Libraries.html?cvsroot=www&r1=1.66&r2=1.67
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/FTP-Upload-Directive-File-_002d-v1_002e0.html?cvsroot=www&r1=1.56&r2=1.57
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/FTP-Upload-Directive-File-_002d-v1_002e1.html?cvsroot=www&r1=1.56&r2=1.57
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Free-Software-Directory.html?cvsroot=www&r1=1.66&r2=1.67
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Free-Software-and-Open-Source.html?cvsroot=www&r1=1.68&r2=1.69
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Freedom-for-Web-Pages.html?cvsroot=www&r1=1.25&r2=1.26
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/GNU-Free-Documentation-License.html?cvsroot=www&r1=1.43&r2=1.44
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/GNU-and-Linux.html?cvsroot=www&r1=1.66&r2=1.67
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Getting-Help.html?cvsroot=www&r1=1.20&r2=1.21
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Getting-a-GNU-Account.html?cvsroot=www&r1=1.19&r2=1.20
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Hosting-for-Web-Pages.html?cvsroot=www&r1=1.25&r2=1.26
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Hosting.html?cvsroot=www&r1=1.66&r2=1.67
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Index.html?cvsroot=www&r1=1.66&r2=1.67
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Invoking-gendocs_002esh.html?cvsroot=www&r1=1.66&r2=1.67
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Legal-Matters.html?cvsroot=www&r1=1.66&r2=1.67
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Legally-Significant.html?cvsroot=www&r1=1.66&r2=1.67
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/License-Notices-for-Code.html?cvsroot=www&r1=1.50&r2=1.51
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/License-Notices-for-Documentation.html?cvsroot=www&r1=1.50&r2=1.51
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/License-Notices-for-Other-Files.html?cvsroot=www&r1=1.50&r2=1.51
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/License-Notices.html?cvsroot=www&r1=1.68&r2=1.69
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Licensing-of-GNU-Packages.html?cvsroot=www&r1=1.6&r2=1.7
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Mail.html?cvsroot=www&r1=1.66&r2=1.67
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Manuals-on-Web-Pages.html?cvsroot=www&r1=1.25&r2=1.26
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Old-Versions.html?cvsroot=www&r1=1.68&r2=1.69
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Platforms.html?cvsroot=www&r1=1.66&r2=1.67
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Preface.html?cvsroot=www&r1=1.66&r2=1.67
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Recording-Contributors.html?cvsroot=www&r1=1.66&r2=1.67
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Recruiting-Developers.html?cvsroot=www&r1=1.66&r2=1.67
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Replying-to-Mail.html?cvsroot=www&r1=1.17&r2=1.18
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Standard-Mailing-Lists.html?cvsroot=www&r1=1.17&r2=1.18
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Stepping-Down.html?cvsroot=www&r1=1.66&r2=1.67
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Terminology.html?cvsroot=www&r1=1.66&r2=1.67
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Test-Releases.html?cvsroot=www&r1=1.66&r2=1.67
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Using-the-Proofreaders-List.html?cvsroot=www&r1=1.66&r2=1.67
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Web-Pages.html?cvsroot=www&r1=1.66&r2=1.67
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/index.html?cvsroot=www&r1=1.66&r2=1.67

Patches:
Index: index.html
===================================================================
RCS file: /web/www/www/prep/maintain/index.html,v
retrieving revision 1.76
retrieving revision 1.77
diff -u -b -r1.76 -r1.77
--- index.html  7 Sep 2011 01:31:08 -0000       1.76
+++ index.html  7 Sep 2011 14:59:06 -0000       1.77
@@ -4,25 +4,25 @@
 <h2>Information for maintainers of GNU software</h2>
 
 <address>Free Software Foundation</address>
-<address>last updated September 06, 2011</address>
+<address>last updated September 07, 2011</address>
 
 <p>This manual (maintain) is available in the following formats:</p>
 
 <ul>
 <li><a href="maintain.html">HTML
-    (172K bytes)</a> - entirely on one web page.</li>
+    (196K bytes)</a> - entirely on one web page.</li>
 <li><a href="html_node/index.html">HTML</a> - with one web page per
     node.</li>
 <li><a href="maintain.html.gz">HTML compressed
     (48K gzipped characters)</a> - entirely on
     one web page.</li>
 <li><a href="maintain.html_node.tar.gz">HTML compressed
-    (60K gzipped tar file)</a> -
+    (64K gzipped tar file)</a> -
     with one web page per node.</li>
 <li><a href="maintain.info.tar.gz">Info document
     (40K bytes gzipped tar file)</a>.</li>
 <li><a href="maintain.txt">ASCII text
-    (124K bytes)</a>.</li>
+    (116K bytes)</a>.</li>
 <li><a href="maintain.txt.gz">ASCII text compressed
     (40K bytes gzipped)</a>.</li>
 <li><a href="maintain.dvi.gz">TeX dvi file

Index: maintain.dvi.gz
===================================================================
RCS file: /web/www/www/prep/maintain/maintain.dvi.gz,v
retrieving revision 1.68
retrieving revision 1.69
diff -u -b -r1.68 -r1.69
Binary files /tmp/cvsCA6nG2 and /tmp/cvsfK3XvJ differ

Index: maintain.html
===================================================================
RCS file: /web/www/www/prep/maintain/maintain.html,v
retrieving revision 1.71
retrieving revision 1.72
diff -u -b -r1.71 -r1.72
--- maintain.html       7 Sep 2011 01:31:08 -0000       1.71
+++ maintain.html       7 Sep 2011 14:59:07 -0000       1.72
@@ -1,175 +1,216 @@
-<html lang="en">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" 
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
+<!-- Information for maintainers of GNU software, last updated September 5, 
2011.
+
+Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
+2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
+2010, 2011 Free Software Foundation, Inc.
+
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
+Texts.  A copy of the license is included in the section entitled
+"GNU Free Documentation License". -->
+<!-- Created by texi2html, http://www.gnu.org/software/texinfo/ -->
 <head>
 <title>Information for Maintainers of GNU Software</title>
-<meta http-equiv="Content-Type" content="text/html">
+
 <meta name="description" content="Information for Maintainers of GNU Software">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="top" href="#Top">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home" 
title="Texinfo Homepage">
+<meta name="keywords" content="Information for Maintainers of GNU Software">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="texi2html">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="#Top" rel="start" title="Top">
+<link href="#Index" rel="index" title="Index">
+<link href="#SEC_Contents" rel="contents" title="Table of Contents">
+<style type="text/css">
 <!--
-Information for maintainers of GNU software, last updated September 5, 2011.
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smalllisp {margin-left: 3.2em}
+pre.display {font-family: serif}
+pre.format {font-family: serif}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: serif; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: serif; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:pre}
+span.nolinebreak {white-space:pre}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
 
-Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
-2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
-2010, 2011 Free Software Foundation, Inc.
 
-     Permission is granted to copy, distribute and/or modify this
-     document under the terms of the GNU Free Documentation License,
-     Version 1.3 or any later version published by the Free Software
-     Foundation; with no Invariant Sections, with no Front-Cover Texts,
-     and with no Back-Cover Texts.  A copy of the license is included
-     in the section entitled "GNU Free Documentation License".
-   -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
-  pre.display { font-family:inherit }
-  pre.format  { font-family:inherit }
-  pre.smalldisplay { font-family:inherit; font-size:smaller }
-  pre.smallformat  { font-family:inherit; font-size:smaller }
-  pre.smallexample { font-size:smaller }
-  pre.smalllisp    { font-size:smaller }
-  span.sc    { font-variant:small-caps }
-  span.roman { font-family:serif; font-weight:normal; } 
-  span.sansserif { font-family:sans-serif; font-weight:normal; } 
---></style>
 </head>
-<body>
-<h1 class="settitle">Information for Maintainers of GNU Software</h1>
-<div class="contents">
-<h2>Table of Contents</h2>
-<ul>
-<li><a name="toc_Top" href="#Top">Version</a>
-<li><a name="toc_Preface" href="#Preface">1 About This Document</a>
-<li><a name="toc_Getting-Help" href="#Getting-Help">2 Getting Help</a>
-<li><a name="toc_Getting-a-GNU-Account" href="#Getting-a-GNU-Account">3 
Getting a GNU Account</a>
-<li><a name="toc_Stepping-Down" href="#Stepping-Down">4 Stepping Down</a>
-<li><a name="toc_Recruiting-Developers" href="#Recruiting-Developers">5 
Recruiting Developers</a>
-<li><a name="toc_Legal-Matters" href="#Legal-Matters">6 Legal Matters</a>
-<ul>
-<li><a href="#Copyright-Papers">6.1 Copyright Papers</a>
-<li><a href="#Legally-Significant">6.2 Legally Significant Changes</a>
-<li><a href="#Recording-Contributors">6.3 Recording Contributors</a>
-<li><a href="#Copying-from-Other-Packages">6.4 Copying from Other Packages</a>
-<li><a href="#Copyright-Notices">6.5 Copyright Notices</a>
-<li><a href="#License-Notices">6.6 License Notices</a>
-<ul>
-<li><a href="#Licensing-of-GNU-Packages">6.6.1 Licensing of GNU Packages</a>
-<li><a href="#Canonical-License-Sources">6.6.2 Canonical License Sources</a>
-<li><a href="#License-Notices-for-Code">6.6.3 License Notices for Code</a>
-<li><a href="#License-Notices-for-Documentation">6.6.4 License Notices for 
Documentation</a>
-<li><a href="#License-Notices-for-Other-Files">6.6.5 License Notices for Other 
Files</a>
-</li></ul>
-<li><a href="#External-Libraries">6.7 External Libraries</a>
-</li></ul>
-<li><a name="toc_Clean-Ups" href="#Clean-Ups">7 Cleaning Up Changes</a>
-<li><a name="toc_Platforms" href="#Platforms">8 Platforms to Support</a>
-<li><a name="toc_Mail" href="#Mail">9 Dealing With Mail</a>
-<ul>
-<li><a href="#Standard-Mailing-Lists">9.1 Standard Mailing Lists</a>
-<li><a href="#Creating-Mailing-Lists">9.2 Creating Mailing Lists</a>
-<li><a href="#Replying-to-Mail">9.3 Replying to Mail</a>
-</li></ul>
-<li><a name="toc_Old-Versions" href="#Old-Versions">10 Recording Old 
Versions</a>
-<li><a name="toc_Distributions" href="#Distributions">11 Distributions</a>
-<ul>
-<li><a href="#Distribution-tar-Files">11.1 Distribution tar Files</a>
-<li><a href="#Distribution-Patches">11.2 Distribution Patches</a>
-<li><a href="#Distribution-on-ftp_002egnu_002eorg">11.3 Distribution on 
<code>ftp.gnu.org</code></a>
-<li><a href="#Test-Releases">11.4 Test Releases</a>
-<li><a href="#Automated-FTP-Uploads">11.5 Automated FTP Uploads</a>
-<ul>
-<li><a href="#Automated-Upload-Registration">11.5.1 Automated Upload 
Registration</a>
-<li><a href="#Automated-Upload-Procedure">11.5.2 Automated Upload Procedure</a>
-<li><a href="#FTP-Upload-Directive-File-_002d-v1_002e1">11.5.3 FTP Upload 
Directive File - v1.1</a>
-<li><a href="#FTP-Upload-Directive-File-_002d-v1_002e0">11.5.4 FTP Upload 
Directive File - v1.0</a>
-</li></ul>
-<li><a href="#Announcements">11.6 Announcing Releases</a>
-</li></ul>
-<li><a name="toc_Web-Pages" href="#Web-Pages">12 Web Pages</a>
-<ul>
-<li><a href="#Hosting-for-Web-Pages">12.1 Hosting for Web Pages</a>
-<li><a href="#Freedom-for-Web-Pages">12.2 Freedom for Web Pages</a>
-<li><a href="#Manuals-on-Web-Pages">12.3 Manuals on Web Pages</a>
-<ul>
-<li><a href="#Invoking-gendocs_002esh">12.3.1 Invoking <samp><span 
class="command">gendocs.sh</span></samp></a>
-</li></ul>
-<li><a href="#CVS-Keywords-in-Web-Pages">12.4 CVS Keywords in Web Pages</a>
-</li></ul>
-<li><a name="toc_Ethical-and-Philosophical-Consideration" 
href="#Ethical-and-Philosophical-Consideration">13 Ethical and Philosophical 
Consideration</a>
-<li><a name="toc_Terminology" href="#Terminology">14 Terminology Issues</a>
-<ul>
-<li><a href="#Free-Software-and-Open-Source">14.1 Free Software and Open 
Source</a>
-<li><a href="#GNU-and-Linux">14.2 GNU and Linux</a>
-</li></ul>
-<li><a name="toc_Hosting" href="#Hosting">15 Hosting</a>
-<li><a name="toc_Donations" href="#Donations">16 Donations</a>
-<li><a name="toc_Free-Software-Directory" href="#Free-Software-Directory">17 
Free Software Directory</a>
-<li><a name="toc_Using-the-Proofreaders-List" 
href="#Using-the-Proofreaders-List">18 Using the Proofreaders List</a>
-<li><a name="toc_GNU-Free-Documentation-License" 
href="#GNU-Free-Documentation-License">Appendix A GNU Free Documentation 
License</a>
-<li><a name="toc_Index" href="#Index">Index</a>
-</li></ul>
-</div>
 
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF" 
vlink="#800080" alink="#FF0000">
 
+<h1 class="settitle" align="center">Information for Maintainers of GNU 
Software</h1>
+<a name="SEC_Contents"></a>
+<h1>Table of Contents</h1>
 
-<div class="node">
-<a name="Top"></a>
-<p><hr>
-Next:&nbsp;<a rel="next" accesskey="n" href="#Preface">Preface</a>,
-Up:&nbsp;<a rel="up" accesskey="u" href="#dir">(dir)</a>
+<div class="contents">
 
+<ul class="no-bullet">
+  <li><a name="toc-About-This-Document" href="#Preface">1 About This 
Document</a></li>
+  <li><a name="toc-Getting-Help-1" href="#Getting-Help">2 Getting Help</a></li>
+  <li><a name="toc-Getting-a-GNU-Account-1" href="#Getting-a-GNU-Account">3 
Getting a GNU Account</a></li>
+  <li><a name="toc-Stepping-Down-1" href="#Stepping-Down">4 Stepping 
Down</a></li>
+  <li><a name="toc-Recruiting-Developers-1" href="#Recruiting-Developers">5 
Recruiting Developers</a></li>
+  <li><a name="toc-Legal-Matters-1" href="#Legal-Matters">6 Legal Matters</a>
+  <ul class="no-bullet">
+    <li><a name="toc-Copyright-Papers-1" href="#Copyright-Papers">6.1 
Copyright Papers</a></li>
+    <li><a name="toc-Legally-Significant-Changes" 
href="#Legally-Significant">6.2 Legally Significant Changes</a></li>
+    <li><a name="toc-Recording-Contributors-1" 
href="#Recording-Contributors">6.3 Recording Contributors</a></li>
+    <li><a name="toc-Copying-from-Other-Packages-1" 
href="#Copying-from-Other-Packages">6.4 Copying from Other Packages</a></li>
+    <li><a name="toc-Copyright-Notices-1" href="#Copyright-Notices">6.5 
Copyright Notices</a></li>
+    <li><a name="toc-License-Notices-1" href="#License-Notices">6.6 License 
Notices</a>
+    <ul class="no-bullet">
+      <li><a name="toc-Licensing-of-GNU-Packages-1" 
href="#Licensing-of-GNU-Packages">6.6.1 Licensing of GNU Packages</a></li>
+      <li><a name="toc-Canonical-License-Sources-1" 
href="#Canonical-License-Sources">6.6.2 Canonical License Sources</a></li>
+      <li><a name="toc-License-Notices-for-Code-1" 
href="#License-Notices-for-Code">6.6.3 License Notices for Code</a></li>
+      <li><a name="toc-License-Notices-for-Documentation-1" 
href="#License-Notices-for-Documentation">6.6.4 License Notices for 
Documentation</a></li>
+      <li><a name="toc-License-Notices-for-Other-Files-1" 
href="#License-Notices-for-Other-Files">6.6.5 License Notices for Other 
Files</a></li>
+    </ul></li>
+    <li><a name="toc-External-Libraries-1" href="#External-Libraries">6.7 
External Libraries</a></li>
+  </ul></li>
+  <li><a name="toc-Cleaning-Up-Changes" href="#Clean-Ups">7 Cleaning Up 
Changes</a></li>
+  <li><a name="toc-Platforms-to-Support" href="#Platforms">8 Platforms to 
Support</a></li>
+  <li><a name="toc-Dealing-With-Mail" href="#Mail">9 Dealing With Mail</a>
+  <ul class="no-bullet">
+    <li><a name="toc-Standard-Mailing-Lists-1" 
href="#Standard-Mailing-Lists">9.1 Standard Mailing Lists</a></li>
+    <li><a name="toc-Creating-Mailing-Lists-1" 
href="#Creating-Mailing-Lists">9.2 Creating Mailing Lists</a></li>
+    <li><a name="toc-Replying-to-Mail-1" href="#Replying-to-Mail">9.3 Replying 
to Mail</a></li>
+  </ul></li>
+  <li><a name="toc-Recording-Old-Versions" href="#Old-Versions">10 Recording 
Old Versions</a></li>
+  <li><a name="toc-Distributions-1" href="#Distributions">11 Distributions</a>
+  <ul class="no-bullet">
+    <li><a name="toc-Distribution-tar-Files-1" 
href="#Distribution-tar-Files">11.1 Distribution tar Files</a></li>
+    <li><a name="toc-Distribution-Patches-1" href="#Distribution-Patches">11.2 
Distribution Patches</a></li>
+    <li><a name="toc-Distribution-on-ftp_002egnu_002eorg-1" 
href="#Distribution-on-ftp_002egnu_002eorg">11.3 Distribution on 
<code>ftp.gnu.org</code></a></li>
+    <li><a name="toc-Test-Releases-1" href="#Test-Releases">11.4 Test 
Releases</a></li>
+    <li><a name="toc-Automated-FTP-Uploads-1" 
href="#Automated-FTP-Uploads">11.5 Automated FTP Uploads</a>
+    <ul class="no-bullet">
+      <li><a name="toc-Automated-Upload-Registration-1" 
href="#Automated-Upload-Registration">11.5.1 Automated Upload 
Registration</a></li>
+      <li><a name="toc-Automated-Upload-Procedure-1" 
href="#Automated-Upload-Procedure">11.5.2 Automated Upload Procedure</a></li>
+      <li><a name="toc-FTP-Upload-Directive-File-_002d-v1_002e1-1" 
href="#FTP-Upload-Directive-File-_002d-v1_002e1">11.5.3 FTP Upload Directive 
File - v1.1</a></li>
+      <li><a name="toc-FTP-Upload-Directive-File-_002d-v1_002e0-1" 
href="#FTP-Upload-Directive-File-_002d-v1_002e0">11.5.4 FTP Upload Directive 
File - v1.0</a></li>
+    </ul></li>
+    <li><a name="toc-Announcing-Releases" href="#Announcements">11.6 
Announcing Releases</a></li>
+  </ul></li>
+  <li><a name="toc-Web-Pages-1" href="#Web-Pages">12 Web Pages</a>
+  <ul class="no-bullet">
+    <li><a name="toc-Hosting-for-Web-Pages-1" 
href="#Hosting-for-Web-Pages">12.1 Hosting for Web Pages</a></li>
+    <li><a name="toc-Freedom-for-Web-Pages-1" 
href="#Freedom-for-Web-Pages">12.2 Freedom for Web Pages</a></li>
+    <li><a name="toc-Manuals-on-Web-Pages-1" href="#Manuals-on-Web-Pages">12.3 
Manuals on Web Pages</a>
+    <ul class="no-bullet">
+      <li><a name="toc-Invoking-gendocs_002esh-1" 
href="#Invoking-gendocs_002esh">12.3.1 Invoking <code>gendocs.sh</code></a></li>
+    </ul></li>
+    <li><a name="toc-CVS-Keywords-in-Web-Pages-1" 
href="#CVS-Keywords-in-Web-Pages">12.4 CVS Keywords in Web Pages</a></li>
+  </ul></li>
+  <li><a name="toc-Ethical-and-Philosophical-Consideration-1" 
href="#Ethical-and-Philosophical-Consideration">13 Ethical and Philosophical 
Consideration</a></li>
+  <li><a name="toc-Terminology-Issues" href="#Terminology">14 Terminology 
Issues</a>
+  <ul class="no-bullet">
+    <li><a name="toc-Free-Software-and-Open-Source-1" 
href="#Free-Software-and-Open-Source">14.1 Free Software and Open 
Source</a></li>
+    <li><a name="toc-GNU-and-Linux-1" href="#GNU-and-Linux">14.2 GNU and 
Linux</a></li>
+  </ul></li>
+  <li><a name="toc-Hosting-1" href="#Hosting">15 Hosting</a></li>
+  <li><a name="toc-Donations-1" href="#Donations">16 Donations</a></li>
+  <li><a name="toc-Free-Software-Directory-1" 
href="#Free-Software-Directory">17 Free Software Directory</a></li>
+  <li><a name="toc-Using-the-Proofreaders-List-1" 
href="#Using-the-Proofreaders-List">18 Using the Proofreaders List</a></li>
+  <li><a name="toc-GNU-Free-Documentation-License-1" 
href="#GNU-Free-Documentation-License">Appendix A GNU Free Documentation 
License</a></li>
+  <li><a name="toc-Index-1" href="#Index">Index</a></li>
+</ul>
 </div>
 
-<h2 class="unnumbered">Version</h2>
 
-<p>Information for maintainers of GNU software, last updated September 5, 2011.
+<a name="Top"></a>
+<div class="header">
+<p>
+Next: <a href="#Preface" accesskey="n" rel="next">Preface</a>, Up: <a 
href="dir.html#Top" accesskey="u" rel="up">(dir)</a> &nbsp; [<a 
href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a 
href="#Index" title="Index" rel="index">Index</a>]</p>
+</div>
+<a name="Version"></a>
+<h1 class="top">Version</h1>
 
-   <p>Copyright &copy; 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
+<p>Information for maintainers of GNU software, last updated September 5, 2011.
+</p>
+<p>Copyright &copy; 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
 2010, 2011 Free Software Foundation, Inc.
-
-   <blockquote>
-Permission is granted to copy, distribute and/or modify this document
+</p>
+<blockquote>
+<p>Permission is granted to copy, distribute and/or modify this document
 under the terms of the GNU Free Documentation License, Version 1.3 or
 any later version published by the Free Software Foundation; with no
 Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
 Texts.  A copy of the license is included in the section entitled
 &ldquo;GNU Free Documentation License&rdquo;. 
-</blockquote>
+</p></blockquote>
 
-<ul class="menu">
-<li><a accesskey="1" href="#Preface">Preface</a>
-<li><a accesskey="2" href="#Getting-Help">Getting Help</a>
-<li><a accesskey="3" href="#Getting-a-GNU-Account">Getting a GNU Account</a>
-<li><a accesskey="4" href="#Stepping-Down">Stepping Down</a>
-<li><a accesskey="5" href="#Recruiting-Developers">Recruiting Developers</a>
-<li><a accesskey="6" href="#Legal-Matters">Legal Matters</a>
-<li><a accesskey="7" href="#Clean-Ups">Clean Ups</a>
-<li><a accesskey="8" href="#Platforms">Platforms</a>
-<li><a accesskey="9" href="#Mail">Mail</a>
-<li><a href="#Old-Versions">Old Versions</a>
-<li><a href="#Distributions">Distributions</a>
-<li><a href="#Web-Pages">Web Pages</a>
-<li><a href="#Ethical-and-Philosophical-Consideration">Ethical and 
Philosophical Consideration</a>
-<li><a href="#Terminology">Terminology</a>
-<li><a href="#Hosting">Hosting</a>
-<li><a href="#Donations">Donations</a>
-<li><a href="#Free-Software-Directory">Free Software Directory</a>
-<li><a href="#Using-the-Proofreaders-List">Using the Proofreaders List</a>
-<li><a href="#GNU-Free-Documentation-License">GNU Free Documentation 
License</a>
-<li><a href="#Index">Index</a>
-</ul>
 
-<div class="node">
-<a name="Preface"></a>
-<p><hr>
-Next:&nbsp;<a rel="next" accesskey="n" href="#Getting-Help">Getting Help</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" href="#Top">Top</a>,
-Up:&nbsp;<a rel="up" accesskey="u" href="#Top">Top</a>
+<table class="menu" border="0" cellspacing="0">
+<tr><td align="left" valign="top">&bull; <a href="#Preface" 
accesskey="1">Preface</a>:</td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a href="#Getting-Help" 
accesskey="2">Getting Help</a>:</td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a href="#Getting-a-GNU-Account" 
accesskey="3">Getting a GNU Account</a>:</td><td>&nbsp;&nbsp;</td><td 
align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a href="#Stepping-Down" 
accesskey="4">Stepping Down</a>:</td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a href="#Recruiting-Developers" 
accesskey="5">Recruiting Developers</a>:</td><td>&nbsp;&nbsp;</td><td 
align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a href="#Legal-Matters" 
accesskey="6">Legal Matters</a>:</td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a href="#Clean-Ups" 
accesskey="7">Clean Ups</a>:</td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a href="#Platforms" 
accesskey="8">Platforms</a>:</td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a href="#Mail" 
accesskey="9">Mail</a>:</td><td>&nbsp;&nbsp;</td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a href="#Old-Versions">Old 
Versions</a>:</td><td>&nbsp;&nbsp;</td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a 
href="#Distributions">Distributions</a>:</td><td>&nbsp;&nbsp;</td><td 
align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a href="#Web-Pages">Web 
Pages</a>:</td><td>&nbsp;&nbsp;</td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a 
href="#Ethical-and-Philosophical-Consideration">Ethical and Philosophical 
Consideration</a>:</td><td>&nbsp;&nbsp;</td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a 
href="#Terminology">Terminology</a>:</td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a 
href="#Hosting">Hosting</a>:</td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a 
href="#Donations">Donations</a>:</td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a 
href="#Free-Software-Directory">Free Software 
Directory</a>:</td><td>&nbsp;&nbsp;</td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a 
href="#Using-the-Proofreaders-List">Using the Proofreaders 
List</a>:</td><td>&nbsp;&nbsp;</td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a 
href="#GNU-Free-Documentation-License">GNU Free Documentation 
License</a>:</td><td>&nbsp;&nbsp;</td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a 
href="#Index">Index</a>:</td><td>&nbsp;&nbsp;</td><td align="left" valign="top">
+</td></tr>
+</table>
 
-</div>
 
-<h2 class="chapter">1 About This Document</h2>
+<hr>
+<a name="Preface"></a>
+<div class="header">
+<p>
+Next: <a href="#Getting-Help" accesskey="n" rel="next">Getting Help</a>, 
Previous: <a href="#Top" accesskey="p" rel="previous">Top</a>, Up: <a 
href="#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a href="#SEC_Contents" 
title="Table of contents" rel="contents">Contents</a>][<a href="#Index" 
title="Index" rel="index">Index</a>]</p>
+</div>
+<a name="About-This-Document"></a>
+<h1 class="chapter">1 About This Document</h1>
 
 <p>This file contains guidelines and advice for someone who is the
 maintainer of a GNU program on behalf of the GNU Project.  Everyone is
@@ -178,536 +219,555 @@
 a version for widespread distribution, we suggest you follow these
 guidelines.  If you are or would like to be a GNU maintainer, then it
 is essential to follow these guidelines.
-
-   <p>In addition to this document, please read and follow the GNU Coding
-Standards (see <a href="standards.html#Top">Contents</a>).
-
-   <p><a 
name="index-g_t_0040code_007bbug_002dstandards_0040_0040gnu_002eorg_007d-email-address-1"></a><a
 name="index-Savannah-repository-for-_0040code_007bgnustandards_007d-2"></a><a 
name="index-g_t_0040code_007bgnustandards_007d-project-repository-3"></a>Please 
send corrections or suggestions for this document to
+</p>
+<p>In addition to this document, please read and follow the GNU Coding
+Standards (see <a 
href="http://www.gnu.org/prep/standards/standards.html#Top";>Contents</a> in 
<cite>GNU Coding Standards</cite>).
+</p>
+<a name="index-bug_002dstandards_0040gnu_002eorg-email-address"></a>
+<a name="index-Savannah-repository-for-gnustandards"></a>
+<a name="index-gnustandards-project-repository"></a>
+<p>Please send corrections or suggestions for this document to
 <a href="mailto:address@hidden";>address@hidden</a>.  If you make a suggestion, 
please
 include suggested new wording if you can.  We prefer a context diff to
-the Texinfo source, but if that's difficult for you, you can make a
+the Texinfo source, but if that&rsquo;s difficult for you, you can make a
 diff for some other version of this document, or propose it in any way
 that makes it clear.  The source repository for this document can be
 found at <a 
href="http://savannah.gnu.org/projects/gnustandards";>http://savannah.gnu.org/projects/gnustandards</a>.
-
-   <p><a 
name="index-g_t_0040code_007bgnustandards_002dcommit_0040_0040gnu_002eorg_007d-mailing-list-4"></a>If
 you want to receive diffs for every change to these GNU documents,
+</p>
+<a name="index-gnustandards_002dcommit_0040gnu_002eorg-mailing-list"></a>
+<p>If you want to receive diffs for every change to these GNU documents,
 join the mailing list <code>address@hidden</code>, for
 instance via the web interface at
 <a 
href="http://lists.gnu.org/mailman/listinfo/gnustandards-commit";>http://lists.gnu.org/mailman/listinfo/gnustandards-commit</a>.
 
 Archives are also available there.
-
-   <p><a name="index-Piercy_002c-Marge-5"></a>This document uses the 
gender-neutral third-person pronouns &ldquo;person&rdquo;,
+</p>
+<a name="index-Piercy_002c-Marge"></a>
+<p>This document uses the gender-neutral third-person pronouns 
&ldquo;person&rdquo;,
 &ldquo;per&rdquo;, &ldquo;pers&rdquo; and &ldquo;perself&rdquo; which were 
promoted, and perhaps
 invented, by Marge Piercy in <cite>Woman on the Edge of Time</cite>.  They are
 used just like &ldquo;she&rdquo;, &ldquo;her&rdquo;, &ldquo;hers&rdquo; and 
&ldquo;herself&rdquo;, except that
 they apply equally to males and females.  For example, &ldquo;Person placed
 per new program under the GNU GPL, to let the public benefit from per
 work, and to enable per to feel person has done the right thing.&rdquo;
-
-   <p>This release of the GNU Maintainer Information was last updated
+</p>
+<p>This release of the GNU Maintainer Information was last updated
 September 5, 2011.
+</p>
 
-<div class="node">
+<hr>
 <a name="Getting-Help"></a>
-<p><hr>
-Next:&nbsp;<a rel="next" accesskey="n" href="#Getting-a-GNU-Account">Getting a 
GNU Account</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" href="#Preface">Preface</a>,
-Up:&nbsp;<a rel="up" accesskey="u" href="#Top">Top</a>
-
-</div>
-
-<h2 class="chapter">2 Getting Help</h2>
-
-<p><a name="index-help_002c-getting-6"></a>
-<a 
name="index-g_t_0040code_007bmentors_0040_0040gnu_002eorg_007d-mailing-list-7"></a>If
 you have any general questions or encounter a situation where it
-isn't clear how to get something done or who to ask, you (as a GNU
+<div class="header">
+<p>
+Next: <a href="#Getting-a-GNU-Account" accesskey="n" rel="next">Getting a GNU 
Account</a>, Previous: <a href="#Preface" accesskey="p" 
rel="previous">Preface</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> 
&nbsp; [<a href="#SEC_Contents" title="Table of contents" 
rel="contents">Contents</a>][<a href="#Index" title="Index" 
rel="index">Index</a>]</p>
+</div>
+<a name="Getting-Help-1"></a>
+<h1 class="chapter">2 Getting Help</h1>
+<a name="index-help_002c-getting"></a>
+
+<a name="index-mentors_0040gnu_002eorg-mailing-list"></a>
+<p>If you have any general questions or encounter a situation where it
+isn&rsquo;t clear how to get something done or who to ask, you (as a GNU
 contributor) can always write to <a 
href="mailto:address@hidden";>address@hidden</a>, which is a
 list of a few experienced GNU folks who have volunteered to answer
 questions.  Any GNU-related question is fair game for the
 <code>mentors</code> list.
-
-   <p><a name="index-advisory-committee-8"></a>The GNU Advisory Committee 
helps to coordinate activities in the GNU
+</p>
+<a name="index-advisory-committee"></a>
+<p>The GNU Advisory Committee helps to coordinate activities in the GNU
 project on behalf of RMS (Richard Stallman, the Chief GNUisance).  If
 you have any organizational questions or concerns you can contact the
 committee at <a href="mailto:address@hidden";>address@hidden</a>.  See
 <a 
href="http://www.gnu.org/contact/gnu-advisory.html";>http://www.gnu.org/contact/gnu-advisory.html</a>
 for the current
 committee members.  Additional information is in
-<samp><span class="file">/gd/gnuorg/advisory</span></samp>.
-
-   <p><a name="index-down_002c-when-GNU-machines-are-9"></a><a 
name="index-outage_002c-of-GNU-machines-10"></a><a 
name="index-g_t_0040url_007bhttp_003a_002f_002fidenti_002eca_002fgroup_002ffsfstatus_007d-11"></a>If
 you find that any GNU computer systems (<code>fencepost.gnu.org</code>,
+&lsquo;<tt>/gd/gnuorg/advisory</tt>&rsquo;.
+</p>
+<a name="index-down_002c-when-GNU-machines-are"></a>
+<a name="index-outage_002c-of-GNU-machines"></a>
+<a name="index-http_003a_002f_002fidenti_002eca_002fgroup_002ffsfstatus"></a>
+<p>If you find that any GNU computer systems (<code>fencepost.gnu.org</code>,
 <code>ftp.gnu.org</code>, <code>www.gnu.org</code>, 
<code>savannah.gnu.org</code>,
-<small class="dots">...</small>) seem to be down, you can check the current 
status at
+&hellip;) seem to be down, you can check the current status at
 <a 
href="http://identi.ca/group/fsfstatus";>http://identi.ca/group/fsfstatus</a>.  
Most likely the problem, if
 it can be alleviated at the FSF end, is already being worked on.
-
-   <p><a name="index-sysadmin_002c-FSF-12"></a><a 
name="index-FSF-system-administrators-13"></a><a 
name="index-GNU-system-administrators-14"></a>The FSF system administrators are 
responsible for the network and GNU
+</p>
+<a name="index-sysadmin_002c-FSF"></a>
+<a name="index-FSF-system-administrators"></a>
+<a name="index-GNU-system-administrators"></a>
+<p>The FSF system administrators are responsible for the network and GNU
 hardware.  You can email them at <a 
href="mailto:address@hidden";>address@hidden</a>, but please
 try not to burden them unnecessarily.
+</p>
 
-<div class="node">
+<hr>
 <a name="Getting-a-GNU-Account"></a>
-<p><hr>
-Next:&nbsp;<a rel="next" accesskey="n" href="#Stepping-Down">Stepping Down</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" href="#Getting-Help">Getting 
Help</a>,
-Up:&nbsp;<a rel="up" accesskey="u" href="#Top">Top</a>
-
+<div class="header">
+<p>
+Next: <a href="#Stepping-Down" accesskey="n" rel="next">Stepping Down</a>, 
Previous: <a href="#Getting-Help" accesskey="p" rel="previous">Getting 
Help</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a 
href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a 
href="#Index" title="Index" rel="index">Index</a>]</p>
 </div>
+<a name="Getting-a-GNU-Account-1"></a>
+<h1 class="chapter">3 Getting a GNU Account</h1>
+<a name="index-shell-account_002c-on-fencepost"></a>
+<a name="index-fencepost_002egnu_002eorg-GNU-machine"></a>
 
-<h2 class="chapter">3 Getting a GNU Account</h2>
-
-<p><a name="index-shell-account_002c-on-fencepost-15"></a><a 
name="index-g_t_0040code_007bfencepost_002egnu_002eorg_007d-GNU-machine-16"></a>
-<!-- We want to repeat this text later, so define a macro. -->
 
-   <p>The directory <samp><span class="file">/gd/gnuorg</span></samp> 
mentioned throughout this document is
+<p>The directory &lsquo;<tt>/gd/gnuorg</tt>&rsquo; mentioned throughout this 
document is
 available on the general GNU server, currently
 <code>fencepost.gnu.org</code>.  If you are the maintainer of a GNU package,
-you should have an account there.  If you don't have one already,
+you should have an account there.  If you don&rsquo;t have one already,
 <a 
href="http://www.gnu.org/software/README.accounts.html";>http://www.gnu.org/software/README.accounts.html</a>.
  You can also
 ask for accounts for people who significantly help you in working on
 the package.
+</p>
 
-<div class="node">
+<hr>
 <a name="Stepping-Down"></a>
-<p><hr>
-Next:&nbsp;<a rel="next" accesskey="n" 
href="#Recruiting-Developers">Recruiting Developers</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" 
href="#Getting-a-GNU-Account">Getting a GNU Account</a>,
-Up:&nbsp;<a rel="up" accesskey="u" href="#Top">Top</a>
-
-</div>
+<div class="header">
+<p>
+Next: <a href="#Recruiting-Developers" accesskey="n" rel="next">Recruiting 
Developers</a>, Previous: <a href="#Getting-a-GNU-Account" accesskey="p" 
rel="previous">Getting a GNU Account</a>, Up: <a href="#Top" accesskey="u" 
rel="up">Top</a> &nbsp; [<a href="#SEC_Contents" title="Table of contents" 
rel="contents">Contents</a>][<a href="#Index" title="Index" 
rel="index">Index</a>]</p>
+</div>
+<a name="Stepping-Down-1"></a>
+<h1 class="chapter">4 Stepping Down</h1>
+<a name="index-stepping-down-as-maintainer"></a>
+<a name="index-resigning-as-maintainer"></a>
 
-<h2 class="chapter">4 Stepping Down</h2>
-
-<p><a name="index-stepping-down-as-maintainer-17"></a><a 
name="index-resigning-as-maintainer-18"></a>
-With good fortune, you will continue maintaining your package for many
+<p>With good fortune, you will continue maintaining your package for many
 decades.  But sometimes for various reasons maintainers decide to step
 down.
-
-   <p>If you're the official maintainer of a GNU package and you decide to
+</p>
+<p>If you&rsquo;re the official maintainer of a GNU package and you decide to
 step down, please inform the GNU Project (<a 
href="mailto:address@hidden";>address@hidden</a>). 
 We need to know that the package no longer has a maintainer, so we can
 look for and appoint a new maintainer.
-
-   <p><a 
name="index-g_t_0040email_007bmaintainers_0040_0040gnu_002eorg_007d-19"></a>If 
you have an idea for who should take over, please tell
+</p>
+<a name="index-maintainers_0040gnu_002eorg"></a>
+<p>If you have an idea for who should take over, please tell
 <a href="mailto:address@hidden";>address@hidden</a> your suggestion.  The 
appointment of a new
-maintainer needs the GNU Project's confirmation, but your judgment that
+maintainer needs the GNU Project&rsquo;s confirmation, but your judgment that
 a person is capable of doing the job will carry a lot of weight.
-
-   <p>As your final act as maintainer, it would be helpful to set up or
-update the package under <code>savannah.gnu.org</code> (see <a 
href="#Old-Versions">Old Versions</a>).  This will make it much easier for the 
new maintainer to
+</p>
+<p>As your final act as maintainer, it would be helpful to set up or
+update the package under <code>savannah.gnu.org</code> (see <a 
href="#Old-Versions">Old
+Versions</a>).  This will make it much easier for the new maintainer to
 pick up where you left off and will ensure that the source tree is not
 misplaced if it takes us a while to find a new maintainer.
+</p>
 
-<div class="node">
+<hr>
 <a name="Recruiting-Developers"></a>
-<p><hr>
-Next:&nbsp;<a rel="next" accesskey="n" href="#Legal-Matters">Legal Matters</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" href="#Stepping-Down">Stepping 
Down</a>,
-Up:&nbsp;<a rel="up" accesskey="u" href="#Top">Top</a>
-
+<div class="header">
+<p>
+Next: <a href="#Legal-Matters" accesskey="n" rel="next">Legal Matters</a>, 
Previous: <a href="#Stepping-Down" accesskey="p" rel="previous">Stepping 
Down</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a 
href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a 
href="#Index" title="Index" rel="index">Index</a>]</p>
 </div>
+<a name="Recruiting-Developers-1"></a>
+<h1 class="chapter">5 Recruiting Developers</h1>
 
-<h2 class="chapter">5 Recruiting Developers</h2>
-
-<p>Unless your package is a fairly small, you probably won't do all the
+<p>Unless your package is a fairly small, you probably won&rsquo;t do all the
 work on it yourself.  Most maintainers recruit other developers to help.
-
-   <p>Sometimes people will offer to help.  Some of them will be capable,
-while others will not.  It's up to you to determine who provides useful
+</p>
+<p>Sometimes people will offer to help.  Some of them will be capable,
+while others will not.  It&rsquo;s up to you to determine who provides useful
 help, and encourage those people to participate more.
-
-   <p>Some of the people who offer to help will support the GNU Project, while
+</p>
+<p>Some of the people who offer to help will support the GNU Project, while
 others may be interested for other reasons.  Some will support the goals
 of the Free Software Movement, but some may not.  They are all welcome
-to help with the work&mdash;we don't ask people's views or motivations
+to help with the work&mdash;we don&rsquo;t ask people&rsquo;s views or 
motivations
 before they contribute to GNU packages.
-
-   <p>As a consequence, you cannot expect all contributors to support the GNU
+</p>
+<p>As a consequence, you cannot expect all contributors to support the GNU
 Project, or to have a concern for its policies and standards.  So part
 of your job as maintainer is to exercise your authority on these points
 when they arise.  No matter how much of the work other people do, you
 are in charge of what goes in the release.  When a crucial point arises,
 you should calmly state your decision and stick to it.
-
-   <p>Sometimes a package has several co-maintainers who share the role of
+</p>
+<p>Sometimes a package has several co-maintainers who share the role of
 maintainer.  Unlike developers who help, co-maintainers have actually
 been appointed jointly as the maintainers of the package, and they carry
-out the maintainer's functions together.  If you would like to propose
+out the maintainer&rsquo;s functions together.  If you would like to propose
 some of your developers as co-maintainers, please contact
 <a href="mailto:address@hidden";>address@hidden</a>.
-
-   <p>We're happy to acknowledge all major contributors to GNU packages on
+</p>
+<p>We&rsquo;re happy to acknowledge all major contributors to GNU packages on
 the <a 
href="http://www.gnu.org/people/people.html";>http://www.gnu.org/people/people.html</a>
 web page.  Please send
 an entry for yourself to <a href="mailto:address@hidden";>address@hidden</a>, 
and feel free to
 suggest it to other significant developers on your package.
+</p>
 
-<div class="node">
+<hr>
 <a name="Legal-Matters"></a>
-<p><hr>
-Next:&nbsp;<a rel="next" accesskey="n" href="#Clean-Ups">Clean Ups</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" 
href="#Recruiting-Developers">Recruiting Developers</a>,
-Up:&nbsp;<a rel="up" accesskey="u" href="#Top">Top</a>
+<div class="header">
+<p>
+Next: <a href="#Clean-Ups" accesskey="n" rel="next">Clean Ups</a>, Previous: 
<a href="#Recruiting-Developers" accesskey="p" rel="previous">Recruiting 
Developers</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a 
href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a 
href="#Index" title="Index" rel="index">Index</a>]</p>
+</div>
+<a name="Legal-Matters-1"></a>
+<h1 class="chapter">6 Legal Matters</h1>
+<a name="index-legal-matters"></a>
 
-</div>
-
-<h2 class="chapter">6 Legal Matters</h2>
-
-<p><a name="index-legal-matters-20"></a>
-This chapter describes procedures you should follow for legal reasons
+<p>This chapter describes procedures you should follow for legal reasons
 as you maintain the program, to avoid legal difficulties.
+</p>
+<table class="menu" border="0" cellspacing="0">
+<tr><td align="left" valign="top">&bull; <a href="#Copyright-Papers" 
accesskey="1">Copyright Papers</a>:</td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a href="#Legally-Significant" 
accesskey="2">Legally Significant</a>:</td><td>&nbsp;&nbsp;</td><td 
align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a href="#Recording-Contributors" 
accesskey="3">Recording Contributors</a>:</td><td>&nbsp;&nbsp;</td><td 
align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a 
href="#Copying-from-Other-Packages" accesskey="4">Copying from Other 
Packages</a>:</td><td>&nbsp;&nbsp;</td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a href="#Copyright-Notices" 
accesskey="5">Copyright Notices</a>:</td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a href="#License-Notices" 
accesskey="6">License Notices</a>:</td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a href="#External-Libraries" 
accesskey="7">External Libraries</a>:</td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">
+</td></tr>
+</table>
 
-<ul class="menu">
-<li><a accesskey="1" href="#Copyright-Papers">Copyright Papers</a>
-<li><a accesskey="2" href="#Legally-Significant">Legally Significant</a>
-<li><a accesskey="3" href="#Recording-Contributors">Recording Contributors</a>
-<li><a accesskey="4" href="#Copying-from-Other-Packages">Copying from Other 
Packages</a>
-<li><a accesskey="5" href="#Copyright-Notices">Copyright Notices</a>
-<li><a accesskey="6" href="#License-Notices">License Notices</a>
-<li><a accesskey="7" href="#External-Libraries">External Libraries</a>
-</ul>
-
-<div class="node">
+<hr>
 <a name="Copyright-Papers"></a>
-<p><hr>
-Next:&nbsp;<a rel="next" accesskey="n" href="#Legally-Significant">Legally 
Significant</a>,
-Up:&nbsp;<a rel="up" accesskey="u" href="#Legal-Matters">Legal Matters</a>
-
-</div>
-
-<h3 class="section">6.1 Copyright Papers</h3>
+<div class="header">
+<p>
+Next: <a href="#Legally-Significant" accesskey="n" rel="next">Legally 
Significant</a>, Up: <a href="#Legal-Matters" accesskey="u" rel="up">Legal 
Matters</a> &nbsp; [<a href="#SEC_Contents" title="Table of contents" 
rel="contents">Contents</a>][<a href="#Index" title="Index" 
rel="index">Index</a>]</p>
+</div>
+<a name="Copyright-Papers-1"></a>
+<h2 class="section">6.1 Copyright Papers</h2>
+<a name="index-copyright-papers"></a>
 
-<p><a name="index-copyright-papers-21"></a>
-If you maintain an FSF-copyrighted package
+<p>If you maintain an FSF-copyrighted package
 certain legal procedures are required when incorporating legally significant
 changes written by other people.  This ensures that the FSF has the
 legal right to distribute the package, and the standing to defend its
 GPL-covered status in court if necessary.
-
-   <p><strong>Before</strong> incorporating significant changes, make sure 
that the
+</p>
+<p><strong>Before</strong> incorporating significant changes, make sure that 
the
 person who wrote the changes has signed copyright papers and that the
 Free Software Foundation has received and signed them.  We may also need
-an employer's disclaimer from the person's employer.
-
-   <p><a name="index-data-base-of-GNU-copyright-assignments-22"></a>To check 
whether papers have been received, look in
-<samp><span class="file">/gd/gnuorg/copyright.list</span></samp>.  If you 
can't look there directly,
+an employer&rsquo;s disclaimer from the person&rsquo;s employer.
+</p>
+<a name="index-data-base-of-GNU-copyright-assignments"></a>
+<p>To check whether papers have been received, look in
+&lsquo;<tt>/gd/gnuorg/copyright.list</tt>&rsquo;.  If you can&rsquo;t look 
there directly,
 <a href="mailto:address@hidden";>address@hidden</a> can check for you.  Our 
clerk can also
 check for papers that are waiting to be entered and inform you when
 expected papers arrive.
-
-   <p><a 
name="index-g_t_0040file_007b_002fgd_002fgnuorg_007d-directory-23"></a><!-- 
This paragraph intentionally duplicates information given -->
-<!-- near the beginning of the file-to make sure people don't miss it. -->
-The directory <samp><span class="file">/gd/gnuorg</span></samp> mentioned 
throughout this document is
+</p>
+<a name="index-_002fgd_002fgnuorg-directory"></a>
+<p>The directory &lsquo;<tt>/gd/gnuorg</tt>&rsquo; mentioned throughout this 
document is
 available on the general GNU server, currently
 <code>fencepost.gnu.org</code>.  If you are the maintainer of a GNU package,
-you should have an account there.  If you don't have one already,
+you should have an account there.  If you don&rsquo;t have one already,
 <a 
href="http://www.gnu.org/software/README.accounts.html";>http://www.gnu.org/software/README.accounts.html</a>.
  You can also
 ask for accounts for people who significantly help you in working on
 the package.
-
-   <p>In order for the contributor to know person should sign papers, you need
-to ask per for the necessary papers.  If you don't know per well, and you
-don't know that person is used to our ways of handling copyright papers,
+</p>
+<p>In order for the contributor to know person should sign papers, you need
+to ask per for the necessary papers.  If you don&rsquo;t know per well, and you
+don&rsquo;t know that person is used to our ways of handling copyright papers,
 then it might be a good idea to raise the subject with a message like
 this:
-
-   <blockquote>
-Would you be willing to assign the copyright to the Free Software
+</p>
+<blockquote>
+<p>Would you be willing to assign the copyright to the Free Software
 Foundation, so that we could install it in <var>package</var>? 
-</blockquote>
-
-<p class="noindent">or
+</p></blockquote>
 
-   <blockquote>
-Would you be willing to sign a copyright disclaimer to put this change
+<p>or
+</p>
+<blockquote>
+<p>Would you be willing to sign a copyright disclaimer to put this change
 in the public domain, so that we can install it in <var>package</var>? 
-</blockquote>
+</p></blockquote>
 
-   <p>If the contributor then wants more information, you can send per the file
-<samp><span class="file">/gd/gnuorg/conditions.text</span></samp>, which 
explains per options (assign
+<p>If the contributor then wants more information, you can send per the file
+&lsquo;<tt>/gd/gnuorg/conditions.text</tt>&rsquo;, which explains per options 
(assign
 vs. disclaim) and their consequences.
-
-   <p>Once the conversation is under way and the contributor is ready for
+</p>
+<p>Once the conversation is under way and the contributor is ready for
 more details, you should send one of the templates that are found in
-the directory <samp><span class="file">/gd/gnuorg/Copyright/</span></samp>; 
they are also available
-from the <samp><span class="file">doc/Copyright/</span></samp> directory of 
the <code>gnulib</code> project
+the directory &lsquo;<tt>/gd/gnuorg/Copyright/</tt>&rsquo;; they are also 
available
+from the &lsquo;<tt>doc/Copyright/</tt>&rsquo; directory of the 
<code>gnulib</code> project
 at <a 
href="http://savannah.gnu.org/projects/gnulib";>http://savannah.gnu.org/projects/gnulib</a>.
  This section
 explains which templates you should use in which circumstances. 
-<strong>Please don't use any of the templates except for those listed
-here, and please don't change the wording.</strong>
-
-   <p>Once the conversation is under way, you can send the contributor the
+<strong>Please don&rsquo;t use any of the templates except for those listed
+here, and please don&rsquo;t change the wording.</strong>
+</p>
+<p>Once the conversation is under way, you can send the contributor the
 precise wording and instructions by email.  Before you do this, make
 sure to get the current version of the template you will use!  We change
-these templates occasionally&mdash;don't keep using an old version.
-
-   <p>For large changes, ask the contributor for an assignment.  Send per a
-copy of the file <samp><span 
class="file">request-assign.changes</span></samp>.  (Like all the
-&lsquo;<samp><span class="samp">request-</span></samp>&rsquo; files, it is in 
<samp><span class="file">/gd/gnuorg/Copyright</span></samp> and in
+these templates occasionally&mdash;don&rsquo;t keep using an old version.
+</p>
+<p>For large changes, ask the contributor for an assignment.  Send per a
+copy of the file &lsquo;<tt>request-assign.changes</tt>&rsquo;.  (Like all the
+&lsquo;<samp>request-</samp>&rsquo; files, it is in 
&lsquo;<tt>/gd/gnuorg/Copyright</tt>&rsquo; and in
 <code>gnulib</code>.)
-
-   <p>For medium to small changes, request a personal disclaimer by sending
-per the file <samp><span class="file">request-disclaim.changes</span></samp>.
-
-   <p>If the contributor is likely to keep making changes, person might want
+</p>
+<p>For medium to small changes, request a personal disclaimer by sending
+per the file &lsquo;<tt>request-disclaim.changes</tt>&rsquo;.
+</p>
+<p>If the contributor is likely to keep making changes, person might want
 to sign an assignment for all per future changes to the program.  So it
 is useful to offer per that alternative.  If person wants to do it that
-way, send per the <samp><span class="file">request-assign.future</span></samp>.
-
-   <p>When you send a <samp><span class="file">request-</span></samp> file, 
you don't need to fill in anything
+way, send per the &lsquo;<tt>request-assign.future</tt>&rsquo;.
+</p>
+<p>When you send a &lsquo;<tt>request-</tt>&rsquo; file, you don&rsquo;t need 
to fill in anything
 before sending it.  Just send the file verbatim to the contributor.  The
 file gives per instructions for how to ask the FSF to mail per the
-papers to sign.  The <samp><span class="file">request-</span></samp> file also 
raises the issue of
-getting an employer's disclaimer from the contributor's employer.
-
-   <p>When the contributor emails the form to the FSF, the FSF sends per
+papers to sign.  The &lsquo;<tt>request-</tt>&rsquo; file also raises the 
issue of
+getting an employer&rsquo;s disclaimer from the contributor&rsquo;s employer.
+</p>
+<p>When the contributor emails the form to the FSF, the FSF sends per
 papers to sign.  If person signs them right away, the whole process
 takes a couple of weeks&mdash;mostly waiting for letters to go back and
 forth.
-
-   <p>For less common cases, we have template files you should send to the
+</p>
+<p>For less common cases, we have template files you should send to the
 contributor.  Be sure to fill in the name of the person and the name
-of the program in these templates, where it says &lsquo;<samp><span 
class="samp">NAME OF PERSON</span></samp>&rsquo;
-and &lsquo;<samp><span class="samp">NAME OF PROGRAM</span></samp>&rsquo;, 
before sending; otherwise person might
+of the program in these templates, where it says &lsquo;<samp>NAME OF 
PERSON</samp>&rsquo;
+and &lsquo;<samp>NAME OF PROGRAM</samp>&rsquo;, before sending; otherwise 
person might
 sign without noticing them, and the papers would be useless.  Note
 that in some templates there is more than one place to put the name of
 the program or the name of the person; be sure to change all of them. 
-All the templates raise the issue of an employer's disclaimer as well.
-
-   <p><a name="index-legal-papers-for-changes-in-manuals-24"></a>You do not 
need to ask for separate papers for a manual that is
+All the templates raise the issue of an employer&rsquo;s disclaimer as well.
+</p>
+<a name="index-legal-papers-for-changes-in-manuals"></a>
+<p>You do not need to ask for separate papers for a manual that is
 distributed only in the software package it describes.  But if we
 sometimes distribute the manual separately (for instance, if we publish
 it as a book), then we need separate legal papers for changes in the
 manual.  For smaller changes, use
-<samp><span class="file">disclaim.changes.manual</span></samp>; for larger 
ones, use
-<samp><span class="file">assign.changes.manual</span></samp>.  To cover both 
past and future
-changes to a manual, you can use <samp><span 
class="file">assign.future.manual</span></samp>. 
-For a translation of a manual, use <samp><span 
class="file">assign.translation.manual</span></samp>.
-
-   <p>For translations of program strings (as used by GNU Gettext, for
-example; see <a 
href="standards.html#Internationalization">Internationalization</a>), use 
<samp><span class="file">disclaim.translation</span></samp>.  If you make use 
of the
+&lsquo;<tt>disclaim.changes.manual</tt>&rsquo;; for larger ones, use
+&lsquo;<tt>assign.changes.manual</tt>&rsquo;.  To cover both past and future
+changes to a manual, you can use &lsquo;<tt>assign.future.manual</tt>&rsquo;.
+For a translation of a manual, use 
&lsquo;<tt>assign.translation.manual</tt>&rsquo;.
+</p>
+<p>For translations of program strings (as used by GNU Gettext, for
+example; see <a 
href="http://www.gnu.org/prep/standards/standards.html#Internationalization";>Internationalization</a>
 in <cite>GNU Coding
+Standards</cite>), use &lsquo;<tt>disclaim.translation</tt>&rsquo;.  If you 
make use of the
 Translation Project (<a 
href="http://translationproject.org";>http://translationproject.org</a>) 
facilities,
 please check with the TP coordinators that they have sent the
-contributor the papers; if they haven't, then you should send the
+contributor the papers; if they haven&rsquo;t, then you should send the
 papers.  In any case, you should wait for the confirmation from the
 FSF that the signed papers have been received and accepted before
-integrating the new contributor's material, as usual.
-
-   <p>If a contributor is reluctant to sign an assignment for a large change,
+integrating the new contributor&rsquo;s material, as usual.
+</p>
+<p>If a contributor is reluctant to sign an assignment for a large change,
 and is willing to sign a disclaimer instead, that is acceptable, so you
 should offer this alternative if it helps you reach agreement.  We
 prefer an assignment for a larger change, so that we can enforce the GNU
 GPL for the new text, but a disclaimer is enough to let us use the text.
-
-   <p>If you maintain a collection of programs, occasionally someone will
+</p>
+<p>If you maintain a collection of programs, occasionally someone will
 contribute an entire separate program or manual that should be added to
 the collection.  Then you can use the files
-<samp><span class="file">request-assign.program</span></samp>, <samp><span 
class="file">disclaim.program</span></samp>,
-<samp><span class="file">assign.manual</span></samp>, and <samp><span 
class="file">disclaim.manual</span></samp>.  We very much prefer
+&lsquo;<tt>request-assign.program</tt>&rsquo;, 
&lsquo;<tt>disclaim.program</tt>&rsquo;,
+&lsquo;<tt>assign.manual</tt>&rsquo;, and 
&lsquo;<tt>disclaim.manual</tt>&rsquo;.  We very much prefer
 an assignment for a new separate program or manual, unless it is quite
 small, but a disclaimer is acceptable if the contributor insists on
 handling the matter that way.
-
-   <p>If a contributor wants the FSF to publish only a pseudonym, that is
+</p>
+<p>If a contributor wants the FSF to publish only a pseudonym, that is
 ok.  The contributor should say this, and state the desired pseudonym,
-when answering the <samp><span class="file">request-</span></samp> form.  The 
actual legal papers will
+when answering the &lsquo;<tt>request-</tt>&rsquo; form.  The actual legal 
papers will
 use the real name, but the FSF will publish only the pseudonym.  When
 using one of the other forms, fill in the real name but ask the
 contributor to discuss the use of a pseudonym with
 <a href="mailto:address@hidden";>address@hidden</a> before sending back the 
signed form.
-
-   <p><strong>Although there are other templates besides the ones listed here,
+</p>
+<p><strong>Although there are other templates besides the ones listed here,
 they are for special circumstances; please do not use them without
 getting advice from <a 
href="mailto:address@hidden";>address@hidden</a>.</strong>
-
-   <p>If you are not sure what to do, then please ask <a 
href="mailto:address@hidden";>address@hidden</a> for
+</p>
+<p>If you are not sure what to do, then please ask <a 
href="mailto:address@hidden";>address@hidden</a> for
 advice; if the contributor asks you questions about the meaning and
-consequences of the legal papers, and you don't know the answers, you
+consequences of the legal papers, and you don&rsquo;t know the answers, you
 can forward them to <a href="mailto:address@hidden";>address@hidden</a> and we 
will answer.
-
-   <p><strong>Please do not try changing the wording of a template yourself. 
+</p>
+<p><strong>Please do not try changing the wording of a template yourself.
 If you think a change is needed, please talk with <a 
href="mailto:address@hidden";>address@hidden</a>,
 and we will work with a lawyer to decide what to do.</strong>
-
-<div class="node">
+</p>
+<hr>
 <a name="Legally-Significant"></a>
-<p><hr>
-Next:&nbsp;<a rel="next" accesskey="n" 
href="#Recording-Contributors">Recording Contributors</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" 
href="#Copyright-Papers">Copyright Papers</a>,
-Up:&nbsp;<a rel="up" accesskey="u" href="#Legal-Matters">Legal Matters</a>
-
+<div class="header">
+<p>
+Next: <a href="#Recording-Contributors" accesskey="n" rel="next">Recording 
Contributors</a>, Previous: <a href="#Copyright-Papers" accesskey="p" 
rel="previous">Copyright Papers</a>, Up: <a href="#Legal-Matters" accesskey="u" 
rel="up">Legal Matters</a> &nbsp; [<a href="#SEC_Contents" title="Table of 
contents" rel="contents">Contents</a>][<a href="#Index" title="Index" 
rel="index">Index</a>]</p>
 </div>
-
-<h3 class="section">6.2 Legally Significant Changes</h3>
+<a name="Legally-Significant-Changes"></a>
+<h2 class="section">6.2 Legally Significant Changes</h2>
 
 <p>If a person contributes more than around 15 lines of code and/or text
 that is legally significant for copyright purposes, we
 need copyright papers for that contribution, as described above.
-
-   <p>A change of just a few lines (less than 15 or so) is not legally
+</p>
+<p>A change of just a few lines (less than 15 or so) is not legally
 significant for copyright.  A regular series of repeated changes, such
 as renaming a symbol, is not legally significant even if the symbol
 has to be renamed in many places.  Keep in mind, however, that a
 series of minor changes by the same person can add up to a significant
 contribution.  What counts is the total contribution of the person; it
 is irrelevant which parts of it were contributed when.
-
-   <p>Copyright does not cover ideas.  If someone contributes ideas but no
+</p>
+<p>Copyright does not cover ideas.  If someone contributes ideas but no
 text, these ideas may be morally significant as contributions, and
 worth giving credit for, but they are not significant for copyright
 purposes.  Likewise, bug reports do not count for copyright purposes.
-
-   <p>When giving credit to people whose contributions are not legally
+</p>
+<p>When giving credit to people whose contributions are not legally
 significant for copyright purposes, be careful to make that fact
 clear.  The credit should clearly say they did not contribute
 significant code or text.
-
-   <p>When people's contributions are not legally significant because they
+</p>
+<p>When people&rsquo;s contributions are not legally significant because they
 did not write code, do this by stating clearly what their contribution
 was.  For instance, you could write this:
-
-<pre class="example">     /*
+</p>
+<div class="example">
+<pre class="example">/*
       * Ideas by:
       *   Richard Mlynarik &lt;address@hidden&gt; (1997)
       *   Masatake Yamato &lt;address@hidden&gt; (1999)
       */
-</pre>
-   <p class="noindent"><code>Ideas by:</code> makes it clear that Mlynarik and 
Yamato here
+</pre></div>
+
+<p><code>Ideas by:</code> makes it clear that Mlynarik and Yamato here
 contributed only ideas, not code.  Without the <code>Ideas by:</code> note,
 several years from now we would find it hard to be sure whether they
 had contributed code, and we might have to track them down and ask
 them.
-
-   <p>When you record a small patch in a change log file, first search for
+</p>
+<p>When you record a small patch in a change log file, first search for
 previous changes by the same person, and see if per past
 contributions, plus the new one, add up to something legally
 significant.  If so, you should get copyright papers for all per
 changes before you install the new change.
+</p>
+<p>If that is not so, you can install the small patch.  Write 
&lsquo;<samp>(tiny
+change)</samp>&rsquo; after the patch author&rsquo;s name, like this:
+</p>
+<div class="example">
+<pre class="example">2002-11-04  Robert Fenk  &lt;address@hidden&gt;  (tiny 
change)
+</pre></div>
 
-   <p>If that is not so, you can install the small patch.  Write 
&lsquo;<samp><span class="samp">(tiny
-change)</span></samp>&rsquo; after the patch author's name, like this:
-
-<pre class="example">     2002-11-04  Robert Fenk  &lt;address@hidden&gt;  
(tiny change)
-</pre>
-   <div class="node">
+<hr>
 <a name="Recording-Contributors"></a>
-<p><hr>
-Next:&nbsp;<a rel="next" accesskey="n" 
href="#Copying-from-Other-Packages">Copying from Other Packages</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" 
href="#Legally-Significant">Legally Significant</a>,
-Up:&nbsp;<a rel="up" accesskey="u" href="#Legal-Matters">Legal Matters</a>
-
-</div>
-
-<h3 class="section">6.3 Recording Contributors</h3>
+<div class="header">
+<p>
+Next: <a href="#Copying-from-Other-Packages" accesskey="n" rel="next">Copying 
from Other Packages</a>, Previous: <a href="#Legally-Significant" accesskey="p" 
rel="previous">Legally Significant</a>, Up: <a href="#Legal-Matters" 
accesskey="u" rel="up">Legal Matters</a> &nbsp; [<a href="#SEC_Contents" 
title="Table of contents" rel="contents">Contents</a>][<a href="#Index" 
title="Index" rel="index">Index</a>]</p>
+</div>
+<a name="Recording-Contributors-1"></a>
+<h2 class="section">6.3 Recording Contributors</h2>
+<a name="index-recording-contributors"></a>
 
-<p><a name="index-recording-contributors-25"></a>
-<strong>Keep correct records of which portions were written by whom.</strong>
+<p><strong>Keep correct records of which portions were written by 
whom.</strong>
 This is very important.  These records should say which files or
 parts of files were written by each person, and which files or
 parts of files were revised by each person.  This should include
 installation scripts as well as manuals and documentation
 files&mdash;everything.
-
-   <p>These records don't need to be as detailed as a change log.  They
-don't need to distinguish work done at different times, only different
-people.  They don't need describe changes in more detail than which
-files or parts of a file were changed.  And they don't need to say
+</p>
+<p>These records don&rsquo;t need to be as detailed as a change log.  They
+don&rsquo;t need to distinguish work done at different times, only different
+people.  They don&rsquo;t need describe changes in more detail than which
+files or parts of a file were changed.  And they don&rsquo;t need to say
 anything about the function or purpose of a file or change&mdash;the
-Register of Copyrights doesn't care what the text does, just who wrote
+Register of Copyrights doesn&rsquo;t care what the text does, just who wrote
 or contributed to which parts.
-
-   <p>The list should also mention if certain files distributed in the same
+</p>
+<p>The list should also mention if certain files distributed in the same
 package are really a separate program.
-
-   <p>Only the contributions that are legally significant for copyright
+</p>
+<p>Only the contributions that are legally significant for copyright
 purposes (see <a href="#Legally-Significant">Legally Significant</a>) need to 
be listed.  Small
 contributions, bug reports, ideas, etc., can be omitted.
-
-   <p>For example, this would describe an early version of GAS:
-
-<pre class="display">     Dean Elsner   first version of all files except 
gdb-lines.c and m68k.c.
-     Jay Fenlason  entire files gdb-lines.c and m68k.c, most of app.c,
+</p>
+<p>For example, this would describe an early version of GAS:
+</p>
+<div class="display">
+<pre class="display">Dean Elsner   first version of all files except 
gdb-lines.c and m68k.c.
+Jay Fenlason  entire files gdb-lines.c and m68k.c, most of app.c,
                    plus extensive changes in messages.c, input-file.c, write.c
                    and revisions elsewhere.
      
-     Note: GAS is distributed with the files obstack.c and obstack.h, but
-     they are considered a separate package, not part of GAS proper.
-</pre>
-   <p><a name="index-g_t_0040file_007bAUTHORS_007d-file-26"></a>Please keep 
these records in a file named <samp><span class="file">AUTHORS</span></samp> in 
the source
-directory for the program itself.
+Note: GAS is distributed with the files obstack.c and obstack.h, but
+they are considered a separate package, not part of GAS proper.
+</pre></div>
 
-   <p>You can use the change log as the basis for these records, if you
+<a name="index-AUTHORS-file"></a>
+<p>Please keep these records in a file named &lsquo;<tt>AUTHORS</tt>&rsquo; in 
the source
+directory for the program itself.
+</p>
+<p>You can use the change log as the basis for these records, if you
 wish.  Just make sure to record the correct author for each change
 (the person who wrote the change, <em>not</em> the person who installed
-it), and add &lsquo;<samp><span class="samp">(tiny 
change)</span></samp>&rsquo; for those changes that are too
+it), and add &lsquo;<samp>(tiny change)</samp>&rsquo; for those changes that 
are too
 trivial to matter for copyright purposes.  Later on you can update the
-<samp><span class="file">AUTHORS</span></samp> file from the change log.  This 
can even be done
+&lsquo;<tt>AUTHORS</tt>&rsquo; file from the change log.  This can even be done
 automatically, if you are careful about the formatting of the change
 log entries.
-
-<div class="node">
+</p>
+<hr>
 <a name="Copying-from-Other-Packages"></a>
-<p><hr>
-Next:&nbsp;<a rel="next" accesskey="n" href="#Copyright-Notices">Copyright 
Notices</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" 
href="#Recording-Contributors">Recording Contributors</a>,
-Up:&nbsp;<a rel="up" accesskey="u" href="#Legal-Matters">Legal Matters</a>
-
+<div class="header">
+<p>
+Next: <a href="#Copyright-Notices" accesskey="n" rel="next">Copyright 
Notices</a>, Previous: <a href="#Recording-Contributors" accesskey="p" 
rel="previous">Recording Contributors</a>, Up: <a href="#Legal-Matters" 
accesskey="u" rel="up">Legal Matters</a> &nbsp; [<a href="#SEC_Contents" 
title="Table of contents" rel="contents">Contents</a>][<a href="#Index" 
title="Index" rel="index">Index</a>]</p>
 </div>
-
-<h3 class="section">6.4 Copying from Other Packages</h3>
+<a name="Copying-from-Other-Packages-1"></a>
+<h2 class="section">6.4 Copying from Other Packages</h2>
 
 <p>When you copy legally significant code from another free software
 package with a GPL-compatible license, you should look in the
-package's records to find out the authors of the part you are copying,
+package&rsquo;s records to find out the authors of the part you are copying,
 and list them as the contributors of the code that you copied.  If all
 you did was copy it, not write it, then for copyright purposes you are
 <em>not</em> one of the contributors of <em>this</em> code.
-
-   <p>Especially when code has been released into the public domain, authors
+</p>
+<p>Especially when code has been released into the public domain, authors
 sometimes fail to write a license statement in each file.  In this
 case, please first be sure that all the authors of the code have
 disclaimed copyright interest.  Then, when copying the new files into
 your project, add a brief note at the beginning of the files recording
 the authors, the public domain status, and anything else relevant.
-
-   <p>On the other hand, when merging some public domain code into an
+</p>
+<p>On the other hand, when merging some public domain code into an
 existing file covered by the GPL (or LGPL or other free software
 license), there is no reason to indicate the pieces which are public
 domain.  The notice saying that the whole file is under the GPL (or
 other license) is legally sufficient.
-
-   <p>Using code that is released under a GPL-compatible free license,
+</p>
+<p>Using code that is released under a GPL-compatible free license,
 rather than being in the public domain, may require preserving
 copyright notices or other steps.  Of course, you should do what is
 needed.
-
-   <p>If you are maintaining an FSF-copyrighted package, please verify we
+</p>
+<p>If you are maintaining an FSF-copyrighted package, please verify we
 have papers for the code you are copying, <em>before</em> copying it. 
 If you are copying from another FSF-copyrighted package, then we
-presumably have papers for that package's own code, but you must check
+presumably have papers for that package&rsquo;s own code, but you must check
 whether the code you are copying is part of an external library; if
-that is the case, we don't have papers for it, so you should not copy
-it.  It can't hurt in any case to double-check with the developer of
+that is the case, we don&rsquo;t have papers for it, so you should not copy
+it.  It can&rsquo;t hurt in any case to double-check with the developer of
 that package.
-
-   <p>When you are copying code for which we do not already have papers, you
+</p>
+<p>When you are copying code for which we do not already have papers, you
 need to get papers for it.  It may be difficult to get the papers if
 the code was not written as a contribution to your package, but that
-doesn't mean it is ok to do without them.  If you cannot get papers
+doesn&rsquo;t mean it is ok to do without them.  If you cannot get papers
 for the code, you can only use it as an external library
 (see <a href="#External-Libraries">External Libraries</a>).
+</p>
 
-<div class="node">
+<hr>
 <a name="Copyright-Notices"></a>
-<p><hr>
-Next:&nbsp;<a rel="next" accesskey="n" href="#License-Notices">License 
Notices</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" 
href="#Copying-from-Other-Packages">Copying from Other Packages</a>,
-Up:&nbsp;<a rel="up" accesskey="u" href="#Legal-Matters">Legal Matters</a>
+<div class="header">
+<p>
+Next: <a href="#License-Notices" accesskey="n" rel="next">License Notices</a>, 
Previous: <a href="#Copying-from-Other-Packages" accesskey="p" 
rel="previous">Copying from Other Packages</a>, Up: <a href="#Legal-Matters" 
accesskey="u" rel="up">Legal Matters</a> &nbsp; [<a href="#SEC_Contents" 
title="Table of contents" rel="contents">Contents</a>][<a href="#Index" 
title="Index" rel="index">Index</a>]</p>
+</div>
+<a name="Copyright-Notices-1"></a>
+<h2 class="section">6.5 Copyright Notices</h2>
+<a name="index-copyright-notices-in-program-files"></a>
 
-</div>
-
-<h3 class="section">6.5 Copyright Notices</h3>
-
-<p><a name="index-copyright-notices-in-program-files-27"></a>
-You should maintain a proper copyright notice and a license
+<p>You should maintain a proper copyright notice and a license
 notice in each nontrivial file in the package.  (Any file more than ten
 lines long is nontrivial for this purpose.)  This includes header files
 and interface definitions for
@@ -715,146 +775,153 @@
 files.  If a file has been explicitly placed in the public domain, then
 instead of a copyright notice, it should have a notice saying explicitly
 that it is in the public domain.
-
-   <p>Even image files and sound files should contain copyright notices and
+</p>
+<p>Even image files and sound files should contain copyright notices and
 license notices, if their format permits.  Some formats do not have
 room for textual annotations; for these files, state the copyright and
-copying permissions in a <samp><span class="file">README</span></samp> file in 
the same directory.
-
-   <p>Change log files should have a copyright notice and license notice at
+copying permissions in a &lsquo;<tt>README</tt>&rsquo; file in the same 
directory.
+</p>
+<p>Change log files should have a copyright notice and license notice at
 the end, since new material is added at the beginning but the end
 remains the end.
-
-   <p>When a file is automatically generated from some other file in the
+</p>
+<p>When a file is automatically generated from some other file in the
 distribution, it is useful for the automatic procedure to copy the
 copyright notice and permission notice of the file it is generated
 from, if possible.  Alternatively, put a notice at the beginning saying
 which file it is generated from.
+</p>
+<p>A copyright notice looks like this:
+</p>
+<div class="example">
+<pre class="example">Copyright (C) <var>year1</var>, <var>year2</var>, 
<var>year3</var> <var>copyright-holder</var>
+</pre></div>
 
-   <p>A copyright notice looks like this:
-
-<pre class="example">     Copyright (C) <var>year1</var>, <var>year2</var>, 
<var>year3</var> <var>copyright-holder</var>
-</pre>
-   <p>The word &lsquo;<samp><span class="samp">Copyright</span></samp>&rsquo; 
must always be in English, by international
+<p>The word &lsquo;<samp>Copyright</samp>&rsquo; must always be in English, by 
international
 convention.
-
-   <p>The <var>copyright-holder</var> may be the Free Software Foundation, 
Inc., or
+</p>
+<p>The <var>copyright-holder</var> may be the Free Software Foundation, Inc., 
or
 someone else; you should know who is the copyright holder for your
 package.
-
-   <p>Replace the &lsquo;<samp><span class="samp">(C)</span></samp>&rsquo; 
with a C-in-a-circle symbol if it is available. 
-For example, use &lsquo;<samp><span 
class="samp">@copyright{}</span></samp>&rsquo; in a Texinfo file.  However,
-stick with parenthesized &lsquo;<samp><span 
class="samp">C</span></samp>&rsquo; unless you know that C-in-a-circle
-will work.  For example, a program's standard <samp><span 
class="option">--version</span></samp>
-message should use parenthesized &lsquo;<samp><span 
class="samp">C</span></samp>&rsquo; by default, though message
+</p>
+<p>Replace the &lsquo;<samp>(C)</samp>&rsquo; with a C-in-a-circle symbol if 
it is available.
+For example, use &lsquo;<samp>@copyright{}</samp>&rsquo; in a Texinfo file.  
However,
+stick with parenthesized &lsquo;<samp>C</samp>&rsquo; unless you know that 
C-in-a-circle
+will work.  For example, a program&rsquo;s standard 
&lsquo;<samp>--version</samp>&rsquo;
+message should use parenthesized &lsquo;<samp>C</samp>&rsquo; by default, 
though message
 translations may use C-in-a-circle in locales where that symbol is
-known to work.  Alternatively, the &lsquo;<samp><span 
class="samp">(C)</span></samp>&rsquo; or C-in-a-circle can be
-omitted entirely; the word &lsquo;<samp><span 
class="samp">Copyright</span></samp>&rsquo; suffices.
-
-   <p>To update the list of year numbers, add each year in which you have
-made nontrivial changes to the package.  (Here we assume you're using
+known to work.  Alternatively, the &lsquo;<samp>(C)</samp>&rsquo; or 
C-in-a-circle can be
+omitted entirely; the word &lsquo;<samp>Copyright</samp>&rsquo; suffices.
+</p>
+<p>To update the list of year numbers, add each year in which you have
+made nontrivial changes to the package.  (Here we assume you&rsquo;re using
 a publicly accessible revision control server, so that every revision
 installed is also immediately and automatically published.)  When you
 add the new year, it is not required to keep track of which files have
 seen significant changes in the new year and which have not.  It is
 recommended and simpler to add the new year to all files in the
 package, and be done with it for the rest of the year.
-
-   <p>Don't delete old year numbers, though; they are significant since they
+</p>
+<p>Don&rsquo;t delete old year numbers, though; they are significant since they
 indicate when older versions might theoretically go into the public
-domain, if the movie companies don't continue buying laws to further
+domain, if the movie companies don&rsquo;t continue buying laws to further
 extend copyright.  If you copy a file into the package from some other
 program, keep the copyright years that come with the file.
-
-   <p>You can use a range (&lsquo;<samp><span 
class="samp">2008-2010</span></samp>&rsquo;) instead of listing individual
-years (&lsquo;<samp><span class="samp">2008, 2009, 2010</span></samp>&rsquo;) 
if and only if: 1)&nbsp;every year in
+</p>
+<p>You can use a range (&lsquo;<samp>2008-2010</samp>&rsquo;) instead of 
listing individual
+years (&lsquo;<samp>2008, 2009, 2010</samp>&rsquo;) if and only if: 
1)&nbsp;every year in
 the range, inclusive, really is a &ldquo;copyrightable&rdquo; year that would 
be
 listed individually; <em>and</em> 2)&nbsp;you make an explicit statement
-in a <samp><span class="file">README</span></samp> file about this usage.
-
-   <p>For files which are regularly copied from another project (such as
-&lsquo;<samp><span class="samp">gnulib</span></samp>&rsquo;), leave the 
copyright notice as it is in the original.
-
-   <p>The copyright statement may be split across multiple lines, both in
+in a &lsquo;<tt>README</tt>&rsquo; file about this usage.
+</p>
+<p>For files which are regularly copied from another project (such as
+&lsquo;<samp>gnulib</samp>&rsquo;), leave the copyright notice as it is in the 
original.
+</p>
+<p>The copyright statement may be split across multiple lines, both in
 source files and in any generated output.  This often happens for
 files with a long history, having many different years of
 publication.
-
-   <p>For an FSF-copyrighted package, if you have followed the procedures to
+</p>
+<p>For an FSF-copyrighted package, if you have followed the procedures to
 obtain legal papers, each file should have just one copyright holder:
-the Free Software Foundation, Inc.  You should edit the file's
+the Free Software Foundation, Inc.  You should edit the file&rsquo;s
 copyright notice to list that name and only that name.
-
-   <p>But if contributors are not all assigning their copyrights to a single
+</p>
+<p>But if contributors are not all assigning their copyrights to a single
 copyright holder, it can easily happen that one file has several
 copyright holders.  Each contributor of nontrivial text is a copyright
 holder.
-
-   <p>In that case, you should always include a copyright notice in the name
+</p>
+<p>In that case, you should always include a copyright notice in the name
 of main copyright holder of the file.  You can also include copyright
 notices for other copyright holders as well, and this is a good idea
 for those who have contributed a large amount and for those who
 specifically ask for notices in their names.  (Sometimes the license
 on code that you copy in may require preserving certain copyright
-notices.)  But you don't have to include a notice for everyone who
+notices.)  But you don&rsquo;t have to include a notice for everyone who
 contributed to the file (which would be rather inconvenient).
-
-   <p>Sometimes a program has an overall copyright notice that refers to the
-whole program.  It might be in the <samp><span 
class="file">README</span></samp> file, or it might be
+</p>
+<p>Sometimes a program has an overall copyright notice that refers to the
+whole program.  It might be in the &lsquo;<tt>README</tt>&rsquo; file, or it 
might be
 displayed when the program starts up.  This copyright notice should
 mention the year of completion of the most recent major version; it
 can mention years of completion of previous major versions, but that
 is optional.
+</p>
 
-<div class="node">
+<hr>
 <a name="License-Notices"></a>
-<p><hr>
-Next:&nbsp;<a rel="next" accesskey="n" href="#External-Libraries">External 
Libraries</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" 
href="#Copyright-Notices">Copyright Notices</a>,
-Up:&nbsp;<a rel="up" accesskey="u" href="#Legal-Matters">Legal Matters</a>
-
-</div>
-
-<h3 class="section">6.6 License Notices</h3>
+<div class="header">
+<p>
+Next: <a href="#External-Libraries" accesskey="n" rel="next">External 
Libraries</a>, Previous: <a href="#Copyright-Notices" accesskey="p" 
rel="previous">Copyright Notices</a>, Up: <a href="#Legal-Matters" 
accesskey="u" rel="up">Legal Matters</a> &nbsp; [<a href="#SEC_Contents" 
title="Table of contents" rel="contents">Contents</a>][<a href="#Index" 
title="Index" rel="index">Index</a>]</p>
+</div>
+<a name="License-Notices-1"></a>
+<h2 class="section">6.6 License Notices</h2>
+<a name="index-license-notices-in-program-files"></a>
 
-<p><a name="index-license-notices-in-program-files-28"></a>
-Every nontrivial file needs a license notice as well as the copyright
+<p>Every nontrivial file needs a license notice as well as the copyright
 notice.  (Without a license notice giving permission to copy and
 change the file, the file is non-free.)
-
-   <p>The package itself should contain a full copy of GPL in plain text
-(conventionally in a file named <samp><span 
class="file">COPYING</span></samp>) and the GNU Free
+</p>
+<p>The package itself should contain a full copy of GPL in plain text
+(conventionally in a file named &lsquo;<tt>COPYING</tt>&rsquo;) and the GNU 
Free
 Documentation License (included within your documentation, so there is
 no need for a separate plain text version).  If the package contains
 any files distributed under the Lesser GPL, it should contain a full
 copy of its plain text version also (conventionally in a file named
-<samp><span class="file">COPYING.LESSER</span></samp>).
-
-   <p>If you have questions about licensing issues for your GNU package,
+&lsquo;<tt>COPYING.LESSER</tt>&rsquo;).
+</p>
+<p>If you have questions about licensing issues for your GNU package,
 please write <a href="mailto:address@hidden";>address@hidden</a>.
+</p>
+<table class="menu" border="0" cellspacing="0">
+<tr><td align="left" valign="top">&bull; <a href="#Licensing-of-GNU-Packages" 
accesskey="1">Which</a>:</td><td>&nbsp;&nbsp;</td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a href="#Canonical-License-Sources" 
accesskey="2">Canonical</a>:</td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a href="#License-Notices-for-Code" 
accesskey="3">Code</a>:</td><td>&nbsp;&nbsp;</td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a 
href="#License-Notices-for-Documentation" 
accesskey="4">Documentation</a>:</td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a 
href="#License-Notices-for-Other-Files" 
accesskey="5">Other</a>:</td><td>&nbsp;&nbsp;</td><td align="left" valign="top">
+</td></tr>
+</table>
 
-<ul class="menu">
-<li><a accesskey="1" href="#Licensing-of-GNU-Packages">Which</a>
-<li><a accesskey="2" href="#Canonical-License-Sources">Canonical</a>
-<li><a accesskey="3" href="#License-Notices-for-Code">Code</a>
-<li><a accesskey="4" 
href="#License-Notices-for-Documentation">Documentation</a>
-<li><a accesskey="5" href="#License-Notices-for-Other-Files">Other</a>
-</ul>
 
-<div class="node">
+<hr>
 <a name="Licensing-of-GNU-Packages"></a>
-<p><hr>
-Next:&nbsp;<a rel="next" accesskey="n" 
href="#Canonical-License-Sources">Canonical License Sources</a>,
-Up:&nbsp;<a rel="up" accesskey="u" href="#License-Notices">License Notices</a>
-
+<div class="header">
+<p>
+Next: <a href="#Canonical-License-Sources" accesskey="n" rel="next">Canonical 
License Sources</a>, Up: <a href="#License-Notices" accesskey="u" 
rel="up">License Notices</a> &nbsp; [<a href="#SEC_Contents" title="Table of 
contents" rel="contents">Contents</a>][<a href="#Index" title="Index" 
rel="index">Index</a>]</p>
 </div>
-
-<h4 class="subsection">6.6.1 Licensing of GNU Packages</h4>
+<a name="Licensing-of-GNU-Packages-1"></a>
+<h3 class="subsection">6.6.1 Licensing of GNU Packages</h3>
 
 <p>Normally, GNU packages should use the latest version of the GNU GPL,
-with the &ldquo;or any later version&rdquo; formulation.  See <a 
href="#License-Notices-for-Code">License Notices for Code</a>, for the exact 
wording of the license notice.
-
-   <p>Occasionally, a GNU library may provide functionality which is already
+with the &ldquo;or any later version&rdquo; formulation.  See <a 
href="#License-Notices-for-Code">License Notices
+for Code</a>, for the exact wording of the license notice.
+</p>
+<p>Occasionally, a GNU library may provide functionality which is already
 widely available to proprietary programs through alternative
 implementations; for example, the GNU C Library.  In such cases, the
 Lesser GPL should be used (again, for the notice wording,
@@ -862,310 +929,315 @@
 functionality, however, the GNU GPL should be used. 
 <a 
href="http://www.gnu.org/licenses/why-not-lgpl.html";>http://www.gnu.org/licenses/why-not-lgpl.html</a>
 discusses this
 strategic choice.
-
-   <p>Some of these libraries need to work with programs released under
+</p>
+<p>Some of these libraries need to work with programs released under
 GPLv2-only; that is, which allow the GNU GPL version 2 but not later
 versions.  In this case, the GNU package should be released under a
 dual license: GNU GPL version 2 (or any later version) and the GNU
 Lesser GPL version 3 (or any later version).  Here is the notice for
 that case:
+</p>
+<div class="smallexample">
+<pre class="smallexample">This file is part of GNU <var>package</var>.
 
-<pre class="smallexample">     This file is part of GNU <var>package</var>.
-     
-     GNU <var>package</var> is free software: you can redistribute it and/or
-     modify it under the terms of either:
+GNU <var>package</var> is free software: you can redistribute it and/or
+modify it under the terms of either:
      
        * the GNU Lesser General Public License as published by the Free
          Software Foundation; either version 3 of the License, or (at your
          option) any later version.
      
-     or
+or
      
        * the GNU General Public License as published by the Free
          Software Foundation; either version 2 of the License, or (at your
          option) any later version.
      
-     or both in parallel, as here.
+or both in parallel, as here.
      
-     GNU <var>package</var> 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 copies of the GNU General Public License and
-     the GNU Lesser General Public License along with this program.  If
-     not, see <a 
href="http://www.gnu.org/licenses/";>http://www.gnu.org/licenses/</a>.
-</pre>
-   <p>For small packages, you can use &ldquo;This program&rdquo; instead of 
&ldquo;GNU
+GNU <var>package</var> 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 copies of the GNU General Public License and
+the GNU Lesser General Public License along with this program.  If
+not, see <a 
href="http://www.gnu.org/licenses/";>http://www.gnu.org/licenses/</a>.
+</pre></div>
+
+<p>For small packages, you can use &ldquo;This program&rdquo; instead of 
&ldquo;GNU
 <var>package</var>&rdquo;.
+</p>
 
-<div class="node">
+<hr>
 <a name="Canonical-License-Sources"></a>
-<p><hr>
-Next:&nbsp;<a rel="next" accesskey="n" 
href="#License-Notices-for-Code">License Notices for Code</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" 
href="#Licensing-of-GNU-Packages">Licensing of GNU Packages</a>,
-Up:&nbsp;<a rel="up" accesskey="u" href="#License-Notices">License Notices</a>
-
+<div class="header">
+<p>
+Next: <a href="#License-Notices-for-Code" accesskey="n" rel="next">License 
Notices for Code</a>, Previous: <a href="#Licensing-of-GNU-Packages" 
accesskey="p" rel="previous">Licensing of GNU Packages</a>, Up: <a 
href="#License-Notices" accesskey="u" rel="up">License Notices</a> &nbsp; [<a 
href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a 
href="#Index" title="Index" rel="index">Index</a>]</p>
 </div>
-
-<h4 class="subsection">6.6.2 Canonical License Sources</h4>
+<a name="Canonical-License-Sources-1"></a>
+<h3 class="subsection">6.6.2 Canonical License Sources</h3>
 
 <p>You can get the official versions of these files from several places. 
 You can use whichever is the most convenient for you.
+</p>
+<ul>
+<li> <a href="http://www.gnu.org/licenses/";>http://www.gnu.org/licenses/</a>.
 
-     <ul>
-<li><a href="http://www.gnu.org/licenses/";>http://www.gnu.org/licenses/</a>.
-
-     <li>The <code>gnulib</code> project on <code>savannah.gnu.org</code>, 
which you
+</li><li> The <code>gnulib</code> project on <code>savannah.gnu.org</code>, 
which you
 can access via anonymous Git or CVS.  See
 <a 
href="http://savannah.gnu.org/projects/gnulib";>http://savannah.gnu.org/projects/gnulib</a>.
 
-   </ul>
+</li></ul>
 
-   <p>The official Texinfo sources for the licenses are also available in
+<p>The official Texinfo sources for the licenses are also available in
 those same places, so you can include them in your documentation.  A
-GFDL-covered manual should include the GFDL in this way.  See <a 
href="texinfo.html#GNU-Sample-Texts">GNU Sample Texts</a>, for a full example 
in a Texinfo
+GFDL-covered manual should include the GFDL in this way.  See <a 
href="http://www.gnu.org/software/texinfo/manual/texinfo/texinfo.html#GNU-Sample-Texts";>GNU
+Sample Texts</a> in <cite>Texinfo</cite>, for a full example in a Texinfo
 manual.
+</p>
 
-<div class="node">
+<hr>
 <a name="License-Notices-for-Code"></a>
-<p><hr>
-Next:&nbsp;<a rel="next" accesskey="n" 
href="#License-Notices-for-Documentation">License Notices for Documentation</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" 
href="#Canonical-License-Sources">Canonical License Sources</a>,
-Up:&nbsp;<a rel="up" accesskey="u" href="#License-Notices">License Notices</a>
-
+<div class="header">
+<p>
+Next: <a href="#License-Notices-for-Documentation" accesskey="n" 
rel="next">License Notices for Documentation</a>, Previous: <a 
href="#Canonical-License-Sources" accesskey="p" rel="previous">Canonical 
License Sources</a>, Up: <a href="#License-Notices" accesskey="u" 
rel="up">License Notices</a> &nbsp; [<a href="#SEC_Contents" title="Table of 
contents" rel="contents">Contents</a>][<a href="#Index" title="Index" 
rel="index">Index</a>]</p>
 </div>
-
-<h4 class="subsection">6.6.3 License Notices for Code</h4>
+<a name="License-Notices-for-Code-1"></a>
+<h3 class="subsection">6.6.3 License Notices for Code</h3>
 
 <p>Typically the license notice for program files (including build scripts,
 configure files and makefiles) should cite the GPL, like this:
-
-   <blockquote>
-This file is part of GNU <var>package</var>.
-
-   <p>GNU <var>package</var> is free software: you can redistribute it and/or
+</p>
+<blockquote>
+<p>This file is part of GNU <var>package</var>.
+</p>
+<p>GNU <var>package</var> 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.
-
-   <p>GNU <var>package</var> is distributed in the hope that it will be useful,
+</p>
+<p>GNU <var>package</var> is distributed in the hope that it will be useful,
 but WITHOUT ANY WARRANTY; without even the implied warranty of
 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
 GNU General Public License for more details.
-
-   <p>You should have received a copy of the GNU General Public License
+</p>
+<p>You should have received a copy of the GNU General Public License
 along with this program.  If not, see <a 
href="http://www.gnu.org/licenses/";>http://www.gnu.org/licenses/</a>. 
-</blockquote>
+</p></blockquote>
 
-   <p>But in a small program which is just a few files, you can use
+<p>But in a small program which is just a few files, you can use
 this instead:
-
-   <blockquote>
-This program is free software: you can redistribute it and/or modify
+</p>
+<blockquote>
+<p>This program is free software: you can redistribute it and/or modify
 it under the terms of the GNU General Public License as published by
 the Free Software Foundation; either version 3 of the License, or
 (at your option) any later version.
-
-   <p>This program is distributed in the hope that it will be useful,
+</p>
+<p>This program is distributed in the hope that it will be useful,
 but WITHOUT ANY WARRANTY; without even the implied warranty of
 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
 GNU General Public License for more details.
-
-   <p>You should have received a copy of the GNU General Public License
+</p>
+<p>You should have received a copy of the GNU General Public License
 along with this program.  If not, see <a 
href="http://www.gnu.org/licenses/";>http://www.gnu.org/licenses/</a>. 
-</blockquote>
+</p></blockquote>
 
-   <p>In either case, for those few packages which use the Lesser GPL
+<p>In either case, for those few packages which use the Lesser GPL
 (see <a href="#Licensing-of-GNU-Packages">Licensing of GNU Packages</a>), 
insert the word &ldquo;Lesser&rdquo; before
 &ldquo;General&rdquo; in <em>all three</em> places. 
 <a 
href="http://www.gnu.org/licenses/gpl-howto.html";>http://www.gnu.org/licenses/gpl-howto.html</a>
 discusses application
 the GPL in more detail.
+</p>
 
-<div class="node">
+<hr>
 <a name="License-Notices-for-Documentation"></a>
-<p><hr>
-Next:&nbsp;<a rel="next" accesskey="n" 
href="#License-Notices-for-Other-Files">License Notices for Other Files</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" 
href="#License-Notices-for-Code">License Notices for Code</a>,
-Up:&nbsp;<a rel="up" accesskey="u" href="#License-Notices">License Notices</a>
-
+<div class="header">
+<p>
+Next: <a href="#License-Notices-for-Other-Files" accesskey="n" 
rel="next">License Notices for Other Files</a>, Previous: <a 
href="#License-Notices-for-Code" accesskey="p" rel="previous">License Notices 
for Code</a>, Up: <a href="#License-Notices" accesskey="u" rel="up">License 
Notices</a> &nbsp; [<a href="#SEC_Contents" title="Table of contents" 
rel="contents">Contents</a>][<a href="#Index" title="Index" 
rel="index">Index</a>]</p>
 </div>
-
-<h4 class="subsection">6.6.4 License Notices for Documentation</h4>
+<a name="License-Notices-for-Documentation-1"></a>
+<h3 class="subsection">6.6.4 License Notices for Documentation</h3>
 
 <p>Documentation files should have license notices also.  Manuals should
 use the GNU Free Documentation License.  Following is an example of the
 license notice to use after the copyright line(s) using all the
 features of the GFDL.
+</p>
+<div class="smallexample">
+<pre class="smallexample">Permission is granted to copy, distribute and/or 
modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with the
+Invariant Sections being ``GNU General Public License'', with the
+Front-Cover Texts being ``A GNU Manual'', and with the Back-Cover Texts
+as in (a) below.  A copy of the license is included in the section
+entitled ``GNU Free Documentation License''.
+
+(a) The FSF's Back-Cover Text is: ``You have the freedom to
+copy and modify this GNU manual.  Buying copies from the FSF
+supports it in developing GNU and promoting software freedom.''
+</pre></div>
 
-<pre class="smallexample">     Permission is granted to copy, distribute 
and/or modify this document
-     under the terms of the GNU Free Documentation License, Version 1.3 or
-     any later version published by the Free Software Foundation; with the
-     Invariant Sections being ``GNU General Public License'', with the
-     Front-Cover Texts being ``A GNU Manual'', and with the Back-Cover Texts
-     as in (a) below.  A copy of the license is included in the section
-     entitled ``GNU Free Documentation License''.
-     
-     (a) The FSF's Back-Cover Text is: ``You have the freedom to
-     copy and modify this GNU manual.  Buying copies from the FSF
-     supports it in developing GNU and promoting software freedom.''
-</pre>
-   <p>If the FSF does not publish this manual on paper, then omit the last
+<p>If the FSF does not publish this manual on paper, then omit the last
 sentence in (a) that talks about copies from GNU Press.  If the FSF is
-not the copyright holder, then replace &lsquo;<samp><span 
class="samp">FSF</span></samp>&rsquo; with the appropriate
+not the copyright holder, then replace &lsquo;<samp>FSF</samp>&rsquo; with the 
appropriate
 name.
-
-   <p>Please adjust the list of invariant sections as appropriate for your
+</p>
+<p>Please adjust the list of invariant sections as appropriate for your
 manual.  If there are none, then say &ldquo;with no Invariant Sections&rdquo;. 
 If your manual is not published by the FSF, and under 400 pages, you
 can omit both cover texts.
-
-   <p>See <a href="texinfo.html#GNU-Sample-Texts">GNU Sample Texts</a>, for a 
full example in a
+</p>
+<p>See <a 
href="http://www.gnu.org/software/texinfo/manual/texinfo/texinfo.html#GNU-Sample-Texts";>GNU
 Sample Texts</a> in <cite>Texinfo</cite>, for a full example in a
 Texinfo manual, and see
 <a 
href="http://www.gnu.org/licenses/fdl-howto.html";>http://www.gnu.org/licenses/fdl-howto.html</a>
 for more advice about
 how to use the GNU FDL.
-
-   <p>If the manual is over 400 pages, or if the FSF thinks it might be a
+</p>
+<p>If the manual is over 400 pages, or if the FSF thinks it might be a
 good choice for publishing on paper, then please include the GNU GPL,
 as in the notice above.  Please also include our standard invariant
 section which explains the importance of free documentation.  Write to
 <a href="mailto:address@hidden";>address@hidden</a> to get a copy of this 
section.
-
-   <p>When you distribute several manuals together in one software package,
+</p>
+<p>When you distribute several manuals together in one software package,
 their on-line forms can share a single copy of the GFDL (see
-section&nbsp;6).  However, the printed (&lsquo;<samp><span 
class="samp">.dvi</span></samp>&rsquo;, &lsquo;<samp><span 
class="samp">.pdf</span></samp>&rsquo;,
-<small class="dots">...</small>) forms should each contain a copy of the GFDL, 
unless they are
+section&nbsp;6).  However, the printed (&lsquo;<samp>.dvi</samp>&rsquo;, 
&lsquo;<samp>.pdf</samp>&rsquo;,
+&hellip;) forms should each contain a copy of the GFDL, unless they are
 set up to be printed and published only together.  Therefore, it is
 usually simplest to include the GFDL in each manual.
+</p>
 
-<div class="node">
+<hr>
 <a name="License-Notices-for-Other-Files"></a>
-<p><hr>
-Previous:&nbsp;<a rel="previous" accesskey="p" 
href="#License-Notices-for-Documentation">License Notices for Documentation</a>,
-Up:&nbsp;<a rel="up" accesskey="u" href="#License-Notices">License Notices</a>
-
+<div class="header">
+<p>
+Previous: <a href="#License-Notices-for-Documentation" accesskey="p" 
rel="previous">License Notices for Documentation</a>, Up: <a 
href="#License-Notices" accesskey="u" rel="up">License Notices</a> &nbsp; [<a 
href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a 
href="#Index" title="Index" rel="index">Index</a>]</p>
 </div>
-
-<h4 class="subsection">6.6.5 License Notices for Other Files</h4>
+<a name="License-Notices-for-Other-Files-1"></a>
+<h3 class="subsection">6.6.5 License Notices for Other Files</h3>
 
 <p>Small supporting files, short manuals (under 300 lines long) and rough
-documentation (<samp><span class="file">README</span></samp> files, 
<samp><span class="file">INSTALL</span></samp> files, etc.) can
+documentation (&lsquo;<tt>README</tt>&rsquo; files, 
&lsquo;<tt>INSTALL</tt>&rsquo; files, etc.) can
 use a simple all-permissive license like this one:
+</p>
+<div class="smallexample">
+<pre class="smallexample">Copying and distribution of this file, with or 
without modification,
+are permitted in any medium without royalty provided the copyright
+notice and this notice are preserved.  This file is offered as-is,
+without any warranty.
+</pre></div>
 
-<pre class="smallexample">     Copying and distribution of this file, with or 
without modification,
-     are permitted in any medium without royalty provided the copyright
-     notice and this notice are preserved.  This file is offered as-is,
-     without any warranty.
-</pre>
-   <p>Older versions of this license did not have the second sentence with
+<p>Older versions of this license did not have the second sentence with
 the express warranty disclaimer.  There is no urgent need to update
 existing files, but new files should use the new text.
-
-   <p>If your package distributes Autoconf macros that are intended to be
+</p>
+<p>If your package distributes Autoconf macros that are intended to be
 used (hence distributed) by third-party packages under possibly
 incompatible licenses, you may also use the above all-permissive
 license for these macros.
+</p>
 
-<div class="node">
+<hr>
 <a name="External-Libraries"></a>
-<p><hr>
-Previous:&nbsp;<a rel="previous" accesskey="p" href="#License-Notices">License 
Notices</a>,
-Up:&nbsp;<a rel="up" accesskey="u" href="#Legal-Matters">Legal Matters</a>
-
+<div class="header">
+<p>
+Previous: <a href="#License-Notices" accesskey="p" rel="previous">License 
Notices</a>, Up: <a href="#Legal-Matters" accesskey="u" rel="up">Legal 
Matters</a> &nbsp; [<a href="#SEC_Contents" title="Table of contents" 
rel="contents">Contents</a>][<a href="#Index" title="Index" 
rel="index">Index</a>]</p>
 </div>
-
-<h3 class="section">6.7 External Libraries</h3>
+<a name="External-Libraries-1"></a>
+<h2 class="section">6.7 External Libraries</h2>
 
 <p>When maintaining an FSF-copyrighted GNU package, you may occasionally
 want to use a general-purpose free software module which offers a
 useful functionality, as a &ldquo;library&rdquo; facility (though the module is
 not always packaged technically as a library).
-
-   <p>In a case like this, it would be unreasonable to ask the author of that
+</p>
+<p>In a case like this, it would be unreasonable to ask the author of that
 module to assign the copyright to the FSF.  After all, person did not
 write it specifically as a contribution to your package, so it would be
 impertinent to ask per, out of the blue, &ldquo;Please give the FSF your
 copyright.&rdquo;
-
-   <p>So the thing to do in this case is to make your program use the module,
+</p>
+<p>So the thing to do in this case is to make your program use the module,
 but not consider it a part of your program.  There are two reasonable
 methods of doing this:
-
-     <ol type=1 start=1>
-<li>Assume the module is already installed on the system, and use it when
+</p>
+<ol>
+<li> Assume the module is already installed on the system, and use it when
 linking your program.  This is only reasonable if the module really has
 the form of a library.
 
-     <li>Include the module in your package, putting the source in a separate
-subdirectory whose <samp><span class="file">README</span></samp> file says, 
&ldquo;This is not part of the
+</li><li> Include the module in your package, putting the source in a separate
+subdirectory whose &lsquo;<tt>README</tt>&rsquo; file says, &ldquo;This is not 
part of the
 GNU FOO program, but is used with GNU FOO.&rdquo;  Then set up your makefiles
 to build this module and link it into the executable.
 
-     <p>For this method, it is not necessary to treat the module as a library
-and make a &lsquo;<samp><span class="samp">.a</span></samp>&rsquo; file from 
it.  You can link with the &lsquo;<samp><span 
class="samp">.o</span></samp>&rsquo;
+<p>For this method, it is not necessary to treat the module as a library
+and make a &lsquo;<samp>.a</samp>&rsquo; file from it.  You can link with the 
&lsquo;<samp>.o</samp>&rsquo;
 files directly in the usual manner.
-        </ol>
+</p></li></ol>
 
-   <p>Both of these methods create an irregularity, and our lawyers have told
+<p>Both of these methods create an irregularity, and our lawyers have told
 us to minimize the amount of such irregularity.  So consider using these
 methods only for general-purpose modules that were written for other
 programs and released separately for general use.  For anything that was
 written as a contribution to your package, please get papers signed.
+</p>
 
-<div class="node">
+<hr>
 <a name="Clean-Ups"></a>
-<p><hr>
-Next:&nbsp;<a rel="next" accesskey="n" href="#Platforms">Platforms</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" href="#Legal-Matters">Legal 
Matters</a>,
-Up:&nbsp;<a rel="up" accesskey="u" href="#Top">Top</a>
-
-</div>
+<div class="header">
+<p>
+Next: <a href="#Platforms" accesskey="n" rel="next">Platforms</a>, Previous: 
<a href="#Legal-Matters" accesskey="p" rel="previous">Legal Matters</a>, Up: <a 
href="#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a href="#SEC_Contents" 
title="Table of contents" rel="contents">Contents</a>][<a href="#Index" 
title="Index" rel="index">Index</a>]</p>
+</div>
+<a name="Cleaning-Up-Changes"></a>
+<h1 class="chapter">7 Cleaning Up Changes</h1>
+<a name="index-contributions_002c-accepting"></a>
+<a name="index-quality-of-changes-suggested-by-others"></a>
 
-<h2 class="chapter">7 Cleaning Up Changes</h2>
-
-<p><a name="index-contributions_002c-accepting-29"></a><a 
name="index-quality-of-changes-suggested-by-others-30"></a>
-Don't feel obligated to include every change that someone asks you to
+<p>Don&rsquo;t feel obligated to include every change that someone asks you to
 include.  You must judge which changes are improvements&mdash;partly based
 on what you think the users will like, and partly based on your own
 judgment of what is better.  If you think a change is not good, you
 should reject it.
-
-   <p>If someone sends you changes which are useful, but written in an ugly
-way or hard to understand and maintain in the future, don't hesitate to
+</p>
+<p>If someone sends you changes which are useful, but written in an ugly
+way or hard to understand and maintain in the future, don&rsquo;t hesitate to
 ask per to clean up their changes before you merge them.  Since the
 amount of work we can do is limited, the more we convince others to help
 us work efficiently, the faster GNU will advance.
-
-   <p>If the contributor will not or can not make the changes clean enough,
-then it is legitimate to say &ldquo;I can't install this in its present form;
+</p>
+<p>If the contributor will not or can not make the changes clean enough,
+then it is legitimate to say &ldquo;I can&rsquo;t install this in its present 
form;
 I can only do so if you clean it up.&rdquo;  Invite per to distribute per
 changes another way, or to find other people to make them clean enough
 for you to install and maintain.
-
-   <p>The only reason to do these cleanups yourself is if (1) it is easy, less
+</p>
+<p>The only reason to do these cleanups yourself is if (1) it is easy, less
 work than telling the author what to clean up, or (2) the change is an
 important one, important enough to be worth the work of cleaning it up.
-
-   <p>The GNU Coding Standards are a good thing to send people when you ask
-them to clean up changes (see <a href="standards.html#Top">Contents</a>).  The 
Emacs Lisp manual contains an appendix that gives
+</p>
+<p>The GNU Coding Standards are a good thing to send people when you ask
+them to clean up changes (see <a 
href="http://www.gnu.org/prep/standards/standards.html#Top";>Contents</a> in 
<cite>GNU Coding
+Standards</cite>).  The Emacs Lisp manual contains an appendix that gives
 coding standards for Emacs Lisp programs; it is good to urge Lisp authors to
-read it (see <a href="elisp.html#Tips">Tips and Conventions</a>).
+read it (see <a 
href="http://www.gnu.org/software/emacs/manual/html_mono/elisp.html#Tips";>Tips 
and Conventions</a> in <cite>The GNU Emacs Lisp
+Reference Manual</cite>).
+</p>
 
-<div class="node">
+<hr>
 <a name="Platforms"></a>
-<p><hr>
-Next:&nbsp;<a rel="next" accesskey="n" href="#Mail">Mail</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" href="#Clean-Ups">Clean Ups</a>,
-Up:&nbsp;<a rel="up" accesskey="u" href="#Top">Top</a>
-
+<div class="header">
+<p>
+Next: <a href="#Mail" accesskey="n" rel="next">Mail</a>, Previous: <a 
href="#Clean-Ups" accesskey="p" rel="previous">Clean Ups</a>, Up: <a 
href="#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a href="#SEC_Contents" 
title="Table of contents" rel="contents">Contents</a>][<a href="#Index" 
title="Index" rel="index">Index</a>]</p>
 </div>
-
-<h2 class="chapter">8 Platforms to Support</h2>
+<a name="Platforms-to-Support"></a>
+<h1 class="chapter">8 Platforms to Support</h1>
 
 <p>Most GNU packages run on a wide range of platforms.  These platforms are
 not equally important.
-
-   <p>The most important platforms for a GNU package to support are GNU and
+</p>
+<p>The most important platforms for a GNU package to support are GNU and
 GNU/Linux.  Developing the GNU operating system is the whole point of
 the GNU Project; a GNU package exists to make the whole GNU system more
 powerful.  So please keep that goal in mind and let it shape your work. 
@@ -1174,12 +1246,12 @@
 GNU/Linux, it could still be acceptable.  However, a feature that runs
 only on other systems and not on GNU or GNU/Linux makes no sense in a
 GNU package.
-
-   <p>You will naturally want to keep the program running on all the platforms
+</p>
+<p>You will naturally want to keep the program running on all the platforms
 it supports.  But you personally will not have access to most of these
 platforms&mdash;so how should you do it?
-
-   <p>Don't worry about trying to get access to all of these platforms.  Even
+</p>
+<p>Don&rsquo;t worry about trying to get access to all of these platforms.  
Even
 if you did have access to all the platforms, it would be inefficient for
 you to test the program on each platform yourself.  Instead, you should
 test the program on a few platforms, including GNU or GNU/Linux, and let
@@ -1188,259 +1260,279 @@
 problems, in a package that is mostly portable, you can just make a
 release and let the users tell you if anything unportable was
 introduced.
-
-   <p>It is important to test the program personally on GNU or GNU/Linux,
+</p>
+<p>It is important to test the program personally on GNU or GNU/Linux,
 because these are the most important platforms for a GNU package.  If
-you don't have access to one of these platforms, as a GNU maintainer
+you don&rsquo;t have access to one of these platforms, as a GNU maintainer
 you can get access to the general GNU login machine; see
 <a 
href="http://www.gnu.org/software/README.accounts.html";>http://www.gnu.org/software/README.accounts.html</a>.
-
-   <p>Supporting other platforms is optional&mdash;we do it when that seems 
like
-a good idea, but we don't consider it obligatory.  If the users don't
+</p>
+<p>Supporting other platforms is optional&mdash;we do it when that seems like
+a good idea, but we don&rsquo;t consider it obligatory.  If the users 
don&rsquo;t
 take care of a certain platform, you may have to desupport it unless
 and until users come forward to help.  Conversely, if a user offers
 changes to support an additional platform, you will probably want to
-install them, but you don't have to.  If you feel the changes are
+install them, but you don&rsquo;t have to.  If you feel the changes are
 complex and ugly, if you think that they will increase the burden of
 future maintenance, you can and should reject them.  This includes
 both free or mainly-free platforms such as OpenBSD, FreeBSD, and
 NetBSD, and non-free platforms such as Windows.
+</p>
 
-<div class="node">
+<hr>
 <a name="Mail"></a>
-<p><hr>
-Next:&nbsp;<a rel="next" accesskey="n" href="#Old-Versions">Old Versions</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" href="#Platforms">Platforms</a>,
-Up:&nbsp;<a rel="up" accesskey="u" href="#Top">Top</a>
-
-</div>
-
-<h2 class="chapter">9 Dealing With Mail</h2>
+<div class="header">
+<p>
+Next: <a href="#Old-Versions" accesskey="n" rel="next">Old Versions</a>, 
Previous: <a href="#Platforms" accesskey="p" rel="previous">Platforms</a>, Up: 
<a href="#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a href="#SEC_Contents" 
title="Table of contents" rel="contents">Contents</a>][<a href="#Index" 
title="Index" rel="index">Index</a>]</p>
+</div>
+<a name="Dealing-With-Mail"></a>
+<h1 class="chapter">9 Dealing With Mail</h1>
+<a name="index-email"></a>
 
-<p><a name="index-email-31"></a>
-This chapter describes setting up mailing lists for your package, and
+<p>This chapter describes setting up mailing lists for your package, and
 gives advice on how to handle bug reports and random requests once you
 have them.
+</p>
+<table class="menu" border="0" cellspacing="0">
+<tr><td align="left" valign="top">&bull; <a href="#Standard-Mailing-Lists" 
accesskey="1">Standard Mailing Lists</a>:</td><td>&nbsp;&nbsp;</td><td 
align="left" valign="top">  &lsquo;<samp>address@hidden</samp>&rsquo; and other 
standard names.
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a href="#Creating-Mailing-Lists" 
accesskey="2">Creating Mailing Lists</a>:</td><td>&nbsp;&nbsp;</td><td 
align="left" valign="top">  The best way is to use Savannah.
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a href="#Replying-to-Mail" 
accesskey="3">Replying to Mail</a>:</td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">        Advice on replying to incoming mail.
+</td></tr>
+</table>
 
-<ul class="menu">
-<li><a accesskey="1" href="#Standard-Mailing-Lists">Standard Mailing 
Lists</a>:   &lsquo;<samp><span 
class="samp">address@hidden</span></samp>&rsquo; and other standard names. 
-<li><a accesskey="2" href="#Creating-Mailing-Lists">Creating Mailing 
Lists</a>:   The best way is to use Savannah. 
-<li><a accesskey="3" href="#Replying-to-Mail">Replying to Mail</a>:         
Advice on replying to incoming mail. 
-</ul>
 
-<div class="node">
+<hr>
 <a name="Standard-Mailing-Lists"></a>
-<p><hr>
-Next:&nbsp;<a rel="next" accesskey="n" href="#Creating-Mailing-Lists">Creating 
Mailing Lists</a>,
-Up:&nbsp;<a rel="up" accesskey="u" href="#Mail">Mail</a>
-
+<div class="header">
+<p>
+Next: <a href="#Creating-Mailing-Lists" accesskey="n" rel="next">Creating 
Mailing Lists</a>, Up: <a href="#Mail" accesskey="u" rel="up">Mail</a> &nbsp; 
[<a href="#SEC_Contents" title="Table of contents" 
rel="contents">Contents</a>][<a href="#Index" title="Index" 
rel="index">Index</a>]</p>
 </div>
+<a name="Standard-Mailing-Lists-1"></a>
+<h2 class="section">9.1 Standard Mailing Lists</h2>
 
-<h3 class="section">9.1 Standard Mailing Lists</h3>
+<a name="index-standard-mailing-lists"></a>
+<a name="index-mailing-lists_002c-standard-names-of"></a>
 
-<p><a name="index-standard-mailing-lists-32"></a><a 
name="index-mailing-lists_002c-standard-names-of-33"></a>
-<a name="index-mailing-list-for-bug-reports-34"></a>Once a program is in use, 
you will get bug reports for it.  Most GNU
+<a name="index-mailing-list-for-bug-reports"></a>
+<p>Once a program is in use, you will get bug reports for it.  Most GNU
 programs have their own special lists for sending bug reports.  The
 advertised bug-reporting email address should always be
-&lsquo;<samp><span class="samp">bug-</span><var>package</var><span 
class="samp">@gnu.org</span></samp>&rsquo;, to help show users that the program
+&lsquo;<samp>bug-<var>package</var>@gnu.org</samp>&rsquo;, to help show users 
that the program
 is a GNU package, but it is ok to set up that list to forward to another
 site if you prefer.  The package distribution should state the
 name of the bug-reporting list in a prominent place, and ask users to
 help us by reporting bugs there.
-
-   <p><a 
name="index-g_t_0040email_007bbug_002dgnu_002dutils_0040_0040gnu_002eorg_007d-35"></a>We
 also have a catch-all list, <a 
href="mailto:address@hidden";>address@hidden</a>, which is
-used for all GNU programs that don't have their own specific lists.  But
+</p>
+<a name="index-bug_002dgnu_002dutils_0040gnu_002eorg"></a>
+<p>We also have a catch-all list, <a 
href="mailto:address@hidden";>address@hidden</a>, which is
+used for all GNU programs that don&rsquo;t have their own specific lists.  But
 nowadays we want to give each program its own bug-reporting list and
 move away from using <a href="mailto:bug-gnu-utils";>bug-gnu-utils</a>.
-
-   <p><a name="index-help-for-users_002c-mailing-list-for-36"></a>Some GNU 
programs with many users have another mailing list,
-&lsquo;<samp><span class="samp">help-</span><var>package</var><span 
class="samp">.org</span></samp>&rsquo;, for people to ask other users for help. 
+</p>
+<a name="index-help-for-users_002c-mailing-list-for"></a>
+<p>Some GNU programs with many users have another mailing list,
+&lsquo;<samp>help-<var>package</var>.org</samp>&rsquo;, for people to ask 
other users for help.
 If your program has many users, you should create such a list for it. 
-For a fairly new program, which doesn't have a large user base yet, it
+For a fairly new program, which doesn&rsquo;t have a large user base yet, it
 is better not to bother with this.
-
-   <p><a name="index-announcements_002c-mailing-list-for-37"></a>If you wish, 
you can also have a mailing list
-&lsquo;<samp><span class="samp">info-</span><var>package</var></samp>&rsquo; 
for announcements (see <a href="#Announcements">Announcements</a>),
+</p>
+<a name="index-announcements_002c-mailing-list-for"></a>
+<p>If you wish, you can also have a mailing list
+&lsquo;<samp>info-<var>package</var></samp>&rsquo; for announcements (see <a 
href="#Announcements">Announcements</a>),
 and any others you find useful.
+</p>
 
-<div class="node">
+<hr>
 <a name="Creating-Mailing-Lists"></a>
-<p><hr>
-Next:&nbsp;<a rel="next" accesskey="n" href="#Replying-to-Mail">Replying to 
Mail</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" 
href="#Standard-Mailing-Lists">Standard Mailing Lists</a>,
-Up:&nbsp;<a rel="up" accesskey="u" href="#Mail">Mail</a>
-
+<div class="header">
+<p>
+Next: <a href="#Replying-to-Mail" accesskey="n" rel="next">Replying to 
Mail</a>, Previous: <a href="#Standard-Mailing-Lists" accesskey="p" 
rel="previous">Standard Mailing Lists</a>, Up: <a href="#Mail" accesskey="u" 
rel="up">Mail</a> &nbsp; [<a href="#SEC_Contents" title="Table of contents" 
rel="contents">Contents</a>][<a href="#Index" title="Index" 
rel="index">Index</a>]</p>
 </div>
+<a name="Creating-Mailing-Lists-1"></a>
+<h2 class="section">9.2 Creating Mailing Lists</h2>
 
-<h3 class="section">9.2 Creating Mailing Lists</h3>
+<a name="index-creating-mailing-lists"></a>
+<a name="index-mailing-lists_002c-creating"></a>
 
-<p><a name="index-creating-mailing-lists-38"></a><a 
name="index-mailing-lists_002c-creating-39"></a>
-Using the web interface on <code>savannah.gnu.org</code> is by far the
+<p>Using the web interface on <code>savannah.gnu.org</code> is by far the
 easiest way to create normal mailing lists, managed through Mailman on
 the GNU mail server.  Once you register your package on Savannah, you
-can create (and remove) lists yourself through the `Mailing Lists'
+can create (and remove) lists yourself through the &lsquo;Mailing Lists&rsquo;
 menu, without needing to wait for intervention by anyone else. 
 Furthermore, lists created through Savannah will have a reasonable
 default configuration for antispam purposes (see below).
-
-   <p>To create and maintain simple aliases and unmanaged lists, you can
-edit <samp><span class="file">/com/mailer/aliases</span></samp> on the main 
GNU server.  If you don't
+</p>
+<p>To create and maintain simple aliases and unmanaged lists, you can
+edit &lsquo;<tt>/com/mailer/aliases</tt>&rsquo; on the main GNU server.  If 
you don&rsquo;t
 have an account there, please read
-<a 
href="http://www.gnu.org/software/README.accounts.html";>http://www.gnu.org/software/README.accounts.html</a>
 (see <a href="#Getting-a-GNU-Account">Getting a GNU Account</a>).
-
-   <p>But if you don't want to learn how to do those things, you can
+<a 
href="http://www.gnu.org/software/README.accounts.html";>http://www.gnu.org/software/README.accounts.html</a>
 (see <a href="#Getting-a-GNU-Account">Getting
+a GNU Account</a>).
+</p>
+<p>But if you don&rsquo;t want to learn how to do those things, you can
 alternatively ask <a href="mailto:address@hidden";>address@hidden</a> to add 
you to the
 bug-reporting list for your program.  To set up a new list, contact
 <a href="mailto:address@hidden";>address@hidden</a>.  You can subscribe to a 
list managed
-by Mailman by sending mail to the corresponding &lsquo;<samp><span 
class="samp">-request</span></samp>&rsquo; address.
-
-   <p><a name="index-spam-prevention-40"></a>You should moderate postings from 
non-subscribed addresses on your
+by Mailman by sending mail to the corresponding 
&lsquo;<samp>-request</samp>&rsquo; address.
+</p>
+<a name="index-spam-prevention"></a>
+<p>You should moderate postings from non-subscribed addresses on your
 mailing lists, to prevent propagation of unwanted messages (&ldquo;spam&rdquo;)
 to subscribers and to the list archives.  For lists controlled by
 Mailman, you can do this by setting <code>Privacy Options - Sender
 Filter - generic_nonmember_action</code> to <code>Hold</code>, and then
 periodically (daily is best) reviewing the held messages, accepting
 the real ones and discarding the junk.
-
-   <p>Lists created through Savannah will have this setting, and a number of
+</p>
+<p>Lists created through Savannah will have this setting, and a number of
 others, such that spam will be automatically deleted (after a short
 delay).  The Savannah mailing list page describes all the details. 
 You should still review the held messages in order to approve any that
 are real.
+</p>
 
-<div class="node">
+<hr>
 <a name="Replying-to-Mail"></a>
-<p><hr>
-Previous:&nbsp;<a rel="previous" accesskey="p" 
href="#Creating-Mailing-Lists">Creating Mailing Lists</a>,
-Up:&nbsp;<a rel="up" accesskey="u" href="#Mail">Mail</a>
+<div class="header">
+<p>
+Previous: <a href="#Creating-Mailing-Lists" accesskey="p" 
rel="previous">Creating Mailing Lists</a>, Up: <a href="#Mail" accesskey="u" 
rel="up">Mail</a> &nbsp; [<a href="#SEC_Contents" title="Table of contents" 
rel="contents">Contents</a>][<a href="#Index" title="Index" 
rel="index">Index</a>]</p>
+</div>
+<a name="Replying-to-Mail-1"></a>
+<h2 class="section">9.3 Replying to Mail</h2>
+
+<a name="index-responding-to-bug-reports"></a>
+<a name="index-bug-reports_002c-handling"></a>
+<a name="index-help-requests_002c-handling"></a>
 
-</div>
-
-<h3 class="section">9.3 Replying to Mail</h3>
-
-<p><a name="index-responding-to-bug-reports-41"></a><a 
name="index-bug-reports_002c-handling-42"></a><a 
name="index-help-requests_002c-handling-43"></a>
-When you receive bug reports, keep in mind that bug reports are crucial
-for your work.  If you don't know about problems, you cannot fix them. 
+<p>When you receive bug reports, keep in mind that bug reports are crucial
+for your work.  If you don&rsquo;t know about problems, you cannot fix them.
 So always thank each person who sends a bug report.
-
-   <p>You don't have an obligation to give more response than that, though. 
+</p>
+<p>You don&rsquo;t have an obligation to give more response than that, though.
 The main purpose of bug reports is to help you contribute to the
 community by improving the next version of the program.  Many of the
-people who report bugs don't realize this&mdash;they think that the point is
+people who report bugs don&rsquo;t realize this&mdash;they think that the 
point is
 for you to help them individually.  Some will ask you to focus on that
 <em>instead of</em> on making the program better.  If you comply with
 their wishes, you will have been distracted from the job of maintaining
 the program.
-
-   <p>For example, people sometimes report a bug in a vague (and therefore
+</p>
+<p>For example, people sometimes report a bug in a vague (and therefore
 useless) way, and when you ask for more information, they say, &ldquo;I just
 wanted to see if you already knew the solution&rdquo; (in which case the bug
 report would do nothing to help improve the program).  When this
 happens, you should explain to them the real purpose of bug reports.  (A
 canned explanation will make this more efficient.)
-
-   <p>When people ask you to put your time into helping them use the program,
+</p>
+<p>When people ask you to put your time into helping them use the program,
 it may seem &ldquo;helpful&rdquo; to do what they ask.  But it is much 
<em>less</em>
-helpful than improving the program, which is the maintainer's real job.
-
-   <p>By all means help individual users when you feel like it, if you feel
+helpful than improving the program, which is the maintainer&rsquo;s real job.
+</p>
+<p>By all means help individual users when you feel like it, if you feel
 you have the time available.  But be careful to limit the amount of time
-you spend doing this&mdash;don't let it eat away the time you need to
+you spend doing this&mdash;don&rsquo;t let it eat away the time you need to
 maintain the program!  Know how to say no; when you are pressed for
 time, just &ldquo;thanks for the bug report&mdash;I will fix it&rdquo; is 
enough
 response.
-
-   <p>Some GNU packages, such as Emacs and GCC, come with advice about how
+</p>
+<p>Some GNU packages, such as Emacs and GCC, come with advice about how
 to make bug reports useful.  Copying and adapting that could be very
 useful for your package.
+</p>
 
-<div class="node">
+<hr>
 <a name="Old-Versions"></a>
-<p><hr>
-Next:&nbsp;<a rel="next" accesskey="n" href="#Distributions">Distributions</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" href="#Mail">Mail</a>,
-Up:&nbsp;<a rel="up" accesskey="u" href="#Top">Top</a>
+<div class="header">
+<p>
+Next: <a href="#Distributions" accesskey="n" rel="next">Distributions</a>, 
Previous: <a href="#Mail" accesskey="p" rel="previous">Mail</a>, Up: <a 
href="#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a href="#SEC_Contents" 
title="Table of contents" rel="contents">Contents</a>][<a href="#Index" 
title="Index" rel="index">Index</a>]</p>
+</div>
+<a name="Recording-Old-Versions"></a>
+<h1 class="chapter">10 Recording Old Versions</h1>
+<a name="index-version-control"></a>
 
-</div>
-
-<h2 class="chapter">10 Recording Old Versions</h2>
-
-<p><a name="index-version-control-44"></a>
-It is very important to keep backup files of all source files of GNU. 
+<p>It is very important to keep backup files of all source files of GNU.
 You can do this using a source control system (such as Bazaar, RCS,
-CVS, Git, Subversion, <small class="dots">...</small>) if you like.  An easy 
way to use
+CVS, Git, Subversion, &hellip;) if you like.  An easy way to use
 many such systems is via the Version Control library in Emacs
-(see <a href="emacs.html#Introduction-to-VC">Introduction to Version 
Control</a>).
-
-   <p>The history of previous revisions and log entries is very important for
+(see <a 
href="http://www.gnu.org/software/emacs/manual/html_mono/emacs.html#Introduction-to-VC";>Introduction
 to Version Control</a> in <cite>The GNU Emacs Manual</cite>).
+</p>
+<p>The history of previous revisions and log entries is very important for
 future maintainers of the package, so even if you do not make it
 publicly accessible, be careful not to put anything in the repository or
 change log that you would not want to hand over to another maintainer
 some day.
-
-   <p><a 
name="index-g_t_0040code_007bsavannah_002dhackers_0040_0040gnu_002eorg_007d-45"></a>The
 GNU Project provides a server that GNU packages can use
+</p>
+<a name="index-savannah_002dhackers_0040gnu_002eorg"></a>
+<p>The GNU Project provides a server that GNU packages can use
 for source control and other package needs: <code>savannah.gnu.org</code>. 
 Savannah is managed by <a href="mailto:address@hidden";>address@hidden</a>.  
For more
 details on using and contributing to Savannah, see
 <a 
href="http://savannah.gnu.org/maintenance";>http://savannah.gnu.org/maintenance</a>.
-
-   <p>It's not an absolute requirement, but all GNU maintainers are strongly
+</p>
+<p>It&rsquo;s not an absolute requirement, but all GNU maintainers are strongly
 encouraged to take advantage of Savannah, as sharing such a central
 point can serve to foster a sense of community among GNU developers as
-well as help in keeping up with project management.  Please don't mark
+well as help in keeping up with project management.  Please don&rsquo;t mark
 Savannah projects for GNU packages as private; that defeats a large
 part of the purpose of using Savannah in the first place.
-
-   <p><a 
name="index-g_t_0040code_007bsavannah_002dannounce_0040_0040gnu_002eorg_007d-mailing-list-46"></a>If
 you do use Savannah, please subscribe to the
+</p>
+<a name="index-savannah_002dannounce_0040gnu_002eorg-mailing-list"></a>
+<p>If you do use Savannah, please subscribe to the
 <a href="mailto:address@hidden";>address@hidden</a> mailing list
 (<a 
href="http://lists.gnu.org/mailman/listinfo/savannah-announce";>http://lists.gnu.org/mailman/listinfo/savannah-announce</a>).
  This
 is a very low-volume list to keep Savannah users informed of system
 upgrades, problems, and the like.
+</p>
 
-<div class="node">
+<hr>
 <a name="Distributions"></a>
-<p><hr>
-Next:&nbsp;<a rel="next" accesskey="n" href="#Web-Pages">Web Pages</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" href="#Old-Versions">Old 
Versions</a>,
-Up:&nbsp;<a rel="up" accesskey="u" href="#Top">Top</a>
-
+<div class="header">
+<p>
+Next: <a href="#Web-Pages" accesskey="n" rel="next">Web Pages</a>, Previous: 
<a href="#Old-Versions" accesskey="p" rel="previous">Old Versions</a>, Up: <a 
href="#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a href="#SEC_Contents" 
title="Table of contents" rel="contents">Contents</a>][<a href="#Index" 
title="Index" rel="index">Index</a>]</p>
 </div>
-
-<h2 class="chapter">11 Distributions</h2>
+<a name="Distributions-1"></a>
+<h1 class="chapter">11 Distributions</h1>
 
 <p>It is important to follow the GNU conventions when making GNU software
 distributions.
+</p>
+<table class="menu" border="0" cellspacing="0">
+<tr><td align="left" valign="top">&bull; <a href="#Distribution-tar-Files" 
accesskey="1">Distribution tar Files</a>:</td><td>&nbsp;&nbsp;</td><td 
align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a href="#Distribution-Patches" 
accesskey="2">Distribution Patches</a>:</td><td>&nbsp;&nbsp;</td><td 
align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a 
href="#Distribution-on-ftp_002egnu_002eorg" accesskey="3">Distribution on 
ftp.gnu.org</a>:</td><td>&nbsp;&nbsp;</td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a href="#Test-Releases" 
accesskey="4">Test Releases</a>:</td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a href="#Automated-FTP-Uploads" 
accesskey="5">Automated FTP Uploads</a>:</td><td>&nbsp;&nbsp;</td><td 
align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a href="#Announcements" 
accesskey="6">Announcements</a>:</td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">
+</td></tr>
+</table>
 
-<ul class="menu">
-<li><a accesskey="1" href="#Distribution-tar-Files">Distribution tar Files</a>
-<li><a accesskey="2" href="#Distribution-Patches">Distribution Patches</a>
-<li><a accesskey="3" href="#Distribution-on-ftp_002egnu_002eorg">Distribution 
on ftp.gnu.org</a>
-<li><a accesskey="4" href="#Test-Releases">Test Releases</a>
-<li><a accesskey="5" href="#Automated-FTP-Uploads">Automated FTP Uploads</a>
-<li><a accesskey="6" href="#Announcements">Announcements</a>
-</ul>
-
-<div class="node">
+<hr>
 <a name="Distribution-tar-Files"></a>
-<p><hr>
-Next:&nbsp;<a rel="next" accesskey="n" 
href="#Distribution-Patches">Distribution Patches</a>,
-Up:&nbsp;<a rel="up" accesskey="u" href="#Distributions">Distributions</a>
-
-</div>
-
-<h3 class="section">11.1 Distribution tar Files</h3>
-
-<p><a name="index-distribution_002c-tar-files-47"></a>
-The tar file for version <var>m</var>.<var>n</var> of program <code>foo</code> 
should be
-named <samp><span class="file">foo-</span><var>m</var><span 
class="file">.</span><var>n</var><span class="file">.tar</span></samp>.  It 
should unpack into a
-subdirectory named <samp><span class="file">foo-</span><var>m</var><span 
class="file">.</span><var>n</var></samp>.  Tar files should not
+<div class="header">
+<p>
+Next: <a href="#Distribution-Patches" accesskey="n" rel="next">Distribution 
Patches</a>, Up: <a href="#Distributions" accesskey="u" 
rel="up">Distributions</a> &nbsp; [<a href="#SEC_Contents" title="Table of 
contents" rel="contents">Contents</a>][<a href="#Index" title="Index" 
rel="index">Index</a>]</p>
+</div>
+<a name="Distribution-tar-Files-1"></a>
+<h2 class="section">11.1 Distribution tar Files</h2>
+<a name="index-distribution_002c-tar-files"></a>
+
+<p>The tar file for version <var>m</var>.<var>n</var> of program 
<code>foo</code> should be
+named &lsquo;<tt>foo-<var>m</var>.<var>n</var>.tar</tt>&rsquo;.  It should 
unpack into a
+subdirectory named &lsquo;<tt>foo-<var>m</var>.<var>n</var></tt>&rsquo;.  Tar 
files should not
 unpack into files in the current directory, because this is inconvenient
 if the user happens to unpack into a directory with other files in it.
-
-   <p>Here is how the <samp><span class="file">Makefile</span></samp> for 
Bison creates the tar file. 
+</p>
+<p>Here is how the &lsquo;<tt>Makefile</tt>&rsquo; for Bison creates the tar 
file.
 This method is good for other programs.
-
-<pre class="example">     dist: bison.info
+</p>
+<div class="example">
+<pre class="example">dist: bison.info
              echo bison-`sed -e '/version_string/!d' \
                -e 's/[^0-9.]*\([0-9.]*\).*/\1/' -e q version.c` &gt; .fname
              -rm -rf `cat .fname`
@@ -1451,802 +1543,851 @@
              done
              tar --gzip -chf `cat .fname`.tar.gz `cat .fname`
              -rm -rf `cat .fname` .fname
-</pre>
-   <p>Source files that are symbolic links to other file systems cannot be
+</pre></div>
+
+<p>Source files that are symbolic links to other file systems cannot be
 installed in the temporary directory using <code>ln</code>, so use 
<code>cp</code>
 if <code>ln</code> fails.
-
-   <p><a name="index-automake-48"></a>Using Automake is a good way to take 
care of writing the <code>dist</code>
+</p>
+<a name="index-automake"></a>
+<p>Using Automake is a good way to take care of writing the <code>dist</code>
 target.
-
-<div class="node">
+</p>
+<hr>
 <a name="Distribution-Patches"></a>
-<p><hr>
-Next:&nbsp;<a rel="next" accesskey="n" 
href="#Distribution-on-ftp_002egnu_002eorg">Distribution on ftp.gnu.org</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" 
href="#Distribution-tar-Files">Distribution tar Files</a>,
-Up:&nbsp;<a rel="up" accesskey="u" href="#Distributions">Distributions</a>
-
-</div>
+<div class="header">
+<p>
+Next: <a href="#Distribution-on-ftp_002egnu_002eorg" accesskey="n" 
rel="next">Distribution on ftp.gnu.org</a>, Previous: <a 
href="#Distribution-tar-Files" accesskey="p" rel="previous">Distribution tar 
Files</a>, Up: <a href="#Distributions" accesskey="u" 
rel="up">Distributions</a> &nbsp; [<a href="#SEC_Contents" title="Table of 
contents" rel="contents">Contents</a>][<a href="#Index" title="Index" 
rel="index">Index</a>]</p>
+</div>
+<a name="Distribution-Patches-1"></a>
+<h2 class="section">11.2 Distribution Patches</h2>
+<a name="index-patches_002c-against-previous-releases"></a>
 
-<h3 class="section">11.2 Distribution Patches</h3>
-
-<p><a name="index-patches_002c-against-previous-releases-49"></a>
-If the program is large, it is useful to make a set of diffs for each
+<p>If the program is large, it is useful to make a set of diffs for each
 release, against the previous important release.
-
-   <p>At the front of the set of diffs, put a short explanation of which
+</p>
+<p>At the front of the set of diffs, put a short explanation of which
 version this is for and which previous version it is relative to. 
 Also explain what else people need to do to update the sources
 properly (for example, delete or rename certain files before
 installing the diffs).
-
-   <p>The purpose of having diffs is that they are small.  To keep them
+</p>
+<p>The purpose of having diffs is that they are small.  To keep them
 small, exclude files that the user can easily update.  For example,
 exclude info files, DVI files, tags tables, output files of Bison or
 Flex.  In Emacs diffs, we exclude compiled Lisp files, leaving it up
 to the installer to recompile the patched sources.
-
-   <p>When you make the diffs, each version should be in a directory suitably
-named&mdash;for example, <samp><span class="file">gcc-2.3.2</span></samp> and 
<samp><span class="file">gcc-2.3.3</span></samp>.  This way,
+</p>
+<p>When you make the diffs, each version should be in a directory suitably
+named&mdash;for example, &lsquo;<tt>gcc-2.3.2</tt>&rsquo; and 
&lsquo;<tt>gcc-2.3.3</tt>&rsquo;.  This way,
 it will be very clear from the diffs themselves which version is which.
-
-   <p><a name="index-diff-50"></a><a name="index-patch-51"></a><a 
name="index-time-stamp-in-diffs-52"></a>If you use GNU <code>diff</code> to 
make the patch, use the options
-&lsquo;<samp><span class="samp">-rc2P</span></samp>&rsquo;.  That will put any 
new files into the output as &ldquo;entirely
-different.&rdquo;  Also, the patch's context diff headers should have dates
+</p>
+<a name="index-diff"></a>
+<a name="index-patch"></a>
+<a name="index-time-stamp-in-diffs"></a>
+<p>If you use GNU <code>diff</code> to make the patch, use the options
+&lsquo;<samp>-rc2P</samp>&rsquo;.  That will put any new files into the output 
as &ldquo;entirely
+different.&rdquo;  Also, the patch&rsquo;s context diff headers should have 
dates
 and times in Universal Time using traditional Unix format, so that patch
-recipients can use GNU <code>patch</code>'s &lsquo;<samp><span 
class="samp">-Z</span></samp>&rsquo; option.  For example,
+recipients can use GNU <code>patch</code>&rsquo;s 
&lsquo;<samp>-Z</samp>&rsquo; option.  For example,
 you could use the following Bourne shell command to create the patch:
+</p>
+<div class="example">
+<pre class="example">LC_ALL=C TZ=UTC0 diff -rc2P gcc-2.3.2 gcc-2.3.3 | \
+gzip -9 &gt;gcc-2.3.2-2.3.3.patch.gz
+</pre></div>
 
-<pre class="example">     LC_ALL=C TZ=UTC0 diff -rc2P gcc-2.3.2 gcc-2.3.3 | \
-     gzip -9 &gt;gcc-2.3.2-2.3.3.patch.gz
-</pre>
-   <p>If the distribution has subdirectories in it, then the diffs probably
+<p>If the distribution has subdirectories in it, then the diffs probably
 include some files in the subdirectories.  To help users install such
 patches reliably, give them precise directions for how to run patch. 
 For example, say this:
+</p>
+<div class="display">
+<pre class="display">To apply these patches, cd to the main directory of the 
program
+and then use &lsquo;patch -p1&rsquo;.   &lsquo;-p1&rsquo; avoids guesswork in 
choosing
+which subdirectory to find each file in.
+</pre></div>
 
-<pre class="display">     To apply these patches, cd to the main directory of 
the program
-     and then use `patch -p1'.   `-p1' avoids guesswork in choosing
-     which subdirectory to find each file in.
-</pre>
-   <p>It's wise to test your patch by applying it to a copy of the old
+<p>It&rsquo;s wise to test your patch by applying it to a copy of the old
 version, and checking that the result exactly matches the new version.
-
-<div class="node">
-<a name="Distribution-on-ftp.gnu.org"></a>
+</p>
+<hr>
 <a name="Distribution-on-ftp_002egnu_002eorg"></a>
-<p><hr>
-Next:&nbsp;<a rel="next" accesskey="n" href="#Test-Releases">Test Releases</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" 
href="#Distribution-Patches">Distribution Patches</a>,
-Up:&nbsp;<a rel="up" accesskey="u" href="#Distributions">Distributions</a>
-
-</div>
+<div class="header">
+<p>
+Next: <a href="#Test-Releases" accesskey="n" rel="next">Test Releases</a>, 
Previous: <a href="#Distribution-Patches" accesskey="p" 
rel="previous">Distribution Patches</a>, Up: <a href="#Distributions" 
accesskey="u" rel="up">Distributions</a> &nbsp; [<a href="#SEC_Contents" 
title="Table of contents" rel="contents">Contents</a>][<a href="#Index" 
title="Index" rel="index">Index</a>]</p>
+</div>
+<a name="Distribution-on-ftp_002egnu_002eorg-1"></a>
+<h2 class="section">11.3 Distribution on <code>ftp.gnu.org</code></h2>
+<a name="index-GNU-ftp-site"></a>
+<a name="index-ftp_002egnu_002eorg_002c-the-GNU-release-site"></a>
 
-<h3 class="section">11.3 Distribution on <code>ftp.gnu.org</code></h3>
-
-<p><a name="index-GNU-ftp-site-53"></a><a 
name="index-g_t_0040code_007bftp_002egnu_002eorg_007d_002c-the-GNU-release-site-54"></a>
-GNU packages are distributed through the directory <samp><span 
class="file">/gnu</span></samp> on
+<p>GNU packages are distributed through the directory 
&lsquo;<tt>/gnu</tt>&rsquo; on
 <code>ftp.gnu.org</code>, via both HTTP and FTP.  Each package should have a
 subdirectory named after the package, and all the distribution files
 for the package should go in that subdirectory.
+</p>
 
-<!-- If you have an interest in seeing the monthly download logs from the FTP 
-->
-<!-- site at @code{ftp.gnu.org} for your program, that is something that -->
-<!-- @email{ftp-upload@@gnu.org} can set up for you.  Please contact them if 
-->
-<!-- you are interested. -->
-   <p>See <a href="#Automated-FTP-Uploads">Automated FTP Uploads</a>, for 
procedural details of putting new
+<p>See <a href="#Automated-FTP-Uploads">Automated FTP Uploads</a>, for 
procedural details of putting new
 versions on <code>ftp.gnu.org</code>.
-
-<div class="node">
+</p>
+<hr>
 <a name="Test-Releases"></a>
-<p><hr>
-Next:&nbsp;<a rel="next" accesskey="n" href="#Automated-FTP-Uploads">Automated 
FTP Uploads</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" 
href="#Distribution-on-ftp_002egnu_002eorg">Distribution on ftp.gnu.org</a>,
-Up:&nbsp;<a rel="up" accesskey="u" href="#Distributions">Distributions</a>
-
-</div>
+<div class="header">
+<p>
+Next: <a href="#Automated-FTP-Uploads" accesskey="n" rel="next">Automated FTP 
Uploads</a>, Previous: <a href="#Distribution-on-ftp_002egnu_002eorg" 
accesskey="p" rel="previous">Distribution on ftp.gnu.org</a>, Up: <a 
href="#Distributions" accesskey="u" rel="up">Distributions</a> &nbsp; [<a 
href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a 
href="#Index" title="Index" rel="index">Index</a>]</p>
+</div>
+<a name="Test-Releases-1"></a>
+<h2 class="section">11.4 Test Releases</h2>
+<a name="index-test-releases"></a>
+<a name="index-beta-releases"></a>
+<a name="index-pretest-releases"></a>
 
-<h3 class="section">11.4 Test Releases</h3>
-
-<p><a name="index-test-releases-55"></a><a 
name="index-beta-releases-56"></a><a name="index-pretest-releases-57"></a>
-<a 
name="index-g_t_0040code_007balpha_002egnu_002eorg_007d_002c-test-release-site-58"></a>When
 you release a greatly changed new major version of a program, you
+<a name="index-alpha_002egnu_002eorg_002c-test-release-site"></a>
+<p>When you release a greatly changed new major version of a program, you
 might want to do so as a pretest.  This means that you make a tar file,
 but send it only to a group of volunteers that you have recruited.  (Use
 a suitable GNU mailing list/newsgroup to recruit them.)
-
-   <p>We normally use the server <code>alpha.gnu.org</code> for pretests and
+</p>
+<p>We normally use the server <code>alpha.gnu.org</code> for pretests and
 prerelease versions.  See <a href="#Automated-FTP-Uploads">Automated FTP 
Uploads</a>, for procedural details
 of putting new versions on <code>alpha.gnu.org</code>.
-
-   <p>Once a program gets to be widely used and people expect it to work
+</p>
+<p>Once a program gets to be widely used and people expect it to work
 solidly, it is a good idea to do pretest releases before each 
&ldquo;real&rdquo;
 release.
-
-   <p>There are two ways of handling version numbers for pretest versions. 
+</p>
+<p>There are two ways of handling version numbers for pretest versions.
 One method is to treat them as versions preceding the release you are going
 to make.
-
-   <p>In this method, if you are about to release version 4.6 but you want
+</p>
+<p>In this method, if you are about to release version 4.6 but you want
 to do a pretest first, call it 4.5.90.  If you need a second pretest,
 call it 4.5.91, and so on.  If you are really unlucky and ten pretests
 are not enough, after 4.5.99 you could advance to 4.5.990 and so on. 
 (You could also use 4.5.100, but 990 has the advantage of sorting in
 the right order.)
-
-   <p>The other method is to attach a date to the release number that is
+</p>
+<p>The other method is to attach a date to the release number that is
 coming.  For a pretest for version 4.6, made on Dec 10, 2002, this
 would be 4.6.20021210.  A second pretest made the same day could be
 4.6.20021210.1.
-
-   <p>For development snapshots that are not formal pretests, using just
+</p>
+<p>For development snapshots that are not formal pretests, using just
 the date without the version numbers is ok too.
-
-   <p>One thing that you should never do is to release a pretest with the same
+</p>
+<p>One thing that you should never do is to release a pretest with the same
 version number as the planned real release.  Many people will look only
 at the version number (in the tar file name, in the directory name that
 it unpacks into, or wherever they can find it) to determine whether a
 tar file is the latest version.  People might look at the test release
 in this way and mistake it for the real release.  Therefore, always
 change the number when you release changed code.
+</p>
 
-<div class="node">
+<hr>
 <a name="Automated-FTP-Uploads"></a>
-<p><hr>
-Next:&nbsp;<a rel="next" accesskey="n" href="#Announcements">Announcements</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" href="#Test-Releases">Test 
Releases</a>,
-Up:&nbsp;<a rel="up" accesskey="u" href="#Distributions">Distributions</a>
-
+<div class="header">
+<p>
+Next: <a href="#Announcements" accesskey="n" rel="next">Announcements</a>, 
Previous: <a href="#Test-Releases" accesskey="p" rel="previous">Test 
Releases</a>, Up: <a href="#Distributions" accesskey="u" 
rel="up">Distributions</a> &nbsp; [<a href="#SEC_Contents" title="Table of 
contents" rel="contents">Contents</a>][<a href="#Index" title="Index" 
rel="index">Index</a>]</p>
 </div>
+<a name="Automated-FTP-Uploads-1"></a>
+<h2 class="section">11.5 Automated FTP Uploads</h2>
 
-<h3 class="section">11.5 Automated FTP Uploads</h3>
-
-<p><a name="index-ftp-uploads_002c-automated-59"></a>In order to upload new 
releases to <code>ftp.gnu.org</code> or
+<a name="index-ftp-uploads_002c-automated"></a>
+<p>In order to upload new releases to <code>ftp.gnu.org</code> or
 <code>alpha.gnu.org</code>, you first need to register the necessary
 information.  Then, you can perform uploads yourself, with no
 intervention needed by the system administrators.
-
-   <p>The general idea is that releases should be crytographically signed
+</p>
+<p>The general idea is that releases should be crytographically signed
 before they are made publicly available.
+</p>
+<table class="menu" border="0" cellspacing="0">
+<tr><td align="left" valign="top">&bull; <a 
href="#Automated-Upload-Registration" accesskey="1">Automated Upload 
Registration</a>:</td><td>&nbsp;&nbsp;</td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a href="#Automated-Upload-Procedure" 
accesskey="2">Automated Upload Procedure</a>:</td><td>&nbsp;&nbsp;</td><td 
align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a 
href="#FTP-Upload-Directive-File-_002d-v1_002e1" accesskey="3">FTP Upload 
Directive File - v1.1</a>:</td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a 
href="#FTP-Upload-Directive-File-_002d-v1_002e0" accesskey="4">FTP Upload 
Directive File - v1.0</a>:</td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">
+</td></tr>
+</table>
 
-<ul class="menu">
-<li><a accesskey="1" href="#Automated-Upload-Registration">Automated Upload 
Registration</a>
-<li><a accesskey="2" href="#Automated-Upload-Procedure">Automated Upload 
Procedure</a>
-<li><a accesskey="3" href="#FTP-Upload-Directive-File-_002d-v1_002e1">FTP 
Upload Directive File - v1.1</a>
-<li><a accesskey="4" href="#FTP-Upload-Directive-File-_002d-v1_002e0">FTP 
Upload Directive File - v1.0</a>
-</ul>
 
-<div class="node">
+<hr>
 <a name="Automated-Upload-Registration"></a>
-<p><hr>
-Next:&nbsp;<a rel="next" accesskey="n" 
href="#Automated-Upload-Procedure">Automated Upload Procedure</a>,
-Up:&nbsp;<a rel="up" accesskey="u" href="#Automated-FTP-Uploads">Automated FTP 
Uploads</a>
-
+<div class="header">
+<p>
+Next: <a href="#Automated-Upload-Procedure" accesskey="n" rel="next">Automated 
Upload Procedure</a>, Up: <a href="#Automated-FTP-Uploads" accesskey="u" 
rel="up">Automated FTP Uploads</a> &nbsp; [<a href="#SEC_Contents" title="Table 
of contents" rel="contents">Contents</a>][<a href="#Index" title="Index" 
rel="index">Index</a>]</p>
 </div>
+<a name="Automated-Upload-Registration-1"></a>
+<h3 class="subsection">11.5.1 Automated Upload Registration</h3>
 
-<h4 class="subsection">11.5.1 Automated Upload Registration</h4>
+<a name="index-registration-for-uploads"></a>
+<a name="index-uploads_002c-registration-for"></a>
 
-<p><a name="index-registration-for-uploads-60"></a><a 
name="index-uploads_002c-registration-for-61"></a>
-Here is how to register your information so you can perform uploads
+<p>Here is how to register your information so you can perform uploads
 for your GNU package:
-
-     <ol type=1 start=1>
-
-     <li>Create an account for yourself at <a 
href="http://savannah.gnu.org";>http://savannah.gnu.org</a>, if
-you don't already have one.  By the way, this is also needed to
+</p>
+<ol>
+<li> Create an account for yourself at <a 
href="http://savannah.gnu.org";>http://savannah.gnu.org</a>, if
+you don&rsquo;t already have one.  By the way, this is also needed to
 maintain the web pages at <a href="http://www.gnu.org";>http://www.gnu.org</a> 
for your project
 (see <a href="#Web-Pages">Web Pages</a>).
 
-     <li>In the &lsquo;<samp><span class="samp">My Account 
Conf</span></samp>&rsquo; page on <code>savannah</code>, upload the GPG
-key you will use to sign your packages.  If you haven't created one
+</li><li> In the &lsquo;<samp>My Account Conf</samp>&rsquo; page on 
<code>savannah</code>, upload the GPG
+key you will use to sign your packages.  If you haven&rsquo;t created one
 before, you can do so with the command <code>gpg --gen-key</code> (you can
 accept all the default answers to its questions).
 
-     <p>Optional but recommended: Send your key to a GPG public key server:
-<code>gpg --keyserver keys.gnupg.net --send-keys </code><var>keyid</var>, where
+<p>Optional but recommended: Send your key to a GPG public key server:
+<code>gpg --keyserver keys.gnupg.net --send-keys <var>keyid</var></code>, where
 <var>keyid</var> is the eight hex digits reported by <code>gpg
 --list-public-keys</code> on the <code>pub</code> line before the date.  For 
full
 information about GPG, see <a 
href="http://www.gnu.org/software/gpg";>http://www.gnu.org/software/gpg</a>.
-
-     <li>Compose a message with the following items in some 
<var>msgfile</var>. 
-Then GPG-sign it by running <code>gpg --clearsign </code><var>msgfile</var>, 
and
-finally email the resulting <samp><var>msgfile</var><span 
class="file">.asc</span></samp>), to
+</p>
+</li><li> Compose a message with the following items in some 
<var>msgfile</var>.
+Then GPG-sign it by running <code>gpg --clearsign <var>msgfile</var></code>, 
and
+finally email the resulting &lsquo;<tt><var>msgfile</var>.asc</tt>&rsquo;), to
 <a href="mailto:address@hidden";>address@hidden</a>.
 
-          <ol type=1 start=1>
-<li>Name of package(s) that you are the maintainer for, your
+<ol>
+<li> Name of package(s) that you are the maintainer for, your
 preferred email address, and your Savannah username.
 
-          <li>An ASCII armored copy of your GPG key, as an attachment.  
(&lsquo;<samp><span class="samp">gpg
---export -a </span><var>your_key_id</var><span class="samp"> 
&gt;mykey.asc</span></samp>&rsquo; should give you this.)
+</li><li> An ASCII armored copy of your GPG key, as an attachment.  
(&lsquo;<samp>gpg
+--export -a <var>your_key_id</var> &gt;mykey.asc</samp>&rsquo; should give you 
this.)
 
-          <li>A list of names and preferred email addresses of other 
individuals you
+</li><li> A list of names and preferred email addresses of other individuals 
you
 authorize to make releases for which packages, if any (in the case that you
-don't make all releases yourself).
+don&rsquo;t make all releases yourself).
 
-          <li>ASCII armored copies of GPG keys for any individuals listed in 
(3).
-          </ol>
-        </ol>
+</li><li> ASCII armored copies of GPG keys for any individuals listed in (3).
+</li></ol>
+</li></ol>
 
-   <p>The administrators will acknowledge your message when they have added
+<p>The administrators will acknowledge your message when they have added
 the proper GPG keys as authorized to upload files for the
 corresponding packages.
-
-   <p>The upload system will email receipts to the given email addresses
+</p>
+<p>The upload system will email receipts to the given email addresses
 when an upload is made, either successfully or unsuccessfully.
+</p>
 
-<div class="node">
+<hr>
 <a name="Automated-Upload-Procedure"></a>
-<p><hr>
-Next:&nbsp;<a rel="next" accesskey="n" 
href="#FTP-Upload-Directive-File-_002d-v1_002e1">FTP Upload Directive File - 
v1.1</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" 
href="#Automated-Upload-Registration">Automated Upload Registration</a>,
-Up:&nbsp;<a rel="up" accesskey="u" href="#Automated-FTP-Uploads">Automated FTP 
Uploads</a>
-
+<div class="header">
+<p>
+Next: <a href="#FTP-Upload-Directive-File-_002d-v1_002e1" accesskey="n" 
rel="next">FTP Upload Directive File - v1.1</a>, Previous: <a 
href="#Automated-Upload-Registration" accesskey="p" rel="previous">Automated 
Upload Registration</a>, Up: <a href="#Automated-FTP-Uploads" accesskey="u" 
rel="up">Automated FTP Uploads</a> &nbsp; [<a href="#SEC_Contents" title="Table 
of contents" rel="contents">Contents</a>][<a href="#Index" title="Index" 
rel="index">Index</a>]</p>
 </div>
+<a name="Automated-Upload-Procedure-1"></a>
+<h3 class="subsection">11.5.2 Automated Upload Procedure</h3>
 
-<h4 class="subsection">11.5.2 Automated Upload Procedure</h4>
+<a name="index-uploads"></a>
 
-<p><a name="index-uploads-62"></a>
-Once you have registered your information as described in the previous
+<p>Once you have registered your information as described in the previous
 section, you will be able to do ftp uploads for yourself using the
 following procedure.
-
-   <p>For each upload destined for <code>ftp.gnu.org</code> or
-<code>alpha.gnu.org</code>, three files (a <dfn>triplet</dfn>) need to be
+</p>
+<p>For each upload destined for <code>ftp.gnu.org</code> or
+<code>alpha.gnu.org</code>, three files (a <em>triplet</em>) need to be
 uploaded via ftp to the host <code>ftp-upload.gnu.org</code>.
+</p>
+<ol>
+<li> The file to be distributed; for example, 
&lsquo;<tt>foo.tar.gz</tt>&rsquo;.
+
+</li><li> Detached GPG binary signature file for (1); for example,
+&lsquo;<tt>foo.tar.gz.sig</tt>&rsquo;.  Make this with &lsquo;<samp>gpg -b 
foo.tar.gz</samp>&rsquo;.
+
+</li><li> A clearsigned <em>directive file</em>; for example,
+&lsquo;<tt>foo.tar.gz.directive.asc</tt>&rsquo;.  Make this by preparing the 
plain
+text file &lsquo;<tt>foo.tar.gz.directive</tt>&rsquo; and then run 
&lsquo;<samp>gpg
+--clearsign foo.tar.gz.directive</samp>&rsquo;.  See <a 
href="#FTP-Upload-Directive-File-_002d-v1_002e1">FTP Upload Directive File -
+v1.1</a>, for the contents of the directive file.
+</li></ol>
 
-     <ol type=1 start=1>
-<li>The file to be distributed; for example, <samp><span 
class="file">foo.tar.gz</span></samp>.
-
-     <li>Detached GPG binary signature file for (1); for example,
-<samp><span class="file">foo.tar.gz.sig</span></samp>.  Make this with 
&lsquo;<samp><span class="samp">gpg -b foo.tar.gz</span></samp>&rsquo;.
-
-     <li>A clearsigned <dfn>directive file</dfn>; for example,
-<samp><span class="file">foo.tar.gz.directive.asc</span></samp>.  Make this by 
preparing the plain
-text file <samp><span class="file">foo.tar.gz.directive</span></samp> and then 
run &lsquo;<samp><span class="samp">gpg
---clearsign foo.tar.gz.directive</span></samp>&rsquo;.  See <a 
href="#FTP-Upload-Directive-File-_002d-v1_002e1">FTP Upload Directive File - 
v1.1</a>, for the contents of the directive file.
-        </ol>
-
-   <p>The names of the files are important. The signature file must have the
+<p>The names of the files are important. The signature file must have the
 same name as the file to be distributed, with an additional
-<samp><span class="file">.sig</span></samp> extension. The directive file must 
have the same name as
-the file to be distributed, with an additional <samp><span 
class="file">.directive.asc</span></samp>
+&lsquo;<tt>.sig</tt>&rsquo; extension. The directive file must have the same 
name as
+the file to be distributed, with an additional 
&lsquo;<tt>.directive.asc</tt>&rsquo;
 extension. If you do not follow this naming convention, the upload
 <em>will not be processed</em>.
-
-   <p>Since v1.1 of the upload script, it is also possible to upload a
-clearsigned directive file on its own (no accompanying <samp><span 
class="file">.sig</span></samp> or
+</p>
+<p>Since v1.1 of the upload script, it is also possible to upload a
+clearsigned directive file on its own (no accompanying 
&lsquo;<tt>.sig</tt>&rsquo; or
 any other file) to perform certain operations on the server. 
 See <a href="#FTP-Upload-Directive-File-_002d-v1_002e1">FTP Upload Directive 
File - v1.1</a>, for more information.
-
-   <p>Upload the file(s) via anonymous ftp to <code>ftp-upload.gnu.org</code>. 
If
+</p>
+<p>Upload the file(s) via anonymous ftp to <code>ftp-upload.gnu.org</code>. If
 the upload is destined for <code>ftp.gnu.org</code>, place the file(s) in
-the <samp><span class="file">/incoming/ftp</span></samp> directory. If the 
upload is destined for
-<code>alpha.gnu.org</code>, place the file(s) in the <samp><span 
class="file">/incoming/alpha</span></samp>
+the &lsquo;<tt>/incoming/ftp</tt>&rsquo; directory. If the upload is destined 
for
+<code>alpha.gnu.org</code>, place the file(s) in the 
&lsquo;<tt>/incoming/alpha</tt>&rsquo;
 directory.
-
-   <p>Uploads are processed every five minutes.  Uploads that are in
+</p>
+<p>Uploads are processed every five minutes.  Uploads that are in
 progress while the upload processing script is running are handled
 properly, so do not worry about the timing of your upload.  Uploaded
 files that belong to an incomplete triplet are deleted automatically
 after 24 hours.
-
-   <p>Your designated upload email addresses (see <a 
href="#Automated-Upload-Registration">Automated Upload Registration</a>)
+</p>
+<p>Your designated upload email addresses (see <a 
href="#Automated-Upload-Registration">Automated Upload Registration</a>)
 are sent a message if there are any problems processing an upload for your
 package. You also receive a message when your upload has been successfully
 processed.
-
-   <p>One automated way to create and transfer the necessary files is to use
+</p>
+<p>One automated way to create and transfer the necessary files is to use
 the <code>gnupload</code> script, which is available from the
-<samp><span class="file">build-aux/</span></samp> directory of the 
<code>gnulib</code> project at
+&lsquo;<tt>build-aux/</tt>&rsquo; directory of the <code>gnulib</code> project 
at
 <a 
href="http://savannah.gnu.org/projects/gnulib";>http://savannah.gnu.org/projects/gnulib</a>.
  <code>gnupload</code> can
 also remove uploaded files.  Run <code>gnupload --help</code> for a
 description and examples.
-
-   <p><code>gnupload</code> uses the <code>ncftpput</code> program to do the 
actual
-transfers; if you don't happen to have the <code>ncftp</code> package
-installed, the <code>ncftpput-ftp</code> script in the <samp><span 
class="file">build-aux/</span></samp>
+</p>
+<p><code>gnupload</code> uses the <code>ncftpput</code> program to do the 
actual
+transfers; if you don&rsquo;t happen to have the <code>ncftp</code> package
+installed, the <code>ncftpput-ftp</code> script in the 
&lsquo;<tt>build-aux/</tt>&rsquo;
 directory of <code>gnulib</code> serves as a replacement which uses plain
 command line <code>ftp</code>.
-
-   <p>If you have difficulties with an upload, email
+</p>
+<p>If you have difficulties with an upload, email
 <a href="mailto:address@hidden";>address@hidden</a>.
+</p>
 
-<div class="node">
-<a name="FTP-Upload-Directive-File---v1.1"></a>
+<hr>
 <a name="FTP-Upload-Directive-File-_002d-v1_002e1"></a>
-<p><hr>
-Next:&nbsp;<a rel="next" accesskey="n" 
href="#FTP-Upload-Directive-File-_002d-v1_002e0">FTP Upload Directive File - 
v1.0</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" 
href="#Automated-Upload-Procedure">Automated Upload Procedure</a>,
-Up:&nbsp;<a rel="up" accesskey="u" href="#Automated-FTP-Uploads">Automated FTP 
Uploads</a>
-
-</div>
-
-<h4 class="subsection">11.5.3 FTP Upload Directive File - v1.1</h4>
-
-<p>The directive file name must end in <samp><span 
class="file">directive.asc</span></samp>.
-
-   <p>When part of a triplet, the directive file must always contain the
+<div class="header">
+<p>
+Next: <a href="#FTP-Upload-Directive-File-_002d-v1_002e0" accesskey="n" 
rel="next">FTP Upload Directive File - v1.0</a>, Previous: <a 
href="#Automated-Upload-Procedure" accesskey="p" rel="previous">Automated 
Upload Procedure</a>, Up: <a href="#Automated-FTP-Uploads" accesskey="u" 
rel="up">Automated FTP Uploads</a> &nbsp; [<a href="#SEC_Contents" title="Table 
of contents" rel="contents">Contents</a>][<a href="#Index" title="Index" 
rel="index">Index</a>]</p>
+</div>
+<a name="FTP-Upload-Directive-File-_002d-v1_002e1-1"></a>
+<h3 class="subsection">11.5.3 FTP Upload Directive File - v1.1</h3>
+
+<p>The directive file name must end in &lsquo;<tt>directive.asc</tt>&rsquo;.
+</p>
+<p>When part of a triplet, the directive file must always contain the
 directives <code>version</code>, <code>directory</code> and 
<code>filename</code>, as
-described. In addition, a 'comment' directive is allowed.
-
-   <p>The <code>version</code> directive must always have the value 
&lsquo;<samp><span class="samp">1.1</span></samp>&rsquo;.
-
-   <p>The <code>directory</code> directive specifies the final destination
-directory where the uploaded file and its <samp><span 
class="file">.sig</span></samp> companion are to
+described. In addition, a &rsquo;comment&rsquo; directive is allowed.
+</p>
+<p>The <code>version</code> directive must always have the value 
&lsquo;<samp>1.1</samp>&rsquo;.
+</p>
+<p>The <code>directory</code> directive specifies the final destination
+directory where the uploaded file and its &lsquo;<tt>.sig</tt>&rsquo; 
companion are to
 be placed.
-
-   <p>The <code>filename</code> directive must contain the name of the file to 
be
+</p>
+<p>The <code>filename</code> directive must contain the name of the file to be
 distributed (item&nbsp;(1) above).
-
-   <p>For example, as part of an uploaded triplet, a
-<samp><span class="file">foo.tar.gz.directive.asc</span></samp> file might 
contain these lines (before
+</p>
+<p>For example, as part of an uploaded triplet, a
+&lsquo;<tt>foo.tar.gz.directive.asc</tt>&rsquo; file might contain these lines 
(before
 being gpg clearsigned):
-
-<pre class="example">     version: 1.1
-     directory: bar/v1
-     filename: foo.tar.gz
-     comment: hello world!
-</pre>
-   <p>This directory line indicates that <samp><span 
class="file">foo.tar.gz</span></samp> and
-<samp><span class="file">foo.tar.gz.sig</span></samp> are part of package 
<code>bar</code>.  If you uploaded
-this triplet to <samp><span class="file">/incoming/ftp</span></samp> and the 
system positively
-authenticates the signatures, the files <samp><span 
class="file">foo.tar.gz</span></samp> and
-<samp><span class="file">foo.tar.gz.sig</span></samp> will be placed in the 
directory
-<samp><span class="file">gnu/bar/v1</span></samp> of the 
<code>ftp.gnu.org</code> site.
-
-   <p>The directive file can be used to create currently non-existent
+</p>
+<div class="example">
+<pre class="example">version: 1.1
+directory: bar/v1
+filename: foo.tar.gz
+comment: hello world!
+</pre></div>
+
+<p>This directory line indicates that &lsquo;<tt>foo.tar.gz</tt>&rsquo; and
+&lsquo;<tt>foo.tar.gz.sig</tt>&rsquo; are part of package <code>bar</code>.  
If you uploaded
+this triplet to &lsquo;<tt>/incoming/ftp</tt>&rsquo; and the system positively
+authenticates the signatures, the files &lsquo;<tt>foo.tar.gz</tt>&rsquo; and
+&lsquo;<tt>foo.tar.gz.sig</tt>&rsquo; will be placed in the directory
+&lsquo;<tt>gnu/bar/v1</tt>&rsquo; of the <code>ftp.gnu.org</code> site.
+</p>
+<p>The directive file can be used to create currently non-existent
 directory trees, as long as they are under the package directory for
 your package (in the example above, that is <code>bar</code>).
-
-   <p>If you upload a file that already exists in the FTP directory, the
+</p>
+<p>If you upload a file that already exists in the FTP directory, the
 original will simply be archived and replaced with the new upload.
-
-<h4 class="subheading">Standalone directives</h4>
+</p>
+<a name="Standalone-directives"></a>
+<h3 class="subheading">Standalone directives</h3>
 
 <p>When uploaded by itself, the directive file must contain one or more
 of the directives <code>symlink</code>, <code>rmsymlink</code> or 
<code>archive</code>,
 in addition to the obligatory <code>directory</code> and <code>version</code>
 directives.  A <code>filename</code> directive is not allowed, and a
 <code>comment</code> directive remains optional.
-
-   <p>If you use more than one directive, the directives are executed in the
+</p>
+<p>If you use more than one directive, the directives are executed in the
 sequence they are specified in.  If a directive results in an error,
 further execution of the upload is aborted.
-
-   <p>Removing a symbolic link (with <code>rmsymlink</code>) which does not 
exist
+</p>
+<p>Removing a symbolic link (with <code>rmsymlink</code>) which does not exist
 results in an error.  However, attempting to create a symbolic link
 that already exists (with <code>symlink</code>) is not an error.  In this
-case <code>symlink</code> behaves like the command <samp><span 
class="command">ln -s -f</span></samp>: any
+case <code>symlink</code> behaves like the command <code>ln -s -f</code>: any
 existing symlink is removed before creating the link.  (But an
 existing regular file or directory is not removed.)
+</p>
+<p>Here are a few examples.  The first removes a symlink:
+</p>
+<div class="example">
+<pre class="example">version: 1.1
+directory: bar/v1
+rmsymlink: foo-latest.tgz
+comment: remove a symlink
+</pre></div>
+
+<p>Archive an old file, taking it offline:
+</p>
+<div class="example">
+<pre class="example">version: 1.1
+directory: bar/v1
+archive: foo-1.1.tar.gz
+comment: archive an old file; it will not be
+comment: available through FTP any more.
+</pre></div>
+
+<p>Archive an old directory (with all contents), taking it offline:
+</p>
+<div class="example">
+<pre class="example">version: 1.1
+directory: bar/v1
+archive: foo
+comment: archive an old directory; it and its entire
+comment: contents will not be available through FTP anymore
+</pre></div>
+
+<p>Create a new symlink:
+</p>
+<div class="example">
+<pre class="example">version: 1.1
+directory: bar/v1
+symlink: foo-1.2.tar.gz foo-latest.tgz
+comment: create a new symlink
+</pre></div>
+
+<p>Do everything at once:
+</p>
+<div class="example">
+<pre class="example">version: 1.1
+directory: bar/v1
+rmsymlink: foo-latest.tgz
+symlink: foo-1.2.tar.gz foo-latest.tgz
+archive: foo-1.1.tar.gz
+comment: now do everything at once
+</pre></div>
 
-   <p>Here are a few examples.  The first removes a symlink:
 
-<pre class="example">     version: 1.1
-     directory: bar/v1
-     rmsymlink: foo-latest.tgz
-     comment: remove a symlink
-</pre>
-   <p class="noindent">Archive an old file, taking it offline:
-
-<pre class="example">     version: 1.1
-     directory: bar/v1
-     archive: foo-1.1.tar.gz
-     comment: archive an old file; it will not be
-     comment: available through FTP any more.
-</pre>
-   <p class="noindent">Archive an old directory (with all contents), taking it 
offline:
-
-<pre class="example">     version: 1.1
-     directory: bar/v1
-     archive: foo
-     comment: archive an old directory; it and its entire
-     comment: contents will not be available through FTP anymore
-</pre>
-   <p class="noindent">Create a new symlink:
-
-<pre class="example">     version: 1.1
-     directory: bar/v1
-     symlink: foo-1.2.tar.gz foo-latest.tgz
-     comment: create a new symlink
-</pre>
-   <p class="noindent">Do everything at once:
-
-<pre class="example">     version: 1.1
-     directory: bar/v1
-     rmsymlink: foo-latest.tgz
-     symlink: foo-1.2.tar.gz foo-latest.tgz
-     archive: foo-1.1.tar.gz
-     comment: now do everything at once
-</pre>
-   <div class="node">
-<a name="FTP-Upload-Directive-File---v1.0"></a>
+<hr>
 <a name="FTP-Upload-Directive-File-_002d-v1_002e0"></a>
-<p><hr>
-Previous:&nbsp;<a rel="previous" accesskey="p" 
href="#FTP-Upload-Directive-File-_002d-v1_002e1">FTP Upload Directive File - 
v1.1</a>,
-Up:&nbsp;<a rel="up" accesskey="u" href="#Automated-FTP-Uploads">Automated FTP 
Uploads</a>
-
+<div class="header">
+<p>
+Previous: <a href="#FTP-Upload-Directive-File-_002d-v1_002e1" accesskey="p" 
rel="previous">FTP Upload Directive File - v1.1</a>, Up: <a 
href="#Automated-FTP-Uploads" accesskey="u" rel="up">Automated FTP Uploads</a> 
&nbsp; [<a href="#SEC_Contents" title="Table of contents" 
rel="contents">Contents</a>][<a href="#Index" title="Index" 
rel="index">Index</a>]</p>
 </div>
+<a name="FTP-Upload-Directive-File-_002d-v1_002e0-1"></a>
+<h3 class="subsection">11.5.4 FTP Upload Directive File - v1.0</h3>
 
-<h4 class="subsection">11.5.4 FTP Upload Directive File - v1.0</h4>
-
-<p><dfn>As of June 2006, the upload script is running in compatibility
+<p><em>As of June 2006, the upload script is running in compatibility
 mode, allowing uploads with either version&nbsp;1.1 or
 version&nbsp;1.0 of the directive file syntax.  Support for v1.0
 uploads will be phased out by the end of 2006, so please upgrade
-to&nbsp;v1.1.</dfn>
-
-   <p>The directive file should contain one line, excluding the clearsigned
+to&nbsp;v1.1.</em>
+</p>
+<p>The directive file should contain one line, excluding the clearsigned
 data GPG that inserts, which specifies the final destination directory
 where items (1) and (2) are to be placed.
-
-   <p>For example, the <samp><span 
class="file">foo.tar.gz.directive.asc</span></samp> file might contain the
+</p>
+<p>For example, the &lsquo;<tt>foo.tar.gz.directive.asc</tt>&rsquo; file might 
contain the
 single line:
-
-<pre class="example">     directory: bar/v1
-</pre>
-   <p>This directory line indicates that <samp><span 
class="file">foo.tar.gz</span></samp> and
-<samp><span class="file">foo.tar.gz.sig</span></samp> are part of package 
<code>bar</code>.  If you were to
-upload the triplet to <samp><span class="file">/incoming/ftp</span></samp>, 
and the system can
+</p>
+<div class="example">
+<pre class="example">directory: bar/v1
+</pre></div>
+
+<p>This directory line indicates that &lsquo;<tt>foo.tar.gz</tt>&rsquo; and
+&lsquo;<tt>foo.tar.gz.sig</tt>&rsquo; are part of package <code>bar</code>.  
If you were to
+upload the triplet to &lsquo;<tt>/incoming/ftp</tt>&rsquo;, and the system can
 positively authenticate the signatures, then the files
-<samp><span class="file">foo.tar.gz</span></samp> and <samp><span 
class="file">foo.tar.gz.sig</span></samp> will be placed in the
-directory <samp><span class="file">gnu/bar/v1</span></samp> of the 
<code>ftp.gnu.org</code> site.
-
-   <p>The directive file can be used to create currently non-existent
+&lsquo;<tt>foo.tar.gz</tt>&rsquo; and &lsquo;<tt>foo.tar.gz.sig</tt>&rsquo; 
will be placed in the
+directory &lsquo;<tt>gnu/bar/v1</tt>&rsquo; of the <code>ftp.gnu.org</code> 
site.
+</p>
+<p>The directive file can be used to create currently non-existent
 directory trees, as long as they are under the package directory for
 your package (in the example above, that is <code>bar</code>).
+</p>
 
-<div class="node">
+<hr>
 <a name="Announcements"></a>
-<p><hr>
-Previous:&nbsp;<a rel="previous" accesskey="p" 
href="#Automated-FTP-Uploads">Automated FTP Uploads</a>,
-Up:&nbsp;<a rel="up" accesskey="u" href="#Distributions">Distributions</a>
-
-</div>
+<div class="header">
+<p>
+Previous: <a href="#Automated-FTP-Uploads" accesskey="p" 
rel="previous">Automated FTP Uploads</a>, Up: <a href="#Distributions" 
accesskey="u" rel="up">Distributions</a> &nbsp; [<a href="#SEC_Contents" 
title="Table of contents" rel="contents">Contents</a>][<a href="#Index" 
title="Index" rel="index">Index</a>]</p>
+</div>
+<a name="Announcing-Releases"></a>
+<h2 class="section">11.6 Announcing Releases</h2>
+<a name="index-announcements"></a>
 
-<h3 class="section">11.6 Announcing Releases</h3>
-
-<p><a name="index-announcements-63"></a>
-<a name="index-g_t_0040code_007binfo_002dgnu_007d-mailing-list-64"></a>When 
you have a new release, please make an announcement.  For
+<a name="index-info_002dgnu-mailing-list"></a>
+<p>When you have a new release, please make an announcement.  For
 official new releases, including those made just to fix bugs, we
 strongly recommend using the (moderated) general GNU announcements
 list, <a href="mailto:address@hidden";>address@hidden</a>.  Doing so makes it 
easier for users
 and developers to find the latest GNU releases.  On the other hand,
-please do not announce test releases on <code>info-gnu</code> unless it's a
+please do not announce test releases on <code>info-gnu</code> unless 
it&rsquo;s a
 highly unusual situation.
-
-   <p><a 
name="index-g_t_0040url_007bhttp_003a_002f_002fplanet_002egnu_002eorg_007d-65"></a><a
 name="index-Savannah_002c-news-area-66"></a>Please also post release 
announcements in the news section of your
+</p>
+<a name="index-http_003a_002f_002fplanet_002egnu_002eorg"></a>
+<a name="index-Savannah_002c-news-area"></a>
+<p>Please also post release announcements in the news section of your
 Savannah project site.  Here, it is fine to also write news entries
 for test releases and any other newsworthy events.  The news feeds
 from all GNU projects at savannah are aggregated at
 <a href="http://planet.gnu.org";>http://planet.gnu.org</a> (GNU Planet).  You 
can also post items
 directly, or arrange for feeds from other locations; see information
 on the GNU Planet web page.
-
-   <p><a 
name="index-announcement-mailing-list_002c-project_002dspecific-67"></a>You can 
maintain your own mailing list (typically
+</p>
+<a name="index-announcement-mailing-list_002c-project_002dspecific"></a>
+<p>You can maintain your own mailing list (typically
 <a 
href="mailto:info-<var>package</var>@gnu.org">info-<var>package</var>@gnu.org</a>)
 for announcements as well if you
 like.  For your own list, of course you decide as you see fit what
 events are worth announcing.  (See <a href="#Mail">Mail</a>, for setting this 
up, and
 more suggestions on handling mail for your package.)
-
-   <p><a name="index-contents-of-announcements-68"></a>When writing an 
announcement, please include the following:
-
-     <ul>
-<li>A very brief description (a few sentences at most) of the general
+</p>
+<a name="index-contents-of-announcements"></a>
+<p>When writing an announcement, please include the following:
+</p>
+<ul>
+<li> A very brief description (a few sentences at most) of the general
 purpose of your package.
 
-     <li>Your package's web page (normally
-&lt;<code>http://www.gnu.org/software/</code><var>package</var><code>/</code>&gt;).
+</li><li> Your package&rsquo;s web page (normally
+&lt;<code>http://www.gnu.org/software/<var>package</var>/</code>&gt;).
 
-     <li>Your package's download location (normally
-&lt;<code>http://ftp.gnu.org/gnu/</code><var>package</var><code>/</code>&gt;). 
 It is also
+</li><li> Your package&rsquo;s download location (normally
+&lt;<code>http://ftp.gnu.org/gnu/<var>package</var>/</code>&gt;).  It is also
 useful to mention the mirror list at
 <a 
href="http://www.gnu.org/order/ftp.html";>http://www.gnu.org/order/ftp.html</a>, 
and that
-<a 
href="http://ftpmirror.gnu.org/<var>package/</var>">http://ftpmirror.gnu.org/<var>package/</var></a>
 will automatically
+<a 
href="http://ftpmirror.gnu.org/package/";>http://ftpmirror.gnu.org/package/</a> 
will automatically
 redirect to a nearby mirror.
 
-     <li>The <tt>NEWS</tt> (see <a href="standards.html#NEWS-File">NEWS 
File</a>) for
+</li><li> The <tt>NEWS</tt> (see <a 
href="http://www.gnu.org/prep/standards/standards.html#NEWS-File";>NEWS File</a> 
in <cite>GNU Coding Standards</cite>) for
 the present release. 
-</ul>
-
-<div class="node">
-<a name="Web-Pages"></a>
-<p><hr>
-Next:&nbsp;<a rel="next" accesskey="n" 
href="#Ethical-and-Philosophical-Consideration">Ethical and Philosophical 
Consideration</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" 
href="#Distributions">Distributions</a>,
-Up:&nbsp;<a rel="up" accesskey="u" href="#Top">Top</a>
+</li></ul>
 
-</div>
 
-<h2 class="chapter">12 Web Pages</h2>
+<hr>
+<a name="Web-Pages"></a>
+<div class="header">
+<p>
+Next: <a href="#Ethical-and-Philosophical-Consideration" accesskey="n" 
rel="next">Ethical and Philosophical Consideration</a>, Previous: <a 
href="#Distributions" accesskey="p" rel="previous">Distributions</a>, Up: <a 
href="#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a href="#SEC_Contents" 
title="Table of contents" rel="contents">Contents</a>][<a href="#Index" 
title="Index" rel="index">Index</a>]</p>
+</div>
+<a name="Web-Pages-1"></a>
+<h1 class="chapter">12 Web Pages</h1>
+<a name="index-web-pages"></a>
 
-<p><a name="index-web-pages-69"></a>
-Please write web pages about your package, and install them on
+<p>Please write web pages about your package, and install them on
 <code>www.gnu.org</code>.  They should follow our usual standards for web
 pages (see <a 
href="http://www.gnu.org/server/fsf-html-style-sheet.html";>http://www.gnu.org/server/fsf-html-style-sheet.html</a>).
 
 The overall goals are to support a wide variety of browsers, to focus
 on information rather than flashy eye candy, and to keep the site
 simple and uniform.
-
-   <p>We encourage you to use the standard <code>www.gnu.org</code> template as
+</p>
+<p>We encourage you to use the standard <code>www.gnu.org</code> template as
 the basis for your pages:
 <a 
href="http://www.gnu.org/server/standards/boilerplate-source.html";>http://www.gnu.org/server/standards/boilerplate-source.html</a>.
-
-   <p>Some GNU packages have just simple web pages, but the more information
+</p>
+<p>Some GNU packages have just simple web pages, but the more information
 you provide, the better.  So please write as much as you usefully can,
 and put all of it on <code>www.gnu.org</code>.  However, pages that access
 databases (including mail archives and bug tracking) are an exception;
 set them up on whatever site is convenient for you, and make the pages
 on <code>www.gnu.org</code> link to that site.
+</p>
+<table class="menu" border="0" cellspacing="0">
+<tr><td align="left" valign="top">&bull; <a href="#Hosting-for-Web-Pages" 
accesskey="1">Hosting for Web Pages</a>:</td><td>&nbsp;&nbsp;</td><td 
align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a href="#Freedom-for-Web-Pages" 
accesskey="2">Freedom for Web Pages</a>:</td><td>&nbsp;&nbsp;</td><td 
align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a href="#Manuals-on-Web-Pages" 
accesskey="3">Manuals on Web Pages</a>:</td><td>&nbsp;&nbsp;</td><td 
align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a href="#CVS-Keywords-in-Web-Pages" 
accesskey="4">CVS Keywords in Web Pages</a>:</td><td>&nbsp;&nbsp;</td><td 
align="left" valign="top">
+</td></tr>
+</table>
 
-<ul class="menu">
-<li><a accesskey="1" href="#Hosting-for-Web-Pages">Hosting for Web Pages</a>
-<li><a accesskey="2" href="#Freedom-for-Web-Pages">Freedom for Web Pages</a>
-<li><a accesskey="3" href="#Manuals-on-Web-Pages">Manuals on Web Pages</a>
-<li><a accesskey="4" href="#CVS-Keywords-in-Web-Pages">CVS Keywords in Web 
Pages</a>
-</ul>
 
-<div class="node">
+<hr>
 <a name="Hosting-for-Web-Pages"></a>
-<p><hr>
-Next:&nbsp;<a rel="next" accesskey="n" href="#Freedom-for-Web-Pages">Freedom 
for Web Pages</a>,
-Up:&nbsp;<a rel="up" accesskey="u" href="#Web-Pages">Web Pages</a>
-
+<div class="header">
+<p>
+Next: <a href="#Freedom-for-Web-Pages" accesskey="n" rel="next">Freedom for 
Web Pages</a>, Up: <a href="#Web-Pages" accesskey="u" rel="up">Web Pages</a> 
&nbsp; [<a href="#SEC_Contents" title="Table of contents" 
rel="contents">Contents</a>][<a href="#Index" title="Index" 
rel="index">Index</a>]</p>
 </div>
-
-<h3 class="section">12.1 Hosting for Web Pages</h3>
+<a name="Hosting-for-Web-Pages-1"></a>
+<h2 class="section">12.1 Hosting for Web Pages</h2>
 
 <p>The best way to maintain the web pages for your project is to register
 the project on <code>savannah.gnu.org</code>.  Then you can edit the pages
 using CVS, using the separate &ldquo;web repository&rdquo; available on
 Savannah, which corresponds to
-&lt;<code>http://www.gnu.org/software/</code><var>package</var><code>/</code>&gt;.
  You can
+&lt;<code>http://www.gnu.org/software/<var>package</var>/</code>&gt;.  You can
 keep your source files there too (using any of a variety of version
 control systems), but you can use <code>savannah.gnu.org</code> only for
 your gnu.org web pages if you wish; simply register a &ldquo;web-only&rdquo;
 project.
-
-   <p>If you don't want to use that method, please talk with
+</p>
+<p>If you don&rsquo;t want to use that method, please talk with
 <a href="mailto:address@hidden";>address@hidden</a> about other possible 
methods.  For
 instance, you can mail them pages to install, if necessary.  But that
 is more work for them, so please use Savannah if you can.
-
-   <p>If you use Savannah, you can use a special file named <samp><span 
class="file">.symlinks</span></samp>
+</p>
+<p>If you use Savannah, you can use a special file named 
&lsquo;<tt>.symlinks</tt>&rsquo;
 in order to create symbolic links, which are not supported in CVS. 
 For details, see
 <a 
href="http://www.gnu.org/server/standards/README.webmastering.html#symlinks";>http://www.gnu.org/server/standards/README.webmastering.html#symlinks</a>.
+</p>
 
-<div class="node">
+<hr>
 <a name="Freedom-for-Web-Pages"></a>
-<p><hr>
-Next:&nbsp;<a rel="next" accesskey="n" href="#Manuals-on-Web-Pages">Manuals on 
Web Pages</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" 
href="#Hosting-for-Web-Pages">Hosting for Web Pages</a>,
-Up:&nbsp;<a rel="up" accesskey="u" href="#Web-Pages">Web Pages</a>
-
+<div class="header">
+<p>
+Next: <a href="#Manuals-on-Web-Pages" accesskey="n" rel="next">Manuals on Web 
Pages</a>, Previous: <a href="#Hosting-for-Web-Pages" accesskey="p" 
rel="previous">Hosting for Web Pages</a>, Up: <a href="#Web-Pages" 
accesskey="u" rel="up">Web Pages</a> &nbsp; [<a href="#SEC_Contents" 
title="Table of contents" rel="contents">Contents</a>][<a href="#Index" 
title="Index" rel="index">Index</a>]</p>
 </div>
-
-<h3 class="section">12.2 Freedom for Web Pages</h3>
+<a name="Freedom-for-Web-Pages-1"></a>
+<h2 class="section">12.2 Freedom for Web Pages</h2>
 
 <p>If you use a site other than <code>www.gnu.org</code>, please make sure that
 the site runs on free software alone.  (It is ok if the site uses
 unreleased custom software, since that is free in a trivial sense:
-there's only one user and it has the four freedoms.)  If the web site
+there&rsquo;s only one user and it has the four freedoms.)  If the web site
 for a GNU package runs on non-free software, the public will see this,
 and it will have the effect of granting legitimacy to the non-free
 program.
-
-   <p>If you use multiple sites, they should all follow that criterion. 
-Please don't link to a site that is about your package, which the
+</p>
+<p>If you use multiple sites, they should all follow that criterion.
+Please don&rsquo;t link to a site that is about your package, which the
 public might perceive as connected with it and reflecting the position
 of its developers, unless it follows that criterion.
-
-   <p>Historically, web pages for GNU packages did not include GIF images,
-because of patent problems (see <a 
href="#Ethical-and-Philosophical-Consideration">Ethical and Philosophical 
Consideration</a>).  Although the GIF patents expired in 2006, using GIF
+</p>
+<p>Historically, web pages for GNU packages did not include GIF images,
+because of patent problems (see <a 
href="#Ethical-and-Philosophical-Consideration">Ethical and Philosophical
+Consideration</a>).  Although the GIF patents expired in 2006, using GIF
 images is still not recommended, as the PNG and JPEG formats are
 generally superior.  See <a 
href="http://www.gnu.org/philosophy/gif.html";>http://www.gnu.org/philosophy/gif.html</a>.
+</p>
 
-<div class="node">
+<hr>
 <a name="Manuals-on-Web-Pages"></a>
-<p><hr>
-Next:&nbsp;<a rel="next" accesskey="n" href="#CVS-Keywords-in-Web-Pages">CVS 
Keywords in Web Pages</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" 
href="#Freedom-for-Web-Pages">Freedom for Web Pages</a>,
-Up:&nbsp;<a rel="up" accesskey="u" href="#Web-Pages">Web Pages</a>
-
+<div class="header">
+<p>
+Next: <a href="#CVS-Keywords-in-Web-Pages" accesskey="n" rel="next">CVS 
Keywords in Web Pages</a>, Previous: <a href="#Freedom-for-Web-Pages" 
accesskey="p" rel="previous">Freedom for Web Pages</a>, Up: <a 
href="#Web-Pages" accesskey="u" rel="up">Web Pages</a> &nbsp; [<a 
href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a 
href="#Index" title="Index" rel="index">Index</a>]</p>
 </div>
-
-<h3 class="section">12.3 Manuals on Web Pages</h3>
+<a name="Manuals-on-Web-Pages-1"></a>
+<h2 class="section">12.3 Manuals on Web Pages</h2>
 
 <p>The web pages for the package should include its manuals, in HTML,
 DVI, Info, PostScript, PDF, plain ASCII, and Texinfo format (source). 
 All of these can be generated automatically from the Texinfo source
 using Makeinfo and other programs.
-
-   <p>When there is only one manual, put it in a subdirectory called
-<samp><span class="file">manual</span></samp>; the file <samp><span 
class="file">manual/index.html</span></samp> should have a link to
+</p>
+<p>When there is only one manual, put it in a subdirectory called
+&lsquo;<tt>manual</tt>&rsquo;; the file 
&lsquo;<tt>manual/index.html</tt>&rsquo; should have a link to
 the manual in each of its forms.
-
-   <p>If the package has more than one manual, put each one in a
-subdirectory of <samp><span class="file">manual</span></samp>, set up 
<samp><span class="file">index.html</span></samp> in each
+</p>
+<p>If the package has more than one manual, put each one in a
+subdirectory of &lsquo;<tt>manual</tt>&rsquo;, set up 
&lsquo;<tt>index.html</tt>&rsquo; in each
 subdirectory to link to that manual in all its forms, and make
-<samp><span class="file">manual/index.html</span></samp> link to each manual 
through its subdirectory.
-
-   <p>See the section below for details on a script to make the job of
+&lsquo;<tt>manual/index.html</tt>&rsquo; link to each manual through its 
subdirectory.
+</p>
+<p>See the section below for details on a script to make the job of
 creating all these different formats and index pages easier.
-
-   <p>We would like to list all GNU manuals on the page
-<a href="http://www.gnu.org/manual";>http://www.gnu.org/manual</a>, so if yours 
isn't there, please send
+</p>
+<p>We would like to list all GNU manuals on the page
+<a href="http://www.gnu.org/manual";>http://www.gnu.org/manual</a>, so if yours 
isn&rsquo;t there, please send
 mail to <code>address@hidden</code>, asking them to add yours, and they
-will do so based on the contents of your <samp><span 
class="file">manual</span></samp> directory.
+will do so based on the contents of your &lsquo;<tt>manual</tt>&rsquo; 
directory.
+</p>
+<table class="menu" border="0" cellspacing="0">
+<tr><td align="left" valign="top">&bull; <a href="#Invoking-gendocs_002esh" 
accesskey="1">Invoking gendocs.sh</a>:</td><td>&nbsp;&nbsp;</td><td 
align="left" valign="top">
+</td></tr>
+</table>
 
-<ul class="menu">
-<li><a accesskey="1" href="#Invoking-gendocs_002esh">Invoking gendocs.sh</a>
-</ul>
 
-<div class="node">
-<a name="Invoking-gendocs.sh"></a>
+<hr>
 <a name="Invoking-gendocs_002esh"></a>
-<p><hr>
-Up:&nbsp;<a rel="up" accesskey="u" href="#Manuals-on-Web-Pages">Manuals on Web 
Pages</a>
-
-</div>
-
-<h4 class="subsection">12.3.1 Invoking <samp><span 
class="command">gendocs.sh</span></samp></h4>
+<div class="header">
+<p>
+Up: <a href="#Manuals-on-Web-Pages" accesskey="u" rel="up">Manuals on Web 
Pages</a> &nbsp; [<a href="#SEC_Contents" title="Table of contents" 
rel="contents">Contents</a>][<a href="#Index" title="Index" 
rel="index">Index</a>]</p>
+</div>
+<a name="Invoking-gendocs_002esh-1"></a>
+<h3 class="subsection">12.3.1 Invoking <code>gendocs.sh</code></h3>
+<a name="index-gendocs_002esh"></a>
+<a name="index-generating-documentation-output"></a>
 
-<p><a name="index-gendocs_002esh-70"></a><a 
name="index-generating-documentation-output-71"></a>
-The script <samp><span class="command">gendocs.sh</span></samp> eases the task 
of generating the
+<p>The script <code>gendocs.sh</code> eases the task of generating the
 Texinfo documentation output for your web pages
 section above.  It has a companion template file, used as the basis
 for the HTML index pages.  Both are available from the Texinfo CVS
 sources:
-
+</p>
+<div class="smallformat">
 <pre class="smallformat"><a 
href="http://savannah.gnu.org/cgi-bin/viewcvs/texinfo/texinfo/util/gendocs.sh";>http://savannah.gnu.org/cgi-bin/viewcvs/texinfo/texinfo/util/gendocs.sh</a>
 <a 
href="http://savannah.gnu.org/cgi-bin/viewcvs/texinfo/texinfo/util/gendocs_template";>http://savannah.gnu.org/cgi-bin/viewcvs/texinfo/texinfo/util/gendocs_template</a>
-</pre>
-   <p>There is also a minimalistic template, available from:
+</pre></div>
 
+<p>There is also a minimalistic template, available from:
+</p>
+<div class="smallformat">
 <pre class="smallformat"><a 
href="http://savannah.gnu.org/cgi-bin/viewcvs/texinfo/texinfo/util/gendocs_template_min";>http://savannah.gnu.org/cgi-bin/viewcvs/texinfo/texinfo/util/gendocs_template_min</a>
-</pre>
-   <p>Invoke the script like this, in the directory containing the Texinfo
+</pre></div>
+
+<p>Invoke the script like this, in the directory containing the Texinfo
 source:
+</p>
+<div class="smallexample">
+<pre class="smallexample">gendocs.sh --email <var>yourbuglist</var> 
<var>yourmanual</var> &quot;GNU <var>yourmanual</var> manual&quot;
+</pre></div>
 
-<pre class="smallexample">     gendocs.sh --email <var>yourbuglist</var> 
<var>yourmanual</var> "GNU <var>yourmanual</var> manual"
-</pre>
-   <p class="noindent">where <var>yourmanual</var> is the short name for your 
package
+<p>where <var>yourmanual</var> is the short name for your package
 and <var>yourbuglist</var> is the email address for bug reports (typically
-<code>bug-</code><var>package</var><code>@gnu.org</code>).  The script 
processes the file
-<samp><var>yourmanual</var><span class="file">.texinfo</span></samp> (or 
<samp><span class="file">.texi</span></samp> or <samp><span 
class="file">.txi</span></samp>).  For
+<code>bug-<var>package</var>@gnu.org</code>).  The script processes the file
+&lsquo;<tt><var>yourmanual</var>.texinfo</tt>&rsquo; (or 
&lsquo;<tt>.texi</tt>&rsquo; or &lsquo;<tt>.txi</tt>&rsquo;).  For
 example:
+</p>
+<div class="smallexample">
+<pre class="smallexample">cd .../emacs/man
+# download gendocs.sh and gendocs_template
+gendocs.sh --email address@hidden emacs &quot;GNU Emacs manual&quot;
+</pre></div>
 
-<pre class="smallexample">     cd .../emacs/man
-     # download gendocs.sh and gendocs_template
-     gendocs.sh --email address@hidden emacs "GNU Emacs manual"
-</pre>
-   <p><samp><span class="command">gendocs.sh</span></samp> creates a 
subdirectory <samp><span class="file">manual/</span></samp> containing
+<p><code>gendocs.sh</code> creates a subdirectory 
&lsquo;<tt>manual/</tt>&rsquo; containing
 the manual generated in all the standard output formats: Info, HTML,
 DVI, and so on, as well as the Texinfo source.  You then need to move
 all those files, retaining the subdirectories, into the web pages for
 your package.
-
-   <p>You can specify the option <samp><span class="option">-o 
</span><var>outdir</var></samp> to override the
-name <samp><span class="file">manual</span></samp>.  Any previous contents of 
<var>outdir</var> will be deleted.
-
-   <p>The second argument, with the description, is included as part of the
-HTML <code>&lt;title&gt;</code> of the overall <samp><span 
class="file">manual/index.html</span></samp> file.  It
+</p>
+<p>You can specify the option &lsquo;<samp>-o <var>outdir</var></samp>&rsquo; 
to override the
+name &lsquo;<tt>manual</tt>&rsquo;.  Any previous contents of 
<var>outdir</var> will be deleted.
+</p>
+<p>The second argument, with the description, is included as part of the
+HTML <code>&lt;title&gt;</code> of the overall 
&lsquo;<tt>manual/index.html</tt>&rsquo; file.  It
 should include the name of the package being documented, as shown. 
-<samp><span class="file">manual/index.html</span></samp> is created by 
substitution from the file
-<samp><span class="file">gendocs_template</span></samp>.  (Feel free to modify 
the generic template
+&lsquo;<tt>manual/index.html</tt>&rsquo; is created by substitution from the 
file
+&lsquo;<tt>gendocs_template</tt>&rsquo;.  (Feel free to modify the generic 
template
 for your own purposes.)
-
-   <p>If you have several manuals, you'll need to run this script several
+</p>
+<p>If you have several manuals, you&rsquo;ll need to run this script several
 times with different arguments, specifying a different output
-directory with <samp><span class="option">-o</span></samp> each time, and 
moving all the output to
+directory with &lsquo;<samp>-o</samp>&rsquo; each time, and moving all the 
output to
 your web page.  Then write (by hand) an overall index.html with links
 to them all.  For example:
+</p>
+<div class="smallexample">
+<pre class="smallexample">cd .../texinfo/doc
+gendocs.sh --email address@hidden -o texinfo texinfo &quot;GNU Texinfo 
manual&quot;
+gendocs.sh --email address@hidden -o info info &quot;GNU Info manual&quot;
+gendocs.sh --email address@hidden -o info-stnd info-stnd &quot;GNU info-stnd 
manual&quot;
+</pre></div>
+
+<p>By default, the script uses <code>makeinfo</code> for generating
+<acronym>HTML</acronym> output.  If you prefer to use <code>texi2html</code>, 
use
+the &lsquo;<samp>--texi2html</samp>&rsquo; command line option, e.g.:
+</p>
+<div class="smallexample">
+<pre class="smallexample">gendocs --texi2html -o texinfo texinfo &quot;GNU 
Texinfo manual&quot;
+</pre></div>
 
-<pre class="smallexample">     cd .../texinfo/doc
-     gendocs.sh --email address@hidden -o texinfo texinfo "GNU Texinfo manual"
-     gendocs.sh --email address@hidden -o info info "GNU Info manual"
-     gendocs.sh --email address@hidden -o info-stnd info-stnd "GNU info-stnd 
manual"
-</pre>
-   <p>By default, the script uses <samp><span 
class="command">makeinfo</span></samp> for generating
-<acronym>HTML</acronym> output.  If you prefer to use <samp><span 
class="command">texi2html</span></samp>, use
-the <samp><span class="option">--texi2html</span></samp> command line option, 
e.g.:
-
-<pre class="smallexample">     gendocs --texi2html -o texinfo texinfo "GNU 
Texinfo manual"
-</pre>
-   <p>The template files will automatically produce entries for additional
-HTML output generated by <samp><span class="command">texi2html</span></samp> 
(i.e., split by sections
+<p>The template files will automatically produce entries for additional
+HTML output generated by <code>texi2html</code> (i.e., split by sections
 and chapters).
-
-   <p>You can set the environment variables <samp><span 
class="env">MAKEINFO</span></samp>, <samp><span 
class="env">TEXI2DVI</span></samp>,
-<samp><span class="env">TEXI2HTML</span></samp> and <samp><span 
class="env">DVIPS</span></samp> to control the programs that get
-executed, and <samp><span class="env">GENDOCS_TEMPLATE_DIR</span></samp> to 
control where the
-<samp><span class="file">gendocs_template</span></samp> file is found.
-
-   <p>As usual, run &lsquo;<samp><span class="samp">gendocs.sh 
--help</span></samp>&rsquo; for a description of all the
+</p>
+<p>You can set the environment variables <code>MAKEINFO</code>, 
<code>TEXI2DVI</code>,
+<code>TEXI2HTML</code> and <code>DVIPS</code> to control the programs that get
+executed, and <code>GENDOCS_TEMPLATE_DIR</code> to control where the
+&lsquo;<tt>gendocs_template</tt>&rsquo; file is found.
+</p>
+<p>As usual, run &lsquo;<samp>gendocs.sh --help</samp>&rsquo; for a 
description of all the
 options, environment variables, and more information.
-
-   <p>Please email bug reports, enhancement requests, or other
+</p>
+<p>Please email bug reports, enhancement requests, or other
 correspondence to <a href="mailto:address@hidden";>address@hidden</a>.
+</p>
 
-<div class="node">
+<hr>
 <a name="CVS-Keywords-in-Web-Pages"></a>
-<p><hr>
-Previous:&nbsp;<a rel="previous" accesskey="p" 
href="#Manuals-on-Web-Pages">Manuals on Web Pages</a>,
-Up:&nbsp;<a rel="up" accesskey="u" href="#Web-Pages">Web Pages</a>
-
-</div>
-
-<h3 class="section">12.4 CVS Keywords in Web Pages</h3>
-
-<p><a name="index-CVS-keywords-in-web-pages-72"></a><a 
name="index-RCS-keywords-in-web-pages-73"></a><a 
name="index-g_t_0024-keywords-in-web-pages-74"></a><a 
name="index-web-pages_002c-and-CVS-keywords-75"></a>
-Since <code>www.gnu.org</code> works through CVS, CVS keywords in your
-manual, such as <code>$<!-- /@w -->Log$</code>, need special treatment (even 
if you
-don't happen to maintain your manual in CVS).
-
-   <p>If these keywords end up in the generated output as literal strings,
+<div class="header">
+<p>
+Previous: <a href="#Manuals-on-Web-Pages" accesskey="p" rel="previous">Manuals 
on Web Pages</a>, Up: <a href="#Web-Pages" accesskey="u" rel="up">Web Pages</a> 
&nbsp; [<a href="#SEC_Contents" title="Table of contents" 
rel="contents">Contents</a>][<a href="#Index" title="Index" 
rel="index">Index</a>]</p>
+</div>
+<a name="CVS-Keywords-in-Web-Pages-1"></a>
+<h2 class="section">12.4 CVS Keywords in Web Pages</h2>
+<a name="index-CVS-keywords-in-web-pages"></a>
+<a name="index-RCS-keywords-in-web-pages"></a>
+<a name="index-_0024-keywords-in-web-pages"></a>
+<a name="index-web-pages_002c-and-CVS-keywords"></a>
+
+<p>Since <code>www.gnu.org</code> works through CVS, CVS keywords in your
+manual, such as <code>$Log$</code>, need special treatment (even if you
+don&rsquo;t happen to maintain your manual in CVS).
+</p>
+<p>If these keywords end up in the generated output as literal strings,
 they will be expanded.  The most robust way to handle this is to turn
 off keyword expansion for such generated files.  For existing files,
 this is done with:
+</p>
+<div class="example">
+<pre class="example">cvs admin -ko <var>file1</var> <var>file2</var> ...
+</pre></div>
+
+<p>For new files:
+</p>
+<div class="example">
+<pre class="example">cvs add -ko <var>file1</var> <var>file2</var> ...
+</pre></div>
 
-<pre class="example">     cvs admin -ko <var>file1</var> <var>file2</var> ...
-</pre>
-   <p class="noindent">For new files:
-
-<pre class="example">     cvs add -ko <var>file1</var> <var>file2</var> ...
-</pre>
-   <!-- The CVS manual is now built with numeric references and no nonsplit -->
-<!-- form, so it's not worth trying to give a direct link. -->
-   <p>See the &ldquo;Keyword Substitution&rdquo; section in the CVS manual, 
available
+<p>See the &ldquo;Keyword Substitution&rdquo; section in the CVS manual, 
available
 at <a href="http://ximbiot.com/cvs/manual";>http://ximbiot.com/cvs/manual</a>.
-
-   <p>In Texinfo source, the recommended way to literally specify a
+</p>
+<p>In Texinfo source, the recommended way to literally specify a
 &ldquo;dollar&rdquo; keyword is:
+</p>
+<div class="example">
+<pre class="example">@w{$}Log$
+</pre></div>
 
-<pre class="example">     @w{$}Log$
-</pre>
-   <p>The <code>@w</code> prevents keyword expansion in the Texinfo source
+<p>The <code>@w</code> prevents keyword expansion in the Texinfo source
 itself.  Also, <code>makeinfo</code> notices the <code>@w</code> and generates
 output avoiding the literal keyword string.
+</p>
 
-<div class="node">
+<hr>
 <a name="Ethical-and-Philosophical-Consideration"></a>
-<p><hr>
-Next:&nbsp;<a rel="next" accesskey="n" href="#Terminology">Terminology</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" href="#Web-Pages">Web Pages</a>,
-Up:&nbsp;<a rel="up" accesskey="u" href="#Top">Top</a>
+<div class="header">
+<p>
+Next: <a href="#Terminology" accesskey="n" rel="next">Terminology</a>, 
Previous: <a href="#Web-Pages" accesskey="p" rel="previous">Web Pages</a>, Up: 
<a href="#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a href="#SEC_Contents" 
title="Table of contents" rel="contents">Contents</a>][<a href="#Index" 
title="Index" rel="index">Index</a>]</p>
+</div>
+<a name="Ethical-and-Philosophical-Consideration-1"></a>
+<h1 class="chapter">13 Ethical and Philosophical Consideration</h1>
+<a name="index-ethics"></a>
+<a name="index-philosophy"></a>
 
-</div>
-
-<h2 class="chapter">13 Ethical and Philosophical Consideration</h2>
-
-<p><a name="index-ethics-76"></a><a name="index-philosophy-77"></a>
-The GNU project takes a strong stand for software freedom.  Many
-times, this means you'll need to avoid certain technologies when their
+<p>The GNU project takes a strong stand for software freedom.  Many
+times, this means you&rsquo;ll need to avoid certain technologies when their
 use would conflict with our long-term goals.
-
-   <p>Software patents threaten the advancement of free software and freedom
+</p>
+<p>Software patents threaten the advancement of free software and freedom
 to program.  There are so many software patents in the US that any
 large program probably implements hundreds of patented techniques,
-unknown to the program's developers.  It would be futile and
+unknown to the program&rsquo;s developers.  It would be futile and
 self-defeating to try to find and avoid all these patents.  But there
 are some patents which we know are likely to be used to threaten free
 software, so we make an effort to avoid the patented techniques.  If
 you are concerned about the danger of a patent and would like advice,
 write to <a href="mailto:address@hidden";>address@hidden</a>, and we will try 
to help you get
 advice from a lawyer.
-
-   <p>Sometimes the GNU project takes a strong stand against a particular
+</p>
+<p>Sometimes the GNU project takes a strong stand against a particular
 patented technology in order to encourage society to reject it.
-
-   <p>For example, the MP3 audio format is covered by a software patent in
+</p>
+<p>For example, the MP3 audio format is covered by a software patent in
 the USA and some other countries.  A patent holder has threatened
 lawsuits against the developers of free programs (these are not GNU
 programs) to produce and play MP3, and some GNU/Linux distributors are
 afraid to include them.  Development of the programs continues, but we
 campaign for the rejection of MP3 format in favor of Ogg Vorbis format.
-
-   <p>A GNU package should not recommend use of any non-free program, nor
+</p>
+<p>A GNU package should not recommend use of any non-free program, nor
 should it require a non-free program (such as a non-free compiler or
 IDE) to build.  Thus, a GNU package cannot be written in a programming
 language that does not have a free software implementation.  Now that
@@ -2254,51 +2395,54 @@
 provide full functionality on a 100% free GNU/Linux system, and should
 not require any non-free software to build or function. 
 The GNU Coding Standards say a lot more about this issue.
-
-   <p>A GNU package should not refer the user to any non-free documentation
+</p>
+<p>A GNU package should not refer the user to any non-free documentation
 for free software.  The need for free documentation to come with free
 software is now a major focus of the GNU project; to show that we are
 serious about the need for free documentation, we must not contradict
-our position by recommending use of documentation that isn't free.
-
-   <p>Finally, new issues concerning the ethics of software freedom come up
+our position by recommending use of documentation that isn&rsquo;t free.
+</p>
+<p>Finally, new issues concerning the ethics of software freedom come up
 frequently.  We ask that GNU maintainers, at least on matters that
 pertain specifically to their package, stand with the rest of the GNU
 project when such issues come up.
+</p>
 
-<div class="node">
+<hr>
 <a name="Terminology"></a>
-<p><hr>
-Next:&nbsp;<a rel="next" accesskey="n" href="#Hosting">Hosting</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" 
href="#Ethical-and-Philosophical-Consideration">Ethical and Philosophical 
Consideration</a>,
-Up:&nbsp;<a rel="up" accesskey="u" href="#Top">Top</a>
-
-</div>
-
-<h2 class="chapter">14 Terminology Issues</h2>
+<div class="header">
+<p>
+Next: <a href="#Hosting" accesskey="n" rel="next">Hosting</a>, Previous: <a 
href="#Ethical-and-Philosophical-Consideration" accesskey="p" 
rel="previous">Ethical and Philosophical Consideration</a>, Up: <a href="#Top" 
accesskey="u" rel="up">Top</a> &nbsp; [<a href="#SEC_Contents" title="Table of 
contents" rel="contents">Contents</a>][<a href="#Index" title="Index" 
rel="index">Index</a>]</p>
+</div>
+<a name="Terminology-Issues"></a>
+<h1 class="chapter">14 Terminology Issues</h1>
+<a name="index-terminology"></a>
 
-<p><a name="index-terminology-78"></a>
-This chapter explains a couple of issues of terminology which are
+<p>This chapter explains a couple of issues of terminology which are
 important for correcting two widespread and important misunderstandings
 about GNU.
+</p>
+<table class="menu" border="0" cellspacing="0">
+<tr><td align="left" valign="top">&bull; <a 
href="#Free-Software-and-Open-Source" accesskey="1">Free Software and Open 
Source</a>:</td><td>&nbsp;&nbsp;</td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a href="#GNU-and-Linux" 
accesskey="2">GNU and Linux</a>:</td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">
+</td></tr>
+</table>
 
-<ul class="menu">
-<li><a accesskey="1" href="#Free-Software-and-Open-Source">Free Software and 
Open Source</a>
-<li><a accesskey="2" href="#GNU-and-Linux">GNU and Linux</a>
-</ul>
-
-<div class="node">
+<hr>
 <a name="Free-Software-and-Open-Source"></a>
-<p><hr>
-Next:&nbsp;<a rel="next" accesskey="n" href="#GNU-and-Linux">GNU and Linux</a>,
-Up:&nbsp;<a rel="up" accesskey="u" href="#Terminology">Terminology</a>
-
-</div>
+<div class="header">
+<p>
+Next: <a href="#GNU-and-Linux" accesskey="n" rel="next">GNU and Linux</a>, Up: 
<a href="#Terminology" accesskey="u" rel="up">Terminology</a> &nbsp; [<a 
href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a 
href="#Index" title="Index" rel="index">Index</a>]</p>
+</div>
+<a name="Free-Software-and-Open-Source-1"></a>
+<h2 class="section">14.1 Free Software and Open Source</h2>
+<a name="index-free-software-movement"></a>
+<a name="index-open-source"></a>
+<a name="index-movement_002c-free-software"></a>
+<a name="index-development-method_002c-open-source"></a>
 
-<h3 class="section">14.1 Free Software and Open Source</h3>
-
-<p><a name="index-free-software-movement-79"></a><a 
name="index-open-source-80"></a><a 
name="index-movement_002c-free-software-81"></a><a 
name="index-development-method_002c-open-source-82"></a>
-The terms &ldquo;free software&rdquo; and &ldquo;open source&rdquo;, while 
describing
+<p>The terms &ldquo;free software&rdquo; and &ldquo;open source&rdquo;, while 
describing
 almost the same category of software, stand for views based on
 fundamentally different values.  The free software movement is
 idealistic, and raises issues of freedom, ethics, principle and what
@@ -2306,13 +2450,13 @@
 associated with a philosophy which studiously avoids such questions. 
 For a detailed explanation, see
 <a 
href="http://www.gnu.org/philosophy/open-source-misses-the-point.html";>http://www.gnu.org/philosophy/open-source-misses-the-point.html</a>.
-
-   <p>The GNU Project is aligned with the free software movement.  This
-doesn't mean that all GNU contributors and maintainers have to agree;
-your views on these issues are up to you, and you're entitled to express
+</p>
+<p>The GNU Project is aligned with the free software movement.  This
+doesn&rsquo;t mean that all GNU contributors and maintainers have to agree;
+your views on these issues are up to you, and you&rsquo;re entitled to express
 them when speaking for yourself.
-
-   <p>However, due to the much greater publicity that the term &ldquo;open 
source&rdquo;
+</p>
+<p>However, due to the much greater publicity that the term &ldquo;open 
source&rdquo;
 receives, the GNU Project needs to overcome a widespread
 mistaken impression that GNU is <em>and always was</em> an &ldquo;open
 source&rdquo; activity.  For this reason, please use the term &ldquo;free
@@ -2321,273 +2465,281 @@
 role as the maintainer of a GNU package.  A reference to the URL given
 above, to explain the difference, is a useful thing to include as
 well.
+</p>
 
-<div class="node">
+<hr>
 <a name="GNU-and-Linux"></a>
-<p><hr>
-Previous:&nbsp;<a rel="previous" accesskey="p" 
href="#Free-Software-and-Open-Source">Free Software and Open Source</a>,
-Up:&nbsp;<a rel="up" accesskey="u" href="#Terminology">Terminology</a>
+<div class="header">
+<p>
+Previous: <a href="#Free-Software-and-Open-Source" accesskey="p" 
rel="previous">Free Software and Open Source</a>, Up: <a href="#Terminology" 
accesskey="u" rel="up">Terminology</a> &nbsp; [<a href="#SEC_Contents" 
title="Table of contents" rel="contents">Contents</a>][<a href="#Index" 
title="Index" rel="index">Index</a>]</p>
+</div>
+<a name="GNU-and-Linux-1"></a>
+<h2 class="section">14.2 GNU and Linux</h2>
+<a name="index-Linux"></a>
+<a name="index-GNU_002fLinux"></a>
 
-</div>
-
-<h3 class="section">14.2 GNU and Linux</h3>
-
-<p><a name="index-Linux-83"></a><a name="index-GNU_002fLinux-84"></a>
-The GNU Project was formed to develop a free Unix-like operating system,
+<p>The GNU Project was formed to develop a free Unix-like operating system,
 GNU.  The existence of this system is our major accomplishment. 
 However, the widely used version of the GNU system, in which Linux is
 used as the kernel, is often called simply &ldquo;Linux&rdquo;.  As a result, 
most
-users don't know about the GNU Project's major accomplishment&mdash;or more
-precisely, they know about it, but don't realize it is the GNU Project's
+users don&rsquo;t know about the GNU Project&rsquo;s major 
accomplishment&mdash;or more
+precisely, they know about it, but don&rsquo;t realize it is the GNU 
Project&rsquo;s
 accomplishment and reason for existence.  Even people who believe they
 know the real history often believe that the goal of GNU was to develop
 &ldquo;tools&rdquo; or &ldquo;utilities.&rdquo;
-
-   <p>To correct this confusion, we have made a years-long effort to
+</p>
+<p>To correct this confusion, we have made a years-long effort to
 distinguish between Linux, the kernel that Linus Torvalds wrote, and
 GNU/Linux, the operating system that is the combination of GNU and
 Linux.  The resulting increased awareness of what the GNU Project has
 already done helps every activity of the GNU Project recruit more
 support and contributors.
-
-   <p>Please make this distinction consistently in GNU software releases, GNU
+</p>
+<p>Please make this distinction consistently in GNU software releases, GNU
 documentation, and announcements and articles that you publish in your
 role as the maintainer of a GNU package.  If you want to explain the
 terminology and its reasons, you can refer to the URL
 <a 
href="http://www.gnu.org/gnu/linux-and-gnu.html";>http://www.gnu.org/gnu/linux-and-gnu.html</a>.
-
-   <p>To contrast the GNU system properly with respect to GNU/Linux, you can
+</p>
+<p>To contrast the GNU system properly with respect to GNU/Linux, you can
 call it &ldquo;GNU/Hurd&rdquo; or &ldquo;the GNU/Hurd system.&rdquo;  However, 
when that
 contrast is not specifically the focus, please call it just &ldquo;GNU&rdquo; 
or
 &ldquo;the GNU system.&rdquo;
-
-   <p>When referring to the collection of servers that is the higher level
+</p>
+<p>When referring to the collection of servers that is the higher level
 of the GNU kernel, please call it &ldquo;the Hurd&rdquo; or &ldquo;the GNU 
Hurd.&rdquo;
 Note that this uses a space, not a slash.
+</p>
 
-<div class="node">
+<hr>
 <a name="Hosting"></a>
-<p><hr>
-Next:&nbsp;<a rel="next" accesskey="n" href="#Donations">Donations</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" 
href="#Terminology">Terminology</a>,
-Up:&nbsp;<a rel="up" accesskey="u" href="#Top">Top</a>
-
-</div>
-
-<h2 class="chapter">15 Hosting</h2>
-
-<p><a name="index-CVS-repository-85"></a><a name="index-repository-86"></a><a 
name="index-source-repository-87"></a><a 
name="index-version-control-system-88"></a><a name="index-FTP-site-89"></a><a 
name="index-release-site-90"></a><a name="index-hosting-91"></a>
-We recommend using <code>savannah.gnu.org</code> for the source code
-repository for your package, but that's not required.  See <a 
href="#Old-Versions">Old Versions</a>, for more information about Savannah.
-
-   <p>We strongly urge you to use <code>ftp.gnu.org</code> as the standard
+<div class="header">
+<p>
+Next: <a href="#Donations" accesskey="n" rel="next">Donations</a>, Previous: 
<a href="#Terminology" accesskey="p" rel="previous">Terminology</a>, Up: <a 
href="#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a href="#SEC_Contents" 
title="Table of contents" rel="contents">Contents</a>][<a href="#Index" 
title="Index" rel="index">Index</a>]</p>
+</div>
+<a name="Hosting-1"></a>
+<h1 class="chapter">15 Hosting</h1>
+<a name="index-CVS-repository"></a>
+<a name="index-repository"></a>
+<a name="index-source-repository"></a>
+<a name="index-version-control-system"></a>
+<a name="index-FTP-site"></a>
+<a name="index-release-site"></a>
+<a name="index-hosting"></a>
+
+<p>We recommend using <code>savannah.gnu.org</code> for the source code
+repository for your package, but that&rsquo;s not required.  See <a 
href="#Old-Versions">Old
+Versions</a>, for more information about Savannah.
+</p>
+<p>We strongly urge you to use <code>ftp.gnu.org</code> as the standard
 distribution site for releases.  Doing so makes it easier for
 developers and users to find the latest GNU releases.  However, it is
 ok to use another server if you wish, provided it allows access from
 the general public without limitation (for instance, without excluding
 any country).
-
-   <p>If you use a company's machine to hold the repository for your
+</p>
+<p>If you use a company&rsquo;s machine to hold the repository for your
 program, or as its release distribution site, please put this
 statement in a prominent place on the site, so as to prevent people
 from getting the wrong idea about the relationship between the package
 and the company:
+</p>
+<div class="smallexample">
+<pre class="smallexample">The programs &lt;list of them&gt; hosted here are 
free software packages
+of the GNU Project, not products of &lt;company name&gt;.  We call them
+&quot;free software&quot; because you are free to copy and redistribute them,
+following the rules stated in the license of each package.  For more
+information, see http://www.gnu.org/philosophy/free-sw.html.
+
+If you are looking for service or support for GNU software, see
+http://www.gnu.org/gethelp/ for suggestions of where to ask.
+
+If you would like to contribute to the development of one of these
+packages, contact the package maintainer or the bug-reporting address
+of the package (which should be listed in the package itself), or look
+on www.gnu.org for more information on how to contribute.
+</pre></div>
 
-<pre class="smallexample">     The programs &lt;list of them&gt; hosted here 
are free software packages
-     of the GNU Project, not products of &lt;company name&gt;.  We call them
-     "free software" because you are free to copy and redistribute them,
-     following the rules stated in the license of each package.  For more
-     information, see http://www.gnu.org/philosophy/free-sw.html.
-     
-     If you are looking for service or support for GNU software, see
-     http://www.gnu.org/gethelp/ for suggestions of where to ask.
-     
-     If you would like to contribute to the development of one of these
-     packages, contact the package maintainer or the bug-reporting address
-     of the package (which should be listed in the package itself), or look
-     on www.gnu.org for more information on how to contribute.
-</pre>
-   <div class="node">
-<a name="Donations"></a>
-<p><hr>
-Next:&nbsp;<a rel="next" accesskey="n" href="#Free-Software-Directory">Free 
Software Directory</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" href="#Hosting">Hosting</a>,
-Up:&nbsp;<a rel="up" accesskey="u" href="#Top">Top</a>
-
-</div>
 
-<h2 class="chapter">16 Donations</h2>
+<hr>
+<a name="Donations"></a>
+<div class="header">
+<p>
+Next: <a href="#Free-Software-Directory" accesskey="n" rel="next">Free 
Software Directory</a>, Previous: <a href="#Hosting" accesskey="p" 
rel="previous">Hosting</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> 
&nbsp; [<a href="#SEC_Contents" title="Table of contents" 
rel="contents">Contents</a>][<a href="#Index" title="Index" 
rel="index">Index</a>]</p>
+</div>
+<a name="Donations-1"></a>
+<h1 class="chapter">16 Donations</h1>
+<a name="index-Donations_002c-for-packages"></a>
+<a name="index-Money_002c-donated-to-packages"></a>
 
-<p><a name="index-Donations_002c-for-packages-92"></a><a 
name="index-Money_002c-donated-to-packages-93"></a>
-As a maintainer, you might want to accept donations for your work,
+<p>As a maintainer, you might want to accept donations for your work,
 especially if you pay for any of your own hosting/development
 infrastructure.  Following is some text you can adapt to your own
-situation, and use on your package's web site, <samp><span 
class="file">README</span></samp>, or
+situation, and use on your package&rsquo;s web site, 
&lsquo;<tt>README</tt>&rsquo;, or
 in wherever way you find it useful:
+</p>
+<div class="smallexample">
+<pre class="smallexample">We appreciate contributions of any size -- donations 
enable us to spend
+more time working on the project, and help cover our infrastructure
+expenses.
+
+If you'd like to make a small donation, please visit <var>url1</var> and do
+it through <var>payment-service</var>.  Since our project isn't a
+tax-exempt organization, we can't offer you a tax deduction, but for
+all donations over <var>amount1</var>, we'd be happy to recognize your
+contribution on <var>url2</var>.
+
+We are also happy to consider making particular improvements or
+changes, or giving specific technical assistance, in return for a
+substantial donation over <var>amount2</var>.  If you would like to discuss
+this possibility, write to us at <var>address</var>.
+
+Another possibility is to pay a software maintenance fee.  Again,
+write to us about this at <var>address</var> to discuss how much you want
+to pay and how much maintenance we can offer in return.  If you pay
+more than <var>amount1</var>, we can give you a document for your records.
 
-<pre class="smallexample">     We appreciate contributions of any size -- 
donations enable us to spend
-     more time working on the project, and help cover our infrastructure
-     expenses.
-     
-     If you'd like to make a small donation, please visit <var>url1</var> and 
do
-     it through <var>payment-service</var>.  Since our project isn't a
-     tax-exempt organization, we can't offer you a tax deduction, but for
-     all donations over <var>amount1</var>, we'd be happy to recognize your
-     contribution on <var>url2</var>.
-     
-     We are also happy to consider making particular improvements or
-     changes, or giving specific technical assistance, in return for a
-     substantial donation over <var>amount2</var>.  If you would like to 
discuss
-     this possibility, write to us at <var>address</var>.
-     
-     Another possibility is to pay a software maintenance fee.  Again,
-     write to us about this at <var>address</var> to discuss how much you want
-     to pay and how much maintenance we can offer in return.  If you pay
-     more than <var>amount1</var>, we can give you a document for your records.
-     
-     Thanks for your support!
-</pre>
-   <p>We don't recommend any specific payment service.  However, GNU
-developers should not use a service that requires them to sign a
-proprietary software license, such as Google's payment service.
+Thanks for your support!
+</pre></div>
 
-   <p>Of course, it is also good to encourage people to join or contribute
+<p>We don&rsquo;t recommend any specific payment service.  However, GNU
+developers should not use a service that requires them to sign a
+proprietary software license, such as Google&rsquo;s payment service.
+</p>
+<p>Of course, it is also good to encourage people to join or contribute
 to the FSF (<a href="http://www.fsf.org";>http://www.fsf.org</a>), either 
instead of or as well as
 package-specific donations.
+</p>
 
-<div class="node">
+<hr>
 <a name="Free-Software-Directory"></a>
-<p><hr>
-Next:&nbsp;<a rel="next" accesskey="n" 
href="#Using-the-Proofreaders-List">Using the Proofreaders List</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" href="#Donations">Donations</a>,
-Up:&nbsp;<a rel="up" accesskey="u" href="#Top">Top</a>
+<div class="header">
+<p>
+Next: <a href="#Using-the-Proofreaders-List" accesskey="n" rel="next">Using 
the Proofreaders List</a>, Previous: <a href="#Donations" accesskey="p" 
rel="previous">Donations</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> 
&nbsp; [<a href="#SEC_Contents" title="Table of contents" 
rel="contents">Contents</a>][<a href="#Index" title="Index" 
rel="index">Index</a>]</p>
+</div>
+<a name="Free-Software-Directory-1"></a>
+<h1 class="chapter">17 Free Software Directory</h1>
+<a name="index-Free-Software-Directory"></a>
+<a name="index-Directory_002c-Free-Software"></a>
 
-</div>
-
-<h2 class="chapter">17 Free Software Directory</h2>
-
-<p><a name="index-Free-Software-Directory-94"></a><a 
name="index-Directory_002c-Free-Software-95"></a>
-The Free Software Directory aims to be a complete list of free
+<p>The Free Software Directory aims to be a complete list of free
 software packages, within certain criteria.  Every GNU package should
 be listed there, so please see
 <a 
href="http://www.gnu.org/help/directory.html#adding-entries";>http://www.gnu.org/help/directory.html#adding-entries</a>
 for
 information on how to write an entry for your package.  Contact
 <a href="mailto:address@hidden";>address@hidden</a> with any questions or 
suggestions for
 the Free Software Directory.
+</p>
 
-<div class="node">
+<hr>
 <a name="Using-the-Proofreaders-List"></a>
-<p><hr>
-Next:&nbsp;<a rel="next" accesskey="n" 
href="#GNU-Free-Documentation-License">GNU Free Documentation License</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" 
href="#Free-Software-Directory">Free Software Directory</a>,
-Up:&nbsp;<a rel="up" accesskey="u" href="#Top">Top</a>
+<div class="header">
+<p>
+Next: <a href="#GNU-Free-Documentation-License" accesskey="n" rel="next">GNU 
Free Documentation License</a>, Previous: <a href="#Free-Software-Directory" 
accesskey="p" rel="previous">Free Software Directory</a>, Up: <a href="#Top" 
accesskey="u" rel="up">Top</a> &nbsp; [<a href="#SEC_Contents" title="Table of 
contents" rel="contents">Contents</a>][<a href="#Index" title="Index" 
rel="index">Index</a>]</p>
+</div>
+<a name="Using-the-Proofreaders-List-1"></a>
+<h1 class="chapter">18 Using the Proofreaders List</h1>
+<a name="index-proofreading"></a>
 
-</div>
-
-<h2 class="chapter">18 Using the Proofreaders List</h2>
-
-<p><a name="index-proofreading-96"></a>
-If you want help finding errors in documentation,
+<p>If you want help finding errors in documentation,
 or help improving the quality of writing,
 or if you are not a native speaker of English
 and want help producing good English documentation,
 you can use the GNU proofreaders mailing list:
 <a href="mailto:address@hidden";>address@hidden</a>.
-
-   <p>But be careful when you use the list,
+</p>
+<p>But be careful when you use the list,
 because there are over 200 people on it. 
 If you simply ask everyone on the list to read your work,
 there will probably be tremendous duplication of effort
 by the proofreaders,
 and you will probably get the same errors reported 100 times. 
 This must be avoided.
-
-   <p>Also, the people on the list do not want to get
+</p>
+<p>Also, the people on the list do not want to get
 a large amount of mail from it. 
 So do not ever ask people on the list to send mail to the list!
-
-   <p>Here are a few methods that seem reasonable to use:
-
-     <ul>
-<li>For something small, mail it to the list,
+</p>
+<p>Here are a few methods that seem reasonable to use:
+</p>
+<ul>
+<li> For something small, mail it to the list,
 and ask people to pick a random number from 1 to 20,
 and read it if the number comes out as 10. 
 This way, assuming 50% response, some 5 people will read the piece.
 
-     <li>For a larger work, divide your work into around 20 equal-sized parts,
+</li><li> For a larger work, divide your work into around 20 equal-sized parts,
 tell people where to get it,
 and ask each person to pick randomly which part to read.
 
-     <p>Be sure to specify the random choice procedure;
+<p>Be sure to specify the random choice procedure;
 otherwise people will probably use a mental procedure
 that is not really random,
 such as &ldquo;pick a part near the middle&rdquo;,
 and you will not get even coverage.
-
-     <p>You can either divide up the work physically, into 20 separate files,
+</p>
+<p>You can either divide up the work physically, into 20 separate files,
 or describe a virtual division, such as by sections
 (if your work has approximately 20 sections). 
 If you do the latter, be sure to be precise about it&mdash;for example,
 do you want the material before the first section heading
 to count as a section, or not?
-
-     <li>For a job needing special skills, send an explanation of it,
+</p>
+</li><li> For a job needing special skills, send an explanation of it,
 and ask people to send you mail if they volunteer for the job. 
 When you get enough volunteers, send another message to the list saying
 &ldquo;I have enough volunteers, no more please.&rdquo;
-</ul>
-
-<div class="node">
-<a name="GNU-Free-Documentation-License"></a>
-<p><hr>
-Next:&nbsp;<a rel="next" accesskey="n" href="#Index">Index</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" 
href="#Using-the-Proofreaders-List">Using the Proofreaders List</a>,
-Up:&nbsp;<a rel="up" accesskey="u" href="#Top">Top</a>
-
-</div>
-
-<h2 class="appendix">Appendix A GNU Free Documentation License</h2>
-
-<p><a name="index-FDL_002c-GNU-Free-Documentation-License-97"></a>
+</li></ul>
 
-<!-- The GNU Free Documentation License. -->
-<div align="center">Version 1.3, 3 November 2008</div>
 
-<!-- This file is intended to be included within another document, -->
-<!-- hence no sectioning command or @node. -->
-<pre class="display">     Copyright &copy; 2000, 2001, 2002, 2007, 2008 Free 
Software Foundation, Inc.
-     <a href="http://fsf.org/";>http://fsf.org/</a>
+<hr>
+<a name="GNU-Free-Documentation-License"></a>
+<div class="header">
+<p>
+Next: <a href="#Index" accesskey="n" rel="next">Index</a>, Previous: <a 
href="#Using-the-Proofreaders-List" accesskey="p" rel="previous">Using the 
Proofreaders List</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> &nbsp; 
[<a href="#SEC_Contents" title="Table of contents" 
rel="contents">Contents</a>][<a href="#Index" title="Index" 
rel="index">Index</a>]</p>
+</div>
+<a name="GNU-Free-Documentation-License-1"></a>
+<h1 class="appendix">Appendix A GNU Free Documentation License</h1>
+
+<a name="index-FDL_002c-GNU-Free-Documentation-License"></a>
+<p align="center">Version 1.3, 3 November 2008
+</p>
+
+<div class="display">
+<pre class="display">Copyright &copy; 2000, 2001, 2002, 2007, 2008 Free 
Software Foundation, Inc.
+<a href="http://fsf.org/";>http://fsf.org/</a>
+
+Everyone is permitted to copy and distribute verbatim copies
+of this license document, but changing it is not allowed.
+</pre></div>
      
-     Everyone is permitted to copy and distribute verbatim copies
-     of this license document, but changing it is not allowed.
-</pre>
-     <ol type=1 start=0>
-<li>PREAMBLE
+<ol>
+<li> PREAMBLE
 
-     <p>The purpose of this License is to make a manual, textbook, or other
-functional and useful document <dfn>free</dfn> in the sense of freedom: to
+<p>The purpose of this License is to make a manual, textbook, or other
+functional and useful document <em>free</em> in the sense of freedom: to
 assure everyone the effective freedom to copy and redistribute it,
 with or without modifying it, either commercially or noncommercially. 
 Secondarily, this License preserves for the author and publisher a way
 to get credit for their work, while not being considered responsible
 for modifications made by others.
-
-     <p>This License is a kind of &ldquo;copyleft&rdquo;, which means that 
derivative
+</p>
+<p>This License is a kind of &ldquo;copyleft&rdquo;, which means that 
derivative
 works of the document must themselves be free in the same sense.  It
 complements the GNU General Public License, which is a copyleft
 license designed for free software.
-
-     <p>We have designed this License in order to use it for manuals for free
+</p>
+<p>We have designed this License in order to use it for manuals for free
 software, because free software needs free documentation: a free
 program should come with manuals providing the same freedoms that the
 software does.  But this License is not limited to software manuals;
 it can be used for any textual work, regardless of subject matter or
 whether it is published as a printed book.  We recommend this License
 principally for works whose purpose is instruction or reference.
+</p>
+</li><li> APPLICABILITY AND DEFINITIONS
 
-     <li>APPLICABILITY AND DEFINITIONS
-
-     <p>This License applies to any manual or other work, in any medium, that
+<p>This License applies to any manual or other work, in any medium, that
 contains a notice placed by the copyright holder saying it can be
 distributed under the terms of this License.  Such a notice grants a
 world-wide, royalty-free license, unlimited in duration, to use that
@@ -2596,14 +2748,14 @@
 licensee, and is addressed as &ldquo;you&rdquo;.  You accept the license if you
 copy, modify or distribute the work in a way requiring permission
 under copyright law.
-
-     <p>A &ldquo;Modified Version&rdquo; of the Document means any work 
containing the
+</p>
+<p>A &ldquo;Modified Version&rdquo; of the Document means any work containing 
the
 Document or a portion of it, either copied verbatim, or with
 modifications and/or translated into another language.
-
-     <p>A &ldquo;Secondary Section&rdquo; is a named appendix or a 
front-matter section
+</p>
+<p>A &ldquo;Secondary Section&rdquo; is a named appendix or a front-matter 
section
 of the Document that deals exclusively with the relationship of the
-publishers or authors of the Document to the Document's overall
+publishers or authors of the Document to the Document&rsquo;s overall
 subject (or to related matters) and contains nothing that could fall
 directly within that overall subject.  (Thus, if the Document is in
 part a textbook of mathematics, a Secondary Section may not explain
@@ -2611,21 +2763,21 @@
 connection with the subject or with related matters, or of legal,
 commercial, philosophical, ethical or political position regarding
 them.
-
-     <p>The &ldquo;Invariant Sections&rdquo; are certain Secondary Sections 
whose titles
+</p>
+<p>The &ldquo;Invariant Sections&rdquo; are certain Secondary Sections whose 
titles
 are designated, as being those of Invariant Sections, in the notice
 that says that the Document is released under this License.  If a
 section does not fit the above definition of Secondary then it is not
 allowed to be designated as Invariant.  The Document may contain zero
 Invariant Sections.  If the Document does not identify any Invariant
 Sections then there are none.
-
-     <p>The &ldquo;Cover Texts&rdquo; are certain short passages of text that 
are listed,
+</p>
+<p>The &ldquo;Cover Texts&rdquo; are certain short passages of text that are 
listed,
 as Front-Cover Texts or Back-Cover Texts, in the notice that says that
 the Document is released under this License.  A Front-Cover Text may
 be at most 5 words, and a Back-Cover Text may be at most 25 words.
-
-     <p>A &ldquo;Transparent&rdquo; copy of the Document means a 
machine-readable copy,
+</p>
+<p>A &ldquo;Transparent&rdquo; copy of the Document means a machine-readable 
copy,
 represented in a format whose specification is available to the
 general public, that is suitable for revising the document
 straightforwardly with generic text editors or (for images composed of
@@ -2637,8 +2789,8 @@
 or discourage subsequent modification by readers is not Transparent. 
 An image format is not Transparent if used for any substantial amount
 of text.  A copy that is not &ldquo;Transparent&rdquo; is called 
&ldquo;Opaque&rdquo;.
-
-     <p>Examples of suitable formats for Transparent copies include plain
+</p>
+<p>Examples of suitable formats for Transparent copies include plain
 ASCII without markup, Texinfo input format, LaTeX input
 format, SGML or XML using a publicly available
 DTD, and standard-conforming simple HTML,
@@ -2650,35 +2802,35 @@
 not generally available, and the machine-generated HTML,
 PostScript or PDF produced by some word processors for
 output purposes only.
-
-     <p>The &ldquo;Title Page&rdquo; means, for a printed book, the title page 
itself,
+</p>
+<p>The &ldquo;Title Page&rdquo; means, for a printed book, the title page 
itself,
 plus such following pages as are needed to hold, legibly, the material
 this License requires to appear in the title page.  For works in
 formats which do not have any title page as such, &ldquo;Title Page&rdquo; 
means
-the text near the most prominent appearance of the work's title,
+the text near the most prominent appearance of the work&rsquo;s title,
 preceding the beginning of the body of the text.
-
-     <p>The &ldquo;publisher&rdquo; means any person or entity that 
distributes copies
+</p>
+<p>The &ldquo;publisher&rdquo; means any person or entity that distributes 
copies
 of the Document to the public.
-
-     <p>A section &ldquo;Entitled XYZ&rdquo; means a named subunit of the 
Document whose
+</p>
+<p>A section &ldquo;Entitled XYZ&rdquo; means a named subunit of the Document 
whose
 title either is precisely XYZ or contains XYZ in parentheses following
 text that translates XYZ in another language.  (Here XYZ stands for a
 specific section name mentioned below, such as &ldquo;Acknowledgements&rdquo;,
 &ldquo;Dedications&rdquo;, &ldquo;Endorsements&rdquo;, or 
&ldquo;History&rdquo;.)  To &ldquo;Preserve the Title&rdquo;
 of such a section when you modify the Document means that it remains a
 section &ldquo;Entitled XYZ&rdquo; according to this definition.
-
-     <p>The Document may include Warranty Disclaimers next to the notice which
+</p>
+<p>The Document may include Warranty Disclaimers next to the notice which
 states that this License applies to the Document.  These Warranty
 Disclaimers are considered to be included by reference in this
 License, but only as regards disclaiming warranties: any other
 implication that these Warranty Disclaimers may have is void and has
 no effect on the meaning of this License.
+</p>
+</li><li> VERBATIM COPYING
 
-     <li>VERBATIM COPYING
-
-     <p>You may copy and distribute the Document in any medium, either
+<p>You may copy and distribute the Document in any medium, either
 commercially or noncommercially, provided that this License, the
 copyright notices, and the license notice saying this License applies
 to the Document are reproduced in all copies, and that you add no other
@@ -2687,15 +2839,15 @@
 copying of the copies you make or distribute.  However, you may accept
 compensation in exchange for copies.  If you distribute a large enough
 number of copies you must also follow the conditions in section 3.
-
-     <p>You may also lend copies, under the same conditions stated above, and
+</p>
+<p>You may also lend copies, under the same conditions stated above, and
 you may publicly display copies.
+</p>
+</li><li> COPYING IN QUANTITY
 
-     <li>COPYING IN QUANTITY
-
-     <p>If you publish printed copies (or copies in media that commonly have
+<p>If you publish printed copies (or copies in media that commonly have
 printed covers) of the Document, numbering more than 100, and the
-Document's license notice requires Cover Texts, you must enclose the
+Document&rsquo;s license notice requires Cover Texts, you must enclose the
 copies in covers that carry, clearly and legibly, all these Cover
 Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on
 the back cover.  Both covers must also clearly and legibly identify
@@ -2705,13 +2857,13 @@
 Copying with changes limited to the covers, as long as they preserve
 the title of the Document and satisfy these conditions, can be treated
 as verbatim copying in other respects.
-
-     <p>If the required texts for either cover are too voluminous to fit
+</p>
+<p>If the required texts for either cover are too voluminous to fit
 legibly, you should put the first ones listed (as many as fit
 reasonably) on the actual cover, and continue the rest onto adjacent
 pages.
-
-     <p>If you publish or distribute Opaque copies of the Document numbering
+</p>
+<p>If you publish or distribute Opaque copies of the Document numbering
 more than 100, you must either include a machine-readable Transparent
 copy along with each Opaque copy, or state in or with each Opaque copy
 a computer-network location from which the general network-using
@@ -2723,51 +2875,51 @@
 location until at least one year after the last time you distribute an
 Opaque copy (directly or through your agents or retailers) of that
 edition to the public.
-
-     <p>It is requested, but not required, that you contact the authors of the
+</p>
+<p>It is requested, but not required, that you contact the authors of the
 Document well before redistributing any large number of copies, to give
 them a chance to provide you with an updated version of the Document.
+</p>
+</li><li> MODIFICATIONS
 
-     <li>MODIFICATIONS
-
-     <p>You may copy and distribute a Modified Version of the Document under
+<p>You may copy and distribute a Modified Version of the Document under
 the conditions of sections 2 and 3 above, provided that you release
 the Modified Version under precisely this License, with the Modified
 Version filling the role of the Document, thus licensing distribution
 and modification of the Modified Version to whoever possesses a copy
 of it.  In addition, you must do these things in the Modified Version:
-
-          <ol type=A start=1>
-<li>Use in the Title Page (and on the covers, if any) a title distinct
+</p>
+<ol>
+<li> Use in the Title Page (and on the covers, if any) a title distinct
 from that of the Document, and from those of previous versions
 (which should, if there were any, be listed in the History section
 of the Document).  You may use the same title as a previous version
 if the original publisher of that version gives permission.
 
-          <li>List on the Title Page, as authors, one or more persons or 
entities
+</li><li> List on the Title Page, as authors, one or more persons or entities
 responsible for authorship of the modifications in the Modified
 Version, together with at least five of the principal authors of the
 Document (all of its principal authors, if it has fewer than five),
 unless they release you from this requirement.
 
-          <li>State on the Title page the name of the publisher of the
+</li><li> State on the Title page the name of the publisher of the
 Modified Version, as the publisher.
 
-          <li>Preserve all the copyright notices of the Document.
+</li><li> Preserve all the copyright notices of the Document.
 
-          <li>Add an appropriate copyright notice for your modifications
+</li><li> Add an appropriate copyright notice for your modifications
 adjacent to the other copyright notices.
 
-          <li>Include, immediately after the copyright notices, a license 
notice
+</li><li> Include, immediately after the copyright notices, a license notice
 giving the public permission to use the Modified Version under the
 terms of this License, in the form shown in the Addendum below.
 
-          <li>Preserve in that license notice the full lists of Invariant 
Sections
-and required Cover Texts given in the Document's license notice.
+</li><li> Preserve in that license notice the full lists of Invariant Sections
+and required Cover Texts given in the Document&rsquo;s license notice.
 
-          <li>Include an unaltered copy of this License.
+</li><li> Include an unaltered copy of this License.
 
-          <li>Preserve the section Entitled &ldquo;History&rdquo;, Preserve 
its Title, and add
+</li><li> Preserve the section Entitled &ldquo;History&rdquo;, Preserve its 
Title, and add
 to it an item stating at least the title, year, new authors, and
 publisher of the Modified Version as given on the Title Page.  If
 there is no section Entitled &ldquo;History&rdquo; in the Document, create one
@@ -2775,7 +2927,7 @@
 given on its Title Page, then add an item describing the Modified
 Version as stated in the previous sentence.
 
-          <li>Preserve the network location, if any, given in the Document for
+</li><li> Preserve the network location, if any, given in the Document for
 public access to a Transparent copy of the Document, and likewise
 the network locations given in the Document for previous versions
 it was based on.  These may be placed in the &ldquo;History&rdquo; section. 
@@ -2783,38 +2935,38 @@
 least four years before the Document itself, or if the original
 publisher of the version it refers to gives permission.
 
-          <li>For any section Entitled &ldquo;Acknowledgements&rdquo; or 
&ldquo;Dedications&rdquo;, Preserve
+</li><li> For any section Entitled &ldquo;Acknowledgements&rdquo; or 
&ldquo;Dedications&rdquo;, Preserve
 the Title of the section, and preserve in the section all the
 substance and tone of each of the contributor acknowledgements and/or
 dedications given therein.
 
-          <li>Preserve all the Invariant Sections of the Document,
+</li><li> Preserve all the Invariant Sections of the Document,
 unaltered in their text and in their titles.  Section numbers
 or the equivalent are not considered part of the section titles.
 
-          <li>Delete any section Entitled &ldquo;Endorsements&rdquo;.  Such a 
section
+</li><li> Delete any section Entitled &ldquo;Endorsements&rdquo;.  Such a 
section
 may not be included in the Modified Version.
 
-          <li>Do not retitle any existing section to be Entitled 
&ldquo;Endorsements&rdquo; or
+</li><li> Do not retitle any existing section to be Entitled 
&ldquo;Endorsements&rdquo; or
 to conflict in title with any Invariant Section.
 
-          <li>Preserve any Warranty Disclaimers.
-          </ol>
+</li><li> Preserve any Warranty Disclaimers.
+</li></ol>
 
-     <p>If the Modified Version includes new front-matter sections or
+<p>If the Modified Version includes new front-matter sections or
 appendices that qualify as Secondary Sections and contain no material
 copied from the Document, you may at your option designate some or all
 of these sections as invariant.  To do this, add their titles to the
-list of Invariant Sections in the Modified Version's license notice. 
+list of Invariant Sections in the Modified Version&rsquo;s license notice.
 These titles must be distinct from any other section titles.
-
-     <p>You may add a section Entitled &ldquo;Endorsements&rdquo;, provided it 
contains
+</p>
+<p>You may add a section Entitled &ldquo;Endorsements&rdquo;, provided it 
contains
 nothing but endorsements of your Modified Version by various
 parties&mdash;for example, statements of peer review or that the text has
 been approved by an organization as the authoritative definition of a
 standard.
-
-     <p>You may add a passage of up to five words as a Front-Cover Text, and a
+</p>
+<p>You may add a passage of up to five words as a Front-Cover Text, and a
 passage of up to 25 words as a Back-Cover Text, to the end of the list
 of Cover Texts in the Modified Version.  Only one passage of
 Front-Cover Text and one of Back-Cover Text may be added by (or
@@ -2823,21 +2975,21 @@
 by arrangement made by the same entity you are acting on behalf of,
 you may not add another; but you may replace the old one, on explicit
 permission from the previous publisher that added the old one.
-
-     <p>The author(s) and publisher(s) of the Document do not by this License
+</p>
+<p>The author(s) and publisher(s) of the Document do not by this License
 give permission to use their names for publicity for or to assert or
 imply endorsement of any Modified Version.
+</p>
+</li><li> COMBINING DOCUMENTS
 
-     <li>COMBINING DOCUMENTS
-
-     <p>You may combine the Document with other documents released under this
+<p>You may combine the Document with other documents released under this
 License, under the terms defined in section 4 above for modified
 versions, provided that you include in the combination all of the
 Invariant Sections of all of the original documents, unmodified, and
 list them all as Invariant Sections of your combined work in its
 license notice, and that you preserve all their Warranty Disclaimers.
-
-     <p>The combined work need only contain one copy of this License, and
+</p>
+<p>The combined work need only contain one copy of this License, and
 multiple identical Invariant Sections may be replaced with a single
 copy.  If there are multiple Invariant Sections with the same name but
 different contents, make the title of each such section unique by
@@ -2845,48 +2997,48 @@
 author or publisher of that section if known, or else a unique number. 
 Make the same adjustment to the section titles in the list of
 Invariant Sections in the license notice of the combined work.
-
-     <p>In the combination, you must combine any sections Entitled 
&ldquo;History&rdquo;
+</p>
+<p>In the combination, you must combine any sections Entitled 
&ldquo;History&rdquo;
 in the various original documents, forming one section Entitled
 &ldquo;History&rdquo;; likewise combine any sections Entitled 
&ldquo;Acknowledgements&rdquo;,
 and any sections Entitled &ldquo;Dedications&rdquo;.  You must delete all
 sections Entitled &ldquo;Endorsements.&rdquo;
+</p>
+</li><li> COLLECTIONS OF DOCUMENTS
 
-     <li>COLLECTIONS OF DOCUMENTS
-
-     <p>You may make a collection consisting of the Document and other 
documents
+<p>You may make a collection consisting of the Document and other documents
 released under this License, and replace the individual copies of this
 License in the various documents with a single copy that is included in
 the collection, provided that you follow the rules of this License for
 verbatim copying of each of the documents in all other respects.
-
-     <p>You may extract a single document from such a collection, and 
distribute
+</p>
+<p>You may extract a single document from such a collection, and distribute
 it individually under this License, provided you insert a copy of this
 License into the extracted document, and follow this License in all
 other respects regarding verbatim copying of that document.
+</p>
+</li><li> AGGREGATION WITH INDEPENDENT WORKS
 
-     <li>AGGREGATION WITH INDEPENDENT WORKS
-
-     <p>A compilation of the Document or its derivatives with other separate
+<p>A compilation of the Document or its derivatives with other separate
 and independent documents or works, in or on a volume of a storage or
 distribution medium, is called an &ldquo;aggregate&rdquo; if the copyright
 resulting from the compilation is not used to limit the legal rights
-of the compilation's users beyond what the individual works permit. 
+of the compilation&rsquo;s users beyond what the individual works permit.
 When the Document is included in an aggregate, this License does not
 apply to the other works in the aggregate which are not themselves
 derivative works of the Document.
-
-     <p>If the Cover Text requirement of section 3 is applicable to these
+</p>
+<p>If the Cover Text requirement of section 3 is applicable to these
 copies of the Document, then if the Document is less than one half of
-the entire aggregate, the Document's Cover Texts may be placed on
+the entire aggregate, the Document&rsquo;s Cover Texts may be placed on
 covers that bracket the Document within the aggregate, or the
 electronic equivalent of covers if the Document is in electronic form. 
 Otherwise they must appear on printed covers that bracket the whole
 aggregate.
+</p>
+</li><li> TRANSLATION
 
-     <li>TRANSLATION
-
-     <p>Translation is considered a kind of modification, so you may
+<p>Translation is considered a kind of modification, so you may
 distribute translations of the Document under the terms of section 4. 
 Replacing Invariant Sections with translations requires special
 permission from their copyright holders, but you may include
@@ -2898,48 +3050,48 @@
 of those notices and disclaimers.  In case of a disagreement between
 the translation and the original version of this License or a notice
 or disclaimer, the original version will prevail.
-
-     <p>If a section in the Document is Entitled 
&ldquo;Acknowledgements&rdquo;,
+</p>
+<p>If a section in the Document is Entitled &ldquo;Acknowledgements&rdquo;,
 &ldquo;Dedications&rdquo;, or &ldquo;History&rdquo;, the requirement (section 
4) to Preserve
 its Title (section 1) will typically require changing the actual
 title.
+</p>
+</li><li> TERMINATION
 
-     <li>TERMINATION
-
-     <p>You may not copy, modify, sublicense, or distribute the Document
+<p>You may not copy, modify, sublicense, or distribute the Document
 except as expressly provided under this License.  Any attempt
 otherwise to copy, modify, sublicense, or distribute it is void, and
 will automatically terminate your rights under this License.
-
-     <p>However, if you cease all violation of this License, then your license
+</p>
+<p>However, if you cease all violation of this License, then your license
 from a particular copyright holder is reinstated (a) provisionally,
 unless and until the copyright holder explicitly and finally
 terminates your license, and (b) permanently, if the copyright holder
 fails to notify you of the violation by some reasonable means prior to
 60 days after the cessation.
-
-     <p>Moreover, your license from a particular copyright holder is
+</p>
+<p>Moreover, your license from a particular copyright holder is
 reinstated permanently if the copyright holder notifies you of the
 violation by some reasonable means, this is the first time you have
 received notice of violation of this License (for any work) from that
 copyright holder, and you cure the violation prior to 30 days after
 your receipt of the notice.
-
-     <p>Termination of your rights under this section does not terminate the
+</p>
+<p>Termination of your rights under this section does not terminate the
 licenses of parties who have received copies or rights from you under
 this License.  If your rights have been terminated and not permanently
 reinstated, receipt of a copy of some or all of the same material does
 not give you any rights to use it.
+</p>
+</li><li> FUTURE REVISIONS OF THIS LICENSE
 
-     <li>FUTURE REVISIONS OF THIS LICENSE
-
-     <p>The Free Software Foundation may publish new, revised versions
+<p>The Free Software Foundation may publish new, revised versions
 of the GNU Free Documentation License from time to time.  Such new
 versions will be similar in spirit to the present version, but may
 differ in detail to address new problems or concerns.  See
 <a href="http://www.gnu.org/copyleft/";>http://www.gnu.org/copyleft/</a>.
-
-     <p>Each version of the License is given a distinguishing version number. 
+</p>
+<p>Each version of the License is given a distinguishing version number.
 If the Document specifies that a particular numbered version of this
 License &ldquo;or any later version&rdquo; applies to it, you have the option 
of
 following the terms and conditions either of that specified version or
@@ -2948,47 +3100,49 @@
 number of this License, you may choose any version ever published (not
 as a draft) by the Free Software Foundation.  If the Document
 specifies that a proxy can decide which future versions of this
-License can be used, that proxy's public statement of acceptance of a
+License can be used, that proxy&rsquo;s public statement of acceptance of a
 version permanently authorizes you to choose that version for the
 Document.
+</p>
+</li><li> RELICENSING
 
-     <li>RELICENSING
-
-     <p>&ldquo;Massive Multiauthor Collaboration Site&rdquo; (or &ldquo;MMC 
Site&rdquo;) means any
+<p>&ldquo;Massive Multiauthor Collaboration Site&rdquo; (or &ldquo;MMC 
Site&rdquo;) means any
 World Wide Web server that publishes copyrightable works and also
 provides prominent facilities for anybody to edit those works.  A
 public wiki that anybody can edit is an example of such a server.  A
 &ldquo;Massive Multiauthor Collaboration&rdquo; (or &ldquo;MMC&rdquo;) 
contained in the
 site means any set of copyrightable works thus published on the MMC
 site.
-
-     <p>&ldquo;CC-BY-SA&rdquo; means the Creative Commons Attribution-Share 
Alike 3.0
+</p>
+<p>&ldquo;CC-BY-SA&rdquo; means the Creative Commons Attribution-Share Alike 
3.0
 license published by Creative Commons Corporation, a not-for-profit
 corporation with a principal place of business in San Francisco,
 California, as well as future copyleft versions of that license
 published by that same organization.
-
-     <p>&ldquo;Incorporate&rdquo; means to publish or republish a Document, in 
whole or
+</p>
+<p>&ldquo;Incorporate&rdquo; means to publish or republish a Document, in 
whole or
 in part, as part of another Document.
-
-     <p>An MMC is &ldquo;eligible for relicensing&rdquo; if it is licensed 
under this
+</p>
+<p>An MMC is &ldquo;eligible for relicensing&rdquo; if it is licensed under 
this
 License, and if all works that were first published under this License
 somewhere other than this MMC, and subsequently incorporated in whole
 or in part into the MMC, (1) had no cover texts or invariant sections,
 and (2) were thus incorporated prior to November 1, 2008.
-
-     <p>The operator of an MMC Site may republish an MMC contained in the site
+</p>
+<p>The operator of an MMC Site may republish an MMC contained in the site
 under CC-BY-SA on the same site at any time before August 1, 2009,
 provided the MMC is eligible for relicensing.
+</p>
+</li></ol>
 
-        </ol>
-
-<h3 class="heading">ADDENDUM: How to use this License for your documents</h3>
+<a name="ADDENDUM_003a-How-to-use-this-License-for-your-documents"></a>
+<h2 class="heading">ADDENDUM: How to use this License for your documents</h2>
 
 <p>To use this License in a document you have written, include a copy of
 the License in the document and put the following copyright and
 license notices just after the title page:
-
+</p>
+<div class="smallexample">
 <pre class="smallexample">       Copyright (C)  <var>year</var>  <var>your 
name</var>.
        Permission is granted to copy, distribute and/or modify this document
        under the terms of the GNU Free Documentation License, Version 1.3
@@ -2996,133 +3150,279 @@
        with no Invariant Sections, no Front-Cover Texts, and no Back-Cover
        Texts.  A copy of the license is included in the section entitled ``GNU
        Free Documentation License''.
-</pre>
-   <p>If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts,
-replace the &ldquo;with<small class="dots">...</small>Texts.&rdquo; line with 
this:
+</pre></div>
 
+<p>If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts,
+replace the &ldquo;with&hellip;Texts.&rdquo; line with this:
+</p>
+<div class="smallexample">
 <pre class="smallexample">         with the Invariant Sections being <var>list 
their titles</var>, with
          the Front-Cover Texts being <var>list</var>, and with the Back-Cover 
Texts
          being <var>list</var>.
-</pre>
-   <p>If you have Invariant Sections without Cover Texts, or some other
+</pre></div>
+
+<p>If you have Invariant Sections without Cover Texts, or some other
 combination of the three, merge those two alternatives to suit the
 situation.
-
-   <p>If your document contains nontrivial examples of program code, we
+</p>
+<p>If your document contains nontrivial examples of program code, we
 recommend releasing these examples in parallel under your choice of
 free software license, such as the GNU General Public License,
 to permit their use in free software.
+</p>
+
 
-<!-- Local Variables: -->
-<!-- ispell-local-pdict: "ispell-dict" -->
-<!-- End: -->
-<div class="node">
-<a name="Index"></a>
-<p><hr>
-Previous:&nbsp;<a rel="previous" accesskey="p" 
href="#GNU-Free-Documentation-License">GNU Free Documentation License</a>,
-Up:&nbsp;<a rel="up" accesskey="u" href="#Top">Top</a>
-
-</div>
-
-<h2 class="unnumbered">Index</h2>
-
-<ul class="index-cp" compact>
-<li><a href="#index-g_t_0024-keywords-in-web-pages-74">$ keywords in web 
pages</a>: <a href="#CVS-Keywords-in-Web-Pages">CVS Keywords in Web 
Pages</a></li>
-<li><a 
href="#index-g_t_0040file_007b_002fgd_002fgnuorg_007d-directory-23"><samp><span 
class="file">/gd/gnuorg</span></samp> directory</a>: <a 
href="#Copyright-Papers">Copyright Papers</a></li>
-<li><a 
href="#index-g_t_0040email_007bbug_002dgnu_002dutils_0040_0040gnu_002eorg_007d-35"><a
 href="mailto:address@hidden";>address@hidden</a></a>: <a 
href="#Standard-Mailing-Lists">Standard Mailing Lists</a></li>
-<li><a 
href="#index-g_t_0040email_007bmaintainers_0040_0040gnu_002eorg_007d-19"><a 
href="mailto:address@hidden";>address@hidden</a></a>: <a 
href="#Stepping-Down">Stepping Down</a></li>
-<li><a href="#index-advisory-committee-8">advisory committee</a>: <a 
href="#Getting-Help">Getting Help</a></li>
-<li><a 
href="#index-g_t_0040code_007balpha_002egnu_002eorg_007d_002c-test-release-site-58"><code>alpha.gnu.org</code>,
 test release site</a>: <a href="#Test-Releases">Test Releases</a></li>
-<li><a 
href="#index-announcement-mailing-list_002c-project_002dspecific-67">announcement
 mailing list, project-specific</a>: <a 
href="#Announcements">Announcements</a></li>
-<li><a href="#index-announcements-63">announcements</a>: <a 
href="#Announcements">Announcements</a></li>
-<li><a href="#index-announcements_002c-mailing-list-for-37">announcements, 
mailing list for</a>: <a href="#Standard-Mailing-Lists">Standard Mailing 
Lists</a></li>
-<li><a href="#index-g_t_0040file_007bAUTHORS_007d-file-26"><samp><span 
class="file">AUTHORS</span></samp> file</a>: <a 
href="#Recording-Contributors">Recording Contributors</a></li>
-<li><a href="#index-automake-48"><code>automake</code></a>: <a 
href="#Distribution-tar-Files">Distribution tar Files</a></li>
-<li><a href="#index-beta-releases-56">beta releases</a>: <a 
href="#Test-Releases">Test Releases</a></li>
-<li><a href="#index-bug-reports_002c-handling-42">bug reports, handling</a>: 
<a href="#Replying-to-Mail">Replying to Mail</a></li>
-<li><a 
href="#index-g_t_0040code_007bbug_002dstandards_0040_0040gnu_002eorg_007d-email-address-1"><code>address@hidden</code>
 email address</a>: <a href="#Preface">Preface</a></li>
-<li><a href="#index-contents-of-announcements-68">contents of 
announcements</a>: <a href="#Announcements">Announcements</a></li>
-<li><a href="#index-contributions_002c-accepting-29">contributions, 
accepting</a>: <a href="#Clean-Ups">Clean Ups</a></li>
-<li><a href="#index-copyright-notices-in-program-files-27">copyright notices 
in program files</a>: <a href="#Copyright-Notices">Copyright Notices</a></li>
-<li><a href="#index-copyright-papers-21">copyright papers</a>: <a 
href="#Copyright-Papers">Copyright Papers</a></li>
-<li><a href="#index-creating-mailing-lists-38">creating mailing lists</a>: <a 
href="#Creating-Mailing-Lists">Creating Mailing Lists</a></li>
-<li><a href="#index-CVS-keywords-in-web-pages-72">CVS keywords in web 
pages</a>: <a href="#CVS-Keywords-in-Web-Pages">CVS Keywords in Web 
Pages</a></li>
-<li><a href="#index-CVS-repository-85">CVS repository</a>: <a 
href="#Hosting">Hosting</a></li>
-<li><a href="#index-data-base-of-GNU-copyright-assignments-22">data base of 
GNU copyright assignments</a>: <a href="#Copyright-Papers">Copyright 
Papers</a></li>
-<li><a href="#index-development-method_002c-open-source-82">development 
method, open source</a>: <a href="#Free-Software-and-Open-Source">Free Software 
and Open Source</a></li>
-<li><a href="#index-diff-50"><code>diff</code></a>: <a 
href="#Distribution-Patches">Distribution Patches</a></li>
-<li><a href="#index-Directory_002c-Free-Software-95">Directory, Free 
Software</a>: <a href="#Free-Software-Directory">Free Software 
Directory</a></li>
-<li><a href="#index-distribution_002c-tar-files-47">distribution, tar 
files</a>: <a href="#Distribution-tar-Files">Distribution tar Files</a></li>
-<li><a href="#index-Donations_002c-for-packages-92">Donations, for 
packages</a>: <a href="#Donations">Donations</a></li>
-<li><a href="#index-down_002c-when-GNU-machines-are-9">down, when GNU machines 
are</a>: <a href="#Getting-Help">Getting Help</a></li>
-<li><a href="#index-email-31">email</a>: <a href="#Mail">Mail</a></li>
-<li><a href="#index-ethics-76">ethics</a>: <a 
href="#Ethical-and-Philosophical-Consideration">Ethical and Philosophical 
Consideration</a></li>
-<li><a href="#index-FDL_002c-GNU-Free-Documentation-License-97">FDL, GNU Free 
Documentation License</a>: <a href="#GNU-Free-Documentation-License">GNU Free 
Documentation License</a></li>
-<li><a 
href="#index-g_t_0040code_007bfencepost_002egnu_002eorg_007d-GNU-machine-16"><code>fencepost.gnu.org</code>
 GNU machine</a>: <a href="#Getting-a-GNU-Account">Getting a GNU 
Account</a></li>
-<li><a href="#index-Free-Software-Directory-94">Free Software Directory</a>: 
<a href="#Free-Software-Directory">Free Software Directory</a></li>
-<li><a href="#index-free-software-movement-79">free software movement</a>: <a 
href="#Free-Software-and-Open-Source">Free Software and Open Source</a></li>
-<li><a href="#index-FSF-system-administrators-13">FSF system 
administrators</a>: <a href="#Getting-Help">Getting Help</a></li>
-<li><a href="#index-FTP-site-89">FTP site</a>: <a 
href="#Hosting">Hosting</a></li>
-<li><a href="#index-ftp-uploads_002c-automated-59">ftp uploads, automated</a>: 
<a href="#Automated-FTP-Uploads">Automated FTP Uploads</a></li>
-<li><a 
href="#index-g_t_0040code_007bftp_002egnu_002eorg_007d_002c-the-GNU-release-site-54"><code>ftp.gnu.org</code>,
 the GNU release site</a>: <a 
href="#Distribution-on-ftp_002egnu_002eorg">Distribution on ftp.gnu.org</a></li>
-<li><a href="#index-gendocs_002esh-70"><code>gendocs.sh</code></a>: <a 
href="#Invoking-gendocs_002esh">Invoking gendocs.sh</a></li>
-<li><a href="#index-generating-documentation-output-71">generating 
documentation output</a>: <a href="#Invoking-gendocs_002esh">Invoking 
gendocs.sh</a></li>
-<li><a href="#index-GNU-ftp-site-53">GNU ftp site</a>: <a 
href="#Distribution-on-ftp_002egnu_002eorg">Distribution on ftp.gnu.org</a></li>
-<li><a href="#index-GNU-system-administrators-14">GNU system 
administrators</a>: <a href="#Getting-Help">Getting Help</a></li>
-<li><a href="#index-GNU_002fLinux-84">GNU/Linux</a>: <a 
href="#GNU-and-Linux">GNU and Linux</a></li>
-<li><a 
href="#index-g_t_0040code_007bgnustandards_007d-project-repository-3"><code>gnustandards</code>
 project repository</a>: <a href="#Preface">Preface</a></li>
-<li><a 
href="#index-g_t_0040code_007bgnustandards_002dcommit_0040_0040gnu_002eorg_007d-mailing-list-4"><code>address@hidden</code>
 mailing list</a>: <a href="#Preface">Preface</a></li>
-<li><a href="#index-help-for-users_002c-mailing-list-for-36">help for users, 
mailing list for</a>: <a href="#Standard-Mailing-Lists">Standard Mailing 
Lists</a></li>
-<li><a href="#index-help-requests_002c-handling-43">help requests, 
handling</a>: <a href="#Replying-to-Mail">Replying to Mail</a></li>
-<li><a href="#index-help_002c-getting-6">help, getting</a>: <a 
href="#Getting-Help">Getting Help</a></li>
-<li><a href="#index-hosting-91">hosting</a>: <a 
href="#Hosting">Hosting</a></li>
-<li><a 
href="#index-g_t_0040url_007bhttp_003a_002f_002fidenti_002eca_002fgroup_002ffsfstatus_007d-11"><a
 
href="http://identi.ca/group/fsfstatus";>http://identi.ca/group/fsfstatus</a></a>:
 <a href="#Getting-Help">Getting Help</a></li>
-<li><a 
href="#index-g_t_0040url_007bhttp_003a_002f_002fplanet_002egnu_002eorg_007d-65"><a
 href="http://planet.gnu.org";>http://planet.gnu.org</a></a>: <a 
href="#Announcements">Announcements</a></li>
-<li><a 
href="#index-g_t_0040code_007binfo_002dgnu_007d-mailing-list-64"><code>info-gnu</code>
 mailing list</a>: <a href="#Announcements">Announcements</a></li>
-<li><a href="#index-legal-matters-20">legal matters</a>: <a 
href="#Legal-Matters">Legal Matters</a></li>
-<li><a href="#index-legal-papers-for-changes-in-manuals-24">legal papers for 
changes in manuals</a>: <a href="#Copyright-Papers">Copyright Papers</a></li>
-<li><a href="#index-license-notices-in-program-files-28">license notices in 
program files</a>: <a href="#License-Notices">License Notices</a></li>
-<li><a href="#index-Linux-83">Linux</a>: <a href="#GNU-and-Linux">GNU and 
Linux</a></li>
-<li><a href="#index-mailing-list-for-bug-reports-34">mailing list for bug 
reports</a>: <a href="#Standard-Mailing-Lists">Standard Mailing Lists</a></li>
-<li><a href="#index-mailing-lists_002c-creating-39">mailing lists, 
creating</a>: <a href="#Creating-Mailing-Lists">Creating Mailing Lists</a></li>
-<li><a href="#index-mailing-lists_002c-standard-names-of-33">mailing lists, 
standard names of</a>: <a href="#Standard-Mailing-Lists">Standard Mailing 
Lists</a></li>
-<li><a 
href="#index-g_t_0040code_007bmentors_0040_0040gnu_002eorg_007d-mailing-list-7"><code>address@hidden</code>
 mailing list</a>: <a href="#Getting-Help">Getting Help</a></li>
-<li><a href="#index-Money_002c-donated-to-packages-93">Money, donated to 
packages</a>: <a href="#Donations">Donations</a></li>
-<li><a href="#index-movement_002c-free-software-81">movement, free 
software</a>: <a href="#Free-Software-and-Open-Source">Free Software and Open 
Source</a></li>
-<li><a href="#index-open-source-80">open source</a>: <a 
href="#Free-Software-and-Open-Source">Free Software and Open Source</a></li>
-<li><a href="#index-outage_002c-of-GNU-machines-10">outage, of GNU 
machines</a>: <a href="#Getting-Help">Getting Help</a></li>
-<li><a href="#index-patch-51"><code>patch</code></a>: <a 
href="#Distribution-Patches">Distribution Patches</a></li>
-<li><a href="#index-patches_002c-against-previous-releases-49">patches, 
against previous releases</a>: <a href="#Distribution-Patches">Distribution 
Patches</a></li>
-<li><a href="#index-philosophy-77">philosophy</a>: <a 
href="#Ethical-and-Philosophical-Consideration">Ethical and Philosophical 
Consideration</a></li>
-<li><a href="#index-Piercy_002c-Marge-5">Piercy, Marge</a>: <a 
href="#Preface">Preface</a></li>
-<li><a href="#index-pretest-releases-57">pretest releases</a>: <a 
href="#Test-Releases">Test Releases</a></li>
-<li><a href="#index-proofreading-96">proofreading</a>: <a 
href="#Using-the-Proofreaders-List">Using the Proofreaders List</a></li>
-<li><a href="#index-quality-of-changes-suggested-by-others-30">quality of 
changes suggested by others</a>: <a href="#Clean-Ups">Clean Ups</a></li>
-<li><a href="#index-RCS-keywords-in-web-pages-73">RCS keywords in web 
pages</a>: <a href="#CVS-Keywords-in-Web-Pages">CVS Keywords in Web 
Pages</a></li>
-<li><a href="#index-recording-contributors-25">recording contributors</a>: <a 
href="#Recording-Contributors">Recording Contributors</a></li>
-<li><a href="#index-registration-for-uploads-60">registration for uploads</a>: 
<a href="#Automated-Upload-Registration">Automated Upload Registration</a></li>
-<li><a href="#index-release-site-90">release site</a>: <a 
href="#Hosting">Hosting</a></li>
-<li><a href="#index-repository-86">repository</a>: <a 
href="#Hosting">Hosting</a></li>
-<li><a href="#index-resigning-as-maintainer-18">resigning as maintainer</a>: 
<a href="#Stepping-Down">Stepping Down</a></li>
-<li><a href="#index-responding-to-bug-reports-41">responding to bug 
reports</a>: <a href="#Replying-to-Mail">Replying to Mail</a></li>
-<li><a 
href="#index-Savannah-repository-for-_0040code_007bgnustandards_007d-2">Savannah
 repository for <code>gnustandards</code></a>: <a 
href="#Preface">Preface</a></li>
-<li><a href="#index-Savannah_002c-news-area-66">Savannah, news area</a>: <a 
href="#Announcements">Announcements</a></li>
-<li><a 
href="#index-g_t_0040code_007bsavannah_002dannounce_0040_0040gnu_002eorg_007d-mailing-list-46"><code>address@hidden</code>
 mailing list</a>: <a href="#Old-Versions">Old Versions</a></li>
-<li><a 
href="#index-g_t_0040code_007bsavannah_002dhackers_0040_0040gnu_002eorg_007d-45"><code>address@hidden</code></a>:
 <a href="#Old-Versions">Old Versions</a></li>
-<li><a href="#index-shell-account_002c-on-fencepost-15">shell account, on 
fencepost</a>: <a href="#Getting-a-GNU-Account">Getting a GNU Account</a></li>
-<li><a href="#index-source-repository-87">source repository</a>: <a 
href="#Hosting">Hosting</a></li>
-<li><a href="#index-spam-prevention-40">spam prevention</a>: <a 
href="#Creating-Mailing-Lists">Creating Mailing Lists</a></li>
-<li><a href="#index-standard-mailing-lists-32">standard mailing lists</a>: <a 
href="#Standard-Mailing-Lists">Standard Mailing Lists</a></li>
-<li><a href="#index-stepping-down-as-maintainer-17">stepping down as 
maintainer</a>: <a href="#Stepping-Down">Stepping Down</a></li>
-<li><a href="#index-sysadmin_002c-FSF-12">sysadmin, FSF</a>: <a 
href="#Getting-Help">Getting Help</a></li>
-<li><a href="#index-terminology-78">terminology</a>: <a 
href="#Terminology">Terminology</a></li>
-<li><a href="#index-test-releases-55">test releases</a>: <a 
href="#Test-Releases">Test Releases</a></li>
-<li><a href="#index-time-stamp-in-diffs-52">time stamp in diffs</a>: <a 
href="#Distribution-Patches">Distribution Patches</a></li>
-<li><a href="#index-uploads-62">uploads</a>: <a 
href="#Automated-Upload-Procedure">Automated Upload Procedure</a></li>
-<li><a href="#index-uploads_002c-registration-for-61">uploads, registration 
for</a>: <a href="#Automated-Upload-Registration">Automated Upload 
Registration</a></li>
-<li><a href="#index-version-control-44">version control</a>: <a 
href="#Old-Versions">Old Versions</a></li>
-<li><a href="#index-version-control-system-88">version control system</a>: <a 
href="#Hosting">Hosting</a></li>
-<li><a href="#index-web-pages-69">web pages</a>: <a href="#Web-Pages">Web 
Pages</a></li>
-<li><a href="#index-web-pages_002c-and-CVS-keywords-75">web pages, and CVS 
keywords</a>: <a href="#CVS-Keywords-in-Web-Pages">CVS Keywords in Web 
Pages</a></li>
-   </ul></body></html>
 
+<hr>
+<a name="Index"></a>
+<div class="header">
+<p>
+Previous: <a href="#GNU-Free-Documentation-License" accesskey="p" 
rel="previous">GNU Free Documentation License</a>, Up: <a href="#Top" 
accesskey="u" rel="up">Top</a> &nbsp; [<a href="#SEC_Contents" title="Table of 
contents" rel="contents">Contents</a>][<a href="#Index" title="Index" 
rel="index">Index</a>]</p>
+</div>
+<a name="Index-1"></a>
+<h1 class="unnumbered">Index</h1>
+<table><tr><th valign="top">Jump to: &nbsp; </th><td><a class="summary-letter" 
href="#Index_cp_symbol-1"><b>$</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_symbol-2"><b>/</b></a>
+ &nbsp; 
+<br>
+<a class="summary-letter" href="#Index_cp_letter-A"><b>A</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-B"><b>B</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-C"><b>C</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-D"><b>D</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-E"><b>E</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-F"><b>F</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-G"><b>G</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-H"><b>H</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-I"><b>I</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-L"><b>L</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-M"><b>M</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-O"><b>O</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-P"><b>P</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-Q"><b>Q</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-R"><b>R</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-S"><b>S</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-T"><b>T</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-U"><b>U</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-V"><b>V</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-W"><b>W</b></a>
+ &nbsp; 
+</td></tr></table>
+<table class="index-cp" border="0">
+<tr><td></td><th align="left">Index Entry</th><td>&nbsp;</td><th align="left"> 
Section</th></tr>
+<tr><td colspan="4"> <hr></td></tr>
+<tr><th><a name="Index_cp_symbol-1">$</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a href="#index-_0024-keywords-in-web-pages">$ 
keywords in web pages</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="#CVS-Keywords-in-Web-Pages">CVS Keywords in Web Pages</a></td></tr>
+<tr><td colspan="4"> <hr></td></tr>
+<tr><th><a name="Index_cp_symbol-2">/</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a 
href="#index-_002fgd_002fgnuorg-directory">&lsquo;<tt>/gd/gnuorg</tt>&rsquo; 
directory</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="#Copyright-Papers">Copyright Papers</a></td></tr>
+<tr><td colspan="4"> <hr></td></tr>
+<tr><th><a name="Index_cp_letter-A">A</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a href="#index-advisory-committee">advisory 
committee</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="#Getting-Help">Getting Help</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="#index-alpha_002egnu_002eorg_002c-test-release-site"><code>alpha.gnu.org</code>,
 test release site</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="#Test-Releases">Test Releases</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="#index-announcement-mailing-list_002c-project_002dspecific">announcement 
mailing list, project-specific</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="#Announcements">Announcements</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="#index-announcements">announcements</a>:</td><td>&nbsp;</td><td 
valign="top"><a href="#Announcements">Announcements</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="#index-announcements_002c-mailing-list-for">announcements, mailing list 
for</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="#Standard-Mailing-Lists">Standard Mailing Lists</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="#index-AUTHORS-file">&lsquo;<tt>AUTHORS</tt>&rsquo; 
file</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="#Recording-Contributors">Recording Contributors</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="#index-automake"><code>automake</code></a>:</td><td>&nbsp;</td><td 
valign="top"><a href="#Distribution-tar-Files">Distribution tar 
Files</a></td></tr>
+<tr><td colspan="4"> <hr></td></tr>
+<tr><th><a name="Index_cp_letter-B">B</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a href="#index-beta-releases">beta 
releases</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Test-Releases">Test 
Releases</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-bug-reports_002c-handling">bug 
reports, handling</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="#Replying-to-Mail">Replying to Mail</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="#index-bug_002dgnu_002dutils_0040gnu_002eorg"><a 
href="mailto:address@hidden";>address@hidden</a></a>:</td><td>&nbsp;</td><td 
valign="top"><a href="#Standard-Mailing-Lists">Standard Mailing 
Lists</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="#index-bug_002dstandards_0040gnu_002eorg-email-address"><code>address@hidden</code>
 email address</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="#Preface">Preface</a></td></tr>
+<tr><td colspan="4"> <hr></td></tr>
+<tr><th><a name="Index_cp_letter-C">C</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a 
href="#index-contents-of-announcements">contents of 
announcements</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="#Announcements">Announcements</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="#index-contributions_002c-accepting">contributions, 
accepting</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Clean-Ups">Clean 
Ups</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="#index-copyright-notices-in-program-files">copyright notices in program 
files</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="#Copyright-Notices">Copyright Notices</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-copyright-papers">copyright 
papers</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="#Copyright-Papers">Copyright Papers</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-creating-mailing-lists">creating 
mailing lists</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="#Creating-Mailing-Lists">Creating Mailing Lists</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-CVS-keywords-in-web-pages">CVS 
keywords in web pages</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="#CVS-Keywords-in-Web-Pages">CVS Keywords in Web Pages</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-CVS-repository">CVS 
repository</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="#Hosting">Hosting</a></td></tr>
+<tr><td colspan="4"> <hr></td></tr>
+<tr><th><a name="Index_cp_letter-D">D</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a 
href="#index-data-base-of-GNU-copyright-assignments">data base of GNU copyright 
assignments</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="#Copyright-Papers">Copyright Papers</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="#index-development-method_002c-open-source">development method, open 
source</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="#Free-Software-and-Open-Source">Free Software and Open 
Source</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="#index-diff"><code>diff</code></a>:</td><td>&nbsp;</td><td 
valign="top"><a href="#Distribution-Patches">Distribution Patches</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="#index-Directory_002c-Free-Software">Directory, Free 
Software</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="#Free-Software-Directory">Free Software Directory</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="#index-distribution_002c-tar-files">distribution, tar 
files</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="#Distribution-tar-Files">Distribution tar Files</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="#index-Donations_002c-for-packages">Donations, for 
packages</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="#Donations">Donations</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="#index-down_002c-when-GNU-machines-are">down, when GNU machines 
are</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Getting-Help">Getting 
Help</a></td></tr>
+<tr><td colspan="4"> <hr></td></tr>
+<tr><th><a name="Index_cp_letter-E">E</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a 
href="#index-email">email</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="#Mail">Mail</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="#index-ethics">ethics</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="#Ethical-and-Philosophical-Consideration">Ethical and Philosophical 
Consideration</a></td></tr>
+<tr><td colspan="4"> <hr></td></tr>
+<tr><th><a name="Index_cp_letter-F">F</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a 
href="#index-FDL_002c-GNU-Free-Documentation-License">FDL, GNU Free 
Documentation License</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="#GNU-Free-Documentation-License">GNU Free Documentation 
License</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="#index-fencepost_002egnu_002eorg-GNU-machine"><code>fencepost.gnu.org</code>
 GNU machine</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="#Getting-a-GNU-Account">Getting a GNU Account</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-Free-Software-Directory">Free 
Software Directory</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="#Free-Software-Directory">Free Software Directory</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-free-software-movement">free 
software movement</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="#Free-Software-and-Open-Source">Free Software and Open 
Source</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-FSF-system-administrators">FSF 
system administrators</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="#Getting-Help">Getting Help</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-FTP-site">FTP 
site</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="#Hosting">Hosting</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-ftp-uploads_002c-automated">ftp 
uploads, automated</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="#Automated-FTP-Uploads">Automated FTP Uploads</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="#index-ftp_002egnu_002eorg_002c-the-GNU-release-site"><code>ftp.gnu.org</code>,
 the GNU release site</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="#Distribution-on-ftp_002egnu_002eorg">Distribution on 
ftp.gnu.org</a></td></tr>
+<tr><td colspan="4"> <hr></td></tr>
+<tr><th><a name="Index_cp_letter-G">G</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a 
href="#index-gendocs_002esh"><code>gendocs.sh</code></a>:</td><td>&nbsp;</td><td
 valign="top"><a href="#Invoking-gendocs_002esh">Invoking 
gendocs.sh</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="#index-generating-documentation-output">generating documentation 
output</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="#Invoking-gendocs_002esh">Invoking gendocs.sh</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-GNU-ftp-site">GNU ftp 
site</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="#Distribution-on-ftp_002egnu_002eorg">Distribution on 
ftp.gnu.org</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-GNU-system-administrators">GNU 
system administrators</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="#Getting-Help">Getting Help</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="#index-GNU_002fLinux">GNU/Linux</a>:</td><td>&nbsp;</td><td 
valign="top"><a href="#GNU-and-Linux">GNU and Linux</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="#index-gnustandards-project-repository"><code>gnustandards</code> project 
repository</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="#Preface">Preface</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="#index-gnustandards_002dcommit_0040gnu_002eorg-mailing-list"><code>address@hidden</code>
 mailing list</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="#Preface">Preface</a></td></tr>
+<tr><td colspan="4"> <hr></td></tr>
+<tr><th><a name="Index_cp_letter-H">H</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a 
href="#index-help-for-users_002c-mailing-list-for">help for users, mailing list 
for</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="#Standard-Mailing-Lists">Standard Mailing Lists</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="#index-help-requests_002c-handling">help requests, 
handling</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="#Replying-to-Mail">Replying to Mail</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-help_002c-getting">help, 
getting</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="#Getting-Help">Getting Help</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="#index-hosting">hosting</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="#Hosting">Hosting</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="#index-http_003a_002f_002fidenti_002eca_002fgroup_002ffsfstatus"><a 
href="http://identi.ca/group/fsfstatus";>http://identi.ca/group/fsfstatus</a></a>:</td><td>&nbsp;</td><td
 valign="top"><a href="#Getting-Help">Getting Help</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="#index-http_003a_002f_002fplanet_002egnu_002eorg"><a 
href="http://planet.gnu.org";>http://planet.gnu.org</a></a>:</td><td>&nbsp;</td><td
 valign="top"><a href="#Announcements">Announcements</a></td></tr>
+<tr><td colspan="4"> <hr></td></tr>
+<tr><th><a name="Index_cp_letter-I">I</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a 
href="#index-info_002dgnu-mailing-list"><code>info-gnu</code> mailing 
list</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="#Announcements">Announcements</a></td></tr>
+<tr><td colspan="4"> <hr></td></tr>
+<tr><th><a name="Index_cp_letter-L">L</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a href="#index-legal-matters">legal 
matters</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Legal-Matters">Legal 
Matters</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="#index-legal-papers-for-changes-in-manuals">legal papers for changes in 
manuals</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="#Copyright-Papers">Copyright Papers</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="#index-license-notices-in-program-files">license notices in program 
files</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="#License-Notices">License Notices</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="#index-Linux">Linux</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="#GNU-and-Linux">GNU and Linux</a></td></tr>
+<tr><td colspan="4"> <hr></td></tr>
+<tr><th><a name="Index_cp_letter-M">M</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a 
href="#index-mailing-list-for-bug-reports">mailing list for bug 
reports</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="#Standard-Mailing-Lists">Standard Mailing Lists</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="#index-mailing-lists_002c-creating">mailing lists, 
creating</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="#Creating-Mailing-Lists">Creating Mailing Lists</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="#index-mailing-lists_002c-standard-names-of">mailing lists, standard 
names of</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="#Standard-Mailing-Lists">Standard Mailing Lists</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-maintainers_0040gnu_002eorg"><a 
href="mailto:address@hidden";>address@hidden</a></a>:</td><td>&nbsp;</td><td 
valign="top"><a href="#Stepping-Down">Stepping Down</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="#index-mentors_0040gnu_002eorg-mailing-list"><code>address@hidden</code> 
mailing list</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="#Getting-Help">Getting Help</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="#index-Money_002c-donated-to-packages">Money, donated to 
packages</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="#Donations">Donations</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="#index-movement_002c-free-software">movement, free 
software</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="#Free-Software-and-Open-Source">Free Software and Open 
Source</a></td></tr>
+<tr><td colspan="4"> <hr></td></tr>
+<tr><th><a name="Index_cp_letter-O">O</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a href="#index-open-source">open 
source</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="#Free-Software-and-Open-Source">Free Software and Open 
Source</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="#index-outage_002c-of-GNU-machines">outage, of GNU 
machines</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="#Getting-Help">Getting Help</a></td></tr>
+<tr><td colspan="4"> <hr></td></tr>
+<tr><th><a name="Index_cp_letter-P">P</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a 
href="#index-patch"><code>patch</code></a>:</td><td>&nbsp;</td><td 
valign="top"><a href="#Distribution-Patches">Distribution Patches</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="#index-patches_002c-against-previous-releases">patches, against previous 
releases</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="#Distribution-Patches">Distribution Patches</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="#index-philosophy">philosophy</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="#Ethical-and-Philosophical-Consideration">Ethical and Philosophical 
Consideration</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-Piercy_002c-Marge">Piercy, 
Marge</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="#Preface">Preface</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-pretest-releases">pretest 
releases</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Test-Releases">Test 
Releases</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="#index-proofreading">proofreading</a>:</td><td>&nbsp;</td><td 
valign="top"><a href="#Using-the-Proofreaders-List">Using the Proofreaders 
List</a></td></tr>
+<tr><td colspan="4"> <hr></td></tr>
+<tr><th><a name="Index_cp_letter-Q">Q</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a 
href="#index-quality-of-changes-suggested-by-others">quality of changes 
suggested by others</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="#Clean-Ups">Clean Ups</a></td></tr>
+<tr><td colspan="4"> <hr></td></tr>
+<tr><th><a name="Index_cp_letter-R">R</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a href="#index-RCS-keywords-in-web-pages">RCS 
keywords in web pages</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="#CVS-Keywords-in-Web-Pages">CVS Keywords in Web Pages</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="#index-recording-contributors">recording 
contributors</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="#Recording-Contributors">Recording Contributors</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="#index-registration-for-uploads">registration for 
uploads</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="#Automated-Upload-Registration">Automated Upload 
Registration</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-release-site">release 
site</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="#Hosting">Hosting</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="#index-repository">repository</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="#Hosting">Hosting</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="#index-resigning-as-maintainer">resigning as 
maintainer</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="#Stepping-Down">Stepping Down</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="#index-responding-to-bug-reports">responding to bug 
reports</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="#Replying-to-Mail">Replying to Mail</a></td></tr>
+<tr><td colspan="4"> <hr></td></tr>
+<tr><th><a name="Index_cp_letter-S">S</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a 
href="#index-Savannah-repository-for-gnustandards">Savannah repository for 
<code>gnustandards</code></a>:</td><td>&nbsp;</td><td valign="top"><a 
href="#Preface">Preface</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="#index-Savannah_002c-news-area">Savannah, news 
area</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="#Announcements">Announcements</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="#index-savannah_002dannounce_0040gnu_002eorg-mailing-list"><code>address@hidden</code>
 mailing list</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="#Old-Versions">Old Versions</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="#index-savannah_002dhackers_0040gnu_002eorg"><code>address@hidden</code></a>:</td><td>&nbsp;</td><td
 valign="top"><a href="#Old-Versions">Old Versions</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="#index-shell-account_002c-on-fencepost">shell account, on 
fencepost</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="#Getting-a-GNU-Account">Getting a GNU Account</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-source-repository">source 
repository</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="#Hosting">Hosting</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-spam-prevention">spam 
prevention</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="#Creating-Mailing-Lists">Creating Mailing Lists</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-standard-mailing-lists">standard 
mailing lists</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="#Standard-Mailing-Lists">Standard Mailing Lists</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="#index-stepping-down-as-maintainer">stepping down as 
maintainer</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="#Stepping-Down">Stepping Down</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-sysadmin_002c-FSF">sysadmin, 
FSF</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Getting-Help">Getting 
Help</a></td></tr>
+<tr><td colspan="4"> <hr></td></tr>
+<tr><th><a name="Index_cp_letter-T">T</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a 
href="#index-terminology">terminology</a>:</td><td>&nbsp;</td><td 
valign="top"><a href="#Terminology">Terminology</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-test-releases">test 
releases</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Test-Releases">Test 
Releases</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-time-stamp-in-diffs">time stamp 
in diffs</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="#Distribution-Patches">Distribution Patches</a></td></tr>
+<tr><td colspan="4"> <hr></td></tr>
+<tr><th><a name="Index_cp_letter-U">U</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a 
href="#index-uploads">uploads</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="#Automated-Upload-Procedure">Automated Upload Procedure</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="#index-uploads_002c-registration-for">uploads, registration 
for</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="#Automated-Upload-Registration">Automated Upload 
Registration</a></td></tr>
+<tr><td colspan="4"> <hr></td></tr>
+<tr><th><a name="Index_cp_letter-V">V</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a href="#index-version-control">version 
control</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Old-Versions">Old 
Versions</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-version-control-system">version 
control system</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="#Hosting">Hosting</a></td></tr>
+<tr><td colspan="4"> <hr></td></tr>
+<tr><th><a name="Index_cp_letter-W">W</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a href="#index-web-pages">web 
pages</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Web-Pages">Web 
Pages</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="#index-web-pages_002c-and-CVS-keywords">web pages, and CVS 
keywords</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="#CVS-Keywords-in-Web-Pages">CVS Keywords in Web Pages</a></td></tr>
+<tr><td colspan="4"> <hr></td></tr>
+</table>
+<table><tr><th valign="top">Jump to: &nbsp; </th><td><a class="summary-letter" 
href="#Index_cp_symbol-1"><b>$</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_symbol-2"><b>/</b></a>
+ &nbsp; 
+<br>
+<a class="summary-letter" href="#Index_cp_letter-A"><b>A</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-B"><b>B</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-C"><b>C</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-D"><b>D</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-E"><b>E</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-F"><b>F</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-G"><b>G</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-H"><b>H</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-I"><b>I</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-L"><b>L</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-M"><b>M</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-O"><b>O</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-P"><b>P</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-Q"><b>Q</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-R"><b>R</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-S"><b>S</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-T"><b>T</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-U"><b>U</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-V"><b>V</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-W"><b>W</b></a>
+ &nbsp; 
+</td></tr></table>
+
+<hr>
+<p>
+
+
+</p>
+</body>
+</html>

Index: maintain.html.gz
===================================================================
RCS file: /web/www/www/prep/maintain/maintain.html.gz,v
retrieving revision 1.69
retrieving revision 1.70
diff -u -b -r1.69 -r1.70
Binary files /tmp/cvsUx4X92 and /tmp/cvs9tEY5J differ

Index: maintain.html_node.tar.gz
===================================================================
RCS file: /web/www/www/prep/maintain/maintain.html_node.tar.gz,v
retrieving revision 1.69
retrieving revision 1.70
diff -u -b -r1.69 -r1.70
Binary files /tmp/cvsKw5ML3 and /tmp/cvsWi76IK differ

Index: maintain.info.tar.gz
===================================================================
RCS file: /web/www/www/prep/maintain/maintain.info.tar.gz,v
retrieving revision 1.68
retrieving revision 1.69
diff -u -b -r1.68 -r1.69
Binary files /tmp/cvsgsaqG6 and /tmp/cvs6bFWEN differ

Index: maintain.pdf
===================================================================
RCS file: /web/www/www/prep/maintain/maintain.pdf,v
retrieving revision 1.69
retrieving revision 1.70
diff -u -b -r1.69 -r1.70
Binary files /tmp/cvsXhl8j7 and /tmp/cvsgui0kO differ

Index: maintain.ps.gz
===================================================================
RCS file: /web/www/www/prep/maintain/maintain.ps.gz,v
retrieving revision 1.68
retrieving revision 1.69
diff -u -b -r1.68 -r1.69
Binary files /tmp/cvs3F3XQ8 and /tmp/cvs7GcBVP differ

Index: maintain.texi.tar.gz
===================================================================
RCS file: /web/www/www/prep/maintain/maintain.texi.tar.gz,v
retrieving revision 1.68
retrieving revision 1.69
diff -u -b -r1.68 -r1.69
Binary files /tmp/cvsdxLxm8 and /tmp/cvszHaNsP differ

Index: maintain.txt
===================================================================
RCS file: /web/www/www/prep/maintain/maintain.txt,v
retrieving revision 1.71
retrieving revision 1.72
diff -u -b -r1.71 -r1.72
--- maintain.txt        7 Sep 2011 01:31:10 -0000       1.71
+++ maintain.txt        7 Sep 2011 14:59:09 -0000       1.72
@@ -1,6 +1,3 @@
-Table of Contents
-*****************
-
 Version
 1 About This Document
 2 Getting Help
@@ -54,8 +51,6 @@
 18 Using the Proofreaders List
 Appendix A GNU Free Documentation License
 Index
-
-
 Version
 *******
 
@@ -70,8 +65,8 @@
      document under the terms of the GNU Free Documentation License,
      Version 1.3 or any later version published by the Free Software
      Foundation; with no Invariant Sections, with no Front-Cover Texts,
-     and with no Back-Cover Texts.  A copy of the license is included
-     in the section entitled "GNU Free Documentation License".
+     and with no Back-Cover Texts.  A copy of the license is included in
+     the section entitled "GNU Free Documentation License".
 
 1 About This Document
 *********************
@@ -79,10 +74,10 @@
 This file contains guidelines and advice for someone who is the
 maintainer of a GNU program on behalf of the GNU Project.  Everyone is
 entitled to change and redistribute GNU software; you need not pay
-attention to this file to get permission.  But if you want to maintain
-a version for widespread distribution, we suggest you follow these
-guidelines.  If you are or would like to be a GNU maintainer, then it
-is essential to follow these guidelines.
+attention to this file to get permission.  But if you want to maintain a
+version for widespread distribution, we suggest you follow these
+guidelines.  If you are or would like to be a GNU maintainer, then it is
+essential to follow these guidelines.
 
    In addition to this document, please read and follow the GNU Coding
 Standards (*note Contents: (standards)Top.).
@@ -90,10 +85,10 @@
    Please send corrections or suggestions for this document to
 <address@hidden>.  If you make a suggestion, please include
 suggested new wording if you can.  We prefer a context diff to the
-Texinfo source, but if that's difficult for you, you can make a diff
-for some other version of this document, or propose it in any way that
-makes it clear.  The source repository for this document can be found
-at `http://savannah.gnu.org/projects/gnustandards'.
+Texinfo source, but if that's difficult for you, you can make a diff for
+some other version of this document, or propose it in any way that makes
+it clear.  The source repository for this document can be found at
+`http://savannah.gnu.org/projects/gnustandards'.
 
    If you want to receive diffs for every change to these GNU documents,
 join the mailing list address@hidden', for instance via
@@ -103,11 +98,11 @@
 
    This document uses the gender-neutral third-person pronouns "person",
 "per", "pers" and "perself" which were promoted, and perhaps invented,
-by Marge Piercy in `Woman on the Edge of Time'.  They are used just
-like "she", "her", "hers" and "herself", except that they apply equally
-to males and females.  For example, "Person placed per new program
-under the GNU GPL, to let the public benefit from per work, and to
-enable per to feel person has done the right thing."
+by Marge Piercy in `Woman on the Edge of Time'.  They are used just like
+"she", "her", "hers" and "herself", except that they apply equally to
+males and females.  For example, "Person placed per new program under
+the GNU GPL, to let the public benefit from per work, and to enable per
+to feel person has done the right thing."
 
    This release of the GNU Maintainer Information was last updated
 September 5, 2011.
@@ -117,16 +112,16 @@
 
 If you have any general questions or encounter a situation where it
 isn't clear how to get something done or who to ask, you (as a GNU
-contributor) can always write to <address@hidden>, which is a list of
-a few experienced GNU folks who have volunteered to answer questions.
-Any GNU-related question is fair game for the `mentors' list.
+contributor) can always write to <address@hidden>, which is a list of a
+few experienced GNU folks who have volunteered to answer questions.  Any
+GNU-related question is fair game for the `mentors' list.
 
    The GNU Advisory Committee helps to coordinate activities in the GNU
 project on behalf of RMS (Richard Stallman, the Chief GNUisance).  If
 you have any organizational questions or concerns you can contact the
 committee at <address@hidden>.  See
-`http://www.gnu.org/contact/gnu-advisory.html' for the current
-committee members.  Additional information is in `/gd/gnuorg/advisory'.
+`http://www.gnu.org/contact/gnu-advisory.html' for the current committee
+members.  Additional information is in `/gd/gnuorg/advisory'.
 
    If you find that any GNU computer systems (`fencepost.gnu.org',
 `ftp.gnu.org', `www.gnu.org', `savannah.gnu.org', ...) seem to be down,
@@ -158,8 +153,8 @@
 
    If you're the official maintainer of a GNU package and you decide to
 step down, please inform the GNU Project (<address@hidden>).  We
-need to know that the package no longer has a maintainer, so we can
-look for and appoint a new maintainer.
+need to know that the package no longer has a maintainer, so we can look
+for and appoint a new maintainer.
 
    If you have an idea for who should take over, please tell
 <address@hidden> your suggestion.  The appointment of a new
@@ -169,8 +164,8 @@
    As your final act as maintainer, it would be helpful to set up or
 update the package under `savannah.gnu.org' (*note Old Versions::).
 This will make it much easier for the new maintainer to pick up where
-you left off and will ensure that the source tree is not misplaced if
-it takes us a while to find a new maintainer.
+you left off and will ensure that the source tree is not misplaced if it
+takes us a while to find a new maintainer.
 
 5 Recruiting Developers
 ***********************
@@ -183,17 +178,17 @@
 help, and encourage those people to participate more.
 
    Some of the people who offer to help will support the GNU Project,
-while others may be interested for other reasons.  Some will support
-the goals of the Free Software Movement, but some may not.  They are
-all welcome to help with the work--we don't ask people's views or
+while others may be interested for other reasons.  Some will support the
+goals of the Free Software Movement, but some may not.  They are all
+welcome to help with the work--we don't ask people's views or
 motivations before they contribute to GNU packages.
 
    As a consequence, you cannot expect all contributors to support the
 GNU Project, or to have a concern for its policies and standards.  So
 part of your job as maintainer is to exercise your authority on these
-points when they arise.  No matter how much of the work other people
-do, you are in charge of what goes in the release.  When a crucial
-point arises, you should calmly state your decision and stick to it.
+points when they arise.  No matter how much of the work other people do,
+you are in charge of what goes in the release.  When a crucial point
+arises, you should calmly state your decision and stick to it.
 
    Sometimes a package has several co-maintainers who share the role of
 maintainer.  Unlike developers who help, co-maintainers have actually
@@ -210,22 +205,22 @@
 6 Legal Matters
 ***************
 
-This chapter describes procedures you should follow for legal reasons
-as you maintain the program, to avoid legal difficulties.
+This chapter describes procedures you should follow for legal reasons as
+you maintain the program, to avoid legal difficulties.
 
 6.1 Copyright Papers
 ====================
 
 If you maintain an FSF-copyrighted package certain legal procedures are
-required when incorporating legally significant changes written by
-other people.  This ensures that the FSF has the legal right to
-distribute the package, and the standing to defend its GPL-covered
-status in court if necessary.
-
-   *Before* incorporating significant changes, make sure that the
-person who wrote the changes has signed copyright papers and that the
-Free Software Foundation has received and signed them.  We may also need
-an employer's disclaimer from the person's employer.
+required when incorporating legally significant changes written by other
+people.  This ensures that the FSF has the legal right to distribute the
+package, and the standing to defend its GPL-covered status in court if
+necessary.
+
+   *Before* incorporating significant changes, make sure that the person
+who wrote the changes has signed copyright papers and that the Free
+Software Foundation has received and signed them.  We may also need an
+employer's disclaimer from the person's employer.
 
    To check whether papers have been received, look in
 `/gd/gnuorg/copyright.list'.  If you can't look there directly,
@@ -243,9 +238,9 @@
 
    In order for the contributor to know person should sign papers, you
 need to ask per for the necessary papers.  If you don't know per well,
-and you don't know that person is used to our ways of handling
-copyright papers, then it might be a good idea to raise the subject
-with a message like this:
+and you don't know that person is used to our ways of handling copyright
+papers, then it might be a good idea to raise the subject with a message
+like this:
 
      Would you be willing to assign the copyright to the Free Software
      Foundation, so that we could install it in PACKAGE?
@@ -260,8 +255,8 @@
 vs. disclaim) and their consequences.
 
    Once the conversation is under way and the contributor is ready for
-more details, you should send one of the templates that are found in
-the directory `/gd/gnuorg/Copyright/'; they are also available from the
+more details, you should send one of the templates that are found in the
+directory `/gd/gnuorg/Copyright/'; they are also available from the
 `doc/Copyright/' directory of the `gnulib' project at
 `http://savannah.gnu.org/projects/gnulib'.  This section explains which
 templates you should use in which circumstances.  *Please don't use any
@@ -282,14 +277,14 @@
 
    If the contributor is likely to keep making changes, person might
 want to sign an assignment for all per future changes to the program.
-So it is useful to offer per that alternative.  If person wants to do
-it that way, send per the `request-assign.future'.
+So it is useful to offer per that alternative.  If person wants to do it
+that way, send per the `request-assign.future'.
 
    When you send a `request-' file, you don't need to fill in anything
 before sending it.  Just send the file verbatim to the contributor.  The
 file gives per instructions for how to ask the FSF to mail per the
-papers to sign.  The `request-' file also raises the issue of getting
-an employer's disclaimer from the contributor's employer.
+papers to sign.  The `request-' file also raises the issue of getting an
+employer's disclaimer from the contributor's employer.
 
    When the contributor emails the form to the FSF, the FSF sends per
 papers to sign.  If person signs them right away, the whole process
@@ -298,11 +293,11 @@
 
    For less common cases, we have template files you should send to the
 contributor.  Be sure to fill in the name of the person and the name of
-the program in these templates, where it says `NAME OF PERSON' and
-`NAME OF PROGRAM', before sending; otherwise person might sign without
+the program in these templates, where it says `NAME OF PERSON' and `NAME
+OF PROGRAM', before sending; otherwise person might sign without
 noticing them, and the papers would be useless.  Note that in some
-templates there is more than one place to put the name of the program
-or the name of the person; be sure to change all of them.  All the
+templates there is more than one place to put the name of the program or
+the name of the person; be sure to change all of them.  All the
 templates raise the issue of an employer's disclaimer as well.
 
    You do not need to ask for separate papers for a manual that is
@@ -321,15 +316,15 @@
 coordinators that they have sent the contributor the papers; if they
 haven't, then you should send the papers.  In any case, you should wait
 for the confirmation from the FSF that the signed papers have been
-received and accepted before integrating the new contributor's
-material, as usual.
+received and accepted before integrating the new contributor's material,
+as usual.
 
    If a contributor is reluctant to sign an assignment for a large
-change, and is willing to sign a disclaimer instead, that is
-acceptable, so you should offer this alternative if it helps you reach
-agreement.  We prefer an assignment for a larger change, so that we can
-enforce the GNU GPL for the new text, but a disclaimer is enough to let
-us use the text.
+change, and is willing to sign a disclaimer instead, that is acceptable,
+so you should offer this alternative if it helps you reach agreement.
+We prefer an assignment for a larger change, so that we can enforce the
+GNU GPL for the new text, but a disclaimer is enough to let us use the
+text.
 
    If you maintain a collection of programs, occasionally someone will
 contribute an entire separate program or manual that should be added to
@@ -343,9 +338,9 @@
 ok.  The contributor should say this, and state the desired pseudonym,
 when answering the `request-' form.  The actual legal papers will use
 the real name, but the FSF will publish only the pseudonym.  When using
-one of the other forms, fill in the real name but ask the contributor
-to discuss the use of a pseudonym with <address@hidden> before sending
-back the signed form.
+one of the other forms, fill in the real name but ask the contributor to
+discuss the use of a pseudonym with <address@hidden> before sending back
+the signed form.
 
    *Although there are other templates besides the ones listed here,
 they are for special circumstances; please do not use them without
@@ -376,9 +371,9 @@
 is irrelevant which parts of it were contributed when.
 
    Copyright does not cover ideas.  If someone contributes ideas but no
-text, these ideas may be morally significant as contributions, and
-worth giving credit for, but they are not significant for copyright
-purposes.  Likewise, bug reports do not count for copyright purposes.
+text, these ideas may be morally significant as contributions, and worth
+giving credit for, but they are not significant for copyright purposes.
+Likewise, bug reports do not count for copyright purposes.
 
    When giving credit to people whose contributions are not legally
 significant for copyright purposes, be careful to make that fact clear.
@@ -424,9 +419,9 @@
 don't need to distinguish work done at different times, only different
 people.  They don't need describe changes in more detail than which
 files or parts of a file were changed.  And they don't need to say
-anything about the function or purpose of a file or change--the
-Register of Copyrights doesn't care what the text does, just who wrote
-or contributed to which parts.
+anything about the function or purpose of a file or change--the Register
+of Copyrights doesn't care what the text does, just who wrote or
+contributed to which parts.
 
    The list should also mention if certain files distributed in the same
 package are really a separate program.
@@ -450,11 +445,11 @@
 
    You can use the change log as the basis for these records, if you
 wish.  Just make sure to record the correct author for each change (the
-person who wrote the change, _not_ the person who installed it), and
-add `(tiny change)' for those changes that are too trivial to matter
-for copyright purposes.  Later on you can update the `AUTHORS' file
-from the change log.  This can even be done automatically, if you are
-careful about the formatting of the change log entries.
+person who wrote the change, _not_ the person who installed it), and add
+`(tiny change)' for those changes that are too trivial to matter for
+copyright purposes.  Later on you can update the `AUTHORS' file from the
+change log.  This can even be done automatically, if you are careful
+about the formatting of the change log entries.
 
 6.4 Copying from Other Packages
 ===============================
@@ -463,8 +458,8 @@
 package with a GPL-compatible license, you should look in the package's
 records to find out the authors of the part you are copying, and list
 them as the contributors of the code that you copied.  If all you did
-was copy it, not write it, then for copyright purposes you are _not_
-one of the contributors of _this_ code.
+was copy it, not write it, then for copyright purposes you are _not_ one
+of the contributors of _this_ code.
 
    Especially when code has been released into the public domain,
 authors sometimes fail to write a license statement in each file.  In
@@ -480,9 +475,8 @@
 other license) is legally sufficient.
 
    Using code that is released under a GPL-compatible free license,
-rather than being in the public domain, may require preserving
-copyright notices or other steps.  Of course, you should do what is
-needed.
+rather than being in the public domain, may require preserving copyright
+notices or other steps.  Of course, you should do what is needed.
 
    If you are maintaining an FSF-copyrighted package, please verify we
 have papers for the code you are copying, _before_ copying it.  If you
@@ -503,17 +497,16 @@
 =====================
 
 You should maintain a proper copyright notice and a license notice in
-each nontrivial file in the package.  (Any file more than ten lines
-long is nontrivial for this purpose.)  This includes header files and
-interface definitions for building or running the program,
-documentation files, and any supporting files.  If a file has been
-explicitly placed in the public domain, then instead of a copyright
-notice, it should have a notice saying explicitly that it is in the
-public domain.
+each nontrivial file in the package.  (Any file more than ten lines long
+is nontrivial for this purpose.)  This includes header files and
+interface definitions for building or running the program, documentation
+files, and any supporting files.  If a file has been explicitly placed
+in the public domain, then instead of a copyright notice, it should have
+a notice saying explicitly that it is in the public domain.
 
    Even image files and sound files should contain copyright notices and
-license notices, if their format permits.  Some formats do not have
-room for textual annotations; for these files, state the copyright and
+license notices, if their format permits.  Some formats do not have room
+for textual annotations; for these files, state the copyright and
 copying permissions in a `README' file in the same directory.
 
    Change log files should have a copyright notice and license notice at
@@ -522,9 +515,9 @@
 
    When a file is automatically generated from some other file in the
 distribution, it is useful for the automatic procedure to copy the
-copyright notice and permission notice of the file it is generated
-from, if possible.  Alternatively, put a notice at the beginning saying
-which file it is generated from.
+copyright notice and permission notice of the file it is generated from,
+if possible.  Alternatively, put a notice at the beginning saying which
+file it is generated from.
 
    A copyright notice looks like this:
 
@@ -552,8 +545,8 @@
 installed is also immediately and automatically published.)  When you
 add the new year, it is not required to keep track of which files have
 seen significant changes in the new year and which have not.  It is
-recommended and simpler to add the new year to all files in the
-package, and be done with it for the rest of the year.
+recommended and simpler to add the new year to all files in the package,
+and be done with it for the rest of the year.
 
    Don't delete old year numbers, though; they are significant since
 they indicate when older versions might theoretically go into the public
@@ -561,11 +554,11 @@
 extend copyright.  If you copy a file into the package from some other
 program, keep the copyright years that come with the file.
 
-   You can use a range (`2008-2010') instead of listing individual
-years (`2008, 2009, 2010') if and only if: 1) every year in the range,
+   You can use a range (`2008-2010') instead of listing individual years
+(`2008, 2009, 2010') if and only if: 1) every year in the range,
 inclusive, really is a "copyrightable" year that would be listed
-individually; _and_ 2) you make an explicit statement in a `README'
-file about this usage.
+individually; _and_ 2) you make an explicit statement in a `README' file
+about this usage.
 
    For files which are regularly copied from another project (such as
 `gnulib'), leave the copyright notice as it is in the original.
@@ -576,8 +569,8 @@
 
    For an FSF-copyrighted package, if you have followed the procedures
 to obtain legal papers, each file should have just one copyright holder:
-the Free Software Foundation, Inc.  You should edit the file's
-copyright notice to list that name and only that name.
+the Free Software Foundation, Inc.  You should edit the file's copyright
+notice to list that name and only that name.
 
    But if contributors are not all assigning their copyrights to a
 single copyright holder, it can easily happen that one file has several
@@ -610,9 +603,9 @@
    The package itself should contain a full copy of GPL in plain text
 (conventionally in a file named `COPYING') and the GNU Free
 Documentation License (included within your documentation, so there is
-no need for a separate plain text version).  If the package contains
-any files distributed under the Lesser GPL, it should contain a full
-copy of its plain text version also (conventionally in a file named
+no need for a separate plain text version).  If the package contains any
+files distributed under the Lesser GPL, it should contain a full copy of
+its plain text version also (conventionally in a file named
 `COPYING.LESSER').
 
    If you have questions about licensing issues for your GNU package,
@@ -631,15 +624,14 @@
 Lesser GPL should be used (again, for the notice wording, *note License
 Notices for Code::).  If a GNU library provides unique functionality,
 however, the GNU GPL should be used.
-`http://www.gnu.org/licenses/why-not-lgpl.html' discusses this
-strategic choice.
+`http://www.gnu.org/licenses/why-not-lgpl.html' discusses this strategic
+choice.
 
    Some of these libraries need to work with programs released under
 GPLv2-only; that is, which allow the GNU GPL version 2 but not later
-versions.  In this case, the GNU package should be released under a
-dual license: GNU GPL version 2 (or any later version) and the GNU
-Lesser GPL version 3 (or any later version).  Here is the notice for
-that case:
+versions.  In this case, the GNU package should be released under a dual
+license: GNU GPL version 2 (or any later version) and the GNU Lesser GPL
+version 3 (or any later version).  Here is the notice for that case:
 
      This file is part of GNU PACKAGE.
 
@@ -682,7 +674,6 @@
      via anonymous Git or CVS.  See
      `http://savannah.gnu.org/projects/gnulib'.
 
-
    The official Texinfo sources for the licenses are also available in
 those same places, so you can include them in your documentation.  A
 GFDL-covered manual should include the GFDL in this way.  *Note GNU
@@ -697,10 +688,10 @@
 
      This file is part of GNU PACKAGE.
 
-     GNU PACKAGE 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.
+     GNU PACKAGE 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.
 
      GNU PACKAGE is distributed in the hope that it will be useful, but
      WITHOUT ANY WARRANTY; without even the implied warranty of
@@ -719,8 +710,8 @@
      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
+     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.
 
@@ -739,8 +730,8 @@
 
 Documentation files should have license notices also.  Manuals should
 use the GNU Free Documentation License.  Following is an example of the
-license notice to use after the copyright line(s) using all the
-features of the GFDL.
+license notice to use after the copyright line(s) using all the features
+of the GFDL.
 
      Permission is granted to copy, distribute and/or modify this document
      under the terms of the GNU Free Documentation License, Version 1.3 or
@@ -763,23 +754,23 @@
 your manual is not published by the FSF, and under 400 pages, you can
 omit both cover texts.
 
-   *Note GNU Sample Texts: (texinfo)GNU Sample Texts, for a full
-example in a Texinfo manual, and see
+   *Note GNU Sample Texts: (texinfo)GNU Sample Texts, for a full example
+in a Texinfo manual, and see
 `http://www.gnu.org/licenses/fdl-howto.html' for more advice about how
 to use the GNU FDL.
 
    If the manual is over 400 pages, or if the FSF thinks it might be a
-good choice for publishing on paper, then please include the GNU GPL,
-as in the notice above.  Please also include our standard invariant
-section which explains the importance of free documentation.  Write to
+good choice for publishing on paper, then please include the GNU GPL, as
+in the notice above.  Please also include our standard invariant section
+which explains the importance of free documentation.  Write to
 <address@hidden> to get a copy of this section.
 
    When you distribute several manuals together in one software package,
-their on-line forms can share a single copy of the GFDL (see
-section 6).  However, the printed (`.dvi', `.pdf', ...) forms should
-each contain a copy of the GFDL, unless they are set up to be printed
-and published only together.  Therefore, it is usually simplest to
-include the GFDL in each manual.
+their on-line forms can share a single copy of the GFDL (see section 6).
+However, the printed (`.dvi', `.pdf', ...) forms should each contain a
+copy of the GFDL, unless they are set up to be printed and published
+only together.  Therefore, it is usually simplest to include the GFDL in
+each manual.
 
 6.6.5 License Notices for Other Files
 -------------------------------------
@@ -799,22 +790,22 @@
 
    If your package distributes Autoconf macros that are intended to be
 used (hence distributed) by third-party packages under possibly
-incompatible licenses, you may also use the above all-permissive
-license for these macros.
+incompatible licenses, you may also use the above all-permissive license
+for these macros.
 
 6.7 External Libraries
 ======================
 
 When maintaining an FSF-copyrighted GNU package, you may occasionally
-want to use a general-purpose free software module which offers a
-useful functionality, as a "library" facility (though the module is not
-always packaged technically as a library).
+want to use a general-purpose free software module which offers a useful
+functionality, as a "library" facility (though the module is not always
+packaged technically as a library).
 
    In a case like this, it would be unreasonable to ask the author of
 that module to assign the copyright to the FSF.  After all, person did
-not write it specifically as a contribution to your package, so it
-would be impertinent to ask per, out of the blue, "Please give the FSF
-your copyright."
+not write it specifically as a contribution to your package, so it would
+be impertinent to ask per, out of the blue, "Please give the FSF your
+copyright."
 
    So the thing to do in this case is to make your program use the
 module, but not consider it a part of your program.  There are two
@@ -826,9 +817,8 @@
 
   2. Include the module in your package, putting the source in a
      separate subdirectory whose `README' file says, "This is not part
-     of the GNU FOO program, but is used with GNU FOO."  Then set up
-     your makefiles to build this module and link it into the
-     executable.
+     of the GNU FOO program, but is used with GNU FOO." Then set up your
+     makefiles to build this module and link it into the executable.
 
      For this method, it is not necessary to treat the module as a
      library and make a `.a' file from it.  You can link with the `.o'
@@ -845,8 +835,8 @@
 *********************
 
 Don't feel obligated to include every change that someone asks you to
-include.  You must judge which changes are improvements--partly based
-on what you think the users will like, and partly based on your own
+include.  You must judge which changes are improvements--partly based on
+what you think the users will like, and partly based on your own
 judgment of what is better.  If you think a change is not good, you
 should reject it.
 
@@ -863,9 +853,9 @@
 for you to install and maintain.
 
    The only reason to do these cleanups yourself is if (1) it is easy,
-less work than telling the author what to clean up, or (2) the change
-is an important one, important enough to be worth the work of cleaning
-it up.
+less work than telling the author what to clean up, or (2) the change is
+an important one, important enough to be worth the work of cleaning it
+up.
 
    The GNU Coding Standards are a good thing to send people when you ask
 them to clean up changes (*note Contents: (standards)Top.).  The Emacs
@@ -897,28 +887,28 @@
 Even if you did have access to all the platforms, it would be
 inefficient for you to test the program on each platform yourself.
 Instead, you should test the program on a few platforms, including GNU
-or GNU/Linux, and let the users test it on the other platforms.  You
-can do this through a pretest phase before the real release; when there
-is no reason to expect problems, in a package that is mostly portable,
-you can just make a release and let the users tell you if anything
+or GNU/Linux, and let the users test it on the other platforms.  You can
+do this through a pretest phase before the real release; when there is
+no reason to expect problems, in a package that is mostly portable, you
+can just make a release and let the users tell you if anything
 unportable was introduced.
 
    It is important to test the program personally on GNU or GNU/Linux,
 because these are the most important platforms for a GNU package.  If
-you don't have access to one of these platforms, as a GNU maintainer
-you can get access to the general GNU login machine; see
+you don't have access to one of these platforms, as a GNU maintainer you
+can get access to the general GNU login machine; see
 `http://www.gnu.org/software/README.accounts.html'.
 
    Supporting other platforms is optional--we do it when that seems like
 a good idea, but we don't consider it obligatory.  If the users don't
-take care of a certain platform, you may have to desupport it unless
-and until users come forward to help.  Conversely, if a user offers
-changes to support an additional platform, you will probably want to
-install them, but you don't have to.  If you feel the changes are
-complex and ugly, if you think that they will increase the burden of
-future maintenance, you can and should reject them.  This includes both
-free or mainly-free platforms such as OpenBSD, FreeBSD, and NetBSD, and
-non-free platforms such as Windows.
+take care of a certain platform, you may have to desupport it unless and
+until users come forward to help.  Conversely, if a user offers changes
+to support an additional platform, you will probably want to install
+them, but you don't have to.  If you feel the changes are complex and
+ugly, if you think that they will increase the burden of future
+maintenance, you can and should reject them.  This includes both free or
+mainly-free platforms such as OpenBSD, FreeBSD, and NetBSD, and non-free
+platforms such as Windows.
 
 9 Dealing With Mail
 *******************
@@ -939,8 +929,8 @@
 bug-reporting list in a prominent place, and ask users to help us by
 reporting bugs there.
 
-   We also have a catch-all list, <address@hidden>, which is
-used for all GNU programs that don't have their own specific lists.  But
+   We also have a catch-all list, <address@hidden>, which is used
+for all GNU programs that don't have their own specific lists.  But
 nowadays we want to give each program its own bug-reporting list and
 move away from using <bug-gnu-utils>.
 
@@ -958,15 +948,15 @@
 
 Using the web interface on `savannah.gnu.org' is by far the easiest way
 to create normal mailing lists, managed through Mailman on the GNU mail
-server.  Once you register your package on Savannah, you can create
-(and remove) lists yourself through the `Mailing Lists' menu, without
-needing to wait for intervention by anyone else.  Furthermore, lists
-created through Savannah will have a reasonable default configuration
-for antispam purposes (see below).
+server.  Once you register your package on Savannah, you can create (and
+remove) lists yourself through the `Mailing Lists' menu, without needing
+to wait for intervention by anyone else.  Furthermore, lists created
+through Savannah will have a reasonable default configuration for
+antispam purposes (see below).
 
    To create and maintain simple aliases and unmanaged lists, you can
-edit `/com/mailer/aliases' on the main GNU server.  If you don't have
-an account there, please read
+edit `/com/mailer/aliases' on the main GNU server.  If you don't have an
+account there, please read
 `http://www.gnu.org/software/README.accounts.html' (*note Getting a GNU
 Account::).
 
@@ -1033,10 +1023,10 @@
 *************************
 
 It is very important to keep backup files of all source files of GNU.
-You can do this using a source control system (such as Bazaar, RCS,
-CVS, Git, Subversion, ...) if you like.  An easy way to use many such
-systems is via the Version Control library in Emacs (*note Introduction
-to Version Control: (emacs)Introduction to VC.).
+You can do this using a source control system (such as Bazaar, RCS, CVS,
+Git, Subversion, ...) if you like.  An easy way to use many such systems
+is via the Version Control library in Emacs (*note Introduction to
+Version Control: (emacs)Introduction to VC.).
 
    The history of previous revisions and log entries is very important
 for future maintainers of the package, so even if you do not make it
@@ -1045,9 +1035,9 @@
 some day.
 
    The GNU Project provides a server that GNU packages can use for
-source control and other package needs: `savannah.gnu.org'.  Savannah
-is managed by <address@hidden>.  For more details on using
-and contributing to Savannah, see `http://savannah.gnu.org/maintenance'.
+source control and other package needs: `savannah.gnu.org'.  Savannah is
+managed by <address@hidden>.  For more details on using and
+contributing to Savannah, see `http://savannah.gnu.org/maintenance'.
 
    It's not an absolute requirement, but all GNU maintainers are
 strongly encouraged to take advantage of Savannah, as sharing such a
@@ -1060,8 +1050,8 @@
    If you do use Savannah, please subscribe to the
 <address@hidden> mailing list
 (`http://lists.gnu.org/mailman/listinfo/savannah-announce').  This is a
-very low-volume list to keep Savannah users informed of system
-upgrades, problems, and the like.
+very low-volume list to keep Savannah users informed of system upgrades,
+problems, and the like.
 
 11 Distributions
 ****************
@@ -1074,9 +1064,9 @@
 
 The tar file for version M.N of program `foo' should be named
 `foo-M.N.tar'.  It should unpack into a subdirectory named `foo-M.N'.
-Tar files should not unpack into files in the current directory,
-because this is inconvenient if the user happens to unpack into a
-directory with other files in it.
+Tar files should not unpack into files in the current directory, because
+this is inconvenient if the user happens to unpack into a directory with
+other files in it.
 
    Here is how the `Makefile' for Bison creates the tar file.  This
 method is good for other programs.
@@ -1148,8 +1138,8 @@
 
 GNU packages are distributed through the directory `/gnu' on
 `ftp.gnu.org', via both HTTP and FTP.  Each package should have a
-subdirectory named after the package, and all the distribution files
-for the package should go in that subdirectory.
+subdirectory named after the package, and all the distribution files for
+the package should go in that subdirectory.
 
    *Note Automated FTP Uploads::, for procedural details of putting new
 versions on `ftp.gnu.org'.
@@ -1178,12 +1168,12 @@
 to do a pretest first, call it 4.5.90.  If you need a second pretest,
 call it 4.5.91, and so on.  If you are really unlucky and ten pretests
 are not enough, after 4.5.99 you could advance to 4.5.990 and so on.
-(You could also use 4.5.100, but 990 has the advantage of sorting in
-the right order.)
+(You could also use 4.5.100, but 990 has the advantage of sorting in the
+right order.)
 
    The other method is to attach a date to the release number that is
-coming.  For a pretest for version 4.6, made on Dec 10, 2002, this
-would be 4.6.20021210.  A second pretest made the same day could be
+coming.  For a pretest for version 4.6, made on Dec 10, 2002, this would
+be 4.6.20021210.  A second pretest made the same day could be
 4.6.20021210.1.
 
    For development snapshots that are not formal pretests, using just
@@ -1192,17 +1182,17 @@
    One thing that you should never do is to release a pretest with the
 same version number as the planned real release.  Many people will look
 only at the version number (in the tar file name, in the directory name
-that it unpacks into, or wherever they can find it) to determine
-whether a tar file is the latest version.  People might look at the
-test release in this way and mistake it for the real release.
-Therefore, always change the number when you release changed code.
+that it unpacks into, or wherever they can find it) to determine whether
+a tar file is the latest version.  People might look at the test release
+in this way and mistake it for the real release.  Therefore, always
+change the number when you release changed code.
 
 11.5 Automated FTP Uploads
 ==========================
 
-In order to upload new releases to `ftp.gnu.org' or `alpha.gnu.org',
-you first need to register the necessary information.  Then, you can
-perform uploads yourself, with no intervention needed by the system
+In order to upload new releases to `ftp.gnu.org' or `alpha.gnu.org', you
+first need to register the necessary information.  Then, you can perform
+uploads yourself, with no intervention needed by the system
 administrators.
 
    The general idea is that releases should be crytographically signed
@@ -1214,15 +1204,15 @@
 Here is how to register your information so you can perform uploads for
 your GNU package:
 
-  1. Create an account for yourself at `http://savannah.gnu.org', if
-     you don't already have one.  By the way, this is also needed to
+  1. Create an account for yourself at `http://savannah.gnu.org', if you
+     don't already have one.  By the way, this is also needed to
      maintain the web pages at `http://www.gnu.org' for your project
      (*note Web Pages::).
 
-  2. In the `My Account Conf' page on `savannah', upload the GPG key
-     you will use to sign your packages.  If you haven't created one
-     before, you can do so with the command `gpg --gen-key' (you can
-     accept all the default answers to its questions).
+  2. In the `My Account Conf' page on `savannah', upload the GPG key you
+     will use to sign your packages.  If you haven't created one before,
+     you can do so with the command `gpg --gen-key' (you can accept all
+     the default answers to its questions).
 
      Optional but recommended: Send your key to a GPG public key server:
      `gpg --keyserver keys.gnupg.net --send-keys KEYID', where KEYID is
@@ -1231,8 +1221,8 @@
      `http://www.gnu.org/software/gpg'.
 
   3. Compose a message with the following items in some MSGFILE.  Then
-     GPG-sign it by running `gpg --clearsign MSGFILE', and finally
-     email the resulting `MSGFILE.asc'), to <address@hidden>.
+     GPG-sign it by running `gpg --clearsign MSGFILE', and finally email
+     the resulting `MSGFILE.asc'), to <address@hidden>.
 
        1. Name of package(s) that you are the maintainer for, your
           preferred email address, and your Savannah username.
@@ -1242,12 +1232,12 @@
           this.)
 
        3. A list of names and preferred email addresses of other
-          individuals you authorize to make releases for which
-          packages, if any (in the case that you don't make all
-          releases yourself).
+          individuals you authorize to make releases for which packages,
+          if any (in the case that you don't make all releases
+          yourself).
 
-       4. ASCII armored copies of GPG keys for any individuals listed
-          in (3).
+       4. ASCII armored copies of GPG keys for any individuals listed in
+          (3).
 
    The administrators will acknowledge your message when they have added
 the proper GPG keys as authorized to upload files for the corresponding
@@ -1311,8 +1301,8 @@
 `http://savannah.gnu.org/projects/gnulib'.  `gnupload' can also remove
 uploaded files.  Run `gnupload --help' for a description and examples.
 
-   `gnupload' uses the `ncftpput' program to do the actual transfers;
-if you don't happen to have the `ncftp' package installed, the
+   `gnupload' uses the `ncftpput' program to do the actual transfers; if
+you don't happen to have the `ncftp' package installed, the
 `ncftpput-ftp' script in the `build-aux/' directory of `gnulib' serves
 as a replacement which uses plain command line `ftp'.
 
@@ -1362,19 +1352,19 @@
 
 When uploaded by itself, the directive file must contain one or more of
 the directives `symlink', `rmsymlink' or `archive', in addition to the
-obligatory `directory' and `version' directives.  A `filename'
-directive is not allowed, and a `comment' directive remains optional.
+obligatory `directory' and `version' directives.  A `filename' directive
+is not allowed, and a `comment' directive remains optional.
 
    If you use more than one directive, the directives are executed in
 the sequence they are specified in.  If a directive results in an error,
 further execution of the upload is aborted.
 
    Removing a symbolic link (with `rmsymlink') which does not exist
-results in an error.  However, attempting to create a symbolic link
-that already exists (with `symlink') is not an error.  In this case
-`symlink' behaves like the command `ln -s -f': any existing symlink is
-removed before creating the link.  (But an existing regular file or
-directory is not removed.)
+results in an error.  However, attempting to create a symbolic link that
+already exists (with `symlink') is not an error.  In this case `symlink'
+behaves like the command `ln -s -f': any existing symlink is removed
+before creating the link.  (But an existing regular file or directory is
+not removed.)
 
    Here are a few examples.  The first removes a symlink:
 
@@ -1419,9 +1409,9 @@
 ---------------------------------------
 
 "As of June 2006, the upload script is running in compatibility mode,
-allowing uploads with either version 1.1 or version 1.0 of the
-directive file syntax.  Support for v1.0 uploads will be phased out by
-the end of 2006, so please upgrade to v1.1."
+allowing uploads with either version 1.1 or version 1.0 of the directive
+file syntax.  Support for v1.0 uploads will be phased out by the end of
+2006, so please upgrade to v1.1."
 
    The directive file should contain one line, excluding the clearsigned
 data GPG that inserts, which specifies the final destination directory
@@ -1461,10 +1451,10 @@
 other locations; see information on the GNU Planet web page.
 
    You can maintain your own mailing list (typically
-<address@hidden>) for announcements as well if you like.  For
-your own list, of course you decide as you see fit what events are
-worth announcing.  (*Note Mail::, for setting this up, and more
-suggestions on handling mail for your package.)
+<address@hidden>) for announcements as well if you like.  For your
+own list, of course you decide as you see fit what events are worth
+announcing.  (*Note Mail::, for setting this up, and more suggestions on
+handling mail for your package.)
 
    When writing an announcement, please include the following:
 
@@ -1517,8 +1507,8 @@
 
    If you don't want to use that method, please talk with
 <address@hidden> about other possible methods.  For instance, you
-can mail them pages to install, if necessary.  But that is more work
-for them, so please use Savannah if you can.
+can mail them pages to install, if necessary.  But that is more work for
+them, so please use Savannah if you can.
 
    If you use Savannah, you can use a special file named `.symlinks' in
 order to create symbolic links, which are not supported in CVS.  For
@@ -1529,17 +1519,16 @@
 ==========================
 
 If you use a site other than `www.gnu.org', please make sure that the
-site runs on free software alone.  (It is ok if the site uses
-unreleased custom software, since that is free in a trivial sense:
-there's only one user and it has the four freedoms.)  If the web site
-for a GNU package runs on non-free software, the public will see this,
-and it will have the effect of granting legitimacy to the non-free
-program.
+site runs on free software alone.  (It is ok if the site uses unreleased
+custom software, since that is free in a trivial sense: there's only one
+user and it has the four freedoms.)  If the web site for a GNU package
+runs on non-free software, the public will see this, and it will have
+the effect of granting legitimacy to the non-free program.
 
    If you use multiple sites, they should all follow that criterion.
-Please don't link to a site that is about your package, which the
-public might perceive as connected with it and reflecting the position
-of its developers, unless it follows that criterion.
+Please don't link to a site that is about your package, which the public
+might perceive as connected with it and reflecting the position of its
+developers, unless it follows that criterion.
 
    Historically, web pages for GNU packages did not include GIF images,
 because of patent problems (*note Ethical and Philosophical
@@ -1551,8 +1540,8 @@
 =========================
 
 The web pages for the package should include its manuals, in HTML, DVI,
-Info, PostScript, PDF, plain ASCII, and Texinfo format (source).  All
-of these can be generated automatically from the Texinfo source using
+Info, PostScript, PDF, plain ASCII, and Texinfo format (source).  All of
+these can be generated automatically from the Texinfo source using
 Makeinfo and other programs.
 
    When there is only one manual, put it in a subdirectory called
@@ -1607,8 +1596,8 @@
 files, retaining the subdirectories, into the web pages for your
 package.
 
-   You can specify the option `-o OUTDIR' to override the name
-`manual'.  Any previous contents of OUTDIR will be deleted.
+   You can specify the option `-o OUTDIR' to override the name `manual'.
+Any previous contents of OUTDIR will be deleted.
 
    The second argument, with the description, is included as part of the
 HTML `<title>' of the overall `manual/index.html' file.  It should
@@ -1652,12 +1641,12 @@
 12.4 CVS Keywords in Web Pages
 ==============================
 
-Since `www.gnu.org' works through CVS, CVS keywords in your manual,
-such as `$Log: maintain.txt,v $
-such as `Revision 1.71  2011/09/07 01:31:10  karl
-such as `non-FTP distribution wording from rms
-such as `', need special treatment (even if you don't happen to
-maintain your manual in CVS).
+Since `www.gnu.org' works through CVS, CVS keywords in your manual, such
+as `$Log: maintain.txt,v $
+as `Revision 1.72  2011/09/07 14:59:09  karl
+as `regenerate with new makeinfo
+as `', need special treatment (even if you don't happen to maintain
+your manual in CVS).
 
    If these keywords end up in the generated output as literal strings,
 they will be expanded.  The most robust way to handle this is to turn
@@ -1695,10 +1684,10 @@
 unknown to the program's developers.  It would be futile and
 self-defeating to try to find and avoid all these patents.  But there
 are some patents which we know are likely to be used to threaten free
-software, so we make an effort to avoid the patented techniques.  If
-you are concerned about the danger of a patent and would like advice,
-write to <address@hidden>, and we will try to help you get advice
-from a lawyer.
+software, so we make an effort to avoid the patented techniques.  If you
+are concerned about the danger of a patent and would like advice, write
+to <address@hidden>, and we will try to help you get advice from a
+lawyer.
 
    Sometimes the GNU project takes a strong stand against a particular
 patented technology in order to encourage society to reject it.
@@ -1740,13 +1729,12 @@
 14.1 Free Software and Open Source
 ==================================
 
-The terms "free software" and "open source", while describing almost
-the same category of software, stand for views based on fundamentally
+The terms "free software" and "open source", while describing almost the
+same category of software, stand for views based on fundamentally
 different values.  The free software movement is idealistic, and raises
 issues of freedom, ethics, principle and what makes for a good society.
-The term open source, initiated in 1998, is associated with a
-philosophy which studiously avoids such questions.  For a detailed
-explanation, see
+The term open source, initiated in 1998, is associated with a philosophy
+which studiously avoids such questions.  For a detailed explanation, see
 `http://www.gnu.org/philosophy/open-source-misses-the-point.html'.
 
    The GNU Project is aligned with the free software movement.  This
@@ -1767,11 +1755,11 @@
 ==================
 
 The GNU Project was formed to develop a free Unix-like operating system,
-GNU.  The existence of this system is our major accomplishment.
-However, the widely used version of the GNU system, in which Linux is
-used as the kernel, is often called simply "Linux".  As a result, most
-users don't know about the GNU Project's major accomplishment--or more
-precisely, they know about it, but don't realize it is the GNU Project's
+GNU. The existence of this system is our major accomplishment.  However,
+the widely used version of the GNU system, in which Linux is used as the
+kernel, is often called simply "Linux".  As a result, most users don't
+know about the GNU Project's major accomplishment--or more precisely,
+they know about it, but don't realize it is the GNU Project's
 accomplishment and reason for existence.  Even people who believe they
 know the real history often believe that the goal of GNU was to develop
 "tools" or "utilities."
@@ -1801,16 +1789,15 @@
 15 Hosting
 **********
 
-We recommend using `savannah.gnu.org' for the source code repository
-for your package, but that's not required.  *Note Old Versions::, for
-more information about Savannah.
+We recommend using `savannah.gnu.org' for the source code repository for
+your package, but that's not required.  *Note Old Versions::, for more
+information about Savannah.
 
    We strongly urge you to use `ftp.gnu.org' as the standard
-distribution site for releases.  Doing so makes it easier for
-developers and users to find the latest GNU releases.  However, it is
-ok to use another server if you wish, provided it allows access from
-the general public without limitation (for instance, without excluding
-any country).
+distribution site for releases.  Doing so makes it easier for developers
+and users to find the latest GNU releases.  However, it is ok to use
+another server if you wish, provided it allows access from the general
+public without limitation (for instance, without excluding any country).
 
    If you use a company's machine to hold the repository for your
 program, or as its release distribution site, please put this statement
@@ -1897,8 +1884,8 @@
 times.  This must be avoided.
 
    Also, the people on the list do not want to get a large amount of
-mail from it.  So do not ever ask people on the list to send mail to
-the list!
+mail from it.  So do not ever ask people on the list to send mail to the
+list!
 
    Here are a few methods that seem reasonable to use:
 
@@ -1917,11 +1904,10 @@
      coverage.
 
      You can either divide up the work physically, into 20 separate
-     files, or describe a virtual division, such as by sections (if
-     your work has approximately 20 sections).  If you do the latter,
-     be sure to be precise about it--for example, do you want the
-     material before the first section heading to count as a section,
-     or not?
+     files, or describe a virtual division, such as by sections (if your
+     work has approximately 20 sections).  If you do the latter, be sure
+     to be precise about it--for example, do you want the material
+     before the first section heading to count as a section, or not?
 
    * For a job needing special skills, send an explanation of it, and
      ask people to send you mail if they volunteer for the job.  When
@@ -1959,21 +1945,21 @@
      free program should come with manuals providing the same freedoms
      that the software does.  But this License is not limited to
      software manuals; it can be used for any textual work, regardless
-     of subject matter or whether it is published as a printed book.
-     We recommend this License principally for works whose purpose is
+     of subject matter or whether it is published as a printed book.  We
+     recommend this License principally for works whose purpose is
      instruction or reference.
 
   1. APPLICABILITY AND DEFINITIONS
 
      This License applies to any manual or other work, in any medium,
-     that contains a notice placed by the copyright holder saying it
-     can be distributed under the terms of this License.  Such a notice
+     that contains a notice placed by the copyright holder saying it can
+     be distributed under the terms of this License.  Such a notice
      grants a world-wide, royalty-free license, unlimited in duration,
      to use that work under the conditions stated herein.  The
      "Document", below, refers to any such manual or work.  Any member
-     of the public is a licensee, and is addressed as "you".  You
-     accept the license if you copy, modify or distribute the work in a
-     way requiring permission under copyright law.
+     of the public is a licensee, and is addressed as "you".  You accept
+     the license if you copy, modify or distribute the work in a way
+     requiring permission under copyright law.
 
      A "Modified Version" of the Document means any work containing the
      Document or a portion of it, either copied verbatim, or with
@@ -1991,12 +1977,12 @@
      regarding them.
 
      The "Invariant Sections" are certain Secondary Sections whose
-     titles are designated, as being those of Invariant Sections, in
-     the notice that says that the Document is released under this
-     License.  If a section does not fit the above definition of
-     Secondary then it is not allowed to be designated as Invariant.
-     The Document may contain zero Invariant Sections.  If the Document
-     does not identify any Invariant Sections then there are none.
+     titles are designated, as being those of Invariant Sections, in the
+     notice that says that the Document is released under this License.
+     If a section does not fit the above definition of Secondary then it
+     is not allowed to be designated as Invariant.  The Document may
+     contain zero Invariant Sections.  If the Document does not identify
+     any Invariant Sections then there are none.
 
      The "Cover Texts" are certain short passages of text that are
      listed, as Front-Cover Texts or Back-Cover Texts, in the notice
@@ -2007,27 +1993,27 @@
      A "Transparent" copy of the Document means a machine-readable copy,
      represented in a format whose specification is available to the
      general public, that is suitable for revising the document
-     straightforwardly with generic text editors or (for images
-     composed of pixels) generic paint programs or (for drawings) some
-     widely available drawing editor, and that is suitable for input to
-     text formatters or for automatic translation to a variety of
-     formats suitable for input to text formatters.  A copy made in an
-     otherwise Transparent file format whose markup, or absence of
-     markup, has been arranged to thwart or discourage subsequent
-     modification by readers is not Transparent.  An image format is
-     not Transparent if used for any substantial amount of text.  A
-     copy that is not "Transparent" is called "Opaque".
+     straightforwardly with generic text editors or (for images composed
+     of pixels) generic paint programs or (for drawings) some widely
+     available drawing editor, and that is suitable for input to text
+     formatters or for automatic translation to a variety of formats
+     suitable for input to text formatters.  A copy made in an otherwise
+     Transparent file format whose markup, or absence of markup, has
+     been arranged to thwart or discourage subsequent modification by
+     readers is not Transparent.  An image format is not Transparent if
+     used for any substantial amount of text.  A copy that is not
+     "Transparent" is called "Opaque".
 
      Examples of suitable formats for Transparent copies include plain
      ASCII without markup, Texinfo input format, LaTeX input format,
-     SGML or XML using a publicly available DTD, and
-     standard-conforming simple HTML, PostScript or PDF designed for
-     human modification.  Examples of transparent image formats include
-     PNG, XCF and JPG.  Opaque formats include proprietary formats that
-     can be read and edited only by proprietary word processors, SGML or
-     XML for which the DTD and/or processing tools are not generally
-     available, and the machine-generated HTML, PostScript or PDF
-     produced by some word processors for output purposes only.
+     SGML or XML using a publicly available DTD, and standard-conforming
+     simple HTML, PostScript or PDF designed for human modification.
+     Examples of transparent image formats include PNG, XCF and JPG.
+     Opaque formats include proprietary formats that can be read and
+     edited only by proprietary word processors, SGML or XML for which
+     the DTD and/or processing tools are not generally available, and
+     the machine-generated HTML, PostScript or PDF produced by some word
+     processors for output purposes only.
 
      The "Title Page" means, for a printed book, the title page itself,
      plus such following pages as are needed to hold, legibly, the
@@ -2065,8 +2051,8 @@
      may not use technical measures to obstruct or control the reading
      or further copying of the copies you make or distribute.  However,
      you may accept compensation in exchange for copies.  If you
-     distribute a large enough number of copies you must also follow
-     the conditions in section 3.
+     distribute a large enough number of copies you must also follow the
+     conditions in section 3.
 
      You may also lend copies, under the same conditions stated above,
      and you may publicly display copies.
@@ -2080,12 +2066,11 @@
      these Cover Texts: Front-Cover Texts on the front cover, and
      Back-Cover Texts on the back cover.  Both covers must also clearly
      and legibly identify you as the publisher of these copies.  The
-     front cover must present the full title with all words of the
-     title equally prominent and visible.  You may add other material
-     on the covers in addition.  Copying with changes limited to the
-     covers, as long as they preserve the title of the Document and
-     satisfy these conditions, can be treated as verbatim copying in
-     other respects.
+     front cover must present the full title with all words of the title
+     equally prominent and visible.  You may add other material on the
+     covers in addition.  Copying with changes limited to the covers, as
+     long as they preserve the title of the Document and satisfy these
+     conditions, can be treated as verbatim copying in other respects.
 
      If the required texts for either cover are too voluminous to fit
      legibly, you should put the first ones listed (as many as fit
@@ -2093,40 +2078,39 @@
      adjacent pages.
 
      If you publish or distribute Opaque copies of the Document
-     numbering more than 100, you must either include a
-     machine-readable Transparent copy along with each Opaque copy, or
-     state in or with each Opaque copy a computer-network location from
-     which the general network-using public has access to download
-     using public-standard network protocols a complete Transparent
-     copy of the Document, free of added material.  If you use the
-     latter option, you must take reasonably prudent steps, when you
-     begin distribution of Opaque copies in quantity, to ensure that
-     this Transparent copy will remain thus accessible at the stated
-     location until at least one year after the last time you
-     distribute an Opaque copy (directly or through your agents or
-     retailers) of that edition to the public.
+     numbering more than 100, you must either include a machine-readable
+     Transparent copy along with each Opaque copy, or state in or with
+     each Opaque copy a computer-network location from which the general
+     network-using public has access to download using public-standard
+     network protocols a complete Transparent copy of the Document, free
+     of added material.  If you use the latter option, you must take
+     reasonably prudent steps, when you begin distribution of Opaque
+     copies in quantity, to ensure that this Transparent copy will
+     remain thus accessible at the stated location until at least one
+     year after the last time you distribute an Opaque copy (directly or
+     through your agents or retailers) of that edition to the public.
 
      It is requested, but not required, that you contact the authors of
-     the Document well before redistributing any large number of
-     copies, to give them a chance to provide you with an updated
-     version of the Document.
+     the Document well before redistributing any large number of copies,
+     to give them a chance to provide you with an updated version of the
+     Document.
 
   4. MODIFICATIONS
 
      You may copy and distribute a Modified Version of the Document
      under the conditions of sections 2 and 3 above, provided that you
-     release the Modified Version under precisely this License, with
-     the Modified Version filling the role of the Document, thus
-     licensing distribution and modification of the Modified Version to
-     whoever possesses a copy of it.  In addition, you must do these
-     things in the Modified Version:
+     release the Modified Version under precisely this License, with the
+     Modified Version filling the role of the Document, thus licensing
+     distribution and modification of the Modified Version to whoever
+     possesses a copy of it.  In addition, you must do these things in
+     the Modified Version:
 
        A. Use in the Title Page (and on the covers, if any) a title
-          distinct from that of the Document, and from those of
-          previous versions (which should, if there were any, be listed
-          in the History section of the Document).  You may use the
-          same title as a previous version if the original publisher of
-          that version gives permission.
+          distinct from that of the Document, and from those of previous
+          versions (which should, if there were any, be listed in the
+          History section of the Document).  You may use the same title
+          as a previous version if the original publisher of that
+          version gives permission.
 
        B. List on the Title Page, as authors, one or more persons or
           entities responsible for authorship of the modifications in
@@ -2156,31 +2140,30 @@
 
        I. Preserve the section Entitled "History", Preserve its Title,
           and add to it an item stating at least the title, year, new
-          authors, and publisher of the Modified Version as given on
-          the Title Page.  If there is no section Entitled "History" in
-          the Document, create one stating the title, year, authors,
-          and publisher of the Document as given on its Title Page,
-          then add an item describing the Modified Version as stated in
-          the previous sentence.
+          authors, and publisher of the Modified Version as given on the
+          Title Page.  If there is no section Entitled "History" in the
+          Document, create one stating the title, year, authors, and
+          publisher of the Document as given on its Title Page, then add
+          an item describing the Modified Version as stated in the
+          previous sentence.
 
        J. Preserve the network location, if any, given in the Document
           for public access to a Transparent copy of the Document, and
           likewise the network locations given in the Document for
-          previous versions it was based on.  These may be placed in
-          the "History" section.  You may omit a network location for a
-          work that was published at least four years before the
-          Document itself, or if the original publisher of the version
-          it refers to gives permission.
+          previous versions it was based on.  These may be placed in the
+          "History" section.  You may omit a network location for a work
+          that was published at least four years before the Document
+          itself, or if the original publisher of the version it refers
+          to gives permission.
 
        K. For any section Entitled "Acknowledgements" or "Dedications",
-          Preserve the Title of the section, and preserve in the
-          section all the substance and tone of each of the contributor
+          Preserve the Title of the section, and preserve in the section
+          all the substance and tone of each of the contributor
           acknowledgements and/or dedications given therein.
 
-       L. Preserve all the Invariant Sections of the Document,
-          unaltered in their text and in their titles.  Section numbers
-          or the equivalent are not considered part of the section
-          titles.
+       L. Preserve all the Invariant Sections of the Document, unaltered
+          in their text and in their titles.  Section numbers or the
+          equivalent are not considered part of the section titles.
 
        M. Delete any section Entitled "Endorsements".  Such a section
           may not be included in the Modified Version.
@@ -2193,11 +2176,11 @@
 
      If the Modified Version includes new front-matter sections or
      appendices that qualify as Secondary Sections and contain no
-     material copied from the Document, you may at your option
-     designate some or all of these sections as invariant.  To do this,
-     add their titles to the list of Invariant Sections in the Modified
-     Version's license notice.  These titles must be distinct from any
-     other section titles.
+     material copied from the Document, you may at your option designate
+     some or all of these sections as invariant.  To do this, add their
+     titles to the list of Invariant Sections in the Modified Version's
+     license notice.  These titles must be distinct from any other
+     section titles.
 
      You may add a section Entitled "Endorsements", provided it contains
      nothing but endorsements of your Modified Version by various
@@ -2206,15 +2189,15 @@
      definition of a standard.
 
      You may add a passage of up to five words as a Front-Cover Text,
-     and a passage of up to 25 words as a Back-Cover Text, to the end
-     of the list of Cover Texts in the Modified Version.  Only one
-     passage of Front-Cover Text and one of Back-Cover Text may be
-     added by (or through arrangements made by) any one entity.  If the
-     Document already includes a cover text for the same cover,
-     previously added by you or by arrangement made by the same entity
-     you are acting on behalf of, you may not add another; but you may
-     replace the old one, on explicit permission from the previous
-     publisher that added the old one.
+     and a passage of up to 25 words as a Back-Cover Text, to the end of
+     the list of Cover Texts in the Modified Version.  Only one passage
+     of Front-Cover Text and one of Back-Cover Text may be added by (or
+     through arrangements made by) any one entity.  If the Document
+     already includes a cover text for the same cover, previously added
+     by you or by arrangement made by the same entity you are acting on
+     behalf of, you may not add another; but you may replace the old
+     one, on explicit permission from the previous publisher that added
+     the old one.
 
      The author(s) and publisher(s) of the Document do not by this
      License give permission to use their names for publicity for or to
@@ -2224,8 +2207,8 @@
 
      You may combine the Document with other documents released under
      this License, under the terms defined in section 4 above for
-     modified versions, provided that you include in the combination
-     all of the Invariant Sections of all of the original documents,
+     modified versions, provided that you include in the combination all
+     of the Invariant Sections of all of the original documents,
      unmodified, and list them all as Invariant Sections of your
      combined work in its license notice, and that you preserve all
      their Warranty Disclaimers.
@@ -2252,20 +2235,20 @@
      documents released under this License, and replace the individual
      copies of this License in the various documents with a single copy
      that is included in the collection, provided that you follow the
-     rules of this License for verbatim copying of each of the
-     documents in all other respects.
+     rules of this License for verbatim copying of each of the documents
+     in all other respects.
 
      You may extract a single document from such a collection, and
      distribute it individually under this License, provided you insert
-     a copy of this License into the extracted document, and follow
-     this License in all other respects regarding verbatim copying of
-     that document.
+     a copy of this License into the extracted document, and follow this
+     License in all other respects regarding verbatim copying of that
+     document.
 
   7. AGGREGATION WITH INDEPENDENT WORKS
 
      A compilation of the Document or its derivatives with other
-     separate and independent documents or works, in or on a volume of
-     a storage or distribution medium, is called an "aggregate" if the
+     separate and independent documents or works, in or on a volume of a
+     storage or distribution medium, is called an "aggregate" if the
      copyright resulting from the compilation is not used to limit the
      legal rights of the compilation's users beyond what the individual
      works permit.  When the Document is included in an aggregate, this
@@ -2310,8 +2293,8 @@
 
      However, if you cease all violation of this License, then your
      license from a particular copyright holder is reinstated (a)
-     provisionally, unless and until the copyright holder explicitly
-     and finally terminates your license, and (b) permanently, if the
+     provisionally, unless and until the copyright holder explicitly and
+     finally terminates your license, and (b) permanently, if the
      copyright holder fails to notify you of the violation by some
      reasonable means prior to 60 days after the cessation.
 
@@ -2323,10 +2306,10 @@
      after your receipt of the notice.
 
      Termination of your rights under this section does not terminate
-     the licenses of parties who have received copies or rights from
-     you under this License.  If your rights have been terminated and
-     not permanently reinstated, receipt of a copy of some or all of
-     the same material does not give you any rights to use it.
+     the licenses of parties who have received copies or rights from you
+     under this License.  If your rights have been terminated and not
+     permanently reinstated, receipt of a copy of some or all of the
+     same material does not give you any rights to use it.
 
  10. FUTURE REVISIONS OF THIS LICENSE
 
@@ -2341,11 +2324,11 @@
      version of this License "or any later version" applies to it, you
      have the option of following the terms and conditions either of
      that specified version or of any later version that has been
-     published (not as a draft) by the Free Software Foundation.  If
-     the Document does not specify a version number of this License,
-     you may choose any version ever published (not as a draft) by the
-     Free Software Foundation.  If the Document specifies that a proxy
-     can decide which future versions of this License can be used, that
+     published (not as a draft) by the Free Software Foundation.  If the
+     Document does not specify a version number of this License, you may
+     choose any version ever published (not as a draft) by the Free
+     Software Foundation.  If the Document specifies that a proxy can
+     decide which future versions of this License can be used, that
      proxy's public statement of acceptance of a version permanently
      authorizes you to choose that version for the Document.
 
@@ -2379,7 +2362,6 @@
      site under CC-BY-SA on the same site at any time before August 1,
      2009, provided the MMC is eligible for relicensing.
 
-
 ADDENDUM: How to use this License for your documents
 ====================================================
 
@@ -2407,108 +2389,10 @@
 situation.
 
    If your document contains nontrivial examples of program code, we
-recommend releasing these examples in parallel under your choice of
-free software license, such as the GNU General Public License, to
-permit their use in free software.
+recommend releasing these examples in parallel under your choice of free
+software license, such as the GNU General Public License, to permit
+their use in free software.
 
 Index
 *****
 
-$ keywords in web pages:                       See 12.4.     (line 1655)
-/gd/gnuorg directory:                          See 6.1.      (line  236)
-<address@hidden>:                       See 9.1.      (line  942)
-<address@hidden>:                         See 4.        (line  164)
-advisory committee:                            See 2.        (line  124)
-alpha.gnu.org, test release site:              See 11.4.     (line 1160)
-announcement mailing list, project-specific:   See 11.6.     (line 1463)
-announcements:                                 See 11.6.     (line 1448)
-announcements, mailing list for:               See 9.1.      (line  953)
-AUTHORS file:                                  See 6.3.      (line  448)
-automake:                                      See 11.1.     (line 1100)
-beta releases:                                 See 11.4.     (line 1160)
-bug reports, handling:                         See 9.3.      (line  996)
address@hidden email address:           See 1.        (line   90)
-contents of announcements:                     See 11.6.     (line 1469)
-contributions, accepting:                      See 7.        (line  847)
-copyright notices in program files:            See 6.5.      (line  505)
-copyright papers:                              See 6.1.      (line  219)
-creating mailing lists:                        See 9.2.      (line  959)
-CVS keywords in web pages:                     See 12.4.     (line 1655)
-CVS repository:                                See 15.       (line 1801)
-data base of GNU copyright assignments:        See 6.1.      (line  230)
-development method, open source:               See 14.1.     (line 1740)
-diff:                                          See 11.2.     (line 1124)
-Directory, Free Software:                      See 17.       (line 1874)
-distribution, tar files:                       See 11.1.     (line 1075)
-Donations, for packages:                       See 16.       (line 1835)
-down, when GNU machines are:                   See 2.        (line  131)
-email:                                         See 9.        (line  926)
-ethics:                                        See 13.       (line 1685)
-FDL, GNU Free Documentation License:           See Appendix A.
-                                                             (line 1931)
-fencepost.gnu.org GNU machine:                 See 3.        (line  144)
-Free Software Directory:                       See 17.       (line 1874)
-free software movement:                        See 14.1.     (line 1740)
-FSF system administrators:                     See 2.        (line  137)
-FTP site:                                      See 15.       (line 1801)
-ftp uploads, automated:                        See 11.5.     (line 1203)
-ftp.gnu.org, the GNU release site:             See 11.3.     (line 1149)
-gendocs.sh:                                    See 12.3.1.   (line 1578)
-generating documentation output:               See 12.3.1.   (line 1578)
-GNU ftp site:                                  See 11.3.     (line 1149)
-GNU system administrators:                     See 2.        (line  137)
-GNU/Linux:                                     See 14.2.     (line 1766)
-gnustandards project repository:               See 1.        (line   90)
address@hidden mailing list:      See 1.        (line   98)
-help for users, mailing list for:              See 9.1.      (line  947)
-help requests, handling:                       See 9.3.      (line  996)
-help, getting:                                 See 2.        (line  118)
-hosting:                                       See 15.       (line 1801)
-http://identi.ca/group/fsfstatus:              See 2.        (line  131)
-http://planet.gnu.org:                         See 11.6.     (line 1456)
-info-gnu mailing list:                         See 11.6.     (line 1448)
-legal matters:                                 See 6.        (line  213)
-legal papers for changes in manuals:           See 6.1.      (line  308)
-license notices in program files:              See 6.6.      (line  606)
-Linux:                                         See 14.2.     (line 1766)
-mailing list for bug reports:                  See 9.1.      (line  933)
-mailing lists, creating:                       See 9.2.      (line  959)
-mailing lists, standard names of:              See 9.1.      (line  933)
address@hidden mailing list:                  See 2.        (line  118)
-Money, donated to packages:                    See 16.       (line 1835)
-movement, free software:                       See 14.1.     (line 1740)
-open source:                                   See 14.1.     (line 1740)
-outage, of GNU machines:                       See 2.        (line  131)
-patch:                                         See 11.2.     (line 1124)
-patches, against previous releases:            See 11.2.     (line 1106)
-philosophy:                                    See 13.       (line 1685)
-Piercy, Marge:                                 See 1.        (line  104)
-pretest releases:                              See 11.4.     (line 1160)
-proofreading:                                  See 18.       (line 1885)
-quality of changes suggested by others:        See 7.        (line  847)
-RCS keywords in web pages:                     See 12.4.     (line 1655)
-recording contributors:                        See 6.3.      (line  417)
-registration for uploads:                      See 11.5.1.   (line 1214)
-release site:                                  See 15.       (line 1801)
-repository:                                    See 15.       (line 1801)
-resigning as maintainer:                       See 4.        (line  155)
-responding to bug reports:                     See 9.3.      (line  996)
-Savannah repository for gnustandards:          See 1.        (line   90)
-Savannah, news area:                           See 11.6.     (line 1456)
address@hidden mailing list:        See 10.       (line 1060)
address@hidden:                      See 10.       (line 1047)
-shell account, on fencepost:                   See 3.        (line  144)
-source repository:                             See 15.       (line 1801)
-spam prevention:                               See 9.2.      (line  979)
-standard mailing lists:                        See 9.1.      (line  933)
-stepping down as maintainer:                   See 4.        (line  155)
-sysadmin, FSF:                                 See 2.        (line  137)
-terminology:                                   See 14.       (line 1733)
-test releases:                                 See 11.4.     (line 1160)
-time stamp in diffs:                           See 11.2.     (line 1124)
-uploads:                                       See 11.5.2.   (line 1262)
-uploads, registration for:                     See 11.5.1.   (line 1214)
-version control:                               See 10.       (line 1035)
-version control system:                        See 15.       (line 1801)
-web pages:                                     See 12.       (line 1489)
-web pages, and CVS keywords:                   See 12.4.     (line 1655)

Index: maintain.txt.gz
===================================================================
RCS file: /web/www/www/prep/maintain/maintain.txt.gz,v
retrieving revision 1.68
retrieving revision 1.69
diff -u -b -r1.68 -r1.69
Binary files /tmp/cvs5mEP89 and /tmp/cvsHlOViR differ

Index: html_node/Announcements.html
===================================================================
RCS file: /web/www/www/prep/maintain/html_node/Announcements.html,v
retrieving revision 1.66
retrieving revision 1.67
diff -u -b -r1.66 -r1.67
--- html_node/Announcements.html        7 Sep 2011 01:31:16 -0000       1.66
+++ html_node/Announcements.html        7 Sep 2011 15:00:14 -0000       1.67
@@ -1,93 +1,130 @@
-<html lang="en">
-<head>
-<title>Announcements - Information for Maintainers of GNU Software</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="Information for Maintainers of GNU Software">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="Distributions.html#Distributions" title="Distributions">
-<link rel="prev" href="Automated-FTP-Uploads.html#Automated-FTP-Uploads" 
title="Automated FTP Uploads">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home" 
title="Texinfo Homepage">
-<!--
-Information for maintainers of GNU software, last updated September 5, 2011.
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" 
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
+<!-- Information for maintainers of GNU software, last updated September 5, 
2011.
 
 Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
 2010, 2011 Free Software Foundation, Inc.
 
-     Permission is granted to copy, distribute and/or modify this
-     document under the terms of the GNU Free Documentation License,
-     Version 1.3 or any later version published by the Free Software
-     Foundation; with no Invariant Sections, with no Front-Cover Texts,
-     and with no Back-Cover Texts.  A copy of the license is included
-     in the section entitled ``GNU Free Documentation License''.
-   -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
-  pre.display { font-family:inherit }
-  pre.format  { font-family:inherit }
-  pre.smalldisplay { font-family:inherit; font-size:smaller }
-  pre.smallformat  { font-family:inherit; font-size:smaller }
-  pre.smallexample { font-size:smaller }
-  pre.smalllisp    { font-size:smaller }
-  span.sc    { font-variant:small-caps }
-  span.roman { font-family:serif; font-weight:normal; } 
-  span.sansserif { font-family:sans-serif; font-weight:normal; } 
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
+Texts.  A copy of the license is included in the section entitled
+"GNU Free Documentation License". -->
+<!-- Created by texi2html, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>Information for Maintainers of GNU Software: Announcements</title>
+
+<meta name="description" content="Information for Maintainers of GNU Software: 
Announcements">
+<meta name="keywords" content="Information for Maintainers of GNU Software: 
Announcements">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="texi2html">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Distributions.html#Distributions" rel="up" title="Distributions">
+<link href="Web-Pages.html#Web-Pages" rel="next" title="Web Pages">
+<link 
href="FTP-Upload-Directive-File-_002d-v1_002e0.html#FTP-Upload-Directive-File-_002d-v1_002e0"
 rel="previous" title="FTP Upload Directive File - v1.0">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smalllisp {margin-left: 3.2em}
+pre.display {font-family: serif}
+pre.format {font-family: serif}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: serif; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: serif; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:pre}
+span.nolinebreak {white-space:pre}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
 </head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF" 
vlink="#800080" alink="#FF0000">
+
 <a name="Announcements"></a>
+<div class="header">
 <p>
-Previous:&nbsp;<a rel="previous" accesskey="p" 
href="Automated-FTP-Uploads.html#Automated-FTP-Uploads">Automated FTP 
Uploads</a>,
-Up:&nbsp;<a rel="up" accesskey="u" 
href="Distributions.html#Distributions">Distributions</a>
-<hr>
+Previous: <a href="Automated-FTP-Uploads.html#Automated-FTP-Uploads" 
accesskey="p" rel="previous">Automated FTP Uploads</a>, Up: <a 
href="Distributions.html#Distributions" accesskey="u" 
rel="up">Distributions</a> &nbsp; [<a href="index.html#SEC_Contents" 
title="Table of contents" rel="contents">Contents</a>][<a 
href="Index.html#Index" title="Index" rel="index">Index</a>]</p>
 </div>
+<hr>
+<a name="Announcing-Releases"></a>
+<h2 class="section">11.6 Announcing Releases</h2>
+<a name="index-announcements"></a>
 
-<h3 class="section">11.6 Announcing Releases</h3>
-
-<p><a name="index-announcements-63"></a>
-<a name="index-g_t_0040code_007binfo_002dgnu_007d-mailing-list-64"></a>When 
you have a new release, please make an announcement.  For
+<a name="index-info_002dgnu-mailing-list"></a>
+<p>When you have a new release, please make an announcement.  For
 official new releases, including those made just to fix bugs, we
 strongly recommend using the (moderated) general GNU announcements
 list, <a href="mailto:address@hidden";>address@hidden</a>.  Doing so makes it 
easier for users
 and developers to find the latest GNU releases.  On the other hand,
-please do not announce test releases on <code>info-gnu</code> unless it's a
+please do not announce test releases on <code>info-gnu</code> unless 
it&rsquo;s a
 highly unusual situation.
-
-   <p><a 
name="index-g_t_0040url_007bhttp_003a_002f_002fplanet_002egnu_002eorg_007d-65"></a><a
 name="index-Savannah_002c-news-area-66"></a>Please also post release 
announcements in the news section of your
+</p>
+<a name="index-http_003a_002f_002fplanet_002egnu_002eorg"></a>
+<a name="index-Savannah_002c-news-area"></a>
+<p>Please also post release announcements in the news section of your
 Savannah project site.  Here, it is fine to also write news entries
 for test releases and any other newsworthy events.  The news feeds
 from all GNU projects at savannah are aggregated at
 <a href="http://planet.gnu.org";>http://planet.gnu.org</a> (GNU Planet).  You 
can also post items
 directly, or arrange for feeds from other locations; see information
 on the GNU Planet web page.
-
-   <p><a 
name="index-announcement-mailing-list_002c-project_002dspecific-67"></a>You can 
maintain your own mailing list (typically
+</p>
+<a name="index-announcement-mailing-list_002c-project_002dspecific"></a>
+<p>You can maintain your own mailing list (typically
 <a 
href="mailto:info-<var>package</var>@gnu.org">info-<var>package</var>@gnu.org</a>)
 for announcements as well if you
 like.  For your own list, of course you decide as you see fit what
 events are worth announcing.  (See <a href="Mail.html#Mail">Mail</a>, for 
setting this up, and
 more suggestions on handling mail for your package.)
-
-   <p><a name="index-contents-of-announcements-68"></a>When writing an 
announcement, please include the following:
-
-     <ul>
-<li>A very brief description (a few sentences at most) of the general
+</p>
+<a name="index-contents-of-announcements"></a>
+<p>When writing an announcement, please include the following:
+</p>
+<ul>
+<li> A very brief description (a few sentences at most) of the general
 purpose of your package.
 
-     <li>Your package's web page (normally
-&lt;<code>http://www.gnu.org/software/</code><var>package</var><code>/</code>&gt;).
+</li><li> Your package&rsquo;s web page (normally
+&lt;<code>http://www.gnu.org/software/<var>package</var>/</code>&gt;).
 
-     <li>Your package's download location (normally
-&lt;<code>http://ftp.gnu.org/gnu/</code><var>package</var><code>/</code>&gt;). 
 It is also
+</li><li> Your package&rsquo;s download location (normally
+&lt;<code>http://ftp.gnu.org/gnu/<var>package</var>/</code>&gt;).  It is also
 useful to mention the mirror list at
 <a 
href="http://www.gnu.org/order/ftp.html";>http://www.gnu.org/order/ftp.html</a>, 
and that
-<a 
href="http://ftpmirror.gnu.org/<var>package/</var>">http://ftpmirror.gnu.org/<var>package/</var></a>
 will automatically
+<a 
href="http://ftpmirror.gnu.org/package/";>http://ftpmirror.gnu.org/package/</a> 
will automatically
 redirect to a nearby mirror.
 
-     <li>The <tt>NEWS</tt> (see <a 
href="../standards/NEWS-File.html#NEWS-File">NEWS File</a>) for
+</li><li> The <tt>NEWS</tt> (see <a 
href="http://www.gnu.org/prep/standards/html_node/NEWS-File.html#NEWS-File";>NEWS
 File</a> in <cite>GNU Coding Standards</cite>) for
 the present release. 
-</ul>
+</li></ul>
+
+
+<hr>
+<div class="header">
+<p>
+Previous: <a href="Automated-FTP-Uploads.html#Automated-FTP-Uploads" 
accesskey="p" rel="previous">Automated FTP Uploads</a>, Up: <a 
href="Distributions.html#Distributions" accesskey="u" 
rel="up">Distributions</a> &nbsp; [<a href="index.html#SEC_Contents" 
title="Table of contents" rel="contents">Contents</a>][<a 
href="Index.html#Index" title="Index" rel="index">Index</a>]</p>
+</div>
+<p>
 
-   </body></html>
 
+</p>
+</body>
+</html>

Index: html_node/Automated-FTP-Uploads.html
===================================================================
RCS file: /web/www/www/prep/maintain/html_node/Automated-FTP-Uploads.html,v
retrieving revision 1.66
retrieving revision 1.67
diff -u -b -r1.66 -r1.67
--- html_node/Automated-FTP-Uploads.html        7 Sep 2011 01:31:16 -0000       
1.66
+++ html_node/Automated-FTP-Uploads.html        7 Sep 2011 15:00:14 -0000       
1.67
@@ -1,67 +1,97 @@
-<html lang="en">
-<head>
-<title>Automated FTP Uploads - Information for Maintainers of GNU 
Software</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="Information for Maintainers of GNU Software">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="Distributions.html#Distributions" title="Distributions">
-<link rel="prev" href="Test-Releases.html#Test-Releases" title="Test Releases">
-<link rel="next" href="Announcements.html#Announcements" title="Announcements">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home" 
title="Texinfo Homepage">
-<!--
-Information for maintainers of GNU software, last updated September 5, 2011.
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" 
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
+<!-- Information for maintainers of GNU software, last updated September 5, 
2011.
 
 Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
 2010, 2011 Free Software Foundation, Inc.
 
-     Permission is granted to copy, distribute and/or modify this
-     document under the terms of the GNU Free Documentation License,
-     Version 1.3 or any later version published by the Free Software
-     Foundation; with no Invariant Sections, with no Front-Cover Texts,
-     and with no Back-Cover Texts.  A copy of the license is included
-     in the section entitled ``GNU Free Documentation License''.
-   -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
-  pre.display { font-family:inherit }
-  pre.format  { font-family:inherit }
-  pre.smalldisplay { font-family:inherit; font-size:smaller }
-  pre.smallformat  { font-family:inherit; font-size:smaller }
-  pre.smallexample { font-size:smaller }
-  pre.smalllisp    { font-size:smaller }
-  span.sc    { font-variant:small-caps }
-  span.roman { font-family:serif; font-weight:normal; } 
-  span.sansserif { font-family:sans-serif; font-weight:normal; } 
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
+Texts.  A copy of the license is included in the section entitled
+"GNU Free Documentation License". -->
+<!-- Created by texi2html, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>Information for Maintainers of GNU Software: Automated FTP 
Uploads</title>
+
+<meta name="description" content="Information for Maintainers of GNU Software: 
Automated FTP Uploads">
+<meta name="keywords" content="Information for Maintainers of GNU Software: 
Automated FTP Uploads">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="texi2html">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Distributions.html#Distributions" rel="up" title="Distributions">
+<link href="Automated-Upload-Registration.html#Automated-Upload-Registration" 
rel="next" title="Automated Upload Registration">
+<link href="Test-Releases.html#Test-Releases" rel="previous" title="Test 
Releases">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smalllisp {margin-left: 3.2em}
+pre.display {font-family: serif}
+pre.format {font-family: serif}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: serif; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: serif; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:pre}
+span.nolinebreak {white-space:pre}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
 </head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF" 
vlink="#800080" alink="#FF0000">
+
 <a name="Automated-FTP-Uploads"></a>
+<div class="header">
 <p>
-Next:&nbsp;<a rel="next" accesskey="n" 
href="Announcements.html#Announcements">Announcements</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" 
href="Test-Releases.html#Test-Releases">Test Releases</a>,
-Up:&nbsp;<a rel="up" accesskey="u" 
href="Distributions.html#Distributions">Distributions</a>
-<hr>
+Next: <a href="Announcements.html#Announcements" accesskey="n" 
rel="next">Announcements</a>, Previous: <a 
href="Test-Releases.html#Test-Releases" accesskey="p" rel="previous">Test 
Releases</a>, Up: <a href="Distributions.html#Distributions" accesskey="u" 
rel="up">Distributions</a> &nbsp; [<a href="index.html#SEC_Contents" 
title="Table of contents" rel="contents">Contents</a>][<a 
href="Index.html#Index" title="Index" rel="index">Index</a>]</p>
 </div>
+<hr>
+<a name="Automated-FTP-Uploads-1"></a>
+<h2 class="section">11.5 Automated FTP Uploads</h2>
 
-<h3 class="section">11.5 Automated FTP Uploads</h3>
-
-<p><a name="index-ftp-uploads_002c-automated-59"></a>In order to upload new 
releases to <code>ftp.gnu.org</code> or
+<a name="index-ftp-uploads_002c-automated"></a>
+<p>In order to upload new releases to <code>ftp.gnu.org</code> or
 <code>alpha.gnu.org</code>, you first need to register the necessary
 information.  Then, you can perform uploads yourself, with no
 intervention needed by the system administrators.
-
-   <p>The general idea is that releases should be crytographically signed
+</p>
+<p>The general idea is that releases should be crytographically signed
 before they are made publicly available.
+</p>
+<table class="menu" border="0" cellspacing="0">
+<tr><td align="left" valign="top">&bull; <a 
href="Automated-Upload-Registration.html#Automated-Upload-Registration" 
accesskey="1">Automated Upload Registration</a>:</td><td>&nbsp;&nbsp;</td><td 
align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a 
href="Automated-Upload-Procedure.html#Automated-Upload-Procedure" 
accesskey="2">Automated Upload Procedure</a>:</td><td>&nbsp;&nbsp;</td><td 
align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a 
href="FTP-Upload-Directive-File-_002d-v1_002e1.html#FTP-Upload-Directive-File-_002d-v1_002e1"
 accesskey="3">FTP Upload Directive File - 
v1.1</a>:</td><td>&nbsp;&nbsp;</td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a 
href="FTP-Upload-Directive-File-_002d-v1_002e0.html#FTP-Upload-Directive-File-_002d-v1_002e0"
 accesskey="4">FTP Upload Directive File - 
v1.0</a>:</td><td>&nbsp;&nbsp;</td><td align="left" valign="top">
+</td></tr>
+</table>
+
 
-<ul class="menu">
-<li><a accesskey="1" 
href="Automated-Upload-Registration.html#Automated-Upload-Registration">Automated
 Upload Registration</a>
-<li><a accesskey="2" 
href="Automated-Upload-Procedure.html#Automated-Upload-Procedure">Automated 
Upload Procedure</a>
-<li><a accesskey="3" 
href="FTP-Upload-Directive-File-_002d-v1_002e1.html#FTP-Upload-Directive-File-_002d-v1_002e1">FTP
 Upload Directive File - v1.1</a>
-<li><a accesskey="4" 
href="FTP-Upload-Directive-File-_002d-v1_002e0.html#FTP-Upload-Directive-File-_002d-v1_002e0">FTP
 Upload Directive File - v1.0</a>
-</ul>
+<p>
 
-   </body></html>
 
+</p>
+</body>
+</html>

Index: html_node/Automated-Upload-Procedure.html
===================================================================
RCS file: /web/www/www/prep/maintain/html_node/Automated-Upload-Procedure.html,v
retrieving revision 1.66
retrieving revision 1.67
diff -u -b -r1.66 -r1.67
--- html_node/Automated-Upload-Procedure.html   7 Sep 2011 01:31:16 -0000       
1.66
+++ html_node/Automated-Upload-Procedure.html   7 Sep 2011 15:00:16 -0000       
1.67
@@ -1,118 +1,150 @@
-<html lang="en">
-<head>
-<title>Automated Upload Procedure - Information for Maintainers of GNU 
Software</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="Information for Maintainers of GNU Software">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="Automated-FTP-Uploads.html#Automated-FTP-Uploads" 
title="Automated FTP Uploads">
-<link rel="prev" 
href="Automated-Upload-Registration.html#Automated-Upload-Registration" 
title="Automated Upload Registration">
-<link rel="next" 
href="FTP-Upload-Directive-File-_002d-v1_002e1.html#FTP-Upload-Directive-File-_002d-v1_002e1"
 title="FTP Upload Directive File - v1.1">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home" 
title="Texinfo Homepage">
-<!--
-Information for maintainers of GNU software, last updated September 5, 2011.
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" 
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
+<!-- Information for maintainers of GNU software, last updated September 5, 
2011.
 
 Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
 2010, 2011 Free Software Foundation, Inc.
 
-     Permission is granted to copy, distribute and/or modify this
-     document under the terms of the GNU Free Documentation License,
-     Version 1.3 or any later version published by the Free Software
-     Foundation; with no Invariant Sections, with no Front-Cover Texts,
-     and with no Back-Cover Texts.  A copy of the license is included
-     in the section entitled ``GNU Free Documentation License''.
-   -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
-  pre.display { font-family:inherit }
-  pre.format  { font-family:inherit }
-  pre.smalldisplay { font-family:inherit; font-size:smaller }
-  pre.smallformat  { font-family:inherit; font-size:smaller }
-  pre.smallexample { font-size:smaller }
-  pre.smalllisp    { font-size:smaller }
-  span.sc    { font-variant:small-caps }
-  span.roman { font-family:serif; font-weight:normal; } 
-  span.sansserif { font-family:sans-serif; font-weight:normal; } 
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
+Texts.  A copy of the license is included in the section entitled
+"GNU Free Documentation License". -->
+<!-- Created by texi2html, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>Information for Maintainers of GNU Software: Automated Upload 
Procedure</title>
+
+<meta name="description" content="Information for Maintainers of GNU Software: 
Automated Upload Procedure">
+<meta name="keywords" content="Information for Maintainers of GNU Software: 
Automated Upload Procedure">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="texi2html">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Automated-FTP-Uploads.html#Automated-FTP-Uploads" rel="up" 
title="Automated FTP Uploads">
+<link 
href="FTP-Upload-Directive-File-_002d-v1_002e1.html#FTP-Upload-Directive-File-_002d-v1_002e1"
 rel="next" title="FTP Upload Directive File - v1.1">
+<link href="Automated-Upload-Registration.html#Automated-Upload-Registration" 
rel="previous" title="Automated Upload Registration">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smalllisp {margin-left: 3.2em}
+pre.display {font-family: serif}
+pre.format {font-family: serif}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: serif; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: serif; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:pre}
+span.nolinebreak {white-space:pre}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
 </head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF" 
vlink="#800080" alink="#FF0000">
+
 <a name="Automated-Upload-Procedure"></a>
+<div class="header">
 <p>
-Next:&nbsp;<a rel="next" accesskey="n" 
href="FTP-Upload-Directive-File-_002d-v1_002e1.html#FTP-Upload-Directive-File-_002d-v1_002e1">FTP
 Upload Directive File - v1.1</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" 
href="Automated-Upload-Registration.html#Automated-Upload-Registration">Automated
 Upload Registration</a>,
-Up:&nbsp;<a rel="up" accesskey="u" 
href="Automated-FTP-Uploads.html#Automated-FTP-Uploads">Automated FTP 
Uploads</a>
-<hr>
+Next: <a 
href="FTP-Upload-Directive-File-_002d-v1_002e1.html#FTP-Upload-Directive-File-_002d-v1_002e1"
 accesskey="n" rel="next">FTP Upload Directive File - v1.1</a>, Previous: <a 
href="Automated-Upload-Registration.html#Automated-Upload-Registration" 
accesskey="p" rel="previous">Automated Upload Registration</a>, Up: <a 
href="Automated-FTP-Uploads.html#Automated-FTP-Uploads" accesskey="u" 
rel="up">Automated FTP Uploads</a> &nbsp; [<a href="index.html#SEC_Contents" 
title="Table of contents" rel="contents">Contents</a>][<a 
href="Index.html#Index" title="Index" rel="index">Index</a>]</p>
 </div>
+<hr>
+<a name="Automated-Upload-Procedure-1"></a>
+<h3 class="subsection">11.5.2 Automated Upload Procedure</h3>
 
-<h4 class="subsection">11.5.2 Automated Upload Procedure</h4>
+<a name="index-uploads"></a>
 
-<p><a name="index-uploads-62"></a>
-Once you have registered your information as described in the previous
+<p>Once you have registered your information as described in the previous
 section, you will be able to do ftp uploads for yourself using the
 following procedure.
-
-   <p>For each upload destined for <code>ftp.gnu.org</code> or
-<code>alpha.gnu.org</code>, three files (a <dfn>triplet</dfn>) need to be
+</p>
+<p>For each upload destined for <code>ftp.gnu.org</code> or
+<code>alpha.gnu.org</code>, three files (a <em>triplet</em>) need to be
 uploaded via ftp to the host <code>ftp-upload.gnu.org</code>.
+</p>
+<ol>
+<li> The file to be distributed; for example, 
&lsquo;<tt>foo.tar.gz</tt>&rsquo;.
+
+</li><li> Detached GPG binary signature file for (1); for example,
+&lsquo;<tt>foo.tar.gz.sig</tt>&rsquo;.  Make this with &lsquo;<samp>gpg -b 
foo.tar.gz</samp>&rsquo;.
+
+</li><li> A clearsigned <em>directive file</em>; for example,
+&lsquo;<tt>foo.tar.gz.directive.asc</tt>&rsquo;.  Make this by preparing the 
plain
+text file &lsquo;<tt>foo.tar.gz.directive</tt>&rsquo; and then run 
&lsquo;<samp>gpg
+--clearsign foo.tar.gz.directive</samp>&rsquo;.  See <a 
href="FTP-Upload-Directive-File-_002d-v1_002e1.html#FTP-Upload-Directive-File-_002d-v1_002e1">FTP
 Upload Directive File -
+v1.1</a>, for the contents of the directive file.
+</li></ol>
 
-     <ol type=1 start=1>
-<li>The file to be distributed; for example, <samp><span 
class="file">foo.tar.gz</span></samp>.
-
-     <li>Detached GPG binary signature file for (1); for example,
-<samp><span class="file">foo.tar.gz.sig</span></samp>.  Make this with 
&lsquo;<samp><span class="samp">gpg -b foo.tar.gz</span></samp>&rsquo;.
-
-     <li>A clearsigned <dfn>directive file</dfn>; for example,
-<samp><span class="file">foo.tar.gz.directive.asc</span></samp>.  Make this by 
preparing the plain
-text file <samp><span class="file">foo.tar.gz.directive</span></samp> and then 
run &lsquo;<samp><span class="samp">gpg
---clearsign foo.tar.gz.directive</span></samp>&rsquo;.  See <a 
href="FTP-Upload-Directive-File-_002d-v1_002e1.html#FTP-Upload-Directive-File-_002d-v1_002e1">FTP
 Upload Directive File - v1.1</a>, for the contents of the directive file.
-        </ol>
-
-   <p>The names of the files are important. The signature file must have the
+<p>The names of the files are important. The signature file must have the
 same name as the file to be distributed, with an additional
-<samp><span class="file">.sig</span></samp> extension. The directive file must 
have the same name as
-the file to be distributed, with an additional <samp><span 
class="file">.directive.asc</span></samp>
+&lsquo;<tt>.sig</tt>&rsquo; extension. The directive file must have the same 
name as
+the file to be distributed, with an additional 
&lsquo;<tt>.directive.asc</tt>&rsquo;
 extension. If you do not follow this naming convention, the upload
 <em>will not be processed</em>.
-
-   <p>Since v1.1 of the upload script, it is also possible to upload a
-clearsigned directive file on its own (no accompanying <samp><span 
class="file">.sig</span></samp> or
+</p>
+<p>Since v1.1 of the upload script, it is also possible to upload a
+clearsigned directive file on its own (no accompanying 
&lsquo;<tt>.sig</tt>&rsquo; or
 any other file) to perform certain operations on the server. 
 See <a 
href="FTP-Upload-Directive-File-_002d-v1_002e1.html#FTP-Upload-Directive-File-_002d-v1_002e1">FTP
 Upload Directive File - v1.1</a>, for more information.
-
-   <p>Upload the file(s) via anonymous ftp to <code>ftp-upload.gnu.org</code>. 
If
+</p>
+<p>Upload the file(s) via anonymous ftp to <code>ftp-upload.gnu.org</code>. If
 the upload is destined for <code>ftp.gnu.org</code>, place the file(s) in
-the <samp><span class="file">/incoming/ftp</span></samp> directory. If the 
upload is destined for
-<code>alpha.gnu.org</code>, place the file(s) in the <samp><span 
class="file">/incoming/alpha</span></samp>
+the &lsquo;<tt>/incoming/ftp</tt>&rsquo; directory. If the upload is destined 
for
+<code>alpha.gnu.org</code>, place the file(s) in the 
&lsquo;<tt>/incoming/alpha</tt>&rsquo;
 directory.
-
-   <p>Uploads are processed every five minutes.  Uploads that are in
+</p>
+<p>Uploads are processed every five minutes.  Uploads that are in
 progress while the upload processing script is running are handled
 properly, so do not worry about the timing of your upload.  Uploaded
 files that belong to an incomplete triplet are deleted automatically
 after 24 hours.
-
-   <p>Your designated upload email addresses (see <a 
href="Automated-Upload-Registration.html#Automated-Upload-Registration">Automated
 Upload Registration</a>)
+</p>
+<p>Your designated upload email addresses (see <a 
href="Automated-Upload-Registration.html#Automated-Upload-Registration">Automated
 Upload Registration</a>)
 are sent a message if there are any problems processing an upload for your
 package. You also receive a message when your upload has been successfully
 processed.
-
-   <p>One automated way to create and transfer the necessary files is to use
+</p>
+<p>One automated way to create and transfer the necessary files is to use
 the <code>gnupload</code> script, which is available from the
-<samp><span class="file">build-aux/</span></samp> directory of the 
<code>gnulib</code> project at
+&lsquo;<tt>build-aux/</tt>&rsquo; directory of the <code>gnulib</code> project 
at
 <a 
href="http://savannah.gnu.org/projects/gnulib";>http://savannah.gnu.org/projects/gnulib</a>.
  <code>gnupload</code> can
 also remove uploaded files.  Run <code>gnupload --help</code> for a
 description and examples.
-
-   <p><code>gnupload</code> uses the <code>ncftpput</code> program to do the 
actual
-transfers; if you don't happen to have the <code>ncftp</code> package
-installed, the <code>ncftpput-ftp</code> script in the <samp><span 
class="file">build-aux/</span></samp>
+</p>
+<p><code>gnupload</code> uses the <code>ncftpput</code> program to do the 
actual
+transfers; if you don&rsquo;t happen to have the <code>ncftp</code> package
+installed, the <code>ncftpput-ftp</code> script in the 
&lsquo;<tt>build-aux/</tt>&rsquo;
 directory of <code>gnulib</code> serves as a replacement which uses plain
 command line <code>ftp</code>.
-
-   <p>If you have difficulties with an upload, email
+</p>
+<p>If you have difficulties with an upload, email
 <a href="mailto:address@hidden";>address@hidden</a>.
+</p>
+
+<hr>
+<div class="header">
+<p>
+Next: <a 
href="FTP-Upload-Directive-File-_002d-v1_002e1.html#FTP-Upload-Directive-File-_002d-v1_002e1"
 accesskey="n" rel="next">FTP Upload Directive File - v1.1</a>, Previous: <a 
href="Automated-Upload-Registration.html#Automated-Upload-Registration" 
accesskey="p" rel="previous">Automated Upload Registration</a>, Up: <a 
href="Automated-FTP-Uploads.html#Automated-FTP-Uploads" accesskey="u" 
rel="up">Automated FTP Uploads</a> &nbsp; [<a href="index.html#SEC_Contents" 
title="Table of contents" rel="contents">Contents</a>][<a 
href="Index.html#Index" title="Index" rel="index">Index</a>]</p>
+</div>
+<p>
 
-   </body></html>
 
+</p>
+</body>
+</html>

Index: html_node/Automated-Upload-Registration.html
===================================================================
RCS file: 
/web/www/www/prep/maintain/html_node/Automated-Upload-Registration.html,v
retrieving revision 1.66
retrieving revision 1.67
diff -u -b -r1.66 -r1.67
--- html_node/Automated-Upload-Registration.html        7 Sep 2011 01:31:16 
-0000       1.66
+++ html_node/Automated-Upload-Registration.html        7 Sep 2011 15:00:16 
-0000       1.67
@@ -1,99 +1,132 @@
-<html lang="en">
-<head>
-<title>Automated Upload Registration - Information for Maintainers of GNU 
Software</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="Information for Maintainers of GNU Software">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="Automated-FTP-Uploads.html#Automated-FTP-Uploads" 
title="Automated FTP Uploads">
-<link rel="next" 
href="Automated-Upload-Procedure.html#Automated-Upload-Procedure" 
title="Automated Upload Procedure">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home" 
title="Texinfo Homepage">
-<!--
-Information for maintainers of GNU software, last updated September 5, 2011.
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" 
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
+<!-- Information for maintainers of GNU software, last updated September 5, 
2011.
 
 Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
 2010, 2011 Free Software Foundation, Inc.
 
-     Permission is granted to copy, distribute and/or modify this
-     document under the terms of the GNU Free Documentation License,
-     Version 1.3 or any later version published by the Free Software
-     Foundation; with no Invariant Sections, with no Front-Cover Texts,
-     and with no Back-Cover Texts.  A copy of the license is included
-     in the section entitled ``GNU Free Documentation License''.
-   -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
-  pre.display { font-family:inherit }
-  pre.format  { font-family:inherit }
-  pre.smalldisplay { font-family:inherit; font-size:smaller }
-  pre.smallformat  { font-family:inherit; font-size:smaller }
-  pre.smallexample { font-size:smaller }
-  pre.smalllisp    { font-size:smaller }
-  span.sc    { font-variant:small-caps }
-  span.roman { font-family:serif; font-weight:normal; } 
-  span.sansserif { font-family:sans-serif; font-weight:normal; } 
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
+Texts.  A copy of the license is included in the section entitled
+"GNU Free Documentation License". -->
+<!-- Created by texi2html, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>Information for Maintainers of GNU Software: Automated Upload 
Registration</title>
+
+<meta name="description" content="Information for Maintainers of GNU Software: 
Automated Upload Registration">
+<meta name="keywords" content="Information for Maintainers of GNU Software: 
Automated Upload Registration">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="texi2html">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Automated-FTP-Uploads.html#Automated-FTP-Uploads" rel="up" 
title="Automated FTP Uploads">
+<link href="Automated-Upload-Procedure.html#Automated-Upload-Procedure" 
rel="next" title="Automated Upload Procedure">
+<link href="Automated-FTP-Uploads.html#Automated-FTP-Uploads" rel="previous" 
title="Automated FTP Uploads">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smalllisp {margin-left: 3.2em}
+pre.display {font-family: serif}
+pre.format {font-family: serif}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: serif; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: serif; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:pre}
+span.nolinebreak {white-space:pre}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
 </head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF" 
vlink="#800080" alink="#FF0000">
+
 <a name="Automated-Upload-Registration"></a>
+<div class="header">
 <p>
-Next:&nbsp;<a rel="next" accesskey="n" 
href="Automated-Upload-Procedure.html#Automated-Upload-Procedure">Automated 
Upload Procedure</a>,
-Up:&nbsp;<a rel="up" accesskey="u" 
href="Automated-FTP-Uploads.html#Automated-FTP-Uploads">Automated FTP 
Uploads</a>
-<hr>
+Next: <a href="Automated-Upload-Procedure.html#Automated-Upload-Procedure" 
accesskey="n" rel="next">Automated Upload Procedure</a>, Up: <a 
href="Automated-FTP-Uploads.html#Automated-FTP-Uploads" accesskey="u" 
rel="up">Automated FTP Uploads</a> &nbsp; [<a href="index.html#SEC_Contents" 
title="Table of contents" rel="contents">Contents</a>][<a 
href="Index.html#Index" title="Index" rel="index">Index</a>]</p>
 </div>
+<hr>
+<a name="Automated-Upload-Registration-1"></a>
+<h3 class="subsection">11.5.1 Automated Upload Registration</h3>
 
-<h4 class="subsection">11.5.1 Automated Upload Registration</h4>
+<a name="index-registration-for-uploads"></a>
+<a name="index-uploads_002c-registration-for"></a>
 
-<p><a name="index-registration-for-uploads-60"></a><a 
name="index-uploads_002c-registration-for-61"></a>
-Here is how to register your information so you can perform uploads
+<p>Here is how to register your information so you can perform uploads
 for your GNU package:
-
-     <ol type=1 start=1>
-
-     <li>Create an account for yourself at <a 
href="http://savannah.gnu.org";>http://savannah.gnu.org</a>, if
-you don't already have one.  By the way, this is also needed to
+</p>
+<ol>
+<li> Create an account for yourself at <a 
href="http://savannah.gnu.org";>http://savannah.gnu.org</a>, if
+you don&rsquo;t already have one.  By the way, this is also needed to
 maintain the web pages at <a href="http://www.gnu.org";>http://www.gnu.org</a> 
for your project
 (see <a href="Web-Pages.html#Web-Pages">Web Pages</a>).
 
-     <li>In the &lsquo;<samp><span class="samp">My Account 
Conf</span></samp>&rsquo; page on <code>savannah</code>, upload the GPG
-key you will use to sign your packages.  If you haven't created one
+</li><li> In the &lsquo;<samp>My Account Conf</samp>&rsquo; page on 
<code>savannah</code>, upload the GPG
+key you will use to sign your packages.  If you haven&rsquo;t created one
 before, you can do so with the command <code>gpg --gen-key</code> (you can
 accept all the default answers to its questions).
 
-     <p>Optional but recommended: Send your key to a GPG public key server:
-<code>gpg --keyserver keys.gnupg.net --send-keys </code><var>keyid</var>, where
+<p>Optional but recommended: Send your key to a GPG public key server:
+<code>gpg --keyserver keys.gnupg.net --send-keys <var>keyid</var></code>, where
 <var>keyid</var> is the eight hex digits reported by <code>gpg
 --list-public-keys</code> on the <code>pub</code> line before the date.  For 
full
 information about GPG, see <a 
href="http://www.gnu.org/software/gpg";>http://www.gnu.org/software/gpg</a>.
-
-     <li>Compose a message with the following items in some 
<var>msgfile</var>. 
-Then GPG-sign it by running <code>gpg --clearsign </code><var>msgfile</var>, 
and
-finally email the resulting <samp><var>msgfile</var><span 
class="file">.asc</span></samp>), to
+</p>
+</li><li> Compose a message with the following items in some 
<var>msgfile</var>.
+Then GPG-sign it by running <code>gpg --clearsign <var>msgfile</var></code>, 
and
+finally email the resulting &lsquo;<tt><var>msgfile</var>.asc</tt>&rsquo;), to
 <a href="mailto:address@hidden";>address@hidden</a>.
 
-          <ol type=1 start=1>
-<li>Name of package(s) that you are the maintainer for, your
+<ol>
+<li> Name of package(s) that you are the maintainer for, your
 preferred email address, and your Savannah username.
 
-          <li>An ASCII armored copy of your GPG key, as an attachment.  
(&lsquo;<samp><span class="samp">gpg
---export -a </span><var>your_key_id</var><span class="samp"> 
&gt;mykey.asc</span></samp>&rsquo; should give you this.)
+</li><li> An ASCII armored copy of your GPG key, as an attachment.  
(&lsquo;<samp>gpg
+--export -a <var>your_key_id</var> &gt;mykey.asc</samp>&rsquo; should give you 
this.)
 
-          <li>A list of names and preferred email addresses of other 
individuals you
+</li><li> A list of names and preferred email addresses of other individuals 
you
 authorize to make releases for which packages, if any (in the case that you
-don't make all releases yourself).
+don&rsquo;t make all releases yourself).
 
-          <li>ASCII armored copies of GPG keys for any individuals listed in 
(3).
-          </ol>
-        </ol>
+</li><li> ASCII armored copies of GPG keys for any individuals listed in (3).
+</li></ol>
+</li></ol>
 
-   <p>The administrators will acknowledge your message when they have added
+<p>The administrators will acknowledge your message when they have added
 the proper GPG keys as authorized to upload files for the
 corresponding packages.
-
-   <p>The upload system will email receipts to the given email addresses
+</p>
+<p>The upload system will email receipts to the given email addresses
 when an upload is made, either successfully or unsuccessfully.
+</p>
+
+<hr>
+<div class="header">
+<p>
+Next: <a href="Automated-Upload-Procedure.html#Automated-Upload-Procedure" 
accesskey="n" rel="next">Automated Upload Procedure</a>, Up: <a 
href="Automated-FTP-Uploads.html#Automated-FTP-Uploads" accesskey="u" 
rel="up">Automated FTP Uploads</a> &nbsp; [<a href="index.html#SEC_Contents" 
title="Table of contents" rel="contents">Contents</a>][<a 
href="Index.html#Index" title="Index" rel="index">Index</a>]</p>
+</div>
+<p>
 
-   </body></html>
 
+</p>
+</body>
+</html>

Index: html_node/CVS-Keywords-in-Web-Pages.html
===================================================================
RCS file: /web/www/www/prep/maintain/html_node/CVS-Keywords-in-Web-Pages.html,v
retrieving revision 1.65
retrieving revision 1.66
diff -u -b -r1.65 -r1.66
--- html_node/CVS-Keywords-in-Web-Pages.html    7 Sep 2011 01:31:16 -0000       
1.65
+++ html_node/CVS-Keywords-in-Web-Pages.html    7 Sep 2011 15:00:17 -0000       
1.66
@@ -1,80 +1,114 @@
-<html lang="en">
-<head>
-<title>CVS Keywords in Web Pages - Information for Maintainers of GNU 
Software</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="Information for Maintainers of GNU Software">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="Web-Pages.html#Web-Pages" title="Web Pages">
-<link rel="prev" href="Manuals-on-Web-Pages.html#Manuals-on-Web-Pages" 
title="Manuals on Web Pages">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home" 
title="Texinfo Homepage">
-<!--
-Information for maintainers of GNU software, last updated September 5, 2011.
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" 
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
+<!-- Information for maintainers of GNU software, last updated September 5, 
2011.
 
 Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
 2010, 2011 Free Software Foundation, Inc.
 
-     Permission is granted to copy, distribute and/or modify this
-     document under the terms of the GNU Free Documentation License,
-     Version 1.3 or any later version published by the Free Software
-     Foundation; with no Invariant Sections, with no Front-Cover Texts,
-     and with no Back-Cover Texts.  A copy of the license is included
-     in the section entitled ``GNU Free Documentation License''.
-   -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
-  pre.display { font-family:inherit }
-  pre.format  { font-family:inherit }
-  pre.smalldisplay { font-family:inherit; font-size:smaller }
-  pre.smallformat  { font-family:inherit; font-size:smaller }
-  pre.smallexample { font-size:smaller }
-  pre.smalllisp    { font-size:smaller }
-  span.sc    { font-variant:small-caps }
-  span.roman { font-family:serif; font-weight:normal; } 
-  span.sansserif { font-family:sans-serif; font-weight:normal; } 
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
+Texts.  A copy of the license is included in the section entitled
+"GNU Free Documentation License". -->
+<!-- Created by texi2html, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>Information for Maintainers of GNU Software: CVS Keywords in Web 
Pages</title>
+
+<meta name="description" content="Information for Maintainers of GNU Software: 
CVS Keywords in Web Pages">
+<meta name="keywords" content="Information for Maintainers of GNU Software: 
CVS Keywords in Web Pages">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="texi2html">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Web-Pages.html#Web-Pages" rel="up" title="Web Pages">
+<link 
href="Ethical-and-Philosophical-Consideration.html#Ethical-and-Philosophical-Consideration"
 rel="next" title="Ethical and Philosophical Consideration">
+<link href="Invoking-gendocs_002esh.html#Invoking-gendocs_002esh" 
rel="previous" title="Invoking gendocs.sh">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smalllisp {margin-left: 3.2em}
+pre.display {font-family: serif}
+pre.format {font-family: serif}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: serif; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: serif; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:pre}
+span.nolinebreak {white-space:pre}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
 </head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF" 
vlink="#800080" alink="#FF0000">
+
 <a name="CVS-Keywords-in-Web-Pages"></a>
+<div class="header">
 <p>
-Previous:&nbsp;<a rel="previous" accesskey="p" 
href="Manuals-on-Web-Pages.html#Manuals-on-Web-Pages">Manuals on Web Pages</a>,
-Up:&nbsp;<a rel="up" accesskey="u" href="Web-Pages.html#Web-Pages">Web 
Pages</a>
-<hr>
+Previous: <a href="Manuals-on-Web-Pages.html#Manuals-on-Web-Pages" 
accesskey="p" rel="previous">Manuals on Web Pages</a>, Up: <a 
href="Web-Pages.html#Web-Pages" accesskey="u" rel="up">Web Pages</a> &nbsp; [<a 
href="index.html#SEC_Contents" title="Table of contents" 
rel="contents">Contents</a>][<a href="Index.html#Index" title="Index" 
rel="index">Index</a>]</p>
 </div>
-
-<h3 class="section">12.4 CVS Keywords in Web Pages</h3>
-
-<p><a name="index-CVS-keywords-in-web-pages-72"></a><a 
name="index-RCS-keywords-in-web-pages-73"></a><a 
name="index-g_t_0024-keywords-in-web-pages-74"></a><a 
name="index-web-pages_002c-and-CVS-keywords-75"></a>
-Since <code>www.gnu.org</code> works through CVS, CVS keywords in your
-manual, such as <code>$<!-- /@w -->Log$</code>, need special treatment (even 
if you
-don't happen to maintain your manual in CVS).
-
-   <p>If these keywords end up in the generated output as literal strings,
+<hr>
+<a name="CVS-Keywords-in-Web-Pages-1"></a>
+<h2 class="section">12.4 CVS Keywords in Web Pages</h2>
+<a name="index-CVS-keywords-in-web-pages"></a>
+<a name="index-RCS-keywords-in-web-pages"></a>
+<a name="index-_0024-keywords-in-web-pages"></a>
+<a name="index-web-pages_002c-and-CVS-keywords"></a>
+
+<p>Since <code>www.gnu.org</code> works through CVS, CVS keywords in your
+manual, such as <code>$Log$</code>, need special treatment (even if you
+don&rsquo;t happen to maintain your manual in CVS).
+</p>
+<p>If these keywords end up in the generated output as literal strings,
 they will be expanded.  The most robust way to handle this is to turn
 off keyword expansion for such generated files.  For existing files,
 this is done with:
+</p>
+<div class="example">
+<pre class="example">cvs admin -ko <var>file1</var> <var>file2</var> ...
+</pre></div>
+
+<p>For new files:
+</p>
+<div class="example">
+<pre class="example">cvs add -ko <var>file1</var> <var>file2</var> ...
+</pre></div>
 
-<pre class="example">     cvs admin -ko <var>file1</var> <var>file2</var> ...
-</pre>
-   <p class="noindent">For new files:
-
-<pre class="example">     cvs add -ko <var>file1</var> <var>file2</var> ...
-</pre>
-   <!-- The CVS manual is now built with numeric references and no nonsplit -->
-<!-- form, so it's not worth trying to give a direct link. -->
-   <p>See the &ldquo;Keyword Substitution&rdquo; section in the CVS manual, 
available
+<p>See the &ldquo;Keyword Substitution&rdquo; section in the CVS manual, 
available
 at <a href="http://ximbiot.com/cvs/manual";>http://ximbiot.com/cvs/manual</a>.
-
-   <p>In Texinfo source, the recommended way to literally specify a
+</p>
+<p>In Texinfo source, the recommended way to literally specify a
 &ldquo;dollar&rdquo; keyword is:
+</p>
+<div class="example">
+<pre class="example">@w{$}Log$
+</pre></div>
 
-<pre class="example">     @w{$}Log$
-</pre>
-   <p>The <code>@w</code> prevents keyword expansion in the Texinfo source
+<p>The <code>@w</code> prevents keyword expansion in the Texinfo source
 itself.  Also, <code>makeinfo</code> notices the <code>@w</code> and generates
 output avoiding the literal keyword string.
+</p>
+
+<p>
 
-   </body></html>
 
+</p>
+</body>
+</html>

Index: html_node/Canonical-License-Sources.html
===================================================================
RCS file: /web/www/www/prep/maintain/html_node/Canonical-License-Sources.html,v
retrieving revision 1.50
retrieving revision 1.51
diff -u -b -r1.50 -r1.51
--- html_node/Canonical-License-Sources.html    7 Sep 2011 01:31:16 -0000       
1.50
+++ html_node/Canonical-License-Sources.html    7 Sep 2011 15:00:17 -0000       
1.51
@@ -1,69 +1,95 @@
-<html lang="en">
-<head>
-<title>Canonical License Sources - Information for Maintainers of GNU 
Software</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="Information for Maintainers of GNU Software">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="License-Notices.html#License-Notices" title="License 
Notices">
-<link rel="prev" 
href="Licensing-of-GNU-Packages.html#Licensing-of-GNU-Packages" 
title="Licensing of GNU Packages">
-<link rel="next" href="License-Notices-for-Code.html#License-Notices-for-Code" 
title="License Notices for Code">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home" 
title="Texinfo Homepage">
-<!--
-Information for maintainers of GNU software, last updated September 5, 2011.
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" 
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
+<!-- Information for maintainers of GNU software, last updated September 5, 
2011.
 
 Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
 2010, 2011 Free Software Foundation, Inc.
 
-     Permission is granted to copy, distribute and/or modify this
-     document under the terms of the GNU Free Documentation License,
-     Version 1.3 or any later version published by the Free Software
-     Foundation; with no Invariant Sections, with no Front-Cover Texts,
-     and with no Back-Cover Texts.  A copy of the license is included
-     in the section entitled ``GNU Free Documentation License''.
-   -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
-  pre.display { font-family:inherit }
-  pre.format  { font-family:inherit }
-  pre.smalldisplay { font-family:inherit; font-size:smaller }
-  pre.smallformat  { font-family:inherit; font-size:smaller }
-  pre.smallexample { font-size:smaller }
-  pre.smalllisp    { font-size:smaller }
-  span.sc    { font-variant:small-caps }
-  span.roman { font-family:serif; font-weight:normal; } 
-  span.sansserif { font-family:sans-serif; font-weight:normal; } 
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
+Texts.  A copy of the license is included in the section entitled
+"GNU Free Documentation License". -->
+<!-- Created by texi2html, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>Information for Maintainers of GNU Software: Canonical License 
Sources</title>
+
+<meta name="description" content="Information for Maintainers of GNU Software: 
Canonical License Sources">
+<meta name="keywords" content="Information for Maintainers of GNU Software: 
Canonical License Sources">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="texi2html">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="License-Notices.html#License-Notices" rel="up" title="License 
Notices">
+<link href="License-Notices-for-Code.html#License-Notices-for-Code" rel="next" 
title="License Notices for Code">
+<link href="Licensing-of-GNU-Packages.html#Licensing-of-GNU-Packages" 
rel="previous" title="Licensing of GNU Packages">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smalllisp {margin-left: 3.2em}
+pre.display {font-family: serif}
+pre.format {font-family: serif}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: serif; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: serif; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:pre}
+span.nolinebreak {white-space:pre}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
 </head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF" 
vlink="#800080" alink="#FF0000">
+
 <a name="Canonical-License-Sources"></a>
+<div class="header">
 <p>
-Next:&nbsp;<a rel="next" accesskey="n" 
href="License-Notices-for-Code.html#License-Notices-for-Code">License Notices 
for Code</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" 
href="Licensing-of-GNU-Packages.html#Licensing-of-GNU-Packages">Licensing of 
GNU Packages</a>,
-Up:&nbsp;<a rel="up" accesskey="u" 
href="License-Notices.html#License-Notices">License Notices</a>
-<hr>
+Next: <a href="License-Notices-for-Code.html#License-Notices-for-Code" 
accesskey="n" rel="next">License Notices for Code</a>, Previous: <a 
href="Licensing-of-GNU-Packages.html#Licensing-of-GNU-Packages" accesskey="p" 
rel="previous">Licensing of GNU Packages</a>, Up: <a 
href="License-Notices.html#License-Notices" accesskey="u" rel="up">License 
Notices</a> &nbsp; [<a href="index.html#SEC_Contents" title="Table of contents" 
rel="contents">Contents</a>][<a href="Index.html#Index" title="Index" 
rel="index">Index</a>]</p>
 </div>
-
-<h4 class="subsection">6.6.2 Canonical License Sources</h4>
+<hr>
+<a name="Canonical-License-Sources-1"></a>
+<h3 class="subsection">6.6.2 Canonical License Sources</h3>
 
 <p>You can get the official versions of these files from several places. 
 You can use whichever is the most convenient for you.
+</p>
+<ul>
+<li> <a href="http://www.gnu.org/licenses/";>http://www.gnu.org/licenses/</a>.
 
-     <ul>
-<li><a href="http://www.gnu.org/licenses/";>http://www.gnu.org/licenses/</a>.
-
-     <li>The <code>gnulib</code> project on <code>savannah.gnu.org</code>, 
which you
+</li><li> The <code>gnulib</code> project on <code>savannah.gnu.org</code>, 
which you
 can access via anonymous Git or CVS.  See
 <a 
href="http://savannah.gnu.org/projects/gnulib";>http://savannah.gnu.org/projects/gnulib</a>.
 
-   </ul>
+</li></ul>
 
-   <p>The official Texinfo sources for the licenses are also available in
+<p>The official Texinfo sources for the licenses are also available in
 those same places, so you can include them in your documentation.  A
-GFDL-covered manual should include the GFDL in this way.  See <a 
href="../texinfo/GNU-Sample-Texts.html#GNU-Sample-Texts">GNU Sample Texts</a>, 
for a full example in a Texinfo
+GFDL-covered manual should include the GFDL in this way.  See <a 
href="http://www.gnu.org/software/texinfo/manual/texinfo/html_node/GNU-Sample-Texts.html#GNU-Sample-Texts";>GNU
+Sample Texts</a> in <cite>Texinfo</cite>, for a full example in a Texinfo
 manual.
+</p>
+
+<p>
 
-   </body></html>
 
+</p>
+</body>
+</html>

Index: html_node/Clean-Ups.html
===================================================================
RCS file: /web/www/www/prep/maintain/html_node/Clean-Ups.html,v
retrieving revision 1.66
retrieving revision 1.67
diff -u -b -r1.66 -r1.67
--- html_node/Clean-Ups.html    7 Sep 2011 01:31:17 -0000       1.66
+++ html_node/Clean-Ups.html    7 Sep 2011 15:00:18 -0000       1.67
@@ -1,79 +1,113 @@
-<html lang="en">
-<head>
-<title>Clean Ups - Information for Maintainers of GNU Software</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="Information for Maintainers of GNU Software">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="prev" href="Legal-Matters.html#Legal-Matters" title="Legal Matters">
-<link rel="next" href="Platforms.html#Platforms" title="Platforms">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home" 
title="Texinfo Homepage">
-<!--
-Information for maintainers of GNU software, last updated September 5, 2011.
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" 
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
+<!-- Information for maintainers of GNU software, last updated September 5, 
2011.
 
 Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
 2010, 2011 Free Software Foundation, Inc.
 
-     Permission is granted to copy, distribute and/or modify this
-     document under the terms of the GNU Free Documentation License,
-     Version 1.3 or any later version published by the Free Software
-     Foundation; with no Invariant Sections, with no Front-Cover Texts,
-     and with no Back-Cover Texts.  A copy of the license is included
-     in the section entitled ``GNU Free Documentation License''.
-   -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
-  pre.display { font-family:inherit }
-  pre.format  { font-family:inherit }
-  pre.smalldisplay { font-family:inherit; font-size:smaller }
-  pre.smallformat  { font-family:inherit; font-size:smaller }
-  pre.smallexample { font-size:smaller }
-  pre.smalllisp    { font-size:smaller }
-  span.sc    { font-variant:small-caps }
-  span.roman { font-family:serif; font-weight:normal; } 
-  span.sansserif { font-family:sans-serif; font-weight:normal; } 
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
+Texts.  A copy of the license is included in the section entitled
+"GNU Free Documentation License". -->
+<!-- Created by texi2html, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>Information for Maintainers of GNU Software: Clean Ups</title>
+
+<meta name="description" content="Information for Maintainers of GNU Software: 
Clean Ups">
+<meta name="keywords" content="Information for Maintainers of GNU Software: 
Clean Ups">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="texi2html">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="index.html#Top" rel="up" title="Top">
+<link href="Platforms.html#Platforms" rel="next" title="Platforms">
+<link href="External-Libraries.html#External-Libraries" rel="previous" 
title="External Libraries">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smalllisp {margin-left: 3.2em}
+pre.display {font-family: serif}
+pre.format {font-family: serif}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: serif; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: serif; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:pre}
+span.nolinebreak {white-space:pre}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
 </head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF" 
vlink="#800080" alink="#FF0000">
+
 <a name="Clean-Ups"></a>
+<div class="header">
 <p>
-Next:&nbsp;<a rel="next" accesskey="n" 
href="Platforms.html#Platforms">Platforms</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" 
href="Legal-Matters.html#Legal-Matters">Legal Matters</a>,
-Up:&nbsp;<a rel="up" accesskey="u" href="index.html#Top">Top</a>
-<hr>
+Next: <a href="Platforms.html#Platforms" accesskey="n" 
rel="next">Platforms</a>, Previous: <a href="Legal-Matters.html#Legal-Matters" 
accesskey="p" rel="previous">Legal Matters</a>, Up: <a href="index.html#Top" 
accesskey="u" rel="up">Top</a> &nbsp; [<a href="index.html#SEC_Contents" 
title="Table of contents" rel="contents">Contents</a>][<a 
href="Index.html#Index" title="Index" rel="index">Index</a>]</p>
 </div>
+<hr>
+<a name="Cleaning-Up-Changes"></a>
+<h1 class="chapter">7 Cleaning Up Changes</h1>
+<a name="index-contributions_002c-accepting"></a>
+<a name="index-quality-of-changes-suggested-by-others"></a>
 
-<h2 class="chapter">7 Cleaning Up Changes</h2>
-
-<p><a name="index-contributions_002c-accepting-29"></a><a 
name="index-quality-of-changes-suggested-by-others-30"></a>
-Don't feel obligated to include every change that someone asks you to
+<p>Don&rsquo;t feel obligated to include every change that someone asks you to
 include.  You must judge which changes are improvements&mdash;partly based
 on what you think the users will like, and partly based on your own
 judgment of what is better.  If you think a change is not good, you
 should reject it.
-
-   <p>If someone sends you changes which are useful, but written in an ugly
-way or hard to understand and maintain in the future, don't hesitate to
+</p>
+<p>If someone sends you changes which are useful, but written in an ugly
+way or hard to understand and maintain in the future, don&rsquo;t hesitate to
 ask per to clean up their changes before you merge them.  Since the
 amount of work we can do is limited, the more we convince others to help
 us work efficiently, the faster GNU will advance.
-
-   <p>If the contributor will not or can not make the changes clean enough,
-then it is legitimate to say &ldquo;I can't install this in its present form;
+</p>
+<p>If the contributor will not or can not make the changes clean enough,
+then it is legitimate to say &ldquo;I can&rsquo;t install this in its present 
form;
 I can only do so if you clean it up.&rdquo;  Invite per to distribute per
 changes another way, or to find other people to make them clean enough
 for you to install and maintain.
-
-   <p>The only reason to do these cleanups yourself is if (1) it is easy, less
+</p>
+<p>The only reason to do these cleanups yourself is if (1) it is easy, less
 work than telling the author what to clean up, or (2) the change is an
 important one, important enough to be worth the work of cleaning it up.
-
-   <p>The GNU Coding Standards are a good thing to send people when you ask
-them to clean up changes (see <a 
href="../standards/index.html#Top">Contents</a>).  The Emacs Lisp manual 
contains an appendix that gives
+</p>
+<p>The GNU Coding Standards are a good thing to send people when you ask
+them to clean up changes (see <a 
href="http://www.gnu.org/prep/standards/html_node/index.html#Top";>Contents</a> 
in <cite>GNU Coding
+Standards</cite>).  The Emacs Lisp manual contains an appendix that gives
 coding standards for Emacs Lisp programs; it is good to urge Lisp authors to
-read it (see <a href="../elisp/Tips.html#Tips">Tips and Conventions</a>).
+read it (see <a 
href="http://www.gnu.org/software/emacs/manual/html_node/elisp/Tips.html#Tips";>Tips
 and Conventions</a> in <cite>The GNU Emacs Lisp
+Reference Manual</cite>).
+</p>
+
+<hr>
+<div class="header">
+<p>
+Next: <a href="Platforms.html#Platforms" accesskey="n" 
rel="next">Platforms</a>, Previous: <a href="Legal-Matters.html#Legal-Matters" 
accesskey="p" rel="previous">Legal Matters</a>, Up: <a href="index.html#Top" 
accesskey="u" rel="up">Top</a> &nbsp; [<a href="index.html#SEC_Contents" 
title="Table of contents" rel="contents">Contents</a>][<a 
href="Index.html#Index" title="Index" rel="index">Index</a>]</p>
+</div>
+<p>
 
-   </body></html>
 
+</p>
+</body>
+</html>

Index: html_node/Copying-from-Other-Packages.html
===================================================================
RCS file: 
/web/www/www/prep/maintain/html_node/Copying-from-Other-Packages.html,v
retrieving revision 1.54
retrieving revision 1.55
diff -u -b -r1.54 -r1.55
--- html_node/Copying-from-Other-Packages.html  7 Sep 2011 01:31:17 -0000       
1.54
+++ html_node/Copying-from-Other-Packages.html  7 Sep 2011 15:00:24 -0000       
1.55
@@ -1,93 +1,123 @@
-<html lang="en">
-<head>
-<title>Copying from Other Packages - Information for Maintainers of GNU 
Software</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="Information for Maintainers of GNU Software">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="Legal-Matters.html#Legal-Matters" title="Legal Matters">
-<link rel="prev" href="Recording-Contributors.html#Recording-Contributors" 
title="Recording Contributors">
-<link rel="next" href="Copyright-Notices.html#Copyright-Notices" 
title="Copyright Notices">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home" 
title="Texinfo Homepage">
-<!--
-Information for maintainers of GNU software, last updated September 5, 2011.
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" 
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
+<!-- Information for maintainers of GNU software, last updated September 5, 
2011.
 
 Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
 2010, 2011 Free Software Foundation, Inc.
 
-     Permission is granted to copy, distribute and/or modify this
-     document under the terms of the GNU Free Documentation License,
-     Version 1.3 or any later version published by the Free Software
-     Foundation; with no Invariant Sections, with no Front-Cover Texts,
-     and with no Back-Cover Texts.  A copy of the license is included
-     in the section entitled ``GNU Free Documentation License''.
-   -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
-  pre.display { font-family:inherit }
-  pre.format  { font-family:inherit }
-  pre.smalldisplay { font-family:inherit; font-size:smaller }
-  pre.smallformat  { font-family:inherit; font-size:smaller }
-  pre.smallexample { font-size:smaller }
-  pre.smalllisp    { font-size:smaller }
-  span.sc    { font-variant:small-caps }
-  span.roman { font-family:serif; font-weight:normal; } 
-  span.sansserif { font-family:sans-serif; font-weight:normal; } 
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
+Texts.  A copy of the license is included in the section entitled
+"GNU Free Documentation License". -->
+<!-- Created by texi2html, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>Information for Maintainers of GNU Software: Copying from Other 
Packages</title>
+
+<meta name="description" content="Information for Maintainers of GNU Software: 
Copying from Other Packages">
+<meta name="keywords" content="Information for Maintainers of GNU Software: 
Copying from Other Packages">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="texi2html">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Legal-Matters.html#Legal-Matters" rel="up" title="Legal Matters">
+<link href="Copyright-Notices.html#Copyright-Notices" rel="next" 
title="Copyright Notices">
+<link href="Recording-Contributors.html#Recording-Contributors" rel="previous" 
title="Recording Contributors">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smalllisp {margin-left: 3.2em}
+pre.display {font-family: serif}
+pre.format {font-family: serif}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: serif; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: serif; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:pre}
+span.nolinebreak {white-space:pre}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
 </head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF" 
vlink="#800080" alink="#FF0000">
+
 <a name="Copying-from-Other-Packages"></a>
+<div class="header">
 <p>
-Next:&nbsp;<a rel="next" accesskey="n" 
href="Copyright-Notices.html#Copyright-Notices">Copyright Notices</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" 
href="Recording-Contributors.html#Recording-Contributors">Recording 
Contributors</a>,
-Up:&nbsp;<a rel="up" accesskey="u" 
href="Legal-Matters.html#Legal-Matters">Legal Matters</a>
-<hr>
+Next: <a href="Copyright-Notices.html#Copyright-Notices" accesskey="n" 
rel="next">Copyright Notices</a>, Previous: <a 
href="Recording-Contributors.html#Recording-Contributors" accesskey="p" 
rel="previous">Recording Contributors</a>, Up: <a 
href="Legal-Matters.html#Legal-Matters" accesskey="u" rel="up">Legal 
Matters</a> &nbsp; [<a href="index.html#SEC_Contents" title="Table of contents" 
rel="contents">Contents</a>][<a href="Index.html#Index" title="Index" 
rel="index">Index</a>]</p>
 </div>
-
-<h3 class="section">6.4 Copying from Other Packages</h3>
+<hr>
+<a name="Copying-from-Other-Packages-1"></a>
+<h2 class="section">6.4 Copying from Other Packages</h2>
 
 <p>When you copy legally significant code from another free software
 package with a GPL-compatible license, you should look in the
-package's records to find out the authors of the part you are copying,
+package&rsquo;s records to find out the authors of the part you are copying,
 and list them as the contributors of the code that you copied.  If all
 you did was copy it, not write it, then for copyright purposes you are
 <em>not</em> one of the contributors of <em>this</em> code.
-
-   <p>Especially when code has been released into the public domain, authors
+</p>
+<p>Especially when code has been released into the public domain, authors
 sometimes fail to write a license statement in each file.  In this
 case, please first be sure that all the authors of the code have
 disclaimed copyright interest.  Then, when copying the new files into
 your project, add a brief note at the beginning of the files recording
 the authors, the public domain status, and anything else relevant.
-
-   <p>On the other hand, when merging some public domain code into an
+</p>
+<p>On the other hand, when merging some public domain code into an
 existing file covered by the GPL (or LGPL or other free software
 license), there is no reason to indicate the pieces which are public
 domain.  The notice saying that the whole file is under the GPL (or
 other license) is legally sufficient.
-
-   <p>Using code that is released under a GPL-compatible free license,
+</p>
+<p>Using code that is released under a GPL-compatible free license,
 rather than being in the public domain, may require preserving
 copyright notices or other steps.  Of course, you should do what is
 needed.
-
-   <p>If you are maintaining an FSF-copyrighted package, please verify we
+</p>
+<p>If you are maintaining an FSF-copyrighted package, please verify we
 have papers for the code you are copying, <em>before</em> copying it. 
 If you are copying from another FSF-copyrighted package, then we
-presumably have papers for that package's own code, but you must check
+presumably have papers for that package&rsquo;s own code, but you must check
 whether the code you are copying is part of an external library; if
-that is the case, we don't have papers for it, so you should not copy
-it.  It can't hurt in any case to double-check with the developer of
+that is the case, we don&rsquo;t have papers for it, so you should not copy
+it.  It can&rsquo;t hurt in any case to double-check with the developer of
 that package.
-
-   <p>When you are copying code for which we do not already have papers, you
+</p>
+<p>When you are copying code for which we do not already have papers, you
 need to get papers for it.  It may be difficult to get the papers if
 the code was not written as a contribution to your package, but that
-doesn't mean it is ok to do without them.  If you cannot get papers
+doesn&rsquo;t mean it is ok to do without them.  If you cannot get papers
 for the code, you can only use it as an external library
 (see <a href="External-Libraries.html#External-Libraries">External 
Libraries</a>).
+</p>
+
+<hr>
+<div class="header">
+<p>
+Next: <a href="Copyright-Notices.html#Copyright-Notices" accesskey="n" 
rel="next">Copyright Notices</a>, Previous: <a 
href="Recording-Contributors.html#Recording-Contributors" accesskey="p" 
rel="previous">Recording Contributors</a>, Up: <a 
href="Legal-Matters.html#Legal-Matters" accesskey="u" rel="up">Legal 
Matters</a> &nbsp; [<a href="index.html#SEC_Contents" title="Table of contents" 
rel="contents">Contents</a>][<a href="Index.html#Index" title="Index" 
rel="index">Index</a>]</p>
+</div>
+<p>
 
-   </body></html>
 
+</p>
+</body>
+</html>

Index: html_node/Copyright-Notices.html
===================================================================
RCS file: /web/www/www/prep/maintain/html_node/Copyright-Notices.html,v
retrieving revision 1.66
retrieving revision 1.67
diff -u -b -r1.66 -r1.67
--- html_node/Copyright-Notices.html    7 Sep 2011 01:31:17 -0000       1.66
+++ html_node/Copyright-Notices.html    7 Sep 2011 15:00:24 -0000       1.67
@@ -1,55 +1,75 @@
-<html lang="en">
-<head>
-<title>Copyright Notices - Information for Maintainers of GNU Software</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="Information for Maintainers of GNU Software">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="Legal-Matters.html#Legal-Matters" title="Legal Matters">
-<link rel="prev" 
href="Copying-from-Other-Packages.html#Copying-from-Other-Packages" 
title="Copying from Other Packages">
-<link rel="next" href="License-Notices.html#License-Notices" title="License 
Notices">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home" 
title="Texinfo Homepage">
-<!--
-Information for maintainers of GNU software, last updated September 5, 2011.
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" 
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
+<!-- Information for maintainers of GNU software, last updated September 5, 
2011.
 
 Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
 2010, 2011 Free Software Foundation, Inc.
 
-     Permission is granted to copy, distribute and/or modify this
-     document under the terms of the GNU Free Documentation License,
-     Version 1.3 or any later version published by the Free Software
-     Foundation; with no Invariant Sections, with no Front-Cover Texts,
-     and with no Back-Cover Texts.  A copy of the license is included
-     in the section entitled ``GNU Free Documentation License''.
-   -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
-  pre.display { font-family:inherit }
-  pre.format  { font-family:inherit }
-  pre.smalldisplay { font-family:inherit; font-size:smaller }
-  pre.smallformat  { font-family:inherit; font-size:smaller }
-  pre.smallexample { font-size:smaller }
-  pre.smalllisp    { font-size:smaller }
-  span.sc    { font-variant:small-caps }
-  span.roman { font-family:serif; font-weight:normal; } 
-  span.sansserif { font-family:sans-serif; font-weight:normal; } 
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
+Texts.  A copy of the license is included in the section entitled
+"GNU Free Documentation License". -->
+<!-- Created by texi2html, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>Information for Maintainers of GNU Software: Copyright Notices</title>
+
+<meta name="description" content="Information for Maintainers of GNU Software: 
Copyright Notices">
+<meta name="keywords" content="Information for Maintainers of GNU Software: 
Copyright Notices">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="texi2html">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Legal-Matters.html#Legal-Matters" rel="up" title="Legal Matters">
+<link href="License-Notices.html#License-Notices" rel="next" title="License 
Notices">
+<link href="Copying-from-Other-Packages.html#Copying-from-Other-Packages" 
rel="previous" title="Copying from Other Packages">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smalllisp {margin-left: 3.2em}
+pre.display {font-family: serif}
+pre.format {font-family: serif}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: serif; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: serif; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:pre}
+span.nolinebreak {white-space:pre}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
 </head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF" 
vlink="#800080" alink="#FF0000">
+
 <a name="Copyright-Notices"></a>
+<div class="header">
 <p>
-Next:&nbsp;<a rel="next" accesskey="n" 
href="License-Notices.html#License-Notices">License Notices</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" 
href="Copying-from-Other-Packages.html#Copying-from-Other-Packages">Copying 
from Other Packages</a>,
-Up:&nbsp;<a rel="up" accesskey="u" 
href="Legal-Matters.html#Legal-Matters">Legal Matters</a>
-<hr>
+Next: <a href="License-Notices.html#License-Notices" accesskey="n" 
rel="next">License Notices</a>, Previous: <a 
href="Copying-from-Other-Packages.html#Copying-from-Other-Packages" 
accesskey="p" rel="previous">Copying from Other Packages</a>, Up: <a 
href="Legal-Matters.html#Legal-Matters" accesskey="u" rel="up">Legal 
Matters</a> &nbsp; [<a href="index.html#SEC_Contents" title="Table of contents" 
rel="contents">Contents</a>][<a href="Index.html#Index" title="Index" 
rel="index">Index</a>]</p>
 </div>
+<hr>
+<a name="Copyright-Notices-1"></a>
+<h2 class="section">6.5 Copyright Notices</h2>
+<a name="index-copyright-notices-in-program-files"></a>
 
-<h3 class="section">6.5 Copyright Notices</h3>
-
-<p><a name="index-copyright-notices-in-program-files-27"></a>
-You should maintain a proper copyright notice and a license
+<p>You should maintain a proper copyright notice and a license
 notice in each nontrivial file in the package.  (Any file more than ten
 lines long is nontrivial for this purpose.)  This includes header files
 and interface definitions for
@@ -57,96 +77,108 @@
 files.  If a file has been explicitly placed in the public domain, then
 instead of a copyright notice, it should have a notice saying explicitly
 that it is in the public domain.
-
-   <p>Even image files and sound files should contain copyright notices and
+</p>
+<p>Even image files and sound files should contain copyright notices and
 license notices, if their format permits.  Some formats do not have
 room for textual annotations; for these files, state the copyright and
-copying permissions in a <samp><span class="file">README</span></samp> file in 
the same directory.
-
-   <p>Change log files should have a copyright notice and license notice at
+copying permissions in a &lsquo;<tt>README</tt>&rsquo; file in the same 
directory.
+</p>
+<p>Change log files should have a copyright notice and license notice at
 the end, since new material is added at the beginning but the end
 remains the end.
-
-   <p>When a file is automatically generated from some other file in the
+</p>
+<p>When a file is automatically generated from some other file in the
 distribution, it is useful for the automatic procedure to copy the
 copyright notice and permission notice of the file it is generated
 from, if possible.  Alternatively, put a notice at the beginning saying
 which file it is generated from.
+</p>
+<p>A copyright notice looks like this:
+</p>
+<div class="example">
+<pre class="example">Copyright (C) <var>year1</var>, <var>year2</var>, 
<var>year3</var> <var>copyright-holder</var>
+</pre></div>
 
-   <p>A copyright notice looks like this:
-
-<pre class="example">     Copyright (C) <var>year1</var>, <var>year2</var>, 
<var>year3</var> <var>copyright-holder</var>
-</pre>
-   <p>The word &lsquo;<samp><span class="samp">Copyright</span></samp>&rsquo; 
must always be in English, by international
+<p>The word &lsquo;<samp>Copyright</samp>&rsquo; must always be in English, by 
international
 convention.
-
-   <p>The <var>copyright-holder</var> may be the Free Software Foundation, 
Inc., or
+</p>
+<p>The <var>copyright-holder</var> may be the Free Software Foundation, Inc., 
or
 someone else; you should know who is the copyright holder for your
 package.
-
-   <p>Replace the &lsquo;<samp><span class="samp">(C)</span></samp>&rsquo; 
with a C-in-a-circle symbol if it is available. 
-For example, use &lsquo;<samp><span 
class="samp">@copyright{}</span></samp>&rsquo; in a Texinfo file.  However,
-stick with parenthesized &lsquo;<samp><span 
class="samp">C</span></samp>&rsquo; unless you know that C-in-a-circle
-will work.  For example, a program's standard <samp><span 
class="option">--version</span></samp>
-message should use parenthesized &lsquo;<samp><span 
class="samp">C</span></samp>&rsquo; by default, though message
+</p>
+<p>Replace the &lsquo;<samp>(C)</samp>&rsquo; with a C-in-a-circle symbol if 
it is available.
+For example, use &lsquo;<samp>@copyright{}</samp>&rsquo; in a Texinfo file.  
However,
+stick with parenthesized &lsquo;<samp>C</samp>&rsquo; unless you know that 
C-in-a-circle
+will work.  For example, a program&rsquo;s standard 
&lsquo;<samp>--version</samp>&rsquo;
+message should use parenthesized &lsquo;<samp>C</samp>&rsquo; by default, 
though message
 translations may use C-in-a-circle in locales where that symbol is
-known to work.  Alternatively, the &lsquo;<samp><span 
class="samp">(C)</span></samp>&rsquo; or C-in-a-circle can be
-omitted entirely; the word &lsquo;<samp><span 
class="samp">Copyright</span></samp>&rsquo; suffices.
-
-   <p>To update the list of year numbers, add each year in which you have
-made nontrivial changes to the package.  (Here we assume you're using
+known to work.  Alternatively, the &lsquo;<samp>(C)</samp>&rsquo; or 
C-in-a-circle can be
+omitted entirely; the word &lsquo;<samp>Copyright</samp>&rsquo; suffices.
+</p>
+<p>To update the list of year numbers, add each year in which you have
+made nontrivial changes to the package.  (Here we assume you&rsquo;re using
 a publicly accessible revision control server, so that every revision
 installed is also immediately and automatically published.)  When you
 add the new year, it is not required to keep track of which files have
 seen significant changes in the new year and which have not.  It is
 recommended and simpler to add the new year to all files in the
 package, and be done with it for the rest of the year.
-
-   <p>Don't delete old year numbers, though; they are significant since they
+</p>
+<p>Don&rsquo;t delete old year numbers, though; they are significant since they
 indicate when older versions might theoretically go into the public
-domain, if the movie companies don't continue buying laws to further
+domain, if the movie companies don&rsquo;t continue buying laws to further
 extend copyright.  If you copy a file into the package from some other
 program, keep the copyright years that come with the file.
-
-   <p>You can use a range (&lsquo;<samp><span 
class="samp">2008-2010</span></samp>&rsquo;) instead of listing individual
-years (&lsquo;<samp><span class="samp">2008, 2009, 2010</span></samp>&rsquo;) 
if and only if: 1)&nbsp;every year in
+</p>
+<p>You can use a range (&lsquo;<samp>2008-2010</samp>&rsquo;) instead of 
listing individual
+years (&lsquo;<samp>2008, 2009, 2010</samp>&rsquo;) if and only if: 
1)&nbsp;every year in
 the range, inclusive, really is a &ldquo;copyrightable&rdquo; year that would 
be
 listed individually; <em>and</em> 2)&nbsp;you make an explicit statement
-in a <samp><span class="file">README</span></samp> file about this usage.
-
-   <p>For files which are regularly copied from another project (such as
-&lsquo;<samp><span class="samp">gnulib</span></samp>&rsquo;), leave the 
copyright notice as it is in the original.
-
-   <p>The copyright statement may be split across multiple lines, both in
+in a &lsquo;<tt>README</tt>&rsquo; file about this usage.
+</p>
+<p>For files which are regularly copied from another project (such as
+&lsquo;<samp>gnulib</samp>&rsquo;), leave the copyright notice as it is in the 
original.
+</p>
+<p>The copyright statement may be split across multiple lines, both in
 source files and in any generated output.  This often happens for
 files with a long history, having many different years of
 publication.
-
-   <p>For an FSF-copyrighted package, if you have followed the procedures to
+</p>
+<p>For an FSF-copyrighted package, if you have followed the procedures to
 obtain legal papers, each file should have just one copyright holder:
-the Free Software Foundation, Inc.  You should edit the file's
+the Free Software Foundation, Inc.  You should edit the file&rsquo;s
 copyright notice to list that name and only that name.
-
-   <p>But if contributors are not all assigning their copyrights to a single
+</p>
+<p>But if contributors are not all assigning their copyrights to a single
 copyright holder, it can easily happen that one file has several
 copyright holders.  Each contributor of nontrivial text is a copyright
 holder.
-
-   <p>In that case, you should always include a copyright notice in the name
+</p>
+<p>In that case, you should always include a copyright notice in the name
 of main copyright holder of the file.  You can also include copyright
 notices for other copyright holders as well, and this is a good idea
 for those who have contributed a large amount and for those who
 specifically ask for notices in their names.  (Sometimes the license
 on code that you copy in may require preserving certain copyright
-notices.)  But you don't have to include a notice for everyone who
+notices.)  But you don&rsquo;t have to include a notice for everyone who
 contributed to the file (which would be rather inconvenient).
-
-   <p>Sometimes a program has an overall copyright notice that refers to the
-whole program.  It might be in the <samp><span 
class="file">README</span></samp> file, or it might be
+</p>
+<p>Sometimes a program has an overall copyright notice that refers to the
+whole program.  It might be in the &lsquo;<tt>README</tt>&rsquo; file, or it 
might be
 displayed when the program starts up.  This copyright notice should
 mention the year of completion of the most recent major version; it
 can mention years of completion of previous major versions, but that
 is optional.
+</p>
+
+<hr>
+<div class="header">
+<p>
+Next: <a href="License-Notices.html#License-Notices" accesskey="n" 
rel="next">License Notices</a>, Previous: <a 
href="Copying-from-Other-Packages.html#Copying-from-Other-Packages" 
accesskey="p" rel="previous">Copying from Other Packages</a>, Up: <a 
href="Legal-Matters.html#Legal-Matters" accesskey="u" rel="up">Legal 
Matters</a> &nbsp; [<a href="index.html#SEC_Contents" title="Table of contents" 
rel="contents">Contents</a>][<a href="Index.html#Index" title="Index" 
rel="index">Index</a>]</p>
+</div>
+<p>
 
-   </body></html>
 
+</p>
+</body>
+</html>

Index: html_node/Copyright-Papers.html
===================================================================
RCS file: /web/www/www/prep/maintain/html_node/Copyright-Papers.html,v
retrieving revision 1.68
retrieving revision 1.69
diff -u -b -r1.68 -r1.69
--- html_node/Copyright-Papers.html     7 Sep 2011 01:31:17 -0000       1.68
+++ html_node/Copyright-Papers.html     7 Sep 2011 15:00:25 -0000       1.69
@@ -1,202 +1,235 @@
-<html lang="en">
-<head>
-<title>Copyright Papers - Information for Maintainers of GNU Software</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="Information for Maintainers of GNU Software">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="Legal-Matters.html#Legal-Matters" title="Legal Matters">
-<link rel="next" href="Legally-Significant.html#Legally-Significant" 
title="Legally Significant">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home" 
title="Texinfo Homepage">
-<!--
-Information for maintainers of GNU software, last updated September 5, 2011.
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" 
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
+<!-- Information for maintainers of GNU software, last updated September 5, 
2011.
 
 Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
 2010, 2011 Free Software Foundation, Inc.
 
-     Permission is granted to copy, distribute and/or modify this
-     document under the terms of the GNU Free Documentation License,
-     Version 1.3 or any later version published by the Free Software
-     Foundation; with no Invariant Sections, with no Front-Cover Texts,
-     and with no Back-Cover Texts.  A copy of the license is included
-     in the section entitled ``GNU Free Documentation License''.
-   -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
-  pre.display { font-family:inherit }
-  pre.format  { font-family:inherit }
-  pre.smalldisplay { font-family:inherit; font-size:smaller }
-  pre.smallformat  { font-family:inherit; font-size:smaller }
-  pre.smallexample { font-size:smaller }
-  pre.smalllisp    { font-size:smaller }
-  span.sc    { font-variant:small-caps }
-  span.roman { font-family:serif; font-weight:normal; } 
-  span.sansserif { font-family:sans-serif; font-weight:normal; } 
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
+Texts.  A copy of the license is included in the section entitled
+"GNU Free Documentation License". -->
+<!-- Created by texi2html, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>Information for Maintainers of GNU Software: Copyright Papers</title>
+
+<meta name="description" content="Information for Maintainers of GNU Software: 
Copyright Papers">
+<meta name="keywords" content="Information for Maintainers of GNU Software: 
Copyright Papers">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="texi2html">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Legal-Matters.html#Legal-Matters" rel="up" title="Legal Matters">
+<link href="Legally-Significant.html#Legally-Significant" rel="next" 
title="Legally Significant">
+<link href="Legal-Matters.html#Legal-Matters" rel="previous" title="Legal 
Matters">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smalllisp {margin-left: 3.2em}
+pre.display {font-family: serif}
+pre.format {font-family: serif}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: serif; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: serif; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:pre}
+span.nolinebreak {white-space:pre}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
 </head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF" 
vlink="#800080" alink="#FF0000">
+
 <a name="Copyright-Papers"></a>
+<div class="header">
 <p>
-Next:&nbsp;<a rel="next" accesskey="n" 
href="Legally-Significant.html#Legally-Significant">Legally Significant</a>,
-Up:&nbsp;<a rel="up" accesskey="u" 
href="Legal-Matters.html#Legal-Matters">Legal Matters</a>
-<hr>
+Next: <a href="Legally-Significant.html#Legally-Significant" accesskey="n" 
rel="next">Legally Significant</a>, Up: <a 
href="Legal-Matters.html#Legal-Matters" accesskey="u" rel="up">Legal 
Matters</a> &nbsp; [<a href="index.html#SEC_Contents" title="Table of contents" 
rel="contents">Contents</a>][<a href="Index.html#Index" title="Index" 
rel="index">Index</a>]</p>
 </div>
+<hr>
+<a name="Copyright-Papers-1"></a>
+<h2 class="section">6.1 Copyright Papers</h2>
+<a name="index-copyright-papers"></a>
 
-<h3 class="section">6.1 Copyright Papers</h3>
-
-<p><a name="index-copyright-papers-21"></a>
-If you maintain an FSF-copyrighted package
+<p>If you maintain an FSF-copyrighted package
 certain legal procedures are required when incorporating legally significant
 changes written by other people.  This ensures that the FSF has the
 legal right to distribute the package, and the standing to defend its
 GPL-covered status in court if necessary.
-
-   <p><strong>Before</strong> incorporating significant changes, make sure 
that the
+</p>
+<p><strong>Before</strong> incorporating significant changes, make sure that 
the
 person who wrote the changes has signed copyright papers and that the
 Free Software Foundation has received and signed them.  We may also need
-an employer's disclaimer from the person's employer.
-
-   <p><a name="index-data-base-of-GNU-copyright-assignments-22"></a>To check 
whether papers have been received, look in
-<samp><span class="file">/gd/gnuorg/copyright.list</span></samp>.  If you 
can't look there directly,
+an employer&rsquo;s disclaimer from the person&rsquo;s employer.
+</p>
+<a name="index-data-base-of-GNU-copyright-assignments"></a>
+<p>To check whether papers have been received, look in
+&lsquo;<tt>/gd/gnuorg/copyright.list</tt>&rsquo;.  If you can&rsquo;t look 
there directly,
 <a href="mailto:address@hidden";>address@hidden</a> can check for you.  Our 
clerk can also
 check for papers that are waiting to be entered and inform you when
 expected papers arrive.
-
-   <p><a 
name="index-g_t_0040file_007b_002fgd_002fgnuorg_007d-directory-23"></a><!-- 
This paragraph intentionally duplicates information given -->
-<!-- near the beginning of the file-to make sure people don't miss it. -->
-The directory <samp><span class="file">/gd/gnuorg</span></samp> mentioned 
throughout this document is
+</p>
+<a name="index-_002fgd_002fgnuorg-directory"></a>
+<p>The directory &lsquo;<tt>/gd/gnuorg</tt>&rsquo; mentioned throughout this 
document is
 available on the general GNU server, currently
 <code>fencepost.gnu.org</code>.  If you are the maintainer of a GNU package,
-you should have an account there.  If you don't have one already,
+you should have an account there.  If you don&rsquo;t have one already,
 <a 
href="http://www.gnu.org/software/README.accounts.html";>http://www.gnu.org/software/README.accounts.html</a>.
  You can also
 ask for accounts for people who significantly help you in working on
 the package.
-
-   <p>In order for the contributor to know person should sign papers, you need
-to ask per for the necessary papers.  If you don't know per well, and you
-don't know that person is used to our ways of handling copyright papers,
+</p>
+<p>In order for the contributor to know person should sign papers, you need
+to ask per for the necessary papers.  If you don&rsquo;t know per well, and you
+don&rsquo;t know that person is used to our ways of handling copyright papers,
 then it might be a good idea to raise the subject with a message like
 this:
-
-   <blockquote>
-Would you be willing to assign the copyright to the Free Software
+</p>
+<blockquote>
+<p>Would you be willing to assign the copyright to the Free Software
 Foundation, so that we could install it in <var>package</var>? 
-</blockquote>
+</p></blockquote>
 
-<p class="noindent">or
-
-   <blockquote>
-Would you be willing to sign a copyright disclaimer to put this change
+<p>or
+</p>
+<blockquote>
+<p>Would you be willing to sign a copyright disclaimer to put this change
 in the public domain, so that we can install it in <var>package</var>? 
-</blockquote>
+</p></blockquote>
 
-   <p>If the contributor then wants more information, you can send per the file
-<samp><span class="file">/gd/gnuorg/conditions.text</span></samp>, which 
explains per options (assign
+<p>If the contributor then wants more information, you can send per the file
+&lsquo;<tt>/gd/gnuorg/conditions.text</tt>&rsquo;, which explains per options 
(assign
 vs. disclaim) and their consequences.
-
-   <p>Once the conversation is under way and the contributor is ready for
+</p>
+<p>Once the conversation is under way and the contributor is ready for
 more details, you should send one of the templates that are found in
-the directory <samp><span class="file">/gd/gnuorg/Copyright/</span></samp>; 
they are also available
-from the <samp><span class="file">doc/Copyright/</span></samp> directory of 
the <code>gnulib</code> project
+the directory &lsquo;<tt>/gd/gnuorg/Copyright/</tt>&rsquo;; they are also 
available
+from the &lsquo;<tt>doc/Copyright/</tt>&rsquo; directory of the 
<code>gnulib</code> project
 at <a 
href="http://savannah.gnu.org/projects/gnulib";>http://savannah.gnu.org/projects/gnulib</a>.
  This section
 explains which templates you should use in which circumstances. 
-<strong>Please don't use any of the templates except for those listed
-here, and please don't change the wording.</strong>
-
-   <p>Once the conversation is under way, you can send the contributor the
+<strong>Please don&rsquo;t use any of the templates except for those listed
+here, and please don&rsquo;t change the wording.</strong>
+</p>
+<p>Once the conversation is under way, you can send the contributor the
 precise wording and instructions by email.  Before you do this, make
 sure to get the current version of the template you will use!  We change
-these templates occasionally&mdash;don't keep using an old version.
-
-   <p>For large changes, ask the contributor for an assignment.  Send per a
-copy of the file <samp><span 
class="file">request-assign.changes</span></samp>.  (Like all the
-&lsquo;<samp><span class="samp">request-</span></samp>&rsquo; files, it is in 
<samp><span class="file">/gd/gnuorg/Copyright</span></samp> and in
+these templates occasionally&mdash;don&rsquo;t keep using an old version.
+</p>
+<p>For large changes, ask the contributor for an assignment.  Send per a
+copy of the file &lsquo;<tt>request-assign.changes</tt>&rsquo;.  (Like all the
+&lsquo;<samp>request-</samp>&rsquo; files, it is in 
&lsquo;<tt>/gd/gnuorg/Copyright</tt>&rsquo; and in
 <code>gnulib</code>.)
-
-   <p>For medium to small changes, request a personal disclaimer by sending
-per the file <samp><span class="file">request-disclaim.changes</span></samp>.
-
-   <p>If the contributor is likely to keep making changes, person might want
+</p>
+<p>For medium to small changes, request a personal disclaimer by sending
+per the file &lsquo;<tt>request-disclaim.changes</tt>&rsquo;.
+</p>
+<p>If the contributor is likely to keep making changes, person might want
 to sign an assignment for all per future changes to the program.  So it
 is useful to offer per that alternative.  If person wants to do it that
-way, send per the <samp><span class="file">request-assign.future</span></samp>.
-
-   <p>When you send a <samp><span class="file">request-</span></samp> file, 
you don't need to fill in anything
+way, send per the &lsquo;<tt>request-assign.future</tt>&rsquo;.
+</p>
+<p>When you send a &lsquo;<tt>request-</tt>&rsquo; file, you don&rsquo;t need 
to fill in anything
 before sending it.  Just send the file verbatim to the contributor.  The
 file gives per instructions for how to ask the FSF to mail per the
-papers to sign.  The <samp><span class="file">request-</span></samp> file also 
raises the issue of
-getting an employer's disclaimer from the contributor's employer.
-
-   <p>When the contributor emails the form to the FSF, the FSF sends per
+papers to sign.  The &lsquo;<tt>request-</tt>&rsquo; file also raises the 
issue of
+getting an employer&rsquo;s disclaimer from the contributor&rsquo;s employer.
+</p>
+<p>When the contributor emails the form to the FSF, the FSF sends per
 papers to sign.  If person signs them right away, the whole process
 takes a couple of weeks&mdash;mostly waiting for letters to go back and
 forth.
-
-   <p>For less common cases, we have template files you should send to the
+</p>
+<p>For less common cases, we have template files you should send to the
 contributor.  Be sure to fill in the name of the person and the name
-of the program in these templates, where it says &lsquo;<samp><span 
class="samp">NAME OF PERSON</span></samp>&rsquo;
-and &lsquo;<samp><span class="samp">NAME OF PROGRAM</span></samp>&rsquo;, 
before sending; otherwise person might
+of the program in these templates, where it says &lsquo;<samp>NAME OF 
PERSON</samp>&rsquo;
+and &lsquo;<samp>NAME OF PROGRAM</samp>&rsquo;, before sending; otherwise 
person might
 sign without noticing them, and the papers would be useless.  Note
 that in some templates there is more than one place to put the name of
 the program or the name of the person; be sure to change all of them. 
-All the templates raise the issue of an employer's disclaimer as well.
-
-   <p><a name="index-legal-papers-for-changes-in-manuals-24"></a>You do not 
need to ask for separate papers for a manual that is
+All the templates raise the issue of an employer&rsquo;s disclaimer as well.
+</p>
+<a name="index-legal-papers-for-changes-in-manuals"></a>
+<p>You do not need to ask for separate papers for a manual that is
 distributed only in the software package it describes.  But if we
 sometimes distribute the manual separately (for instance, if we publish
 it as a book), then we need separate legal papers for changes in the
 manual.  For smaller changes, use
-<samp><span class="file">disclaim.changes.manual</span></samp>; for larger 
ones, use
-<samp><span class="file">assign.changes.manual</span></samp>.  To cover both 
past and future
-changes to a manual, you can use <samp><span 
class="file">assign.future.manual</span></samp>. 
-For a translation of a manual, use <samp><span 
class="file">assign.translation.manual</span></samp>.
-
-   <p>For translations of program strings (as used by GNU Gettext, for
-example; see <a 
href="../standards/Internationalization.html#Internationalization">Internationalization</a>),
 use <samp><span class="file">disclaim.translation</span></samp>.  If you make 
use of the
+&lsquo;<tt>disclaim.changes.manual</tt>&rsquo;; for larger ones, use
+&lsquo;<tt>assign.changes.manual</tt>&rsquo;.  To cover both past and future
+changes to a manual, you can use &lsquo;<tt>assign.future.manual</tt>&rsquo;.
+For a translation of a manual, use 
&lsquo;<tt>assign.translation.manual</tt>&rsquo;.
+</p>
+<p>For translations of program strings (as used by GNU Gettext, for
+example; see <a 
href="http://www.gnu.org/prep/standards/html_node/Internationalization.html#Internationalization";>Internationalization</a>
 in <cite>GNU Coding
+Standards</cite>), use &lsquo;<tt>disclaim.translation</tt>&rsquo;.  If you 
make use of the
 Translation Project (<a 
href="http://translationproject.org";>http://translationproject.org</a>) 
facilities,
 please check with the TP coordinators that they have sent the
-contributor the papers; if they haven't, then you should send the
+contributor the papers; if they haven&rsquo;t, then you should send the
 papers.  In any case, you should wait for the confirmation from the
 FSF that the signed papers have been received and accepted before
-integrating the new contributor's material, as usual.
-
-   <p>If a contributor is reluctant to sign an assignment for a large change,
+integrating the new contributor&rsquo;s material, as usual.
+</p>
+<p>If a contributor is reluctant to sign an assignment for a large change,
 and is willing to sign a disclaimer instead, that is acceptable, so you
 should offer this alternative if it helps you reach agreement.  We
 prefer an assignment for a larger change, so that we can enforce the GNU
 GPL for the new text, but a disclaimer is enough to let us use the text.
-
-   <p>If you maintain a collection of programs, occasionally someone will
+</p>
+<p>If you maintain a collection of programs, occasionally someone will
 contribute an entire separate program or manual that should be added to
 the collection.  Then you can use the files
-<samp><span class="file">request-assign.program</span></samp>, <samp><span 
class="file">disclaim.program</span></samp>,
-<samp><span class="file">assign.manual</span></samp>, and <samp><span 
class="file">disclaim.manual</span></samp>.  We very much prefer
+&lsquo;<tt>request-assign.program</tt>&rsquo;, 
&lsquo;<tt>disclaim.program</tt>&rsquo;,
+&lsquo;<tt>assign.manual</tt>&rsquo;, and 
&lsquo;<tt>disclaim.manual</tt>&rsquo;.  We very much prefer
 an assignment for a new separate program or manual, unless it is quite
 small, but a disclaimer is acceptable if the contributor insists on
 handling the matter that way.
-
-   <p>If a contributor wants the FSF to publish only a pseudonym, that is
+</p>
+<p>If a contributor wants the FSF to publish only a pseudonym, that is
 ok.  The contributor should say this, and state the desired pseudonym,
-when answering the <samp><span class="file">request-</span></samp> form.  The 
actual legal papers will
+when answering the &lsquo;<tt>request-</tt>&rsquo; form.  The actual legal 
papers will
 use the real name, but the FSF will publish only the pseudonym.  When
 using one of the other forms, fill in the real name but ask the
 contributor to discuss the use of a pseudonym with
 <a href="mailto:address@hidden";>address@hidden</a> before sending back the 
signed form.
-
-   <p><strong>Although there are other templates besides the ones listed here,
+</p>
+<p><strong>Although there are other templates besides the ones listed here,
 they are for special circumstances; please do not use them without
 getting advice from <a 
href="mailto:address@hidden";>address@hidden</a>.</strong>
-
-   <p>If you are not sure what to do, then please ask <a 
href="mailto:address@hidden";>address@hidden</a> for
+</p>
+<p>If you are not sure what to do, then please ask <a 
href="mailto:address@hidden";>address@hidden</a> for
 advice; if the contributor asks you questions about the meaning and
-consequences of the legal papers, and you don't know the answers, you
+consequences of the legal papers, and you don&rsquo;t know the answers, you
 can forward them to <a href="mailto:address@hidden";>address@hidden</a> and we 
will answer.
-
-   <p><strong>Please do not try changing the wording of a template yourself. 
+</p>
+<p><strong>Please do not try changing the wording of a template yourself.
 If you think a change is needed, please talk with <a 
href="mailto:address@hidden";>address@hidden</a>,
 and we will work with a lawyer to decide what to do.</strong>
+</p>
+<hr>
+<div class="header">
+<p>
+Next: <a href="Legally-Significant.html#Legally-Significant" accesskey="n" 
rel="next">Legally Significant</a>, Up: <a 
href="Legal-Matters.html#Legal-Matters" accesskey="u" rel="up">Legal 
Matters</a> &nbsp; [<a href="index.html#SEC_Contents" title="Table of contents" 
rel="contents">Contents</a>][<a href="Index.html#Index" title="Index" 
rel="index">Index</a>]</p>
+</div>
+<p>
 
-   </body></html>
 
+</p>
+</body>
+</html>

Index: html_node/Creating-Mailing-Lists.html
===================================================================
RCS file: /web/www/www/prep/maintain/html_node/Creating-Mailing-Lists.html,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -b -r1.17 -r1.18
--- html_node/Creating-Mailing-Lists.html       7 Sep 2011 01:31:17 -0000       
1.17
+++ html_node/Creating-Mailing-Lists.html       7 Sep 2011 15:00:26 -0000       
1.18
@@ -1,86 +1,120 @@
-<html lang="en">
-<head>
-<title>Creating Mailing Lists - Information for Maintainers of GNU 
Software</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="Information for Maintainers of GNU Software">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="Mail.html#Mail" title="Mail">
-<link rel="prev" href="Standard-Mailing-Lists.html#Standard-Mailing-Lists" 
title="Standard Mailing Lists">
-<link rel="next" href="Replying-to-Mail.html#Replying-to-Mail" title="Replying 
to Mail">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home" 
title="Texinfo Homepage">
-<!--
-Information for maintainers of GNU software, last updated September 5, 2011.
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" 
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
+<!-- Information for maintainers of GNU software, last updated September 5, 
2011.
 
 Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
 2010, 2011 Free Software Foundation, Inc.
 
-     Permission is granted to copy, distribute and/or modify this
-     document under the terms of the GNU Free Documentation License,
-     Version 1.3 or any later version published by the Free Software
-     Foundation; with no Invariant Sections, with no Front-Cover Texts,
-     and with no Back-Cover Texts.  A copy of the license is included
-     in the section entitled ``GNU Free Documentation License''.
-   -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
-  pre.display { font-family:inherit }
-  pre.format  { font-family:inherit }
-  pre.smalldisplay { font-family:inherit; font-size:smaller }
-  pre.smallformat  { font-family:inherit; font-size:smaller }
-  pre.smallexample { font-size:smaller }
-  pre.smalllisp    { font-size:smaller }
-  span.sc    { font-variant:small-caps }
-  span.roman { font-family:serif; font-weight:normal; } 
-  span.sansserif { font-family:sans-serif; font-weight:normal; } 
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
+Texts.  A copy of the license is included in the section entitled
+"GNU Free Documentation License". -->
+<!-- Created by texi2html, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>Information for Maintainers of GNU Software: Creating Mailing 
Lists</title>
+
+<meta name="description" content="Information for Maintainers of GNU Software: 
Creating Mailing Lists">
+<meta name="keywords" content="Information for Maintainers of GNU Software: 
Creating Mailing Lists">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="texi2html">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Mail.html#Mail" rel="up" title="Mail">
+<link href="Replying-to-Mail.html#Replying-to-Mail" rel="next" title="Replying 
to Mail">
+<link href="Standard-Mailing-Lists.html#Standard-Mailing-Lists" rel="previous" 
title="Standard Mailing Lists">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smalllisp {margin-left: 3.2em}
+pre.display {font-family: serif}
+pre.format {font-family: serif}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: serif; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: serif; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:pre}
+span.nolinebreak {white-space:pre}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
 </head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF" 
vlink="#800080" alink="#FF0000">
+
 <a name="Creating-Mailing-Lists"></a>
+<div class="header">
 <p>
-Next:&nbsp;<a rel="next" accesskey="n" 
href="Replying-to-Mail.html#Replying-to-Mail">Replying to Mail</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" 
href="Standard-Mailing-Lists.html#Standard-Mailing-Lists">Standard Mailing 
Lists</a>,
-Up:&nbsp;<a rel="up" accesskey="u" href="Mail.html#Mail">Mail</a>
-<hr>
+Next: <a href="Replying-to-Mail.html#Replying-to-Mail" accesskey="n" 
rel="next">Replying to Mail</a>, Previous: <a 
href="Standard-Mailing-Lists.html#Standard-Mailing-Lists" accesskey="p" 
rel="previous">Standard Mailing Lists</a>, Up: <a href="Mail.html#Mail" 
accesskey="u" rel="up">Mail</a> &nbsp; [<a href="index.html#SEC_Contents" 
title="Table of contents" rel="contents">Contents</a>][<a 
href="Index.html#Index" title="Index" rel="index">Index</a>]</p>
 </div>
+<hr>
+<a name="Creating-Mailing-Lists-1"></a>
+<h2 class="section">9.2 Creating Mailing Lists</h2>
 
-<h3 class="section">9.2 Creating Mailing Lists</h3>
+<a name="index-creating-mailing-lists"></a>
+<a name="index-mailing-lists_002c-creating"></a>
 
-<p><a name="index-creating-mailing-lists-38"></a><a 
name="index-mailing-lists_002c-creating-39"></a>
-Using the web interface on <code>savannah.gnu.org</code> is by far the
+<p>Using the web interface on <code>savannah.gnu.org</code> is by far the
 easiest way to create normal mailing lists, managed through Mailman on
 the GNU mail server.  Once you register your package on Savannah, you
-can create (and remove) lists yourself through the `Mailing Lists'
+can create (and remove) lists yourself through the &lsquo;Mailing Lists&rsquo;
 menu, without needing to wait for intervention by anyone else. 
 Furthermore, lists created through Savannah will have a reasonable
 default configuration for antispam purposes (see below).
-
-   <p>To create and maintain simple aliases and unmanaged lists, you can
-edit <samp><span class="file">/com/mailer/aliases</span></samp> on the main 
GNU server.  If you don't
+</p>
+<p>To create and maintain simple aliases and unmanaged lists, you can
+edit &lsquo;<tt>/com/mailer/aliases</tt>&rsquo; on the main GNU server.  If 
you don&rsquo;t
 have an account there, please read
-<a 
href="http://www.gnu.org/software/README.accounts.html";>http://www.gnu.org/software/README.accounts.html</a>
 (see <a href="Getting-a-GNU-Account.html#Getting-a-GNU-Account">Getting a GNU 
Account</a>).
-
-   <p>But if you don't want to learn how to do those things, you can
+<a 
href="http://www.gnu.org/software/README.accounts.html";>http://www.gnu.org/software/README.accounts.html</a>
 (see <a href="Getting-a-GNU-Account.html#Getting-a-GNU-Account">Getting
+a GNU Account</a>).
+</p>
+<p>But if you don&rsquo;t want to learn how to do those things, you can
 alternatively ask <a href="mailto:address@hidden";>address@hidden</a> to add 
you to the
 bug-reporting list for your program.  To set up a new list, contact
 <a href="mailto:address@hidden";>address@hidden</a>.  You can subscribe to a 
list managed
-by Mailman by sending mail to the corresponding &lsquo;<samp><span 
class="samp">-request</span></samp>&rsquo; address.
-
-   <p><a name="index-spam-prevention-40"></a>You should moderate postings from 
non-subscribed addresses on your
+by Mailman by sending mail to the corresponding 
&lsquo;<samp>-request</samp>&rsquo; address.
+</p>
+<a name="index-spam-prevention"></a>
+<p>You should moderate postings from non-subscribed addresses on your
 mailing lists, to prevent propagation of unwanted messages (&ldquo;spam&rdquo;)
 to subscribers and to the list archives.  For lists controlled by
 Mailman, you can do this by setting <code>Privacy Options - Sender
 Filter - generic_nonmember_action</code> to <code>Hold</code>, and then
 periodically (daily is best) reviewing the held messages, accepting
 the real ones and discarding the junk.
-
-   <p>Lists created through Savannah will have this setting, and a number of
+</p>
+<p>Lists created through Savannah will have this setting, and a number of
 others, such that spam will be automatically deleted (after a short
 delay).  The Savannah mailing list page describes all the details. 
 You should still review the held messages in order to approve any that
 are real.
+</p>
+
+<hr>
+<div class="header">
+<p>
+Next: <a href="Replying-to-Mail.html#Replying-to-Mail" accesskey="n" 
rel="next">Replying to Mail</a>, Previous: <a 
href="Standard-Mailing-Lists.html#Standard-Mailing-Lists" accesskey="p" 
rel="previous">Standard Mailing Lists</a>, Up: <a href="Mail.html#Mail" 
accesskey="u" rel="up">Mail</a> &nbsp; [<a href="index.html#SEC_Contents" 
title="Table of contents" rel="contents">Contents</a>][<a 
href="Index.html#Index" title="Index" rel="index">Index</a>]</p>
+</div>
+<p>
 
-   </body></html>
 
+</p>
+</body>
+</html>

Index: html_node/Distribution-Patches.html
===================================================================
RCS file: /web/www/www/prep/maintain/html_node/Distribution-Patches.html,v
retrieving revision 1.66
retrieving revision 1.67
diff -u -b -r1.66 -r1.67
--- html_node/Distribution-Patches.html 7 Sep 2011 01:31:17 -0000       1.66
+++ html_node/Distribution-Patches.html 7 Sep 2011 15:00:28 -0000       1.67
@@ -1,94 +1,130 @@
-<html lang="en">
-<head>
-<title>Distribution Patches - Information for Maintainers of GNU 
Software</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="Information for Maintainers of GNU Software">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="Distributions.html#Distributions" title="Distributions">
-<link rel="prev" href="Distribution-tar-Files.html#Distribution-tar-Files" 
title="Distribution tar Files">
-<link rel="next" 
href="Distribution-on-ftp_002egnu_002eorg.html#Distribution-on-ftp_002egnu_002eorg"
 title="Distribution on ftp.gnu.org">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home" 
title="Texinfo Homepage">
-<!--
-Information for maintainers of GNU software, last updated September 5, 2011.
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" 
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
+<!-- Information for maintainers of GNU software, last updated September 5, 
2011.
 
 Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
 2010, 2011 Free Software Foundation, Inc.
 
-     Permission is granted to copy, distribute and/or modify this
-     document under the terms of the GNU Free Documentation License,
-     Version 1.3 or any later version published by the Free Software
-     Foundation; with no Invariant Sections, with no Front-Cover Texts,
-     and with no Back-Cover Texts.  A copy of the license is included
-     in the section entitled ``GNU Free Documentation License''.
-   -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
-  pre.display { font-family:inherit }
-  pre.format  { font-family:inherit }
-  pre.smalldisplay { font-family:inherit; font-size:smaller }
-  pre.smallformat  { font-family:inherit; font-size:smaller }
-  pre.smallexample { font-size:smaller }
-  pre.smalllisp    { font-size:smaller }
-  span.sc    { font-variant:small-caps }
-  span.roman { font-family:serif; font-weight:normal; } 
-  span.sansserif { font-family:sans-serif; font-weight:normal; } 
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
+Texts.  A copy of the license is included in the section entitled
+"GNU Free Documentation License". -->
+<!-- Created by texi2html, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>Information for Maintainers of GNU Software: Distribution 
Patches</title>
+
+<meta name="description" content="Information for Maintainers of GNU Software: 
Distribution Patches">
+<meta name="keywords" content="Information for Maintainers of GNU Software: 
Distribution Patches">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="texi2html">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Distributions.html#Distributions" rel="up" title="Distributions">
+<link 
href="Distribution-on-ftp_002egnu_002eorg.html#Distribution-on-ftp_002egnu_002eorg"
 rel="next" title="Distribution on ftp.gnu.org">
+<link href="Distribution-tar-Files.html#Distribution-tar-Files" rel="previous" 
title="Distribution tar Files">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smalllisp {margin-left: 3.2em}
+pre.display {font-family: serif}
+pre.format {font-family: serif}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: serif; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: serif; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:pre}
+span.nolinebreak {white-space:pre}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
 </head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF" 
vlink="#800080" alink="#FF0000">
+
 <a name="Distribution-Patches"></a>
+<div class="header">
 <p>
-Next:&nbsp;<a rel="next" accesskey="n" 
href="Distribution-on-ftp_002egnu_002eorg.html#Distribution-on-ftp_002egnu_002eorg">Distribution
 on ftp.gnu.org</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" 
href="Distribution-tar-Files.html#Distribution-tar-Files">Distribution tar 
Files</a>,
-Up:&nbsp;<a rel="up" accesskey="u" 
href="Distributions.html#Distributions">Distributions</a>
-<hr>
+Next: <a 
href="Distribution-on-ftp_002egnu_002eorg.html#Distribution-on-ftp_002egnu_002eorg"
 accesskey="n" rel="next">Distribution on ftp.gnu.org</a>, Previous: <a 
href="Distribution-tar-Files.html#Distribution-tar-Files" accesskey="p" 
rel="previous">Distribution tar Files</a>, Up: <a 
href="Distributions.html#Distributions" accesskey="u" 
rel="up">Distributions</a> &nbsp; [<a href="index.html#SEC_Contents" 
title="Table of contents" rel="contents">Contents</a>][<a 
href="Index.html#Index" title="Index" rel="index">Index</a>]</p>
 </div>
+<hr>
+<a name="Distribution-Patches-1"></a>
+<h2 class="section">11.2 Distribution Patches</h2>
+<a name="index-patches_002c-against-previous-releases"></a>
 
-<h3 class="section">11.2 Distribution Patches</h3>
-
-<p><a name="index-patches_002c-against-previous-releases-49"></a>
-If the program is large, it is useful to make a set of diffs for each
+<p>If the program is large, it is useful to make a set of diffs for each
 release, against the previous important release.
-
-   <p>At the front of the set of diffs, put a short explanation of which
+</p>
+<p>At the front of the set of diffs, put a short explanation of which
 version this is for and which previous version it is relative to. 
 Also explain what else people need to do to update the sources
 properly (for example, delete or rename certain files before
 installing the diffs).
-
-   <p>The purpose of having diffs is that they are small.  To keep them
+</p>
+<p>The purpose of having diffs is that they are small.  To keep them
 small, exclude files that the user can easily update.  For example,
 exclude info files, DVI files, tags tables, output files of Bison or
 Flex.  In Emacs diffs, we exclude compiled Lisp files, leaving it up
 to the installer to recompile the patched sources.
-
-   <p>When you make the diffs, each version should be in a directory suitably
-named&mdash;for example, <samp><span class="file">gcc-2.3.2</span></samp> and 
<samp><span class="file">gcc-2.3.3</span></samp>.  This way,
+</p>
+<p>When you make the diffs, each version should be in a directory suitably
+named&mdash;for example, &lsquo;<tt>gcc-2.3.2</tt>&rsquo; and 
&lsquo;<tt>gcc-2.3.3</tt>&rsquo;.  This way,
 it will be very clear from the diffs themselves which version is which.
-
-   <p><a name="index-diff-50"></a><a name="index-patch-51"></a><a 
name="index-time-stamp-in-diffs-52"></a>If you use GNU <code>diff</code> to 
make the patch, use the options
-&lsquo;<samp><span class="samp">-rc2P</span></samp>&rsquo;.  That will put any 
new files into the output as &ldquo;entirely
-different.&rdquo;  Also, the patch's context diff headers should have dates
+</p>
+<a name="index-diff"></a>
+<a name="index-patch"></a>
+<a name="index-time-stamp-in-diffs"></a>
+<p>If you use GNU <code>diff</code> to make the patch, use the options
+&lsquo;<samp>-rc2P</samp>&rsquo;.  That will put any new files into the output 
as &ldquo;entirely
+different.&rdquo;  Also, the patch&rsquo;s context diff headers should have 
dates
 and times in Universal Time using traditional Unix format, so that patch
-recipients can use GNU <code>patch</code>'s &lsquo;<samp><span 
class="samp">-Z</span></samp>&rsquo; option.  For example,
+recipients can use GNU <code>patch</code>&rsquo;s 
&lsquo;<samp>-Z</samp>&rsquo; option.  For example,
 you could use the following Bourne shell command to create the patch:
+</p>
+<div class="example">
+<pre class="example">LC_ALL=C TZ=UTC0 diff -rc2P gcc-2.3.2 gcc-2.3.3 | \
+gzip -9 &gt;gcc-2.3.2-2.3.3.patch.gz
+</pre></div>
 
-<pre class="example">     LC_ALL=C TZ=UTC0 diff -rc2P gcc-2.3.2 gcc-2.3.3 | \
-     gzip -9 &gt;gcc-2.3.2-2.3.3.patch.gz
-</pre>
-   <p>If the distribution has subdirectories in it, then the diffs probably
+<p>If the distribution has subdirectories in it, then the diffs probably
 include some files in the subdirectories.  To help users install such
 patches reliably, give them precise directions for how to run patch. 
 For example, say this:
+</p>
+<div class="display">
+<pre class="display">To apply these patches, cd to the main directory of the 
program
+and then use &lsquo;patch -p1&rsquo;.   &lsquo;-p1&rsquo; avoids guesswork in 
choosing
+which subdirectory to find each file in.
+</pre></div>
 
-<pre class="display">     To apply these patches, cd to the main directory of 
the program
-     and then use `patch -p1'.   `-p1' avoids guesswork in choosing
-     which subdirectory to find each file in.
-</pre>
-   <p>It's wise to test your patch by applying it to a copy of the old
+<p>It&rsquo;s wise to test your patch by applying it to a copy of the old
 version, and checking that the result exactly matches the new version.
+</p>
+<hr>
+<div class="header">
+<p>
+Next: <a 
href="Distribution-on-ftp_002egnu_002eorg.html#Distribution-on-ftp_002egnu_002eorg"
 accesskey="n" rel="next">Distribution on ftp.gnu.org</a>, Previous: <a 
href="Distribution-tar-Files.html#Distribution-tar-Files" accesskey="p" 
rel="previous">Distribution tar Files</a>, Up: <a 
href="Distributions.html#Distributions" accesskey="u" 
rel="up">Distributions</a> &nbsp; [<a href="index.html#SEC_Contents" 
title="Table of contents" rel="contents">Contents</a>][<a 
href="Index.html#Index" title="Index" rel="index">Index</a>]</p>
+</div>
+<p>
 
-   </body></html>
 
+</p>
+</body>
+</html>

Index: html_node/Distribution-on-ftp_002egnu_002eorg.html
===================================================================
RCS file: 
/web/www/www/prep/maintain/html_node/Distribution-on-ftp_002egnu_002eorg.html,v
retrieving revision 1.66
retrieving revision 1.67
diff -u -b -r1.66 -r1.67
--- html_node/Distribution-on-ftp_002egnu_002eorg.html  7 Sep 2011 01:31:17 
-0000       1.66
+++ html_node/Distribution-on-ftp_002egnu_002eorg.html  7 Sep 2011 15:00:28 
-0000       1.67
@@ -1,66 +1,87 @@
-<html lang="en">
-<head>
-<title>Distribution on ftp.gnu.org - Information for Maintainers of GNU 
Software</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="Information for Maintainers of GNU Software">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="Distributions.html#Distributions" title="Distributions">
-<link rel="prev" href="Distribution-Patches.html#Distribution-Patches" 
title="Distribution Patches">
-<link rel="next" href="Test-Releases.html#Test-Releases" title="Test Releases">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home" 
title="Texinfo Homepage">
-<!--
-Information for maintainers of GNU software, last updated September 5, 2011.
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" 
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
+<!-- Information for maintainers of GNU software, last updated September 5, 
2011.
 
 Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
 2010, 2011 Free Software Foundation, Inc.
 
-     Permission is granted to copy, distribute and/or modify this
-     document under the terms of the GNU Free Documentation License,
-     Version 1.3 or any later version published by the Free Software
-     Foundation; with no Invariant Sections, with no Front-Cover Texts,
-     and with no Back-Cover Texts.  A copy of the license is included
-     in the section entitled ``GNU Free Documentation License''.
-   -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
-  pre.display { font-family:inherit }
-  pre.format  { font-family:inherit }
-  pre.smalldisplay { font-family:inherit; font-size:smaller }
-  pre.smallformat  { font-family:inherit; font-size:smaller }
-  pre.smallexample { font-size:smaller }
-  pre.smalllisp    { font-size:smaller }
-  span.sc    { font-variant:small-caps }
-  span.roman { font-family:serif; font-weight:normal; } 
-  span.sansserif { font-family:sans-serif; font-weight:normal; } 
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
+Texts.  A copy of the license is included in the section entitled
+"GNU Free Documentation License". -->
+<!-- Created by texi2html, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>Information for Maintainers of GNU Software: Distribution on 
ftp.gnu.org</title>
+
+<meta name="description" content="Information for Maintainers of GNU Software: 
Distribution on ftp.gnu.org">
+<meta name="keywords" content="Information for Maintainers of GNU Software: 
Distribution on ftp.gnu.org">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="texi2html">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Distributions.html#Distributions" rel="up" title="Distributions">
+<link href="Test-Releases.html#Test-Releases" rel="next" title="Test Releases">
+<link href="Distribution-Patches.html#Distribution-Patches" rel="previous" 
title="Distribution Patches">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smalllisp {margin-left: 3.2em}
+pre.display {font-family: serif}
+pre.format {font-family: serif}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: serif; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: serif; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:pre}
+span.nolinebreak {white-space:pre}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
 </head>
-<body>
-<div class="node">
-<a name="Distribution-on-ftp.gnu.org"></a>
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF" 
vlink="#800080" alink="#FF0000">
+
 <a name="Distribution-on-ftp_002egnu_002eorg"></a>
+<div class="header">
 <p>
-Next:&nbsp;<a rel="next" accesskey="n" 
href="Test-Releases.html#Test-Releases">Test Releases</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" 
href="Distribution-Patches.html#Distribution-Patches">Distribution Patches</a>,
-Up:&nbsp;<a rel="up" accesskey="u" 
href="Distributions.html#Distributions">Distributions</a>
-<hr>
+Next: <a href="Test-Releases.html#Test-Releases" accesskey="n" rel="next">Test 
Releases</a>, Previous: <a 
href="Distribution-Patches.html#Distribution-Patches" accesskey="p" 
rel="previous">Distribution Patches</a>, Up: <a 
href="Distributions.html#Distributions" accesskey="u" 
rel="up">Distributions</a> &nbsp; [<a href="index.html#SEC_Contents" 
title="Table of contents" rel="contents">Contents</a>][<a 
href="Index.html#Index" title="Index" rel="index">Index</a>]</p>
 </div>
+<hr>
+<a name="Distribution-on-ftp_002egnu_002eorg-1"></a>
+<h2 class="section">11.3 Distribution on <code>ftp.gnu.org</code></h2>
+<a name="index-GNU-ftp-site"></a>
+<a name="index-ftp_002egnu_002eorg_002c-the-GNU-release-site"></a>
 
-<h3 class="section">11.3 Distribution on <code>ftp.gnu.org</code></h3>
-
-<p><a name="index-GNU-ftp-site-53"></a><a 
name="index-g_t_0040code_007bftp_002egnu_002eorg_007d_002c-the-GNU-release-site-54"></a>
-GNU packages are distributed through the directory <samp><span 
class="file">/gnu</span></samp> on
+<p>GNU packages are distributed through the directory 
&lsquo;<tt>/gnu</tt>&rsquo; on
 <code>ftp.gnu.org</code>, via both HTTP and FTP.  Each package should have a
 subdirectory named after the package, and all the distribution files
 for the package should go in that subdirectory.
+</p>
 
-<!-- If you have an interest in seeing the monthly download logs from the FTP 
-->
-<!-- site at @code{ftp.gnu.org} for your program, that is something that -->
-<!-- @email{ftp-upload@@gnu.org} can set up for you.  Please contact them if 
-->
-<!-- you are interested. -->
-   <p>See <a href="Automated-FTP-Uploads.html#Automated-FTP-Uploads">Automated 
FTP Uploads</a>, for procedural details of putting new
+<p>See <a href="Automated-FTP-Uploads.html#Automated-FTP-Uploads">Automated 
FTP Uploads</a>, for procedural details of putting new
 versions on <code>ftp.gnu.org</code>.
+</p>
+<p>
 
-   </body></html>
 
+</p>
+</body>
+</html>

Index: html_node/Distribution-tar-Files.html
===================================================================
RCS file: /web/www/www/prep/maintain/html_node/Distribution-tar-Files.html,v
retrieving revision 1.66
retrieving revision 1.67
diff -u -b -r1.66 -r1.67
--- html_node/Distribution-tar-Files.html       7 Sep 2011 01:31:17 -0000       
1.66
+++ html_node/Distribution-tar-Files.html       7 Sep 2011 15:00:30 -0000       
1.67
@@ -1,62 +1,85 @@
-<html lang="en">
-<head>
-<title>Distribution tar Files - Information for Maintainers of GNU 
Software</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="Information for Maintainers of GNU Software">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="Distributions.html#Distributions" title="Distributions">
-<link rel="next" href="Distribution-Patches.html#Distribution-Patches" 
title="Distribution Patches">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home" 
title="Texinfo Homepage">
-<!--
-Information for maintainers of GNU software, last updated September 5, 2011.
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" 
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
+<!-- Information for maintainers of GNU software, last updated September 5, 
2011.
 
 Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
 2010, 2011 Free Software Foundation, Inc.
 
-     Permission is granted to copy, distribute and/or modify this
-     document under the terms of the GNU Free Documentation License,
-     Version 1.3 or any later version published by the Free Software
-     Foundation; with no Invariant Sections, with no Front-Cover Texts,
-     and with no Back-Cover Texts.  A copy of the license is included
-     in the section entitled ``GNU Free Documentation License''.
-   -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
-  pre.display { font-family:inherit }
-  pre.format  { font-family:inherit }
-  pre.smalldisplay { font-family:inherit; font-size:smaller }
-  pre.smallformat  { font-family:inherit; font-size:smaller }
-  pre.smallexample { font-size:smaller }
-  pre.smalllisp    { font-size:smaller }
-  span.sc    { font-variant:small-caps }
-  span.roman { font-family:serif; font-weight:normal; } 
-  span.sansserif { font-family:sans-serif; font-weight:normal; } 
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
+Texts.  A copy of the license is included in the section entitled
+"GNU Free Documentation License". -->
+<!-- Created by texi2html, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>Information for Maintainers of GNU Software: Distribution tar 
Files</title>
+
+<meta name="description" content="Information for Maintainers of GNU Software: 
Distribution tar Files">
+<meta name="keywords" content="Information for Maintainers of GNU Software: 
Distribution tar Files">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="texi2html">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Distributions.html#Distributions" rel="up" title="Distributions">
+<link href="Distribution-Patches.html#Distribution-Patches" rel="next" 
title="Distribution Patches">
+<link href="Distributions.html#Distributions" rel="previous" 
title="Distributions">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smalllisp {margin-left: 3.2em}
+pre.display {font-family: serif}
+pre.format {font-family: serif}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: serif; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: serif; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:pre}
+span.nolinebreak {white-space:pre}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
 </head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF" 
vlink="#800080" alink="#FF0000">
+
 <a name="Distribution-tar-Files"></a>
+<div class="header">
 <p>
-Next:&nbsp;<a rel="next" accesskey="n" 
href="Distribution-Patches.html#Distribution-Patches">Distribution Patches</a>,
-Up:&nbsp;<a rel="up" accesskey="u" 
href="Distributions.html#Distributions">Distributions</a>
-<hr>
+Next: <a href="Distribution-Patches.html#Distribution-Patches" accesskey="n" 
rel="next">Distribution Patches</a>, Up: <a 
href="Distributions.html#Distributions" accesskey="u" 
rel="up">Distributions</a> &nbsp; [<a href="index.html#SEC_Contents" 
title="Table of contents" rel="contents">Contents</a>][<a 
href="Index.html#Index" title="Index" rel="index">Index</a>]</p>
 </div>
-
-<h3 class="section">11.1 Distribution tar Files</h3>
-
-<p><a name="index-distribution_002c-tar-files-47"></a>
-The tar file for version <var>m</var>.<var>n</var> of program <code>foo</code> 
should be
-named <samp><span class="file">foo-</span><var>m</var><span 
class="file">.</span><var>n</var><span class="file">.tar</span></samp>.  It 
should unpack into a
-subdirectory named <samp><span class="file">foo-</span><var>m</var><span 
class="file">.</span><var>n</var></samp>.  Tar files should not
+<hr>
+<a name="Distribution-tar-Files-1"></a>
+<h2 class="section">11.1 Distribution tar Files</h2>
+<a name="index-distribution_002c-tar-files"></a>
+
+<p>The tar file for version <var>m</var>.<var>n</var> of program 
<code>foo</code> should be
+named &lsquo;<tt>foo-<var>m</var>.<var>n</var>.tar</tt>&rsquo;.  It should 
unpack into a
+subdirectory named &lsquo;<tt>foo-<var>m</var>.<var>n</var></tt>&rsquo;.  Tar 
files should not
 unpack into files in the current directory, because this is inconvenient
 if the user happens to unpack into a directory with other files in it.
-
-   <p>Here is how the <samp><span class="file">Makefile</span></samp> for 
Bison creates the tar file. 
+</p>
+<p>Here is how the &lsquo;<tt>Makefile</tt>&rsquo; for Bison creates the tar 
file.
 This method is good for other programs.
-
-<pre class="example">     dist: bison.info
+</p>
+<div class="example">
+<pre class="example">dist: bison.info
              echo bison-`sed -e '/version_string/!d' \
                -e 's/[^0-9.]*\([0-9.]*\).*/\1/' -e q version.c` &gt; .fname
              -rm -rf `cat .fname`
@@ -67,13 +90,19 @@
              done
              tar --gzip -chf `cat .fname`.tar.gz `cat .fname`
              -rm -rf `cat .fname` .fname
-</pre>
-   <p>Source files that are symbolic links to other file systems cannot be
+</pre></div>
+
+<p>Source files that are symbolic links to other file systems cannot be
 installed in the temporary directory using <code>ln</code>, so use 
<code>cp</code>
 if <code>ln</code> fails.
-
-   <p><a name="index-automake-48"></a>Using Automake is a good way to take 
care of writing the <code>dist</code>
+</p>
+<a name="index-automake"></a>
+<p>Using Automake is a good way to take care of writing the <code>dist</code>
 target.
+</p>
+<p>
 
-   </body></html>
 
+</p>
+</body>
+</html>

Index: html_node/Distributions.html
===================================================================
RCS file: /web/www/www/prep/maintain/html_node/Distributions.html,v
retrieving revision 1.66
retrieving revision 1.67
diff -u -b -r1.66 -r1.67
--- html_node/Distributions.html        7 Sep 2011 01:31:17 -0000       1.66
+++ html_node/Distributions.html        7 Sep 2011 15:00:30 -0000       1.67
@@ -1,63 +1,94 @@
-<html lang="en">
-<head>
-<title>Distributions - Information for Maintainers of GNU Software</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="Information for Maintainers of GNU Software">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="prev" href="Old-Versions.html#Old-Versions" title="Old Versions">
-<link rel="next" href="Web-Pages.html#Web-Pages" title="Web Pages">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home" 
title="Texinfo Homepage">
-<!--
-Information for maintainers of GNU software, last updated September 5, 2011.
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" 
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
+<!-- Information for maintainers of GNU software, last updated September 5, 
2011.
 
 Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
 2010, 2011 Free Software Foundation, Inc.
 
-     Permission is granted to copy, distribute and/or modify this
-     document under the terms of the GNU Free Documentation License,
-     Version 1.3 or any later version published by the Free Software
-     Foundation; with no Invariant Sections, with no Front-Cover Texts,
-     and with no Back-Cover Texts.  A copy of the license is included
-     in the section entitled ``GNU Free Documentation License''.
-   -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
-  pre.display { font-family:inherit }
-  pre.format  { font-family:inherit }
-  pre.smalldisplay { font-family:inherit; font-size:smaller }
-  pre.smallformat  { font-family:inherit; font-size:smaller }
-  pre.smallexample { font-size:smaller }
-  pre.smalllisp    { font-size:smaller }
-  span.sc    { font-variant:small-caps }
-  span.roman { font-family:serif; font-weight:normal; } 
-  span.sansserif { font-family:sans-serif; font-weight:normal; } 
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
+Texts.  A copy of the license is included in the section entitled
+"GNU Free Documentation License". -->
+<!-- Created by texi2html, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>Information for Maintainers of GNU Software: Distributions</title>
+
+<meta name="description" content="Information for Maintainers of GNU Software: 
Distributions">
+<meta name="keywords" content="Information for Maintainers of GNU Software: 
Distributions">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="texi2html">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="index.html#Top" rel="up" title="Top">
+<link href="Distribution-tar-Files.html#Distribution-tar-Files" rel="next" 
title="Distribution tar Files">
+<link href="Old-Versions.html#Old-Versions" rel="previous" title="Old 
Versions">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smalllisp {margin-left: 3.2em}
+pre.display {font-family: serif}
+pre.format {font-family: serif}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: serif; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: serif; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:pre}
+span.nolinebreak {white-space:pre}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
 </head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF" 
vlink="#800080" alink="#FF0000">
+
 <a name="Distributions"></a>
+<div class="header">
 <p>
-Next:&nbsp;<a rel="next" accesskey="n" href="Web-Pages.html#Web-Pages">Web 
Pages</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" 
href="Old-Versions.html#Old-Versions">Old Versions</a>,
-Up:&nbsp;<a rel="up" accesskey="u" href="index.html#Top">Top</a>
-<hr>
+Next: <a href="Web-Pages.html#Web-Pages" accesskey="n" rel="next">Web 
Pages</a>, Previous: <a href="Old-Versions.html#Old-Versions" accesskey="p" 
rel="previous">Old Versions</a>, Up: <a href="index.html#Top" accesskey="u" 
rel="up">Top</a> &nbsp; [<a href="index.html#SEC_Contents" title="Table of 
contents" rel="contents">Contents</a>][<a href="Index.html#Index" title="Index" 
rel="index">Index</a>]</p>
 </div>
-
-<h2 class="chapter">11 Distributions</h2>
+<hr>
+<a name="Distributions-1"></a>
+<h1 class="chapter">11 Distributions</h1>
 
 <p>It is important to follow the GNU conventions when making GNU software
 distributions.
+</p>
+<table class="menu" border="0" cellspacing="0">
+<tr><td align="left" valign="top">&bull; <a 
href="Distribution-tar-Files.html#Distribution-tar-Files" 
accesskey="1">Distribution tar Files</a>:</td><td>&nbsp;&nbsp;</td><td 
align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a 
href="Distribution-Patches.html#Distribution-Patches" 
accesskey="2">Distribution Patches</a>:</td><td>&nbsp;&nbsp;</td><td 
align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a 
href="Distribution-on-ftp_002egnu_002eorg.html#Distribution-on-ftp_002egnu_002eorg"
 accesskey="3">Distribution on ftp.gnu.org</a>:</td><td>&nbsp;&nbsp;</td><td 
align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a 
href="Test-Releases.html#Test-Releases" accesskey="4">Test 
Releases</a>:</td><td>&nbsp;&nbsp;</td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a 
href="Automated-FTP-Uploads.html#Automated-FTP-Uploads" accesskey="5">Automated 
FTP Uploads</a>:</td><td>&nbsp;&nbsp;</td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a 
href="Announcements.html#Announcements" 
accesskey="6">Announcements</a>:</td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">
+</td></tr>
+</table>
 
-<ul class="menu">
-<li><a accesskey="1" 
href="Distribution-tar-Files.html#Distribution-tar-Files">Distribution tar 
Files</a>
-<li><a accesskey="2" 
href="Distribution-Patches.html#Distribution-Patches">Distribution Patches</a>
-<li><a accesskey="3" 
href="Distribution-on-ftp_002egnu_002eorg.html#Distribution-on-ftp_002egnu_002eorg">Distribution
 on ftp.gnu.org</a>
-<li><a accesskey="4" href="Test-Releases.html#Test-Releases">Test Releases</a>
-<li><a accesskey="5" 
href="Automated-FTP-Uploads.html#Automated-FTP-Uploads">Automated FTP 
Uploads</a>
-<li><a accesskey="6" href="Announcements.html#Announcements">Announcements</a>
-</ul>
+<p>
 
-   </body></html>
 
+</p>
+</body>
+</html>

Index: html_node/Donations.html
===================================================================
RCS file: /web/www/www/prep/maintain/html_node/Donations.html,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -b -r1.9 -r1.10
--- html_node/Donations.html    7 Sep 2011 01:31:17 -0000       1.9
+++ html_node/Donations.html    7 Sep 2011 15:00:31 -0000       1.10
@@ -1,88 +1,122 @@
-<html lang="en">
-<head>
-<title>Donations - Information for Maintainers of GNU Software</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="Information for Maintainers of GNU Software">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="prev" href="Hosting.html#Hosting" title="Hosting">
-<link rel="next" href="Free-Software-Directory.html#Free-Software-Directory" 
title="Free Software Directory">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home" 
title="Texinfo Homepage">
-<!--
-Information for maintainers of GNU software, last updated September 5, 2011.
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" 
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
+<!-- Information for maintainers of GNU software, last updated September 5, 
2011.
 
 Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
 2010, 2011 Free Software Foundation, Inc.
 
-     Permission is granted to copy, distribute and/or modify this
-     document under the terms of the GNU Free Documentation License,
-     Version 1.3 or any later version published by the Free Software
-     Foundation; with no Invariant Sections, with no Front-Cover Texts,
-     and with no Back-Cover Texts.  A copy of the license is included
-     in the section entitled ``GNU Free Documentation License''.
-   -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
-  pre.display { font-family:inherit }
-  pre.format  { font-family:inherit }
-  pre.smalldisplay { font-family:inherit; font-size:smaller }
-  pre.smallformat  { font-family:inherit; font-size:smaller }
-  pre.smallexample { font-size:smaller }
-  pre.smalllisp    { font-size:smaller }
-  span.sc    { font-variant:small-caps }
-  span.roman { font-family:serif; font-weight:normal; } 
-  span.sansserif { font-family:sans-serif; font-weight:normal; } 
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
+Texts.  A copy of the license is included in the section entitled
+"GNU Free Documentation License". -->
+<!-- Created by texi2html, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>Information for Maintainers of GNU Software: Donations</title>
+
+<meta name="description" content="Information for Maintainers of GNU Software: 
Donations">
+<meta name="keywords" content="Information for Maintainers of GNU Software: 
Donations">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="texi2html">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="index.html#Top" rel="up" title="Top">
+<link href="Free-Software-Directory.html#Free-Software-Directory" rel="next" 
title="Free Software Directory">
+<link href="Hosting.html#Hosting" rel="previous" title="Hosting">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smalllisp {margin-left: 3.2em}
+pre.display {font-family: serif}
+pre.format {font-family: serif}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: serif; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: serif; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:pre}
+span.nolinebreak {white-space:pre}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
 </head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF" 
vlink="#800080" alink="#FF0000">
+
 <a name="Donations"></a>
+<div class="header">
 <p>
-Next:&nbsp;<a rel="next" accesskey="n" 
href="Free-Software-Directory.html#Free-Software-Directory">Free Software 
Directory</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" 
href="Hosting.html#Hosting">Hosting</a>,
-Up:&nbsp;<a rel="up" accesskey="u" href="index.html#Top">Top</a>
-<hr>
+Next: <a href="Free-Software-Directory.html#Free-Software-Directory" 
accesskey="n" rel="next">Free Software Directory</a>, Previous: <a 
href="Hosting.html#Hosting" accesskey="p" rel="previous">Hosting</a>, Up: <a 
href="index.html#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a 
href="index.html#SEC_Contents" title="Table of contents" 
rel="contents">Contents</a>][<a href="Index.html#Index" title="Index" 
rel="index">Index</a>]</p>
 </div>
+<hr>
+<a name="Donations-1"></a>
+<h1 class="chapter">16 Donations</h1>
+<a name="index-Donations_002c-for-packages"></a>
+<a name="index-Money_002c-donated-to-packages"></a>
 
-<h2 class="chapter">16 Donations</h2>
-
-<p><a name="index-Donations_002c-for-packages-92"></a><a 
name="index-Money_002c-donated-to-packages-93"></a>
-As a maintainer, you might want to accept donations for your work,
+<p>As a maintainer, you might want to accept donations for your work,
 especially if you pay for any of your own hosting/development
 infrastructure.  Following is some text you can adapt to your own
-situation, and use on your package's web site, <samp><span 
class="file">README</span></samp>, or
+situation, and use on your package&rsquo;s web site, 
&lsquo;<tt>README</tt>&rsquo;, or
 in wherever way you find it useful:
+</p>
+<div class="smallexample">
+<pre class="smallexample">We appreciate contributions of any size -- donations 
enable us to spend
+more time working on the project, and help cover our infrastructure
+expenses.
+
+If you'd like to make a small donation, please visit <var>url1</var> and do
+it through <var>payment-service</var>.  Since our project isn't a
+tax-exempt organization, we can't offer you a tax deduction, but for
+all donations over <var>amount1</var>, we'd be happy to recognize your
+contribution on <var>url2</var>.
+
+We are also happy to consider making particular improvements or
+changes, or giving specific technical assistance, in return for a
+substantial donation over <var>amount2</var>.  If you would like to discuss
+this possibility, write to us at <var>address</var>.
+
+Another possibility is to pay a software maintenance fee.  Again,
+write to us about this at <var>address</var> to discuss how much you want
+to pay and how much maintenance we can offer in return.  If you pay
+more than <var>amount1</var>, we can give you a document for your records.
 
-<pre class="smallexample">     We appreciate contributions of any size -- 
donations enable us to spend
-     more time working on the project, and help cover our infrastructure
-     expenses.
-     
-     If you'd like to make a small donation, please visit <var>url1</var> and 
do
-     it through <var>payment-service</var>.  Since our project isn't a
-     tax-exempt organization, we can't offer you a tax deduction, but for
-     all donations over <var>amount1</var>, we'd be happy to recognize your
-     contribution on <var>url2</var>.
-     
-     We are also happy to consider making particular improvements or
-     changes, or giving specific technical assistance, in return for a
-     substantial donation over <var>amount2</var>.  If you would like to 
discuss
-     this possibility, write to us at <var>address</var>.
-     
-     Another possibility is to pay a software maintenance fee.  Again,
-     write to us about this at <var>address</var> to discuss how much you want
-     to pay and how much maintenance we can offer in return.  If you pay
-     more than <var>amount1</var>, we can give you a document for your records.
-     
-     Thanks for your support!
-</pre>
-   <p>We don't recommend any specific payment service.  However, GNU
-developers should not use a service that requires them to sign a
-proprietary software license, such as Google's payment service.
+Thanks for your support!
+</pre></div>
 
-   <p>Of course, it is also good to encourage people to join or contribute
+<p>We don&rsquo;t recommend any specific payment service.  However, GNU
+developers should not use a service that requires them to sign a
+proprietary software license, such as Google&rsquo;s payment service.
+</p>
+<p>Of course, it is also good to encourage people to join or contribute
 to the FSF (<a href="http://www.fsf.org";>http://www.fsf.org</a>), either 
instead of or as well as
 package-specific donations.
+</p>
+
+<hr>
+<div class="header">
+<p>
+Next: <a href="Free-Software-Directory.html#Free-Software-Directory" 
accesskey="n" rel="next">Free Software Directory</a>, Previous: <a 
href="Hosting.html#Hosting" accesskey="p" rel="previous">Hosting</a>, Up: <a 
href="index.html#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a 
href="index.html#SEC_Contents" title="Table of contents" 
rel="contents">Contents</a>][<a href="Index.html#Index" title="Index" 
rel="index">Index</a>]</p>
+</div>
+<p>
 
-   </body></html>
 
+</p>
+</body>
+</html>

Index: html_node/Ethical-and-Philosophical-Consideration.html
===================================================================
RCS file: 
/web/www/www/prep/maintain/html_node/Ethical-and-Philosophical-Consideration.html,v
retrieving revision 1.67
retrieving revision 1.68
diff -u -b -r1.67 -r1.68
--- html_node/Ethical-and-Philosophical-Consideration.html      7 Sep 2011 
01:31:17 -0000       1.67
+++ html_node/Ethical-and-Philosophical-Consideration.html      7 Sep 2011 
15:00:31 -0000       1.68
@@ -1,79 +1,101 @@
-<html lang="en">
-<head>
-<title>Ethical and Philosophical Consideration - Information for Maintainers 
of GNU Software</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="Information for Maintainers of GNU Software">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="prev" href="Web-Pages.html#Web-Pages" title="Web Pages">
-<link rel="next" href="Terminology.html#Terminology" title="Terminology">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home" 
title="Texinfo Homepage">
-<!--
-Information for maintainers of GNU software, last updated September 5, 2011.
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" 
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
+<!-- Information for maintainers of GNU software, last updated September 5, 
2011.
 
 Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
 2010, 2011 Free Software Foundation, Inc.
 
-     Permission is granted to copy, distribute and/or modify this
-     document under the terms of the GNU Free Documentation License,
-     Version 1.3 or any later version published by the Free Software
-     Foundation; with no Invariant Sections, with no Front-Cover Texts,
-     and with no Back-Cover Texts.  A copy of the license is included
-     in the section entitled ``GNU Free Documentation License''.
-   -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
-  pre.display { font-family:inherit }
-  pre.format  { font-family:inherit }
-  pre.smalldisplay { font-family:inherit; font-size:smaller }
-  pre.smallformat  { font-family:inherit; font-size:smaller }
-  pre.smallexample { font-size:smaller }
-  pre.smalllisp    { font-size:smaller }
-  span.sc    { font-variant:small-caps }
-  span.roman { font-family:serif; font-weight:normal; } 
-  span.sansserif { font-family:sans-serif; font-weight:normal; } 
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
+Texts.  A copy of the license is included in the section entitled
+"GNU Free Documentation License". -->
+<!-- Created by texi2html, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>Information for Maintainers of GNU Software: Ethical and Philosophical 
Consideration</title>
+
+<meta name="description" content="Information for Maintainers of GNU Software: 
Ethical and Philosophical Consideration">
+<meta name="keywords" content="Information for Maintainers of GNU Software: 
Ethical and Philosophical Consideration">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="texi2html">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="index.html#Top" rel="up" title="Top">
+<link href="Terminology.html#Terminology" rel="next" title="Terminology">
+<link href="CVS-Keywords-in-Web-Pages.html#CVS-Keywords-in-Web-Pages" 
rel="previous" title="CVS Keywords in Web Pages">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smalllisp {margin-left: 3.2em}
+pre.display {font-family: serif}
+pre.format {font-family: serif}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: serif; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: serif; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:pre}
+span.nolinebreak {white-space:pre}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
 </head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF" 
vlink="#800080" alink="#FF0000">
+
 <a name="Ethical-and-Philosophical-Consideration"></a>
+<div class="header">
 <p>
-Next:&nbsp;<a rel="next" accesskey="n" 
href="Terminology.html#Terminology">Terminology</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" 
href="Web-Pages.html#Web-Pages">Web Pages</a>,
-Up:&nbsp;<a rel="up" accesskey="u" href="index.html#Top">Top</a>
-<hr>
+Next: <a href="Terminology.html#Terminology" accesskey="n" 
rel="next">Terminology</a>, Previous: <a href="Web-Pages.html#Web-Pages" 
accesskey="p" rel="previous">Web Pages</a>, Up: <a href="index.html#Top" 
accesskey="u" rel="up">Top</a> &nbsp; [<a href="index.html#SEC_Contents" 
title="Table of contents" rel="contents">Contents</a>][<a 
href="Index.html#Index" title="Index" rel="index">Index</a>]</p>
 </div>
+<hr>
+<a name="Ethical-and-Philosophical-Consideration-1"></a>
+<h1 class="chapter">13 Ethical and Philosophical Consideration</h1>
+<a name="index-ethics"></a>
+<a name="index-philosophy"></a>
 
-<h2 class="chapter">13 Ethical and Philosophical Consideration</h2>
-
-<p><a name="index-ethics-76"></a><a name="index-philosophy-77"></a>
-The GNU project takes a strong stand for software freedom.  Many
-times, this means you'll need to avoid certain technologies when their
+<p>The GNU project takes a strong stand for software freedom.  Many
+times, this means you&rsquo;ll need to avoid certain technologies when their
 use would conflict with our long-term goals.
-
-   <p>Software patents threaten the advancement of free software and freedom
+</p>
+<p>Software patents threaten the advancement of free software and freedom
 to program.  There are so many software patents in the US that any
 large program probably implements hundreds of patented techniques,
-unknown to the program's developers.  It would be futile and
+unknown to the program&rsquo;s developers.  It would be futile and
 self-defeating to try to find and avoid all these patents.  But there
 are some patents which we know are likely to be used to threaten free
 software, so we make an effort to avoid the patented techniques.  If
 you are concerned about the danger of a patent and would like advice,
 write to <a href="mailto:address@hidden";>address@hidden</a>, and we will try 
to help you get
 advice from a lawyer.
-
-   <p>Sometimes the GNU project takes a strong stand against a particular
+</p>
+<p>Sometimes the GNU project takes a strong stand against a particular
 patented technology in order to encourage society to reject it.
-
-   <p>For example, the MP3 audio format is covered by a software patent in
+</p>
+<p>For example, the MP3 audio format is covered by a software patent in
 the USA and some other countries.  A patent holder has threatened
 lawsuits against the developers of free programs (these are not GNU
 programs) to produce and play MP3, and some GNU/Linux distributors are
 afraid to include them.  Development of the programs continues, but we
 campaign for the rejection of MP3 format in favor of Ogg Vorbis format.
-
-   <p>A GNU package should not recommend use of any non-free program, nor
+</p>
+<p>A GNU package should not recommend use of any non-free program, nor
 should it require a non-free program (such as a non-free compiler or
 IDE) to build.  Thus, a GNU package cannot be written in a programming
 language that does not have a free software implementation.  Now that
@@ -81,17 +103,27 @@
 provide full functionality on a 100% free GNU/Linux system, and should
 not require any non-free software to build or function. 
 The GNU Coding Standards say a lot more about this issue.
-
-   <p>A GNU package should not refer the user to any non-free documentation
+</p>
+<p>A GNU package should not refer the user to any non-free documentation
 for free software.  The need for free documentation to come with free
 software is now a major focus of the GNU project; to show that we are
 serious about the need for free documentation, we must not contradict
-our position by recommending use of documentation that isn't free.
-
-   <p>Finally, new issues concerning the ethics of software freedom come up
+our position by recommending use of documentation that isn&rsquo;t free.
+</p>
+<p>Finally, new issues concerning the ethics of software freedom come up
 frequently.  We ask that GNU maintainers, at least on matters that
 pertain specifically to their package, stand with the rest of the GNU
 project when such issues come up.
+</p>
+
+<hr>
+<div class="header">
+<p>
+Next: <a href="Terminology.html#Terminology" accesskey="n" 
rel="next">Terminology</a>, Previous: <a href="Web-Pages.html#Web-Pages" 
accesskey="p" rel="previous">Web Pages</a>, Up: <a href="index.html#Top" 
accesskey="u" rel="up">Top</a> &nbsp; [<a href="index.html#SEC_Contents" 
title="Table of contents" rel="contents">Contents</a>][<a 
href="Index.html#Index" title="Index" rel="index">Index</a>]</p>
+</div>
+<p>
 
-   </body></html>
 
+</p>
+</body>
+</html>

Index: html_node/External-Libraries.html
===================================================================
RCS file: /web/www/www/prep/maintain/html_node/External-Libraries.html,v
retrieving revision 1.66
retrieving revision 1.67
diff -u -b -r1.66 -r1.67
--- html_node/External-Libraries.html   7 Sep 2011 01:31:17 -0000       1.66
+++ html_node/External-Libraries.html   7 Sep 2011 15:00:31 -0000       1.67
@@ -1,86 +1,118 @@
-<html lang="en">
-<head>
-<title>External Libraries - Information for Maintainers of GNU Software</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="Information for Maintainers of GNU Software">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="Legal-Matters.html#Legal-Matters" title="Legal Matters">
-<link rel="prev" href="License-Notices.html#License-Notices" title="License 
Notices">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home" 
title="Texinfo Homepage">
-<!--
-Information for maintainers of GNU software, last updated September 5, 2011.
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" 
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
+<!-- Information for maintainers of GNU software, last updated September 5, 
2011.
 
 Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
 2010, 2011 Free Software Foundation, Inc.
 
-     Permission is granted to copy, distribute and/or modify this
-     document under the terms of the GNU Free Documentation License,
-     Version 1.3 or any later version published by the Free Software
-     Foundation; with no Invariant Sections, with no Front-Cover Texts,
-     and with no Back-Cover Texts.  A copy of the license is included
-     in the section entitled ``GNU Free Documentation License''.
-   -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
-  pre.display { font-family:inherit }
-  pre.format  { font-family:inherit }
-  pre.smalldisplay { font-family:inherit; font-size:smaller }
-  pre.smallformat  { font-family:inherit; font-size:smaller }
-  pre.smallexample { font-size:smaller }
-  pre.smalllisp    { font-size:smaller }
-  span.sc    { font-variant:small-caps }
-  span.roman { font-family:serif; font-weight:normal; } 
-  span.sansserif { font-family:sans-serif; font-weight:normal; } 
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
+Texts.  A copy of the license is included in the section entitled
+"GNU Free Documentation License". -->
+<!-- Created by texi2html, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>Information for Maintainers of GNU Software: External Libraries</title>
+
+<meta name="description" content="Information for Maintainers of GNU Software: 
External Libraries">
+<meta name="keywords" content="Information for Maintainers of GNU Software: 
External Libraries">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="texi2html">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Legal-Matters.html#Legal-Matters" rel="up" title="Legal Matters">
+<link href="Clean-Ups.html#Clean-Ups" rel="next" title="Clean Ups">
+<link 
href="License-Notices-for-Other-Files.html#License-Notices-for-Other-Files" 
rel="previous" title="License Notices for Other Files">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smalllisp {margin-left: 3.2em}
+pre.display {font-family: serif}
+pre.format {font-family: serif}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: serif; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: serif; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:pre}
+span.nolinebreak {white-space:pre}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
 </head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF" 
vlink="#800080" alink="#FF0000">
+
 <a name="External-Libraries"></a>
+<div class="header">
 <p>
-Previous:&nbsp;<a rel="previous" accesskey="p" 
href="License-Notices.html#License-Notices">License Notices</a>,
-Up:&nbsp;<a rel="up" accesskey="u" 
href="Legal-Matters.html#Legal-Matters">Legal Matters</a>
-<hr>
+Previous: <a href="License-Notices.html#License-Notices" accesskey="p" 
rel="previous">License Notices</a>, Up: <a 
href="Legal-Matters.html#Legal-Matters" accesskey="u" rel="up">Legal 
Matters</a> &nbsp; [<a href="index.html#SEC_Contents" title="Table of contents" 
rel="contents">Contents</a>][<a href="Index.html#Index" title="Index" 
rel="index">Index</a>]</p>
 </div>
-
-<h3 class="section">6.7 External Libraries</h3>
+<hr>
+<a name="External-Libraries-1"></a>
+<h2 class="section">6.7 External Libraries</h2>
 
 <p>When maintaining an FSF-copyrighted GNU package, you may occasionally
 want to use a general-purpose free software module which offers a
 useful functionality, as a &ldquo;library&rdquo; facility (though the module is
 not always packaged technically as a library).
-
-   <p>In a case like this, it would be unreasonable to ask the author of that
+</p>
+<p>In a case like this, it would be unreasonable to ask the author of that
 module to assign the copyright to the FSF.  After all, person did not
 write it specifically as a contribution to your package, so it would be
 impertinent to ask per, out of the blue, &ldquo;Please give the FSF your
 copyright.&rdquo;
-
-   <p>So the thing to do in this case is to make your program use the module,
+</p>
+<p>So the thing to do in this case is to make your program use the module,
 but not consider it a part of your program.  There are two reasonable
 methods of doing this:
-
-     <ol type=1 start=1>
-<li>Assume the module is already installed on the system, and use it when
+</p>
+<ol>
+<li> Assume the module is already installed on the system, and use it when
 linking your program.  This is only reasonable if the module really has
 the form of a library.
 
-     <li>Include the module in your package, putting the source in a separate
-subdirectory whose <samp><span class="file">README</span></samp> file says, 
&ldquo;This is not part of the
+</li><li> Include the module in your package, putting the source in a separate
+subdirectory whose &lsquo;<tt>README</tt>&rsquo; file says, &ldquo;This is not 
part of the
 GNU FOO program, but is used with GNU FOO.&rdquo;  Then set up your makefiles
 to build this module and link it into the executable.
 
-     <p>For this method, it is not necessary to treat the module as a library
-and make a &lsquo;<samp><span class="samp">.a</span></samp>&rsquo; file from 
it.  You can link with the &lsquo;<samp><span 
class="samp">.o</span></samp>&rsquo;
+<p>For this method, it is not necessary to treat the module as a library
+and make a &lsquo;<samp>.a</samp>&rsquo; file from it.  You can link with the 
&lsquo;<samp>.o</samp>&rsquo;
 files directly in the usual manner.
-        </ol>
+</p></li></ol>
 
-   <p>Both of these methods create an irregularity, and our lawyers have told
+<p>Both of these methods create an irregularity, and our lawyers have told
 us to minimize the amount of such irregularity.  So consider using these
 methods only for general-purpose modules that were written for other
 programs and released separately for general use.  For anything that was
 written as a contribution to your package, please get papers signed.
+</p>
+
+<hr>
+<div class="header">
+<p>
+Previous: <a href="License-Notices.html#License-Notices" accesskey="p" 
rel="previous">License Notices</a>, Up: <a 
href="Legal-Matters.html#Legal-Matters" accesskey="u" rel="up">Legal 
Matters</a> &nbsp; [<a href="index.html#SEC_Contents" title="Table of contents" 
rel="contents">Contents</a>][<a href="Index.html#Index" title="Index" 
rel="index">Index</a>]</p>
+</div>
+<p>
 
-   </body></html>
 
+</p>
+</body>
+</html>

Index: html_node/FTP-Upload-Directive-File-_002d-v1_002e0.html
===================================================================
RCS file: 
/web/www/www/prep/maintain/html_node/FTP-Upload-Directive-File-_002d-v1_002e0.html,v
retrieving revision 1.56
retrieving revision 1.57
diff -u -b -r1.56 -r1.57
--- html_node/FTP-Upload-Directive-File-_002d-v1_002e0.html     7 Sep 2011 
01:31:17 -0000       1.56
+++ html_node/FTP-Upload-Directive-File-_002d-v1_002e0.html     7 Sep 2011 
15:00:31 -0000       1.57
@@ -1,77 +1,105 @@
-<html lang="en">
-<head>
-<title>FTP Upload Directive File - v1.0 - Information for Maintainers of GNU 
Software</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="Information for Maintainers of GNU Software">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="Automated-FTP-Uploads.html#Automated-FTP-Uploads" 
title="Automated FTP Uploads">
-<link rel="prev" 
href="FTP-Upload-Directive-File-_002d-v1_002e1.html#FTP-Upload-Directive-File-_002d-v1_002e1"
 title="FTP Upload Directive File - v1.1">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home" 
title="Texinfo Homepage">
-<!--
-Information for maintainers of GNU software, last updated September 5, 2011.
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" 
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
+<!-- Information for maintainers of GNU software, last updated September 5, 
2011.
 
 Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
 2010, 2011 Free Software Foundation, Inc.
 
-     Permission is granted to copy, distribute and/or modify this
-     document under the terms of the GNU Free Documentation License,
-     Version 1.3 or any later version published by the Free Software
-     Foundation; with no Invariant Sections, with no Front-Cover Texts,
-     and with no Back-Cover Texts.  A copy of the license is included
-     in the section entitled ``GNU Free Documentation License''.
-   -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
-  pre.display { font-family:inherit }
-  pre.format  { font-family:inherit }
-  pre.smalldisplay { font-family:inherit; font-size:smaller }
-  pre.smallformat  { font-family:inherit; font-size:smaller }
-  pre.smallexample { font-size:smaller }
-  pre.smalllisp    { font-size:smaller }
-  span.sc    { font-variant:small-caps }
-  span.roman { font-family:serif; font-weight:normal; } 
-  span.sansserif { font-family:sans-serif; font-weight:normal; } 
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
+Texts.  A copy of the license is included in the section entitled
+"GNU Free Documentation License". -->
+<!-- Created by texi2html, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>Information for Maintainers of GNU Software: FTP Upload Directive File 
- v1.0</title>
+
+<meta name="description" content="Information for Maintainers of GNU Software: 
FTP Upload Directive File - v1.0">
+<meta name="keywords" content="Information for Maintainers of GNU Software: 
FTP Upload Directive File - v1.0">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="texi2html">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Automated-FTP-Uploads.html#Automated-FTP-Uploads" rel="up" 
title="Automated FTP Uploads">
+<link href="Announcements.html#Announcements" rel="next" title="Announcements">
+<link 
href="FTP-Upload-Directive-File-_002d-v1_002e1.html#FTP-Upload-Directive-File-_002d-v1_002e1"
 rel="previous" title="FTP Upload Directive File - v1.1">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smalllisp {margin-left: 3.2em}
+pre.display {font-family: serif}
+pre.format {font-family: serif}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: serif; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: serif; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:pre}
+span.nolinebreak {white-space:pre}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
 </head>
-<body>
-<div class="node">
-<a name="FTP-Upload-Directive-File---v1.0"></a>
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF" 
vlink="#800080" alink="#FF0000">
+
 <a name="FTP-Upload-Directive-File-_002d-v1_002e0"></a>
+<div class="header">
 <p>
-Previous:&nbsp;<a rel="previous" accesskey="p" 
href="FTP-Upload-Directive-File-_002d-v1_002e1.html#FTP-Upload-Directive-File-_002d-v1_002e1">FTP
 Upload Directive File - v1.1</a>,
-Up:&nbsp;<a rel="up" accesskey="u" 
href="Automated-FTP-Uploads.html#Automated-FTP-Uploads">Automated FTP 
Uploads</a>
-<hr>
+Previous: <a 
href="FTP-Upload-Directive-File-_002d-v1_002e1.html#FTP-Upload-Directive-File-_002d-v1_002e1"
 accesskey="p" rel="previous">FTP Upload Directive File - v1.1</a>, Up: <a 
href="Automated-FTP-Uploads.html#Automated-FTP-Uploads" accesskey="u" 
rel="up">Automated FTP Uploads</a> &nbsp; [<a href="index.html#SEC_Contents" 
title="Table of contents" rel="contents">Contents</a>][<a 
href="Index.html#Index" title="Index" rel="index">Index</a>]</p>
 </div>
+<hr>
+<a name="FTP-Upload-Directive-File-_002d-v1_002e0-1"></a>
+<h3 class="subsection">11.5.4 FTP Upload Directive File - v1.0</h3>
 
-<h4 class="subsection">11.5.4 FTP Upload Directive File - v1.0</h4>
-
-<p><dfn>As of June 2006, the upload script is running in compatibility
+<p><em>As of June 2006, the upload script is running in compatibility
 mode, allowing uploads with either version&nbsp;1.1 or
 version&nbsp;1.0 of the directive file syntax.  Support for v1.0
 uploads will be phased out by the end of 2006, so please upgrade
-to&nbsp;v1.1.</dfn>
-
-   <p>The directive file should contain one line, excluding the clearsigned
+to&nbsp;v1.1.</em>
+</p>
+<p>The directive file should contain one line, excluding the clearsigned
 data GPG that inserts, which specifies the final destination directory
 where items (1) and (2) are to be placed.
-
-   <p>For example, the <samp><span 
class="file">foo.tar.gz.directive.asc</span></samp> file might contain the
+</p>
+<p>For example, the &lsquo;<tt>foo.tar.gz.directive.asc</tt>&rsquo; file might 
contain the
 single line:
-
-<pre class="example">     directory: bar/v1
-</pre>
-   <p>This directory line indicates that <samp><span 
class="file">foo.tar.gz</span></samp> and
-<samp><span class="file">foo.tar.gz.sig</span></samp> are part of package 
<code>bar</code>.  If you were to
-upload the triplet to <samp><span class="file">/incoming/ftp</span></samp>, 
and the system can
+</p>
+<div class="example">
+<pre class="example">directory: bar/v1
+</pre></div>
+
+<p>This directory line indicates that &lsquo;<tt>foo.tar.gz</tt>&rsquo; and
+&lsquo;<tt>foo.tar.gz.sig</tt>&rsquo; are part of package <code>bar</code>.  
If you were to
+upload the triplet to &lsquo;<tt>/incoming/ftp</tt>&rsquo;, and the system can
 positively authenticate the signatures, then the files
-<samp><span class="file">foo.tar.gz</span></samp> and <samp><span 
class="file">foo.tar.gz.sig</span></samp> will be placed in the
-directory <samp><span class="file">gnu/bar/v1</span></samp> of the 
<code>ftp.gnu.org</code> site.
-
-   <p>The directive file can be used to create currently non-existent
+&lsquo;<tt>foo.tar.gz</tt>&rsquo; and &lsquo;<tt>foo.tar.gz.sig</tt>&rsquo; 
will be placed in the
+directory &lsquo;<tt>gnu/bar/v1</tt>&rsquo; of the <code>ftp.gnu.org</code> 
site.
+</p>
+<p>The directive file can be used to create currently non-existent
 directory trees, as long as they are under the package directory for
 your package (in the example above, that is <code>bar</code>).
+</p>
+
+<p>
 
-   </body></html>
 
+</p>
+</body>
+</html>

Index: html_node/FTP-Upload-Directive-File-_002d-v1_002e1.html
===================================================================
RCS file: 
/web/www/www/prep/maintain/html_node/FTP-Upload-Directive-File-_002d-v1_002e1.html,v
retrieving revision 1.56
retrieving revision 1.57
diff -u -b -r1.56 -r1.57
--- html_node/FTP-Upload-Directive-File-_002d-v1_002e1.html     7 Sep 2011 
01:31:17 -0000       1.56
+++ html_node/FTP-Upload-Directive-File-_002d-v1_002e1.html     7 Sep 2011 
15:00:31 -0000       1.57
@@ -1,149 +1,191 @@
-<html lang="en">
-<head>
-<title>FTP Upload Directive File - v1.1 - Information for Maintainers of GNU 
Software</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="Information for Maintainers of GNU Software">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="Automated-FTP-Uploads.html#Automated-FTP-Uploads" 
title="Automated FTP Uploads">
-<link rel="prev" 
href="Automated-Upload-Procedure.html#Automated-Upload-Procedure" 
title="Automated Upload Procedure">
-<link rel="next" 
href="FTP-Upload-Directive-File-_002d-v1_002e0.html#FTP-Upload-Directive-File-_002d-v1_002e0"
 title="FTP Upload Directive File - v1.0">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home" 
title="Texinfo Homepage">
-<!--
-Information for maintainers of GNU software, last updated September 5, 2011.
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" 
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
+<!-- Information for maintainers of GNU software, last updated September 5, 
2011.
 
 Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
 2010, 2011 Free Software Foundation, Inc.
 
-     Permission is granted to copy, distribute and/or modify this
-     document under the terms of the GNU Free Documentation License,
-     Version 1.3 or any later version published by the Free Software
-     Foundation; with no Invariant Sections, with no Front-Cover Texts,
-     and with no Back-Cover Texts.  A copy of the license is included
-     in the section entitled ``GNU Free Documentation License''.
-   -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
-  pre.display { font-family:inherit }
-  pre.format  { font-family:inherit }
-  pre.smalldisplay { font-family:inherit; font-size:smaller }
-  pre.smallformat  { font-family:inherit; font-size:smaller }
-  pre.smallexample { font-size:smaller }
-  pre.smalllisp    { font-size:smaller }
-  span.sc    { font-variant:small-caps }
-  span.roman { font-family:serif; font-weight:normal; } 
-  span.sansserif { font-family:sans-serif; font-weight:normal; } 
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
+Texts.  A copy of the license is included in the section entitled
+"GNU Free Documentation License". -->
+<!-- Created by texi2html, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>Information for Maintainers of GNU Software: FTP Upload Directive File 
- v1.1</title>
+
+<meta name="description" content="Information for Maintainers of GNU Software: 
FTP Upload Directive File - v1.1">
+<meta name="keywords" content="Information for Maintainers of GNU Software: 
FTP Upload Directive File - v1.1">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="texi2html">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Automated-FTP-Uploads.html#Automated-FTP-Uploads" rel="up" 
title="Automated FTP Uploads">
+<link 
href="FTP-Upload-Directive-File-_002d-v1_002e0.html#FTP-Upload-Directive-File-_002d-v1_002e0"
 rel="next" title="FTP Upload Directive File - v1.0">
+<link href="Automated-Upload-Procedure.html#Automated-Upload-Procedure" 
rel="previous" title="Automated Upload Procedure">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smalllisp {margin-left: 3.2em}
+pre.display {font-family: serif}
+pre.format {font-family: serif}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: serif; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: serif; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:pre}
+span.nolinebreak {white-space:pre}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
 </head>
-<body>
-<div class="node">
-<a name="FTP-Upload-Directive-File---v1.1"></a>
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF" 
vlink="#800080" alink="#FF0000">
+
 <a name="FTP-Upload-Directive-File-_002d-v1_002e1"></a>
+<div class="header">
 <p>
-Next:&nbsp;<a rel="next" accesskey="n" 
href="FTP-Upload-Directive-File-_002d-v1_002e0.html#FTP-Upload-Directive-File-_002d-v1_002e0">FTP
 Upload Directive File - v1.0</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" 
href="Automated-Upload-Procedure.html#Automated-Upload-Procedure">Automated 
Upload Procedure</a>,
-Up:&nbsp;<a rel="up" accesskey="u" 
href="Automated-FTP-Uploads.html#Automated-FTP-Uploads">Automated FTP 
Uploads</a>
-<hr>
+Next: <a 
href="FTP-Upload-Directive-File-_002d-v1_002e0.html#FTP-Upload-Directive-File-_002d-v1_002e0"
 accesskey="n" rel="next">FTP Upload Directive File - v1.0</a>, Previous: <a 
href="Automated-Upload-Procedure.html#Automated-Upload-Procedure" accesskey="p" 
rel="previous">Automated Upload Procedure</a>, Up: <a 
href="Automated-FTP-Uploads.html#Automated-FTP-Uploads" accesskey="u" 
rel="up">Automated FTP Uploads</a> &nbsp; [<a href="index.html#SEC_Contents" 
title="Table of contents" rel="contents">Contents</a>][<a 
href="Index.html#Index" title="Index" rel="index">Index</a>]</p>
 </div>
+<hr>
+<a name="FTP-Upload-Directive-File-_002d-v1_002e1-1"></a>
+<h3 class="subsection">11.5.3 FTP Upload Directive File - v1.1</h3>
 
-<h4 class="subsection">11.5.3 FTP Upload Directive File - v1.1</h4>
-
-<p>The directive file name must end in <samp><span 
class="file">directive.asc</span></samp>.
-
-   <p>When part of a triplet, the directive file must always contain the
+<p>The directive file name must end in &lsquo;<tt>directive.asc</tt>&rsquo;.
+</p>
+<p>When part of a triplet, the directive file must always contain the
 directives <code>version</code>, <code>directory</code> and 
<code>filename</code>, as
-described. In addition, a 'comment' directive is allowed.
-
-   <p>The <code>version</code> directive must always have the value 
&lsquo;<samp><span class="samp">1.1</span></samp>&rsquo;.
-
-   <p>The <code>directory</code> directive specifies the final destination
-directory where the uploaded file and its <samp><span 
class="file">.sig</span></samp> companion are to
+described. In addition, a &rsquo;comment&rsquo; directive is allowed.
+</p>
+<p>The <code>version</code> directive must always have the value 
&lsquo;<samp>1.1</samp>&rsquo;.
+</p>
+<p>The <code>directory</code> directive specifies the final destination
+directory where the uploaded file and its &lsquo;<tt>.sig</tt>&rsquo; 
companion are to
 be placed.
-
-   <p>The <code>filename</code> directive must contain the name of the file to 
be
+</p>
+<p>The <code>filename</code> directive must contain the name of the file to be
 distributed (item&nbsp;(1) above).
-
-   <p>For example, as part of an uploaded triplet, a
-<samp><span class="file">foo.tar.gz.directive.asc</span></samp> file might 
contain these lines (before
+</p>
+<p>For example, as part of an uploaded triplet, a
+&lsquo;<tt>foo.tar.gz.directive.asc</tt>&rsquo; file might contain these lines 
(before
 being gpg clearsigned):
-
-<pre class="example">     version: 1.1
-     directory: bar/v1
-     filename: foo.tar.gz
-     comment: hello world!
-</pre>
-   <p>This directory line indicates that <samp><span 
class="file">foo.tar.gz</span></samp> and
-<samp><span class="file">foo.tar.gz.sig</span></samp> are part of package 
<code>bar</code>.  If you uploaded
-this triplet to <samp><span class="file">/incoming/ftp</span></samp> and the 
system positively
-authenticates the signatures, the files <samp><span 
class="file">foo.tar.gz</span></samp> and
-<samp><span class="file">foo.tar.gz.sig</span></samp> will be placed in the 
directory
-<samp><span class="file">gnu/bar/v1</span></samp> of the 
<code>ftp.gnu.org</code> site.
-
-   <p>The directive file can be used to create currently non-existent
+</p>
+<div class="example">
+<pre class="example">version: 1.1
+directory: bar/v1
+filename: foo.tar.gz
+comment: hello world!
+</pre></div>
+
+<p>This directory line indicates that &lsquo;<tt>foo.tar.gz</tt>&rsquo; and
+&lsquo;<tt>foo.tar.gz.sig</tt>&rsquo; are part of package <code>bar</code>.  
If you uploaded
+this triplet to &lsquo;<tt>/incoming/ftp</tt>&rsquo; and the system positively
+authenticates the signatures, the files &lsquo;<tt>foo.tar.gz</tt>&rsquo; and
+&lsquo;<tt>foo.tar.gz.sig</tt>&rsquo; will be placed in the directory
+&lsquo;<tt>gnu/bar/v1</tt>&rsquo; of the <code>ftp.gnu.org</code> site.
+</p>
+<p>The directive file can be used to create currently non-existent
 directory trees, as long as they are under the package directory for
 your package (in the example above, that is <code>bar</code>).
-
-   <p>If you upload a file that already exists in the FTP directory, the
+</p>
+<p>If you upload a file that already exists in the FTP directory, the
 original will simply be archived and replaced with the new upload.
-
-<h4 class="subheading">Standalone directives</h4>
+</p>
+<a name="Standalone-directives"></a>
+<h3 class="subheading">Standalone directives</h3>
 
 <p>When uploaded by itself, the directive file must contain one or more
 of the directives <code>symlink</code>, <code>rmsymlink</code> or 
<code>archive</code>,
 in addition to the obligatory <code>directory</code> and <code>version</code>
 directives.  A <code>filename</code> directive is not allowed, and a
 <code>comment</code> directive remains optional.
-
-   <p>If you use more than one directive, the directives are executed in the
+</p>
+<p>If you use more than one directive, the directives are executed in the
 sequence they are specified in.  If a directive results in an error,
 further execution of the upload is aborted.
-
-   <p>Removing a symbolic link (with <code>rmsymlink</code>) which does not 
exist
+</p>
+<p>Removing a symbolic link (with <code>rmsymlink</code>) which does not exist
 results in an error.  However, attempting to create a symbolic link
 that already exists (with <code>symlink</code>) is not an error.  In this
-case <code>symlink</code> behaves like the command <samp><span 
class="command">ln -s -f</span></samp>: any
+case <code>symlink</code> behaves like the command <code>ln -s -f</code>: any
 existing symlink is removed before creating the link.  (But an
 existing regular file or directory is not removed.)
+</p>
+<p>Here are a few examples.  The first removes a symlink:
+</p>
+<div class="example">
+<pre class="example">version: 1.1
+directory: bar/v1
+rmsymlink: foo-latest.tgz
+comment: remove a symlink
+</pre></div>
+
+<p>Archive an old file, taking it offline:
+</p>
+<div class="example">
+<pre class="example">version: 1.1
+directory: bar/v1
+archive: foo-1.1.tar.gz
+comment: archive an old file; it will not be
+comment: available through FTP any more.
+</pre></div>
+
+<p>Archive an old directory (with all contents), taking it offline:
+</p>
+<div class="example">
+<pre class="example">version: 1.1
+directory: bar/v1
+archive: foo
+comment: archive an old directory; it and its entire
+comment: contents will not be available through FTP anymore
+</pre></div>
+
+<p>Create a new symlink:
+</p>
+<div class="example">
+<pre class="example">version: 1.1
+directory: bar/v1
+symlink: foo-1.2.tar.gz foo-latest.tgz
+comment: create a new symlink
+</pre></div>
+
+<p>Do everything at once:
+</p>
+<div class="example">
+<pre class="example">version: 1.1
+directory: bar/v1
+rmsymlink: foo-latest.tgz
+symlink: foo-1.2.tar.gz foo-latest.tgz
+archive: foo-1.1.tar.gz
+comment: now do everything at once
+</pre></div>
 
-   <p>Here are a few examples.  The first removes a symlink:
 
-<pre class="example">     version: 1.1
-     directory: bar/v1
-     rmsymlink: foo-latest.tgz
-     comment: remove a symlink
-</pre>
-   <p class="noindent">Archive an old file, taking it offline:
-
-<pre class="example">     version: 1.1
-     directory: bar/v1
-     archive: foo-1.1.tar.gz
-     comment: archive an old file; it will not be
-     comment: available through FTP any more.
-</pre>
-   <p class="noindent">Archive an old directory (with all contents), taking it 
offline:
-
-<pre class="example">     version: 1.1
-     directory: bar/v1
-     archive: foo
-     comment: archive an old directory; it and its entire
-     comment: contents will not be available through FTP anymore
-</pre>
-   <p class="noindent">Create a new symlink:
-
-<pre class="example">     version: 1.1
-     directory: bar/v1
-     symlink: foo-1.2.tar.gz foo-latest.tgz
-     comment: create a new symlink
-</pre>
-   <p class="noindent">Do everything at once:
-
-<pre class="example">     version: 1.1
-     directory: bar/v1
-     rmsymlink: foo-latest.tgz
-     symlink: foo-1.2.tar.gz foo-latest.tgz
-     archive: foo-1.1.tar.gz
-     comment: now do everything at once
-</pre>
-   </body></html>
+<hr>
+<div class="header">
+<p>
+Next: <a 
href="FTP-Upload-Directive-File-_002d-v1_002e0.html#FTP-Upload-Directive-File-_002d-v1_002e0"
 accesskey="n" rel="next">FTP Upload Directive File - v1.0</a>, Previous: <a 
href="Automated-Upload-Procedure.html#Automated-Upload-Procedure" accesskey="p" 
rel="previous">Automated Upload Procedure</a>, Up: <a 
href="Automated-FTP-Uploads.html#Automated-FTP-Uploads" accesskey="u" 
rel="up">Automated FTP Uploads</a> &nbsp; [<a href="index.html#SEC_Contents" 
title="Table of contents" rel="contents">Contents</a>][<a 
href="Index.html#Index" title="Index" rel="index">Index</a>]</p>
+</div>
+<p>
+
 
+</p>
+</body>
+</html>

Index: html_node/Free-Software-Directory.html
===================================================================
RCS file: /web/www/www/prep/maintain/html_node/Free-Software-Directory.html,v
retrieving revision 1.66
retrieving revision 1.67
diff -u -b -r1.66 -r1.67
--- html_node/Free-Software-Directory.html      7 Sep 2011 01:31:17 -0000       
1.66
+++ html_node/Free-Software-Directory.html      7 Sep 2011 15:00:32 -0000       
1.67
@@ -1,60 +1,87 @@
-<html lang="en">
-<head>
-<title>Free Software Directory - Information for Maintainers of GNU 
Software</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="Information for Maintainers of GNU Software">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="prev" href="Donations.html#Donations" title="Donations">
-<link rel="next" 
href="Using-the-Proofreaders-List.html#Using-the-Proofreaders-List" 
title="Using the Proofreaders List">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home" 
title="Texinfo Homepage">
-<!--
-Information for maintainers of GNU software, last updated September 5, 2011.
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" 
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
+<!-- Information for maintainers of GNU software, last updated September 5, 
2011.
 
 Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
 2010, 2011 Free Software Foundation, Inc.
 
-     Permission is granted to copy, distribute and/or modify this
-     document under the terms of the GNU Free Documentation License,
-     Version 1.3 or any later version published by the Free Software
-     Foundation; with no Invariant Sections, with no Front-Cover Texts,
-     and with no Back-Cover Texts.  A copy of the license is included
-     in the section entitled ``GNU Free Documentation License''.
-   -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
-  pre.display { font-family:inherit }
-  pre.format  { font-family:inherit }
-  pre.smalldisplay { font-family:inherit; font-size:smaller }
-  pre.smallformat  { font-family:inherit; font-size:smaller }
-  pre.smallexample { font-size:smaller }
-  pre.smalllisp    { font-size:smaller }
-  span.sc    { font-variant:small-caps }
-  span.roman { font-family:serif; font-weight:normal; } 
-  span.sansserif { font-family:sans-serif; font-weight:normal; } 
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
+Texts.  A copy of the license is included in the section entitled
+"GNU Free Documentation License". -->
+<!-- Created by texi2html, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>Information for Maintainers of GNU Software: Free Software 
Directory</title>
+
+<meta name="description" content="Information for Maintainers of GNU Software: 
Free Software Directory">
+<meta name="keywords" content="Information for Maintainers of GNU Software: 
Free Software Directory">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="texi2html">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="index.html#Top" rel="up" title="Top">
+<link href="Using-the-Proofreaders-List.html#Using-the-Proofreaders-List" 
rel="next" title="Using the Proofreaders List">
+<link href="Donations.html#Donations" rel="previous" title="Donations">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smalllisp {margin-left: 3.2em}
+pre.display {font-family: serif}
+pre.format {font-family: serif}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: serif; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: serif; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:pre}
+span.nolinebreak {white-space:pre}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
 </head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF" 
vlink="#800080" alink="#FF0000">
+
 <a name="Free-Software-Directory"></a>
+<div class="header">
 <p>
-Next:&nbsp;<a rel="next" accesskey="n" 
href="Using-the-Proofreaders-List.html#Using-the-Proofreaders-List">Using the 
Proofreaders List</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" 
href="Donations.html#Donations">Donations</a>,
-Up:&nbsp;<a rel="up" accesskey="u" href="index.html#Top">Top</a>
-<hr>
+Next: <a href="Using-the-Proofreaders-List.html#Using-the-Proofreaders-List" 
accesskey="n" rel="next">Using the Proofreaders List</a>, Previous: <a 
href="Donations.html#Donations" accesskey="p" rel="previous">Donations</a>, Up: 
<a href="index.html#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a 
href="index.html#SEC_Contents" title="Table of contents" 
rel="contents">Contents</a>][<a href="Index.html#Index" title="Index" 
rel="index">Index</a>]</p>
 </div>
+<hr>
+<a name="Free-Software-Directory-1"></a>
+<h1 class="chapter">17 Free Software Directory</h1>
+<a name="index-Free-Software-Directory"></a>
+<a name="index-Directory_002c-Free-Software"></a>
 
-<h2 class="chapter">17 Free Software Directory</h2>
-
-<p><a name="index-Free-Software-Directory-94"></a><a 
name="index-Directory_002c-Free-Software-95"></a>
-The Free Software Directory aims to be a complete list of free
+<p>The Free Software Directory aims to be a complete list of free
 software packages, within certain criteria.  Every GNU package should
 be listed there, so please see
 <a 
href="http://www.gnu.org/help/directory.html#adding-entries";>http://www.gnu.org/help/directory.html#adding-entries</a>
 for
 information on how to write an entry for your package.  Contact
 <a href="mailto:address@hidden";>address@hidden</a> with any questions or 
suggestions for
 the Free Software Directory.
+</p>
+
+<p>
 
-   </body></html>
 
+</p>
+</body>
+</html>

Index: html_node/Free-Software-and-Open-Source.html
===================================================================
RCS file: 
/web/www/www/prep/maintain/html_node/Free-Software-and-Open-Source.html,v
retrieving revision 1.68
retrieving revision 1.69
diff -u -b -r1.68 -r1.69
--- html_node/Free-Software-and-Open-Source.html        7 Sep 2011 01:31:17 
-0000       1.68
+++ html_node/Free-Software-and-Open-Source.html        7 Sep 2011 15:00:33 
-0000       1.69
@@ -1,53 +1,78 @@
-<html lang="en">
-<head>
-<title>Free Software and Open Source - Information for Maintainers of GNU 
Software</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="Information for Maintainers of GNU Software">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="Terminology.html#Terminology" title="Terminology">
-<link rel="next" href="GNU-and-Linux.html#GNU-and-Linux" title="GNU and Linux">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home" 
title="Texinfo Homepage">
-<!--
-Information for maintainers of GNU software, last updated September 5, 2011.
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" 
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
+<!-- Information for maintainers of GNU software, last updated September 5, 
2011.
 
 Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
 2010, 2011 Free Software Foundation, Inc.
 
-     Permission is granted to copy, distribute and/or modify this
-     document under the terms of the GNU Free Documentation License,
-     Version 1.3 or any later version published by the Free Software
-     Foundation; with no Invariant Sections, with no Front-Cover Texts,
-     and with no Back-Cover Texts.  A copy of the license is included
-     in the section entitled ``GNU Free Documentation License''.
-   -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
-  pre.display { font-family:inherit }
-  pre.format  { font-family:inherit }
-  pre.smalldisplay { font-family:inherit; font-size:smaller }
-  pre.smallformat  { font-family:inherit; font-size:smaller }
-  pre.smallexample { font-size:smaller }
-  pre.smalllisp    { font-size:smaller }
-  span.sc    { font-variant:small-caps }
-  span.roman { font-family:serif; font-weight:normal; } 
-  span.sansserif { font-family:sans-serif; font-weight:normal; } 
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
+Texts.  A copy of the license is included in the section entitled
+"GNU Free Documentation License". -->
+<!-- Created by texi2html, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>Information for Maintainers of GNU Software: Free Software and Open 
Source</title>
+
+<meta name="description" content="Information for Maintainers of GNU Software: 
Free Software and Open Source">
+<meta name="keywords" content="Information for Maintainers of GNU Software: 
Free Software and Open Source">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="texi2html">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Terminology.html#Terminology" rel="up" title="Terminology">
+<link href="GNU-and-Linux.html#GNU-and-Linux" rel="next" title="GNU and Linux">
+<link href="Terminology.html#Terminology" rel="previous" title="Terminology">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smalllisp {margin-left: 3.2em}
+pre.display {font-family: serif}
+pre.format {font-family: serif}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: serif; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: serif; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:pre}
+span.nolinebreak {white-space:pre}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
 </head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF" 
vlink="#800080" alink="#FF0000">
+
 <a name="Free-Software-and-Open-Source"></a>
+<div class="header">
 <p>
-Next:&nbsp;<a rel="next" accesskey="n" 
href="GNU-and-Linux.html#GNU-and-Linux">GNU and Linux</a>,
-Up:&nbsp;<a rel="up" accesskey="u" 
href="Terminology.html#Terminology">Terminology</a>
-<hr>
+Next: <a href="GNU-and-Linux.html#GNU-and-Linux" accesskey="n" rel="next">GNU 
and Linux</a>, Up: <a href="Terminology.html#Terminology" accesskey="u" 
rel="up">Terminology</a> &nbsp; [<a href="index.html#SEC_Contents" title="Table 
of contents" rel="contents">Contents</a>][<a href="Index.html#Index" 
title="Index" rel="index">Index</a>]</p>
 </div>
+<hr>
+<a name="Free-Software-and-Open-Source-1"></a>
+<h2 class="section">14.1 Free Software and Open Source</h2>
+<a name="index-free-software-movement"></a>
+<a name="index-open-source"></a>
+<a name="index-movement_002c-free-software"></a>
+<a name="index-development-method_002c-open-source"></a>
 
-<h3 class="section">14.1 Free Software and Open Source</h3>
-
-<p><a name="index-free-software-movement-79"></a><a 
name="index-open-source-80"></a><a 
name="index-movement_002c-free-software-81"></a><a 
name="index-development-method_002c-open-source-82"></a>
-The terms &ldquo;free software&rdquo; and &ldquo;open source&rdquo;, while 
describing
+<p>The terms &ldquo;free software&rdquo; and &ldquo;open source&rdquo;, while 
describing
 almost the same category of software, stand for views based on
 fundamentally different values.  The free software movement is
 idealistic, and raises issues of freedom, ethics, principle and what
@@ -55,13 +80,13 @@
 associated with a philosophy which studiously avoids such questions. 
 For a detailed explanation, see
 <a 
href="http://www.gnu.org/philosophy/open-source-misses-the-point.html";>http://www.gnu.org/philosophy/open-source-misses-the-point.html</a>.
-
-   <p>The GNU Project is aligned with the free software movement.  This
-doesn't mean that all GNU contributors and maintainers have to agree;
-your views on these issues are up to you, and you're entitled to express
+</p>
+<p>The GNU Project is aligned with the free software movement.  This
+doesn&rsquo;t mean that all GNU contributors and maintainers have to agree;
+your views on these issues are up to you, and you&rsquo;re entitled to express
 them when speaking for yourself.
-
-   <p>However, due to the much greater publicity that the term &ldquo;open 
source&rdquo;
+</p>
+<p>However, due to the much greater publicity that the term &ldquo;open 
source&rdquo;
 receives, the GNU Project needs to overcome a widespread
 mistaken impression that GNU is <em>and always was</em> an &ldquo;open
 source&rdquo; activity.  For this reason, please use the term &ldquo;free
@@ -70,6 +95,11 @@
 role as the maintainer of a GNU package.  A reference to the URL given
 above, to explain the difference, is a useful thing to include as
 well.
+</p>
+
+<p>
 
-   </body></html>
 
+</p>
+</body>
+</html>

Index: html_node/Freedom-for-Web-Pages.html
===================================================================
RCS file: /web/www/www/prep/maintain/html_node/Freedom-for-Web-Pages.html,v
retrieving revision 1.25
retrieving revision 1.26
diff -u -b -r1.25 -r1.26
--- html_node/Freedom-for-Web-Pages.html        7 Sep 2011 01:31:18 -0000       
1.25
+++ html_node/Freedom-for-Web-Pages.html        7 Sep 2011 15:00:33 -0000       
1.26
@@ -1,70 +1,96 @@
-<html lang="en">
-<head>
-<title>Freedom for Web Pages - Information for Maintainers of GNU 
Software</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="Information for Maintainers of GNU Software">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="Web-Pages.html#Web-Pages" title="Web Pages">
-<link rel="prev" href="Hosting-for-Web-Pages.html#Hosting-for-Web-Pages" 
title="Hosting for Web Pages">
-<link rel="next" href="Manuals-on-Web-Pages.html#Manuals-on-Web-Pages" 
title="Manuals on Web Pages">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home" 
title="Texinfo Homepage">
-<!--
-Information for maintainers of GNU software, last updated September 5, 2011.
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" 
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
+<!-- Information for maintainers of GNU software, last updated September 5, 
2011.
 
 Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
 2010, 2011 Free Software Foundation, Inc.
 
-     Permission is granted to copy, distribute and/or modify this
-     document under the terms of the GNU Free Documentation License,
-     Version 1.3 or any later version published by the Free Software
-     Foundation; with no Invariant Sections, with no Front-Cover Texts,
-     and with no Back-Cover Texts.  A copy of the license is included
-     in the section entitled ``GNU Free Documentation License''.
-   -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
-  pre.display { font-family:inherit }
-  pre.format  { font-family:inherit }
-  pre.smalldisplay { font-family:inherit; font-size:smaller }
-  pre.smallformat  { font-family:inherit; font-size:smaller }
-  pre.smallexample { font-size:smaller }
-  pre.smalllisp    { font-size:smaller }
-  span.sc    { font-variant:small-caps }
-  span.roman { font-family:serif; font-weight:normal; } 
-  span.sansserif { font-family:sans-serif; font-weight:normal; } 
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
+Texts.  A copy of the license is included in the section entitled
+"GNU Free Documentation License". -->
+<!-- Created by texi2html, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>Information for Maintainers of GNU Software: Freedom for Web 
Pages</title>
+
+<meta name="description" content="Information for Maintainers of GNU Software: 
Freedom for Web Pages">
+<meta name="keywords" content="Information for Maintainers of GNU Software: 
Freedom for Web Pages">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="texi2html">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Web-Pages.html#Web-Pages" rel="up" title="Web Pages">
+<link href="Manuals-on-Web-Pages.html#Manuals-on-Web-Pages" rel="next" 
title="Manuals on Web Pages">
+<link href="Hosting-for-Web-Pages.html#Hosting-for-Web-Pages" rel="previous" 
title="Hosting for Web Pages">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smalllisp {margin-left: 3.2em}
+pre.display {font-family: serif}
+pre.format {font-family: serif}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: serif; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: serif; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:pre}
+span.nolinebreak {white-space:pre}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
 </head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF" 
vlink="#800080" alink="#FF0000">
+
 <a name="Freedom-for-Web-Pages"></a>
+<div class="header">
 <p>
-Next:&nbsp;<a rel="next" accesskey="n" 
href="Manuals-on-Web-Pages.html#Manuals-on-Web-Pages">Manuals on Web Pages</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" 
href="Hosting-for-Web-Pages.html#Hosting-for-Web-Pages">Hosting for Web 
Pages</a>,
-Up:&nbsp;<a rel="up" accesskey="u" href="Web-Pages.html#Web-Pages">Web 
Pages</a>
-<hr>
+Next: <a href="Manuals-on-Web-Pages.html#Manuals-on-Web-Pages" accesskey="n" 
rel="next">Manuals on Web Pages</a>, Previous: <a 
href="Hosting-for-Web-Pages.html#Hosting-for-Web-Pages" accesskey="p" 
rel="previous">Hosting for Web Pages</a>, Up: <a 
href="Web-Pages.html#Web-Pages" accesskey="u" rel="up">Web Pages</a> &nbsp; [<a 
href="index.html#SEC_Contents" title="Table of contents" 
rel="contents">Contents</a>][<a href="Index.html#Index" title="Index" 
rel="index">Index</a>]</p>
 </div>
-
-<h3 class="section">12.2 Freedom for Web Pages</h3>
+<hr>
+<a name="Freedom-for-Web-Pages-1"></a>
+<h2 class="section">12.2 Freedom for Web Pages</h2>
 
 <p>If you use a site other than <code>www.gnu.org</code>, please make sure that
 the site runs on free software alone.  (It is ok if the site uses
 unreleased custom software, since that is free in a trivial sense:
-there's only one user and it has the four freedoms.)  If the web site
+there&rsquo;s only one user and it has the four freedoms.)  If the web site
 for a GNU package runs on non-free software, the public will see this,
 and it will have the effect of granting legitimacy to the non-free
 program.
-
-   <p>If you use multiple sites, they should all follow that criterion. 
-Please don't link to a site that is about your package, which the
+</p>
+<p>If you use multiple sites, they should all follow that criterion.
+Please don&rsquo;t link to a site that is about your package, which the
 public might perceive as connected with it and reflecting the position
 of its developers, unless it follows that criterion.
-
-   <p>Historically, web pages for GNU packages did not include GIF images,
-because of patent problems (see <a 
href="Ethical-and-Philosophical-Consideration.html#Ethical-and-Philosophical-Consideration">Ethical
 and Philosophical Consideration</a>).  Although the GIF patents expired in 
2006, using GIF
+</p>
+<p>Historically, web pages for GNU packages did not include GIF images,
+because of patent problems (see <a 
href="Ethical-and-Philosophical-Consideration.html#Ethical-and-Philosophical-Consideration">Ethical
 and Philosophical
+Consideration</a>).  Although the GIF patents expired in 2006, using GIF
 images is still not recommended, as the PNG and JPEG formats are
 generally superior.  See <a 
href="http://www.gnu.org/philosophy/gif.html";>http://www.gnu.org/philosophy/gif.html</a>.
+</p>
+
+<p>
 
-   </body></html>
 
+</p>
+</body>
+</html>

Index: html_node/GNU-Free-Documentation-License.html
===================================================================
RCS file: 
/web/www/www/prep/maintain/html_node/GNU-Free-Documentation-License.html,v
retrieving revision 1.43
retrieving revision 1.44
diff -u -b -r1.43 -r1.44
--- html_node/GNU-Free-Documentation-License.html       7 Sep 2011 01:31:18 
-0000       1.43
+++ html_node/GNU-Free-Documentation-License.html       7 Sep 2011 15:00:33 
-0000       1.44
@@ -1,92 +1,112 @@
-<html lang="en">
-<head>
-<title>GNU Free Documentation License - Information for Maintainers of GNU 
Software</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="Information for Maintainers of GNU Software">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="prev" 
href="Using-the-Proofreaders-List.html#Using-the-Proofreaders-List" 
title="Using the Proofreaders List">
-<link rel="next" href="Index.html#Index" title="Index">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home" 
title="Texinfo Homepage">
-<!--
-Information for maintainers of GNU software, last updated September 5, 2011.
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" 
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
+<!-- Information for maintainers of GNU software, last updated September 5, 
2011.
 
 Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
 2010, 2011 Free Software Foundation, Inc.
 
-     Permission is granted to copy, distribute and/or modify this
-     document under the terms of the GNU Free Documentation License,
-     Version 1.3 or any later version published by the Free Software
-     Foundation; with no Invariant Sections, with no Front-Cover Texts,
-     and with no Back-Cover Texts.  A copy of the license is included
-     in the section entitled ``GNU Free Documentation License''.
-   -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
-  pre.display { font-family:inherit }
-  pre.format  { font-family:inherit }
-  pre.smalldisplay { font-family:inherit; font-size:smaller }
-  pre.smallformat  { font-family:inherit; font-size:smaller }
-  pre.smallexample { font-size:smaller }
-  pre.smalllisp    { font-size:smaller }
-  span.sc    { font-variant:small-caps }
-  span.roman { font-family:serif; font-weight:normal; } 
-  span.sansserif { font-family:sans-serif; font-weight:normal; } 
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
+Texts.  A copy of the license is included in the section entitled
+"GNU Free Documentation License". -->
+<!-- Created by texi2html, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>Information for Maintainers of GNU Software: GNU Free Documentation 
License</title>
+
+<meta name="description" content="Information for Maintainers of GNU Software: 
GNU Free Documentation License">
+<meta name="keywords" content="Information for Maintainers of GNU Software: 
GNU Free Documentation License">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="texi2html">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="index.html#Top" rel="up" title="Top">
+<link href="Index.html#Index" rel="next" title="Index">
+<link href="Using-the-Proofreaders-List.html#Using-the-Proofreaders-List" 
rel="previous" title="Using the Proofreaders List">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smalllisp {margin-left: 3.2em}
+pre.display {font-family: serif}
+pre.format {font-family: serif}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: serif; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: serif; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:pre}
+span.nolinebreak {white-space:pre}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
 </head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF" 
vlink="#800080" alink="#FF0000">
+
 <a name="GNU-Free-Documentation-License"></a>
+<div class="header">
 <p>
-Next:&nbsp;<a rel="next" accesskey="n" href="Index.html#Index">Index</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" 
href="Using-the-Proofreaders-List.html#Using-the-Proofreaders-List">Using the 
Proofreaders List</a>,
-Up:&nbsp;<a rel="up" accesskey="u" href="index.html#Top">Top</a>
-<hr>
+Next: <a href="Index.html#Index" accesskey="n" rel="next">Index</a>, Previous: 
<a href="Using-the-Proofreaders-List.html#Using-the-Proofreaders-List" 
accesskey="p" rel="previous">Using the Proofreaders List</a>, Up: <a 
href="index.html#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a 
href="index.html#SEC_Contents" title="Table of contents" 
rel="contents">Contents</a>][<a href="Index.html#Index" title="Index" 
rel="index">Index</a>]</p>
 </div>
+<hr>
+<a name="GNU-Free-Documentation-License-1"></a>
+<h1 class="appendix">Appendix A GNU Free Documentation License</h1>
 
-<h2 class="appendix">Appendix A GNU Free Documentation License</h2>
-
-<p><a name="index-FDL_002c-GNU-Free-Documentation-License-97"></a>
-
-<!-- The GNU Free Documentation License. -->
-<div align="center">Version 1.3, 3 November 2008</div>
+<a name="index-FDL_002c-GNU-Free-Documentation-License"></a>
+<p align="center">Version 1.3, 3 November 2008
+</p>
+
+<div class="display">
+<pre class="display">Copyright &copy; 2000, 2001, 2002, 2007, 2008 Free 
Software Foundation, Inc.
+<a href="http://fsf.org/";>http://fsf.org/</a>
+
+Everyone is permitted to copy and distribute verbatim copies
+of this license document, but changing it is not allowed.
+</pre></div>
 
-<!-- This file is intended to be included within another document, -->
-<!-- hence no sectioning command or @node. -->
-<pre class="display">     Copyright &copy; 2000, 2001, 2002, 2007, 2008 Free 
Software Foundation, Inc.
-     <a href="http://fsf.org/";>http://fsf.org/</a>
-     
-     Everyone is permitted to copy and distribute verbatim copies
-     of this license document, but changing it is not allowed.
-</pre>
-     <ol type=1 start=0>
-<li>PREAMBLE
+<ol>
+<li> PREAMBLE
 
-     <p>The purpose of this License is to make a manual, textbook, or other
-functional and useful document <dfn>free</dfn> in the sense of freedom: to
+<p>The purpose of this License is to make a manual, textbook, or other
+functional and useful document <em>free</em> in the sense of freedom: to
 assure everyone the effective freedom to copy and redistribute it,
 with or without modifying it, either commercially or noncommercially. 
 Secondarily, this License preserves for the author and publisher a way
 to get credit for their work, while not being considered responsible
 for modifications made by others.
-
-     <p>This License is a kind of &ldquo;copyleft&rdquo;, which means that 
derivative
+</p>
+<p>This License is a kind of &ldquo;copyleft&rdquo;, which means that 
derivative
 works of the document must themselves be free in the same sense.  It
 complements the GNU General Public License, which is a copyleft
 license designed for free software.
-
-     <p>We have designed this License in order to use it for manuals for free
+</p>
+<p>We have designed this License in order to use it for manuals for free
 software, because free software needs free documentation: a free
 program should come with manuals providing the same freedoms that the
 software does.  But this License is not limited to software manuals;
 it can be used for any textual work, regardless of subject matter or
 whether it is published as a printed book.  We recommend this License
 principally for works whose purpose is instruction or reference.
+</p>
+</li><li> APPLICABILITY AND DEFINITIONS
 
-     <li>APPLICABILITY AND DEFINITIONS
-
-     <p>This License applies to any manual or other work, in any medium, that
+<p>This License applies to any manual or other work, in any medium, that
 contains a notice placed by the copyright holder saying it can be
 distributed under the terms of this License.  Such a notice grants a
 world-wide, royalty-free license, unlimited in duration, to use that
@@ -95,14 +115,14 @@
 licensee, and is addressed as &ldquo;you&rdquo;.  You accept the license if you
 copy, modify or distribute the work in a way requiring permission
 under copyright law.
-
-     <p>A &ldquo;Modified Version&rdquo; of the Document means any work 
containing the
+</p>
+<p>A &ldquo;Modified Version&rdquo; of the Document means any work containing 
the
 Document or a portion of it, either copied verbatim, or with
 modifications and/or translated into another language.
-
-     <p>A &ldquo;Secondary Section&rdquo; is a named appendix or a 
front-matter section
+</p>
+<p>A &ldquo;Secondary Section&rdquo; is a named appendix or a front-matter 
section
 of the Document that deals exclusively with the relationship of the
-publishers or authors of the Document to the Document's overall
+publishers or authors of the Document to the Document&rsquo;s overall
 subject (or to related matters) and contains nothing that could fall
 directly within that overall subject.  (Thus, if the Document is in
 part a textbook of mathematics, a Secondary Section may not explain
@@ -110,21 +130,21 @@
 connection with the subject or with related matters, or of legal,
 commercial, philosophical, ethical or political position regarding
 them.
-
-     <p>The &ldquo;Invariant Sections&rdquo; are certain Secondary Sections 
whose titles
+</p>
+<p>The &ldquo;Invariant Sections&rdquo; are certain Secondary Sections whose 
titles
 are designated, as being those of Invariant Sections, in the notice
 that says that the Document is released under this License.  If a
 section does not fit the above definition of Secondary then it is not
 allowed to be designated as Invariant.  The Document may contain zero
 Invariant Sections.  If the Document does not identify any Invariant
 Sections then there are none.
-
-     <p>The &ldquo;Cover Texts&rdquo; are certain short passages of text that 
are listed,
+</p>
+<p>The &ldquo;Cover Texts&rdquo; are certain short passages of text that are 
listed,
 as Front-Cover Texts or Back-Cover Texts, in the notice that says that
 the Document is released under this License.  A Front-Cover Text may
 be at most 5 words, and a Back-Cover Text may be at most 25 words.
-
-     <p>A &ldquo;Transparent&rdquo; copy of the Document means a 
machine-readable copy,
+</p>
+<p>A &ldquo;Transparent&rdquo; copy of the Document means a machine-readable 
copy,
 represented in a format whose specification is available to the
 general public, that is suitable for revising the document
 straightforwardly with generic text editors or (for images composed of
@@ -136,8 +156,8 @@
 or discourage subsequent modification by readers is not Transparent. 
 An image format is not Transparent if used for any substantial amount
 of text.  A copy that is not &ldquo;Transparent&rdquo; is called 
&ldquo;Opaque&rdquo;.
-
-     <p>Examples of suitable formats for Transparent copies include plain
+</p>
+<p>Examples of suitable formats for Transparent copies include plain
 ASCII without markup, Texinfo input format, LaTeX input
 format, SGML or XML using a publicly available
 DTD, and standard-conforming simple HTML,
@@ -149,35 +169,35 @@
 not generally available, and the machine-generated HTML,
 PostScript or PDF produced by some word processors for
 output purposes only.
-
-     <p>The &ldquo;Title Page&rdquo; means, for a printed book, the title page 
itself,
+</p>
+<p>The &ldquo;Title Page&rdquo; means, for a printed book, the title page 
itself,
 plus such following pages as are needed to hold, legibly, the material
 this License requires to appear in the title page.  For works in
 formats which do not have any title page as such, &ldquo;Title Page&rdquo; 
means
-the text near the most prominent appearance of the work's title,
+the text near the most prominent appearance of the work&rsquo;s title,
 preceding the beginning of the body of the text.
-
-     <p>The &ldquo;publisher&rdquo; means any person or entity that 
distributes copies
+</p>
+<p>The &ldquo;publisher&rdquo; means any person or entity that distributes 
copies
 of the Document to the public.
-
-     <p>A section &ldquo;Entitled XYZ&rdquo; means a named subunit of the 
Document whose
+</p>
+<p>A section &ldquo;Entitled XYZ&rdquo; means a named subunit of the Document 
whose
 title either is precisely XYZ or contains XYZ in parentheses following
 text that translates XYZ in another language.  (Here XYZ stands for a
 specific section name mentioned below, such as &ldquo;Acknowledgements&rdquo;,
 &ldquo;Dedications&rdquo;, &ldquo;Endorsements&rdquo;, or 
&ldquo;History&rdquo;.)  To &ldquo;Preserve the Title&rdquo;
 of such a section when you modify the Document means that it remains a
 section &ldquo;Entitled XYZ&rdquo; according to this definition.
-
-     <p>The Document may include Warranty Disclaimers next to the notice which
+</p>
+<p>The Document may include Warranty Disclaimers next to the notice which
 states that this License applies to the Document.  These Warranty
 Disclaimers are considered to be included by reference in this
 License, but only as regards disclaiming warranties: any other
 implication that these Warranty Disclaimers may have is void and has
 no effect on the meaning of this License.
+</p>
+</li><li> VERBATIM COPYING
 
-     <li>VERBATIM COPYING
-
-     <p>You may copy and distribute the Document in any medium, either
+<p>You may copy and distribute the Document in any medium, either
 commercially or noncommercially, provided that this License, the
 copyright notices, and the license notice saying this License applies
 to the Document are reproduced in all copies, and that you add no other
@@ -186,15 +206,15 @@
 copying of the copies you make or distribute.  However, you may accept
 compensation in exchange for copies.  If you distribute a large enough
 number of copies you must also follow the conditions in section 3.
-
-     <p>You may also lend copies, under the same conditions stated above, and
+</p>
+<p>You may also lend copies, under the same conditions stated above, and
 you may publicly display copies.
+</p>
+</li><li> COPYING IN QUANTITY
 
-     <li>COPYING IN QUANTITY
-
-     <p>If you publish printed copies (or copies in media that commonly have
+<p>If you publish printed copies (or copies in media that commonly have
 printed covers) of the Document, numbering more than 100, and the
-Document's license notice requires Cover Texts, you must enclose the
+Document&rsquo;s license notice requires Cover Texts, you must enclose the
 copies in covers that carry, clearly and legibly, all these Cover
 Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on
 the back cover.  Both covers must also clearly and legibly identify
@@ -204,13 +224,13 @@
 Copying with changes limited to the covers, as long as they preserve
 the title of the Document and satisfy these conditions, can be treated
 as verbatim copying in other respects.
-
-     <p>If the required texts for either cover are too voluminous to fit
+</p>
+<p>If the required texts for either cover are too voluminous to fit
 legibly, you should put the first ones listed (as many as fit
 reasonably) on the actual cover, and continue the rest onto adjacent
 pages.
-
-     <p>If you publish or distribute Opaque copies of the Document numbering
+</p>
+<p>If you publish or distribute Opaque copies of the Document numbering
 more than 100, you must either include a machine-readable Transparent
 copy along with each Opaque copy, or state in or with each Opaque copy
 a computer-network location from which the general network-using
@@ -222,51 +242,51 @@
 location until at least one year after the last time you distribute an
 Opaque copy (directly or through your agents or retailers) of that
 edition to the public.
-
-     <p>It is requested, but not required, that you contact the authors of the
+</p>
+<p>It is requested, but not required, that you contact the authors of the
 Document well before redistributing any large number of copies, to give
 them a chance to provide you with an updated version of the Document.
+</p>
+</li><li> MODIFICATIONS
 
-     <li>MODIFICATIONS
-
-     <p>You may copy and distribute a Modified Version of the Document under
+<p>You may copy and distribute a Modified Version of the Document under
 the conditions of sections 2 and 3 above, provided that you release
 the Modified Version under precisely this License, with the Modified
 Version filling the role of the Document, thus licensing distribution
 and modification of the Modified Version to whoever possesses a copy
 of it.  In addition, you must do these things in the Modified Version:
-
-          <ol type=A start=1>
-<li>Use in the Title Page (and on the covers, if any) a title distinct
+</p>
+<ol>
+<li> Use in the Title Page (and on the covers, if any) a title distinct
 from that of the Document, and from those of previous versions
 (which should, if there were any, be listed in the History section
 of the Document).  You may use the same title as a previous version
 if the original publisher of that version gives permission.
 
-          <li>List on the Title Page, as authors, one or more persons or 
entities
+</li><li> List on the Title Page, as authors, one or more persons or entities
 responsible for authorship of the modifications in the Modified
 Version, together with at least five of the principal authors of the
 Document (all of its principal authors, if it has fewer than five),
 unless they release you from this requirement.
 
-          <li>State on the Title page the name of the publisher of the
+</li><li> State on the Title page the name of the publisher of the
 Modified Version, as the publisher.
 
-          <li>Preserve all the copyright notices of the Document.
+</li><li> Preserve all the copyright notices of the Document.
 
-          <li>Add an appropriate copyright notice for your modifications
+</li><li> Add an appropriate copyright notice for your modifications
 adjacent to the other copyright notices.
 
-          <li>Include, immediately after the copyright notices, a license 
notice
+</li><li> Include, immediately after the copyright notices, a license notice
 giving the public permission to use the Modified Version under the
 terms of this License, in the form shown in the Addendum below.
 
-          <li>Preserve in that license notice the full lists of Invariant 
Sections
-and required Cover Texts given in the Document's license notice.
+</li><li> Preserve in that license notice the full lists of Invariant Sections
+and required Cover Texts given in the Document&rsquo;s license notice.
 
-          <li>Include an unaltered copy of this License.
+</li><li> Include an unaltered copy of this License.
 
-          <li>Preserve the section Entitled &ldquo;History&rdquo;, Preserve 
its Title, and add
+</li><li> Preserve the section Entitled &ldquo;History&rdquo;, Preserve its 
Title, and add
 to it an item stating at least the title, year, new authors, and
 publisher of the Modified Version as given on the Title Page.  If
 there is no section Entitled &ldquo;History&rdquo; in the Document, create one
@@ -274,7 +294,7 @@
 given on its Title Page, then add an item describing the Modified
 Version as stated in the previous sentence.
 
-          <li>Preserve the network location, if any, given in the Document for
+</li><li> Preserve the network location, if any, given in the Document for
 public access to a Transparent copy of the Document, and likewise
 the network locations given in the Document for previous versions
 it was based on.  These may be placed in the &ldquo;History&rdquo; section. 
@@ -282,38 +302,38 @@
 least four years before the Document itself, or if the original
 publisher of the version it refers to gives permission.
 
-          <li>For any section Entitled &ldquo;Acknowledgements&rdquo; or 
&ldquo;Dedications&rdquo;, Preserve
+</li><li> For any section Entitled &ldquo;Acknowledgements&rdquo; or 
&ldquo;Dedications&rdquo;, Preserve
 the Title of the section, and preserve in the section all the
 substance and tone of each of the contributor acknowledgements and/or
 dedications given therein.
 
-          <li>Preserve all the Invariant Sections of the Document,
+</li><li> Preserve all the Invariant Sections of the Document,
 unaltered in their text and in their titles.  Section numbers
 or the equivalent are not considered part of the section titles.
 
-          <li>Delete any section Entitled &ldquo;Endorsements&rdquo;.  Such a 
section
+</li><li> Delete any section Entitled &ldquo;Endorsements&rdquo;.  Such a 
section
 may not be included in the Modified Version.
 
-          <li>Do not retitle any existing section to be Entitled 
&ldquo;Endorsements&rdquo; or
+</li><li> Do not retitle any existing section to be Entitled 
&ldquo;Endorsements&rdquo; or
 to conflict in title with any Invariant Section.
 
-          <li>Preserve any Warranty Disclaimers.
-          </ol>
+</li><li> Preserve any Warranty Disclaimers.
+</li></ol>
 
-     <p>If the Modified Version includes new front-matter sections or
+<p>If the Modified Version includes new front-matter sections or
 appendices that qualify as Secondary Sections and contain no material
 copied from the Document, you may at your option designate some or all
 of these sections as invariant.  To do this, add their titles to the
-list of Invariant Sections in the Modified Version's license notice. 
+list of Invariant Sections in the Modified Version&rsquo;s license notice.
 These titles must be distinct from any other section titles.
-
-     <p>You may add a section Entitled &ldquo;Endorsements&rdquo;, provided it 
contains
+</p>
+<p>You may add a section Entitled &ldquo;Endorsements&rdquo;, provided it 
contains
 nothing but endorsements of your Modified Version by various
 parties&mdash;for example, statements of peer review or that the text has
 been approved by an organization as the authoritative definition of a
 standard.
-
-     <p>You may add a passage of up to five words as a Front-Cover Text, and a
+</p>
+<p>You may add a passage of up to five words as a Front-Cover Text, and a
 passage of up to 25 words as a Back-Cover Text, to the end of the list
 of Cover Texts in the Modified Version.  Only one passage of
 Front-Cover Text and one of Back-Cover Text may be added by (or
@@ -322,21 +342,21 @@
 by arrangement made by the same entity you are acting on behalf of,
 you may not add another; but you may replace the old one, on explicit
 permission from the previous publisher that added the old one.
-
-     <p>The author(s) and publisher(s) of the Document do not by this License
+</p>
+<p>The author(s) and publisher(s) of the Document do not by this License
 give permission to use their names for publicity for or to assert or
 imply endorsement of any Modified Version.
+</p>
+</li><li> COMBINING DOCUMENTS
 
-     <li>COMBINING DOCUMENTS
-
-     <p>You may combine the Document with other documents released under this
+<p>You may combine the Document with other documents released under this
 License, under the terms defined in section 4 above for modified
 versions, provided that you include in the combination all of the
 Invariant Sections of all of the original documents, unmodified, and
 list them all as Invariant Sections of your combined work in its
 license notice, and that you preserve all their Warranty Disclaimers.
-
-     <p>The combined work need only contain one copy of this License, and
+</p>
+<p>The combined work need only contain one copy of this License, and
 multiple identical Invariant Sections may be replaced with a single
 copy.  If there are multiple Invariant Sections with the same name but
 different contents, make the title of each such section unique by
@@ -344,48 +364,48 @@
 author or publisher of that section if known, or else a unique number. 
 Make the same adjustment to the section titles in the list of
 Invariant Sections in the license notice of the combined work.
-
-     <p>In the combination, you must combine any sections Entitled 
&ldquo;History&rdquo;
+</p>
+<p>In the combination, you must combine any sections Entitled 
&ldquo;History&rdquo;
 in the various original documents, forming one section Entitled
 &ldquo;History&rdquo;; likewise combine any sections Entitled 
&ldquo;Acknowledgements&rdquo;,
 and any sections Entitled &ldquo;Dedications&rdquo;.  You must delete all
 sections Entitled &ldquo;Endorsements.&rdquo;
+</p>
+</li><li> COLLECTIONS OF DOCUMENTS
 
-     <li>COLLECTIONS OF DOCUMENTS
-
-     <p>You may make a collection consisting of the Document and other 
documents
+<p>You may make a collection consisting of the Document and other documents
 released under this License, and replace the individual copies of this
 License in the various documents with a single copy that is included in
 the collection, provided that you follow the rules of this License for
 verbatim copying of each of the documents in all other respects.
-
-     <p>You may extract a single document from such a collection, and 
distribute
+</p>
+<p>You may extract a single document from such a collection, and distribute
 it individually under this License, provided you insert a copy of this
 License into the extracted document, and follow this License in all
 other respects regarding verbatim copying of that document.
+</p>
+</li><li> AGGREGATION WITH INDEPENDENT WORKS
 
-     <li>AGGREGATION WITH INDEPENDENT WORKS
-
-     <p>A compilation of the Document or its derivatives with other separate
+<p>A compilation of the Document or its derivatives with other separate
 and independent documents or works, in or on a volume of a storage or
 distribution medium, is called an &ldquo;aggregate&rdquo; if the copyright
 resulting from the compilation is not used to limit the legal rights
-of the compilation's users beyond what the individual works permit. 
+of the compilation&rsquo;s users beyond what the individual works permit.
 When the Document is included in an aggregate, this License does not
 apply to the other works in the aggregate which are not themselves
 derivative works of the Document.
-
-     <p>If the Cover Text requirement of section 3 is applicable to these
+</p>
+<p>If the Cover Text requirement of section 3 is applicable to these
 copies of the Document, then if the Document is less than one half of
-the entire aggregate, the Document's Cover Texts may be placed on
+the entire aggregate, the Document&rsquo;s Cover Texts may be placed on
 covers that bracket the Document within the aggregate, or the
 electronic equivalent of covers if the Document is in electronic form. 
 Otherwise they must appear on printed covers that bracket the whole
 aggregate.
+</p>
+</li><li> TRANSLATION
 
-     <li>TRANSLATION
-
-     <p>Translation is considered a kind of modification, so you may
+<p>Translation is considered a kind of modification, so you may
 distribute translations of the Document under the terms of section 4. 
 Replacing Invariant Sections with translations requires special
 permission from their copyright holders, but you may include
@@ -397,48 +417,48 @@
 of those notices and disclaimers.  In case of a disagreement between
 the translation and the original version of this License or a notice
 or disclaimer, the original version will prevail.
-
-     <p>If a section in the Document is Entitled 
&ldquo;Acknowledgements&rdquo;,
+</p>
+<p>If a section in the Document is Entitled &ldquo;Acknowledgements&rdquo;,
 &ldquo;Dedications&rdquo;, or &ldquo;History&rdquo;, the requirement (section 
4) to Preserve
 its Title (section 1) will typically require changing the actual
 title.
+</p>
+</li><li> TERMINATION
 
-     <li>TERMINATION
-
-     <p>You may not copy, modify, sublicense, or distribute the Document
+<p>You may not copy, modify, sublicense, or distribute the Document
 except as expressly provided under this License.  Any attempt
 otherwise to copy, modify, sublicense, or distribute it is void, and
 will automatically terminate your rights under this License.
-
-     <p>However, if you cease all violation of this License, then your license
+</p>
+<p>However, if you cease all violation of this License, then your license
 from a particular copyright holder is reinstated (a) provisionally,
 unless and until the copyright holder explicitly and finally
 terminates your license, and (b) permanently, if the copyright holder
 fails to notify you of the violation by some reasonable means prior to
 60 days after the cessation.
-
-     <p>Moreover, your license from a particular copyright holder is
+</p>
+<p>Moreover, your license from a particular copyright holder is
 reinstated permanently if the copyright holder notifies you of the
 violation by some reasonable means, this is the first time you have
 received notice of violation of this License (for any work) from that
 copyright holder, and you cure the violation prior to 30 days after
 your receipt of the notice.
-
-     <p>Termination of your rights under this section does not terminate the
+</p>
+<p>Termination of your rights under this section does not terminate the
 licenses of parties who have received copies or rights from you under
 this License.  If your rights have been terminated and not permanently
 reinstated, receipt of a copy of some or all of the same material does
 not give you any rights to use it.
+</p>
+</li><li> FUTURE REVISIONS OF THIS LICENSE
 
-     <li>FUTURE REVISIONS OF THIS LICENSE
-
-     <p>The Free Software Foundation may publish new, revised versions
+<p>The Free Software Foundation may publish new, revised versions
 of the GNU Free Documentation License from time to time.  Such new
 versions will be similar in spirit to the present version, but may
 differ in detail to address new problems or concerns.  See
 <a href="http://www.gnu.org/copyleft/";>http://www.gnu.org/copyleft/</a>.
-
-     <p>Each version of the License is given a distinguishing version number. 
+</p>
+<p>Each version of the License is given a distinguishing version number.
 If the Document specifies that a particular numbered version of this
 License &ldquo;or any later version&rdquo; applies to it, you have the option 
of
 following the terms and conditions either of that specified version or
@@ -447,47 +467,49 @@
 number of this License, you may choose any version ever published (not
 as a draft) by the Free Software Foundation.  If the Document
 specifies that a proxy can decide which future versions of this
-License can be used, that proxy's public statement of acceptance of a
+License can be used, that proxy&rsquo;s public statement of acceptance of a
 version permanently authorizes you to choose that version for the
 Document.
+</p>
+</li><li> RELICENSING
 
-     <li>RELICENSING
-
-     <p>&ldquo;Massive Multiauthor Collaboration Site&rdquo; (or &ldquo;MMC 
Site&rdquo;) means any
+<p>&ldquo;Massive Multiauthor Collaboration Site&rdquo; (or &ldquo;MMC 
Site&rdquo;) means any
 World Wide Web server that publishes copyrightable works and also
 provides prominent facilities for anybody to edit those works.  A
 public wiki that anybody can edit is an example of such a server.  A
 &ldquo;Massive Multiauthor Collaboration&rdquo; (or &ldquo;MMC&rdquo;) 
contained in the
 site means any set of copyrightable works thus published on the MMC
 site.
-
-     <p>&ldquo;CC-BY-SA&rdquo; means the Creative Commons Attribution-Share 
Alike 3.0
+</p>
+<p>&ldquo;CC-BY-SA&rdquo; means the Creative Commons Attribution-Share Alike 
3.0
 license published by Creative Commons Corporation, a not-for-profit
 corporation with a principal place of business in San Francisco,
 California, as well as future copyleft versions of that license
 published by that same organization.
-
-     <p>&ldquo;Incorporate&rdquo; means to publish or republish a Document, in 
whole or
+</p>
+<p>&ldquo;Incorporate&rdquo; means to publish or republish a Document, in 
whole or
 in part, as part of another Document.
-
-     <p>An MMC is &ldquo;eligible for relicensing&rdquo; if it is licensed 
under this
+</p>
+<p>An MMC is &ldquo;eligible for relicensing&rdquo; if it is licensed under 
this
 License, and if all works that were first published under this License
 somewhere other than this MMC, and subsequently incorporated in whole
 or in part into the MMC, (1) had no cover texts or invariant sections,
 and (2) were thus incorporated prior to November 1, 2008.
-
-     <p>The operator of an MMC Site may republish an MMC contained in the site
+</p>
+<p>The operator of an MMC Site may republish an MMC contained in the site
 under CC-BY-SA on the same site at any time before August 1, 2009,
 provided the MMC is eligible for relicensing.
+</p>
+</li></ol>
 
-        </ol>
-
-<h3 class="heading">ADDENDUM: How to use this License for your documents</h3>
+<a name="ADDENDUM_003a-How-to-use-this-License-for-your-documents"></a>
+<h2 class="heading">ADDENDUM: How to use this License for your documents</h2>
 
 <p>To use this License in a document you have written, include a copy of
 the License in the document and put the following copyright and
 license notices just after the title page:
-
+</p>
+<div class="smallexample">
 <pre class="smallexample">       Copyright (C)  <var>year</var>  <var>your 
name</var>.
        Permission is granted to copy, distribute and/or modify this document
        under the terms of the GNU Free Documentation License, Version 1.3
@@ -495,25 +517,37 @@
        with no Invariant Sections, no Front-Cover Texts, and no Back-Cover
        Texts.  A copy of the license is included in the section entitled ``GNU
        Free Documentation License''.
-</pre>
-   <p>If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts,
-replace the &ldquo;with<small class="dots">...</small>Texts.&rdquo; line with 
this:
+</pre></div>
 
+<p>If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts,
+replace the &ldquo;with&hellip;Texts.&rdquo; line with this:
+</p>
+<div class="smallexample">
 <pre class="smallexample">         with the Invariant Sections being <var>list 
their titles</var>, with
          the Front-Cover Texts being <var>list</var>, and with the Back-Cover 
Texts
          being <var>list</var>.
-</pre>
-   <p>If you have Invariant Sections without Cover Texts, or some other
+</pre></div>
+
+<p>If you have Invariant Sections without Cover Texts, or some other
 combination of the three, merge those two alternatives to suit the
 situation.
-
-   <p>If your document contains nontrivial examples of program code, we
+</p>
+<p>If your document contains nontrivial examples of program code, we
 recommend releasing these examples in parallel under your choice of
 free software license, such as the GNU General Public License,
 to permit their use in free software.
+</p>
+
+
+
+<hr>
+<div class="header">
+<p>
+Next: <a href="Index.html#Index" accesskey="n" rel="next">Index</a>, Previous: 
<a href="Using-the-Proofreaders-List.html#Using-the-Proofreaders-List" 
accesskey="p" rel="previous">Using the Proofreaders List</a>, Up: <a 
href="index.html#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a 
href="index.html#SEC_Contents" title="Table of contents" 
rel="contents">Contents</a>][<a href="Index.html#Index" title="Index" 
rel="index">Index</a>]</p>
+</div>
+<p>
 
-<!-- Local Variables: -->
-<!-- ispell-local-pdict: "ispell-dict" -->
-<!-- End: -->
-   </body></html>
 
+</p>
+</body>
+</html>

Index: html_node/GNU-and-Linux.html
===================================================================
RCS file: /web/www/www/prep/maintain/html_node/GNU-and-Linux.html,v
retrieving revision 1.66
retrieving revision 1.67
diff -u -b -r1.66 -r1.67
--- html_node/GNU-and-Linux.html        7 Sep 2011 01:31:18 -0000       1.66
+++ html_node/GNU-and-Linux.html        7 Sep 2011 15:00:34 -0000       1.67
@@ -1,83 +1,116 @@
-<html lang="en">
-<head>
-<title>GNU and Linux - Information for Maintainers of GNU Software</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="Information for Maintainers of GNU Software">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="Terminology.html#Terminology" title="Terminology">
-<link rel="prev" 
href="Free-Software-and-Open-Source.html#Free-Software-and-Open-Source" 
title="Free Software and Open Source">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home" 
title="Texinfo Homepage">
-<!--
-Information for maintainers of GNU software, last updated September 5, 2011.
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" 
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
+<!-- Information for maintainers of GNU software, last updated September 5, 
2011.
 
 Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
 2010, 2011 Free Software Foundation, Inc.
 
-     Permission is granted to copy, distribute and/or modify this
-     document under the terms of the GNU Free Documentation License,
-     Version 1.3 or any later version published by the Free Software
-     Foundation; with no Invariant Sections, with no Front-Cover Texts,
-     and with no Back-Cover Texts.  A copy of the license is included
-     in the section entitled ``GNU Free Documentation License''.
-   -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
-  pre.display { font-family:inherit }
-  pre.format  { font-family:inherit }
-  pre.smalldisplay { font-family:inherit; font-size:smaller }
-  pre.smallformat  { font-family:inherit; font-size:smaller }
-  pre.smallexample { font-size:smaller }
-  pre.smalllisp    { font-size:smaller }
-  span.sc    { font-variant:small-caps }
-  span.roman { font-family:serif; font-weight:normal; } 
-  span.sansserif { font-family:sans-serif; font-weight:normal; } 
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
+Texts.  A copy of the license is included in the section entitled
+"GNU Free Documentation License". -->
+<!-- Created by texi2html, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>Information for Maintainers of GNU Software: GNU and Linux</title>
+
+<meta name="description" content="Information for Maintainers of GNU Software: 
GNU and Linux">
+<meta name="keywords" content="Information for Maintainers of GNU Software: 
GNU and Linux">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="texi2html">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Terminology.html#Terminology" rel="up" title="Terminology">
+<link href="Hosting.html#Hosting" rel="next" title="Hosting">
+<link href="Free-Software-and-Open-Source.html#Free-Software-and-Open-Source" 
rel="previous" title="Free Software and Open Source">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smalllisp {margin-left: 3.2em}
+pre.display {font-family: serif}
+pre.format {font-family: serif}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: serif; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: serif; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:pre}
+span.nolinebreak {white-space:pre}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
 </head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF" 
vlink="#800080" alink="#FF0000">
+
 <a name="GNU-and-Linux"></a>
+<div class="header">
 <p>
-Previous:&nbsp;<a rel="previous" accesskey="p" 
href="Free-Software-and-Open-Source.html#Free-Software-and-Open-Source">Free 
Software and Open Source</a>,
-Up:&nbsp;<a rel="up" accesskey="u" 
href="Terminology.html#Terminology">Terminology</a>
-<hr>
+Previous: <a 
href="Free-Software-and-Open-Source.html#Free-Software-and-Open-Source" 
accesskey="p" rel="previous">Free Software and Open Source</a>, Up: <a 
href="Terminology.html#Terminology" accesskey="u" rel="up">Terminology</a> 
&nbsp; [<a href="index.html#SEC_Contents" title="Table of contents" 
rel="contents">Contents</a>][<a href="Index.html#Index" title="Index" 
rel="index">Index</a>]</p>
 </div>
+<hr>
+<a name="GNU-and-Linux-1"></a>
+<h2 class="section">14.2 GNU and Linux</h2>
+<a name="index-Linux"></a>
+<a name="index-GNU_002fLinux"></a>
 
-<h3 class="section">14.2 GNU and Linux</h3>
-
-<p><a name="index-Linux-83"></a><a name="index-GNU_002fLinux-84"></a>
-The GNU Project was formed to develop a free Unix-like operating system,
+<p>The GNU Project was formed to develop a free Unix-like operating system,
 GNU.  The existence of this system is our major accomplishment. 
 However, the widely used version of the GNU system, in which Linux is
 used as the kernel, is often called simply &ldquo;Linux&rdquo;.  As a result, 
most
-users don't know about the GNU Project's major accomplishment&mdash;or more
-precisely, they know about it, but don't realize it is the GNU Project's
+users don&rsquo;t know about the GNU Project&rsquo;s major 
accomplishment&mdash;or more
+precisely, they know about it, but don&rsquo;t realize it is the GNU 
Project&rsquo;s
 accomplishment and reason for existence.  Even people who believe they
 know the real history often believe that the goal of GNU was to develop
 &ldquo;tools&rdquo; or &ldquo;utilities.&rdquo;
-
-   <p>To correct this confusion, we have made a years-long effort to
+</p>
+<p>To correct this confusion, we have made a years-long effort to
 distinguish between Linux, the kernel that Linus Torvalds wrote, and
 GNU/Linux, the operating system that is the combination of GNU and
 Linux.  The resulting increased awareness of what the GNU Project has
 already done helps every activity of the GNU Project recruit more
 support and contributors.
-
-   <p>Please make this distinction consistently in GNU software releases, GNU
+</p>
+<p>Please make this distinction consistently in GNU software releases, GNU
 documentation, and announcements and articles that you publish in your
 role as the maintainer of a GNU package.  If you want to explain the
 terminology and its reasons, you can refer to the URL
 <a 
href="http://www.gnu.org/gnu/linux-and-gnu.html";>http://www.gnu.org/gnu/linux-and-gnu.html</a>.
-
-   <p>To contrast the GNU system properly with respect to GNU/Linux, you can
+</p>
+<p>To contrast the GNU system properly with respect to GNU/Linux, you can
 call it &ldquo;GNU/Hurd&rdquo; or &ldquo;the GNU/Hurd system.&rdquo;  However, 
when that
 contrast is not specifically the focus, please call it just &ldquo;GNU&rdquo; 
or
 &ldquo;the GNU system.&rdquo;
-
-   <p>When referring to the collection of servers that is the higher level
+</p>
+<p>When referring to the collection of servers that is the higher level
 of the GNU kernel, please call it &ldquo;the Hurd&rdquo; or &ldquo;the GNU 
Hurd.&rdquo;
 Note that this uses a space, not a slash.
+</p>
+
+<hr>
+<div class="header">
+<p>
+Previous: <a 
href="Free-Software-and-Open-Source.html#Free-Software-and-Open-Source" 
accesskey="p" rel="previous">Free Software and Open Source</a>, Up: <a 
href="Terminology.html#Terminology" accesskey="u" rel="up">Terminology</a> 
&nbsp; [<a href="index.html#SEC_Contents" title="Table of contents" 
rel="contents">Contents</a>][<a href="Index.html#Index" title="Index" 
rel="index">Index</a>]</p>
+</div>
+<p>
 
-   </body></html>
 
+</p>
+</body>
+</html>

Index: html_node/Getting-Help.html
===================================================================
RCS file: /web/www/www/prep/maintain/html_node/Getting-Help.html,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -b -r1.20 -r1.21
--- html_node/Getting-Help.html 7 Sep 2011 01:31:18 -0000       1.20
+++ html_node/Getting-Help.html 7 Sep 2011 15:00:34 -0000       1.21
@@ -1,77 +1,111 @@
-<html lang="en">
-<head>
-<title>Getting Help - Information for Maintainers of GNU Software</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="Information for Maintainers of GNU Software">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="prev" href="Preface.html#Preface" title="Preface">
-<link rel="next" href="Getting-a-GNU-Account.html#Getting-a-GNU-Account" 
title="Getting a GNU Account">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home" 
title="Texinfo Homepage">
-<!--
-Information for maintainers of GNU software, last updated September 5, 2011.
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" 
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
+<!-- Information for maintainers of GNU software, last updated September 5, 
2011.
 
 Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
 2010, 2011 Free Software Foundation, Inc.
 
-     Permission is granted to copy, distribute and/or modify this
-     document under the terms of the GNU Free Documentation License,
-     Version 1.3 or any later version published by the Free Software
-     Foundation; with no Invariant Sections, with no Front-Cover Texts,
-     and with no Back-Cover Texts.  A copy of the license is included
-     in the section entitled ``GNU Free Documentation License''.
-   -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
-  pre.display { font-family:inherit }
-  pre.format  { font-family:inherit }
-  pre.smalldisplay { font-family:inherit; font-size:smaller }
-  pre.smallformat  { font-family:inherit; font-size:smaller }
-  pre.smallexample { font-size:smaller }
-  pre.smalllisp    { font-size:smaller }
-  span.sc    { font-variant:small-caps }
-  span.roman { font-family:serif; font-weight:normal; } 
-  span.sansserif { font-family:sans-serif; font-weight:normal; } 
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
+Texts.  A copy of the license is included in the section entitled
+"GNU Free Documentation License". -->
+<!-- Created by texi2html, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>Information for Maintainers of GNU Software: Getting Help</title>
+
+<meta name="description" content="Information for Maintainers of GNU Software: 
Getting Help">
+<meta name="keywords" content="Information for Maintainers of GNU Software: 
Getting Help">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="texi2html">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="index.html#Top" rel="up" title="Top">
+<link href="Getting-a-GNU-Account.html#Getting-a-GNU-Account" rel="next" 
title="Getting a GNU Account">
+<link href="Preface.html#Preface" rel="previous" title="Preface">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smalllisp {margin-left: 3.2em}
+pre.display {font-family: serif}
+pre.format {font-family: serif}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: serif; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: serif; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:pre}
+span.nolinebreak {white-space:pre}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
 </head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF" 
vlink="#800080" alink="#FF0000">
+
 <a name="Getting-Help"></a>
+<div class="header">
 <p>
-Next:&nbsp;<a rel="next" accesskey="n" 
href="Getting-a-GNU-Account.html#Getting-a-GNU-Account">Getting a GNU 
Account</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" 
href="Preface.html#Preface">Preface</a>,
-Up:&nbsp;<a rel="up" accesskey="u" href="index.html#Top">Top</a>
-<hr>
+Next: <a href="Getting-a-GNU-Account.html#Getting-a-GNU-Account" accesskey="n" 
rel="next">Getting a GNU Account</a>, Previous: <a href="Preface.html#Preface" 
accesskey="p" rel="previous">Preface</a>, Up: <a href="index.html#Top" 
accesskey="u" rel="up">Top</a> &nbsp; [<a href="index.html#SEC_Contents" 
title="Table of contents" rel="contents">Contents</a>][<a 
href="Index.html#Index" title="Index" rel="index">Index</a>]</p>
 </div>
-
-<h2 class="chapter">2 Getting Help</h2>
-
-<p><a name="index-help_002c-getting-6"></a>
-<a 
name="index-g_t_0040code_007bmentors_0040_0040gnu_002eorg_007d-mailing-list-7"></a>If
 you have any general questions or encounter a situation where it
-isn't clear how to get something done or who to ask, you (as a GNU
+<hr>
+<a name="Getting-Help-1"></a>
+<h1 class="chapter">2 Getting Help</h1>
+<a name="index-help_002c-getting"></a>
+
+<a name="index-mentors_0040gnu_002eorg-mailing-list"></a>
+<p>If you have any general questions or encounter a situation where it
+isn&rsquo;t clear how to get something done or who to ask, you (as a GNU
 contributor) can always write to <a 
href="mailto:address@hidden";>address@hidden</a>, which is a
 list of a few experienced GNU folks who have volunteered to answer
 questions.  Any GNU-related question is fair game for the
 <code>mentors</code> list.
-
-   <p><a name="index-advisory-committee-8"></a>The GNU Advisory Committee 
helps to coordinate activities in the GNU
+</p>
+<a name="index-advisory-committee"></a>
+<p>The GNU Advisory Committee helps to coordinate activities in the GNU
 project on behalf of RMS (Richard Stallman, the Chief GNUisance).  If
 you have any organizational questions or concerns you can contact the
 committee at <a href="mailto:address@hidden";>address@hidden</a>.  See
 <a 
href="http://www.gnu.org/contact/gnu-advisory.html";>http://www.gnu.org/contact/gnu-advisory.html</a>
 for the current
 committee members.  Additional information is in
-<samp><span class="file">/gd/gnuorg/advisory</span></samp>.
-
-   <p><a name="index-down_002c-when-GNU-machines-are-9"></a><a 
name="index-outage_002c-of-GNU-machines-10"></a><a 
name="index-g_t_0040url_007bhttp_003a_002f_002fidenti_002eca_002fgroup_002ffsfstatus_007d-11"></a>If
 you find that any GNU computer systems (<code>fencepost.gnu.org</code>,
+&lsquo;<tt>/gd/gnuorg/advisory</tt>&rsquo;.
+</p>
+<a name="index-down_002c-when-GNU-machines-are"></a>
+<a name="index-outage_002c-of-GNU-machines"></a>
+<a name="index-http_003a_002f_002fidenti_002eca_002fgroup_002ffsfstatus"></a>
+<p>If you find that any GNU computer systems (<code>fencepost.gnu.org</code>,
 <code>ftp.gnu.org</code>, <code>www.gnu.org</code>, 
<code>savannah.gnu.org</code>,
-<small class="dots">...</small>) seem to be down, you can check the current 
status at
+&hellip;) seem to be down, you can check the current status at
 <a 
href="http://identi.ca/group/fsfstatus";>http://identi.ca/group/fsfstatus</a>.  
Most likely the problem, if
 it can be alleviated at the FSF end, is already being worked on.
-
-   <p><a name="index-sysadmin_002c-FSF-12"></a><a 
name="index-FSF-system-administrators-13"></a><a 
name="index-GNU-system-administrators-14"></a>The FSF system administrators are 
responsible for the network and GNU
+</p>
+<a name="index-sysadmin_002c-FSF"></a>
+<a name="index-FSF-system-administrators"></a>
+<a name="index-GNU-system-administrators"></a>
+<p>The FSF system administrators are responsible for the network and GNU
 hardware.  You can email them at <a 
href="mailto:address@hidden";>address@hidden</a>, but please
 try not to burden them unnecessarily.
+</p>
+
+<p>
 
-   </body></html>
 
+</p>
+</body>
+</html>

Index: html_node/Getting-a-GNU-Account.html
===================================================================
RCS file: /web/www/www/prep/maintain/html_node/Getting-a-GNU-Account.html,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -b -r1.19 -r1.20
--- html_node/Getting-a-GNU-Account.html        7 Sep 2011 01:31:18 -0000       
1.19
+++ html_node/Getting-a-GNU-Account.html        7 Sep 2011 15:00:34 -0000       
1.20
@@ -1,62 +1,88 @@
-<html lang="en">
-<head>
-<title>Getting a GNU Account - Information for Maintainers of GNU 
Software</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="Information for Maintainers of GNU Software">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="prev" href="Getting-Help.html#Getting-Help" title="Getting Help">
-<link rel="next" href="Stepping-Down.html#Stepping-Down" title="Stepping Down">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home" 
title="Texinfo Homepage">
-<!--
-Information for maintainers of GNU software, last updated September 5, 2011.
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" 
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
+<!-- Information for maintainers of GNU software, last updated September 5, 
2011.
 
 Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
 2010, 2011 Free Software Foundation, Inc.
 
-     Permission is granted to copy, distribute and/or modify this
-     document under the terms of the GNU Free Documentation License,
-     Version 1.3 or any later version published by the Free Software
-     Foundation; with no Invariant Sections, with no Front-Cover Texts,
-     and with no Back-Cover Texts.  A copy of the license is included
-     in the section entitled ``GNU Free Documentation License''.
-   -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
-  pre.display { font-family:inherit }
-  pre.format  { font-family:inherit }
-  pre.smalldisplay { font-family:inherit; font-size:smaller }
-  pre.smallformat  { font-family:inherit; font-size:smaller }
-  pre.smallexample { font-size:smaller }
-  pre.smalllisp    { font-size:smaller }
-  span.sc    { font-variant:small-caps }
-  span.roman { font-family:serif; font-weight:normal; } 
-  span.sansserif { font-family:sans-serif; font-weight:normal; } 
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
+Texts.  A copy of the license is included in the section entitled
+"GNU Free Documentation License". -->
+<!-- Created by texi2html, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>Information for Maintainers of GNU Software: Getting a GNU 
Account</title>
+
+<meta name="description" content="Information for Maintainers of GNU Software: 
Getting a GNU Account">
+<meta name="keywords" content="Information for Maintainers of GNU Software: 
Getting a GNU Account">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="texi2html">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="index.html#Top" rel="up" title="Top">
+<link href="Stepping-Down.html#Stepping-Down" rel="next" title="Stepping Down">
+<link href="Getting-Help.html#Getting-Help" rel="previous" title="Getting 
Help">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smalllisp {margin-left: 3.2em}
+pre.display {font-family: serif}
+pre.format {font-family: serif}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: serif; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: serif; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:pre}
+span.nolinebreak {white-space:pre}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
 </head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF" 
vlink="#800080" alink="#FF0000">
+
 <a name="Getting-a-GNU-Account"></a>
+<div class="header">
 <p>
-Next:&nbsp;<a rel="next" accesskey="n" 
href="Stepping-Down.html#Stepping-Down">Stepping Down</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" 
href="Getting-Help.html#Getting-Help">Getting Help</a>,
-Up:&nbsp;<a rel="up" accesskey="u" href="index.html#Top">Top</a>
-<hr>
+Next: <a href="Stepping-Down.html#Stepping-Down" accesskey="n" 
rel="next">Stepping Down</a>, Previous: <a 
href="Getting-Help.html#Getting-Help" accesskey="p" rel="previous">Getting 
Help</a>, Up: <a href="index.html#Top" accesskey="u" rel="up">Top</a> &nbsp; 
[<a href="index.html#SEC_Contents" title="Table of contents" 
rel="contents">Contents</a>][<a href="Index.html#Index" title="Index" 
rel="index">Index</a>]</p>
 </div>
+<hr>
+<a name="Getting-a-GNU-Account-1"></a>
+<h1 class="chapter">3 Getting a GNU Account</h1>
+<a name="index-shell-account_002c-on-fencepost"></a>
+<a name="index-fencepost_002egnu_002eorg-GNU-machine"></a>
 
-<h2 class="chapter">3 Getting a GNU Account</h2>
-
-<p><a name="index-shell-account_002c-on-fencepost-15"></a><a 
name="index-g_t_0040code_007bfencepost_002egnu_002eorg_007d-GNU-machine-16"></a>
-<!-- We want to repeat this text later, so define a macro. -->
 
-   <p>The directory <samp><span class="file">/gd/gnuorg</span></samp> 
mentioned throughout this document is
+<p>The directory &lsquo;<tt>/gd/gnuorg</tt>&rsquo; mentioned throughout this 
document is
 available on the general GNU server, currently
 <code>fencepost.gnu.org</code>.  If you are the maintainer of a GNU package,
-you should have an account there.  If you don't have one already,
+you should have an account there.  If you don&rsquo;t have one already,
 <a 
href="http://www.gnu.org/software/README.accounts.html";>http://www.gnu.org/software/README.accounts.html</a>.
  You can also
 ask for accounts for people who significantly help you in working on
 the package.
+</p>
+
+<p>
 
-   </body></html>
 
+</p>
+</body>
+</html>

Index: html_node/Hosting-for-Web-Pages.html
===================================================================
RCS file: /web/www/www/prep/maintain/html_node/Hosting-for-Web-Pages.html,v
retrieving revision 1.25
retrieving revision 1.26
diff -u -b -r1.25 -r1.26
--- html_node/Hosting-for-Web-Pages.html        7 Sep 2011 01:31:18 -0000       
1.25
+++ html_node/Hosting-for-Web-Pages.html        7 Sep 2011 15:00:34 -0000       
1.26
@@ -1,70 +1,97 @@
-<html lang="en">
-<head>
-<title>Hosting for Web Pages - Information for Maintainers of GNU 
Software</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="Information for Maintainers of GNU Software">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="Web-Pages.html#Web-Pages" title="Web Pages">
-<link rel="next" href="Freedom-for-Web-Pages.html#Freedom-for-Web-Pages" 
title="Freedom for Web Pages">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home" 
title="Texinfo Homepage">
-<!--
-Information for maintainers of GNU software, last updated September 5, 2011.
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" 
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
+<!-- Information for maintainers of GNU software, last updated September 5, 
2011.
 
 Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
 2010, 2011 Free Software Foundation, Inc.
 
-     Permission is granted to copy, distribute and/or modify this
-     document under the terms of the GNU Free Documentation License,
-     Version 1.3 or any later version published by the Free Software
-     Foundation; with no Invariant Sections, with no Front-Cover Texts,
-     and with no Back-Cover Texts.  A copy of the license is included
-     in the section entitled ``GNU Free Documentation License''.
-   -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
-  pre.display { font-family:inherit }
-  pre.format  { font-family:inherit }
-  pre.smalldisplay { font-family:inherit; font-size:smaller }
-  pre.smallformat  { font-family:inherit; font-size:smaller }
-  pre.smallexample { font-size:smaller }
-  pre.smalllisp    { font-size:smaller }
-  span.sc    { font-variant:small-caps }
-  span.roman { font-family:serif; font-weight:normal; } 
-  span.sansserif { font-family:sans-serif; font-weight:normal; } 
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
+Texts.  A copy of the license is included in the section entitled
+"GNU Free Documentation License". -->
+<!-- Created by texi2html, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>Information for Maintainers of GNU Software: Hosting for Web 
Pages</title>
+
+<meta name="description" content="Information for Maintainers of GNU Software: 
Hosting for Web Pages">
+<meta name="keywords" content="Information for Maintainers of GNU Software: 
Hosting for Web Pages">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="texi2html">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Web-Pages.html#Web-Pages" rel="up" title="Web Pages">
+<link href="Freedom-for-Web-Pages.html#Freedom-for-Web-Pages" rel="next" 
title="Freedom for Web Pages">
+<link href="Web-Pages.html#Web-Pages" rel="previous" title="Web Pages">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smalllisp {margin-left: 3.2em}
+pre.display {font-family: serif}
+pre.format {font-family: serif}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: serif; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: serif; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:pre}
+span.nolinebreak {white-space:pre}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
 </head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF" 
vlink="#800080" alink="#FF0000">
+
 <a name="Hosting-for-Web-Pages"></a>
+<div class="header">
 <p>
-Next:&nbsp;<a rel="next" accesskey="n" 
href="Freedom-for-Web-Pages.html#Freedom-for-Web-Pages">Freedom for Web 
Pages</a>,
-Up:&nbsp;<a rel="up" accesskey="u" href="Web-Pages.html#Web-Pages">Web 
Pages</a>
-<hr>
+Next: <a href="Freedom-for-Web-Pages.html#Freedom-for-Web-Pages" accesskey="n" 
rel="next">Freedom for Web Pages</a>, Up: <a href="Web-Pages.html#Web-Pages" 
accesskey="u" rel="up">Web Pages</a> &nbsp; [<a href="index.html#SEC_Contents" 
title="Table of contents" rel="contents">Contents</a>][<a 
href="Index.html#Index" title="Index" rel="index">Index</a>]</p>
 </div>
-
-<h3 class="section">12.1 Hosting for Web Pages</h3>
+<hr>
+<a name="Hosting-for-Web-Pages-1"></a>
+<h2 class="section">12.1 Hosting for Web Pages</h2>
 
 <p>The best way to maintain the web pages for your project is to register
 the project on <code>savannah.gnu.org</code>.  Then you can edit the pages
 using CVS, using the separate &ldquo;web repository&rdquo; available on
 Savannah, which corresponds to
-&lt;<code>http://www.gnu.org/software/</code><var>package</var><code>/</code>&gt;.
  You can
+&lt;<code>http://www.gnu.org/software/<var>package</var>/</code>&gt;.  You can
 keep your source files there too (using any of a variety of version
 control systems), but you can use <code>savannah.gnu.org</code> only for
 your gnu.org web pages if you wish; simply register a &ldquo;web-only&rdquo;
 project.
-
-   <p>If you don't want to use that method, please talk with
+</p>
+<p>If you don&rsquo;t want to use that method, please talk with
 <a href="mailto:address@hidden";>address@hidden</a> about other possible 
methods.  For
 instance, you can mail them pages to install, if necessary.  But that
 is more work for them, so please use Savannah if you can.
-
-   <p>If you use Savannah, you can use a special file named <samp><span 
class="file">.symlinks</span></samp>
+</p>
+<p>If you use Savannah, you can use a special file named 
&lsquo;<tt>.symlinks</tt>&rsquo;
 in order to create symbolic links, which are not supported in CVS. 
 For details, see
 <a 
href="http://www.gnu.org/server/standards/README.webmastering.html#symlinks";>http://www.gnu.org/server/standards/README.webmastering.html#symlinks</a>.
+</p>
+
+<p>
 
-   </body></html>
 
+</p>
+</body>
+</html>

Index: html_node/Hosting.html
===================================================================
RCS file: /web/www/www/prep/maintain/html_node/Hosting.html,v
retrieving revision 1.66
retrieving revision 1.67
diff -u -b -r1.66 -r1.67
--- html_node/Hosting.html      7 Sep 2011 01:31:18 -0000       1.66
+++ html_node/Hosting.html      7 Sep 2011 15:00:34 -0000       1.67
@@ -1,82 +1,122 @@
-<html lang="en">
-<head>
-<title>Hosting - Information for Maintainers of GNU Software</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="Information for Maintainers of GNU Software">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="prev" href="Terminology.html#Terminology" title="Terminology">
-<link rel="next" href="Donations.html#Donations" title="Donations">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home" 
title="Texinfo Homepage">
-<!--
-Information for maintainers of GNU software, last updated September 5, 2011.
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" 
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
+<!-- Information for maintainers of GNU software, last updated September 5, 
2011.
 
 Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
 2010, 2011 Free Software Foundation, Inc.
 
-     Permission is granted to copy, distribute and/or modify this
-     document under the terms of the GNU Free Documentation License,
-     Version 1.3 or any later version published by the Free Software
-     Foundation; with no Invariant Sections, with no Front-Cover Texts,
-     and with no Back-Cover Texts.  A copy of the license is included
-     in the section entitled ``GNU Free Documentation License''.
-   -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
-  pre.display { font-family:inherit }
-  pre.format  { font-family:inherit }
-  pre.smalldisplay { font-family:inherit; font-size:smaller }
-  pre.smallformat  { font-family:inherit; font-size:smaller }
-  pre.smallexample { font-size:smaller }
-  pre.smalllisp    { font-size:smaller }
-  span.sc    { font-variant:small-caps }
-  span.roman { font-family:serif; font-weight:normal; } 
-  span.sansserif { font-family:sans-serif; font-weight:normal; } 
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
+Texts.  A copy of the license is included in the section entitled
+"GNU Free Documentation License". -->
+<!-- Created by texi2html, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>Information for Maintainers of GNU Software: Hosting</title>
+
+<meta name="description" content="Information for Maintainers of GNU Software: 
Hosting">
+<meta name="keywords" content="Information for Maintainers of GNU Software: 
Hosting">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="texi2html">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="index.html#Top" rel="up" title="Top">
+<link href="Donations.html#Donations" rel="next" title="Donations">
+<link href="GNU-and-Linux.html#GNU-and-Linux" rel="previous" title="GNU and 
Linux">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smalllisp {margin-left: 3.2em}
+pre.display {font-family: serif}
+pre.format {font-family: serif}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: serif; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: serif; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:pre}
+span.nolinebreak {white-space:pre}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
 </head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF" 
vlink="#800080" alink="#FF0000">
+
 <a name="Hosting"></a>
+<div class="header">
 <p>
-Next:&nbsp;<a rel="next" accesskey="n" 
href="Donations.html#Donations">Donations</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" 
href="Terminology.html#Terminology">Terminology</a>,
-Up:&nbsp;<a rel="up" accesskey="u" href="index.html#Top">Top</a>
-<hr>
+Next: <a href="Donations.html#Donations" accesskey="n" 
rel="next">Donations</a>, Previous: <a href="Terminology.html#Terminology" 
accesskey="p" rel="previous">Terminology</a>, Up: <a href="index.html#Top" 
accesskey="u" rel="up">Top</a> &nbsp; [<a href="index.html#SEC_Contents" 
title="Table of contents" rel="contents">Contents</a>][<a 
href="Index.html#Index" title="Index" rel="index">Index</a>]</p>
 </div>
-
-<h2 class="chapter">15 Hosting</h2>
-
-<p><a name="index-CVS-repository-85"></a><a name="index-repository-86"></a><a 
name="index-source-repository-87"></a><a 
name="index-version-control-system-88"></a><a name="index-FTP-site-89"></a><a 
name="index-release-site-90"></a><a name="index-hosting-91"></a>
-We recommend using <code>savannah.gnu.org</code> for the source code
-repository for your package, but that's not required.  See <a 
href="Old-Versions.html#Old-Versions">Old Versions</a>, for more information 
about Savannah.
-
-   <p>We strongly urge you to use <code>ftp.gnu.org</code> as the standard
+<hr>
+<a name="Hosting-1"></a>
+<h1 class="chapter">15 Hosting</h1>
+<a name="index-CVS-repository"></a>
+<a name="index-repository"></a>
+<a name="index-source-repository"></a>
+<a name="index-version-control-system"></a>
+<a name="index-FTP-site"></a>
+<a name="index-release-site"></a>
+<a name="index-hosting"></a>
+
+<p>We recommend using <code>savannah.gnu.org</code> for the source code
+repository for your package, but that&rsquo;s not required.  See <a 
href="Old-Versions.html#Old-Versions">Old
+Versions</a>, for more information about Savannah.
+</p>
+<p>We strongly urge you to use <code>ftp.gnu.org</code> as the standard
 distribution site for releases.  Doing so makes it easier for
 developers and users to find the latest GNU releases.  However, it is
 ok to use another server if you wish, provided it allows access from
 the general public without limitation (for instance, without excluding
 any country).
-
-   <p>If you use a company's machine to hold the repository for your
+</p>
+<p>If you use a company&rsquo;s machine to hold the repository for your
 program, or as its release distribution site, please put this
 statement in a prominent place on the site, so as to prevent people
 from getting the wrong idea about the relationship between the package
 and the company:
+</p>
+<div class="smallexample">
+<pre class="smallexample">The programs &lt;list of them&gt; hosted here are 
free software packages
+of the GNU Project, not products of &lt;company name&gt;.  We call them
+&quot;free software&quot; because you are free to copy and redistribute them,
+following the rules stated in the license of each package.  For more
+information, see http://www.gnu.org/philosophy/free-sw.html.
+
+If you are looking for service or support for GNU software, see
+http://www.gnu.org/gethelp/ for suggestions of where to ask.
+
+If you would like to contribute to the development of one of these
+packages, contact the package maintainer or the bug-reporting address
+of the package (which should be listed in the package itself), or look
+on www.gnu.org for more information on how to contribute.
+</pre></div>
+
+
+<hr>
+<div class="header">
+<p>
+Next: <a href="Donations.html#Donations" accesskey="n" 
rel="next">Donations</a>, Previous: <a href="Terminology.html#Terminology" 
accesskey="p" rel="previous">Terminology</a>, Up: <a href="index.html#Top" 
accesskey="u" rel="up">Top</a> &nbsp; [<a href="index.html#SEC_Contents" 
title="Table of contents" rel="contents">Contents</a>][<a 
href="Index.html#Index" title="Index" rel="index">Index</a>]</p>
+</div>
+<p>
 
-<pre class="smallexample">     The programs &lt;list of them&gt; hosted here 
are free software packages
-     of the GNU Project, not products of &lt;company name&gt;.  We call them
-     "free software" because you are free to copy and redistribute them,
-     following the rules stated in the license of each package.  For more
-     information, see http://www.gnu.org/philosophy/free-sw.html.
-     
-     If you are looking for service or support for GNU software, see
-     http://www.gnu.org/gethelp/ for suggestions of where to ask.
-     
-     If you would like to contribute to the development of one of these
-     packages, contact the package maintainer or the bug-reporting address
-     of the package (which should be listed in the package itself), or look
-     on www.gnu.org for more information on how to contribute.
-</pre>
-   </body></html>
 
+</p>
+</body>
+</html>

Index: html_node/Index.html
===================================================================
RCS file: /web/www/www/prep/maintain/html_node/Index.html,v
retrieving revision 1.66
retrieving revision 1.67
diff -u -b -r1.66 -r1.67
--- html_node/Index.html        7 Sep 2011 01:31:18 -0000       1.66
+++ html_node/Index.html        7 Sep 2011 15:00:35 -0000       1.67
@@ -1,147 +1,317 @@
-<html lang="en">
-<head>
-<title>Index - Information for Maintainers of GNU Software</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="Information for Maintainers of GNU Software">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="prev" 
href="GNU-Free-Documentation-License.html#GNU-Free-Documentation-License" 
title="GNU Free Documentation License">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home" 
title="Texinfo Homepage">
-<!--
-Information for maintainers of GNU software, last updated September 5, 2011.
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" 
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
+<!-- Information for maintainers of GNU software, last updated September 5, 
2011.
 
 Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
 2010, 2011 Free Software Foundation, Inc.
 
-     Permission is granted to copy, distribute and/or modify this
-     document under the terms of the GNU Free Documentation License,
-     Version 1.3 or any later version published by the Free Software
-     Foundation; with no Invariant Sections, with no Front-Cover Texts,
-     and with no Back-Cover Texts.  A copy of the license is included
-     in the section entitled ``GNU Free Documentation License''.
-   -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
-  pre.display { font-family:inherit }
-  pre.format  { font-family:inherit }
-  pre.smalldisplay { font-family:inherit; font-size:smaller }
-  pre.smallformat  { font-family:inherit; font-size:smaller }
-  pre.smallexample { font-size:smaller }
-  pre.smalllisp    { font-size:smaller }
-  span.sc    { font-variant:small-caps }
-  span.roman { font-family:serif; font-weight:normal; } 
-  span.sansserif { font-family:sans-serif; font-weight:normal; } 
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
+Texts.  A copy of the license is included in the section entitled
+"GNU Free Documentation License". -->
+<!-- Created by texi2html, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>Information for Maintainers of GNU Software: Index</title>
+
+<meta name="description" content="Information for Maintainers of GNU Software: 
Index">
+<meta name="keywords" content="Information for Maintainers of GNU Software: 
Index">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="texi2html">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="index.html#Top" rel="up" title="Top">
+<link 
href="GNU-Free-Documentation-License.html#GNU-Free-Documentation-License" 
rel="previous" title="GNU Free Documentation License">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smalllisp {margin-left: 3.2em}
+pre.display {font-family: serif}
+pre.format {font-family: serif}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: serif; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: serif; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:pre}
+span.nolinebreak {white-space:pre}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
 </head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF" 
vlink="#800080" alink="#FF0000">
+
 <a name="Index"></a>
+<div class="header">
 <p>
-Previous:&nbsp;<a rel="previous" accesskey="p" 
href="GNU-Free-Documentation-License.html#GNU-Free-Documentation-License">GNU 
Free Documentation License</a>,
-Up:&nbsp;<a rel="up" accesskey="u" href="index.html#Top">Top</a>
-<hr>
+Previous: <a 
href="GNU-Free-Documentation-License.html#GNU-Free-Documentation-License" 
accesskey="p" rel="previous">GNU Free Documentation License</a>, Up: <a 
href="index.html#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a 
href="index.html#SEC_Contents" title="Table of contents" 
rel="contents">Contents</a>][<a href="#Index" title="Index" 
rel="index">Index</a>]</p>
 </div>
+<hr>
+<a name="Index-1"></a>
+<h1 class="unnumbered">Index</h1>
+<table><tr><th valign="top">Jump to: &nbsp; </th><td><a class="summary-letter" 
href="#Index_cp_symbol-1"><b>$</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_symbol-2"><b>/</b></a>
+ &nbsp; 
+<br>
+<a class="summary-letter" href="#Index_cp_letter-A"><b>A</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-B"><b>B</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-C"><b>C</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-D"><b>D</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-E"><b>E</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-F"><b>F</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-G"><b>G</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-H"><b>H</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-I"><b>I</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-L"><b>L</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-M"><b>M</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-O"><b>O</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-P"><b>P</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-Q"><b>Q</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-R"><b>R</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-S"><b>S</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-T"><b>T</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-U"><b>U</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-V"><b>V</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-W"><b>W</b></a>
+ &nbsp; 
+</td></tr></table>
+<table class="index-cp" border="0">
+<tr><td></td><th align="left">Index Entry</th><td>&nbsp;</td><th align="left"> 
Section</th></tr>
+<tr><td colspan="4"> <hr></td></tr>
+<tr><th><a name="Index_cp_symbol-1">$</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a 
href="CVS-Keywords-in-Web-Pages.html#index-_0024-keywords-in-web-pages">$ 
keywords in web pages</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="CVS-Keywords-in-Web-Pages.html#CVS-Keywords-in-Web-Pages">CVS Keywords in 
Web Pages</a></td></tr>
+<tr><td colspan="4"> <hr></td></tr>
+<tr><th><a name="Index_cp_symbol-2">/</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a 
href="Copyright-Papers.html#index-_002fgd_002fgnuorg-directory">&lsquo;<tt>/gd/gnuorg</tt>&rsquo;
 directory</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="Copyright-Papers.html#Copyright-Papers">Copyright Papers</a></td></tr>
+<tr><td colspan="4"> <hr></td></tr>
+<tr><th><a name="Index_cp_letter-A">A</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a 
href="Getting-Help.html#index-advisory-committee">advisory 
committee</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="Getting-Help.html#Getting-Help">Getting Help</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="Test-Releases.html#index-alpha_002egnu_002eorg_002c-test-release-site"><code>alpha.gnu.org</code>,
 test release site</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="Test-Releases.html#Test-Releases">Test Releases</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="Announcements.html#index-announcement-mailing-list_002c-project_002dspecific">announcement
 mailing list, project-specific</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="Announcements.html#Announcements">Announcements</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="Announcements.html#index-announcements">announcements</a>:</td><td>&nbsp;</td><td
 valign="top"><a 
href="Announcements.html#Announcements">Announcements</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="Standard-Mailing-Lists.html#index-announcements_002c-mailing-list-for">announcements,
 mailing list for</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="Standard-Mailing-Lists.html#Standard-Mailing-Lists">Standard Mailing 
Lists</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="Recording-Contributors.html#index-AUTHORS-file">&lsquo;<tt>AUTHORS</tt>&rsquo;
 file</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="Recording-Contributors.html#Recording-Contributors">Recording 
Contributors</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="Distribution-tar-Files.html#index-automake"><code>automake</code></a>:</td><td>&nbsp;</td><td
 valign="top"><a 
href="Distribution-tar-Files.html#Distribution-tar-Files">Distribution tar 
Files</a></td></tr>
+<tr><td colspan="4"> <hr></td></tr>
+<tr><th><a name="Index_cp_letter-B">B</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a 
href="Test-Releases.html#index-beta-releases">beta 
releases</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="Test-Releases.html#Test-Releases">Test Releases</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="Replying-to-Mail.html#index-bug-reports_002c-handling">bug reports, 
handling</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="Replying-to-Mail.html#Replying-to-Mail">Replying to Mail</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="Standard-Mailing-Lists.html#index-bug_002dgnu_002dutils_0040gnu_002eorg"><a
 href="mailto:address@hidden";>address@hidden</a></a>:</td><td>&nbsp;</td><td 
valign="top"><a 
href="Standard-Mailing-Lists.html#Standard-Mailing-Lists">Standard Mailing 
Lists</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="Preface.html#index-bug_002dstandards_0040gnu_002eorg-email-address"><code>address@hidden</code>
 email address</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="Preface.html#Preface">Preface</a></td></tr>
+<tr><td colspan="4"> <hr></td></tr>
+<tr><th><a name="Index_cp_letter-C">C</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a 
href="Announcements.html#index-contents-of-announcements">contents of 
announcements</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="Announcements.html#Announcements">Announcements</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="Clean-Ups.html#index-contributions_002c-accepting">contributions, 
accepting</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="Clean-Ups.html#Clean-Ups">Clean Ups</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="Copyright-Notices.html#index-copyright-notices-in-program-files">copyright
 notices in program files</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="Copyright-Notices.html#Copyright-Notices">Copyright Notices</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="Copyright-Papers.html#index-copyright-papers">copyright 
papers</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="Copyright-Papers.html#Copyright-Papers">Copyright Papers</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="Creating-Mailing-Lists.html#index-creating-mailing-lists">creating 
mailing lists</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="Creating-Mailing-Lists.html#Creating-Mailing-Lists">Creating Mailing 
Lists</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="CVS-Keywords-in-Web-Pages.html#index-CVS-keywords-in-web-pages">CVS 
keywords in web pages</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="CVS-Keywords-in-Web-Pages.html#CVS-Keywords-in-Web-Pages">CVS Keywords in 
Web Pages</a></td></tr>
+<tr><td></td><td valign="top"><a href="Hosting.html#index-CVS-repository">CVS 
repository</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="Hosting.html#Hosting">Hosting</a></td></tr>
+<tr><td colspan="4"> <hr></td></tr>
+<tr><th><a name="Index_cp_letter-D">D</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a 
href="Copyright-Papers.html#index-data-base-of-GNU-copyright-assignments">data 
base of GNU copyright assignments</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="Copyright-Papers.html#Copyright-Papers">Copyright Papers</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="Free-Software-and-Open-Source.html#index-development-method_002c-open-source">development
 method, open source</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="Free-Software-and-Open-Source.html#Free-Software-and-Open-Source">Free 
Software and Open Source</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="Distribution-Patches.html#index-diff"><code>diff</code></a>:</td><td>&nbsp;</td><td
 valign="top"><a 
href="Distribution-Patches.html#Distribution-Patches">Distribution 
Patches</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="Free-Software-Directory.html#index-Directory_002c-Free-Software">Directory,
 Free Software</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="Free-Software-Directory.html#Free-Software-Directory">Free Software 
Directory</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="Distribution-tar-Files.html#index-distribution_002c-tar-files">distribution,
 tar files</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="Distribution-tar-Files.html#Distribution-tar-Files">Distribution tar 
Files</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="Donations.html#index-Donations_002c-for-packages">Donations, for 
packages</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="Donations.html#Donations">Donations</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="Getting-Help.html#index-down_002c-when-GNU-machines-are">down, when GNU 
machines are</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="Getting-Help.html#Getting-Help">Getting Help</a></td></tr>
+<tr><td colspan="4"> <hr></td></tr>
+<tr><th><a name="Index_cp_letter-E">E</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a 
href="Mail.html#index-email">email</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="Mail.html#Mail">Mail</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="Ethical-and-Philosophical-Consideration.html#index-ethics">ethics</a>:</td><td>&nbsp;</td><td
 valign="top"><a 
href="Ethical-and-Philosophical-Consideration.html#Ethical-and-Philosophical-Consideration">Ethical
 and Philosophical Consideration</a></td></tr>
+<tr><td colspan="4"> <hr></td></tr>
+<tr><th><a name="Index_cp_letter-F">F</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a 
href="GNU-Free-Documentation-License.html#index-FDL_002c-GNU-Free-Documentation-License">FDL,
 GNU Free Documentation License</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="GNU-Free-Documentation-License.html#GNU-Free-Documentation-License">GNU 
Free Documentation License</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="Getting-a-GNU-Account.html#index-fencepost_002egnu_002eorg-GNU-machine"><code>fencepost.gnu.org</code>
 GNU machine</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="Getting-a-GNU-Account.html#Getting-a-GNU-Account">Getting a GNU 
Account</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="Free-Software-Directory.html#index-Free-Software-Directory">Free Software 
Directory</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="Free-Software-Directory.html#Free-Software-Directory">Free Software 
Directory</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="Free-Software-and-Open-Source.html#index-free-software-movement">free 
software movement</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="Free-Software-and-Open-Source.html#Free-Software-and-Open-Source">Free 
Software and Open Source</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="Getting-Help.html#index-FSF-system-administrators">FSF system 
administrators</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="Getting-Help.html#Getting-Help">Getting Help</a></td></tr>
+<tr><td></td><td valign="top"><a href="Hosting.html#index-FTP-site">FTP 
site</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="Hosting.html#Hosting">Hosting</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="Automated-FTP-Uploads.html#index-ftp-uploads_002c-automated">ftp uploads, 
automated</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="Automated-FTP-Uploads.html#Automated-FTP-Uploads">Automated FTP 
Uploads</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="Distribution-on-ftp_002egnu_002eorg.html#index-ftp_002egnu_002eorg_002c-the-GNU-release-site"><code>ftp.gnu.org</code>,
 the GNU release site</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="Distribution-on-ftp_002egnu_002eorg.html#Distribution-on-ftp_002egnu_002eorg">Distribution
 on ftp.gnu.org</a></td></tr>
+<tr><td colspan="4"> <hr></td></tr>
+<tr><th><a name="Index_cp_letter-G">G</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a 
href="Invoking-gendocs_002esh.html#index-gendocs_002esh"><code>gendocs.sh</code></a>:</td><td>&nbsp;</td><td
 valign="top"><a 
href="Invoking-gendocs_002esh.html#Invoking-gendocs_002esh">Invoking 
gendocs.sh</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="Invoking-gendocs_002esh.html#index-generating-documentation-output">generating
 documentation output</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="Invoking-gendocs_002esh.html#Invoking-gendocs_002esh">Invoking 
gendocs.sh</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="Distribution-on-ftp_002egnu_002eorg.html#index-GNU-ftp-site">GNU ftp 
site</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="Distribution-on-ftp_002egnu_002eorg.html#Distribution-on-ftp_002egnu_002eorg">Distribution
 on ftp.gnu.org</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="Getting-Help.html#index-GNU-system-administrators">GNU system 
administrators</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="Getting-Help.html#Getting-Help">Getting Help</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="GNU-and-Linux.html#index-GNU_002fLinux">GNU/Linux</a>:</td><td>&nbsp;</td><td
 valign="top"><a href="GNU-and-Linux.html#GNU-and-Linux">GNU and 
Linux</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="Preface.html#index-gnustandards-project-repository"><code>gnustandards</code>
 project repository</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="Preface.html#Preface">Preface</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="Preface.html#index-gnustandards_002dcommit_0040gnu_002eorg-mailing-list"><code>address@hidden</code>
 mailing list</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="Preface.html#Preface">Preface</a></td></tr>
+<tr><td colspan="4"> <hr></td></tr>
+<tr><th><a name="Index_cp_letter-H">H</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a 
href="Standard-Mailing-Lists.html#index-help-for-users_002c-mailing-list-for">help
 for users, mailing list for</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="Standard-Mailing-Lists.html#Standard-Mailing-Lists">Standard Mailing 
Lists</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="Replying-to-Mail.html#index-help-requests_002c-handling">help requests, 
handling</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="Replying-to-Mail.html#Replying-to-Mail">Replying to Mail</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="Getting-Help.html#index-help_002c-getting">help, 
getting</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="Getting-Help.html#Getting-Help">Getting Help</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="Hosting.html#index-hosting">hosting</a>:</td><td>&nbsp;</td><td 
valign="top"><a href="Hosting.html#Hosting">Hosting</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="Getting-Help.html#index-http_003a_002f_002fidenti_002eca_002fgroup_002ffsfstatus"><a
 
href="http://identi.ca/group/fsfstatus";>http://identi.ca/group/fsfstatus</a></a>:</td><td>&nbsp;</td><td
 valign="top"><a href="Getting-Help.html#Getting-Help">Getting 
Help</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="Announcements.html#index-http_003a_002f_002fplanet_002egnu_002eorg"><a 
href="http://planet.gnu.org";>http://planet.gnu.org</a></a>:</td><td>&nbsp;</td><td
 valign="top"><a 
href="Announcements.html#Announcements">Announcements</a></td></tr>
+<tr><td colspan="4"> <hr></td></tr>
+<tr><th><a name="Index_cp_letter-I">I</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a 
href="Announcements.html#index-info_002dgnu-mailing-list"><code>info-gnu</code> 
mailing list</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="Announcements.html#Announcements">Announcements</a></td></tr>
+<tr><td colspan="4"> <hr></td></tr>
+<tr><th><a name="Index_cp_letter-L">L</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a 
href="Legal-Matters.html#index-legal-matters">legal 
matters</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="Legal-Matters.html#Legal-Matters">Legal Matters</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="Copyright-Papers.html#index-legal-papers-for-changes-in-manuals">legal 
papers for changes in manuals</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="Copyright-Papers.html#Copyright-Papers">Copyright Papers</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="License-Notices.html#index-license-notices-in-program-files">license 
notices in program files</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="License-Notices.html#License-Notices">License Notices</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="GNU-and-Linux.html#index-Linux">Linux</a>:</td><td>&nbsp;</td><td 
valign="top"><a href="GNU-and-Linux.html#GNU-and-Linux">GNU and 
Linux</a></td></tr>
+<tr><td colspan="4"> <hr></td></tr>
+<tr><th><a name="Index_cp_letter-M">M</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a 
href="Standard-Mailing-Lists.html#index-mailing-list-for-bug-reports">mailing 
list for bug reports</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="Standard-Mailing-Lists.html#Standard-Mailing-Lists">Standard Mailing 
Lists</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="Creating-Mailing-Lists.html#index-mailing-lists_002c-creating">mailing 
lists, creating</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="Creating-Mailing-Lists.html#Creating-Mailing-Lists">Creating Mailing 
Lists</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="Standard-Mailing-Lists.html#index-mailing-lists_002c-standard-names-of">mailing
 lists, standard names of</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="Standard-Mailing-Lists.html#Standard-Mailing-Lists">Standard Mailing 
Lists</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="Stepping-Down.html#index-maintainers_0040gnu_002eorg"><a 
href="mailto:address@hidden";>address@hidden</a></a>:</td><td>&nbsp;</td><td 
valign="top"><a href="Stepping-Down.html#Stepping-Down">Stepping 
Down</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="Getting-Help.html#index-mentors_0040gnu_002eorg-mailing-list"><code>address@hidden</code>
 mailing list</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="Getting-Help.html#Getting-Help">Getting Help</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="Donations.html#index-Money_002c-donated-to-packages">Money, donated to 
packages</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="Donations.html#Donations">Donations</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="Free-Software-and-Open-Source.html#index-movement_002c-free-software">movement,
 free software</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="Free-Software-and-Open-Source.html#Free-Software-and-Open-Source">Free 
Software and Open Source</a></td></tr>
+<tr><td colspan="4"> <hr></td></tr>
+<tr><th><a name="Index_cp_letter-O">O</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a 
href="Free-Software-and-Open-Source.html#index-open-source">open 
source</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="Free-Software-and-Open-Source.html#Free-Software-and-Open-Source">Free 
Software and Open Source</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="Getting-Help.html#index-outage_002c-of-GNU-machines">outage, of GNU 
machines</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="Getting-Help.html#Getting-Help">Getting Help</a></td></tr>
+<tr><td colspan="4"> <hr></td></tr>
+<tr><th><a name="Index_cp_letter-P">P</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a 
href="Distribution-Patches.html#index-patch"><code>patch</code></a>:</td><td>&nbsp;</td><td
 valign="top"><a 
href="Distribution-Patches.html#Distribution-Patches">Distribution 
Patches</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="Distribution-Patches.html#index-patches_002c-against-previous-releases">patches,
 against previous releases</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="Distribution-Patches.html#Distribution-Patches">Distribution 
Patches</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="Ethical-and-Philosophical-Consideration.html#index-philosophy">philosophy</a>:</td><td>&nbsp;</td><td
 valign="top"><a 
href="Ethical-and-Philosophical-Consideration.html#Ethical-and-Philosophical-Consideration">Ethical
 and Philosophical Consideration</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="Preface.html#index-Piercy_002c-Marge">Piercy, 
Marge</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="Preface.html#Preface">Preface</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="Test-Releases.html#index-pretest-releases">pretest 
releases</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="Test-Releases.html#Test-Releases">Test Releases</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="Using-the-Proofreaders-List.html#index-proofreading">proofreading</a>:</td><td>&nbsp;</td><td
 valign="top"><a 
href="Using-the-Proofreaders-List.html#Using-the-Proofreaders-List">Using the 
Proofreaders List</a></td></tr>
+<tr><td colspan="4"> <hr></td></tr>
+<tr><th><a name="Index_cp_letter-Q">Q</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a 
href="Clean-Ups.html#index-quality-of-changes-suggested-by-others">quality of 
changes suggested by others</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="Clean-Ups.html#Clean-Ups">Clean Ups</a></td></tr>
+<tr><td colspan="4"> <hr></td></tr>
+<tr><th><a name="Index_cp_letter-R">R</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a 
href="CVS-Keywords-in-Web-Pages.html#index-RCS-keywords-in-web-pages">RCS 
keywords in web pages</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="CVS-Keywords-in-Web-Pages.html#CVS-Keywords-in-Web-Pages">CVS Keywords in 
Web Pages</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="Recording-Contributors.html#index-recording-contributors">recording 
contributors</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="Recording-Contributors.html#Recording-Contributors">Recording 
Contributors</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="Automated-Upload-Registration.html#index-registration-for-uploads">registration
 for uploads</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="Automated-Upload-Registration.html#Automated-Upload-Registration">Automated
 Upload Registration</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="Hosting.html#index-release-site">release site</a>:</td><td>&nbsp;</td><td 
valign="top"><a href="Hosting.html#Hosting">Hosting</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="Hosting.html#index-repository">repository</a>:</td><td>&nbsp;</td><td 
valign="top"><a href="Hosting.html#Hosting">Hosting</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="Stepping-Down.html#index-resigning-as-maintainer">resigning as 
maintainer</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="Stepping-Down.html#Stepping-Down">Stepping Down</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="Replying-to-Mail.html#index-responding-to-bug-reports">responding to bug 
reports</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="Replying-to-Mail.html#Replying-to-Mail">Replying to Mail</a></td></tr>
+<tr><td colspan="4"> <hr></td></tr>
+<tr><th><a name="Index_cp_letter-S">S</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a 
href="Preface.html#index-Savannah-repository-for-gnustandards">Savannah 
repository for <code>gnustandards</code></a>:</td><td>&nbsp;</td><td 
valign="top"><a href="Preface.html#Preface">Preface</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="Announcements.html#index-Savannah_002c-news-area">Savannah, news 
area</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="Announcements.html#Announcements">Announcements</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="Old-Versions.html#index-savannah_002dannounce_0040gnu_002eorg-mailing-list"><code>address@hidden</code>
 mailing list</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="Old-Versions.html#Old-Versions">Old Versions</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="Old-Versions.html#index-savannah_002dhackers_0040gnu_002eorg"><code>address@hidden</code></a>:</td><td>&nbsp;</td><td
 valign="top"><a href="Old-Versions.html#Old-Versions">Old 
Versions</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="Getting-a-GNU-Account.html#index-shell-account_002c-on-fencepost">shell 
account, on fencepost</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="Getting-a-GNU-Account.html#Getting-a-GNU-Account">Getting a GNU 
Account</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="Hosting.html#index-source-repository">source 
repository</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="Hosting.html#Hosting">Hosting</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="Creating-Mailing-Lists.html#index-spam-prevention">spam 
prevention</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="Creating-Mailing-Lists.html#Creating-Mailing-Lists">Creating Mailing 
Lists</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="Standard-Mailing-Lists.html#index-standard-mailing-lists">standard 
mailing lists</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="Standard-Mailing-Lists.html#Standard-Mailing-Lists">Standard Mailing 
Lists</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="Stepping-Down.html#index-stepping-down-as-maintainer">stepping down as 
maintainer</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="Stepping-Down.html#Stepping-Down">Stepping Down</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="Getting-Help.html#index-sysadmin_002c-FSF">sysadmin, 
FSF</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="Getting-Help.html#Getting-Help">Getting Help</a></td></tr>
+<tr><td colspan="4"> <hr></td></tr>
+<tr><th><a name="Index_cp_letter-T">T</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a 
href="Terminology.html#index-terminology">terminology</a>:</td><td>&nbsp;</td><td
 valign="top"><a href="Terminology.html#Terminology">Terminology</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="Test-Releases.html#index-test-releases">test 
releases</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="Test-Releases.html#Test-Releases">Test Releases</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="Distribution-Patches.html#index-time-stamp-in-diffs">time stamp in 
diffs</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="Distribution-Patches.html#Distribution-Patches">Distribution 
Patches</a></td></tr>
+<tr><td colspan="4"> <hr></td></tr>
+<tr><th><a name="Index_cp_letter-U">U</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a 
href="Automated-Upload-Procedure.html#index-uploads">uploads</a>:</td><td>&nbsp;</td><td
 valign="top"><a 
href="Automated-Upload-Procedure.html#Automated-Upload-Procedure">Automated 
Upload Procedure</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="Automated-Upload-Registration.html#index-uploads_002c-registration-for">uploads,
 registration for</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="Automated-Upload-Registration.html#Automated-Upload-Registration">Automated
 Upload Registration</a></td></tr>
+<tr><td colspan="4"> <hr></td></tr>
+<tr><th><a name="Index_cp_letter-V">V</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a 
href="Old-Versions.html#index-version-control">version 
control</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="Old-Versions.html#Old-Versions">Old Versions</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="Hosting.html#index-version-control-system">version control 
system</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="Hosting.html#Hosting">Hosting</a></td></tr>
+<tr><td colspan="4"> <hr></td></tr>
+<tr><th><a name="Index_cp_letter-W">W</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a href="Web-Pages.html#index-web-pages">web 
pages</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="Web-Pages.html#Web-Pages">Web Pages</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="CVS-Keywords-in-Web-Pages.html#index-web-pages_002c-and-CVS-keywords">web 
pages, and CVS keywords</a>:</td><td>&nbsp;</td><td valign="top"><a 
href="CVS-Keywords-in-Web-Pages.html#CVS-Keywords-in-Web-Pages">CVS Keywords in 
Web Pages</a></td></tr>
+<tr><td colspan="4"> <hr></td></tr>
+</table>
+<table><tr><th valign="top">Jump to: &nbsp; </th><td><a class="summary-letter" 
href="#Index_cp_symbol-1"><b>$</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_symbol-2"><b>/</b></a>
+ &nbsp; 
+<br>
+<a class="summary-letter" href="#Index_cp_letter-A"><b>A</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-B"><b>B</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-C"><b>C</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-D"><b>D</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-E"><b>E</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-F"><b>F</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-G"><b>G</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-H"><b>H</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-I"><b>I</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-L"><b>L</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-M"><b>M</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-O"><b>O</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-P"><b>P</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-Q"><b>Q</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-R"><b>R</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-S"><b>S</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-T"><b>T</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-U"><b>U</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-V"><b>V</b></a>
+ &nbsp; 
+<a class="summary-letter" href="#Index_cp_letter-W"><b>W</b></a>
+ &nbsp; 
+</td></tr></table>
 
-<h2 class="unnumbered">Index</h2>
+<hr>
+<div class="header">
+<p>
+Previous: <a 
href="GNU-Free-Documentation-License.html#GNU-Free-Documentation-License" 
accesskey="p" rel="previous">GNU Free Documentation License</a>, Up: <a 
href="index.html#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a 
href="index.html#SEC_Contents" title="Table of contents" 
rel="contents">Contents</a>][<a href="#Index" title="Index" 
rel="index">Index</a>]</p>
+</div>
+<p>
 
-<ul class="index-cp" compact>
-<li><a 
href="CVS-Keywords-in-Web-Pages.html#index-g_t_0024-keywords-in-web-pages-74">$ 
keywords in web pages</a>: <a 
href="CVS-Keywords-in-Web-Pages.html#CVS-Keywords-in-Web-Pages">CVS Keywords in 
Web Pages</a></li>
-<li><a 
href="Copyright-Papers.html#index-g_t_0040file_007b_002fgd_002fgnuorg_007d-directory-23"><samp><span
 class="file">/gd/gnuorg</span></samp> directory</a>: <a 
href="Copyright-Papers.html#Copyright-Papers">Copyright Papers</a></li>
-<li><a 
href="Standard-Mailing-Lists.html#index-g_t_0040email_007bbug_002dgnu_002dutils_0040_0040gnu_002eorg_007d-35"><a
 href="mailto:address@hidden";>address@hidden</a></a>: <a 
href="Standard-Mailing-Lists.html#Standard-Mailing-Lists">Standard Mailing 
Lists</a></li>
-<li><a 
href="Stepping-Down.html#index-g_t_0040email_007bmaintainers_0040_0040gnu_002eorg_007d-19"><a
 href="mailto:address@hidden";>address@hidden</a></a>: <a 
href="Stepping-Down.html#Stepping-Down">Stepping Down</a></li>
-<li><a href="Getting-Help.html#index-advisory-committee-8">advisory 
committee</a>: <a href="Getting-Help.html#Getting-Help">Getting Help</a></li>
-<li><a 
href="Test-Releases.html#index-g_t_0040code_007balpha_002egnu_002eorg_007d_002c-test-release-site-58"><code>alpha.gnu.org</code>,
 test release site</a>: <a href="Test-Releases.html#Test-Releases">Test 
Releases</a></li>
-<li><a 
href="Announcements.html#index-announcement-mailing-list_002c-project_002dspecific-67">announcement
 mailing list, project-specific</a>: <a 
href="Announcements.html#Announcements">Announcements</a></li>
-<li><a href="Announcements.html#index-announcements-63">announcements</a>: <a 
href="Announcements.html#Announcements">Announcements</a></li>
-<li><a 
href="Standard-Mailing-Lists.html#index-announcements_002c-mailing-list-for-37">announcements,
 mailing list for</a>: <a 
href="Standard-Mailing-Lists.html#Standard-Mailing-Lists">Standard Mailing 
Lists</a></li>
-<li><a 
href="Recording-Contributors.html#index-g_t_0040file_007bAUTHORS_007d-file-26"><samp><span
 class="file">AUTHORS</span></samp> file</a>: <a 
href="Recording-Contributors.html#Recording-Contributors">Recording 
Contributors</a></li>
-<li><a 
href="Distribution-tar-Files.html#index-automake-48"><code>automake</code></a>: 
<a href="Distribution-tar-Files.html#Distribution-tar-Files">Distribution tar 
Files</a></li>
-<li><a href="Test-Releases.html#index-beta-releases-56">beta releases</a>: <a 
href="Test-Releases.html#Test-Releases">Test Releases</a></li>
-<li><a href="Replying-to-Mail.html#index-bug-reports_002c-handling-42">bug 
reports, handling</a>: <a 
href="Replying-to-Mail.html#Replying-to-Mail">Replying to Mail</a></li>
-<li><a 
href="Preface.html#index-g_t_0040code_007bbug_002dstandards_0040_0040gnu_002eorg_007d-email-address-1"><code>address@hidden</code>
 email address</a>: <a href="Preface.html#Preface">Preface</a></li>
-<li><a href="Announcements.html#index-contents-of-announcements-68">contents 
of announcements</a>: <a 
href="Announcements.html#Announcements">Announcements</a></li>
-<li><a 
href="Clean-Ups.html#index-contributions_002c-accepting-29">contributions, 
accepting</a>: <a href="Clean-Ups.html#Clean-Ups">Clean Ups</a></li>
-<li><a 
href="Copyright-Notices.html#index-copyright-notices-in-program-files-27">copyright
 notices in program files</a>: <a 
href="Copyright-Notices.html#Copyright-Notices">Copyright Notices</a></li>
-<li><a href="Copyright-Papers.html#index-copyright-papers-21">copyright 
papers</a>: <a href="Copyright-Papers.html#Copyright-Papers">Copyright 
Papers</a></li>
-<li><a 
href="Creating-Mailing-Lists.html#index-creating-mailing-lists-38">creating 
mailing lists</a>: <a 
href="Creating-Mailing-Lists.html#Creating-Mailing-Lists">Creating Mailing 
Lists</a></li>
-<li><a 
href="CVS-Keywords-in-Web-Pages.html#index-CVS-keywords-in-web-pages-72">CVS 
keywords in web pages</a>: <a 
href="CVS-Keywords-in-Web-Pages.html#CVS-Keywords-in-Web-Pages">CVS Keywords in 
Web Pages</a></li>
-<li><a href="Hosting.html#index-CVS-repository-85">CVS repository</a>: <a 
href="Hosting.html#Hosting">Hosting</a></li>
-<li><a 
href="Copyright-Papers.html#index-data-base-of-GNU-copyright-assignments-22">data
 base of GNU copyright assignments</a>: <a 
href="Copyright-Papers.html#Copyright-Papers">Copyright Papers</a></li>
-<li><a 
href="Free-Software-and-Open-Source.html#index-development-method_002c-open-source-82">development
 method, open source</a>: <a 
href="Free-Software-and-Open-Source.html#Free-Software-and-Open-Source">Free 
Software and Open Source</a></li>
-<li><a href="Distribution-Patches.html#index-diff-50"><code>diff</code></a>: 
<a href="Distribution-Patches.html#Distribution-Patches">Distribution 
Patches</a></li>
-<li><a 
href="Free-Software-Directory.html#index-Directory_002c-Free-Software-95">Directory,
 Free Software</a>: <a 
href="Free-Software-Directory.html#Free-Software-Directory">Free Software 
Directory</a></li>
-<li><a 
href="Distribution-tar-Files.html#index-distribution_002c-tar-files-47">distribution,
 tar files</a>: <a 
href="Distribution-tar-Files.html#Distribution-tar-Files">Distribution tar 
Files</a></li>
-<li><a href="Donations.html#index-Donations_002c-for-packages-92">Donations, 
for packages</a>: <a href="Donations.html#Donations">Donations</a></li>
-<li><a href="Getting-Help.html#index-down_002c-when-GNU-machines-are-9">down, 
when GNU machines are</a>: <a href="Getting-Help.html#Getting-Help">Getting 
Help</a></li>
-<li><a href="Mail.html#index-email-31">email</a>: <a 
href="Mail.html#Mail">Mail</a></li>
-<li><a 
href="Ethical-and-Philosophical-Consideration.html#index-ethics-76">ethics</a>: 
<a 
href="Ethical-and-Philosophical-Consideration.html#Ethical-and-Philosophical-Consideration">Ethical
 and Philosophical Consideration</a></li>
-<li><a 
href="GNU-Free-Documentation-License.html#index-FDL_002c-GNU-Free-Documentation-License-97">FDL,
 GNU Free Documentation License</a>: <a 
href="GNU-Free-Documentation-License.html#GNU-Free-Documentation-License">GNU 
Free Documentation License</a></li>
-<li><a 
href="Getting-a-GNU-Account.html#index-g_t_0040code_007bfencepost_002egnu_002eorg_007d-GNU-machine-16"><code>fencepost.gnu.org</code>
 GNU machine</a>: <a 
href="Getting-a-GNU-Account.html#Getting-a-GNU-Account">Getting a GNU 
Account</a></li>
-<li><a 
href="Free-Software-Directory.html#index-Free-Software-Directory-94">Free 
Software Directory</a>: <a 
href="Free-Software-Directory.html#Free-Software-Directory">Free Software 
Directory</a></li>
-<li><a 
href="Free-Software-and-Open-Source.html#index-free-software-movement-79">free 
software movement</a>: <a 
href="Free-Software-and-Open-Source.html#Free-Software-and-Open-Source">Free 
Software and Open Source</a></li>
-<li><a href="Getting-Help.html#index-FSF-system-administrators-13">FSF system 
administrators</a>: <a href="Getting-Help.html#Getting-Help">Getting 
Help</a></li>
-<li><a href="Hosting.html#index-FTP-site-89">FTP site</a>: <a 
href="Hosting.html#Hosting">Hosting</a></li>
-<li><a 
href="Automated-FTP-Uploads.html#index-ftp-uploads_002c-automated-59">ftp 
uploads, automated</a>: <a 
href="Automated-FTP-Uploads.html#Automated-FTP-Uploads">Automated FTP 
Uploads</a></li>
-<li><a 
href="Distribution-on-ftp_002egnu_002eorg.html#index-g_t_0040code_007bftp_002egnu_002eorg_007d_002c-the-GNU-release-site-54"><code>ftp.gnu.org</code>,
 the GNU release site</a>: <a 
href="Distribution-on-ftp_002egnu_002eorg.html#Distribution-on-ftp_002egnu_002eorg">Distribution
 on ftp.gnu.org</a></li>
-<li><a 
href="Invoking-gendocs_002esh.html#index-gendocs_002esh-70"><code>gendocs.sh</code></a>:
 <a href="Invoking-gendocs_002esh.html#Invoking-gendocs_002esh">Invoking 
gendocs.sh</a></li>
-<li><a 
href="Invoking-gendocs_002esh.html#index-generating-documentation-output-71">generating
 documentation output</a>: <a 
href="Invoking-gendocs_002esh.html#Invoking-gendocs_002esh">Invoking 
gendocs.sh</a></li>
-<li><a 
href="Distribution-on-ftp_002egnu_002eorg.html#index-GNU-ftp-site-53">GNU ftp 
site</a>: <a 
href="Distribution-on-ftp_002egnu_002eorg.html#Distribution-on-ftp_002egnu_002eorg">Distribution
 on ftp.gnu.org</a></li>
-<li><a href="Getting-Help.html#index-GNU-system-administrators-14">GNU system 
administrators</a>: <a href="Getting-Help.html#Getting-Help">Getting 
Help</a></li>
-<li><a href="GNU-and-Linux.html#index-GNU_002fLinux-84">GNU/Linux</a>: <a 
href="GNU-and-Linux.html#GNU-and-Linux">GNU and Linux</a></li>
-<li><a 
href="Preface.html#index-g_t_0040code_007bgnustandards_007d-project-repository-3"><code>gnustandards</code>
 project repository</a>: <a href="Preface.html#Preface">Preface</a></li>
-<li><a 
href="Preface.html#index-g_t_0040code_007bgnustandards_002dcommit_0040_0040gnu_002eorg_007d-mailing-list-4"><code>address@hidden</code>
 mailing list</a>: <a href="Preface.html#Preface">Preface</a></li>
-<li><a 
href="Standard-Mailing-Lists.html#index-help-for-users_002c-mailing-list-for-36">help
 for users, mailing list for</a>: <a 
href="Standard-Mailing-Lists.html#Standard-Mailing-Lists">Standard Mailing 
Lists</a></li>
-<li><a href="Replying-to-Mail.html#index-help-requests_002c-handling-43">help 
requests, handling</a>: <a 
href="Replying-to-Mail.html#Replying-to-Mail">Replying to Mail</a></li>
-<li><a href="Getting-Help.html#index-help_002c-getting-6">help, getting</a>: 
<a href="Getting-Help.html#Getting-Help">Getting Help</a></li>
-<li><a href="Hosting.html#index-hosting-91">hosting</a>: <a 
href="Hosting.html#Hosting">Hosting</a></li>
-<li><a 
href="Getting-Help.html#index-g_t_0040url_007bhttp_003a_002f_002fidenti_002eca_002fgroup_002ffsfstatus_007d-11"><a
 
href="http://identi.ca/group/fsfstatus";>http://identi.ca/group/fsfstatus</a></a>:
 <a href="Getting-Help.html#Getting-Help">Getting Help</a></li>
-<li><a 
href="Announcements.html#index-g_t_0040url_007bhttp_003a_002f_002fplanet_002egnu_002eorg_007d-65"><a
 href="http://planet.gnu.org";>http://planet.gnu.org</a></a>: <a 
href="Announcements.html#Announcements">Announcements</a></li>
-<li><a 
href="Announcements.html#index-g_t_0040code_007binfo_002dgnu_007d-mailing-list-64"><code>info-gnu</code>
 mailing list</a>: <a 
href="Announcements.html#Announcements">Announcements</a></li>
-<li><a href="Legal-Matters.html#index-legal-matters-20">legal matters</a>: <a 
href="Legal-Matters.html#Legal-Matters">Legal Matters</a></li>
-<li><a 
href="Copyright-Papers.html#index-legal-papers-for-changes-in-manuals-24">legal 
papers for changes in manuals</a>: <a 
href="Copyright-Papers.html#Copyright-Papers">Copyright Papers</a></li>
-<li><a 
href="License-Notices.html#index-license-notices-in-program-files-28">license 
notices in program files</a>: <a 
href="License-Notices.html#License-Notices">License Notices</a></li>
-<li><a href="GNU-and-Linux.html#index-Linux-83">Linux</a>: <a 
href="GNU-and-Linux.html#GNU-and-Linux">GNU and Linux</a></li>
-<li><a 
href="Standard-Mailing-Lists.html#index-mailing-list-for-bug-reports-34">mailing
 list for bug reports</a>: <a 
href="Standard-Mailing-Lists.html#Standard-Mailing-Lists">Standard Mailing 
Lists</a></li>
-<li><a 
href="Creating-Mailing-Lists.html#index-mailing-lists_002c-creating-39">mailing 
lists, creating</a>: <a 
href="Creating-Mailing-Lists.html#Creating-Mailing-Lists">Creating Mailing 
Lists</a></li>
-<li><a 
href="Standard-Mailing-Lists.html#index-mailing-lists_002c-standard-names-of-33">mailing
 lists, standard names of</a>: <a 
href="Standard-Mailing-Lists.html#Standard-Mailing-Lists">Standard Mailing 
Lists</a></li>
-<li><a 
href="Getting-Help.html#index-g_t_0040code_007bmentors_0040_0040gnu_002eorg_007d-mailing-list-7"><code>address@hidden</code>
 mailing list</a>: <a href="Getting-Help.html#Getting-Help">Getting 
Help</a></li>
-<li><a href="Donations.html#index-Money_002c-donated-to-packages-93">Money, 
donated to packages</a>: <a href="Donations.html#Donations">Donations</a></li>
-<li><a 
href="Free-Software-and-Open-Source.html#index-movement_002c-free-software-81">movement,
 free software</a>: <a 
href="Free-Software-and-Open-Source.html#Free-Software-and-Open-Source">Free 
Software and Open Source</a></li>
-<li><a href="Free-Software-and-Open-Source.html#index-open-source-80">open 
source</a>: <a 
href="Free-Software-and-Open-Source.html#Free-Software-and-Open-Source">Free 
Software and Open Source</a></li>
-<li><a href="Getting-Help.html#index-outage_002c-of-GNU-machines-10">outage, 
of GNU machines</a>: <a href="Getting-Help.html#Getting-Help">Getting 
Help</a></li>
-<li><a href="Distribution-Patches.html#index-patch-51"><code>patch</code></a>: 
<a href="Distribution-Patches.html#Distribution-Patches">Distribution 
Patches</a></li>
-<li><a 
href="Distribution-Patches.html#index-patches_002c-against-previous-releases-49">patches,
 against previous releases</a>: <a 
href="Distribution-Patches.html#Distribution-Patches">Distribution 
Patches</a></li>
-<li><a 
href="Ethical-and-Philosophical-Consideration.html#index-philosophy-77">philosophy</a>:
 <a 
href="Ethical-and-Philosophical-Consideration.html#Ethical-and-Philosophical-Consideration">Ethical
 and Philosophical Consideration</a></li>
-<li><a href="Preface.html#index-Piercy_002c-Marge-5">Piercy, Marge</a>: <a 
href="Preface.html#Preface">Preface</a></li>
-<li><a href="Test-Releases.html#index-pretest-releases-57">pretest 
releases</a>: <a href="Test-Releases.html#Test-Releases">Test Releases</a></li>
-<li><a 
href="Using-the-Proofreaders-List.html#index-proofreading-96">proofreading</a>: 
<a href="Using-the-Proofreaders-List.html#Using-the-Proofreaders-List">Using 
the Proofreaders List</a></li>
-<li><a 
href="Clean-Ups.html#index-quality-of-changes-suggested-by-others-30">quality 
of changes suggested by others</a>: <a href="Clean-Ups.html#Clean-Ups">Clean 
Ups</a></li>
-<li><a 
href="CVS-Keywords-in-Web-Pages.html#index-RCS-keywords-in-web-pages-73">RCS 
keywords in web pages</a>: <a 
href="CVS-Keywords-in-Web-Pages.html#CVS-Keywords-in-Web-Pages">CVS Keywords in 
Web Pages</a></li>
-<li><a 
href="Recording-Contributors.html#index-recording-contributors-25">recording 
contributors</a>: <a 
href="Recording-Contributors.html#Recording-Contributors">Recording 
Contributors</a></li>
-<li><a 
href="Automated-Upload-Registration.html#index-registration-for-uploads-60">registration
 for uploads</a>: <a 
href="Automated-Upload-Registration.html#Automated-Upload-Registration">Automated
 Upload Registration</a></li>
-<li><a href="Hosting.html#index-release-site-90">release site</a>: <a 
href="Hosting.html#Hosting">Hosting</a></li>
-<li><a href="Hosting.html#index-repository-86">repository</a>: <a 
href="Hosting.html#Hosting">Hosting</a></li>
-<li><a href="Stepping-Down.html#index-resigning-as-maintainer-18">resigning as 
maintainer</a>: <a href="Stepping-Down.html#Stepping-Down">Stepping 
Down</a></li>
-<li><a 
href="Replying-to-Mail.html#index-responding-to-bug-reports-41">responding to 
bug reports</a>: <a href="Replying-to-Mail.html#Replying-to-Mail">Replying to 
Mail</a></li>
-<li><a 
href="Preface.html#index-Savannah-repository-for-_0040code_007bgnustandards_007d-2">Savannah
 repository for <code>gnustandards</code></a>: <a 
href="Preface.html#Preface">Preface</a></li>
-<li><a href="Announcements.html#index-Savannah_002c-news-area-66">Savannah, 
news area</a>: <a href="Announcements.html#Announcements">Announcements</a></li>
-<li><a 
href="Old-Versions.html#index-g_t_0040code_007bsavannah_002dannounce_0040_0040gnu_002eorg_007d-mailing-list-46"><code>address@hidden</code>
 mailing list</a>: <a href="Old-Versions.html#Old-Versions">Old 
Versions</a></li>
-<li><a 
href="Old-Versions.html#index-g_t_0040code_007bsavannah_002dhackers_0040_0040gnu_002eorg_007d-45"><code>address@hidden</code></a>:
 <a href="Old-Versions.html#Old-Versions">Old Versions</a></li>
-<li><a 
href="Getting-a-GNU-Account.html#index-shell-account_002c-on-fencepost-15">shell
 account, on fencepost</a>: <a 
href="Getting-a-GNU-Account.html#Getting-a-GNU-Account">Getting a GNU 
Account</a></li>
-<li><a href="Hosting.html#index-source-repository-87">source repository</a>: 
<a href="Hosting.html#Hosting">Hosting</a></li>
-<li><a href="Creating-Mailing-Lists.html#index-spam-prevention-40">spam 
prevention</a>: <a 
href="Creating-Mailing-Lists.html#Creating-Mailing-Lists">Creating Mailing 
Lists</a></li>
-<li><a 
href="Standard-Mailing-Lists.html#index-standard-mailing-lists-32">standard 
mailing lists</a>: <a 
href="Standard-Mailing-Lists.html#Standard-Mailing-Lists">Standard Mailing 
Lists</a></li>
-<li><a href="Stepping-Down.html#index-stepping-down-as-maintainer-17">stepping 
down as maintainer</a>: <a href="Stepping-Down.html#Stepping-Down">Stepping 
Down</a></li>
-<li><a href="Getting-Help.html#index-sysadmin_002c-FSF-12">sysadmin, FSF</a>: 
<a href="Getting-Help.html#Getting-Help">Getting Help</a></li>
-<li><a href="Terminology.html#index-terminology-78">terminology</a>: <a 
href="Terminology.html#Terminology">Terminology</a></li>
-<li><a href="Test-Releases.html#index-test-releases-55">test releases</a>: <a 
href="Test-Releases.html#Test-Releases">Test Releases</a></li>
-<li><a href="Distribution-Patches.html#index-time-stamp-in-diffs-52">time 
stamp in diffs</a>: <a 
href="Distribution-Patches.html#Distribution-Patches">Distribution 
Patches</a></li>
-<li><a href="Automated-Upload-Procedure.html#index-uploads-62">uploads</a>: <a 
href="Automated-Upload-Procedure.html#Automated-Upload-Procedure">Automated 
Upload Procedure</a></li>
-<li><a 
href="Automated-Upload-Registration.html#index-uploads_002c-registration-for-61">uploads,
 registration for</a>: <a 
href="Automated-Upload-Registration.html#Automated-Upload-Registration">Automated
 Upload Registration</a></li>
-<li><a href="Old-Versions.html#index-version-control-44">version control</a>: 
<a href="Old-Versions.html#Old-Versions">Old Versions</a></li>
-<li><a href="Hosting.html#index-version-control-system-88">version control 
system</a>: <a href="Hosting.html#Hosting">Hosting</a></li>
-<li><a href="Web-Pages.html#index-web-pages-69">web pages</a>: <a 
href="Web-Pages.html#Web-Pages">Web Pages</a></li>
-<li><a 
href="CVS-Keywords-in-Web-Pages.html#index-web-pages_002c-and-CVS-keywords-75">web
 pages, and CVS keywords</a>: <a 
href="CVS-Keywords-in-Web-Pages.html#CVS-Keywords-in-Web-Pages">CVS Keywords in 
Web Pages</a></li>
-   </ul></body></html>
 
+</p>
+</body>
+</html>

Index: html_node/Invoking-gendocs_002esh.html
===================================================================
RCS file: /web/www/www/prep/maintain/html_node/Invoking-gendocs_002esh.html,v
retrieving revision 1.66
retrieving revision 1.67
diff -u -b -r1.66 -r1.67
--- html_node/Invoking-gendocs_002esh.html      7 Sep 2011 01:31:18 -0000       
1.66
+++ html_node/Invoking-gendocs_002esh.html      7 Sep 2011 15:00:35 -0000       
1.67
@@ -1,126 +1,172 @@
-<html lang="en">
-<head>
-<title>Invoking gendocs.sh - Information for Maintainers of GNU 
Software</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="Information for Maintainers of GNU Software">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="Manuals-on-Web-Pages.html#Manuals-on-Web-Pages" 
title="Manuals on Web Pages">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home" 
title="Texinfo Homepage">
-<!--
-Information for maintainers of GNU software, last updated September 5, 2011.
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" 
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
+<!-- Information for maintainers of GNU software, last updated September 5, 
2011.
 
 Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
 2010, 2011 Free Software Foundation, Inc.
 
-     Permission is granted to copy, distribute and/or modify this
-     document under the terms of the GNU Free Documentation License,
-     Version 1.3 or any later version published by the Free Software
-     Foundation; with no Invariant Sections, with no Front-Cover Texts,
-     and with no Back-Cover Texts.  A copy of the license is included
-     in the section entitled ``GNU Free Documentation License''.
-   -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
-  pre.display { font-family:inherit }
-  pre.format  { font-family:inherit }
-  pre.smalldisplay { font-family:inherit; font-size:smaller }
-  pre.smallformat  { font-family:inherit; font-size:smaller }
-  pre.smallexample { font-size:smaller }
-  pre.smalllisp    { font-size:smaller }
-  span.sc    { font-variant:small-caps }
-  span.roman { font-family:serif; font-weight:normal; } 
-  span.sansserif { font-family:sans-serif; font-weight:normal; } 
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
+Texts.  A copy of the license is included in the section entitled
+"GNU Free Documentation License". -->
+<!-- Created by texi2html, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>Information for Maintainers of GNU Software: Invoking gendocs.sh</title>
+
+<meta name="description" content="Information for Maintainers of GNU Software: 
Invoking gendocs.sh">
+<meta name="keywords" content="Information for Maintainers of GNU Software: 
Invoking gendocs.sh">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="texi2html">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Manuals-on-Web-Pages.html#Manuals-on-Web-Pages" rel="up" 
title="Manuals on Web Pages">
+<link href="CVS-Keywords-in-Web-Pages.html#CVS-Keywords-in-Web-Pages" 
rel="next" title="CVS Keywords in Web Pages">
+<link href="Manuals-on-Web-Pages.html#Manuals-on-Web-Pages" rel="previous" 
title="Manuals on Web Pages">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smalllisp {margin-left: 3.2em}
+pre.display {font-family: serif}
+pre.format {font-family: serif}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: serif; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: serif; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:pre}
+span.nolinebreak {white-space:pre}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
 </head>
-<body>
-<div class="node">
-<a name="Invoking-gendocs.sh"></a>
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF" 
vlink="#800080" alink="#FF0000">
+
 <a name="Invoking-gendocs_002esh"></a>
+<div class="header">
 <p>
-Up:&nbsp;<a rel="up" accesskey="u" 
href="Manuals-on-Web-Pages.html#Manuals-on-Web-Pages">Manuals on Web Pages</a>
-<hr>
+Up: <a href="Manuals-on-Web-Pages.html#Manuals-on-Web-Pages" accesskey="u" 
rel="up">Manuals on Web Pages</a> &nbsp; [<a href="index.html#SEC_Contents" 
title="Table of contents" rel="contents">Contents</a>][<a 
href="Index.html#Index" title="Index" rel="index">Index</a>]</p>
 </div>
+<hr>
+<a name="Invoking-gendocs_002esh-1"></a>
+<h3 class="subsection">12.3.1 Invoking <code>gendocs.sh</code></h3>
+<a name="index-gendocs_002esh"></a>
+<a name="index-generating-documentation-output"></a>
 
-<h4 class="subsection">12.3.1 Invoking <samp><span 
class="command">gendocs.sh</span></samp></h4>
-
-<p><a name="index-gendocs_002esh-70"></a><a 
name="index-generating-documentation-output-71"></a>
-The script <samp><span class="command">gendocs.sh</span></samp> eases the task 
of generating the
+<p>The script <code>gendocs.sh</code> eases the task of generating the
 Texinfo documentation output for your web pages
 section above.  It has a companion template file, used as the basis
 for the HTML index pages.  Both are available from the Texinfo CVS
 sources:
-
+</p>
+<div class="smallformat">
 <pre class="smallformat"><a 
href="http://savannah.gnu.org/cgi-bin/viewcvs/texinfo/texinfo/util/gendocs.sh";>http://savannah.gnu.org/cgi-bin/viewcvs/texinfo/texinfo/util/gendocs.sh</a>
 <a 
href="http://savannah.gnu.org/cgi-bin/viewcvs/texinfo/texinfo/util/gendocs_template";>http://savannah.gnu.org/cgi-bin/viewcvs/texinfo/texinfo/util/gendocs_template</a>
-</pre>
-   <p>There is also a minimalistic template, available from:
+</pre></div>
 
+<p>There is also a minimalistic template, available from:
+</p>
+<div class="smallformat">
 <pre class="smallformat"><a 
href="http://savannah.gnu.org/cgi-bin/viewcvs/texinfo/texinfo/util/gendocs_template_min";>http://savannah.gnu.org/cgi-bin/viewcvs/texinfo/texinfo/util/gendocs_template_min</a>
-</pre>
-   <p>Invoke the script like this, in the directory containing the Texinfo
+</pre></div>
+
+<p>Invoke the script like this, in the directory containing the Texinfo
 source:
+</p>
+<div class="smallexample">
+<pre class="smallexample">gendocs.sh --email <var>yourbuglist</var> 
<var>yourmanual</var> &quot;GNU <var>yourmanual</var> manual&quot;
+</pre></div>
 
-<pre class="smallexample">     gendocs.sh --email <var>yourbuglist</var> 
<var>yourmanual</var> "GNU <var>yourmanual</var> manual"
-</pre>
-   <p class="noindent">where <var>yourmanual</var> is the short name for your 
package
+<p>where <var>yourmanual</var> is the short name for your package
 and <var>yourbuglist</var> is the email address for bug reports (typically
-<code>bug-</code><var>package</var><code>@gnu.org</code>).  The script 
processes the file
-<samp><var>yourmanual</var><span class="file">.texinfo</span></samp> (or 
<samp><span class="file">.texi</span></samp> or <samp><span 
class="file">.txi</span></samp>).  For
+<code>bug-<var>package</var>@gnu.org</code>).  The script processes the file
+&lsquo;<tt><var>yourmanual</var>.texinfo</tt>&rsquo; (or 
&lsquo;<tt>.texi</tt>&rsquo; or &lsquo;<tt>.txi</tt>&rsquo;).  For
 example:
+</p>
+<div class="smallexample">
+<pre class="smallexample">cd .../emacs/man
+# download gendocs.sh and gendocs_template
+gendocs.sh --email address@hidden emacs &quot;GNU Emacs manual&quot;
+</pre></div>
 
-<pre class="smallexample">     cd .../emacs/man
-     # download gendocs.sh and gendocs_template
-     gendocs.sh --email address@hidden emacs "GNU Emacs manual"
-</pre>
-   <p><samp><span class="command">gendocs.sh</span></samp> creates a 
subdirectory <samp><span class="file">manual/</span></samp> containing
+<p><code>gendocs.sh</code> creates a subdirectory 
&lsquo;<tt>manual/</tt>&rsquo; containing
 the manual generated in all the standard output formats: Info, HTML,
 DVI, and so on, as well as the Texinfo source.  You then need to move
 all those files, retaining the subdirectories, into the web pages for
 your package.
-
-   <p>You can specify the option <samp><span class="option">-o 
</span><var>outdir</var></samp> to override the
-name <samp><span class="file">manual</span></samp>.  Any previous contents of 
<var>outdir</var> will be deleted.
-
-   <p>The second argument, with the description, is included as part of the
-HTML <code>&lt;title&gt;</code> of the overall <samp><span 
class="file">manual/index.html</span></samp> file.  It
+</p>
+<p>You can specify the option &lsquo;<samp>-o <var>outdir</var></samp>&rsquo; 
to override the
+name &lsquo;<tt>manual</tt>&rsquo;.  Any previous contents of 
<var>outdir</var> will be deleted.
+</p>
+<p>The second argument, with the description, is included as part of the
+HTML <code>&lt;title&gt;</code> of the overall 
&lsquo;<tt>manual/index.html</tt>&rsquo; file.  It
 should include the name of the package being documented, as shown. 
-<samp><span class="file">manual/index.html</span></samp> is created by 
substitution from the file
-<samp><span class="file">gendocs_template</span></samp>.  (Feel free to modify 
the generic template
+&lsquo;<tt>manual/index.html</tt>&rsquo; is created by substitution from the 
file
+&lsquo;<tt>gendocs_template</tt>&rsquo;.  (Feel free to modify the generic 
template
 for your own purposes.)
-
-   <p>If you have several manuals, you'll need to run this script several
+</p>
+<p>If you have several manuals, you&rsquo;ll need to run this script several
 times with different arguments, specifying a different output
-directory with <samp><span class="option">-o</span></samp> each time, and 
moving all the output to
+directory with &lsquo;<samp>-o</samp>&rsquo; each time, and moving all the 
output to
 your web page.  Then write (by hand) an overall index.html with links
 to them all.  For example:
+</p>
+<div class="smallexample">
+<pre class="smallexample">cd .../texinfo/doc
+gendocs.sh --email address@hidden -o texinfo texinfo &quot;GNU Texinfo 
manual&quot;
+gendocs.sh --email address@hidden -o info info &quot;GNU Info manual&quot;
+gendocs.sh --email address@hidden -o info-stnd info-stnd &quot;GNU info-stnd 
manual&quot;
+</pre></div>
+
+<p>By default, the script uses <code>makeinfo</code> for generating
+<acronym>HTML</acronym> output.  If you prefer to use <code>texi2html</code>, 
use
+the &lsquo;<samp>--texi2html</samp>&rsquo; command line option, e.g.:
+</p>
+<div class="smallexample">
+<pre class="smallexample">gendocs --texi2html -o texinfo texinfo &quot;GNU 
Texinfo manual&quot;
+</pre></div>
 
-<pre class="smallexample">     cd .../texinfo/doc
-     gendocs.sh --email address@hidden -o texinfo texinfo "GNU Texinfo manual"
-     gendocs.sh --email address@hidden -o info info "GNU Info manual"
-     gendocs.sh --email address@hidden -o info-stnd info-stnd "GNU info-stnd 
manual"
-</pre>
-   <p>By default, the script uses <samp><span 
class="command">makeinfo</span></samp> for generating
-<acronym>HTML</acronym> output.  If you prefer to use <samp><span 
class="command">texi2html</span></samp>, use
-the <samp><span class="option">--texi2html</span></samp> command line option, 
e.g.:
-
-<pre class="smallexample">     gendocs --texi2html -o texinfo texinfo "GNU 
Texinfo manual"
-</pre>
-   <p>The template files will automatically produce entries for additional
-HTML output generated by <samp><span class="command">texi2html</span></samp> 
(i.e., split by sections
+<p>The template files will automatically produce entries for additional
+HTML output generated by <code>texi2html</code> (i.e., split by sections
 and chapters).
-
-   <p>You can set the environment variables <samp><span 
class="env">MAKEINFO</span></samp>, <samp><span 
class="env">TEXI2DVI</span></samp>,
-<samp><span class="env">TEXI2HTML</span></samp> and <samp><span 
class="env">DVIPS</span></samp> to control the programs that get
-executed, and <samp><span class="env">GENDOCS_TEMPLATE_DIR</span></samp> to 
control where the
-<samp><span class="file">gendocs_template</span></samp> file is found.
-
-   <p>As usual, run &lsquo;<samp><span class="samp">gendocs.sh 
--help</span></samp>&rsquo; for a description of all the
+</p>
+<p>You can set the environment variables <code>MAKEINFO</code>, 
<code>TEXI2DVI</code>,
+<code>TEXI2HTML</code> and <code>DVIPS</code> to control the programs that get
+executed, and <code>GENDOCS_TEMPLATE_DIR</code> to control where the
+&lsquo;<tt>gendocs_template</tt>&rsquo; file is found.
+</p>
+<p>As usual, run &lsquo;<samp>gendocs.sh --help</samp>&rsquo; for a 
description of all the
 options, environment variables, and more information.
-
-   <p>Please email bug reports, enhancement requests, or other
+</p>
+<p>Please email bug reports, enhancement requests, or other
 correspondence to <a href="mailto:address@hidden";>address@hidden</a>.
+</p>
+
+<hr>
+<div class="header">
+<p>
+Up: <a href="Manuals-on-Web-Pages.html#Manuals-on-Web-Pages" accesskey="u" 
rel="up">Manuals on Web Pages</a> &nbsp; [<a href="index.html#SEC_Contents" 
title="Table of contents" rel="contents">Contents</a>][<a 
href="Index.html#Index" title="Index" rel="index">Index</a>]</p>
+</div>
+<p>
 
-   </body></html>
 
+</p>
+</body>
+</html>

Index: html_node/Legal-Matters.html
===================================================================
RCS file: /web/www/www/prep/maintain/html_node/Legal-Matters.html,v
retrieving revision 1.66
retrieving revision 1.67
diff -u -b -r1.66 -r1.67
--- html_node/Legal-Matters.html        7 Sep 2011 01:31:18 -0000       1.66
+++ html_node/Legal-Matters.html        7 Sep 2011 15:00:35 -0000       1.67
@@ -1,65 +1,97 @@
-<html lang="en">
-<head>
-<title>Legal Matters - Information for Maintainers of GNU Software</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="Information for Maintainers of GNU Software">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="prev" href="Recruiting-Developers.html#Recruiting-Developers" 
title="Recruiting Developers">
-<link rel="next" href="Clean-Ups.html#Clean-Ups" title="Clean Ups">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home" 
title="Texinfo Homepage">
-<!--
-Information for maintainers of GNU software, last updated September 5, 2011.
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" 
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
+<!-- Information for maintainers of GNU software, last updated September 5, 
2011.
 
 Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
 2010, 2011 Free Software Foundation, Inc.
 
-     Permission is granted to copy, distribute and/or modify this
-     document under the terms of the GNU Free Documentation License,
-     Version 1.3 or any later version published by the Free Software
-     Foundation; with no Invariant Sections, with no Front-Cover Texts,
-     and with no Back-Cover Texts.  A copy of the license is included
-     in the section entitled ``GNU Free Documentation License''.
-   -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
-  pre.display { font-family:inherit }
-  pre.format  { font-family:inherit }
-  pre.smalldisplay { font-family:inherit; font-size:smaller }
-  pre.smallformat  { font-family:inherit; font-size:smaller }
-  pre.smallexample { font-size:smaller }
-  pre.smalllisp    { font-size:smaller }
-  span.sc    { font-variant:small-caps }
-  span.roman { font-family:serif; font-weight:normal; } 
-  span.sansserif { font-family:sans-serif; font-weight:normal; } 
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
+Texts.  A copy of the license is included in the section entitled
+"GNU Free Documentation License". -->
+<!-- Created by texi2html, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>Information for Maintainers of GNU Software: Legal Matters</title>
+
+<meta name="description" content="Information for Maintainers of GNU Software: 
Legal Matters">
+<meta name="keywords" content="Information for Maintainers of GNU Software: 
Legal Matters">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="texi2html">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="index.html#Top" rel="up" title="Top">
+<link href="Copyright-Papers.html#Copyright-Papers" rel="next" 
title="Copyright Papers">
+<link href="Recruiting-Developers.html#Recruiting-Developers" rel="previous" 
title="Recruiting Developers">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smalllisp {margin-left: 3.2em}
+pre.display {font-family: serif}
+pre.format {font-family: serif}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: serif; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: serif; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:pre}
+span.nolinebreak {white-space:pre}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
 </head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF" 
vlink="#800080" alink="#FF0000">
+
 <a name="Legal-Matters"></a>
+<div class="header">
 <p>
-Next:&nbsp;<a rel="next" accesskey="n" href="Clean-Ups.html#Clean-Ups">Clean 
Ups</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" 
href="Recruiting-Developers.html#Recruiting-Developers">Recruiting 
Developers</a>,
-Up:&nbsp;<a rel="up" accesskey="u" href="index.html#Top">Top</a>
-<hr>
+Next: <a href="Clean-Ups.html#Clean-Ups" accesskey="n" rel="next">Clean 
Ups</a>, Previous: <a href="Recruiting-Developers.html#Recruiting-Developers" 
accesskey="p" rel="previous">Recruiting Developers</a>, Up: <a 
href="index.html#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a 
href="index.html#SEC_Contents" title="Table of contents" 
rel="contents">Contents</a>][<a href="Index.html#Index" title="Index" 
rel="index">Index</a>]</p>
 </div>
+<hr>
+<a name="Legal-Matters-1"></a>
+<h1 class="chapter">6 Legal Matters</h1>
+<a name="index-legal-matters"></a>
 
-<h2 class="chapter">6 Legal Matters</h2>
-
-<p><a name="index-legal-matters-20"></a>
-This chapter describes procedures you should follow for legal reasons
+<p>This chapter describes procedures you should follow for legal reasons
 as you maintain the program, to avoid legal difficulties.
+</p>
+<table class="menu" border="0" cellspacing="0">
+<tr><td align="left" valign="top">&bull; <a 
href="Copyright-Papers.html#Copyright-Papers" accesskey="1">Copyright 
Papers</a>:</td><td>&nbsp;&nbsp;</td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a 
href="Legally-Significant.html#Legally-Significant" accesskey="2">Legally 
Significant</a>:</td><td>&nbsp;&nbsp;</td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a 
href="Recording-Contributors.html#Recording-Contributors" 
accesskey="3">Recording Contributors</a>:</td><td>&nbsp;&nbsp;</td><td 
align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a 
href="Copying-from-Other-Packages.html#Copying-from-Other-Packages" 
accesskey="4">Copying from Other Packages</a>:</td><td>&nbsp;&nbsp;</td><td 
align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a 
href="Copyright-Notices.html#Copyright-Notices" accesskey="5">Copyright 
Notices</a>:</td><td>&nbsp;&nbsp;</td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a 
href="License-Notices.html#License-Notices" accesskey="6">License 
Notices</a>:</td><td>&nbsp;&nbsp;</td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a 
href="External-Libraries.html#External-Libraries" accesskey="7">External 
Libraries</a>:</td><td>&nbsp;&nbsp;</td><td align="left" valign="top">
+</td></tr>
+</table>
 
-<ul class="menu">
-<li><a accesskey="1" href="Copyright-Papers.html#Copyright-Papers">Copyright 
Papers</a>
-<li><a accesskey="2" 
href="Legally-Significant.html#Legally-Significant">Legally Significant</a>
-<li><a accesskey="3" 
href="Recording-Contributors.html#Recording-Contributors">Recording 
Contributors</a>
-<li><a accesskey="4" 
href="Copying-from-Other-Packages.html#Copying-from-Other-Packages">Copying 
from Other Packages</a>
-<li><a accesskey="5" href="Copyright-Notices.html#Copyright-Notices">Copyright 
Notices</a>
-<li><a accesskey="6" href="License-Notices.html#License-Notices">License 
Notices</a>
-<li><a accesskey="7" 
href="External-Libraries.html#External-Libraries">External Libraries</a>
-</ul>
+<p>
 
-   </body></html>
 
+</p>
+</body>
+</html>

Index: html_node/Legally-Significant.html
===================================================================
RCS file: /web/www/www/prep/maintain/html_node/Legally-Significant.html,v
retrieving revision 1.66
retrieving revision 1.67
diff -u -b -r1.66 -r1.67
--- html_node/Legally-Significant.html  7 Sep 2011 01:31:18 -0000       1.66
+++ html_node/Legally-Significant.html  7 Sep 2011 15:00:35 -0000       1.67
@@ -1,101 +1,134 @@
-<html lang="en">
-<head>
-<title>Legally Significant - Information for Maintainers of GNU 
Software</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="Information for Maintainers of GNU Software">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="Legal-Matters.html#Legal-Matters" title="Legal Matters">
-<link rel="prev" href="Copyright-Papers.html#Copyright-Papers" 
title="Copyright Papers">
-<link rel="next" href="Recording-Contributors.html#Recording-Contributors" 
title="Recording Contributors">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home" 
title="Texinfo Homepage">
-<!--
-Information for maintainers of GNU software, last updated September 5, 2011.
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" 
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
+<!-- Information for maintainers of GNU software, last updated September 5, 
2011.
 
 Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
 2010, 2011 Free Software Foundation, Inc.
 
-     Permission is granted to copy, distribute and/or modify this
-     document under the terms of the GNU Free Documentation License,
-     Version 1.3 or any later version published by the Free Software
-     Foundation; with no Invariant Sections, with no Front-Cover Texts,
-     and with no Back-Cover Texts.  A copy of the license is included
-     in the section entitled ``GNU Free Documentation License''.
-   -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
-  pre.display { font-family:inherit }
-  pre.format  { font-family:inherit }
-  pre.smalldisplay { font-family:inherit; font-size:smaller }
-  pre.smallformat  { font-family:inherit; font-size:smaller }
-  pre.smallexample { font-size:smaller }
-  pre.smalllisp    { font-size:smaller }
-  span.sc    { font-variant:small-caps }
-  span.roman { font-family:serif; font-weight:normal; } 
-  span.sansserif { font-family:sans-serif; font-weight:normal; } 
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
+Texts.  A copy of the license is included in the section entitled
+"GNU Free Documentation License". -->
+<!-- Created by texi2html, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>Information for Maintainers of GNU Software: Legally Significant</title>
+
+<meta name="description" content="Information for Maintainers of GNU Software: 
Legally Significant">
+<meta name="keywords" content="Information for Maintainers of GNU Software: 
Legally Significant">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="texi2html">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Legal-Matters.html#Legal-Matters" rel="up" title="Legal Matters">
+<link href="Recording-Contributors.html#Recording-Contributors" rel="next" 
title="Recording Contributors">
+<link href="Copyright-Papers.html#Copyright-Papers" rel="previous" 
title="Copyright Papers">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smalllisp {margin-left: 3.2em}
+pre.display {font-family: serif}
+pre.format {font-family: serif}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: serif; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: serif; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:pre}
+span.nolinebreak {white-space:pre}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
 </head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF" 
vlink="#800080" alink="#FF0000">
+
 <a name="Legally-Significant"></a>
+<div class="header">
 <p>
-Next:&nbsp;<a rel="next" accesskey="n" 
href="Recording-Contributors.html#Recording-Contributors">Recording 
Contributors</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" 
href="Copyright-Papers.html#Copyright-Papers">Copyright Papers</a>,
-Up:&nbsp;<a rel="up" accesskey="u" 
href="Legal-Matters.html#Legal-Matters">Legal Matters</a>
-<hr>
+Next: <a href="Recording-Contributors.html#Recording-Contributors" 
accesskey="n" rel="next">Recording Contributors</a>, Previous: <a 
href="Copyright-Papers.html#Copyright-Papers" accesskey="p" 
rel="previous">Copyright Papers</a>, Up: <a 
href="Legal-Matters.html#Legal-Matters" accesskey="u" rel="up">Legal 
Matters</a> &nbsp; [<a href="index.html#SEC_Contents" title="Table of contents" 
rel="contents">Contents</a>][<a href="Index.html#Index" title="Index" 
rel="index">Index</a>]</p>
 </div>
-
-<h3 class="section">6.2 Legally Significant Changes</h3>
+<hr>
+<a name="Legally-Significant-Changes"></a>
+<h2 class="section">6.2 Legally Significant Changes</h2>
 
 <p>If a person contributes more than around 15 lines of code and/or text
 that is legally significant for copyright purposes, we
 need copyright papers for that contribution, as described above.
-
-   <p>A change of just a few lines (less than 15 or so) is not legally
+</p>
+<p>A change of just a few lines (less than 15 or so) is not legally
 significant for copyright.  A regular series of repeated changes, such
 as renaming a symbol, is not legally significant even if the symbol
 has to be renamed in many places.  Keep in mind, however, that a
 series of minor changes by the same person can add up to a significant
 contribution.  What counts is the total contribution of the person; it
 is irrelevant which parts of it were contributed when.
-
-   <p>Copyright does not cover ideas.  If someone contributes ideas but no
+</p>
+<p>Copyright does not cover ideas.  If someone contributes ideas but no
 text, these ideas may be morally significant as contributions, and
 worth giving credit for, but they are not significant for copyright
 purposes.  Likewise, bug reports do not count for copyright purposes.
-
-   <p>When giving credit to people whose contributions are not legally
+</p>
+<p>When giving credit to people whose contributions are not legally
 significant for copyright purposes, be careful to make that fact
 clear.  The credit should clearly say they did not contribute
 significant code or text.
-
-   <p>When people's contributions are not legally significant because they
+</p>
+<p>When people&rsquo;s contributions are not legally significant because they
 did not write code, do this by stating clearly what their contribution
 was.  For instance, you could write this:
-
-<pre class="example">     /*
+</p>
+<div class="example">
+<pre class="example">/*
       * Ideas by:
       *   Richard Mlynarik &lt;address@hidden&gt; (1997)
       *   Masatake Yamato &lt;address@hidden&gt; (1999)
       */
-</pre>
-   <p class="noindent"><code>Ideas by:</code> makes it clear that Mlynarik and 
Yamato here
+</pre></div>
+
+<p><code>Ideas by:</code> makes it clear that Mlynarik and Yamato here
 contributed only ideas, not code.  Without the <code>Ideas by:</code> note,
 several years from now we would find it hard to be sure whether they
 had contributed code, and we might have to track them down and ask
 them.
-
-   <p>When you record a small patch in a change log file, first search for
+</p>
+<p>When you record a small patch in a change log file, first search for
 previous changes by the same person, and see if per past
 contributions, plus the new one, add up to something legally
 significant.  If so, you should get copyright papers for all per
 changes before you install the new change.
+</p>
+<p>If that is not so, you can install the small patch.  Write 
&lsquo;<samp>(tiny
+change)</samp>&rsquo; after the patch author&rsquo;s name, like this:
+</p>
+<div class="example">
+<pre class="example">2002-11-04  Robert Fenk  &lt;address@hidden&gt;  (tiny 
change)
+</pre></div>
 
-   <p>If that is not so, you can install the small patch.  Write 
&lsquo;<samp><span class="samp">(tiny
-change)</span></samp>&rsquo; after the patch author's name, like this:
+<hr>
+<div class="header">
+<p>
+Next: <a href="Recording-Contributors.html#Recording-Contributors" 
accesskey="n" rel="next">Recording Contributors</a>, Previous: <a 
href="Copyright-Papers.html#Copyright-Papers" accesskey="p" 
rel="previous">Copyright Papers</a>, Up: <a 
href="Legal-Matters.html#Legal-Matters" accesskey="u" rel="up">Legal 
Matters</a> &nbsp; [<a href="index.html#SEC_Contents" title="Table of contents" 
rel="contents">Contents</a>][<a href="Index.html#Index" title="Index" 
rel="index">Index</a>]</p>
+</div>
+<p>
 
-<pre class="example">     2002-11-04  Robert Fenk  &lt;address@hidden&gt;  
(tiny change)
-</pre>
-   </body></html>
 
+</p>
+</body>
+</html>

Index: html_node/License-Notices-for-Code.html
===================================================================
RCS file: /web/www/www/prep/maintain/html_node/License-Notices-for-Code.html,v
retrieving revision 1.50
retrieving revision 1.51
diff -u -b -r1.50 -r1.51
--- html_node/License-Notices-for-Code.html     7 Sep 2011 01:31:18 -0000       
1.50
+++ html_node/License-Notices-for-Code.html     7 Sep 2011 15:00:37 -0000       
1.51
@@ -1,96 +1,126 @@
-<html lang="en">
-<head>
-<title>License Notices for Code - Information for Maintainers of GNU 
Software</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="Information for Maintainers of GNU Software">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="License-Notices.html#License-Notices" title="License 
Notices">
-<link rel="prev" 
href="Canonical-License-Sources.html#Canonical-License-Sources" 
title="Canonical License Sources">
-<link rel="next" 
href="License-Notices-for-Documentation.html#License-Notices-for-Documentation" 
title="License Notices for Documentation">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home" 
title="Texinfo Homepage">
-<!--
-Information for maintainers of GNU software, last updated September 5, 2011.
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" 
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
+<!-- Information for maintainers of GNU software, last updated September 5, 
2011.
 
 Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
 2010, 2011 Free Software Foundation, Inc.
 
-     Permission is granted to copy, distribute and/or modify this
-     document under the terms of the GNU Free Documentation License,
-     Version 1.3 or any later version published by the Free Software
-     Foundation; with no Invariant Sections, with no Front-Cover Texts,
-     and with no Back-Cover Texts.  A copy of the license is included
-     in the section entitled ``GNU Free Documentation License''.
-   -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
-  pre.display { font-family:inherit }
-  pre.format  { font-family:inherit }
-  pre.smalldisplay { font-family:inherit; font-size:smaller }
-  pre.smallformat  { font-family:inherit; font-size:smaller }
-  pre.smallexample { font-size:smaller }
-  pre.smalllisp    { font-size:smaller }
-  span.sc    { font-variant:small-caps }
-  span.roman { font-family:serif; font-weight:normal; } 
-  span.sansserif { font-family:sans-serif; font-weight:normal; } 
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
+Texts.  A copy of the license is included in the section entitled
+"GNU Free Documentation License". -->
+<!-- Created by texi2html, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>Information for Maintainers of GNU Software: License Notices for 
Code</title>
+
+<meta name="description" content="Information for Maintainers of GNU Software: 
License Notices for Code">
+<meta name="keywords" content="Information for Maintainers of GNU Software: 
License Notices for Code">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="texi2html">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="License-Notices.html#License-Notices" rel="up" title="License 
Notices">
+<link 
href="License-Notices-for-Documentation.html#License-Notices-for-Documentation" 
rel="next" title="License Notices for Documentation">
+<link href="Canonical-License-Sources.html#Canonical-License-Sources" 
rel="previous" title="Canonical License Sources">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smalllisp {margin-left: 3.2em}
+pre.display {font-family: serif}
+pre.format {font-family: serif}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: serif; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: serif; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:pre}
+span.nolinebreak {white-space:pre}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
 </head>
-<body>
-<div class="node">
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF" 
vlink="#800080" alink="#FF0000">
+
 <a name="License-Notices-for-Code"></a>
+<div class="header">
 <p>
-Next:&nbsp;<a rel="next" accesskey="n" 
href="License-Notices-for-Documentation.html#License-Notices-for-Documentation">License
 Notices for Documentation</a>,
-Previous:&nbsp;<a rel="previous" accesskey="p" 
href="Canonical-License-Sources.html#Canonical-License-Sources">Canonical 
License Sources</a>,
-Up:&nbsp;<a rel="up" accesskey="u" 
href="License-Notices.html#License-Notices">License Notices</a>
-<hr>
+Next: <a 
href="License-Notices-for-Documentation.html#License-Notices-for-Documentation" 
accesskey="n" rel="next">License Notices for Documentation</a>, Previous: <a 
href="Canonical-License-Sources.html#Canonical-License-Sources" accesskey="p" 
rel="previous">Canonical License Sources</a>, Up: <a 
href="License-Notices.html#License-Notices" accesskey="u" rel="up">License 
Notices</a> &nbsp; [<a href="index.html#SEC_Contents" title="Table of contents" 
rel="contents">Contents</a>][<a href="Index.html#Index" title="Index" 
rel="index">Index</a>]</p>
 </div>
-
-<h4 class="subsection">6.6.3 License Notices for Code</h4>
+<hr>
+<a name="License-Notices-for-Code-1"></a>
+<h3 class="subsection">6.6.3 License Notices for Code</h3>
 
 <p>Typically the license notice for program files (including build scripts,
 configure files and makefiles) should cite the GPL, like this:
-
-   <blockquote>
-This file is part of GNU <var>package</var>.
-
-   <p>GNU <var>package</var> is free software: you can redistribute it and/or
+</p>
+<blockquote>
+<p>This file is part of GNU <var>package</var>.
+</p>
+<p>GNU <var>package</var> 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.
-
-   <p>GNU <var>package</var> is distributed in the hope that it will be useful,
+</p>
+<p>GNU <var>package</var> is distributed in the hope that it will be useful,
 but WITHOUT ANY WARRANTY; without even the implied warranty of
 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
 GNU General Public License for more details.
-
-   <p>You should have received a copy of the GNU General Public License
+</p>
+<p>You should have received a copy of the GNU General Public License
 along with this program.  If not, see <a 
href="http://www.gnu.org/licenses/";>http://www.gnu.org/licenses/</a>. 
-</blockquote>
+</p></blockquote>
 
-   <p>But in a small program which is just a few files, you can use
+<p>But in a small program which is just a few files, you can use
 this instead:
-
-   <blockquote>
-This program is free software: you can redistribute it and/or modify
+</p>
+<blockquote>
+<p>This program is free software: you can redistribute it and/or modify
 it under the terms of the GNU General Public License as published by
 the Free Software Foundation; either version 3 of the License, or
 (at your option) any later version.
-
-   <p>This program is distributed in the hope that it will be useful,
+</p>
+<p>This program is distributed in the hope that it will be useful,
 but WITHOUT ANY WARRANTY; without even the implied warranty of
 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
 GNU General Public License for more details.
-
-   <p>You should have received a copy of the GNU General Public License
+</p>
+<p>You should have received a copy of the GNU General Public License
 along with this program.  If not, see <a 
href="http://www.gnu.org/licenses/";>http://www.gnu.org/licenses/</a>. 
-</blockquote>
+</p></blockquote>
 
-   <p>In either case, for those few packages which use the Lesser GPL
+<p>In either case, for those few packages which use the Lesser GPL
 (see <a 
href="Licensing-of-GNU-Packages.html#Licensing-of-GNU-Packages">Licensing of 
GNU Packages</a>), insert the word &ldquo;Lesser&rdquo; before
 &ldquo;General&rdquo; in <em>all three</em> places. 
 <a 
href="http://www.gnu.org/licenses/gpl-howto.html";>http://www.gnu.org/licenses/gpl-howto.html</a>
 discusses application
 the GPL in more detail.
+</p>
+
+<hr>
+<div class="header">
+<p>
+Next: <a 
href="License-Notices-for-Documentation.html#License-Notices-for-Documentation" 
accesskey="n" rel="next">License Notices for Documentation</a>, Previous: <a 
href="Canonical-License-Sources.html#Canonical-License-Sources" accesskey="p" 
rel="previous">Canonical License Sources</a>, Up: <a 
href="License-Notices.html#License-Notices" accesskey="u" rel="up">License 
Notices</a> &nbsp; [<a href="index.html#SEC_Contents" title="Table of contents" 
rel="contents">Contents</a>][<a href="Index.html#Index" title="Index" 
rel="index">Index</a>]</p>
+</div>
+<p>
 
-   </body></html>
 
+</p>
+</body>
+</html>

Index: html_node/License-Notices-for-Documentation.html
===================================================================
RCS file: 
/web/www/www/prep/maintain/html_node/License-Notices-for-Documentation.html,v
retrieving revision 1.50
retrieving revision 1.51
diff -u -b -r1.50 -r1.51
--- html_node/License-Notices-for-Documentation.html    7 Sep 2011 01:31:18 
-0000       1.50
+++ html_node/License-Notices-for-Documentation.html    7 Sep 2011 15:00:37 
-0000       1.51
@@ -1,97 +1,129 @@
-<html lang="en">
-<head>
-<title>License Notices for Documentation - Information for Maintainers of GNU 
Software</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="Information for Maintainers of GNU Software">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="start" href="index.html#Top">
-<link rel="up" href="License-Notices.html#License-Notices" title="License 
Notices">
-<link rel="prev" href="License-Notices-for-Code.html#License-Notices-for-Code" 
title="License Notices for Code">
-<link rel="next" 
href="License-Notices-for-Other-Files.html#License-Notices-for-Other-Files" 
title="License Notices for Other Files">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home" 
title="Texinfo Homepage">
-<!--
-Information for maintainers of GNU software, last updated September 5, 2011.
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" 
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
+<!-- Information for maintainers of GNU software, last updated September 5, 
2011.
 
 Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
 2010, 2011 Free Software Foundation, Inc.
 
-     Permission is granted to copy, distribute and/or modify this
-     document under the terms of the GNU Free Documentation License,
-     Version 1.3 or any later version published by the Free Software
-     Foundation; with no Invariant Sections, with no Front-Cover Texts,
-     and with no Back-Cover Texts.  A copy of the license is included
-     in the section entitled ``GNU Free Documentation License''.
-   -->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
-  pre.display { font-family:inherit }
-  pre.format  { font-family:inherit }
-  pre.smalldisplay { font-family:inherit; font-size:smaller }
-  pre.smallformat  { font-family:inherit; font-size:smaller }
-  pre.smallexample { font-size:smaller }
-  pre.smalllisp    { font-size:smaller }
-  span.sc    { font-variant:small-caps }
-  span.roman { font-family:serif; font-weight:normal; } 
-  span.sansserif { font-family:sans-serif; font-weight:normal; } 
---></style>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
+Texts.  A copy of the license is included in the section entitled
+"GNU Free Documentation License". -->
+<!-- Created by texi2html, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>Information for Maintainers of GNU Software: License Notices for 
Documentation</title>
+
+<meta name="description" content="Information for Maintainers of GNU Software: 
License Notices for Documentation">
+<meta name="keywords" content="Information for Maintainers of GNU Software: 
License Notices for Documentation">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="texi2html">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="License-Notices.html#License-Notices" rel="up" title="License 
Notices">
+<link 
href="License-Notices-for-Other-Files.html#License-Notices-for-Other-Files" 
rel="next" title="License Notices for Other Files">
+<link href="License-Notices-for-Code.html#License-Notices-for-Code" 
rel="previous" title="License Notices for Code">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smalllisp {margin-lef