From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/9072 Path: main.gmane.org!not-for-mail From: Simon Pepping Newsgroups: gmane.comp.tex.context Subject: Re: XML processing Date: Mon, 26 Aug 2002 20:53:12 +0200 Sender: owner-ntg-context@let.uu.nl Message-ID: <20020826205312.B649@scaprea> References: <20020826123344.9BEC06%05570575@gmx.de> NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1035399431 495 80.91.224.250 (23 Oct 2002 18:57:11 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Wed, 23 Oct 2002 18:57:11 +0000 (UTC) Original-To: ntg-context In-Reply-To: <20020826123344.9BEC06%05570575@gmx.de>; from drymartini@gmx.de on Mon, Aug 26, 2002 at 12:33:44PM +0100 Xref: main.gmane.org gmane.comp.tex.context:9072 X-Report-Spam: http://spam.gmane.org/gmane.comp.tex.context:9072 On Mon, Aug 26, 2002 at 12:33:44PM +0100, Robbie Pickering wrote: > We have for example definitions DEFN which are sometimes followed by an > example EGPH and sometimes not. > > ... > 3 > a large body, esp. of a person > he eased his bulk out of the chair > 4 > unpackaged cargo or goods > > I have setup DEFN very simply > > \defineXMLenvironment [DEFN] {}{.} > to add a full stop after the definition. It would be nice, though, to be > able to automatically add a colon instead in those cases where the DEFN > environment is immediately followed by a EGPH. This is very difficult, because your tagging has no moment at which this can be concluded: is too early to know, but when there is no following EGPH, there is nothing that can trigger the period or colon. It would be easier if the whole definition would be in a container: . Then you can save EGPH, and could typeset it with preceding colon, or it could typeset a period. > is the XML parsing code robust enough that one could start messing > around with counters, etc. in the arguments of a \defineXMLenvironment? > Or is there a better way of going about this? XML parsing is robust enough. In the docbook mapping a context stack and a depth counter are maintained. Simon -- Simon Pepping email: spepping@scaprea.hobby.nl