Perhaps you could edit the tinyMCE config file to remove the unwated HTML tags? rather than doing it in XSLT.

L

no, i don't think so, the data from that rich text box is used in the site, and is perfect

we only want to give that same data trough xml to a flash, and that flash needs to get it without html markup

Sounds like you should write your own stripHtml() function since you want precise control over the output. You could do this as in-line c# or vb or javascript in your xslt file (javascript example below), or you could write your own xslt extension.

Here's how I did it in some xslt once. You'd need to modify it but I think you get the idea.

<xsl:stylesheet version="1.0"
    xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
    xmlns:msxml="urn:schemas-microsoft-com:xslt"
    xmlns:msxsl="urn:schemas-microsoft-com:xslt"
    xmlns:umbraco.library="urn:umbraco.library"
    xmlns:ps="urn:percipientstudios.xsl"
    exclude-result-prefixes="msxml umbraco.library ps">

<xsl:param name="currentPage"/>

<xsl:template match="/">
    <xsl:value-of select="ps:stripHTML($currentPage/data[@alias = 'bodyText'])"/>
</xsl:template>

<msxsl:script language="JavaScript" implements-prefix="ps">
<![CDATA[
// strip all HTML tags, as well as all text within OPTION tags
function stripHTML(oldString) {
    var newString = "";
    var inTag = false;
    var skipContents = false;
    for(var i = 0; i < oldString.length; i++) {
        if(oldString.charAt(i) == '<') {
            inTag = true;
            skipContents = (oldString.substr(i+1, 6).toUpperCase()=='OPTION');
        }
        if(oldString.charAt(i) == '>') {
            inTag = false;
        }else if(!inTag && !skipContents) {
            newString += oldString.charAt(i);
        }
    }
    return newString;
}
]]>
</msxsl:script>

You might want to replace BR's with a space rather than just removing them entirely from the xml so that sentences don't run together without a space between them as might othewise happen. Same would go for closing DIV and P tags I would think, but you'll want to do a bit of testing to be sure.

cheers,
doug.

tried josh's townson's solution first since it seems that easy...
and it seems like it does exactly what we need it to do.

so, for a quick fix i will thank josh townson

i will however take a deeper look into the solution of douglas, as i'm not familiar with incluiding other languages inside xslt,
it looks very interesting

thank you both for the efforts!

Sander

is working on a reply...