> On 15 Apr 2020, at 13:54, Wolfgang Schuster wrote: > > Gerben Wierda schrieb am 15.04.2020 um 12:19: >>> On 14 Apr 2020, at 11:52, Taco Hoekwater wrote: >>>> On 14 Apr 2020, at 11:25, Gerben Wierda 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" > > The TeX file in Tacos example contains the xmlsetup entries which are used > to map the XML tags to ConTeXt commands and environment, the resulting > PDF file has the same name as the XML file. That is different from the resulting PDF file has the name of an entry/field in the XML file. So, what I am looking for is: command foo.xml which results in bar.pdf where ‘bar’ is text in foo.xml G > > Wolfgang >