From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: A pdf-file per XML-node
Date: Thu, 11 Nov 2010 10:08:48 +0100 [thread overview]
Message-ID: <4CDBB2A0.7080207@wxs.nl> (raw)
In-Reply-To: <C900D416.26E7%daniel.grycman@rub.de>
On 10-11-2010 10:58, Daniel Grycman wrote:
> Hi list,
>
> |<worker>
> |<surname>xxx</surname>
> |<name>xxx</name>
> |</worker>
> |<worker>
> |<surname>xxx</surname>
> |<name>xxx</name>
> |</worker>
> |<worker>
> |<surname>xxx</surname>
> |<name>xxx</name>
> |</worker>
> |<worker>
> |<surname>xxx</surname>
> |<name>xxx</name>
> |</worker>
> For every<worker> a separate pdf is needed. It would be also nice to have
> the<name>-entry as a file-name. Any ideas?
you can make a worker.lua file that does it, something (untested) ...
local x = xml.load("workers.xml")
local i = 0
for e in xml.collected(x,"worker") do
i = 1 + 1
logs.simple("processing worker %s",i)
os.execute("context worker --worker=" .. i)
end
and run that with
mtxrun --script worker.lua
where the worker.tex file looks like
... usual xml setups using workers.xml ...
\xmlfilter
{main}
{worker[position()==\getdocumentargument{worker}]}
{xml:worker}
... special worker setup
\startxmlsetup xml:worker
...
\stopxmlsetup
etc etc
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 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 : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2010-11-11 9:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-10 21:58 Daniel Grycman
2010-11-10 22:04 ` Martin Schröder
2010-11-11 4:20 ` Latest info for Correspondance module Russell Urquhart
2010-11-11 5:23 ` Wolfgang Schuster
2010-11-11 13:16 ` Russell Urquhart
2010-11-11 13:31 ` Wolfgang Schuster
2010-11-11 13:37 ` Russell Urquhart
2010-11-11 9:00 ` A pdf-file per XML-node Hans Hagen
2010-11-11 9:08 ` Hans Hagen [this message]
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=4CDBB2A0.7080207@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).