"Bo Peng" <[EMAIL PROTECTED]> writes: >> The fact that >> embedding has problems to cope with it is irrelevant here. > > If I use ../bib/my.bib in my document under linux, I can not use the > same file under windows, because it shows up in the document as an > absolute path which does not exist under windows. This is IMHO a bug.
If you write ../bib/my.bib in the file filed, it will stay as it is, won't it? You only get the absolute path when you keep what browseFile does. Let's propose a different scenario, just to show that there is no perfect solution: if I write a paper with someone in my office, it may be that I have a figure in /usr/share/inria/logo.jpg. Embedding or not, it is natural for me that the browsing returns an absolute path (a relative path would become wrong as soon as I move the file). In the case of ../bib/my.bib, assuming that my.bib is some generic bib file, the solution is really to use TeX PATH mechanisms. The same holds for the graphics (I think), except that LyX will not be able to find it. JMarc
