Subject: [xsl] Profiling Number Ranges From: Naomi Gronson <naomi_gronson@xxxxxxxxx> Date: Thu, 18 Nov 2004 06:58:44 -0800 (PST) |
I have a profiling filter that removes certain elements prior to publish. I've been enabling the content owners to apply multiple attribute values to content within Epic Editor. For most information this is relatively straightforward, the problem comes in with SystemLevel: <para SystemLevel="5.1;5.2;6.0">Now reboot.</para> <para SystemLevel="5.0;5.5;9.2">Log out and go eat a snack.</para> I've allowed users to make selections in the filter such as "5.1" (using contains()) but the trouble is when I try to implement the range feature to give the user a greater than/less than like "5.1+" $SystemLevel = "5.1+" <!-- This code worked when only one SystemLevel attribute value was allowed --> <xsl:when test="contains($SystemLevel, '+') and @SystemLevel and (not(@SystemLevel >= translate($SystemLevel, '+', '')))"> <xsl:message>Process: Suppressing <xsl:value-of select="name()"/> with SystemLevel = <xsl:value-of select="@SystemLevel"/> and Profile of <xsl:value-of select="$SystemLevel"/>.</xsl:message> <xsl:apply-templates mode="suppress"/> </xsl:when> You can probably see the the dilemma now. Does anyone know an approach that could be used to somehow take a list of a few attribute values ("5.1;5.2;6.0") and use the >= greater than symbol to suppress content in which none of the values match the greater than criteria? Would the values need to be parsed in order to do this, etc.? Thanks for the help. Naomi __________________________________ Do you Yahoo!? The all-new My Yahoo! - Get yours free! http://my.yahoo.com
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
RE: [xsl] Sorting RTF, Paul Hebble | Thread | RE: [xsl] Profiling Number Ranges, Michael Kay |
RE: [xsl] Simple XML to XML transfo, Joe Fawcett | Date | [xsl] Re: Problem passing node-set , Charlie Consumer |
Month |