This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Re: Converting attributes to elements and preserving the hierarchy
Thanks Jeni.
I knew there was something like this. Of course, I use recursively nested
element types all the time. It's come to be so ordinary that I wasn't even
able to think of it first thing in the a.m. (here).
Now we have an "impossible" on the table, it may also be worth noting how
absurdly difficult it is to do other ordinary things with for-each, like
process all children in document order regardless of their element type,
but treat each element type differently. It turns out template matching is
a simple and elegant way to drive "conditionals" through the stylesheet.
Cheers,
Wendell
At 12:06 PM 12/19/01, you wrote:
> > I wonder whether the reverse is the case. (Can anyone suggest
> > something that can't be done with a for-each, but can be done with
> > templates? I can think of things much harder to do with for-each,
> > but impossible?)
>
>It's impossible to process arbitrary levels of nesting with just
>xsl:for-each (well, unless you are prepared to generate a stylesheet
>with a stylesheet to do it!).
======================================================================
Wendell Piez mailto:wapiez@mulberrytech.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