Hi Peter,
At 06:28 PM 2/12/2004, you wrote:
The first template doesn't work: $mode is just a string to know what we
want/what we are doing when we are in the <car>-element, nothing more.
Right.
About the second template: so actually there hasn't changed anything since
my 'original example', except the fact that the if-test is moved into the
predicate of the xpath-expression, and 3 'new' templates which all matches
the element <car>, but each of them has a different mode (green, red and
blue). So the condition to see why we are in the <car>-element and the
simulation of multiple modes (propagating mode from <streetrace> ==> sorting
template ==> <car>) is still there?
Yes.
I'm starting to believe there is no real better solution for this; at least
if we are only using XSLT1.0 functions.
That may well be, with two caveats: (1) I hesitate to agree categorically
since we still haven't seen the actual problem (which makes it doubly hard
for me to be sure I'm actually addressing it ;-), and (2) I think you'd
still be well-served to check out the technique Dimitre uses in FXSL
(described by Mike earlier in this thread), which (as was pointed out)
doesn't actually require the node-set() extension to do its magic (it's
just some of the FXSL functions that need it IIUC).
Cheers,
Wendell
======================================================================
Wendell Piez
mailto:wapiez(_at_)mulberrytech(_dot_)com
Mulberry Technologies, Inc. http://www.mulberrytech.com
17 West Jefferson Street Direct Phone: 301/315-9635
Suite 207 Phone: 301/315-9631
Rockville, MD 20850 Fax: 301/315-8285
----------------------------------------------------------------------
Mulberry Technologies: A Consultancy Specializing in SGML and XML
======================================================================
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list