ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Fwd:  Personalizing a PDF generated with ConTeXt
Date: Sat, 5 Mar 2011 13:23:29 +0100	[thread overview]
Message-ID: <0FCD044E-4107-4487-9C86-46CC94800646@gmail.com> (raw)
In-Reply-To: <AANLkTikbppoHhBda6W0Jz3JpBR0LGKJ6FkiPk0d8bfA6@mail.gmail.com>


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


Am 05.03.2011 um 12:25 schrieb Cecil Westerhof:

> 2011/3/1 Taco Hoekwater <taco@elvenkind.com>
> \setvariables and \getvariables sounds like the most general solution
> 
> in that case.
> 
> 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?

%\enablemode[variables]

\startmode[variables]
\setvariables
  [test]
  [one=One,
   two=Two]
\stopmode

\starttext
\doifelsevariable{test}{one}{1: \getvariable{test}{one}}{??}\par
\doifelsevariable{test}{two}{2: \getvariable{test}{two}}{??}
\stoptext

Wolfgang


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

[-- Attachment #2: Type: text/plain, Size: 486 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  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  parent reply	other threads:[~2011-03-05 12:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-01 15:09 Cecil Westerhof
2011-03-01 15:13 ` Matthias Weber
2011-03-01 15:20 ` Taco Hoekwater
     [not found]   ` <AANLkTin6pFP3ioN2cUPT=zxned0bDO8aGvm37GZKrDHE@mail.gmail.com>
     [not found]     ` <4D6D22A8.8070406@elvenkind.com>
     [not found]       ` <AANLkTikbtz4F5R70ryuBMPM3p=dSQPTXL-_CFYTn28Gi@mail.gmail.com>
2011-03-05 11:25         ` Fwd: " Cecil Westerhof
2011-03-05 12:03           ` Cecil Westerhof
2011-03-05 12:23           ` Wolfgang Schuster [this message]
2011-03-05 13:36             ` Fwd: " Cecil Westerhof

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=0FCD044E-4107-4487-9C86-46CC94800646@gmail.com \
    --to=schuster.wolfgang@googlemail.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).