Hi Ulrich,
> The way I handle preprocessors and other options, is, to put them into
> a (pseudo-) comment in the first line of a document, like e.g.:
>
> .\" tbl eqn lnd
I do something similar but put shell commands as a comment, e.g.
.\" set -eEu -o pipefail
.\" f=foo
.\" o='-p -t'
.\" groff $o $f.tr | ps2pdf - $f.pdf
.\" groff $o $f.tr | ps2pdf - $f-debug.pdf
.\" exit 0
foo.tr is then run with something like
sed s/...// | bash
I used to maintain a makefile and store what preprocessors were needed
for each file there, but I prefer this; it keeps them with the source.
And being shell, it's highly flexible.
Cheers, Ralph.
