From: Hans Hagen <pragma@wxs.nl>
Subject: Re: betex -etex block parsing bug
Date: Tue, 20 Dec 2005 21:53:30 +0100 [thread overview]
Message-ID: <43A86F4A.7060806@wxs.nl> (raw)
In-Reply-To: <43A862B0.9060301@boede.nl>
Willi Egger wrote:
> Hi,
>
> It seems that there is a problem with parsing betex - etex blocks in
> the following situation:
> I can not say with which version this has been introduced. (I messed
> up my old TeX, so I have only new ones)
> I tested this with the version of 19-12-2005 an 30-11-2005.
>
> \setMPtext{1}{CENTER}
>
> \startuseMPgraphic{TEST}
> picture Text;
> Text := \MPbetex{1};
> draw Text;
> \stopuseMPgraphic
>
> the betex-etex block will look like 'tex CENTERetex' of course the
> etex should be separated by a space.
> For testing I attach the minimal file.
this was the old code:
% \def\MPtext #1{\getvalue{\@@MPT#1}}
% \def\MPstring #1{"\getvalue{\@@MPT#1}"}
% \def\MPbetex #1{btex \getvalue{\@@MPT#1} etex}
but due to some reported problems with undefined texts, it became
\def\MPtext #1{\executeifdefined{\@@MPT#1}\empty}
\def\MPstring #1{"\executeifdefined{\@@MPT#1}\empty"}
\def\MPbetex #1{btex \executeifdefined{\@@MPT#1}\empty etex}
so, let's add a space:
\def\MPbetex #1{btex \executeifdefined{\@@MPT#1}\empty\space etex}
(interesting is that it runs ok here -)
Hans
next prev parent reply other threads:[~2005-12-20 20:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-20 19:59 Willi Egger
2005-12-20 20:53 ` Hans Hagen [this message]
2005-12-20 21:15 ` Willi Egger
2005-12-20 22:20 ` Hans Hagen
2005-12-21 9:26 ` Willi Egger
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=43A86F4A.7060806@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).