From: "Meer, H. van der" <H.vanderMeer@uva.nl>
To: ConTeXt NTG <ntg-context@ntg.nl>
Subject: \xmlcontext inoperative?
Date: Wed, 9 May 2012 12:53:36 +0000 [thread overview]
Message-ID: <B3B88C45-686A-4F06-A8CB-940BC5F404D6@uva.nl> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 926 bytes --]
Loaded xml with: xmlinclude{problem}{include}{file}
Then called up parts of its contents through a setup:
\startxmlsetups xam:define:get
% The definition is the one with content.
\xmldoiftext{#1}{.}{
\foundtrue
\xmlflush{#1}
\xmlcontext{#1}{.}
}
\stopxmlsetups
The strange thing is that the \xmlflush typesets verbatim the contents of the node called up:
<math version="2.0" xmlns="http://www.w3c.org/mathml"> <apply> <eq/> <ci> f(x) </ci> <apply> <plus/> <ci> 1 </ci> <apply> <power/> <ci> x </ci> <ci> 4 </ci> </apply> <apply> <power/> <ci> x </ci> <ci> 7 </ci> </apply> </apply> </apply> </math>
but, to my surprise the \xmlcontext{#1}{.} lets it disappear completely. So does \xmlflushcontext{#1}. In other parts of the program \xmlcontext does what it should do, thus the mkvi format seems ok.
What could have happened? Some detrimental effect of the \xmlinclude?
Hans van der Meer
[-- Attachment #1.2: Type: text/html, Size: 2784 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
___________________________________________________________________________________
next reply other threads:[~2012-05-09 12:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-09 12:53 Meer, H. van der [this message]
2012-05-09 13:39 ` Meer, H. van der
2012-05-09 14:47 ` Hans Hagen
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=B3B88C45-686A-4F06-A8CB-940BC5F404D6@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).