----- Original Message -----
From: "Geoffrey Lloyd" <[EMAIL PROTECTED]>
To: "Stephen Harris" <[EMAIL PROTECTED]>; "Uwe Stöhr"
<[EMAIL PROTECTED]>
Cc: "LyX-Users" <lyx-users@lists.lyx.org>
Sent: Wednesday, December 07, 2005 4:25 PM
Subject: Re: WinInstaller 0.51
Geoffrey, that was some good sleuthing work, I admired the ingenuity
and persistence. The documentation for Miktex either flatly states, or
strongly recommends, installing MikTex to a directory without spaces.
I think the defaults are c:\texmf and c:\localtexmf.
Just to clear this up this is a problem with Ghostscript not Miktex.
If this is a problem with Ghostscript, rather than paths with spaces, or
LyX, why did "gswin32.exe 0lsypreview.ps" work? Was Ghostscript
used to create 0lsypreview.ps?
I'm under the impression that the same ghostscript was used in both
cases, C:\Lyx which worked and C:\program files\lyx which did not.
The difference is in the path. Miktex and Aspell say to install in paths
without spaces. If Miktex or Aspell failed because of a space in the
path one would not say there is a Miktex or Aspell problem but a
Path problem (due to Linux/Windows porting). The Path appears to
be the problem with ghostscript not working. This seems to be my
day to learn things, so could you provide a little more clarity? I don't
mean repeat Uwe's evaluation, but explain why his diagnosis is correct.
Hmmm good point. Wherever Lyx is the temp directory still has paths with
spaces and so 0lyxpreview.ps still has spaces in its path.
Maybe it is something to do with the path to GS having spaces in this case
but we have stumbled across another problem with GS which is not related.
I honestly couldnt say.
uwe: Could you check as last try to copy the "0lyxpreview.ps" from LyX's
temp directory to LyX's install folder ~\etc\Ghostscript\bin
Then start a console, change to ~\etc\Ghostscript\bin and try if the
command
The command
gswin32c.exe 0lyxpreview.ps
is succesful with your file on my system.
GL: And on mine if i put 0lyxpreview.ps in the same folder as gswin32c.exe
or tell it where to find it. This suggests it cant find the .ps file maybe?
SH: When you put the object file into the same directory as the
executable file, as when copying "0lyxpreview.ps"into Ghostscript/bin
that is going to eliminate a problem with Paths with spaces since there
is no directory with spaces in them to be traversed. Sometimes an issue
of using relative paths versus absolute paths arise because a quirky file
with the same name as the executable may exist earlier in the Path
statement.
gswin32c.exe 0lyxpreview.ps
is successful.
GL wrote: It is (I think i mentioned this in the last email)
