Angus Leeming wrote:
The only thing that I can imagine is that yap is falling over because
of the "." in "rubin.BUSINESS". Perhaps I can leave you to investigate
further?
I tried myself, copying lyx_tmpdir88a04036 to
rubin.BUSINESS/lyx_tmpdir88a04036 and renaming the absolute paths to the
graphics file in the .dvi file as appropriate.
yap behaved perfectly, so I'm afraid that you're going to do most of the
leg work if you want the problem to be resolved.
Happy to try (although it's my RSI-inflamed mouse-moving wrist, not my
leg, doing the work). I may need some guidance, though, as my knowledge
of DVIs (and LyX, for that matter) is limited.
I had the same suspicion about the dot in the path, but I think I've
ruled it out as the culprit. About the time I sent you the archive, I
tried moving the source docs to C:\Temp\my.dir\ and running LyX against
those copies. View->DVI worked fine.
I just tried a more definitive experiment. I created a rubin_BUSINESS
directory under Docs and Settings, replicated the remainder of the path
to the LyX buffer directory there, did the DVI->DTL->DVI circuit with
s/rubin.BUSINESS/rubin_BUSINESS/, and yap blew up on the modified DVI.
Then I created rubin.XBUSINESS under Docs and Settings, cloned the
subdirectories, s/rubin.BUSINESS/rubin.XBUSINESS/, changed the names of
the .eps files from things like
C__Documents_and_Settings_rubin_BUSINESS_My_Documents_MGT_914_Homework_prob_3_8_box.eps
to fig1.eps (etc.), made the appropriate changes in the .dtl file, and
got a .dvi file that yap liked.
So my suspicion at this point is that there is an issue about path/name
lengths. Next experiment: I created a path
C:\Temp\Local Settings\Temp\lyx_tmpdir356a02852\lyx_tmpbuf0
and cloned the contents of the buffer directory there. I left the file
names at their original unholy lengths but edited the .dtl file to
s/Documents and Settings\/rubin.BUSINESS/Temp/ so that the local copies
of the figures were referenced. The modified .dvi file displays just
fine in yap.
I should note that whenever I edit file names/paths in the .dtl file,
dt2dv issues some warnings about resizing strings. My last experiment
was to change the second Temp in the above path to progressively longer
names (Temp012345, Temp0123456789abc, etc.) until yap broke. I got to a
point where, according to dt2dv, the total lengths of the arguments to
the three special commands were 219, 223 and 221. At this point, yap
displayed the first image but broke on the second one. So I suspect
that somewhere between 219 and 223 is a limit to how long a string yap
can process. This limit appears to include not just the path/file name
but also the "PSFile=" part, the bounding box parameters, etc.
Perhaps you can try an experiment at you end with a long path string and
see if you can reproduce this?
Condolences from this side of the pond on today's attacks by Satan's
minions.
-- Paul
