> > [...] you have to use the `.trf' request -- to define a macro `x' > > which contains the contents of file `f', say > > > > .ev 1 > > .di x > > . trf f > > .di > > .ev > >
> > This can be then expanded with \\*f. BTW, there is a mild
> > limitation that only valid groff characters are accepted in the
> > file passed as an argument to `.trf'.
>
> Thank you. I guess you mean \\*x or .x
Yes, of course.
> I've tried both and prepended the included file with \! and not.
> Neither of these combinations went into the PS file as PS
> instructions, just as text to be plotted or something to cause error
> exits. What did I do wrong?
Maybe the two attached files do what you want. Say
groff psline-test > psline-test.ps
to process them. The example artificially demonstrates how to control
the definition of a PS macro (taken from an external file) within
groff. If this doesn't answer you question please provide a small
example which I can work on.
> Question: I'll certainly have DCT encoded images in an ASCII85 coat
> to be read-in. These only contain printable characters but, alas,
> backslash is included. Would I need to duplicate them?
No.
> Other possible problems?
I'm not aware of any.
Werner
psline.ps
Description: PostScript document
.ev 1
.di x
. trf psline.ps
.di
.ev
.
.
.de END
..
.
.
.de line
. de line-aux END
ps: def \\*x
. END
.
. nop \Y[line-aux]
. nop \X'ps: exec psline'
..
.
.
xxx
.line 70
yyy
_______________________________________________ Groff mailing list [email protected] http://lists.gnu.org/mailman/listinfo/groff
