Hi J�rg! > <xsl:template match="text()" name="replace"> > <xsl:param name="string" select="."/> > <xsl:choose> > <xsl:when test="contains($string,'foo')"> > <xsl:call-template name="replace"> > <xsl:param name="string" > select="substring-before($string,'foo')"/> > </xsl:call-template> > <a href="http://www.foo.com";>foo</a> > <xsl:call-template name="replace"> > <xsl:param name="string" > select="substring-after($string,'foo')"/> > </xsl:call-template> > </xsl:when> > <xsl:when test="contains($string,'bar')"> > ... like above ... > </xsl:when> > <xsl:otherwise> > <xsl:value-of select="$string"/> > </xsl:otherwise> > </xsl:choose> > </xsl:template>
Yes, it could work this way, but one problem appears: The keywords are taken out of other xml files. There are about 300 xml files with 2 ore more keywords. Summa summarum: 600 keywords. Phew! That would become a quite big stylesheet! How long does it take to parse a page with this stylesheet? ... > syntax. Also consider adding tags around the affected text for easier > matching. This is what Dave suggested too, but it can't be done this way, because while editing one file I don't know which words have to be keywords to replace. If one of the other 299 files has changed, my keyword index has probably changed too ... This seems to become tricky :-( greetings. jo seibert --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
