From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
Henri Menke <henrimenke@gmail.com>
Subject: Re: Wrong MetaPost text output
Date: Sun, 11 Aug 2019 19:30:13 +0200 [thread overview]
Message-ID: <653f0ae2-644c-1f25-6e18-4cbc52ca9a17@xs4all.nl> (raw)
In-Reply-To: <f91fa2a9-61e3-d6dc-695e-1a6f2128c6df@gmail.com>
On 8/11/2019 6:09 PM, Henri Menke wrote:
> Dear devs,
>
> There seems to be a bug in the MetaPost integration of ConTeXt. The MWE
> below should produce three different labels “dummy foo bar” but instead
> produces “bar bar bar”. The same example works correctly in plain
> MetaPost. Originally reported on
>
> https://tex.stackexchange.com/questions/503773/strange-behaviour-of-the-btex-etex-construct
>
> Cheers, Henri
>
> ---
>
> \starttext
> \startMPpage
> def drawtest(expr i) = %i is not used here
> draw btex dummy etex shifted (0,0);
> draw btex foo etex shifted (1.5cm,0);
> draw btex bar etex shifted (3cm,0);
> enddef;
> drawtest(5);
> \stopMPpage
> \stoptext
It's not a really bug but a side effect. When metapost parses btex ..
etex it immediately replaces its content. In mpost the program that is
hardcoded as 'call out to tex and convert the dvi result into a
picture'. This parsing is not 'delayed' by wrapping in macro.
So in this case, what happens is that where normally there is some
interplay between context and the library, this kind of gets messed up.
Using btex inside a macro body is just a bad idea.
def drawtest(expr i) = %i is not used here
draw textext("dummy") shifted (0,0);
draw textext("foo") shifted (1.5cm,0);
draw textext("bar") shifted (3cm,0);
enddef;
works fine because it is not replaced in the macro body when parsed.
In context lmtx I will give a warning when "btex .. etex" is used inside
a macro definition. Actually btex/etex is just supported in context as a
kind of 'service' (we could just drop it).
Anyway, you can advice not to use "btex .. etex" but textext instead. As
with all things tex (and mp) with some hasty programming much can be
solved but in this case it's not worth the effort and for sure it will
bring up other side effects.
(In a similar fashion it's not a good idea to have global textexts
because there are local stored for them but in that case one can enforce
a persistent textext if needed.)
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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:[~2019-08-11 17:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-11 16:09 Henri Menke
2019-08-11 17:30 ` Hans Hagen [this message]
[not found] ` <02a522d1-29a6-09f2-2818-8007f2bf088c@xs4all.nl>
2019-08-11 18:12 ` Henri Menke
2019-08-11 20:19 ` Alan Braslau
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=653f0ae2-644c-1f25-6e18-4cbc52ca9a17@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=henrimenke@gmail.com \
--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).