From: Gerben Wierda <gerben.wierda@rna.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Using command line values in a TeX document; writing a script?
Date: Wed, 15 Apr 2020 12:19:22 +0200 [thread overview]
Message-ID: <593CDD5F-DBA7-4A5F-8236-09BEC3B5F356@rna.nl> (raw)
In-Reply-To: <F60B1BF1-8C8C-466F-84A5-8161EE5C6A1D@elvenkind.com>
> On 14 Apr 2020, at 11:52, Taco Hoekwater <taco@elvenkind.com> wrote:
>
>
>
>> On 14 Apr 2020, at 11:25, Gerben Wierda <gerben.wierda@rna.nl> wrote:
>>
>> This helps for adding information to my processing.
>>
>> What I was also looking for is that I don’t have a test.tex anymore, just the XML file I am parsing and a command line action.
>>
>> So, I use mtxrun, give it the name of an XML. lua code (using a ’script’ somewhere?) reads the XML, extracts a name (e.g. ‘foo’) from it, creates a .tex file (e.g. ‘foo.tex’), produces a .pdf file from that .tex file (e.g. ‘foo.pdf').
>
> When processing XML, I normally use
>
> context —environment=whatever.tex file.xml
>
> with whatever.tex being a mix of tex and lua to setup and process the XML directly,
> perhaps including other XML files as needed.
But this means that the whatever.tex file needs to exist beforehand and the result is whatever.pdf
I want the actual PDF to be produced have a name that comes from the XML I am processing and thus the whatever.tex file be created by lua. There is no whatever.tex file before I run the command.
Pre-command:
XML:
contains file name “foo”
there is no .tex file
Command:
produces foo.tex (gets the name from the XML) and “foo.pdf"
G
>
> But when you need to extract stuff and rename files, a Makefile or shell script
> comes more naturally (at least for me).
>
> Taco
> ___________________________________________________________________________________
> 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://context.aanhet.net
> archive : https://bitbucket.org/phg/context-mirror/commits/
> wiki : http://contextgarden.net
> ___________________________________________________________________________________
___________________________________________________________________________________
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2020-04-15 10:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-13 8:29 Gerben Wierda
2020-04-14 7:16 ` Taco Hoekwater
2020-04-14 9:25 ` Gerben Wierda
2020-04-14 9:52 ` Taco Hoekwater
2020-04-15 10:19 ` Gerben Wierda [this message]
2020-04-15 11:54 ` Wolfgang Schuster
2020-04-15 12:13 ` Gerben Wierda
2020-04-15 12:43 ` r.ermers
2020-04-14 10:05 ` 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=593CDD5F-DBA7-4A5F-8236-09BEC3B5F356@rna.nl \
--to=gerben.wierda@rna.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).