Re: AM_LIBTOOLFLAGS, maude_LIBTOOLFLAGS, and LIBTOOLFLAGS

[Alexandre Duret-Lutz]

>>> "Karl" == Karl Berry <address@hidden> writes:

 Karl> But grammatically, such text will appear after a period, which looks
 Karl> rather odd, not to say wrong.  For example, the one you found:

Thanks for the clarification.  I found a few other instances in
the automake manual, so I installed the following patch on HEAD
and branch-1-9.

2004-12-18  Alexandre Duret-Lutz  <address@hidden>

        * doc/automake.texi: Correct several misuses of @xref and @pxref

Index: doc/automake.texi
===================================================================
RCS file: /cvs/automake/automake/doc/automake.texi,v
retrieving revision 1.44.2.27
diff -u -r1.44.2.27 automake.texi
--- doc/automake.texi   17 Dec 2004 23:24:10 -0000      1.44.2.27
+++ doc/automake.texi   17 Dec 2004 23:40:10 -0000
@@ -1503,7 +1503,7 @@
 and uses @code{m4_include} instead of copying it into
 @file{aclocal.m4}.  This makes the package smaller, eases dependency
 tracking, and cause the file to be distributed automatically.
-(@pxref{Local Macros} for an example.)  Any macro which is found in a
+(See @ref{Local Macros} for an example.)  Any macro which is found in a
 system-wide directory, or via an absolute search path will be copied.
 So use @code{-I `pwd`/reldir} instead of @code{-I reldir} whenever
 some relative directory need to be considered outside the package.
@@ -3022,7 +3022,7 @@
 be determined until @file{./configure} is run: not all platforms
 support all kinds of libraries, and users can explicitly select which
 libraries should be built.  (However the package's maintainers can
-tune the default, @xref{AC_PROG_LIBTOOL, , The @code{AC_PROG_LIBTOOL}
+tune the default, @ref{AC_PROG_LIBTOOL, , The @code{AC_PROG_LIBTOOL}
 macro, libtool, The Libtool Manual}.)
 
 @cindex suffix @file{.lo}, defined
@@ -3317,7 +3317,7 @@
 
 The @address@hidden variable is the place to list
 additional libtool flags, such as @samp{-version-info},
address@hidden, and a lot more.  See @xref{Link mode, , Using libltdl,
address@hidden, and a lot more.  @xref{Link mode, , Link mode,
 libtool, The Libtool Manual}.
 
 @node LTLIBOBJS, Libtool Issues, Libtool Flags, A Shared Library
@@ -3827,7 +3827,7 @@
 @code{LTLIBOBJS} is defined automatically by Autoconf and should not
 be defined by hand (as in the past), however at the time of writing
 @code{LTALLOCA} still needs to be defined from @code{ALLOCA} manually.
-See @ref{AC_LIBOBJ vs LIBOBJS, , @code{AC_LIBOBJ} vs. @code{LIBOBJS},
address@hidden vs LIBOBJS, , @code{AC_LIBOBJ} vs. @code{LIBOBJS},
 autoconf, The Autoconf Manual}.
 
 
@@ -4756,7 +4756,7 @@
 @samp{nodist_} prefix as in @code{nodist_include_HEADERS} or
 @code{nodist_prog_SOURCES}.  If these generated headers are needed
 during the build, you must also ensure they exist before they are
-used, see @xref{Sources}.
+used, see @ref{Sources}.
 
 
 @node Data
@@ -5718,7 +5718,7 @@
 @cindex @code{make clean} support
 
 The GNU Makefile Standards specify a number of different clean rules.
-See @xref{Standard Targets, , Standard Targets for Users, standards,
address@hidden Targets, , Standard Targets for Users, standards,
 The GNU Coding Standards}.
 
 Generally the files that can be cleaned are determined automatically by
@@ -6127,7 +6127,7 @@
 this should be done elsewhere in the real test suite code.
 Especially, @file{site.exp} should not be distributed.
 
-For more information regarding DejaGnu test suites, see @xref{Top, , ,
+For more information regarding DejaGnu test suites, see @ref{Top, , ,
 dejagnu, The DejaGnu Manual}.
 
 In either case, the testing is done via @samp{make check}.
@@ -6329,7 +6329,7 @@
 @opindex no-dependencies
 This is similar to using @samp{--include-deps} on the command line, but
 is useful for those situations where you don't have the necessary bits
-to make automatic dependency tracking work @xref{Dependencies}.  In this
+to make automatic dependency tracking work @ref{Dependencies}.  In this
 case the effect is to effectively disable automatic dependency tracking.
 
 @item @code{no-dist}
@@ -8066,7 +8066,7 @@
 There are other variables in Automake that follow similar principles
 to allow user options.  For instance Texinfo rules (@pxref{Texinfo})
 uses @code{MAKEINFOFLAGS} and @code{AM_MAKEINFOFLAGS}.  Similarly,
-DejaGnu tests @pxref{Tests} use @code{RUNTESTDEFAULTFLAGS} and
+DejaGnu tests (@pxref{Tests}) use @code{RUNTESTDEFAULTFLAGS} and
 @code{AM_RUNTESTDEFAULTFLAGS}.  The tags and ctags rules
 (@pxref{Tags}) use @code{ETAGSFLAGS}, @code{AM_ETAGSFLAGS},
 @code{CTAGSFLAGS}, and @code{AM_CTAGSFLAGS}.  Java rules
@@ -8081,7 +8081,7 @@
 However you should not think that all variables ending with
 @code{FLAGS} follow this convention.  For instance
 @code{DISTCHECK_CONFIGURE_FLAGS} (@pxref{Dist}),
address@hidden (@pxref{Rebuilding} and @ref{Local Macros}),
address@hidden (see @ref{Rebuilding} and @ref{Local Macros}),
 are two variables that are only useful to the maintainer and have no
 user counterpart.
 
@@ -8093,7 +8093,7 @@
 variable.  For instance the @code{mumble_LDADD} per-target variable
 overrides the global @code{LDADD} variable (which is not a user
 variable), and @code{mumble_LIBADD} exists only as a per-target
-variable.  (@pxref{Program and Library Variables}.)
+variable.  @xref{Program and Library Variables}.
 
 
 @node renamed objects
-- 
Alexandre Duret-Lutz