John Weiss <[EMAIL PROTECTED]> writes: > Okay, then I'm confused and don't understand what it is you're doing. > I was under the impression that the files in question weren't > generated, but were pre-existing EPS files. I was also under the > impression that you were "moving" everything to a temp-directory so > that the resulting DVI files would contain only relative paths, not > absolute ones.
If I understand correctly, it' s not the problem with EPS files themselves but with XFig files which reference EPS files, and TeX files which reference EPS files which are either pre-existing or generated from XFig, and about the resulting DVI files which have the same paths as the TeX files. Of course it would be ok to make symlinks to files which _don't_ reference any other files, although I'm not sure if that will be a big advantage since the temp dir will be deleted later anyway. The mess comes from the fact that with the external insets LyX is so open for different file formats that it is difficult to keep track which files are needed exactly for a given document. BTW, am I correct that LyX does _not_ support EPS files which reference other files ... yet ;-) ? > You can ignore my comments. All or just the one about symlinks? ;-) Anyhow, this is such a confusing topic that it's probably ok to discuss it with some redundancy. That will help to clarify this for us who didn't implement it :-) > BTW: While Windoze doesn't have native symlinks, it does have > shortcuts. You aren't serious, are you? We could as well exploit the specialities of Apple aliases, NFS automounts or Linux userfs - I'm sure we could find a good use for any of those. Brrr, shudder ... > Additionally, with the Cygwin libraries, you can have > symlinks under Windoze. They work only with the Cygwin programs, but > that's a non-issue since (I assume) we need Cygwin for the Win-version > of LyX. Someone else answered that ... :-) Ciao /Andreas
