From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: inclusion of tex code in xml context
Date: Tue, 07 May 2013 19:41:53 +0200 [thread overview]
Message-ID: <51893CE1.8080101@wxs.nl> (raw)
In-Reply-To: <6F0C616B-48F5-4B7B-AB8F-F977243ED26C@uva.nl>
On 5/7/2013 2:18 PM, Meer, H. van der wrote:
> I have some difficulties understanding the intake of ConTeXt-code in an XML processing environment.
> The setup is as follows.
>
> \startbuffer[buffername]
> \startuseMPgraphic{graphicname}{}
> ...
> \stopuseMPgraphic
> \stopbuffer
>
> Processing inside xmlsetup:
>
> \startxmlsetups xmlcommon:mpgraphic
> Here I want to read the buffer and then call it up with
> \useMPgraphic{graphicname}{}
> \stopxmlsetups
>
> This works if I pack the graphic definition in the buffer inside a <tex></tex> node and call
> \xmlprocessbuffer{tex}{\xmlatt{#1}{buffer}}{}
> where <tex> is a ConTeXt processing setup.
>
> This actuallty works, but has the drawback of putting the ConTeXt code inside <tex></tex> thereby makeing it difficult to reuse the definition of the graphic in a non XML-context. I thus want to get rid of the <tex></tex> enclosure.
>
> I tried things like
> \xmlloadbuffer{tex}{\xmlatt{#1}{buffer}}
> \xmlsetup{tex}{xmlcommon:tex} <== the tex processing xmlsetups
> But this does not work. Because the graphic in this case is not found by \useMPgraphic.
> Clearly I am misunderstanding some of the intricacies of the xmlloading macros and probably the solution is quite simple. But I cannot find the right way to do it.
> Any help would be appreciated.
you can look for \xmlcontext and \xmlflushcontext
-----------------------------------------------------------------
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
-----------------------------------------------------------------
___________________________________________________________________________________
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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2013-05-07 17:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-07 12:18 Meer, H. van der
2013-05-07 17:41 ` Hans Hagen [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=51893CE1.8080101@wxs.nl \
--to=pragma@wxs.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).