John,
At 02:40 PM 2/4/2005, you wrote:
Your question has a simple answer, but it also contains a possible
"gotcha" that is potentially very important.
I think I know what you're talking about and I think this software
includes an extension function I can use to access nodes by path even if
it isn't allowed by XSL.
Yes, Saxon has a saxon:evaluate() extension for this (given an arbitrary
string, evaluate as XPath), and other processors may have their own versions.
and then spliced together, this is most easily achieved by a recursive
string-chopping template (or possibly by string-replacement functionality
in XSLT 2.0).
I can't use XSL 2 yet. I will search for recursive string-chopping; my
last search didn't find that.
Try recursive templates, string replacement: "string-chopping" is just the
way I described it (though you might get lucky).
The FAQ has a section on "General String Replace": see
http://www.dpawson.co.uk/xsl/sect2/StringReplace.html.
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>
--~--