Hi Susan,
At 05:38 PM 11/11/2010, Gerrit wrote:
On 11.11.2010 23:24, Susan Bodnik wrote:
Wendell, thanks for your reply - much appreciated.
I made the following change to the
template:<xsl:for-each-groupselect="//indexterm"group-by="(@term.entry,text()[1])">
Try "(@term.entry,text())[1]" as Wendell suggested, which is just a
shorthand for
if (@term.entry) then @term.entry else text()
This is true with one tiny caveat: if indexterm ever has mixed
content, particularly more than one text node. I don't think you want
any indexterms with more than a single text node to appear as many
times as they have text nodes, each time with that fragment of text.
(This can sometimes happen if comments or processing instructions,
not only inline elements, happen to intervene.)
<indexterm>Global <!-- was "World" -->Health</indexterm>
There are two text nodes there, with the values "Global " and "Health".
That's another reason why group-by="(@term.entry,.)[1]" is probably better.
Or, in Gerrit's more transparent style, "if (@term.entry) then
@term.entry else ."
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>
--~--