summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorKarl Berry <karl@freefriends.org>2006-04-09 22:54:34 +0000
committerKarl Berry <karl@freefriends.org>2006-04-09 22:54:34 +0000
commit8b9a568d723459746c648f1a4fba4b0f1291d4a0 (patch)
tree04d99ddb8d292fc674b28de29e4bfdb436b1d43d /doc
parent7cb1cf6cada814b373afefa049fd9d2f78a7e0e4 (diff)
downloadgnulib-8b9a568d723459746c648f1a4fba4b0f1291d4a0.tar.gz
autoupdate
Diffstat (limited to 'doc')
-rw-r--r--doc/standards.texi52
1 files changed, 26 insertions, 26 deletions
diff --git a/doc/standards.texi b/doc/standards.texi
index ff8a73bb66..1bea31c1f0 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 February 12, 2006
+@set lastupdate April 9, 2006
@c %**end of header
@dircategory GNU organization
@@ -72,7 +72,7 @@ Free Documentation License''.
* Managing Releases:: The Release Process
* References:: References to Non-Free Software or Documentation
* Copying This Manual:: How to Make Copies of This Manual
-* Index::
+* Index::
@end menu
@@ -117,8 +117,8 @@ to document them as much as possible. That way, your program will be
more maintainable by others.
The GNU Hello program serves as an example of how to follow the GNU
-coding standards for a trivial program which prints @samp{Hello,
-world!}. @uref{http://www.gnu.org/software/hello/hello.html}.
+coding standards for a trivial program.
+@uref{http://www.gnu.org/software/hello/hello.html}.
@node Legal Issues
@chapter Keeping Free Software Free
@@ -224,7 +224,7 @@ packages or documentation.
Trademark acknowledgements are the statements that such-and-such is a
trademark of so-and-so. The GNU Project has no objection to the basic
-idea of trademarks, but these acknowledgements feel like kowtowing,
+idea of trademarks, but these acknowledgements feel like kowtowing,
and there is no legal requirement for them, so we don't use them.
What is legally required, as regards other people's trademarks, is to
@@ -311,12 +311,12 @@ is written in that language, too. The Emacs editor pioneered this
technique.
@cindex GUILE
-The standard extensibility interpreter for GNU software is GUILE, which
-implements the language Scheme (an especially clean and simple dialect
-of Lisp). @uref{http://www.gnu.org/software/guile/}. We don't reject
-programs written in other ``scripting languages'' such as Perl and
-Python, but using GUILE is very important for the overall consistency of
-the GNU system.
+The standard extensibility interpreter for GNU software is GUILE
+(@uref{http://www.gnu.org/software/guile/}), which implements the
+language Scheme (an especially clean and simple dialect of Lisp). We
+don't reject programs written in other ``scripting languages'' such as
+Perl and Python, but using GUILE is very important for the overall
+consistency of the GNU system.
@node Compatibility
@section Compatibility with Other Implementations
@@ -732,7 +732,7 @@ If you want to mention the column number, use one of these formats:
@example
@var{source-file-name}:@var{lineno}:@var{column}: @var{message}
-@var{source-file-name}:@var{lineno}.@var{column}: @var{message}
+@var{source-file-name}:@var{lineno}.@var{column}: @var{message}
@end example
@@ -987,12 +987,12 @@ copyright notices (@pxref{Internationalization}). If the translation's
character set supports it, the @samp{(C)} should be replaced with the
copyright symbol, as follows:
-@ifinfo
-(the official copyright symbol, which is the letter C in a circle);
-@end ifinfo
-@ifnotinfo
+@ifinfo
+(the official copyright symbol, which is the letter C in a circle);
+@end ifinfo
+@ifnotinfo
@copyright{}
-@end ifnotinfo
+@end ifnotinfo
Write the word ``Copyright'' exactly like that, in English. Do not
translate it into another language. International treaties recognize
@@ -2220,7 +2220,7 @@ concat (char *s1, char *s2)
@end example
@noindent
-or, if you want to use Standard C syntax, format the definition like
+or, if you want to use traditional C syntax, format the definition like
this:
@example
@@ -3075,7 +3075,7 @@ accent. Moreover, Latin1 is still not universally usable.
Unicode contains the unambiguous quote characters required, and its
common encoding UTF-8 is upward compatible with Latin1. However,
-Unicode and UTF-8 are not universally well-supported, either.
+Unicode and UTF-8 are not universally well-supported, either.
This may change over the next few years, and then we will revisit
this.
@@ -3345,10 +3345,10 @@ inconsistencies between different parts of a program, by giving you a
history of how the conflicting concepts arose and who they came from.
@menu
-* Change Log Concepts::
-* Style of Change Logs::
-* Simple Changes::
-* Conditional Changes::
+* Change Log Concepts::
+* Style of Change Logs::
+* Simple Changes::
+* Conditional Changes::
* Indicating the Part Changed::
@end menu
@@ -3712,7 +3712,7 @@ The @code{configure} script needs to be able to decode all plausible
alternatives for how to describe a machine. Thus,
@samp{athlon-pc-gnu/linux} would be a valid alias. There is a shell
script called
-@uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/config/config/config.sub,
+@uref{http://savannah.gnu.org/@/cgi-bin/@/viewcvs/@/*checkout*/@/config/@/config/@/config.sub,
@file{config.sub}} that you can use as a subroutine to validate system
types and canonicalize aliases.
@@ -3723,7 +3723,7 @@ plain @var{buildtype} argument. For example, @samp{configure
i686-pc-linux-gnu}. When the build type is not specified by an option
or argument, the @code{configure} script should normally guess it using
the shell script
-@uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/config/config/config.guess,
+@uref{http://savannah.gnu.org/@/cgi-bin/@/viewcvs/@/*checkout*/@/config/@/config/@/config.guess,
@file{config.guess}}.
@cindex optional features, configure-time
@@ -3913,7 +3913,7 @@ The GNU definition of free software is found on the GNU web site at
of free documentation is found at
@url{http://www.gnu.org/philosophy/free-doc.html}. A list of
important licenses and whether they qualify as free is in
-@url{http://www.gnu.org/licenses/license-list.html}. The terms
+@url{http://www.gnu.org/@/licenses/@/license-list.html}. The terms
``free'' and ``non-free'', used in this document, refer to that
definition. If it is not clear whether a license qualifies as free
under this definition, please ask the GNU Project by writing to