> > But if lyx forbids, or make it very difficult, to make a file that can > > be compiled anywhere, it is lyx' problem. > > You can put the files you want inside the bundle.
This is my proposal, which can embed any file. The files will be in the bundle, and if they are extracted, they can only be extracted to the document directory. The only problem this proposal can cause, is that, *if* a user wants to unbundle such a file (instead of working in the bundle-editing mode), and *if* a file with out-of-tree source needs to be extracted, the user has to extract the files to the document directory, which causes changes to the .lyx file (adjust to the related insets). > > Then why donot you use this technique to our user's guide? I know your > > answer, and that is my problem as well. > > As Jose already answered, all of our doc in its own virtual bundle > anyway. We distribute in together, and the links stay internal. I was asking why do not you use $TEXINPUT so that you can include these images NOT using ../../images paths? If you can not do it for lyx, do not expect me to use it either. People has suggested many solutions, but why do we want to impose such a restriction while it is *not* needed? Why do you expect our users to know all the tricks, whereas they can work as usual using my proposal? As I have shown above, the only problem this may cause can be solved trivially. Bo
