From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: staticMPfigure
Date: Thu, 10 Apr 2008 18:10:33 +0200 [thread overview]
Message-ID: <47FE3BF9.20205@wxs.nl> (raw)
In-Reply-To: <47FE5523.4741.1F28078@wwl.musensturm.de>
Wolfgang Werners-Lucchini wrote:
> Hallo Hans,
>
>>>> the following example is a cooked down version of something I
>> found
>>>> on the net. Compiling this
>>>>
>>>> %------------------------------------------------
>>>> \setupcolors[state=start]
>>>>
>>>> \forceMPTEXcheck{LABEL}
>>>>
>>>> \startMPinclusions
>>>> vardef LABEL@\#(expr s, p)= label@\#(textext("%
>>>> \framed[width=1.5cm]{" & s & "}"),p)
>>>> enddef ;
>>>> \stopMPinclusions
>>> I could not get this to work either. Something has changed
>>> in the MPinclusions parsing, maybe? (Putting the definition
>>> in a separate mp file prevents the error, of course)
>> hm, i'll have a look, but in mkiv there will be no such checks
>> supported
>> anyway
>
> Have you had a look?
\setupcolors[state=start]
\forceMPTEXcheck{LABEL}
\startMPinclusions
vardef LABEL@\#(expr s, p)=
label@\#(textext("\framed[width=1.5cm]{xxx" & s & "xx}"),p) enddef ;
\stopMPinclusions
\startMPpage
LABEL("oeps",origin) ;
\stopMPpage
works ok on my machine using pdftex but luatex gives an unknown (have to
look into it)
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
-----------------------------------------------------------------
___________________________________________________________________________________
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://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2008-04-10 16:10 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.4251.1207220924.4340.ntg-context@ntg.nl>
2008-04-10 15:57 ` staticMPfigure Wolfgang Werners-Lucchini
2008-04-10 16:10 ` Hans Hagen [this message]
2008-04-10 21:41 ` staticMPfigure Aditya Mahajan
2008-04-10 22:01 ` staticMPfigure Mojca Miklavec
2008-04-10 22:23 ` staticMPfigure Aditya Mahajan
2008-04-10 22:38 ` staticMPfigure Mojca Miklavec
2008-04-11 7:44 ` staticMPfigure Hans Hagen
2008-04-11 10:31 ` staticMPfigure Mojca Miklavec
2008-04-11 12:16 ` staticMPfigure Hans Hagen
2008-06-10 10:02 staticMPfigure bbvogel
2008-06-10 12:50 ` staticMPfigure Hans Hagen
2008-06-10 13:31 ` staticMPfigure bbvogel
2008-06-10 14:18 ` staticMPfigure Peter Rolf
2008-06-11 6:57 ` staticMPfigure bbvogel
2008-06-11 9:41 ` staticMPfigure bbvogel
2008-06-11 10:07 ` staticMPfigure Peter Rolf
2008-06-11 11:41 ` staticMPfigure bbvogel
2008-06-11 12:27 ` staticMPfigure Peter Rolf
-- strict thread matches above, loose matches on Subject: below --
2008-04-02 20:22 staticMPfigure Wolfgang Werners-Lucchini
2008-04-03 9:12 ` staticMPfigure Taco Hoekwater
2008-04-03 10:19 ` staticMPfigure Hans Hagen
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=47FE3BF9.20205@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).