ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Alan Stone" <software.list.1es9s@gmail.com>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: modes questions
Date: Wed, 17 Sep 2008 21:11:32 +0200	[thread overview]
Message-ID: <326847810809171211h7cd20ff3ua878510eb9083968@mail.gmail.com> (raw)
In-Reply-To: <48C8F71E.50408@wxs.nl>


[-- Attachment #1.1: Type: text/plain, Size: 1572 bytes --]

On Thu, Sep 11, 2008 at 12:46 PM, Hans Hagen <pragma@wxs.nl> wrote:

> Alan Stone wrote:
> > Hi,
> >
> > (1) --mode=modelist
> >
> > (1.1) Is there a limit to the number of modes in modelist ?
>
> no, just what the console and memory permit
>
> > (1.2) Is there a way to call the modelist and submit it to conditional
> > testing within ConTeXt ? For example, to lookup (true/false) the
> > presence of modes containing/starting with (an) alphannumeric
> > string(s) ?
>
> \doifmodeelse{somemode} { } { } etc etc etc
>
> > (2) --modefile=file
> >
> > (2.1) What's the syntax of a modefile ?
>
> this concerns examodes stuff that we use for process control at pragma
>
> > (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


As I'm not familiar with XML, neither using ConTeXt with XML...

What if I want to pass a list of modes: mode1, mode2, mode3, .... ?


-- 
Best,
Alan

* ConTeXt ver: 2008.09.10 14:01 MKIV fmt: 2008.9.14 int: english/english
* Windows XP Home SP3

[-- Attachment #1.2: Type: text/html, Size: 2458 bytes --]

[-- Attachment #2: Type: text/plain, Size: 487 bytes --]

___________________________________________________________________________________
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
___________________________________________________________________________________

  parent reply	other threads:[~2008-09-17 19:11 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 [this message]
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
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=326847810809171211h7cd20ff3ua878510eb9083968@mail.gmail.com \
    --to=software.list.1es9s@gmail.com \
    --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).