groff-commit
[Top][All Lists]
Advanced

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

[groff] 12/17: groff_me(7): Fix style nits.


From: G. Branden Robinson
Subject: [groff] 12/17: groff_me(7): Fix style nits.
Date: Sun, 8 Aug 2021 05:58:36 -0400 (EDT)

gbranden pushed a commit to branch master
in repository groff.

commit 965da74619a1988b166176bd38e52f24a05ebbf9
Author: G. Branden Robinson <g.branden.robinson@gmail.com>
AuthorDate: Sun Aug 8 04:39:22 2021 +1000

    groff_me(7): Fix style nits.
    
    * Simplify font style alternation macro usage.  Thanks to commit
      e58e32ea, 18 May, we can be confident that we get italic corrections
      where needed.
    * Perform a Kemper notectomy.
    * Say "spaces or tabs" instead of "whitespace".
    * Break input lines after commas.
    * Add an empty request between sentences.
    * Describe the basic Latin apostrophe and (double) quotation mark as
      "neutral" instead of "ASCII".
    * Quote the name of the "-me Reference Manual" instead of italicizing
      it (it's 14 U.S. letter pages).
    * Use .P for paragraphing.
    * Use "and so on" instead of "etc." at the end of a sentence.
---
 tmac/groff_me.7.man | 40 ++++++++++++++++++++++------------------
 1 file changed, 22 insertions(+), 18 deletions(-)

diff --git a/tmac/groff_me.7.man b/tmac/groff_me.7.man
index 0a0b2ca..ecca2fb 100644
--- a/tmac/groff_me.7.man
+++ b/tmac/groff_me.7.man
@@ -142,48 +142,52 @@ string arguments with uppercase.
 An optional macro argument such as
 .I x
 appears in brackets,
-.BI [ x \/\c
-.BR ] .
+.BI [ x ].
 .
-Note that arguments to macros generally must be quoted if they contain
-whitespace.
+Arguments to macros generally must be quoted if they contain spaces or
+tabs.
+.
+An exception is the argument to header and footer macros,
+which require some explanation.
 .
-An exception is the argument to header and footer macros, which require
-some explanation.
 They take the form
 .RI \(lq c
 .I left c middle c right
 .IR c \(rq,
 with spaces added here for clarity.
+.
 The strings
 .IR left ,
 .IR middle ,
 and
 .I right
 correspond to their page placement and can contain unprotected
-whitespace, but must not contain the (non-space) character
+spaces and/or tabs,
+but must not contain the (non-space) character
 .IR c ,
 which delimits them.
-For brevity, the table presents header and footer arguments as
+.
+For brevity,
+the table presents header and footer arguments as
 .IR clcmcrc .
+.
 Popular choices for
 .I c
-are the ASCII apostrophe
+are the neutral apostrophe
 .RB \(lq \(aq \(rq
-and the ASCII double quote
+and the neutral double quote
 .RB \(lq \(dq \(rq.
 .
 .
-.PP
+.P
 This list is incomplete;
-some requests are too complex to summarize in a table, and some that
-are listed below accept additional arguments not shown.
-See the
-.I \-me Reference Manual
-for interesting details.
+some requests are too complex to summarize in a table,
+and some that are listed below accept additional arguments not shown.
 .
+See the \[lq]\-me Reference Manual\[rq] for further details.
 .
-.PP
+.
+.P
 .TS
 l l l lx.
 Request        Initial Causes  Explanation
@@ -489,7 +493,7 @@ macro packages limited themselves to a single-letter 
namespace
 .IR ms ,
 .IR mv ,
 .IR mn ,
-etc.).
+and so on).
 .
 .\" 'When I started writing the -me macros it began as something in my
 .\" private tree (I don't remember what I called it).  Then some other



reply via email to

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