[Top][All Lists]

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

Re: [Groff] [PATCH] groff_tmac(5): Discuss stripping macros.

From: Ralph Corderoy
Subject: Re: [Groff] [PATCH] groff_tmac(5): Discuss stripping macros.
Date: Wed, 08 Nov 2017 11:52:37 +0000

Hi Branden,

Generally, try and use few words whilst preserving meaning and avoiding
ambiguity.  Folks have to wade through this when they're looking for an
answer to their question.  :-)

> +In the
> +.I groff
> +source distribution, some of the macro packages (corresponding to
> +.BR groff_hdtbl (@MAN7EXT@),
> +.BR groff_mdoc (@MAN7EXT@),
> +.BR groff_me (@MAN7EXT@),
> +and
> +.BR groff_mom (@MAN7EXT@)
> +as of this writing)

"currently foo, bar, and xyzzy,".  Or don't add the dependency that
needs maintaining?

> +are maintained in \[lq]unstripped\[rq] forms that are then reduced for
> +installation.

s/reduced/shrunk/?  Since that's the aim, and reduce has many computer

> +The stripping process primarily eliminates spaces between dots and
> +request or macro names (used for indentation and readability of the
> +macro sources) and most comments.

s/process //?
(So it doesn't handle spaces after «'» too.)

> +If you strip your macros, we strongly recommend that you follow GNU
> +.IR roff 's
> +example

When did `GNU roff' get invented?
I see groff(7) starts with

    The name groff stands for GNU roff

but I've always understood it was a contraction of `GNU troff', and roff
was in no way a direct influence on its name or behaviour;  troff and
nroff were copied.

Cheers, Ralph.

reply via email to

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