ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Meer, H. van der" <H.vanderMeer@uva.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: include file in xml processing
Date: Fri, 20 Jan 2012 09:46:40 +0000	[thread overview]
Message-ID: <309758F8-126C-4BB4-A6A2-9732DAE8F63C@uva.nl> (raw)
In-Reply-To: <C213AAB7-C65F-407C-A22A-F49A7999248E@xs4all.nl>


[-- Attachment #1.1: Type: text/plain, Size: 1892 bytes --]

I have seen that I can load a file (containing ConTeXt code) with
\startxmlsetups xmlcommon:texinclude
\writestatus{TEST HVDM}{file: \xmlatt{#1}{file}}
\xmlload{#1}{\xmlatt{#1}{file}}
\stopxmlsetups

But how to use these loaded data? I want them included in ConTeXt-processing like this but it doesn't work:
<texinclude file="filename"/>
<tex>
\useMPgraphic{xyz}{param=285}
</tex>
The <tex> node is just a wrapper around \xmlcontext{#1}{.}

Someone who can put me on the right track?

Hans van der Meer



On 19 jan. 2012, at 21:38, Hans van der Meer wrote:

I have the following setup for use of ConTeXt code in an xml-processing setup:

% Usage: <tex> ... </tex>
\startxmlsetups xmlcommon:tex
\ignorespaces
\xmlstripnolines{#1}{.} % need to strip sufficient space characters
\xmlcontext{#1}{.}
\stopxmlsetups

Since I need some MetaPost drawings repeatedly I thought to include those from a separate file:
<tex>
\input thedirectory/thefile
\useMPgraphic{lfsr}{stages=285}
</tex>

The file is read, but typeset as is, MetaPost processing does not occur. By the way, inserting the MetaPost code in place of the \input works ok.

I also tried \usemodule[thedirectory/thefile] instead, but then nearly everything MetaPost encounters is undefined.

Does someone know how to get the file inclusion right?

Hans van der Meer



___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl<mailto: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
___________________________________________________________________________________


[-- Attachment #1.2: Type: text/html, Size: 4509 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 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://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

      reply	other threads:[~2012-01-20  9:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-19 20:38 Hans van der Meer
2012-01-20  9:46 ` Meer, H. van der [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=309758F8-126C-4BB4-A6A2-9732DAE8F63C@uva.nl \
    --to=h.vandermeer@uva.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).