2011/3/5 Cecil Westerhof <cldwester...@gmail.com> > For example, you could put the various \setvariables statements in various >> separate files and load a specific one from the context command line with >> --environment=... >> > > I tried it and it works. Only one thing: when the variables are not set > (forgot the environment parameter, file not correctly set, ...) I would like > to set default values. How would I do that? >
For who likes to something along the same lines: I attached a BASH script
that generates all the PDF's based on .per files. You call the script with:
compileContextPersonalised.sh <TEX_FILE>
One 'problem': for every generated personalised PDF, there is also a log and
tuo file. But I am using --purgeall. So why are they there?
--
Cecil Westerhof
compileContextPersonalised.sh
Description: Bourne shell script
___________________________________________________________________________________ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___________________________________________________________________________________
