texinfo grammar

Eric Blake <[email protected]>
Newsgroups gmane.comp.gnu.m4.patches
Message-ID <[email protected]>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

According to 'info texinfo', sentences ending with capitals should use @.
so the spacing is correct.  Likewise, abbreviations that do not end a
sentence should use @:.  Meanwhile, I found a usage of "e.g." that should
have been "i.e." [1].

[1]
http://en.wikipedia.org/wiki/List_of_Latin_phrases_%28A%E2%80%93E%29#endnote_egie

Committing a similar patch to branch and head.

- --
Don't work too hard, make some time for fun as well!

Eric Blake             [email protected]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHs7fx84KuGfSFAYARAi7bAJ9pXUT4ERjQf4ANFRTDb36kY88BkACgrIGd
K/AQ0+2JUW8l5SxoOXpBdvc=
=kzaz
-----END PGP SIGNATURE-----

_______________________________________________
M4-patches mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/m4-patches
m4.patch317 (text/plain, 4.8 KB)
From e3dce8bbfdf9b917089814b081c80fb40958e1a9 Mon Sep 17 00:00:00 2001
From: Eric Blake <[email protected]>
Date: Wed, 13 Feb 2008 19:02:33 -0700
Subject: [PATCH] Fix texinfo grammar.

* doc/m4.texinfo (Eval, Incompatibilities): Use @. after capital.
(History): Use @: after abbreviations.
(M4exit): Use correct Latin abbreviation.
(Dumpdef, Debugmode, Frozen file format 2): Use correct spacing
between sentences.

Signed-off-by: Eric Blake <[email protected]>
---
 ChangeLog      |    9 +++++++++
 doc/m4.texinfo |   16 ++++++++--------
 2 files changed, 17 insertions(+), 8 deletions(-)

diff --git a/ChangeLog b/ChangeLog
index 2554a45..f50ac37 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,12 @@
+2008-02-13  Eric Blake  <[email protected]>
+
+	Fix texinfo grammar.
+	* doc/m4.texinfo (Eval, Incompatibilities): Use @. after capital.
+	(History): Use @: after abbreviations.
+	(M4exit): Use correct Latin abbreviation.
+	(Dumpdef, Debugmode, Frozen file format 2): Use correct spacing
+	between sentences.
+
 2008-02-11  Eric Blake  <[email protected]>
 
 	Allow builtin text macros to specify number of arguments.
diff --git a/doc/m4.texinfo b/doc/m4.texinfo
index 357358f..c313984 100644
--- a/doc/m4.texinfo
+++ b/doc/m4.texinfo
@@ -365,11 +365,11 @@ debugging their @code{m4} scripts than doing real work.  Beware that
 @cindex @acronym{GNU} M4, history of
 @code{GPM} was an important ancestor of @code{m4}.  See
 C. Stratchey: ``A General Purpose Macro generator'', Computer Journal
-8,3 (1965), pp. 225 ff.  @code{GPM} is also succinctly described into
+8,3 (1965), pp.@: 225 ff.  @code{GPM} is also succinctly described into
 David Gries classic ``Compiler Construction for Digital Computers''.
 
 The classic B. Kernighan and P.J. Plauger: ``Software Tools'',
-Addison-Wesley, Inc. (1976) describes and implements a Unix
+Addison-Wesley, Inc.@: (1976) describes and implements a Unix
 macro-processor language, which inspired Dennis Ritchie to write
 @code{m3}, a macro processor for the AP-3 minicomputer.
 
@@ -3466,7 +3466,7 @@ f(popdef(`f')dumpdef(`f'))
 @samp{s} flags affect the details of the display.  Remember, the
 @samp{q} flag is implied when the @option{--debug} option (@option{-d},
 @pxref{Debugging options, , Invoking m4}) is used in the command line
-without arguments. Also, @option{--debuglen} (@pxref{Debuglen}) can affect
+without arguments.  Also, @option{--debuglen} (@pxref{Debuglen}) can affect
 output, by truncating longer strings (but not builtin and module names).
 
 @comment options: -ds -l3
@@ -3794,7 +3794,7 @@ the previous setting.
 @comment currently enabled?
 
 If no flags are specified with the @option{--debug} option, the default is
-@samp{aeq}. Many examples in this manual show their output using
+@samp{aeq}.  Many examples in this manual show their output using
 default flags.
 
 @cindex @acronym{GNU} extensions
@@ -6616,7 +6616,7 @@ eval(`2 && 1 % 0')
 
 @cindex @acronym{GNU} extensions
 As a @acronym{GNU} extension, @code{eval} supports several operators
-that do not appear in C.  A right-associative exponentiation operator
+that do not appear in C@.  A right-associative exponentiation operator
 @samp{**} computes the value of the left argument raised to the right,
 modulo the numeric precision width.  If evaluated, the exponent must be
 non-negative, and at least one of the arguments must be non-zero, or a
@@ -7555,7 +7555,7 @@ fatal_error(`this is a BAD one, buster')
 
 After this macro call, @code{m4} will exit with exit status 1.  This macro
 is only intended for error exits, since the normal exit procedures are
-not followed, e.g., diverted text is not undiverted, and saved text
+not followed, i.e., diverted text is not undiverted, and saved text
 (@pxref{M4wrap}) is not reread.  (This macro could be made more robust
 to earlier versions of @code{m4}.  You should try to see if you can find
 weaknesses and correct them; or @pxref{Improved fatal_error, , Answers}).
@@ -7837,7 +7837,7 @@ to the symbol table.
 
 @item F @var{length} @key{NL} @var{string} @key{NL}
 Defines, through @code{pushdef}, a definition for @var{string}
-expanding to the function whose builtin name is also @var{string}. The builtin
+expanding to the function whose builtin name is also @var{string}.  The builtin
 name is searched for among the intrinsic builtin functions only.
 
 @item F @var{length1} , @var{length2} @key{NL} @var{string1} @var{string2} @key{NL}
@@ -8066,7 +8066,7 @@ giving an error.
 
 @item
 @acronym{POSIX} requires @code{eval} (@pxref{Eval}) to treat all
-operators with the same precedence as C.  However, earlier versions of
+operators with the same precedence as C@.  However, earlier versions of
 @acronym{GNU} @code{m4} followed the traditional behavior of other
 @code{m4} implementations, where bitwise and logical negation (@samp{~}
 and @samp{!}) have lower precedence than equality operators; and where
-- 
1.5.4
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.