Patrick Gundlach wrote:
Well, right, of course :), but it seems to me that a font in this new encoding would actually be used by context *and* inline-metafun. Unless, of course, the magic in \startMPenvironment changes. So, if we provide a fontencoding that will be used by metafun, at least the space should look right. Or, \startMPenvironment should choose a different encoding for (ConTeXt-)typesetting and metafun. But how would the rules of this decision look like?
Currently (iirc) I can say
\startMPenvironment[+] \setupencoding[default=newencoding] \switchtobodyfont[patrick] \stopMPenvironment
Text should now be in newencoding and metafun stuff in ???.
keep in mind that currently tex does not use a space either; and btex .. etex will therefore not suffer from lack of space 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 -----------------------------------------------------------------