autoconf-patches
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Fixing trivial grammaros (was: [SCM] GNU Autoconf source repository bran


From: Ralf Wildenhues
Subject: Fixing trivial grammaros (was: [SCM] GNU Autoconf source repository branch, master, updated. v2.63b-26-ge7c7a47)
Date: Tue, 21 Apr 2009 21:45:01 +0200
User-agent: Mutt/1.5.18 (2008-05-17)

Hi Eric,

* Eric Blake wrote on Sun, Apr 19, 2009 at 01:28:02AM CEST:
> According to Ralf Wildenhues on 4/18/2009 5:13 PM:
> > +It configures each @var{tag}; if none are specified, all the templates
> > +are instantiated.  A @var{tag} refers to a file or other tag associated
> > +with a configuration action, as specified by a @code{AC_CONFIG_FOOS}
> 
> Missed one in my review.  s/a @code{AC/an @code{AC/.  We probably have
> several other mismatched a/an scenarios throughout the manual.

I used these vim regexes to search for possible issues:

/\<a\>[ \n] *\(@[^{]*{\)\?[aeiouAEIOU]
/\<a\>[ \n] *\(@[^{]*{\)\?[A-Z][^a-z]
/\<an\>[ \n] *\(@[^{]*{\)\?[bcdfghjklmnpqrstvwxyzu][a-z]
/\<an\>[ \n] *\(@[^{]*{\)\?[BCDFGHJKLMNPQRSTVWXYZU][a-zA-Z]

This is not exhaustive, but good enough for today.  I'm pushing the
patch below.

For the same approach with automake.texi there is one instance where
I'm not sure about the "right" answer: "There is a FAQ entry ..."
Do people usually pronounce FAQ as eff-a-cue or as four letter word?

While at it, here's a couple more helpful vim regexes:

/\<\(the\|a\)\>[ \n]\<\(the\|a\)\>

:set ignorecase
/\(\<[a-z]\{1,\}\>\)[ \n]\<\1\>
finds duplicate words in general.  The nice things about the ignorecase
is that it also finds `Foo foo'.  One can skip known-goods like 'long
long' with
/\(\<[a-z]\{1,\}\>\)[ \n]\<\1\>\&\(long\)address@hidden

Cheers,
Ralf

    manual: fix trivial grammar errors.
    
    * doc/autoconf.texi (Fortran Compiler, Initialization Macros)
    (Limitations of Usual Tools, Pretty Help Strings)
    (config.status Invocation): Fix `a' vs. `an' errors.
    Report by Eric Blake.

diff --git a/doc/autoconf.texi b/doc/autoconf.texi
index e6fd489..2d6fd30 100644
--- a/doc/autoconf.texi
+++ b/doc/autoconf.texi
@@ -7553,7 +7553,7 @@ Fortran Compiler
 (until @code{AC_FC_SRCEXT} is called again).
 
 For example, you would use @code{AC_FC_SRCEXT(f90)} to employ the
address@hidden extension in future tests, and it would set a
address@hidden extension in future tests, and it would set an
 @code{FCFLAGS_f90} output variable with any extra flags that are needed
 to compile such files.
 
@@ -12811,7 +12811,7 @@ Initialization Macros
 parent script has @code{AS_MESSAGE_FD} redirected somewhere besides
 @samp{1}, then the child script already has code that copies stdout to
 that descriptor.  Currently, the suggested
-idiom for writing a M4sh shell script from within another script is:
+idiom for writing an M4sh shell script from within another script is:
 
 @example
 AS_INIT_GENERATED(address@hidden, [[# My child script.
@@ -17214,7 +17214,7 @@ Limitations of Usual Tools
 (not counting @samp{:} commands) and
 48 labels, which can not be circumvented by using more than one script
 file.  It can execute up to 19 reads with the @samp{r} command per cycle.
-Solaris @command{/usr/ucb/sed} rejects usages that exceed an limit of
+Solaris @command{/usr/ucb/sed} rejects usages that exceed a limit of
 about 6000 bytes for the internal representation of commands.
 
 Avoid redundant @samp{;}, as some @command{sed} implementations, such as
@@ -19642,7 +19642,7 @@ Pretty Help Strings
   @dvar{indent-column, 26}, @dvar{wrap-column, 79})
 @asindex{HELP_STRING}
 
-Expands into an help string that looks pretty when the user executes
+Expands into a help string that looks pretty when the user executes
 @samp{configure --help}.  It is typically used in @code{AC_ARG_WITH}
 (@pxref{External Software}) or @code{AC_ARG_ENABLE} (@pxref{Package
 Options}).  The following example makes this clearer.
@@ -20053,7 +20053,7 @@ config.status Invocation
 
 It configures each @var{tag}; if none are specified, all the templates
 are instantiated.  A @var{tag} refers to a file or other tag associated
-with a configuration action, as specified by a @code{AC_CONFIG_FOOS}
+with a configuration action, as specified by an @code{AC_CONFIG_FOOS}
 macro (@pxref{Configuration Actions}).  The files must be specified
 without their dependencies, as in
 




reply via email to

[Prev in Thread] Current Thread [Next in Thread]