Hi. I'm using XSLT 1.

I'm giving the following input:
<Addressees>BILLY, GROUPA (EXCLUDE BOB, JANE), JANE DOE, SMITH FAMILY (EXCLUDE TIMMY), HEIDI,</Addressees>

I need to parse that input into these fields:
<User>BILLY</User>
<User Exclude='(EXCLUDE BOB, JANE)'>GROUPA</User>
<User>JANE DOE</User>
<User Exclude='(EXCLUDE TIMMY)'>SMITH FAMILY</User>
<User>HEIDI</User>

My XSLT code so far:
<xsl:template name='parse'>
<xsl:param name='str'/>
<xsl:variable name='user' select='substring-before($str, ',')/>
<User>
<xsl:value-of select="$user"/>
</User>
<!-- Recursively call to process the remaining users -->
<xsl:call-template name='parse'>
<xsl:with-param name='str' select='normalize-space(substring-after($str, ','))/>
</xsl:call-template>
</xsl:template>

My output so far (which is wrong):
<User>BILLY</User>
<User>GROUPA (EXCLUDE BOB</User>
<User>JANE)</User>
<User>JANE DOE</User>
<User>SMITH FAMILY (EXCLUDE TIMMY)</User>
<User>HEIDI</User>

Please help. Appreciate any help.

Do you really need to do that with XSLT 1? That problem asks for more powerful string processing than XSLT 1.0 provides, at least without using extension functions.

__________________
Martin Honnen
Microsoft MVP (XML, Data Platform Development) 2005/04 - 2013/03
My blog

This one looks pretty tough - it's tricky enough in XSLT 2.0 where you have much more powerful string handling.

It might be worth looking at the parsing framework of FXSL, though there's a steep learning curve involved.

Do you *really* have to do it in 1.0?

__________________
Michael Kay
http://www.saxonica.com/
Author, XSLT 2.0 and XPath 2.0 Programmer\'s Reference

Yes, it has to done in XSLT 1.

I recently instructed that I could produce this output as alternative:

<User>BILLY</User>
<User>GROUPA</User>
<Exclude>(EXCLUDE BOB, JANE)</Exclude>
<User>JANE DOE</User>
<User>SMITH FAMILY</User>
<Exclude>(EXCLUDE TIMMY)</Exclude>
<User>HEIDI</User>

Any help is appreciated.