Cart
[Home] [By Thread] [By Date] [Recent Entries]
Peter:
At 12:16 PM 6/12/2002, you wrote: At this point I don't think its worth you spending more time on it. I just made one other reply a bit ago that may help explain the bit you where "missing". It does have some open questions that I could use some opinions on, but I'm pretty much ok with the way the grouping is currently working. All is cool then. The exception is the open question on why I can't get the key to replace the //dataset reference to work. That's what I'll play with over the next couple of days. I may end up posting back to the list again, but I'm starting to suspect there's a way to restructure the whole set of templates to deal with the data with a different line of attack that may make the whole issue go away... Hm. Well, a suggestion you made in your last message has me a *bit* concerned ... it might have been a typo, but a match="data//*/*" is very different from a match="data/*/*" (the second, a grandchild element of a data element, the first, any element descendant of a data element that is at least a grandchild). You should be sure to check out the exact semantics of '//' if you don't know them, since they're non-obvious (although they work well once you get the hang of them). If you are still mystified after a day or three of letting the grey matter work, post actual code. If necessary we can get out the heavy guns and see if Jeni wants to take a crack. :-> Cheers, Wendell
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
|
