Georg Baum wrote:
> Angus Leeming wrote:
>
>> I therefore suggest a new token '$$orig_i', being the name of the
>> original file from which '$$i' was copied into the temp directory. Ok?
>
> For me, yes.
>
>> Now, Georg, could you expand on your ideas for when this magic should
>> and should not be invoked? I'm afraid I don't see why it shouldn't be
>> used every time that fig2pstex.sh is called.
>
> As long as the input is always in the temp dir, it is of course safe. The
> external and graphics inset call the converter only on files in the temp
> dir, so it should work. However, I have a general bad feeling if
> something that is supposed to read from 'a' and write to 'b' is modifying
> 'a' as a side effect. So this should at least be documented in
> fig2xxxtex.sh.
Let me try and get my head around the various possibilities. Let's store
the .fig file in the lyx document as 'images/img1.fig'. In turn, this .fig
file references 'raw.eps', so the path to 'raw.eps' from the document
directory is 'images/raw.eps' and the absolute path is
'<path to buffer>/images/raw.eps'.
1. Run View->PS etc.
The 'images/img1.fig' is copied to the /tmp directory and this copy is
modified there to contain '<path to buffer>/images/raw.eps'. XFig will be
happy and all will be well. We'll see the raw.eps image in the final PS
file.
2. Export->Latex
buffer.tex will include the snippet:
\input{images/img.pstex_t}
It is the user's responsibility to generate 'images/img.pstex_t' correctly.
2. Export->DVI
Should the DVI file reference 'images/raw.eps' or '<path to
buffer>/images/raw.eps'
3. Being nasty. Export->DVI but 'images/img1.fig' contains a reference to
'images/raw.jpg'. XFig is clever enough to handle this.
Hmmmm. I guess I'm a little confused by this all.
Angus
