I never saw that before too,
but changing for <a></a> solved the display problem...
maybe a bug on Firefox on linux...
Finally, there were many templates to redefined (anchor, titles, etc.)
so I made an ant regex replace on generated files and it works fine.
thanks for your suggestion, I keep it in mind for another time, it
could be usefull.
Marie.
Oliver Becker a écrit :
Marie
Sauvage - EBM WebSourcing wrote:
<xsl:if test="$conditional = 0 or
$node/@id or $node/@xml:id">
<a name="{$id}">.</a>
</xsl:if>
but when I put no content (or a space)
between opening and closing tag (instead of the point here), it's
written in my html generated file like before with simply <a
name="xxx" />. Do you know what does it ? I'm using Ant and Xalan,
is it it ? Do you know a way to force this ?
I'll maybe have a look in an ant regex replacement...
From the XML point of view, <a></a> and <a /> are
totally equivalent.
There's no way in XSLT to enforce one of these outputs.
A single space is stripped from the stylesheet, so using
<a name="{$id}"> </a>
won't help.
However
<a name="{$id}"><xsl:text> </xsl:text></a>
should do it.
What I don't understand is, why <a name=.../> renders a link.
There's no href attribute. I've never heard that browsers have a
problem with link anchors.
Anyway, hope the xsl:text trick helps.
Oliver
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Scanned with Copfilter Version 0.83beta3a (P3Scan 2.2.1)
AntiSpam: SpamAssassin 3.1.4
by Markus Madlener @ http://www.copfilter.org
