Re: standards.texi that comes with GCC is out of date

["Martin v. Loewis" <martin at loewis dot home dot cs dot tu-berlin dot de>]

> Marek indicates that the copy of the standards document that comes with GCC
> is way out of date (by over 2 years).  Could you please update it?

I've updated both standards.texi and make-stds.texi in the gcc CVS tree.
When importing make-stds.texi, I noticed a few typos in the prep version:

--- /vol/marvin-vol2/loewis/make-stds.texi	Thu May 18 09:12:33 2000
+++ make-stds.texi	Thu May 18 09:15:11 2000
@@ -81,7 +81,7 @@
 
 @noindent
 will fail when the build directory is not the source directory, because
-@file{foo.man} and @file{sedscript} are in the the source directory.
+@file{foo.man} and @file{sedscript} are in the source directory.
 
 When using GNU @code{make}, relying on @samp{VPATH} to find the source
 file will work in the case where there is a single dependency file,
@@ -747,7 +747,7 @@
 named, use @code{ln} or @code{cp} to install the proper files in it, and
 then @code{tar} that subdirectory.
 
-Compress the tar file file with @code{gzip}.  For example, the actual
+Compress the tar file with @code{gzip}.  For example, the actual
 distribution file for GCC version 1.40 is called @file{gcc-1.40.tar.gz}.
 
 The @code{dist} target should explicitly depend on all non-source files

> Another option might be simply to refer people to the copy at
> http://www.gnu.org/prep/standards_toc.html.  That way, you wouldn't
> need to worry about updating it.

That would work on a Web page. It does not work terribly well in a
file of the gcc distribution... so I just continued with the existing
procedure.

What *would* work if standards.texi contained a reference to its
master location itself, so people could check whether a new version is
available, even if they only have a printed copy.

Regards,
Martin