From: Hans van der Meer <havdmeer@ziggo.nl>
To: NTG ConTeXt <ntg-context@ntg.nl>
Subject: Re: textext with plain MetaFun
Date: Mon, 21 Jan 2019 09:56:55 +0100 [thread overview]
Message-ID: <6CC770F5-890C-4D97-935F-FDC3F2856561@ziggo.nl> (raw)
In-Reply-To: <db1e96fb-df95-618e-2c44-df5cee7d93ec@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1986 bytes --]
The following always worked for me:
\starttext
\startMPpage
.. metapost code ..
\stopMPpage
\stoptext
and delivered from a ConTeXt-run a separate pdf.
dr. Hans van der Meer
> On 21 Jan 2019, at 09:43, Henri Menke <henrimenke@gmail.com> wrote:
>
> On 1/21/19 9:29 PM, Hans Hagen wrote:
>> On 1/21/2019 8:57 AM, Henri Menke wrote:
>>> Dear list,
>>>
>>> When I process the short MetaFun example
>>>
>>> beginfig(1)
>>> draw textext("MetaFun") ;
>>> endfig;
>>> end
>>>
>>> with plain MetaFun, i.e.
>>>
>>> mpost '&metafun' test.mp
>>>
>>> the resulting file only contains “unknown”. How can I get the expected
>>> output?
>> context foo.mp
>>
>> (in mkii one could use mptopdf but i have no interest in figuring out
>> some pure metapost solution when we can do the job with simple wrapping
>> in mkiv as mentioned)
>
> I tried
>
> mpost '&metafun' test.mp
> mptopdf test.1
>
> and now I have a PDF which says “unknown“. Maybe I didn't understand
> what you meant.
>
> Cheers, Henri
>
>>
>> Hans
>>
>>
>> -----------------------------------------------------------------
>> 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
> ___________________________________________________________________________________
[-- Attachment #1.2: Type: text/html, Size: 5122 bytes --]
[-- Attachment #2: Type: text/plain, Size: 492 bytes --]
___________________________________________________________________________________
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:[~2019-01-21 8:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-21 7:57 Henri Menke
2019-01-21 8:29 ` Hans Hagen
2019-01-21 8:43 ` Henri Menke
2019-01-21 8:56 ` Hans van der Meer [this message]
2019-01-21 9:40 ` luigi scarso
2019-01-21 9:47 ` Henri Menke
2019-01-21 10:00 ` luigi scarso
2019-01-21 23:54 Akira Kakuto
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=6CC770F5-890C-4D97-935F-FDC3F2856561@ziggo.nl \
--to=havdmeer@ziggo.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).