Re: [Groff] Several file arguments to groff

[Bernd Warken]

On Sun, Oct 20, 2002 at 11:48:07AM +0200, Werner LEMBERG wrote:
> 
> > If the file arguments use different macro packages, groff usually
> > generates many errors.  For example, try
> > 
> >   groff -man man/groff.man -me doc/meintro.me -ms doc/pic.ms -Tlatin1
> > 
> > in groff's top source directory.  This produces many wrong macro
> > usages and error reports, being just a bit different if the sequence
> > of the arguments is changed.
> 
> Indeed, this will fail.  But the main reason is not groff but the
> function used to parse the command line arguments: GNU's getopt.  It
> sorts options and non-options (the latter coming first).  For the
> above command line, groff sees this:
> 
>   groff -man -me -ms -Tlatin1 man/groff.man doc/meintro.me doc/pic.ms
>
If getopt() is replaced by a better option hadler, would that be
enough for groff to generate a suitable output for all such kinds of
files with different macro packages?

> > Fixing is easy for `grog',
> 
> How shall grog be fixed?
> 
Writing a shell program that runs the awk grog for every file argument.

Bernd Warken