I notice that one way to check if pdfroff is called is to look at the value of
\V[GROFF_TMPDIR], because the script sets it with an export. (pdfroff sets a
ton of other environment variables, but since they aren't set with an export,
they can't be checked from a troff document.)
The trouble with
On 26/10/15 13:12, Dorai Sitaram wrote:
> Incidentally, is there a way to tell from inside a document whether
> it is being processed by pdfroff or groff -Tps? In both cases, the
> string register .T is 'ps'.
Not really; pdfroff is just a shell script, which runs groff -Tps
multiple times, (to re
On Mon 26 Oct 2015 05:31:28 Keith Marshall wrote:
> > However, when I do this, groff gives the following warnings:
> >
> >
> > Unknown option: I
> > Unknown option: r
> > Unknown option: c
> >
> >
> >
> > Have I done something wrong, and if so, what?
>
> Reproduced here ... looks like another bu
[adding the list back in cc -- please keep it there]
On 26/10/15 05:44, Koz Ross wrote:
> Thanks Keith - good to know I'm already finding bugs. :P
>
> What does the '-P-pa4' do here? I assume it's to do with paper sizing?
Yes. It's to ensure that both troff and its grops postprocessor agree
on
On 26/10/15 04:28, Koz Ross wrote:
> I've just discovered groff, and am quite impressed! However, for some
> reason, I'm having an odd issue. I have a folder called 'src' where I
> plan to store chapters of my book, and I want to add it to the search
> path for stuff to include into the final docum
I've just discovered groff, and am quite impressed! However, for some reason,
I'm having an odd issue. I have a folder called 'src' where I plan to store
chapters of my book, and I want to add it to the search path for stuff to
include into the final document. I give groff the following command
