On Mon, Sep 29, 2008 at 10:37 PM, Hans Hagen <pragma@wxs.nl> wrote:
Alan Stone wrote:
> On Thu, Sep 11, 2008 at 12:46 PM, Hans Hagen <pragma@wxs.nl> wrote:
>
>> Alan Stone wrote:
>>> (2.2) How does ConTeXt handle a modefile ? Are the modes parsed into a
>>> modelist ( re: question 1.2 ) ?
>> best use ctx files instead, like in
>>
>> == somefile.ctx ===
>>
>> <?xml version='1.0' standalone='yes'?>
>>
>> <ctx:job>
>>     <ctx:preprocess/>
>>     <ctx:flags>
>>         <ctx:flag>texengine=luatex</ctx:flag>
>>         <ctx:flag>interface=en</ctx:flag>
>>     </ctx:flags>
>>     <ctx:process>
>>         <ctx:resources>
>>             <ctx:mode>proofing</ctx:mode>
>>             <ctx:environment>somestyle.tex</ctx:environment>
>>         </ctx:resources>
>>     </ctx:process>
>>     <ctx:postprocess/>
>> </ctx:job>
>>
>> texexec .... --ctx=somefile
>>
>
> How about the other texexec options,

i implement them stepwise, i leave out those no longer relevant and all
--pdf* ones will be done with ctx files instead

Are there currently other ones than those listed above which already have been implemented ?

How can one follow along which additional ones are implemented with the update releases ?

--
Best,
Alan

Ubuntu 8.04 Hardy Heron (Desktop)
  * ConTeXt  ver: 2008.09.16 19:49 MKIV  fmt: 2008.9.20  int: english/english  (ConTeXt minimals installation)
  * texexec --lua foo