Is there any particular reason why we are not allowed to use elements as
content for HTML attributes ? I perfectly understand this limitation if
XML is chosen as output, but why impose it for HTML ?
One more twist to the problem: What happens if the name of the localized
resource itself (resName) is a variable coming from the XML document ? I'm
afraid <xml:text> will not be able to help us anymore ...
Regards,
Liviu
> SORRY; I completely misread the question! (I should learn not to fire from
> the hip when short on sleep.)
>
>
> The problem you're having is that attribute contents are expected to be
> text, not elements. XSLT won't let you insert the results of xsl:element
> (or even a literal result element) inside an xsl:attribute. You have to
> hand-construct that syntax as text.
>
> Try:
>
> <xsl:attribute name="value">
> <xsl:text><getLocalizedResource name="resName":gt;</xsl:text>
> </xsl:attribute>
>
>
>
>
> ______________________________________
> Joe Kesselman, IBM Next-Generation Web Technologies: XML, XSL and more.
> "may'ron DaroQbe'chugh vaj bIrIQbej" ("Put down the squeezebox and nobody
> gets hurt.")
>
