> Von: "Bernd Warken"
>
> 5) Macro:
> .\" .UNDERLINE before underlined after
> .de UNDERLINE
> . ie n \\$1\fI\\$2\fP\\$3
> . el \\$1\Z'\\$2'\v'.25m'\D'l \w'\\$2'u 0'\v'-.25m'\\$3
> ..
I now know, where I got the `troff' part `.el' from.
This macro definition is part of the `ms' macro package,
> "IS" == Ingo Schwarze writes:
IS> Building groff-1.22.2 from the release tarball on OpenBSD,
IS> i do have the two lines
IS> Making gropdf.n from gropdf.man
IS> Making pdfmom.n from pdfmom.man
In that case my conclusion was wrong.
The problem then must be gentoo's patch to enable par
Hi James,
James Cloos wrote on Thu, Jul 10, 2014 at 03:06:41PM -0400:
> I was talking about the build log. Not having those Making lines
> means that the build doesn't create the man files which make install
> would install.
Building groff-1.22.2 from the release tarball on OpenBSD,
i do have t
> > I would have no problem with a special groff request
> > with a new name. But one can't change .ul.
>
> I'm not sure Bernd was suggesting .ul change in troff to
> underline. Even if he was, it wouldn't be accepted so
> don't fret. :-)
Actually, why not? I'd like to argue that request nam
Hi Peter,
> Have a look at om.tmac, the macro definition '.de ul*ps'.
http://git.savannah.gnu.org/cgit/groff.git/tree/contrib/mom/om.tmac#n175
OK, so it takes the normal grops definitions, e.g.
/Q{moveto show}bind def
and replaces them with its own,
/Q { moveto X show Y } def
where X
> "DK" == Dave Kemper writes:
DK> I'm not certain what file you mean "does have those lines." Before that
DK> paragraph, you were speaking of a build log,
I was talking about the build log. Not having those Making lines means
that the build doesn't create the man files which make install w
There is another possibility for underlining by using overstriking
with \z and \(ul
# overstrike.groff
This underlines the 3 character part "tar" of the word "start":
.br
.\" ft CR
before s\
\z\[ul]t\
\z\[ul]a\
\z\[ul]r\
t after
#
This works correctly with troffs, e.g.
$ groff -Tps ov
