Subject: Re: [xsl] Unexpected result from <a href="...">...</a> in some cases From: Quinn Taylor <quinntaylor@xxxxxxx> Date: Tue, 19 Aug 2008 15:05:43 -0600 |
At 2008-08-19 14:19 -0600, Quinn Taylor wrote:I've created a recursive template (printRecursivePath) to process a
directory path and build up a string of links from the right side so
as to correctly increase the number of "../" elements for parent link.
Sorry ... I do not understand what you want.
What result to you expect for your test string "/path/to/resource"?
What result to you expect for "/to/resource"?
What result to you expect for "/resource"?
What result to you expect for "resource"?
The problem occurs for path components between the first and the last component.
Because you are not passing your intermediate results to the recursively called template.
<snip>
But I'm only guessing what you want from your succinct description. If you give some examples then someone on the list can probably guide you to the right result.
For now, though, look at what I'm doing below when I pass the intermediate results to the called template ... that may be the bit you are missing. When I write recursive templates I always need to keep track of what is being built along the way, or the intermediate work gets lost. This appears to be the evidence you are presenting, so I'm guessing that is your issue.
Note that even what I have below is incomplete since I don't know what you want to do with "resource" as your input path.
I hope this helps.
. . . . . . . . . . . . Ken
Thanks, - Quinn
<snip>
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] Unexpected result from <a, G. Ken Holman | Thread | Re: [xsl] Unexpected result from <a, Quinn Taylor |
Re: [xsl] Unexpected result from <a, G. Ken Holman | Date | Re: [xsl] Unexpected result from <a, Quinn Taylor |
Month |