From: Cecil Westerhof <cldwesterhof@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Personalizing a PDF generated with ConTeXt
Date: Sat, 5 Mar 2011 13:03:44 +0100 [thread overview]
Message-ID: <AANLkTi=phwWSrfn5tqpyy3BumKEwyhiCr=aD6pCU4rdD@mail.gmail.com> (raw)
In-Reply-To: <AANLkTikbppoHhBda6W0Jz3JpBR0LGKJ6FkiPk0d8bfA6@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 787 bytes --]
2011/3/5 Cecil Westerhof <cldwesterhof@gmail.com>
> 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?
>
For who likes to something along the same lines: I attached a BASH script
that generates all the PDF's based on .per files. You call the script with:
compileContextPersonalised.sh <TEX_FILE>
One 'problem': for every generated personalised PDF, there is also a log and
tuo file. But I am using --purgeall. So why are they there?
--
Cecil Westerhof
[-- Attachment #1.2: Type: text/html, Size: 1344 bytes --]
[-- Attachment #2: compileContextPersonalised.sh --]
[-- Type: application/x-sh, Size: 809 bytes --]
[-- Attachment #3: 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
___________________________________________________________________________________
next prev parent reply other threads:[~2011-03-05 12:03 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 [this message]
2011-03-05 12:23 ` Wolfgang Schuster
2011-03-05 13:36 ` 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='AANLkTi=phwWSrfn5tqpyy3BumKEwyhiCr=aD6pCU4rdD@mail.gmail.com' \
--to=cldwesterhof@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).