From: Hans Hagen <pragma@wxs.nl>
Subject: Re: Passing a string via texexec
Date: Wed, 06 Nov 2002 18:21:11 +0100 [thread overview]
Message-ID: <5.1.0.14.1.20021106182016.00ad6748@server-1> (raw)
In-Reply-To: <200211061036.01991.john@wexfordpress.com>
At 10:36 AM 11/6/2002 -0500, you 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.
in your tex file:
\message{\envvar{test}{it does not work}}\wait
combined with
texexec --arguments="test=it works" test
so, it's there -)
Hans
-------------------------------------------------------------------------
Hans Hagen | PRAGMA ADE | pragma@wxs.nl
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
information: http://www.pragma-ade.com/roadmap.pdf
documentation: http://www.pragma-ade.com/showcase.pdf
-------------------------------------------------------------------------
prev parent reply other threads:[~2002-11-06 17:21 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
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 [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=5.1.0.14.1.20021106182016.00ad6748@server-1 \
--to=pragma@wxs.nl \
--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).