Re: [xsl] Problem using preceding-sibling

Subject: Re: [xsl] Problem using preceding-sibling
From: Greg Faron <gfaron@xxxxxxxxxxxxxxxxxx>
Date: Tue, 14 May 2002 12:58:59 -0600
At 12:46 PM 5/14/2002, you wrote:
Hi Greg,

>>Note that there's no need to use xsl:element to create your elements
>>if you know what their names are.
> Unless you're customizing the optional attributes for the named
> element, which you're not doing here. :)

Could you give an example? You can create attributes with
xsl:attribute even if you're using a literal result element to create
the element on which the attribute will be placed, e.g.:

    <xsl:if test="someTest">
      <xsl:attribute name="bar">baz</xsl:attribute>

if that's what you meant?

Oopsie. I got used to reading (<>) for a "Cliff's Notes" approach to XSL coding. Back when I needed an attribute for an element, I remember only reading the "Can be Contained by" section (thereby missing the entire paragraph at the top). I guess the incorrect assumption stuck in my head.

I didn't think that Jeni would neglect to state something relevant...

Greg Faron Integre Technical Publishing Co.

XSL-List info and archive:

Current Thread