On Wed, Apr 2, 2008 at 5:23 PM, José Matos <[EMAIL PROTECTED]> wrote: > On Wednesday 02 April 2008 22:43:57 Bo Peng wrote: > > Actually, I know only one limitation (assuming others are bugs), and > > this limitation exists from lyx 0.1. I mean, you simply cannot use a > > file with absolute-path on different systems. > > Actually you are referring to version 1.5 the first version (don't ask :-) > lyrics) and the next one lyx 0.5.
Good to know. :-) > OK, let us suppose the following scenario where we have an embedded file > with a given content that was originally in a certain absolute path. In the > current author's path there is a file with the same absolute name but a > different content. What do you suggest to do? > > a) use the external file > b) use the external file and suggest to replace the internal with the > external > c) use the internal file warning that there is an external file > d) something else If the .lyx file is in bundled mode, the external files are ignored. (This is one of the advantages. You do not have to handle external files in this mode). If you unbundle, file checksums are compared if the destination file exists. If they differ, users are asked whether or not they want to overwrite. In either case, the resulting external file will be used because the .lyx file is no longer in bundled mode. If in bundled mode and you would like to use the external version, right click the inset and select 'update from external file' (This does not exist, yet :-) These work for all files, not only files with absolute paths. Cheers, Bo
