From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: modes questions
Date: Mon, 29 Sep 2008 22:37:28 +0200 [thread overview]
Message-ID: <48E13C88.4020604@wxs.nl> (raw)
In-Reply-To: <326847810809290800j16fa684fr79f6a34765de5e97@mail.gmail.com>
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
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2008-09-29 20:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-11 9:47 Alan Stone
2008-09-11 10:46 ` Hans Hagen
2008-09-11 10:52 ` Taco Hoekwater
2008-09-11 11:37 ` Hans Hagen
2008-09-11 12:45 ` Alan Stone
2008-09-11 12:41 ` Alan Stone
2008-09-17 19:11 ` Alan Stone
2008-09-17 20:59 ` Hans Hagen
2008-09-20 15:17 ` Alan Stone
2008-09-20 16:07 ` Hans Hagen
2008-09-20 16:19 ` Alan Stone
2008-09-21 16:06 ` Hans Hagen
2008-09-29 15:00 ` Alan Stone
2008-09-29 20:37 ` Hans Hagen [this message]
2008-09-30 7:18 ` Alan Stone
2008-09-30 7:23 ` Hans Hagen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48E13C88.4020604@wxs.nl \
--to=pragma@wxs.nl \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).