ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "H. van der Meer" <H.vanderMeer@uva.nl>
To: ConTeXt NTG <ntg-context@ntg.nl>
Subject: using different xml-tree's?
Date: Wed, 13 Feb 2013 21:19:46 +0100	[thread overview]
Message-ID: <FB9498AB-2972-4759-B7C3-312C3FE15AB2@uva.nl> (raw)


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

I would like to process my <dvd> nodes in more than one way but I am stuck with the implementation.

The trees could start in a different setup:
\startxmlsetups xml:dvdfirst:dvd .. \stopxmlsetups
\startxmlsetups xml:dvdfirst:setups
	\xmlsetsetup{\xmldocument}
		{error|setup|dvd ..

and

\startxmlsetups xml:dvdsecond:dvd .. \stopxmlsetups
\startxmlsetups xml:dvdsecond:setups .. 

I thought I could call the variants (data collected in a buffer) with:

	\xmlprocessbuffer{dvd}{data.xml}{xml:dvdfirst:dvd}
en
	\xmlprocessbuffer{dvd}{data.xml}{xml:dvdsecond:dvd}

But this does not work. Neither for example ..{xml:dvdfirst}

Guess I am mistreating the 3rd parameter of \xmlprocessbuffer{}{}{initial-xml-setup}. The manual says "process the tree starting with initial-xml-setup.

What am I doing wrong?

Hans van der Meer




[-- Attachment #1.2: Type: text/html, Size: 8630 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:[~2013-02-13 20:19 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=FB9498AB-2972-4759-B7C3-312C3FE15AB2@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).