RE: [xsl] unparsed-text and for-each-group

Subject: RE: [xsl] unparsed-text and for-each-group
From: "Michael Kay" <mike@xxxxxxxxxxxx>
Date: Wed, 21 Dec 2005 18:04:25 -0000
I would tend to do it top-down: first tokenize the unparsed-text() using
two-newlines as the separator to create a set of strings representing
stanzas, then tokenize each of these to get the lines.

<for-each select="tokenize(unparsed-text(), '\n\n')">
    <for-each select="tokenize(., '\n')">
      <l><xsl:value-of select="."/></l>

Michael Kay 

> -----Original Message-----
> From: David Carlisle [mailto:davidc@xxxxxxxxx] 
> Sent: 21 December 2005 17:29
> To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> Subject: Re: [xsl] unparsed-text and for-each-group
>  Am I right in assuming that the best way to do this is two nested
>  xsl:for-each-group's using unparsed-text()?  I'm a bit 
> confused on how
>  to do the <lg> elements....
> only one unparsed-text to pull in the whole file then  use regular
> expressions, probably easiset to pu every lin ein an l first
> <xsl:variable name="lines" as="element()*"">
> <xsl:for-each 
> select="tokenize(unparsed-text('file.txt','&#13;?&#10;')">
>  <l><xsl:value-of select="."/>
> </xsl:for-each>
> </xsl:element>
> then use for-each-group to group up the versesinto lg 
> elements based on
> empty l elements.
> David
> ______________________________________________________________
> __________
> This e-mail has been scanned for all viruses by Star. The
> service is powered by MessageLabs. For more information on a proactive
> anti-virus service working around the clock, around the globe, visit:
> ______________________________________________________________
> __________

Current Thread