On Thu, May 3, 2012 at 3:13 AM, Marco wrote:

The text in Metapost adapts to the text set in ConTeXt. But the font setup should *only* be set for MetaPost, not regular text.

Does that mean, that MPenvironment is deprecated and does not work at all?

Please don't rely on my answer since I haven't been following the development as closely as I used to in past. But my guess is that the argument goes into the opposite way. I past (and still in MKII) one *had to* set up fonts twice - once for the main document and once for MetaPost since MetaPost did its own processing of labels and MetaPost didn't see the ConTeXt font setups. So it was "difficult" to convince MetaPost to use the same font. Now (as Aditya explained) metapost automatically inherits font setups from the main document and it might be that nobody ever thought of / requested / needed to have a special setup for using different font for MetaPost labels. I can think of many workarounds to this, but I agree that there is a valid reason why \startMPenvironment (or some other command) should be able to change the font inside metapost labels only. Mojca

On 2012-05-04 Aditya Mahajan wrote:

On Fri, 4 May 2012, Mojca Miklavec wrote:

...

But my guess is that the argument goes into the opposite way. I past (and still in MKII) one *had to* set up fonts twice - once for the main document and once for MetaPost since MetaPost did its own processing of labels and MetaPost didn't see the ConTeXt font setups. So it was "difficult" to convince MetaPost to use the same font.

I agree, it's a big step forward towards usability and consistency to have MetaPost automatically inherit ConTeXts settings. However, it went out-of-control now.

A better alternative would to define

\setupMPtext [ style=..., color=..., setups=..., ]

that can be used to set the style for metapost text.

+1 Marco

On 4-5-2012 09:13, Aditya Mahajan wrote:

On Fri, 4 May 2012, Mojca Miklavec wrote:

...

I can think of many workarounds to this, but I agree that there is a valid reason why \startMPenvironment (or some other command) should be able to change the font inside metapost labels only.

A better alternative would to define

\setupMPtext [ style=..., color=..., setups=..., ]

that can be used to set the style for metapost text.

As we already have instances, I've extended that mechanism, so one can say: \startsetups mp:instance:one indeed:\space \stopsetups \setupMPinstance [metafun] [textstyle=bold, textcolor=darkgreen, setups=mp:instance:one] \defineMPinstance [mympinstance] [metafun] [textcolor=red] \starttext \startMPcode draw textext("some text") ; \stopMPcode \startMPcode{mympinstance} draw textext("some text") ; \stopMPcode \stoptext

+1

Marco

So .. we know who is going to wikify this ... Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

On Sat, 5 May 2012, Marco wrote:

On 2012-05-05 Hans Hagen wrote:

That means, MPenvironment will be dropped, right? But what is the new interface, \setupMPtext or MPinstance?

\setupMPinstance The advantage is that you can have multiple instances in parallel. Aditya

On 8-5-2012 19:01, Marco wrote:

On 2012-05-05 Hans Hagen wrote:

Did I?

This code fails:

\defineMPinstance [mympinstance] [metafun] [textcolor=red]

\starttext

\startMPcode draw textext("some text") ; \stopMPcode

\startMPcode{mympinstance} draw textext("some text") ; \stopMPcode

\stoptext

Marco

It works here. Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

On 8-5-2012 19:19, Marco wrote:

On 2012-05-08 Hans Hagen wrote:

...

On 8-5-2012 19:01, Marco wrote:

...

On 2012-05-05 Hans Hagen wrote:

Did I?

My bad ;)

...

...

This code fails:

\defineMPinstance [mympinstance] [metafun] [textcolor=red]

\starttext

\startMPcode draw textext("some text") ; \stopMPcode

\startMPcode{mympinstance} draw textext("some text") ; \stopMPcode

\stoptext

Marco

It works here.

Fails here, source and log are attached.

ok, can you add this to cont-new.mkiv (after \unprotect): \def\m_meta_colo_initializations{% vardef OverlayLineColor=\MPcolor{\overlaylinecolor} enddef; vardef OverlayColor=\MPcolor{\overlaycolor} enddef; } I have that in my local experimental code. It has to do with the fact that mp's color spaces are not compatible with each other. As I've used that patch for quite a while now I could probably move it to the core. Maybe more users can test this. Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

Hello, many thanks Marco for wikifying. On Tue, 08 May 2012 21:57:04 +0200, Marco wrote:

Thanks a lot Hans for implementing this.

Wikified:

http://wiki.contextgarden.net/Command/defineMPinstance http://wiki.contextgarden.net/Command/setupMPinstance

Best wishes

Marco

With the permission, I tried to replace the tag <texcode> with <context> to get source and result. <context mode="mkiv" source="yes" text="Gives:"> ... </context> Unfortunately, the result doesn't appear. So, what to do to make the example work? Will it work automatically once the Ctx/MP engine updates on wiki? Best regards, Lukas -- Ing. Lukáš Procházka [mailto:LPr@pontex.cz] Pontex s. r. o. [mailto:pontex@pontex.cz] [http://www.pontex.cz] Bezová 1658 147 14 Praha 4 Tel: +420 244 062 238 Fax: +420 244 461 038