Re: [MiKTeX] dvipdfm and "Program Files"

[George N. W. I. <gn...@gm...>]

On 6/25/07, Ted Pavlic <te...@te...> wrote:

> When I installed MiKTeX 2.4, it installed itself into \texmf, and that
> was fine.
>
> However, I notice now that MiKTeX 2.6 puts itself in \Program Files. I
> think the space in "Program Files" may be causing some problems. Notice
> what happens when I try to execute dvipdfm:
>
> =====
> atod_functions.dvi -> atod_functions.pdf
> [1][2(example.eps<PS>
> C:\Program Files\MiKTeX 2.6\miktex\bin\mgs.exe -q -sPAPERSIZE=a0
> -sDEVICE=pdfwri
> te -dCompatibilityLevel=1.2 -dUseFlateCompression=true -dNOPAUSE
> -sOutputFile="C
> :\DOCUME~1\pavlict.ECE\LOCALS~1\Temp\mik93.tmp" "example.eps" -c quit
> 'C:\Program' is not recognized as an internal or external command,
> operable program or batch file.
> =====
>
> As long as mgs is in the PATH, wouldn't it be preferable to just list
> "mgs" in the dvipdfm config file without the pathname? (making this
> change in the config file seems to work.

Interesting -- a user had what sounds like the same problem with
texlive after installing gs under Program Files, but I wasn't able to
get it to misbehave
on my system using just "gswin32c" in the config file.

In general, it is safer to use the full path for programs like mgs -- there will
always be the odd user who has some unrelated program called mgs.exe
before the MikTeX directory in the PATH list.  In the long run, dvipdfm needs
to support spaces in the executable pathname.

-- 
George N. White III <aa...@ch...>
Head of St. Margarets Bay, Nova Scotia