Re: [Groff] Re: grohtml utility programs in DESC?

[Werner LEMBERG]

> When gs is installed on a Win32 platform, (either the GNU or the
> AFPL version), all the components are installed into a GhostScript
> directory, with registry entries to locate them.  There is no
> guarantee that gswin32c.exe will be installed in a path where
> grohtml would know to look for it -- it would be necessary for the
> end user to add the GhostScript binary directory to his regular PATH
> definition.

I think this is the only thing we can expect, coming from a Unix
environment.

> The alternative, which I suggest in README.MinGW, is to simply copy
> the required gswin32c.exe to a directory which is already in the
> PATH, (e.g. /usr/local/bin under MSYS); in this case, it will work
> equally well if the copy of gswin32c.exe is renamed as gs.exe, or if
> grohtml is configured to search for gswin32c.exe on the Win32
> platform -- I have no strong preference for either choice.

I rather prefer to use gswin32c -- the less changes the better.

Any idea why gs is called gswin32c at all?  I suspect that there is a
command/program/tool which is already called `gs'.


    Werner