From: "Meer, H. van der" <H.vanderMeer@uva.nl>
To: NTG ConTeXt <ntg-context@ntg.nl>
Subject: select setups
Date: Sun, 21 Apr 2013 14:16:41 +0000 [thread overview]
Message-ID: <4D072670-C809-4887-BFB1-7A938D546E5D@uva.nl> (raw)
If I have various setups like:
\startxmlsetups xam:setups
\xmlsetsetup{\xmldocument}{..{xam:*}
\stopxmlsetups
\xmlregistersetup{xam:setups}
\startxmlsetups xbm:setups
\xmlsetsetup{\xmldocument}{..{xbm:*}
\stopxmlsetups
\xmlregistersetup{xbm:setups}
Is it then possible to have \xmlall{#1}{lpath} with a path such that on the top level restrictions apply to some of the xam:setups but to none of the xbm:setups?
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 / 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-04-21 14:16 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=4D072670-C809-4887-BFB1-7A938D546E5D@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).