[groff] 41/47: doc/pic.ms: Fix markup nits.

[G. Branden Robinson]

gbranden pushed a commit to branch master
in repository groff.

commit c6e2681a3139961f6996edf796de8856cb877c40
Author: G. Branden Robinson <g.branden.robinson@gmail.com>
AuthorDate: Tue Jan 11 20:12:29 2022 +1100

    doc/pic.ms: Fix markup nits.
    
    * Stop using \SP in favor of \~; the latter groff extension has been
      supported by Heirloom Doctools troff for over 15 years and has
      multiple advantages.  I leared a new one today: it's much safer to use
      when reflowing in a text editor.  Having \SP turned into \RET could be
      pretty disruptive to text.
    * Stop padding out tags in indented paragraphs (with \SP, no less) to
      try to get the bodies to align; instead use the `IP` macro's second
      argument--that's what it's there for.
---
 doc/pic.ms | 30 +++++++++++++++---------------
 1 file changed, 15 insertions(+), 15 deletions(-)

diff --git a/doc/pic.ms b/doc/pic.ms
index a6f22a45..51c710f6 100644
--- a/doc/pic.ms
+++ b/doc/pic.ms
@@ -637,13 +637,13 @@ Text Special Effects
 .PP
 All \fBpic\fP implementations support the following font-styling
 escapes within text objects:
-.IP "\efR, \ef1"
+.IP "\efR, \ef1" \w'\efR,\~\ef3'u+2n
 Set Roman style (the default)
 .IP "\efI, \ef2"
 Set Italic style
 .IP "\efB, \ef3"
 Set Bold style
-.IP "\efP\ \ \ \ \ \ "
+.IP \efP
 Revert to previous style; only works one level deep, does not stack.
 .PP
 In the \fBpic\fP implementations that are preprocessors for a
@@ -1867,9 +1867,9 @@ and variable assignment to write true functions.
 .PP
 One detail the example above does not illustrate is the fact that
 macro argument parsing is not token-oriented.
-If you call \fBjumper(\ 1\ )\fP, the value of $1 is \fB"\ 1\ "\fP.
-You could even call \fBjumper(big\ string)\fP to give $1 the value
-\fB"big\ string"\fP.
+If you call \fBjumper(\~1\~)\fP, the value of $1 is \fB"\~1\~"\fP.
+You could even call \fBjumper(big\~string)\fP to give $1 the value
+\fB"big\~string"\fP.
 .PP
 If you want to pass in a coordinate pair, you can avoid getting
 tripped up by the comma by wrapping the pair in parentheses.
@@ -2756,7 +2756,7 @@ values of the style variables \fBmaxpswid\fP and 
\fBmaxpsheight\fP
 .PP
 If the ending `.PE' is replaced by `.PF', the page vertical position is
 restored to its value at the time `.PS' was encountered.
-Another alternate form of invocation is `.PS\ <\s[-1]FILENAME\s[0]',
+Another alternate form of invocation is `.PS\~<\s[-1]FILENAME\s[0]',
 which replaces the `.PS' line with a file to be interpreted by \fBpic\fR
 (but this feature is deprecated).
 .PP
@@ -2802,8 +2802,8 @@ In the following, either `|' or a new line starts an 
alternative.
 .R
 .DE
 .PP
-The current position and direction are saved on entry to a `{\ .\|.\|.\ }'
-construction and restored on exit from it.
+The current position and direction are saved on entry to a
+ `{\~.\|.\|.\~}' construction and restored on exit from it.
 .PP
 Note that in `if' constructions, newlines can only occur in
 \s[-1]BALANCED-BODY\s[0].
@@ -2882,13 +2882,13 @@ empty string is considered as `false' for `&&' and 
`|\||'.
 .R
 .DE
 .PP
-Drawn objects within `[\ .\|.\|.\ ]' are treated as a single composite
+Drawn objects within `[\~.\|.\|.\~]' are treated as a single composite
 object with a rectangular shape (that of the bounding box of all the
 elements).
 Variable and label assignments within a block are local to the block.
 Current direction of motion is restored to the value at start of block
 upon exit.
-Position is \fInot\fR restored (unlike `{\ }');
+Position is \fInot\fR restored (unlike `{\~}');
 instead, the current position becomes the exit position for the current
 direction on the block's bounding box.
 .DS
@@ -2944,7 +2944,7 @@ a specified location.
 The `by' primitive is not documented in the tutorial portion of
 the Kernighan paper, and should probably be considered unreliable.
 .PP
-The primitive `arrow' is a synonym for `line\ ->'.
+The primitive `arrow' is a synonym for `line\~->'.
 .PP
 Text is normally an attribute of some object, in which case successive
 strings are vertically stacked and centered on the object's center by
@@ -2959,13 +2959,13 @@ before the end of the current item.
 Text may also contain \e-escapes denoting special characters.
 The base font and specific set of escapes supported is implementation
 dependent, but supported escapes always include the following:
-.IP "\efR, \ef1"
+.IP "\efR, \ef1" \w'\efR,\~\ef3'u+2n
 Set Roman style (the default)
 .IP "\efI, \ef2"
 Set Italic style
 .IP "\efB, \ef3"
 Set Bold style
-.IP "\efP\ \ \ \ \ \ "
+.IP \efP
 Revert to previous style; only works one level deep, does not stack.
 .PP
 Color names are dependent on the \gBpic\fR implementation, but in
@@ -3095,7 +3095,7 @@ A north
 .R
 .DE
 both cause a syntax error.
-(DWB \fBpic\fP also allows the weird form `A\ north\ of'.)
+(DWB \fBpic\fP also allows the weird form `A\~north\~of'.)
 .PP
 Here the special rules for the `with' keyword using a path:
 .DS
@@ -3149,7 +3149,7 @@ _
 .TE
 Any of these can be set by assignment, or reset using the \fBreset\fP
 statement.
-Style variables assigned within `[\ ]' blocks are restored to their
+Style variables assigned within `[\~]' blocks are restored to their
 beginning-of-block value on exit; top-level assignments persist across
 pictures.
 Dimensions are divided by \fBscale\fR on output.