🚀 go-pugleaf

henke@qt.ipa.fhg.de (Juergen Henke) writes:

>I agree with the use of groff, but did YOU try this ?
>I don't have ditroff (i even don't know were to get it ...:-) and
>have till now no big success in printing with groff - text prints fine, but
>(at the moment) it will print only 1 (one) zip in addition to the text, and
>no raster at all - it stays difficult.

running ezprint -t over an ez/fed/raster document produces troff input
using a "comment-quoted" form of postscript inclusion.

groff (well gtroff) is quite explicit in it's manual page about using
other methods of denoting included postscript. Thus, without work
this cannot work for free.

I, like others, cannot get ditroff onto the box easily. I got gtroff to
be called from ezprint fine, and even got gxditview to be the "popup"
for preview to work too... but only if I select the -TX75 font, since
gtroff uses non-standard (ditroff) backend commands for its ps dvi stuff.

I can see two simple ways to get postscript inclusions working.

(1)	change the way postscript is "tokenized" into ezprint -t output
	to be runtime configurable, and make a gtroff backend for this.

(2)	write a post-processor to re-wrap the troff into gtroff acceptable
	form. awk/perl/shell/whatever. the inclusion forms are pretty
	simple.

and a nicer but probably harder third form

(3)	do ALL inclusions by .so <tmpfile> and make the contents of <tmpfile>
	the result of a post-processor of its own. -This would permit
	arbitrary filtering of new ez bodytypes eg FIG/TeX.

and no... I'm not volunteering...

George
-- 
	G.Michaelson
Internet: G.Michaelson@cc.uq.oz.au                     Phone: +61 7 365 4079
  Postal: George Michaelson, the Prentice Centre,
          The University of Queensland, St Lucia, QLD Australia 4072.