Re: nested includes

[Joe Beach]

Hi, 

I encountered the same behaviour when I was writing my thesis. It
appears that the working directory for a lout process is set to be the
directory you are in when you give the lout command. It doesn't change
directory to get to a file referenced in an @Include statement, it just
reads it from where it is. It sounds like a reasonable behaviour to me,
although it would be nice if it could be made to accept relative paths
like you demonstrated. 

I guess that isn't really an answer to your question, just a
confirmation of what you have already seen. 

Joe Beach

On Tue, 2003-08-26 at 12:53, Eric Boucharé wrote:
> Hello
> 
> I have used lout for 3 years, and I'm very happy of it. But here is
> a little problem I meet.
> 
> I would like to make a document with nested includes. For example,
> something like that
> 
> a top file called "tp" in ./
> --------------------------------------------------------
> @SysInclude {doc}
> 
> @Document
>       @InitialFont {Helvetica Base 10p}
>       @InitialLanguage{French}
> //
> @Text @Begin
> @FullWidthRule // @D @B {titre du TP} // @FullWidthRule
> @BeginSections
> @Section
>       @Title{Introduction}
> @Begin
> @Include{"ex1/data"}
> @End @Section
> @EndSections
> @End @Text
> --------------------------------------------------------
> 
> 
> 
> a file called "data" in ./ex1/
> --------------------------------------------------------
> @Include{"images/sch1"}
> --------------------------------------------------------
> 
> 
> and another called "sch1" in ./ex1/images/
> --------------------------------------------------------
> @LP Il était une fois dans l'ouest ...
> --------------------------------------------------------
> 
> My first idea was : lout will find the relative path for each included
> file when I proceed the file with the command
> 
>       lout tp>tp.ps
> 
> Actually, it finds the file "data", but not "sch1". I have to change
> the path to @Include{"ex1/images/sch1"}.
> 
> Can someone tell me why it behaves like that ? Isn't there a solution
> to use relative paths ?
> 
> Thanks
> 
> Eric
-- 
Joe Beach <address@hidden>