This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
RE: RE: Next node name
- From: "Hunsberger, Peter" <Peter dot Hunsberger at stjude dot org>
- To: "'xsl-list at lists dot mulberrytech dot com'" <xsl-list at lists dot mulberrytech dot com>
- Date: Wed, 3 Apr 2002 12:11:07 -0600
- Subject: RE: [xsl] RE: Next node name
- Reply-to: xsl-list at lists dot mulberrytech dot com
> Having said that, I'm not sure whether this is going to help you do
> what you need to do. In your example:
>
> <tu>
> <tuv>
> <seg>Use <ut>{\cs6\f1\cf6\lang1024
> </ut><b><ut>}</ut>Set<ut>{\cs6\f1\cf6\lang1024</ut></b><ut>}
> </ut> when you want to assign an object reference</seg>
> </tuv>
> </tu>
>
> There are three text nodes that are between ut elements:
>
> "<b>"
> "Set"
> "</b>"
>
> So what you'd actually get would be:
>
> <tu>
> <tuv>
> <seg>Use (%TERM%)(%TERM%)(%TERM%) when you want to assign an object
reference</seg>
> </tuv>
> </tu>
>
> I'm not sure what you should do about this because it's not clear to
> me how you can tell that the "<b>" and "</b>" text nodes
> shouldn't be replaced...
Hi Jeni,
I'm just guessing, but I'd bet that the answer to that is that the
"unneeded" nodes are in effect wrapped by text based markup consisting
(partially) of "{" and "}". If so, that suggests that one could filter on
those substrings (or the absence of them). The alternative would be to
build some key based grouping on the higher level <seg> and hope the (ahem)
mark up doesn't allow for multiple (%TERM%) in a <seg> for some other
reason?
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list