On 4-5-2012 13:09, Marco wrote:
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.
well, you still get text and not something random, so out-of-control is a bit too strong anyhow, we can do \newconditional\MPLIBtextgetdone \def\MPLIBsettext#1% #2% {\ifconditional\MPLIBtextgetdone \else \cldcontext{metapost.tex.get()}% \settrue\MPLIBtextgetdone % no \global needed \fi \dowithnextbox{\ctxlua{metapost.settext(\number\nextbox,#1)}}\hbox} \def\MPLIBresettexts {\ctxlua{metapost.resettextexts()}%$ \setfalse\MPLIBtextgetdone} \starttext Serif \startMPcode draw textext("\ss Sans") ; \stopMPcode Serif \startMPenvironment \ss \stopMPenvironment \startMPcode draw textext("Sans") ; \stopMPcode Serif \stoptext
A better alternative would to define
\setupMPtext [ style=..., color=..., setups=..., ]
that can be used to set the style for metapost text.
this is ok for me, but then we mighe as well drop \startMPenviroment (and someone has to wikify that then) 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 -----------------------------------------------------------------