Angus Leeming wrote:
Angus> That's because we'd also have to change os_win32.C's
Angus> implementation of os::external_path:

The current code is clearly bogus. You patch makes more sense, I
believe. Does running latex still work after that?

I've just installed MikTeX. I'll have a play.

Well, I tried. I'm afraid that latex requires the path to be specified as "foo/bar" rather than "foo\bar"

However, I've discovered another problem that we should address first.

I attach the contents of lyx_tmpbuf0 after a failed attempt to generate a .dvi file. The directory contains:

lyx_tmpbuf0/
    J__MinSYS_home_Angus_trial_tex_subdir_ICcrest_wb.eps
    trial1.aux
    trial1.dvi
    trial1.log
    trial1.tex
    trial2.aux
    trial2.dvi
    trial2.log
    trial2.tex
    trial3.aux
    trial3.dvi
    trial3.log
    trial3.tex

trial1.tex is the failed attempt. Notice that it contains the \includegraphics command:

\includegraphics[%
width=7cm]{C:/DOCUME~1/Angus/LOCALS~1/Temp/lyx_tmpdir1872a03448/lyx_tmpbuf0/J__MinSYS_home_Angus_trial_tex_subdir_ICcrest_wb}

The associated dvi file is pretty spectacular!

trial2.tex contains the command:
\includegraphics[%
  width=7cm]{J__MinSYS_home_Angus_trial_tex_subdir_ICcrest_wb}

It succeeds in rendering this local file.

trial3.tex is identical to trial1.tex except that it replaces the "~" characters in the file path the "_". It also fails to compile, but fails now for intelligible reasons:

! LaTeX Error: File `C:/DOCUME_1/Angus/LOCALS_1/Temp/lyx_tmpdir1872a03448/lyx_t
mpbuf0/J__MinSYS_home_Angus_trial_tex_subdir_ICcrest_wb' not found.
See the LaTeX manual or LaTeX Companion for explanation.

I guess that this is all pretty clear. We're going to have to escape the "~" in the file path. However, I'm a little suprised by the absolute path. Wouldn't this be just the file name normally?

Angus

Attachment: lyx_tmpbuf0.tar.gz
Description: GNU Zip compressed data



Reply via email to