> > Then our last disagreement would be on your session proposal. I know > > you would not like me to abuse our user's guide again, but if a user > > send us a revised user's guide in bundled format, none of us can > > unbundle it cleanly to our tree because only he has the session file > > on his machine. Note that my implementation treats ../blah and /blah > > both as out of tree files. > > I fail to see how that can be a problem and I have considered different > scenarios.
There are so many cases that my problems are not problems at all. This is fine. We will eventually work out a solution and I will list the pros and cons of each proposal. We will see. > 1) If the embedded files are referred by their absolute path that will not > work because most of us will use a different path. > 2) If the embedded files use a relative path if you move the file from > directory the relative path will be invalid so there is not use for this. Your session solution certain will not help here either, so? > So in order to use the session we should use absolute paths there, and as I > said before this information is only relevant to the machine where the > document was created/modified. Your session solution can at most do what I can do on a local machine, and my solution is intended to also work on machines without this session file. Bo
