Subject: [xsl] RE: MSXML ancestor-or-self From: Dimitre Novatchev <dnovatchev@xxxxxxxxx> Date: Wed, 7 Mar 2001 13:08:34 -0800 (PST) |
Hi Mike, > the only problem is removing duplicates. Which isn't easy in this case: I > think it might need a recursive-template solution. I just posted a single XPath expression. Do you thing it's wrong? The only thing is that I used "//C" there -- in a more general case this must be "current()" Another question: Have you really changed ICL for SAG??? Cheers, Dimitre. Michael Kay wrote: > > You can't use ancestor-or-self in this case because of the > > structure of your xml. > > He was using ancestor-or-self::*/p which I think selects the correct nodes; > the only problem is removing duplicates. Which isn't easy in this case: I > think it might need a recursive-template solution. > > (There was also a question about the ordering of the axis. The answer is > that the axis is in reverse document order, but the result of the expression > is an unordered set, and the xsl:fro-each processes the set in document > order (by default). You can get reverse document order by <xsl:sort > select="position()" data-type="number" order="descending"/>) > > Mike Kay > Software AG > __________________________________________________ Do You Yahoo!? Get email at your own domain with Yahoo! Mail. http://personal.mail.yahoo.com/ XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
[xsl] RE: MSXML ancestor-or-self, Dimitre Novatchev | Thread | [xsl] RE: MSXML ancestor-or-self, Michael Kay |
RE: [xsl] XSL puzzle, Michael Kay | Date | RE: [xsl] sorting question, Michael Kay |
Month |