RE: Problem using preceding-sibling

Thanks everybody,
The reason I have added xsl:element is that I generate the xsl file
automatically according to a look-up table which translate the element names
in other names, which of course was not visible from my simple xml file.
But, I learnt a lot following the discussion.
Thanks again,
Faroukh
-----Original Message-----
From: owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx
[mailto:owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx]On Behalf Of Greg Faron
Sent: Tuesday, May 14, 2002 1:59 PM
To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
Subject: Re:  Problem using preceding-sibling


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.:
>
>   <foo>
>     <xsl:if test="someTest">
>       <xsl:attribute name="bar">baz</xsl:attribute>
>     </xsl:if>
>   </foo>
>
>if that's what you meant?

   Oopsie.  I got used to reading www.topxml.com
(<http://www.topxml.com/xsl/elmxsl_attribute.asp>) 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:  http://www.mulberrytech.com/xsl/xsl-list


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list