From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/76074 Path: news.gmane.org!not-for-mail From: "Meer, H. van der" Newsgroups: gmane.comp.tex.context Subject: Re: \xmlcontext inoperative? Date: Wed, 9 May 2012 13:39:03 +0000 Message-ID: References: Reply-To: mailing list for ConTeXt users NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0719963072==" X-Trace: dough.gmane.org 1336570753 2325 80.91.229.3 (9 May 2012 13:39:13 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Wed, 9 May 2012 13:39:13 +0000 (UTC) To: mailing list for ConTeXt users Original-X-From: ntg-context-bounces@ntg.nl Wed May 09 15:39:12 2012 Return-path: Envelope-to: gctc-ntg-context-518@m.gmane.org Original-Received: from balder.ntg.nl ([195.12.62.10]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1SS76j-0001LY-Fg for gctc-ntg-context-518@m.gmane.org; Wed, 09 May 2012 15:39:09 +0200 Original-Received: from localhost (localhost [127.0.0.1]) by balder.ntg.nl (Postfix) with ESMTP id 2CE92101F2; Wed, 9 May 2012 15:39:09 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at balder.ntg.nl Original-Received: from balder.ntg.nl ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id XI2lxg9Qieto; Wed, 9 May 2012 15:39:07 +0200 (CEST) Original-Received: from [127.0.0.1] (localhost [127.0.0.1]) by balder.ntg.nl (Postfix) with ESMTP id 35E43101E4; Wed, 9 May 2012 15:39:07 +0200 (CEST) Original-Received: from localhost (localhost [127.0.0.1]) by balder.ntg.nl (Postfix) with ESMTP id C44A7101E4 for ; Wed, 9 May 2012 15:39:05 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at balder.ntg.nl Original-Received: from balder.ntg.nl ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id BDuEFSwgiZdZ for ; Wed, 9 May 2012 15:39:04 +0200 (CEST) Original-Received: from filter2-ams.mf.surf.net (filter2-ams.mf.surf.net [192.87.102.70]) by balder.ntg.nl (Postfix) with ESMTP id AE3E0101E3 for ; Wed, 9 May 2012 15:39:04 +0200 (CEST) Original-Received: from holleman.uva.nl (holleman.uva.nl [146.50.108.228]) by filter2-ams.mf.surf.net (8.14.3/8.14.3/Debian-9.4) with ESMTP id q49Dd3Zj020015 for ; Wed, 9 May 2012 15:39:04 +0200 Original-Received: from ketelaar.uva.nl ([fe80::cc61:4c73:c438:df97]) by holleman.uva.nl ([146.50.108.228]) with mapi id 14.01.0355.002; Wed, 9 May 2012 15:39:03 +0200 Thread-Topic: [NTG-context] \xmlcontext inoperative? Thread-Index: AQHNLeK/vsHvp7kDp0mGaFPI/7jH5JbBVOWA In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [82.95.102.36] X-Bayes-Prob: 0.0001 (Score 0, tokens from: @@RPTN) X-CanIt-Geo: ip=146.50.108.228; country=NL; region=07; city=Amsterdam; latitude=52.3500; longitude=4.9167; http://maps.google.com/maps?q=52.3500,4.9167&z=6 X-CanItPRO-Stream: uu:ntg-context@ntg.nl (inherits from uu:default, base:default) X-Canit-Stats-ID: 0QH7ND3V9 - 9086695bdc75 - 20120509 (trained as not-spam) X-Scanned-By: CanIt (www . roaringpenguin . com) on 192.87.102.70 X-BeenThere: ntg-context@ntg.nl X-Mailman-Version: 2.1.12 Precedence: list List-Id: mailing list for ConTeXt users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: ntg-context-bounces@ntg.nl Errors-To: ntg-context-bounces@ntg.nl Xref: news.gmane.org gmane.comp.tex.context:76074 Archived-At: --===============0719963072== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_A0C86D42A0444906B6FCA863C8B943A8uvanl_" --_000_A0C86D42A0444906B6FCA863C8B943A8uvanl_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable By accident I found something that seems to work. With \xmlregistereddocumentsetups{#1}{#1} put before the \xmlflush{#1} ConT= eXt processing resumes on the node. What I do not understand however, is why \xmlcontext does not work in gener= al. Is it possible to have the \xmlregistereddocumentsetups action put in somew= here or in such a way that \xmlflush and friends always succeed? I did not = understand enough of the code to fully grasp what is is is not happening. On 9 mei 2012, at 14:53, Meer, H. van der wrote: 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 t= he node called up: f(x) 1 x 4 x 7 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 --_000_A0C86D42A0444906B6FCA863C8B943A8uvanl_ Content-Type: text/html; charset="us-ascii" Content-ID: <1D802B3E42B96C429D7FF946BF2AF752@uva.nl> Content-Transfer-Encoding: quoted-printable By accident I found something that seems to work.
With \xmlregistereddocumentsetups{#1}{#1} put before the \xm= lflush{#1} ConTeXt processing resumes on the node.
What I do not understand however, is why \xmlcontext does not work in = general.
Is it possible to have the \xmlregistereddocumentsetups action put in = somewhere or in such a way that \xmlflush and friends always succeed? I did= not understand enough of the code to fully grasp what is is is not happeni= ng.

On 9 mei 2012, at 14:53, Meer, H. van der wrote:

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=3D"2.0&qu= ot; xmlns=3D"http://www.w3c.org/= mathml"> <apply> <eq/> <ci> f(x) </ci> = <apply> <plus/> <ci> 1 </ci> <apply> <powe= r/> <ci> x </ci> <ci> 4 </ci> </apply> <= ;apply> <power/> <ci> x </ci> <ci> 7 </ci> </apply> </appl= y> </apply> </math>

but,= to my surprise the \xmlcontext{#1}{.} lets it disappear completely. So doe= s \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?<= /div>

Hans van der Meer
--_000_A0C86D42A0444906B6FCA863C8B943A8uvanl_-- --===============0719963072== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline ___________________________________________________________________________________ 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 ___________________________________________________________________________________ --===============0719963072==--