Re: [Groff] Re: Problem with grohtml on Win32

[Werner LEMBERG]

> Perhaps the most practical solution would be to specify a *list* of
 > known names for the ghostscript executable, or any other suitable
> image generator, in the DESC file, and have pre-grohtml search for
> each in turn, *at runtime*, until it finds one it can use, giving up
> on image generation only if none can be found.  This list should
> include all of the well known names for the ghostscript executable,
> augmented by any alternative name, or possibly a list of names,
> specified with a '--with-gs=NAME' or '--with-gs=LIST' option to
> 'configure'; ideally any such explicit list should be searched
> first.
>
> In order to give pre-grohtml the best possible opportunity to find
> an image generator, I think the default list of names to be searched
> should *not* include any explicit path information; this will allow
> pre-grohtml to find an image generator program, if one is present at
> *any* location in the runtime PATH.  Of course, an image generator
> name *explicitly* specified with '--with-gs=...' *could* include
> path information; we must assume that any user specifying this knows
> what he or she is doing, and we should not override that choice :-)

Excellent.  Let me recapitulate how a modified grohtml should look
like:

  . By default, groff provides a list of gs binary names for grohtml,
    to be put into the DESC file.

  . The `--with-gs' configuration options replace this list.

  . At run-time, binaries named in the DESC files without a path are
    searched by grohtml in the PATH environment variable; binaries
    with an absolute path are accessed as given.

Correct?  Can you implement this?


    Werner