Bo Peng wrote: >> > Then, you lose the original file information. >> >> I thought that you stored this info for all files. > > I do, but if I use the embedded or not solution, I can throw away > external file information.
But you do not need to throw it away! Especially if you still need this information. I always assumed that you would keep it. >> That is a problem anyway: You either store this info (privacy problem) or >> not. > > This is, IMHO, not a privacy problem because we need the same amount > of information we currently store in the plain-text .lyx file. The > problem is that without this manifest file, I do not know how to store > an embedded file (in temppath()) that originally uses absolute path. I know that you need the info. But that does not make the privacy problem go away: If I bundle everything together I do not expect that this info will still be in the bundle. Of course you can store absolute paths in plain LyX files, too. But that is different IMHO, because you do not send such a file away, it would not work anyway. >> Again, this is unrelated to the auto setting, because you need this >> info in both cases. > > Not in your case. Because you insist to throw it away :-( >> In all other cases it is easy: You simply >> click the edit button in LyX. The important thing is that you have the >> choice: Nobody forces you to permanently embed the files, but if you want >> that you may do so. > > Then you need to give me an option to use embedded or external file. > This is what I am doing (not related to AUTO) but JMarc feels that > indivudal setting is unnecessary. I would not use it either, but I can imagine that some people would like it. IMHO as long as it does not get into the way if you don't want to use it such an option is not a problem. >> I would not consider clicking the edit button in LyX difficult. But even >> if you do: Simply switch embedding off after you receive the file, and >> switch it on before you send it again. This should not be more than one >> mouse in a suitable dialog click each time. > > Because I have a few fancy features like embedding layout, disable <-> > enable may lose information. UNLESS we store manifest in the .lyx file > so it is not used in plain text format, but will not be lost. I still don't get it. You can implement disable <-> enable in such a way that you do not loose any information even with superfancy features. Georg
