Juergen Spitzmueller wrote:
Bo Peng wrote:
However, people are unhappy about one particular
problem:
Files with full path name can be embedded, and works as usual when
embedded. However, it can be troublesome when this file is extracted
under a different operating system. E.g. how would you extract
/usr/local/image/my.img under windows? The current solution is that
users can choose to save to a different directory (with needed changes
in .lyx file), but the problem may happen again, assuming another
absolute-path file is used, if the .lyx file is sent back to the
original file system, and extract over there.
Is the other problem people are unhappy about solved? I.e., the problem
where files without paths that are managed by TeX's kpathsea system (and
stored in the texmf tree) were erroneosuly saved as being in the document
(relative) path (bug 4649)?
No. I have a fix in my tree that deals with the bibliography-related
issue, and Bo has one in his, and I think we agreed the other day that I
could go ahead with mine. It works better with some other changes I'd
like to make to the bibfilesCache_ (these have to do with improving the
handling of child documents). But I haven't had time to do that yet,
since we just agreed it yesterday. There is also this long conversation
now about InsetCommandParams that is somewhat related, but the fix for
this problem need not wait for that to be resolved. A working fix with a
handful of deferred FIXMEs should be possible shortly.
Nothing has yet been done, so far as I know, about other affected
insets, but the problem should be solvable in much the same way. I guess
it would help me to know which insets are affected.
rh
