From: "Gregory D. Collins" <gcollins@cs.yale.edu>
Subject: Re: Passing a string via texexec
Date: Wed, 06 Nov 2002 10:57:33 -0500 [thread overview]
Message-ID: <3DC93BED.30004@cs.yale.edu> (raw)
In-Reply-To: <200211061036.01991.john@wexfordpress.com>
John Culleton wrote:
> This is more of a convenience feature than a necessity, but here goes.
>
> I plan to personalize copies of an ebook in pdf format by putting the
> string:
> "This copy prepared for Joe Smith" on the page, perhaps in a footer.
> This means I have to recompile the book for each separate customer. It
> would save a minute if I could just pass a named string to pdfetex in
> the same way one passes a mode to the program. I am looking for
> something like:
> texexec --mode=ebook --string="Joe Smith" mybook.tex
>
> ...and then have a way to pick up that string in the TeX file and use
> it.
>
> All this does is save me from editing the file in every instance. If
> it is too big a deal forget it.
You can solve this using scripting.
In your TeX file:
...\input{name}...
On the command line (in Windows): put then names in names.txt, then:
for /f %i in (names.txt) do @echo %i > name.tex && texexec --pdf foo.tex
&& ren foo.pdf "%i.pdf"
In the Bourne shell:
for i in `cat names.txt`; do echo $i > name.tex; texexec --pdf
foo.tex; mv foo.pdf "$i.pdf"; done
--
Gregory D. Collins <gcollins@cs.yale.edu>
GPG key available at pgp.mit.edu keyserver, id 0xD2EECA60
next prev parent reply other threads:[~2002-11-06 15:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-06 15:36 John Culleton
2002-11-06 15:57 ` Gregory D. Collins [this message]
2002-11-06 20:12 ` Henning Hraban Ramm
2002-11-06 20:38 ` Hans Hagen
2002-11-09 10:44 ` Henning Hraban Ramm
2002-11-06 17:21 ` 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=3DC93BED.30004@cs.yale.edu \
--to=gcollins@cs.yale.edu \
--cc=ntg-context@ref.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).