On 2/23/24, Larry Kollar wrote:
> But in the case of groff, there’s at least twice as many years of inertia
> (compared to XML) to consider. It really does make sense that an -mm
> based book file should invoke the macro package(s) it needs, but so
> many of us are automatically going to put that
Hi John,
At 2024-02-28T09:56:04+1100, John Gardner wrote:
[I wrote]:
> > Why not refer to the preprocessors by their options? -t -p -e?
>
> Because those preprocessor options won't necessarily be available in
> every Troff implementation; e.g., Heirloom and Neatroff. Even worse,
> they could mea
Hi Branden,
Why not refer to the preprocessors by their options? -t -p -e?
Because those preprocessor options won't necessarily be available in every
Troff implementation; e.g., Heirloom and Neatroff. Even worse, they could
mean different things altogether, like -t and -p did in otroff.
FYI, t
Hi Dave, Larry, and John,
At 2024-02-23T09:07:42-0600, Dave Kemper wrote:
> On 2/22/24, G. Branden Robinson wrote:
> > I've come to think that a set of "best practice" for *roff document
> > composition is to:
> >
> > A. Load your desired full-service macro package (if any) on the command
> >
I tend to begin my documents with the following comment, designed to
illustrate for the author what macro packages are used by the document,
which preprocessors are needed, etc:
.\" uses: -mpdfmark -man -rLL=80 tbl pic eqn
I opt for a *descriptive* directive instead of a *prescriptive* one ("uses
> Dave Kemper wrote:
>
> On 2/22/24, G. Branden Robinson wrote:
>> I've come to think that a set of "best practice" for *roff document
>> composition is to:
>>
>> A. Load your desired full-service macro package (if any) on the command
>>line with `-m`.
>> B. Load any auxiliary macro pac
On 2/22/24, G. Branden Robinson wrote:
> I've come to think that a set of "best practice" for *roff document
> composition is to:
>
> A. Load your desired full-service macro package (if any) on the command
> line with `-m`.
> B. Load any auxiliary macro packages that your document _requires_
