I think we're having problems deducing the general requirement from one
example of input and output. E.g. is it "a div element consists of a
sequence of nodes each of which is either a text node or an <a> element,
followed by a sequence of <p> elements. Output a <p> element that contains
all the material before the first input <p> element, then copy the <p>
elements."?

If that were it you could do it by:

<xsl:template match="div/node()" priority="2">
<p><xsl:copy/><p>
</xsl:template>

<xsl:template match="div/p" priority="1">
<xsl:copy/>
</xsl:template>

Mike

> -----Original Message-----
> From: Pawson, David [mailto:DPawson@xxxxxxxxxxx]
> Sent: 17 December 1999 14:59
> To: 'xsl-list@xxxxxxxxxxxxxxxx'
> Subject: RE: text() children
> 
> 
> Sorry Phil, Mike, I still can't get it.
> 
> 
> <div>Primary contributions by David Ornstein 
>    <a href="mailto:davido@xxxxxxxxxxxxx";>davido@xxxxxxxxxxxxx</a>
>       and Kai Matthews with scientific review by Dr. Karl M. Johnson. 
> <p>This document provides answers to common questions about Ebola. For
> more information about Ebola </p>
> </div>
> 
> 
> I want as output
> 
> <p>Primary contributions by David Ornstein 
>    <a href="mailto:davido@xxxxxxxxxxxxx";>davido@xxxxxxxxxxxxx</a>
>       and Kai Matthews with scientific review by Dr. Karl M. 
> Johnson. </p>
> <p>This document provides answers to common questions about Ebola. For
> more information about Ebola </p>
> 
> The input tree is mixed pcdata and elements.
> 
> If I match on div I then need to pull all the text() children nodes,
> (which will ignore the <a > content.)
> 
> If I match on div/text() I can only tag the 'bits' of text 
> either side of
> the
> <a> element, not all of it.
> 
> (xpath tool shows it up great btw) 
> 
> How can I 'gather' all the text yet still process the <a> element
> within it?
> 
> 
> regards, DaveP
> 
> 
>  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
> 


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list