bug-groff
[Top][All Lists]
Advanced

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

[bug #53547] [PATCH] tmac/groff_ms.7.man: Change bold '[' and ']' to rom


From: G. Branden Robinson
Subject: [bug #53547] [PATCH] tmac/groff_ms.7.man: Change bold '[' and ']' to roman and other tidying
Date: Sat, 21 Apr 2018 07:32:47 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0

Update of bug #53547 (project groff):

                  Status:                    None => In Progress            

    _______________________________________________________

Follow-up Comment #1:

I concur with the following classes of change:

1. Change - to \- if it means a minus sign.

2. Use a macro to change to the italic font, instead of \fI [1], if possible. 
The macros have the italic corrections, but "\c" removes them or add the
italic corrections.

3. Add a comma before "and", "or", or "nor" if a series contains three or more
words. [In other words, use the Oxford comma.]

4. Change '[' and ']' from bold to roman. [In command synopses, yes--only
literals should be rendered in bold.]

I do not concur with the following class of change:

5. Surround a block of comments with the macros ".ig" and "..".  [In my
opinion, the groff man pages should become exemplars of good man page style,
and while .ig and .. are not much harder to understand than "#if 0" and a
corresponding "#endif", that little bit makes a difference.  Comment leaders
are nearly universal in programming languages, and require only a finite
automaton to parse, instead of a pushdown automaton or worse.  I've taught my
Vim installation how to recognize *roff comments, so even reflowing text is no
longer a problem for me.]

Changes I'm still evaluating:

6. Arguments to the macro ".TP" (uses '.itc') [We went back and forth a whole
lot in this, didn't we?]

7. Use '\!' and '\c' to use two input lines as a one line of arguments. [I
need to brush up on \# vs. \! and the interaction each has with \c.]

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?53547>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/




reply via email to

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