X-Git-Url: http://git.chise.org/gitweb/?a=blobdiff_plain;f=info%2Fstandards.info-3;h=5a6af11c898db5d05ada24e52b598fe7db676f58;hb=15416d0609770cf0a2897cb33973eee789b89eb0;hp=c21b67c0f9e9088aa684168c24f8aeed53dc83a0;hpb=82da33b61c3e2dd2937db17b75b2838188793053;p=chise%2Fxemacs-chise.git-

diff --git a/info/standards.info-3 b/info/standards.info-3
index c21b67c..5a6af11 100644
--- a/info/standards.info-3
+++ b/info/standards.info-3
@@ -1,5 +1,5 @@
-This is Info file ../info/standards.info, produced by Makeinfo version
-1.68 from the input file standards.texi.
+This is ../info/standards.info, produced by makeinfo version 4.0 from
+standards.texi.
 
 START-INFO-DIR-ENTRY
 * Standards: (standards).        GNU coding standards.
@@ -105,7 +105,7 @@ compilation command that runs the preprocessor, and use `LDFLAGS' in
 any compilation command that does linking as well as in any direct use
 of `ld'.
 
-   If there are C compiler options that *must* be used for proper
+   If there are C compiler options that _must_ be used for proper
 compilation of certain files, do not include them in `CFLAGS'.  Users
 expect to be able to specify `CFLAGS' freely themselves.  Instead,
 arrange to pass the necessary options to the C compiler independently
@@ -118,7 +118,7 @@ by defining an implicit rule, like this:
              $(CC) -c $(CPPFLAGS) $(ALL_CFLAGS) $<
 
    Do include the `-g' option in `CFLAGS', because that is not
-*required* for proper compilation.  You can consider it a default that
+_required_ for proper compilation.  You can consider it a default that
 is only recommended.  If the package is set up so that it is compiled
 with GCC by default, then you might as well include `-O' in the default
 value of `CFLAGS' as well.
@@ -377,7 +377,7 @@ directories:
 `srcdir'
      The directory for the sources being compiled.  The value of this
      variable is normally inserted by the `configure' shell script.
-     (If you are using Autconf, use `srcdir = @srcdir@'.)
+     (If you are using Autoconf, use `srcdir = @srcdir@'.)
 
    For example:
 
@@ -450,7 +450,7 @@ Makefiles:
      that don't have the Unix man page documentation system installed.
 
      The way to install Info files is to copy them into `$(infodir)'
-     with `$(INSTALL_DATA)' (*note Command Variables::.), and then run
+     with `$(INSTALL_DATA)' (*note Command Variables::), and then run
      the `install-info' program if it is present.  `install-info' is a
      program that edits the Info `dir' file to add or update the menu
      entry for the given Info file; it is part of the Texinfo package.
@@ -685,7 +685,7 @@ variable, plus an optional comment at the end.  There are three
 variables you can use, one for each category; the variable name
 specifies the category.  Category lines are no-ops in ordinary execution
 because these three Make variables are normally undefined (and you
-*should not* define them in the makefile).
+_should not_ define them in the makefile).
 
    Here are the three possible category lines, each with a comment that
 explains what it means:
@@ -709,7 +709,7 @@ classified as normal.
 from the Info directory.
 
    If the `install' or `uninstall' target has any dependencies which
-act as subroutines of installation, then you should start *each*
+act as subroutines of installation, then you should start _each_
 dependency's commands with a category line, and start the main target's
 commands with a category line also.  This way, you can ensure that each
 command is placed in the right category regardless of which of the