From mboxrd@z Thu Jan  1 00:00:00 1970
X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/9068
Path: main.gmane.org!not-for-mail
From: drymartini@gmx.de (Robbie Pickering)
Newsgroups: gmane.comp.tex.context
Subject: XML processing
Date: Mon, 26 Aug 2002 12:33:44 +0100
Sender: owner-ntg-context@let.uu.nl
Message-ID: <20020826123344.9BEC06%05570575@gmx.de>
NNTP-Posting-Host: coloc-standby.netfonds.no
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Trace: main.gmane.org 1035399427 453 80.91.224.250 (23 Oct 2002 18:57:07 GMT)
X-Complaints-To: usenet@main.gmane.org
NNTP-Posting-Date: Wed, 23 Oct 2002 18:57:07 +0000 (UTC)
Original-To: ntg-context <ntg-context@ntg.nl>
Xref: main.gmane.org gmane.comp.tex.context:9068
X-Report-Spam: http://spam.gmane.org/gmane.comp.tex.context:9068

OK, I'm stymied here.

What i'm trying to do is typeset a dictionary entry from XML. It's
relatively simple so far. But there are occasions when I'd like to have
the same tags treated differently according to the context.

We have for example definitions DEFN which are sometimes followed by an
example EGPH and sometimes not.

...
<DNUM>3</DNUM>
<DEFN>a large body, esp. of a person</DEFN>
<EGPH>he eased his bulk out of the chair</EGPH>
<DNUM>4</DNUM>
<DEFN>unpackaged cargo or goods</DEFN>

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.

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?