From: Henning Hraban Ramm <texml@fiee.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: output file name query
Date: Fri, 22 May 2020 17:39:04 +0200 [thread overview]
Message-ID: <0FA790F7-06EA-4FC9-9150-F843D0D32EA5@fiee.net> (raw)
In-Reply-To: <f8547d79-4bc6-d2f7-99cf-0eefa9acea3f@gmail.com>
> Am 22.05.2020 um 15:09 schrieb Wolfgang Schuster <wolfgang.schuster.lists@gmail.com>:
>
> Alan Bowen schrieb am 22.05.2020 um 14:33:
>> In my project, I process a single product file by enabling various modes. What I would like to do is to vary the name of the output PDF file in each instance.
>> So, in processing a file, how does one go directly from prd_filename.tex to myfilename.pdf rather than to prd_filename.pdf—assuming that it is possible?
>> Any tips or pointers to what I should be reading will be greatly appreciated.
>
> 1. Drop the weird (sorry Hraban) naming system and use myfilename for your product.
I force nobody to use that.
> 2. Use the result option on the command line, e.g. "context --result=myfilename prd_filename.tex".
But that still produces a "prd_filename.*" first and then renames it, making it impossible to keep a "prd_filename.pdf". Or did that change recently?
My workflows are adapted to that behaviour: "prd_*.pdf" is just the temporary version, none of those leaves my computer, but only nicely named PDFs (usually MyProductName_yyyy-mm-dd.pdf).
> 3. Ask Hans to add the result option to the first line of the document which is read by the context script before it creates the PDF.
>
> % result="myfilename"
> \starttext
> ...
> \stoptext
That contradicts the mode approach. It would be nice if we could set (or can we?) the result from within the product, depending on a mode – since the product is renamed only later anyway, that could be viable.
Best, Hraban
___________________________________________________________________________________
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-05-22 15:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-22 12:33 Alan Bowen
2020-05-22 13:09 ` Wolfgang Schuster
2020-05-22 15:39 ` Henning Hraban Ramm [this message]
2020-05-22 20:08 ` Rik Kabel
2020-05-23 12:43 ` Wolfgang Schuster
2020-05-23 13:46 ` Gerben Wierda
2020-05-23 19:46 ` Wolfgang Schuster
2020-05-23 21:52 ` Henning Hraban Ramm
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=0FA790F7-06EA-4FC9-9150-F843D0D32EA5@fiee.net \
--to=texml@fiee.net \
--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).