> The procedure would be exactly the same without auto, see below. I will see. The problem is with conversion.
> I don't buy that. Without auto, you do this: > - work on the .lyx and the external files the usual way > - if you want to send it to a colleague, switch embedding on and send the > file Then, you lose the original file information. > - when you get it back, switch embedding off and possibly confirm the > overwriting of some files, on a case by case basis or all at once. No. The problem is with the insets! When you have a single version, they are coded with that file. Then, when you pack/unpack, you will need to update the insets. This is not always doable. If your figures are within the document directory. You can handle this problem by relative path, to document directory (external) or to temppath() (embedded). However, when you have a figure that uses absolute path, I do not see a way to retain its path information. > Or you could choose to have embedding permanently on and never use external > files (this would also be possible with auto IIUC). This makes updating figures difficult, a major problem with word/embedding. > With auto, I never know when LyX will overwrite external files with the > embedded version or vice versa. see later. > For example, when I close LyX, edit an > external .png file with gimp, and open LyX again, how should LyX know that > in this case it should use the external file instead of the embedded one, > because I did not receive a modified file from a colleage? > It cannot know, so I have to tell it (by switching embedding off). The default is always use external file, just like what will happen to plain-text lyx file. (Such compatibility is one of the reasons for AUTO). > And if I edit an external file while my colleague has the embedded file I do > not > want it to get overwritten by the embedded version, so 'auto' cannot be > completely automatic and needs also a confirmation. But then where is the > advantage of auto? Again, .lyx will use your modified version by default. If you unpack, lyx will ask you if you want to overwrite. > Which information is lost? To be exact, path of files outside of document directory and which files will always be embedded or external (info in manifest). > > Also, as I have said, lead to completely DIFFERENT ways to > > handle .lyx file. You either go the MS/Word way, or the transitional > > lyx way. The auto feature makes the differences minimal. > > I don't understand. OK. Let us use your suggestions: simple on/off. Embedded .lyx: Insert figure, always embedded, remove or modify external file does not matter. Difficult to update figure. Plain-text .lyx: Insert figure, not embedded, remove or modify external file matters. Easy to update figures. What I have tried is: Insert figure, AUTO embedding, remove or modify external file matters. Easy to update figures. > Please note that I like the embedding feature, and this > is meant to be a constructive criticism. I do understand. I think we should first figure out the major ways of using this embedding feature, before we talk about implementations. I guess you have understand now that I want embedding, as well as the convenience of modifying external files. Without AUTO, after I update an figure, I will need to go to the lyx document, locate the figure, re-insert or update the inset. Bo
