From: Hans Hagen Outside <pragma@wxs.nl>
Subject: Re: MPost: how to pass variables from mpost to TeX.
Date: Sun, 13 Jun 2004 23:21:49 +0200 [thread overview]
Message-ID: <40CCC56D.4060506@wxs.nl> (raw)
In-Reply-To: <20040613161419.7E5BC4160BD@ws5-2.us4.outblaze.com>
vinuth madinur wrote:
>Hi everyone,
> My mpost doesn’t have “textext” macro.
>So, what are the other ways of doing it?
>
>What I want to do is this :
>
>%I have a variable “GbLableName”
>GbLableName=”B_2”;
>
>%Now I want to use this variable like this:
>
>lable.bot( btex GbLableName etex , (0,0) );
>
>But this will just display “GbLableName” instead of “B_2”.
>
>So can someone please tell how this can be done? I know too little about TeX.
>
>Someone suggested about using “Textext” macro. But my MPost version doesn’t have it.
>So are there any other ways of doing it?
>
>
btex ... etex is scanned by some mp tools and then tex'd; no expansion takes place then, so GBLableName becomes text
textext is more clever;
why not use metafun then? it has everything metapost + more
also,
\starttext
\startMPpage
your code
\stopMPpage
\stoptext
with
(texexec --pdf thatfile.tex)
will work ok; from within metafun/context you can use text variables (\MPstring and such); see metafun manual
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
next prev parent reply other threads:[~2004-06-13 21:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-13 16:14 vinuth madinur
2004-06-13 17:05 ` Patrick Gundlach
2004-06-13 21:21 ` Hans Hagen Outside [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-11 12:00 MPOST: How " vinuth madinur
2004-06-11 13:05 ` Patrick Gundlach
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=40CCC56D.4060506@wxs.nl \
--to=pragma@wxs.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).