summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorKarl Berry <karl@freefriends.org>2010-06-22 09:34:07 -0700
committerKarl Berry <karl@freefriends.org>2010-06-22 09:34:07 -0700
commitd0ed135f8b494a0adf869a311c7bdc1d9d03f050 (patch)
tree9e430459361cb180ea2ad95cab5104fb397415e5 /doc
parentfffd5faca72521880531fdebe05675828fad0628 (diff)
downloadgnulib-d0ed135f8b494a0adf869a311c7bdc1d9d03f050.tar.gz
autoupdates
Diffstat (limited to 'doc')
-rw-r--r--doc/fdl-1.3.texi20
-rw-r--r--doc/maintain.texi11
-rw-r--r--doc/standards.texi4
3 files changed, 19 insertions, 16 deletions
diff --git a/doc/fdl-1.3.texi b/doc/fdl-1.3.texi
index 8805f1a47d..fc19ddddfa 100644
--- a/doc/fdl-1.3.texi
+++ b/doc/fdl-1.3.texi
@@ -92,16 +92,16 @@ 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
-@sc{ascii} without markup, Texinfo input format, La@TeX{} input
-format, @acronym{SGML} or @acronym{XML} using a publicly available
-@acronym{DTD}, and standard-conforming simple @acronym{HTML},
-PostScript or @acronym{PDF} designed for human modification. Examples
-of transparent image formats include @acronym{PNG}, @acronym{XCF} and
-@acronym{JPG}. Opaque formats include proprietary formats that can be
-read and edited only by proprietary word processors, @acronym{SGML} or
-@acronym{XML} for which the @acronym{DTD} and/or processing tools are
-not generally available, and the machine-generated @acronym{HTML},
-PostScript or @acronym{PDF} produced by some word processors for
+ASCII without markup, Texinfo input format, La@TeX{} 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.
The ``Title Page'' means, for a printed book, the title page itself,
diff --git a/doc/maintain.texi b/doc/maintain.texi
index c040b8c937..5bf4a0040c 100644
--- a/doc/maintain.texi
+++ b/doc/maintain.texi
@@ -5,7 +5,7 @@
@c For double-sided printing, uncomment:
@c @setchapternewpage odd
@c This date is automagically updated when you save this file:
-@set lastupdate May 28, 2010
+@set lastupdate June 21, 2010
@c %**end of header
@dircategory GNU organization
@@ -160,7 +160,7 @@ ask for accounts for people who significantly help you in working on
the package.
@end macro
-@gdgnuorgtext
+@gdgnuorgtext{}
@cindex down, when GNU machines are
@cindex outage, of GNU machines
@@ -278,7 +278,7 @@ expected papers arrive.
@cindex @file{/gd/gnuorg} directory
@c This paragraph intentionally duplicates information given
@c near the beginning of the file--to make sure people don't miss it.
-@gdgnuorgtext
+@gdgnuorgtext{}
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
@@ -1884,7 +1884,10 @@ For new files:
cvs add -ko @var{file1} @var{file2} ...
@end example
-@xref{Keyword substitution,,,cvs,Version Management with CVS}.
+@c The CVS manual is now built with numeric references and no nonsplit
+@c form, so it's not worth trying to give a direct link.
+See the ``Keyword Substitution'' section in the CVS manual, available
+at @url{http://ximbiot.com/cvs/manual}.
In Texinfo source, the recommended way to literally specify a
``dollar'' keyword is:
diff --git a/doc/standards.texi b/doc/standards.texi
index 4b1c03dd27..73885d6670 100644
--- a/doc/standards.texi
+++ b/doc/standards.texi
@@ -3,7 +3,7 @@
@setfilename standards.info
@settitle GNU Coding Standards
@c This date is automagically updated when you save this file:
-@set lastupdate April 12, 2010
+@set lastupdate June 21, 2010
@c %**end of header
@dircategory GNU organization
@@ -4191,7 +4191,7 @@ documentation.
By contrast, it is ok to refer to journal articles and textbooks in
the comments of a program for explanation of how it functions, even
though they are non-free. This is because we don't include such
-things in the GNU system even they are free---they are outside the
+things in the GNU system even if they are free---they are outside the
scope of what a software distribution needs to include.
Referring to a web site that describes or recommends a non-free