From: Jan Willem Flamma <jwfregister@icloud.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: buffers inside startMPpage
Date: Fri, 14 Oct 2016 10:48:05 +0200 [thread overview]
Message-ID: <6544FF4C-D5C4-4D05-B7BF-6DCB919A0475@icloud.com> (raw)
In-Reply-To: <58009895.8050209@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2020 bytes --]
Thank you Wolfgang.
This suits my needs just fine.
Kind regards,
Jan Willem Flamma
> On 14 okt. 2016, at 10:34, Wolfgang Schuster <schuster.wolfgang@gmail.com> wrote:
>
>> Jan Willem Flamma <mailto:jwfregister@icloud.com> 14. Oktober 2016 um 10:12
>> Dear list members,
>>
>> I create all my MetaFun drawings in a separate environment file where each individual drawing sits inside a start/stopbuffer. This allows me to easily use those drawings in all my documents using \processMPbuffer[name]. Works just fine.
>>
>> However, I also wish to have all the drawing available in a pdf file (each drawing on a separate page). This allows me to split the pdf and use the drawing elsewhere (e.g. in a Powerpoint) or include page(s) from the pdf in another document.
>>
>> The below MWE represent my MetaFun drawings file.
>> The idea is that by uncommenting the \enablemode[makepdf] I can create the pdf file with drawings. It seems however that startMPpage does not accept buffers (I also tried processbuffer and processMPbuffer).
>>
>> Is it possible to somehow make this work?
> You can use
>
> \startTEXpage
> \processMPbuffer[…]
> \stopTEXpage
>
> but loading a buffer in MPpage doesn’t work because the content of the environment
> is just passed to MetaPost and buffers can’t be loaded inside MetaPost code unless
> Hans adds a function for this, e.g.
>
> \startMPcode
> buffer("mybuffer")
> \stopMPcode
>
> Wolfgang
> ___________________________________________________________________________________
> 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 : http://foundry.supelec.fr/projects/contextrev/
> wiki : http://contextgarden.net
> ___________________________________________________________________________________
[-- Attachment #1.2: Type: text/html, Size: 4429 bytes --]
[-- Attachment #2: Type: text/plain, Size: 489 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 : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2016-10-14 8:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-14 8:12 Jan Willem Flamma
2016-10-14 8:34 ` Wolfgang Schuster
2016-10-14 8:48 ` Jan Willem Flamma [this message]
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=6544FF4C-D5C4-4D05-B7BF-6DCB919A0475@icloud.com \
--to=jwfregister@icloud.com \
--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).