Re: [toolbox] Extended Attributes
Status: Planning
Brought to you by:
jlaurens
From: <jer...@u-...> - 2005-07-08 10:23:58
|
Le 6 juil. 05, =E0 23:15, Maarten Sneep a =E9crit : > On 6 Jul 2005, at 8:38, J=E9r=F4me Laurens wrote: > >> Le 5 juil. 05, =E0 22:39, Maarten Sneep a =E9crit : >> >>> Why would you want to change the name of the master file? I don't=20 >>> get the example you give here - since the slave-files are stored in=20= >>> the master file, and their relative location is fixed through the=20 >>> \input statement (or format specific alternatives). So _moving_ the=20= >>> master is not an option, and renaming (IMHO) is a relatively rare=20 >>> action. Inefficiency is unimportant for such cases. >>> >> >> Gerben just gave me an example where he splitted a big book in=20 >> several chapters, each one could be typeset separately. >> Changing the master name allows this. If each chapter consists of one=20= >> file, you just change the master file name in the header, but if it=20= >> consists of many different files, then this is not practical. > > Call me thick-headed, but I don't see how this works. Care to share a=20= > minimal example? I do not use this design myself but I trust Gerben when he tells me he=20= does (especially when ConTeXt is involved) For latex, I think that many different copies of the master files with=20= different \includeonly declarations will do the job. It is easy to ensure that the preamble is the same except the=20 includeonly's.= |