Russ,
On 2/22/2011 5:19 PM, russurquhart1(_at_)verizon(_dot_)net wrote:
I used contains because filter could have the value
filter="filter1,filter10,filter2" and i thought having a
@filter='filter1' would fail for the previous string. If that is not
the case, i'll change it, but i thought i tried that one time and it
didn't work.
No, you're right, = won't work for this, in XSLT 1.0.
Yet another reason among many to prefer XSLT 2.0 for this kind of thing
is that it makes this sort of problem considerably more tractable:
"tokenize(@filter,',\s*') = ('filter1','filter10')".
It's much harder to deal with in unextended XSLT 1.0: you either have to
work with very carefully constrained values, or get into recursive
templates to handle the strings. Or both. Or model the information in a
way more amenable to XSLT 1.0.
Cheers,
Wendell
--
======================================================================
Wendell Piez
mailto:wapiez(_at_)mulberrytech(_dot_)com
Mulberry Technologies, Inc. http://www.mulberrytech.com
17 West Jefferson Street Direct Phone: 301/315-9635
Suite 207 Phone: 301/315-9631
Rockville, MD 20850 Fax: 301/315-8285
----------------------------------------------------------------------
Mulberry Technologies: A Consultancy Specializing in SGML and XML
======================================================================
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--