> 
> Mike:
> 
> As I understand it, what I'm doing here is constructing an 
> RTF and then 
> asking for its string-length. 

Sorry, yes, I read it too quickly. Actually, it's a rather neat solution
- though not necessarily very efficient!
> 
> Admittedly, when RTFs go away (in XSLT 2) I'd have to wrap 
> the copied nodes 
> in a wrapper in order to get the desired behavior; but won't 
> this work in 
> XSLT 1.0?

Yes, it should work in both XSLT 1.0 and XSLT 2.0.

Michael Kay
Software AG
home: Michael.H.Kay@xxxxxxxxxxxx
work: Michael.Kay@xxxxxxxxxxxxxx 

> 
> At 12:58 PM 5/22/2002, you wrote:
> > >
> > > But if you do
> > >
> > > <xsl:variable name="this-and-preceding-siblings">
> > >    <xsl:copy-of select=".|preceding-sibling::node()"/>
> > > </xsl:variable>
> > > <xsl:value-of 
> select="string-length($this-and-preceding-siblings)"/>
> > >
> > > you may get better results.
> > >
> >No you won't. string-length() works on the first node in the 
> supplied 
> >node-set.
> >
> >Michael Kay
> >Software AG
> >home: Michael.H.Kay@xxxxxxxxxxxx
> >work: Michael.Kay@xxxxxxxxxxxxxx
> >
> >
> >  XSL-List info and archive:  
> http://www.mulberrytech.com/xsl/xsl-list
> 
> 
> 
> ======================================================================
> Wendell Piez                            mailto:wapiez@xxxxxxxxxxxxxxxx
> Mulberry Technologies, Inc.                http://www.mulberrytech.com
> 17 West Jefferson Street                    Direct Phone: 301/315-9635
> Suite 207                                          Phone: 301/315-9631
> Rockville, MD  20850                                 Fax: 301/315-8285
> ----------------------------------------------------------------------
>    Mulberry Technologies: A Consultancy Specializing in SGML 
> and XML 
> ======================================================================
> 
> 
>  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
> 


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