From: Hans Hagen <pragma@wxs.nl>
To: Sergey Slyusarev <cph.lmy@gmail.com>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Bug: \textext inside \*MPinclusions causes error
Date: Tue, 14 Feb 2017 13:13:00 +0100 [thread overview]
Message-ID: <503245d1-35ef-4bd3-16e2-fb9a316fb4f0@wxs.nl> (raw)
In-Reply-To: <CAHUe7fAn24d3SYmA=yvt+XSt_NbnCxHcXz-smm3wQ8BFjUTo_Q@mail.gmail.com>
On 2/13/2017 11:36 PM, Sergey Slyusarev wrote:
>> It's a single tex run so you can do:
>> \starttext
>> \newbox\MyMpBox \setbox\MyMpBox\hbox{foo}
>> \startMPcode
>> draw textext("\copy\MyMpBox") ;
>> \stopMPcode
>> \startMPcode
>> draw textext("\copy\MyMpBox") rotated 45;
>> \stopMPcode
>> \stoptext
>
> This is not much different from:
>
> \starttext
>
> \startMPinclusions
>
> string t;
>
> t := "foo";
>
> \stopMPinclusions
>
> \startMPcode
>
> draw textext(t);
>
> \stopMPcode
>
> \startMPcode
>
> draw textext(t) rotated 45;
>
> \stopMPcode
>
> \stoptext
>
>
> but the problem was not with passing just text, but with more complex
> images that may or may not contain text, without specifically addressing
> text after image is defined.
\starttext
\startMPinclusions
vardef my_text_t =
textext("foo")
enddef ;
\stopMPinclusions
\startMPcode
draw textext(my_text_t);
\stopMPcode
\startMPcode
draw textext(my_text_t) rotated 45;
\stopMPcode
\stoptext
-----------------------------------------------------------------
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:[~2017-02-14 12:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-16 19:31 Sergey Slyusarev
2017-01-17 8:35 ` Hans Hagen
2017-01-21 21:13 ` Sergey Slyusarev
2017-01-22 12:23 ` Hans Hagen
2017-02-13 22:36 ` Sergey Slyusarev
2017-02-14 12:13 ` Hans Hagen [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-01-12 11:23 Sergey Slyusarev
2017-01-15 17:55 ` Hans Hagen
2017-01-11 22:08 Sergey Slyusarev
2017-01-12 9:06 ` Hans Hagen
2017-01-12 16:53 ` 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=503245d1-35ef-4bd3-16e2-fb9a316fb4f0@wxs.nl \
--to=pragma@wxs.nl \
--cc=cph.lmy@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).