Jeff,
This suggestion of Mike's is the one I like best so far:
At 06:06 PM 9/30/2003, he wrote:
(a) in the above template, do something to test whether it's one of the
text nodes you want to treat this way, e.g. by testing whether
<xsl:number level="any" from="p"> is 1
If you did <xsl:number level="any" from="content"
count="text()[normalize-space()]"/> and only handled number 1, you'd work
around the whitespace problem Dimitre cited without having to strip
whitespace-only nodes (always a dangerous thing in running prose). (Note
I've tweaked the from attribute to be "content" since that seems to be the
scope you are interested in.)
Of course, you'll do this in a choose/when/otherwise test, not in the
template match as I had it.
or (b) in the template rule for the <p> element, process the descendants
with a parameter set to the generate-id() of the first descendant text
node, and test this parameter in the text template.
That works too.
Ain't this list amazing?
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