Subject: Re: [xsl] key definition From: Joerg Pietschmann <joerg.pietschmann@xxxxxx> Date: Mon, 29 Oct 2001 12:40:15 +0100 |
"Steve Renshaw" <renshaw_steve@xxxxxxxxxxx> wrote: > Second question: What happens if I encounter markup that looks like > this: > <item> > <data id="1">01</data> > <data id="10">1</data> > </item> > in which case the usage of concat($id,$value) aliases into "101" The usual trick is concat($id,':',$value) and a similar phrase in your key, with a character for ':' which can't appear in either value or is at least selected to avoid aliasing (sometimes, it is called the guard character). You can of course substitute a longer string for ':' to make aliasing more unlikely. Apart from this, XSLT is indeed lacking a really robust mechanism for building keys from compositions. HTH J.Pietschmann XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] key definition, David Carlisle | Thread | [xsl] Cross reference, grouping, so, Tom Hall |
Re: [xsl] Escaping/converting speci, David Carlisle | Date | [xsl] How to substitute a string ba, Mailer Mailer |
Month |