Follow-up Comment #15, bug #61710 (project groff):
This isn't directly responsive to comment #13, but as I just stumbled across
it, I thought it wise to share it.
It turns out that to understand the wherefores of these mysterious `$v` and
`$V` registers, all we had to do was...read the NEWS.
VERSION 1.06
============
[...]
Macros
------
In previous releases the groff -me macros treated the $r and $R number
registers in a way that was incompatible with the BSD -me macros. The
reason for this was that the approach used by the BSD -me macros does
not work with low resolution devices such as -TX75 and -TX100. However,
this caused problems with existing -me documents. In this release, the
vertical spacing is controlled by the $v and $V registers which have the
same meaning as $r and $R in earlier groff releases. In addition, if
the $r or $R register is set to a value that would be correct for
the BSD -me macros and a low resolution device is not being used, then
an appropriate value for the $v or $V register is derived from the $r or
$R register.
The groff -me macros work with -C and (I think) with Unix troff.
For backward compatibility with BSD -me, the \*{ and \*} strings are
also available as \*[ and \*]. Of course, \*[ is only usable with -C.
The \*T string has been deleted. Use \*(Tm instead.
Now, why this is NEWS-worthy but not of being documented in meintro, meref, or
the groff_me(7) man page remains a mystery...
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?61710>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
