From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/7438 Path: main.gmane.org!not-for-mail From: Michael Wiedmann Newsgroups: gmane.comp.tex.context Subject: Re: XML Processing Instructions Date: Sat, 23 Mar 2002 14:28:55 +0100 Sender: owner-ntg-context@let.uu.nl Message-ID: <20020323132855.GA2032@miwie.in-berlin.de> References: <20020318201136.GA7141@miwie.in-berlin.de> <20020321203641.F375@scaprea> NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1035397901 19246 80.91.224.250 (23 Oct 2002 18:31:41 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Wed, 23 Oct 2002 18:31:41 +0000 (UTC) Original-To: NTG ConTeXt In-Reply-To: <20020321203641.F375@scaprea> Xref: main.gmane.org gmane.comp.tex.context:7438 X-Report-Spam: http://spam.gmane.org/gmane.comp.tex.context:7438 * Simon Pepping [020321 20:36]: ... > \defineXMLprocessor[some-pi] \dosomepi > \def\dosomepi#1{(Some PI: #1)} ... > That is because context expects a form like . The > data are inserted as a single token after the defined XML processor, > and thus can be picked up by it as an argument. If no processor is > defined, the data is ignored. Thanks Simon, it works like you pointed out, *but*: in contrary e.g. to the handling of PIs in DocBook DSSSL styleheets *and* against my understanding of the definition for PIs, ConTeXt forces to use a 'data' field in PIs (like ) though alone should be sufficient. ConText stops processing the current element content in the last case. Or do I still miss something. Michael -- mw@miwie.in-berlin.de http://www.miwie.org mw@miwie.org