Willi— Many thanks. That is helpful and much appreciated. I missed the closing remark about \enablemode on the Mode page of ConTeXt wiki (which I come to rely on extensively). The advantage of the command line/texexec approach is that one can specify the name of the output using --result xxx and so avoid clobbering files. But I suspect that the users will find it easier to play with \enablemode commands using their various editors of choice and to rename the output before recompiling the file. Alan On Oct 16, 2005, at 2:53 PM, Willi Egger wrote:
Hi Alan,
This is simle to solve:
%\enablemode[screen] \enablemode[print] \envrionment yourenvironment
Important is to enable the required mode before loading the environment file. - Dit you know that you can select multiple modes e.g. you have a print-mode and the document should be created for letter, A4 and A5. So you could define a letter-mode an A4-mode and an A5-mode.
In the document you can say
\enablemode[print,A4] \envrionment yourenvironment
Hope that this helps
Willi
Alan Bowen wrote:
Following the example in the ConTeXt Wiki (http:// wiki.contextgarden.net/Modes) I have defined an environment file that specifies two modes (screen, print) for the production of the same source file. This works well when the appropriate texexec commands are given at the command line.
The problem is that I am trying to set this production up for users who are happier with a GUI. Is there a way to do generate diverse outputs from the same source file without resorting to the command line? I have experimented with TeXShop—the users tend to works on Macs —but without success thus far.
Thanks for any suggestions.
Alan
_______________________________________________ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
_______________________________________________ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context