[XSL-LIST Mailing List Archive Home]
[By Thread]
[By Date]
Thanks for all the suggestions. Unfortunately, the ones that work are easy enough to do by hand but difficult if not impossible to do in a conversion program. I don't see a way to determine in code where to put the variable binding statement. It would be entirely dependent on the surrounding XSL code.
In any case, I discovered that I can solve the particular construct we use most commonly by recoding it as following-sibling::*.
Thanks, again, everyone.
On Tuesday, April 15, 2003, at 06:04 PM, Wendell Piez wrote:
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Re: [xsl] XSL to XSLT conversion issue
Subject: Re: [xsl] XSL to XSLT conversion issue From: Jim Hart <jhart@xxxxxxxxx> Date: Tue, 15 Apr 2003 18:43:57 -0400 |
Thanks for all the suggestions. Unfortunately, the ones that work are easy enough to do by hand but difficult if not impossible to do in a conversion program. I don't see a way to determine in code where to put the variable binding statement. It would be entirely dependent on the surrounding XSL code.
In any case, I discovered that I can solve the particular construct we use most commonly by recoding it as following-sibling::*.
Thanks, again, everyone.
On Tuesday, April 15, 2003, at 06:04 PM, Wendell Piez wrote:
No, but it is easy enough to bind the position of the current node outside a predicate or other context that changes the context node, then test against the variable.
Jim Hart, Project Manager Academic Technology Services Library and Information Services Bates College Lewiston, Maine, USA
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] XSL to XSLT conversion is, Wendell Piez | Thread | [xsl] How to specify output file ex, Matthew Zimmerman |
[xsl] collecting data using xml/xsl, Kathy Burke | Date | Re: [xsl] XSL to XSLT conversion is, J.Pietschmann |
Month |
Keywords