You could always enclose the ${name} in an <xsl:text/> block, like this:
<!ENTITY ds "#x0024;">
<!ENTITY ob "#x007B;">
<!ENTITY cb "#x007D;">
<!-- snip -->
<xsl:text disable-output-escaping="yes">&ds;&ob;</xsl:text>
<xsl:value-of select="my-property-name"/>
<xsl:text disable-output-escaping="yes">&cb;</xsl:text>
Does that help?
Chris Greenlee
> -----Original Message-----
> From: Frank Carver [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, July 10, 2001 4:21 AM
> To: [EMAIL PROTECTED]
> Subject: Generating build files with XSLT
>
>
> There has been some discussion here about generating build
> files with XSLT, so I tried it yesterday.
> I came up against a problem which seems to be the result of
> an ANT design decision and I wonder
> if anyone has worked round it.
>
> My need is to maintain a central, large, "template" build
> file with various subsitutions in it, and generate
> a specific build file for each new project or to update the
> build file of all the existing projects when the
> template changes. This seemed an ideal use for XSLT - I
> could specify the project as a simple XML
> defintion, and the XSLT style process would merge the
> template and any extension specified in the
> project file.
>
> Unfortunately, Ant uses ${name} to refer to properties, and
> {name} is reserved XSLT syntax. When I ran
> my XSLT process the resulting build file was full of just
> "$", which made no sense to Ant.
>
> Any suggestions?
>
>
>
