Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

I am having proplems using figures (.eps files) in multipart documents.

In my thesis, which I am writing using Lyx (version 1.04), I have
created
a master document and a number of Chapters.
In a directory called Thesis I have a subdirectory Master
(comtaining the master file) and a directory for each 
chapter.

I have created figures for my thesis using XFig.  Some are
.eps files and some are .pstex_t.tex files (combined postscript/latex
files).  Each figure is stored in the Chapter where it is used.
I include the eps files in a chapter using "include figure"
and the .pstex_t.tex files using "include file setting: input".

In order that the figures can be found both when I am working
only on a chapter and also when I am working with the master
file I give the pathname for each figure as follows (for ChapterK)

    "../ChapterK/figurename.pstex_t.tex"  

        or

    "../ChapterK/figurename2.eps"

Now the .pstex_t.tex files are found correctly both through the chapter
file and through the master file.  However the .eps files can
be found by the chapter file but not by the master file.

I discovered that the problem is that someone is too smart and
shortens  "../ChapterK/figurename.eps" to just  "figurename.eps".
(Try setting the path and then return to check what the actual path
name used is later.)
This is of course a correct (but unnecessary) shortcut for the
Chapter file but an incorrect shortcut for the master file.
As a result the master file cannot find the .eps figure files
but can find the pstex_tex files.

There are two crude solutions:

1)  Use absolute path names for .eps files.
    This is ugly and a problem because I have to deal with porting
    my thesis to other machines. I haven't tested this yet.

2)  Only use pstex_tex files.  This is also ugly but it is the
    prefered solution and the one I will implement if no one 
    can suggest a better solution.  Most of my files are
    pstex_tex_t.tex files anyway so I can live with this but
    for some people this would be a real pain if not impossible.


Can anyone suggest alternative solutions?

Is this problem fixed in  Lyx 1.1.4?

Thanks in advance for you help.

Ralph Boland

Reply via email to