> I think that the dos time is gone long ago and a lyx suffix should stand for > lyx files no matter what the internal format used.
This can be done easily later after you and JMarc (and others) reach an agreement. I personally like a unique .lyx extension, even if compression is removed. > > Yes. That is why I say it is dangerous. I really do not know how to > > handle the extraction of files outside of the document directory. > > I agree with you. Backporting is a last resort and not something we > encourage people to do, it is commodity that we provide as bonus not as a > normal feature, so I think that being safe here is the best thing to do. I guess in lyx2lyx, we can use simple rules like: 1. copy embedded files that are originally within the document directory to its original locations. 2. copy embedded files that are originally outside of the document directory to the document directory. 3. do not overwrite any file. In lyx, when some sort of unpack button is pressed, we extract files to their original locations. We prompt for overwrite if necessary (after test if a file is changed). > Regarding the feature I think that every paths inside the embedded file > should be relative and inside the current dir. This is the case now. Embedded files within the document directory is stored in relative paths. For others, only filename is saved. > I am not sure it is wise to > save the original path (for embedded component, for external paths that is > not a problem) even for privacy reasons. I agree. > After embedding we get a local copy > so the original location becomes irrelevant. One important feature of the design is 'AUTO' embedding, in that the embedded files will be updated automatically from external files. That is to say, I can continue to change external files, and lyx will automatically embed the latest version. This is something I really want but certainly makes things much more complicated. For example, original paths need to be stored. Bo
